|
Focus on Linux
Live Upgrade for Linux Mar 25 2003 07:41PM Kelly Sauke (ksauke fastenal com) (5 replies) Re: Live Upgrade for Linux Mar 25 2003 09:42PM Seth Arnold (sarnold wirex com) (4 replies) Re: Live Upgrade for Linux Mar 25 2003 08:20PM Kelly Sauke (ksauke fastenal com) (7 replies) Re: Live Upgrade for Linux Apr 02 2003 02:33AM James F. Wilkus (tflat astrocreep net) (1 replies) Re: Live Upgrade for Linux Apr 08 2003 01:39PM Noah K Sematimba (ksemat ksemat co ug) (1 replies) Re: Live Upgrade for Linux Apr 08 2003 10:04PM Axel Beckert - ecos gmbh (beckert ecos de) (1 replies) RE: Live Upgrade for Linux Mar 26 2003 06:31PM Mario Aguilera (marioa lf-mail com) (3 replies) Re: Live Upgrade for Linux Mar 26 2003 06:11PM Seth Arnold (sarnold wirex com) (1 replies) Re: Live Upgrade for Linux Mar 26 2003 11:14PM Eric Rostetter (eric rostetter physics utexas edu) (3 replies) |
|
Privacy Statement |
Good news: rolling your own isn't to hard.
You can use user mode Linux (UML) to test a system configuration/etc (of
course you can't fully test hardware issues, but it will let you test the
software/etc).
You could use vmware to test a system configuration/etc (of course you can't
fully test hardware issues, but it will let you test the software/etc).
You can setup extra partitions, i.e. /var2, /usr2, /etc2, whatever and
populate them, many RPM's are relocatable, although not all are. One way to
get around this would be to chroot into the alternate "/" and then install
/etc, reconfigure your lilo.conf/grub.conf, and if it goes boom reboot to
the original system. i.e. copy all the rpm's into a dir then do a
rpm -Uvh --force --nodep *.rpm, make sure /dev/ is created, copy in /etc,
and so on.
You could use a tool such as alien to rip the rpm apart and turn it into a
tarball, thus allowing you to forcibly relocate files if the rpm doesn't
support relocation.
http://www.seifried.org/lasg/software/
Hope this helps.
Kurt Seifried, kurt (at) seifried (dot) org [email concealed]
A15B BEE5 B391 B9AD B0EF
AEB0 AD63 0B4E AD56 E574
http://seifried.org/security/
[ reply ]