-----BEGIN PGP SIGNED MESSAGE----- Dear suse-security-announce subscriber and SuSE Linux user, With the release of the SuSE Linux 8.2 i386 ftp version, we announce that the SuSE Linux 7.1 distribution will be discontinued for all architectures. Our SLES (SuSE Linux Enterprise Server) products and the products based on SLES are not affected by this announcement. Vulnerabilities found after Friday, May 16 2002, will not be fixed for SuSE Linux 7.1 any more. After two years of successful use, SuSE Linux 7.1 will free resources for the newly released products. By consequence, the 7.1 distribution directories on our ftp server ftp.suse.com have been moved to the /pub/suse/discontinued/ directory tree structure; the 7.1 directories in the update trees will follow near the end of May, soon after all pending update packages have been published. SuSE puts much effort into adding security improvements (patches) to the software. We usually do not publish new versions of a software package because new features and changed behaviour of a single package can jeopardize the seamless operation of the product as a whole. Over the lifetime of a SuSE Linux distribution, this causes an increasing workload on the SuSE Security Team and SuSE software engineering in general: The older the product (and the package versions in it) is, the more work is needed to prepare patches that fix security related malfunctions. This forces us to focus on the SuSE Linux distributions of a newer release date to ensure that our customers can continuously take advantage of the quality that they are used to with SuSE products. Please note that our SuSE Linux Enterprise Server products have a longer support lifetime which is completely independent from the SuSE Linux distributions. To learn more about the SuSE Linux Enterprise Server product family, please visit http://www.suse.de/en/business/products/index.html . As usual, SuSE will continue to provide update packages for the remaining distributions SuSE-7.2 SuSE-7.3 SuSE-8.0 SuSE-8.1 and SuSE-8.2 for a two-year period after the release of the respective distribution. If you have any questions regarding this announcement, please do not hesitate to direct your questions to security@suse.de (SuSE security contact). Regards, Roman Drahtmüller, SuSE Security. - - | Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, | SuSE Linux AG - Security Phone: // you need vision!" | Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless | - - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPr+qfXey5gA9JdPZAQEAygf+KEI9PrsUt9jqjV4qGYDI2LfMzEswGaTg VfjuJoy9bg+/6LZMk7FSdO3R19ndhNw/C5vXGIad2ta2xgdOuVit9I2POQ6gn7z+ ufUeNBPHI2u0Iv+aDTVemfyjrtwRdWrbL1ygBMr0PxnnowjRmXruK9Q+IGwaJkjo ZjFvK76GER0LkQKfijNr6XvjliFGAqESEAASrzrP8IQwYURjFoBRqze2+T+kUKgo 2pUa5t+WecxqZG7I9hgOti/9sQAuwfMN7uaONVEt6BdIsJki3zL5erPTQjoiprlD kExFoCEydhlL/xjcrEo0PJsPXKH/evxbrQjfcOqQrfsTmJlirCAj4Q== =e7cv -----END PGP SIGNATURE-----
Dear suse-security team,
With the release of the SuSE Linux 8.2 i386 ftp version, we announce that the SuSE Linux 7.1 distribution will be discontinued for all architectures.
I have still a server running on Suse 7.1 and I do not want to change to a newer Linux, as I think the saying: "Never change a running system" is correct. On the other hand. as there are no updates anymore for security leaks I think I will have to switch to a newer Suse ... My problem: The machine is a server which should be running permanently. So I should update the system while running the machine ... any ideas if there are problems updating the system to 8.2 from 7.1 ... I can remember I had to work for two days to get my server running again, when I upgraded from 6.3 to 7.1 ... as the directories, etc. did not fit anymore ... :-(((( Any hints or other suggestions? ThanX, Martin ----------------------------------------------------------------- Dipl.-Ing. Martin Schichl SC&C Software, Communication & Consulting GmbH & Co KEG Grottenhofstr. 3, A-8053 Graz Tel. +43/(0)316/265-205, Fax +43/(0)316/265-234 mschichl@scc.co.at, http://scc.co.at
On May 14, Martin Schichl <mschichl@scc.co.at> wrote:
I have still a server running on Suse 7.1 [...] My problem: The machine is a server which should be running permanently. So I should update the system while running the machine ... any ideas if there are problems updating the system to 8.2 from 7.1 ... I would install 8.2 on a new harddisk, copy all settings from the 7.1 machine and swap disks (this saves you from doing a backup ;) or copy the new installation over the old one.
I can remember I had to work for two days to get my server running again, when I upgraded from 6.3 to 7.1 ... as the directories, etc. did not fit anymore ... :-(((( Will be the same with 8.2, lots of things have changed (which is good IMHO, because it means that there is still some movement in the distribution).
Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \
On Wed, 2003-05-14 at 07:08, Markus Gaugusch wrote:
On May 14, Martin Schichl <mschichl@scc.co.at> wrote:
I have still a server running on Suse 7.1 [...] My problem: The machine is a server which should be running permanently. So I should update the system while running the machine ... any ideas if there are problems updating the system to 8.2 from 7.1 ... I would install 8.2 on a new harddisk, copy all settings from the 7.1 machine and swap disks (this saves you from doing a backup ;) or copy the new installation over the old one.
I can remember I had to work for two days to get my server running again, when I upgraded from 6.3 to 7.1 ... as the directories, etc. did not fit anymore ... :-(((( Will be the same with 8.2, lots of things have changed (which is good IMHO, because it means that there is still some movement in the distribution).
Markus --
Another GOOD reason for the new disk is they don't last forever and you could avoid a real disaster now by upgrading to 8.2 now. Harddrives fail when you least expect them and always when you can afford it the least. Ken
On Wed, 14 May 2003, Markus Gaugusch wrote:
On May 14, Martin Schichl <mschichl@scc.co.at> wrote:
I have still a server running on Suse 7.1 [...] My problem: The machine is a server which should be running permanently. So I should update the system while running the machine ... any ideas if there are problems updating the system to 8.2 from 7.1 ... I would install 8.2 on a new harddisk, copy all settings from the 7.1 machine and swap disks (this saves you from doing a backup ;) or copy the new installation over the old one.
Part of the question is how permanent "permanent" is. If you can handle an hour downtime I'd sit down with a desktop already running 8.2 and do the full setup for the server using the AutoYast dialogue. The only downtime you'll see is the time it takes to move the OS onto the machine. Less than an hour. If that's too much, Markus' suggestion is your only option.
I can remember I had to work for two days to get my server running again, when I upgraded from 6.3 to 7.1 ... as the directories, etc. did not fit anymore ... :-(((( Will be the same with 8.2, lots of things have changed (which is good IMHO, because it means that there is still some movement in the distribution).
Part of the reason I rarely skip a release is I get to solve those differences little by little, spending less time and causing less frustration each time. Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 teknisk@mi.uib.no Email: bjornts@mi.uib.no http://www.mi.uib.no/
participants (5)
-
Bjorn Tore Sund -
Ken Schneider -
Markus Gaugusch -
Martin Schichl -
Roman Drahtmueller