>On Mon, 10 Jul 2000, Mike Keithley wrote about, Re: Slackware 7.1 text.gz foot disk:
>> >On Sun, 09 Jul 2000, Mike Keithley wrote about, Slackware 7.1 text.gz foot disk:
>> >> Beware of the text.gz rootdisk in Slackware 7.1. It does not have SCSI
>> >> device files and it seems some of the errorchecking code has been
>> >> removed from the setup script.
>
>After trying what you describe i think i have an answer for you, however a
>question first.
>
>Was there any problems finding your disks when you booted with the new
>disks.???
>
Yes, the setup script said I didn't have a Linux partition set up. I
did, though as /dev/sdb1. On checking /dev I found no sdd device files
at all.
>I booted from a cdrom however i dont think its a question of which boot
>medium one uses, if a device is not there then the device file is NOT
>created, let me explain, i do not have a /dev/hda or hda only hda and hdd,
>my HardDisk is a SCSI /dev/sda, i checked /dev right after booting i found
>/dev/sda /dev/sda1 up to 10 which is correct, my disk has 10 partitions,
>there was no /dev/hda or hdb and as a matter of fact no /dev/hdd either,
>the only hdX was hdc my cdrom, hdd is a cdwriter.
>
Although I used the cdrom to install software, I used the "tradiitional"
method of making boot and root floppies. It would seem booting via
cdrom give a root filesystem where the /dev/sd* divice files are present.
>So i belive you jumped the gun as it were, as the /dev/ entries are created
>AFTER you partition the drive(s), or thats what i think, i could not check
>that as my drive was partitioned before hand.
>Would you like to comment on that.?
>
Since the /dev/sd* device files were't there in the root floppy, there
would be no way to partition a SCSI disk using that floppy. In my case,
fdisk would want /dev/sdb, which wasn't there. I got around this
problem by using an older (4.0) rootdisk.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs