At 10:12 AM 20/04/00 -0700, Lee Wilson wrote:
> >So I switched to a text console, and tried 'fdisk /dev/rd/c0d0' but it
> >didn't work. I knew the device had to be there somewhere, so I went
> >looking. I eventually found the device in /tmp/rd/ as c0d0. This appears to
> >be a RedHat-ism.
>
> How odd. Good to know though.
>
>
> I DID finally get the system to work, but since I was in a hurry and
> the OS was freshly installed anyway, I just re-installed the OS from
> scratch using the RH6.2 CD. On install, the system saw the raid (on
> /dev/rd/c0d0 -- go figure) and allowed me to format and use it. Now
> everything seems to be working great.
>
> Next time though, I will know about this issue and to possibly do a
> modprobe as well.
Another seemingly RedHat-ism is that all device entries on the boot system
are created in /tmp while Disk Druid plainly says they are in /dev. Disk
Druid hides this fact from you. They will end up on /dev once the install
is completed, but for the moment they are located in /tmp to get the system
set up. One major thing lacking in Disk Druid is the ability to "Refresh
disks/devices" so that you can manually go in with fdisk and then use Disk
Druid to select the mount points, etc, without rebooting the box.
--
-=[ Stuart Young (Aka Cefiar) ]=-------------------------------
| http://amarok.glasswings.com.au/ | [EMAIL PROTECTED] |
---------------------------------------------------------------
