Re: dist-upgrade on remote server
On Tue, Feb 05, 2002 at 02:35:30PM +0100, Andreas Rabus wrote: > > Is it possible to compile a new kernel befor the reboot? kernel-package is your friend :-) never manualy install a kernel, create a deb and install that instead. > Whats about > Our remote box has an RAID Controler from GDT whos driver surely is not in > the default kernel... You might be surprised. The 2.4.x series kernel packages are fully modular and have nearly everything compiled as a module. I haven't needed to compile my own kernel since they came out, except when I needed wierd patches applied. However, make sure you pick the right kernel, and make sure the right modules will be loaded when it boots. I installed the 2.4-17-686 kernel on this machine before I remembered it was a Pentium classic (-586tsc) not a Celeron. Fortunately I remembered while the reboot countdown was going, so I stopped it and installed the right one (only to still stuff it up). The discover package is pretty cool for automaticly loading the right modules. It gets it right about 90% of the time. The only thing I've seen it get wrong was the rtl8139 instead of 8139too for the 2.4.x kernels. But the safe way is modconf :-) Oh, yeah, the other thing to make sure of is your lilo.conf needs the initrd entry for the 2.4.x kernels. > > -Ursprüngliche Nachricht- > Von: Donovan Baarda [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 5. Februar 2002 14:08 > An: I. Forbes > Cc: Andreas Rabus; debian-isp@lists.debian.org > Betreff: Re: dist-upgrade on remote server > > > On Tue, Feb 05, 2002 at 11:52:49AM +0200, I. Forbes wrote: > > Hello Andreas > > > > It should be possible. I upgraded a number machines from slink to > > potato - remotely but I have not started on remote potato to woody > > upgrades yet. If helps if you have practised on a local machine. > > > > I suggest you take a few precautions: > [...] > > - be vary careful before you re-boot the machine. > > I just had to travel to a server that failed to come up from a reboot after > remote upgrade to woody. The problem was kernel-2.4.17's initrd stuff didn't > automaticly load the AHA-2940 module... In the 2.2.x series kernel this must > have been compiled in, but for the new 2.4.x series it needed an entry in > /etc/modules. I ended up manualy running modconf to add it in, then > dpkg-reconfigure'd the kernel to make sure the initrd had it in. Another > option that _might_ have worked is installing discover... > > Just something else to be wary of :-( > > > -- > -- > ABO: finger [EMAIL PROTECTED] for more info, including pgp key > -- > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key --
Re: dist-upgrade on remote server
On Tue, Feb 05, 2002 at 02:35:30PM +0100, Andreas Rabus wrote: > > Is it possible to compile a new kernel befor the reboot? kernel-package is your friend :-) never manualy install a kernel, create a deb and install that instead. > Whats about > Our remote box has an RAID Controler from GDT whos driver surely is not in > the default kernel... You might be surprised. The 2.4.x series kernel packages are fully modular and have nearly everything compiled as a module. I haven't needed to compile my own kernel since they came out, except when I needed wierd patches applied. However, make sure you pick the right kernel, and make sure the right modules will be loaded when it boots. I installed the 2.4-17-686 kernel on this machine before I remembered it was a Pentium classic (-586tsc) not a Celeron. Fortunately I remembered while the reboot countdown was going, so I stopped it and installed the right one (only to still stuff it up). The discover package is pretty cool for automaticly loading the right modules. It gets it right about 90% of the time. The only thing I've seen it get wrong was the rtl8139 instead of 8139too for the 2.4.x kernels. But the safe way is modconf :-) Oh, yeah, the other thing to make sure of is your lilo.conf needs the initrd entry for the 2.4.x kernels. > > -Ursprüngliche Nachricht- > Von: Donovan Baarda [mailto:[EMAIL PROTECTED]] > Gesendet: Dienstag, 5. Februar 2002 14:08 > An: I. Forbes > Cc: Andreas Rabus; [EMAIL PROTECTED] > Betreff: Re: dist-upgrade on remote server > > > On Tue, Feb 05, 2002 at 11:52:49AM +0200, I. Forbes wrote: > > Hello Andreas > > > > It should be possible. I upgraded a number machines from slink to > > potato - remotely but I have not started on remote potato to woody > > upgrades yet. If helps if you have practised on a local machine. > > > > I suggest you take a few precautions: > [...] > > - be vary careful before you re-boot the machine. > > I just had to travel to a server that failed to come up from a reboot after > remote upgrade to woody. The problem was kernel-2.4.17's initrd stuff didn't > automaticly load the AHA-2940 module... In the 2.2.x series kernel this must > have been compiled in, but for the new 2.4.x series it needed an entry in > /etc/modules. I ended up manualy running modconf to add it in, then > dpkg-reconfigure'd the kernel to make sure the initrd had it in. Another > option that _might_ have worked is installing discover... > > Just something else to be wary of :-( > > > -- > -- > ABO: finger [EMAIL PROTECTED] for more info, including pgp key > -- > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade on remote server
On Tue, Feb 05, 2002 at 11:52:49AM +0200, I. Forbes wrote: > Hello Andreas > > It should be possible. I upgraded a number machines from slink to > potato - remotely but I have not started on remote potato to woody > upgrades yet. If helps if you have practised on a local machine. > > I suggest you take a few precautions: [...] > - be vary careful before you re-boot the machine. I just had to travel to a server that failed to come up from a reboot after remote upgrade to woody. The problem was kernel-2.4.17's initrd stuff didn't automaticly load the AHA-2940 module... In the 2.2.x series kernel this must have been compiled in, but for the new 2.4.x series it needed an entry in /etc/modules. I ended up manualy running modconf to add it in, then dpkg-reconfigure'd the kernel to make sure the initrd had it in. Another option that _might_ have worked is installing discover... Just something else to be wary of :-( -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key --
Re: dist-upgrade on remote server
On Tue, Feb 05, 2002 at 11:52:49AM +0200, I. Forbes wrote: > Hello Andreas > > It should be possible. I upgraded a number machines from slink to > potato - remotely but I have not started on remote potato to woody > upgrades yet. If helps if you have practised on a local machine. > > I suggest you take a few precautions: [...] > - be vary careful before you re-boot the machine. I just had to travel to a server that failed to come up from a reboot after remote upgrade to woody. The problem was kernel-2.4.17's initrd stuff didn't automaticly load the AHA-2940 module... In the 2.2.x series kernel this must have been compiled in, but for the new 2.4.x series it needed an entry in /etc/modules. I ended up manualy running modconf to add it in, then dpkg-reconfigure'd the kernel to make sure the initrd had it in. Another option that _might_ have worked is installing discover... Just something else to be wary of :-( -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dist-upgrade on remote server
Hello Andreas It should be possible. I upgraded a number machines from slink to potato - remotely but I have not started on remote potato to woody upgrades yet. If helps if you have practised on a local machine. I suggest you take a few precautions: - use apt-get -d to download everything you need before you start. - open 3 or more ssh sessions. Setup a ping in the spare sessions. Then if you loose your main one, the others should still be open to give you a "back door". This can save you if something crashes during the setup of the new ssh. - use "script" or something similar to keep a record of the screen dump. Then if you miss a warning or error you can go back and read it. - be vary careful before you do anything that changes ipchains rules. - be vary careful before you re-boot the machine. Let me know how it goes. Good Luck. Ian On 4 Feb 2002, at 15:16, Andreas Rabus wrote: > > Hi, > > there was an thread about potaota/woody on the weekend, but i didn't get an > important answer: > I'd like to "dist-upgrade" our potato InternetServer in production to woodo > and i have only a ssh and telnet-ssl connection to that box. > > So, what's the best way to do it? > > If i lost net connection, i'm stuck. (Grab a monitor, a keyboard etc. take > it to the cellar of the box at the other end of the city, reboot, wait, > repait and menawhile i got a few hoers downtime...) > That's s.th. i'm afaraid of so i should try to avoid it... > > But how can a connecten get lost whiel dist-upgrade and what can i do to > avoid this? > > I have an other box wich ist nearly similar t that interbox in the LAN, so i > can try it there first, but they dont share the network connectin and > config. An i can't switch boxes, the are to different. > > Has anybody done s.th. like that before? With succes? Failed? > > ar > > Andreas Rabus > entity38 AG > > Theresienstraße 29 > 80333 München > > Tel +49 (89) 286772-27 > Fax +49 (89) 286772-21 > ISDN +49 (89) 286772-30 > ICQ #132675697 > > [EMAIL PROTECTED] > www.entity38.de > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > - Ian Forbes ZSD http://www.zsd.co.za Office: +27 21 683-1388 Fax: +27 21 674-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa -
Re: dist-upgrade on remote server
Hello Andreas It should be possible. I upgraded a number machines from slink to potato - remotely but I have not started on remote potato to woody upgrades yet. If helps if you have practised on a local machine. I suggest you take a few precautions: - use apt-get -d to download everything you need before you start. - open 3 or more ssh sessions. Setup a ping in the spare sessions. Then if you loose your main one, the others should still be open to give you a "back door". This can save you if something crashes during the setup of the new ssh. - use "script" or something similar to keep a record of the screen dump. Then if you miss a warning or error you can go back and read it. - be vary careful before you do anything that changes ipchains rules. - be vary careful before you re-boot the machine. Let me know how it goes. Good Luck. Ian On 4 Feb 2002, at 15:16, Andreas Rabus wrote: > > Hi, > > there was an thread about potaota/woody on the weekend, but i didn't get an > important answer: > I'd like to "dist-upgrade" our potato InternetServer in production to woodo > and i have only a ssh and telnet-ssl connection to that box. > > So, what's the best way to do it? > > If i lost net connection, i'm stuck. (Grab a monitor, a keyboard etc. take > it to the cellar of the box at the other end of the city, reboot, wait, > repait and menawhile i got a few hoers downtime...) > That's s.th. i'm afaraid of so i should try to avoid it... > > But how can a connecten get lost whiel dist-upgrade and what can i do to > avoid this? > > I have an other box wich ist nearly similar t that interbox in the LAN, so i > can try it there first, but they dont share the network connectin and > config. An i can't switch boxes, the are to different. > > Has anybody done s.th. like that before? With succes? Failed? > > ar > > Andreas Rabus > entity38 AG > > Theresienstraße 29 > 80333 München > > Tel +49 (89) 286772-27 > Fax +49 (89) 286772-21 > ISDN +49 (89) 286772-30 > ICQ #132675697 > > [EMAIL PROTECTED] > www.entity38.de > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > - Ian Forbes ZSD http://www.zsd.co.za Office: +27 21 683-1388 Fax: +27 21 674-1106 Snail Mail: P.O. Box 46827, Glosderry, 7702, South Africa - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: dist-upgrade on remote server
Whenever I did an apt-get dist-upgrade I never had a problem with doing that. To be safe, I believe what you could do, is edit your sources.list to woody, and then do "apt-get update" to get the newest list. Then you could apt-get install ssh, and I believe it should upgrade your version if there have been updates. Then do a dist-upgrade and it won't touch ssh. I've had debian on my webserver for a year or so, and installed many times on my laptop or pc, and never had any problems with dist-upgrading. -Original Message- From: Andreas Rabus [mailto:[EMAIL PROTECTED] Sent: Monday, February 04, 2002 9:16 AM To: Debian ISP List (E-Mail) Subject: dist-upgrade on remote server Hi, there was an thread about potaota/woody on the weekend, but i didn't get an important answer: I'd like to "dist-upgrade" our potato InternetServer in production to woodo and i have only a ssh and telnet-ssl connection to that box. So, what's the best way to do it? If i lost net connection, i'm stuck. (Grab a monitor, a keyboard etc. take it to the cellar of the box at the other end of the city, reboot, wait, repait and menawhile i got a few hoers downtime...) That's s.th. i'm afaraid of so i should try to avoid it... But how can a connecten get lost whiel dist-upgrade and what can i do to avoid this? I have an other box wich ist nearly similar t that interbox in the LAN, so i can try it there first, but they dont share the network connectin and config. An i can't switch boxes, the are to different. Has anybody done s.th. like that before? With succes? Failed? ar Andreas Rabus entity38 AG Theresienstraße 29 80333 München Tel +49 (89) 286772-27 Fax +49 (89) 286772-21 ISDN +49 (89) 286772-30 ICQ #132675697 [EMAIL PROTECTED] www.entity38.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: dist-upgrade on remote server
Whenever I did an apt-get dist-upgrade I never had a problem with doing that. To be safe, I believe what you could do, is edit your sources.list to woody, and then do "apt-get update" to get the newest list. Then you could apt-get install ssh, and I believe it should upgrade your version if there have been updates. Then do a dist-upgrade and it won't touch ssh. I've had debian on my webserver for a year or so, and installed many times on my laptop or pc, and never had any problems with dist-upgrading. -Original Message- From: Andreas Rabus [mailto:[EMAIL PROTECTED]] Sent: Monday, February 04, 2002 9:16 AM To: Debian ISP List (E-Mail) Subject: dist-upgrade on remote server Hi, there was an thread about potaota/woody on the weekend, but i didn't get an important answer: I'd like to "dist-upgrade" our potato InternetServer in production to woodo and i have only a ssh and telnet-ssl connection to that box. So, what's the best way to do it? If i lost net connection, i'm stuck. (Grab a monitor, a keyboard etc. take it to the cellar of the box at the other end of the city, reboot, wait, repait and menawhile i got a few hoers downtime...) That's s.th. i'm afaraid of so i should try to avoid it... But how can a connecten get lost whiel dist-upgrade and what can i do to avoid this? I have an other box wich ist nearly similar t that interbox in the LAN, so i can try it there first, but they dont share the network connectin and config. An i can't switch boxes, the are to different. Has anybody done s.th. like that before? With succes? Failed? ar Andreas Rabus entity38 AG Theresienstraße 29 80333 München Tel +49 (89) 286772-27 Fax +49 (89) 286772-21 ISDN +49 (89) 286772-30 ICQ #132675697 [EMAIL PROTECTED] www.entity38.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
