[NTLUG:Discuss] kernel sees CDROM on /dev/hdc during bootup,
Victor Brilon
victor at vail.net
Mon Jun 4 08:11:21 CDT 2001
Doing a 'mknod /dev/hdc b 22 0' *should* create the proper device block
for the cdrom drive. You should also have a program in /dev called
MAKEDEV. Run that as: 'MAKEDEV hdc' and it'll also create the device
for you.
Victor
On 04-Jun-2001 Richard Geoffrion wrote:
> I had the CDROM as primary-slave at one point, but to no avail.
>
> As for the mknod command. I verified that it IS on the installation
> file
> system, but I don't know how to use it. 'mknod -b hdc' didn't
> work....it
> gave me a seg. fault. What would be the correct command?
>
> while I'm waiting... This computer has a samsung hard drive....I
> remember
> that some of the old IDE hard drives had a setting for master/no
> slave and
> master w/slave. I'll try researching that.
>
> ----- Original Message -----
> From: "Daniel Hauck" <xdesign at hotmail.com>
> To: <discuss at ntlug.org>
> Sent: Monday, June 04, 2001 7:24 AM
> Subject: Re: [NTLUG:Discuss] kernel sees CDROM on /dev/hdc during
> bootup,
> but can't mount it..
>
>
>> I haven't played with slackware for years but I can suggest that you
>> just
>> create the /dev entry by using the mknod command.
>>
>> I recall from my early experience with slackware that it didn't like
> having
>> non-contiguous IDE devices. So if your CDROM was Secondary Master
>> and
> there
>> was no Primary Slave, there was a problem. In other words, if there
>> is no
>> device on /dev/hdb it will not register a device on /dev/hdc. At
>> least
>> that's the way it used to be. It sort of makes sense in a way
>> too... in a
>> weird sort of way.
>>
>> So have you tried to mknod an entry??
>>
>
>
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
--
Victor Brilon
victor at vail.net
http://www.victorland.com
Thought for the day --
For my birthday I got a humidifier and a dehumidifier. I put
them in the same room and let them fight it out.
--Steven Wright
More information about the Discuss
mailing list