In message <>, "Adam C. Powell, IV" writes:
> Bob Taylor wrote:
>
> > In message <[EMAIL PROTECTED]>, "Adam C. Powell, IV" writes:
> > > Bob Taylor wrote:
> > >
> > > > I cp'd the new kernel to /vmlinux.gz and rebooted. Naturally, I have
> > > > forgotten a step or ten as the new kernel will not boot. So ...
> > >
> > > Er, you did rename the old kernel, right? Let's say you renamed it to
> > > oldvmlinux.gz.
> > >
> > > In MILO, just type:
> > > boot <partition>:oldvmlinux.gz root=/dev/<partition>
> > >
> > > where <partition> is the disk partition where root lives (hda2 for mine).
> > >
> > > If you didn't rename the old kernel (i.e. you overwrote it with the new
> > > one), this will be somewhat more involved... But it is definitely still
> > > possible to recover.
> >
> > Ah ... I cp'd the old kernel to /mvlinux-old.gz and cp'd the new kernel
> > to /vmlinux.gz. I understood milo looked for a file name so that's why
> > I did this.
> >
> > My system is using AlphaBIOS so milo > is nowwhere to be seen. I could
> > really use some guidance.
> >
> > I have dd'd milo, lx164, and ramdisk images from the Alpha CD onto seperate
> > floppies on my Intel box. I tried booting that way with no luck. I have
> > the official boxed set from Red Hat.
>
> Okay, when the BIOS comes up, after it has tested RAM and probed for disks
> etc., does it give you an OS selection menu and count down for start? If so,
> press F2 to change the configuration, and follow the menus to (I think it's
> called) OS selection utility. In that area, either add a new selection with
> the same parameters as before but with the old kernel's filename
> (vmlinux-old.gz), or else just change the existing selection to point to the
> old kernel. (A new selection is probably better, so you can try a bunch of
> different configurations and switch easily between new and old if they don't
> work.)
I had done all of this.
> I hope this works! (It is odd, though, that the floppies don't boot...
> I don't know what might be wrong there.)
I finally got the milo prompt. I then ran the command "boot floppy" with
the kernel boot disk and have successfully re-installed 5.1. After the
installation told me to reboot and I did so, I executed dd if=/dev/fd0
of=/dev/sda2 bs=1440k where /dev/fd0 was the milo disk and sda2 is the
milo partition. I'm hesitant to reboot until I settle some questions.
1. Is the dd command I did correct?
2. What argument to make to compile a new kernel--boot or zImage or ?
3. On the HD originally there was a file named lx164 in /boot. Now /boot
is empty. Why?
4. Executing man <whatever> segfaults. Is this a known problem?
Thanks to all who have responded.
Bob
--
+---------------------------------------------------------------+
| Bob Taylor Email: [EMAIL PROTECTED] |
|---------------------------------------------------------------|
| Like the ad says, at 300 dpi you can tell she's wearing a |
| swimsuit. At 600 dpi you can tell it's wet. At 1200 dpi you |
| can tell it's painted on. I suppose at 2400 dpi you can tell |
| if the paint is giving her a rash. (So says Joshua R. Poulson)|
+---------------------------------------------------------------+
