In message <>, "Adam C. Powell, IV" writes:
> Bob Taylor wrote:
[snip]
> > 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?
>
> Interesting- a direct inverse of the dd to make a milo floppy. I'm not sure
>if
> this will work.
I created the milo floppy on my Intel box with the command "dd if=/mnt/cdrom/
images/milo.img of=/dev/fd0"
> Try mounting /dev/sda2 as, say, /milo, and see what you find
>.
> You should see two executables: linload.exe and milo. My guess is that you j
>ust
> created a single .img-style file with dd. But you should be able to make a v
>iable
> linload.exe and milo just by mounting the milo floppy and copying * into /mil
>o
> (=/dev/sda2). (This is how I updated milo from RH 5.0 to 5.1, though I'm not
> certain it's the "right" way to do things. :-)
Hm. I don't have a directory /milo. What fs is it? Msdos?
> > 2. What argument to make to compile a new kernel--boot or zImage or ?
>
> I use "make dep clean boot modules modules_install", where boot is the import
>ant
> one, then "cp arch/alpha/boot/vmlinux.gz /vmlinux-2.1.125.gz" and edit the OS
> selection next time I cycle power. Since milo can boot a gzipped kernel, the
>re's
> no need for zimage on Alpha.
Ok. This is what I thought. However, I have read in the documentation I
have that the Alpha can't do modules. I would certainly like to use them.
> > 3. On the HD originally there was a file named lx164 in /boot. Now /boot is
> > empty. Why?
>
> My /boot has always been empty. Shouldn't be a problem.
I think VAResearch made a mistake on this.
> > 4. Executing man <whatever> segfaults. Is this a known problem?
>
> Yes. It is listed in the RedHat 5.1 errata. Get and install the new rpm, or
> download the source .tar.gz from ftp.win.tue.nl:/pub/linux/util/man .
Thanks. I forgot to check the errata. I didn't even think to. Sorry.
This is where I am before I read this post:
1. I recompiled the kernel with SCSI tape support and Sound Blaster support.
2. With much trepidation, I rebooted.
3. The system came up fine with the new kernel running.
BTW, I re-partitioned my HD wiping out the original milo partition. I read
the documentation (by documentation I mean Linux Alpha Installation Addendum
by Red Hat) to find if I should have an entry in /etc/fstab for /milo. I
didn't find any so left it empty.
The instruction I followed to load milo and linload.exe onto the milo
partition (sda2) is on page 10 of Red Hat's Alpha Installation Addendum.
The bottom line seems to be that my system is properly set up (I guess!).
However, there is still the question in my mind--why did the system boot
when I first powered up and failed rebooting a recompiled kernel and now
boots properly after a re-installation and recompiled kernel? Weird!
Thanks for putting up with me and your help. I really appreciate it!
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)|
+---------------------------------------------------------------+
