- Do an RPM listing before you start, and filter it through egrep -v '(^lib|^kernel|pubkey)';
- The older RPMs don’t try to update themselves first, so after establishing your package sources, start with urpmi urpmi libkrb53 iptables libstdc++6;
- The libstdc++6 part might be optional if the machine will never run a GUI, but I still recommend it;
- The iptables part might be optional if the machine does not run a firewall, masquerade or anything, but I still recommend it;
- The libkrb53 is not optional, without it you will break rpm – oops – and will have to hand-install it by rpm2cpio-ing the rpm (on another machine), tarring it up and unpacking it by hand;
- Do not attempt this over a mere 256kb ADSL uplink unless you have a day or so to spare;
- Do have plenty of space free on /var, since the older urpmi will download everything (typically ~300 packages) it thinks it needs before trying to install anything;
- If you cannot easily get to the machine (in case it breaks during this step), add the --test option, come back to it after it’s finished downloading, and re-run urpmi without --test;
- You will probably have to make the new initrd by hand, and tell the boot-loader about it;
- (update) AMaViS-NG will clobber its configuration and the die horribly (ie silently on each connection even with full logging) when you restore the configuration; replace it with amavisd-new instead;
- You will probably have to uninstall devfs by hand, and use chkconfig to tee up udev to start automatically;
- An older urpmi will probably not work correctly with rsync, so be prepared with correct HTTP or FTP URLs;
- When the first bout of installing has finished, reboot into the newer kernel. At this stage, you will also have a newer installer;
- Re-run urpmi like this urpmi $(cat list.of.rpms); when it breaks, either uninstall the offending (obsolete) packages from the system or delete them from the list, and try again; be prepared to iterate three or four times until urpmi is willing to fly solo;
- Watch the first twenty or so packages install; they will be “unimportant” things like basesystem and glibc.
Hi, Darl. I see you’re being dishonest again . It’d be really nice if you could shoot straight for a change, but I think Kerry’s Dad will be selling snowplows in Hell first. Three years ago, when I first joined The SCO Group, we focused the company on the area that was most profitable and provided the most benefit to customers, investors, resellers, developers and employees: UNIX No, you focused the company on suing people, which was most profitable to lawyers and provided some golden parachutes for your buddies. People thought we were crazy. They were right. But since SCO owns the UNIX operating system The SCO Group does not own UNIX® in any sense of the word. The Open Group owns the UNIX trademark, definition and other rights , The SCO Group does not. The SCO Group doesn’t even own the UnixWare® or OpenServer® code, the rights to those are held by Novell and TSG use them only by permission and under certain conditions — which they have violate...
Comments