RE: Ver. 7.2 block device definition errors
"Santos, Luis-Rodrigues" <[email protected]>
| Newsgroups | gmane.linux.redhat.release.enigma |
|---|---|
| Message-ID | <7D7D7C7B0749D411BC5C0008C7731D91016089E4@ptvwaepasx001.autoeuropa.vwg> |
Steve, The question about the failing of the cdrom to mount is not dumb, the one about the "l" was IMHO. It was not my intention to be paternalist or something like that, although I work with computers for almost 20 years I'm not on IT business and I'm just a curious guy that is tired of having to work with Windows, struggling to work with Linux. My apologies to you, and to the forum for eating bandwith. Luis Santos > -----Original Message----- > From: Steve R. [SMTP:[email protected]] > Sent: Friday, March 14, 2003 5:20 AM > To: [email protected] > Subject: RE: Ver. 7.2 block device definition errors > > Luis, > I don't think this is a dumb question. I honestly > believe there is a bug in this installer. FYI: I am > also an IT professional. I have been in the field for > over 20 years and functioned as everything from a > Windows desktop support staff person to a network > admin. It is ONLY Unix / Linux o/s that is new to me. > I have three comprehensive books on the subjects and > have followed ALL of the recommended mounting > techniques including the ones you just described and > the damn thing SITLL won't mount! The /mnt/cdrom > directory was created by default during the install > and even issuing the command you mention here it gives > me the same stupid error! The cdrom IS already by > itself on the second ide controller as the master > device and I get the same error even if I attempt to > mount /dev/hdc /mnt/cdrom "this is not a valid block > device". Even though the attributes for /dev/hdc show > it to be a block device - go figure! > I am not offended by your words - just frustrated that > this is not working and I have been fighting it for > three evenings now. The very first time I installed > this operating system the cdrom did work and I was > able to mount it but now mysteriously after reloading > the operating system to correct a kernel error I am > dealing with this. > I appreciate your time in responding to my emails and > I will look into the support sites you mentioned. > > Regards; > Steve R. > >