On Thu, 14 Jan 1999, Michael Perry wrote:
> Johnson points out in his followup post. Now when I decide to compile
> a kernel at /dev/hdb1 what do I do to get it seen? I have no lilo
> there to run and the /vmlinuz.slak is copied from /dev/hdb1 to
> /dev/hda2. If I run the /sbin/lilo on /dev/hda2 it will just see the
> /vmlinuz.slak I placed there before.
Well, I still say, you didn't need to copy it over in the first place, but
hey that's just me.:-) It'll work on it's own partition if lilo is setup
right. Actually, now that you mention it, I'd like to know that too: For
those that dualbooted dists and had one kernel copied over, how did you
recompile the second kernel and update it? Is this a dumb question? Did
you just compile in the other dist, and then copy it over again and run
lilo?
Do me a favor? When you get RH5.2 on board and up and running, can you
give me your opinion on it? I was running ( on different occasions ) RH5.0
and a net upgraded 5.0->5.1, but haven't done the 5.2 thing yet. I might
get a copy this weekend. I'd like to hear what your view is on runing
RH5.2, and what you like/don't like. I had some issues with 5.0-5.1 and
I'd like to see if 5.2 is any better. ( I wanted glibc and
didn't want to mess with S.u.S.E. in light of coming 6.0. Some apps I was
working with needed threaded X libs.)
-M
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
