Thanks to everyone's help, I successfully moved from 2.2.18pre21 to 2.2.19.
Not a big leap, admittedly, but this was more of a feasibility study
than a real need. Actually, it was a good thing I took this rather
small step instead of a big one.
I don't current backup my Linux files (don't ha
due to recommendations on the list about not using the HFS stuff
built into the kernel (file corruptions issues), i use the hfsutils
utilities to copy my new kernels into the system folder.
If fact at one time i had a pretty neat script that would:
- copy new vmlinux/System.map to /boot (with
On Sun, Dec 30, 2001 at 11:10:36AM -0500, William C Brennan wrote:
> Folks,
>
> Okay, I'm ready to take the plunge and upgrade my kernel (first to
> the most recent potato, then probably to woody), but I'm a fairly
The potato and woody kernels are basically the same (2.2.19 and 2.2.20
I think).
If you keep your kernels in a folder in your system folder, I suggest
putting the kernel folder on your shared partition, and then making an alias
of that folder and putting the alias in your system folder. That way when you
copy the vmlinux file over to the kernel folder and then reboot, your
Folks,
Okay, I'm ready to take the plunge and upgrade my kernel (first to
the most recent potato, then probably to woody), but I'm a fairly
naive user, so I could use a little help.
I've got an OldWorld Mac (PowerMac 7200) which means I'm using BootX
(ver 1.2.2) by necessity. BootX requires
5 matches
Mail list logo
