Thanks again Civileme for answering my messages,
I hope my mailer does better this time around.  I have a
pretty generic setup hardware wise I believe.  It's a six
month old Hewlett Packard Pavilion 6540C, Intel Celeron
466Mhz.  All onboard junk video/audio/modem I junked
the modem in favor of a external USR model which worked
flawlessly in MDK 6.1 I need to  read my floppy which has
the RPMS to drive my on board video (i810 based) it all
worked in the 6.1 version.  I used the "recommended"
install, Lothar entered a bogus "scuzzy" device for an alternate
CD-ROM (two on the list).  I can spin the floppy with a manual
mount command but nothing shows on the /mnt/floppy
directory?  I'm still using VGA16 which won't let me see
all the options in the config GUI displays.
Thanks again for taking the time to mess with
all this "newbie" stuff!
Vern

----- Original Message -----
From: Civileme <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, March 25, 2000 2:35 AM
Subject: Re: [expert] accessing floppy and cdrom?


> Vern asked:
>
> >Which files do I edit to get access to my floppy disk and CD RoM?  (or
words to that effect)
> >>>>>Vern, your mailer is sending your text as attachments and  that
format killed one of my replies<<<<
>
> Vern, I don't understand.  Your floppy and CDROM should be
> immediately accessible without editing any files, unless you did
> an expert install with PARANOID security or you have some really
> strange hardware.
>
> Without more information, I have no idea how to help you.
>
> I do recomend to newer users that they start with LOW security
> level until they learn the dodges needed to work with the higher
> ones.  Just running linux is a deterrent to most script kiddies
> and mandrake doesn't have any 3-year old binaries full of holes
> for them to exploit.  The higher levels are fine, once you know
> how to work the system.
>
> But the only file to really "edit" to get the access would be
> /etc/fstab.  If you have to ask, I recommend you use
> DrakConf->Linuxconf->access local filesystems as your editor,
> because a mistake in directly editing /etc/fstab could leave you
> reaching for the rescue floppy and learning the chroot command.
>
> Civileme
>
> --
> Remember that if it is done on networks, it may occur on
> your host which is a network unto itself.
>

Reply via email to