zens wrote:

<MY VALUE="$0.02"> just a quick observation, I dont know anything about the yast admin tool suse being one of the few linux distributions I havent run yet (*cough*still waiting for my copy of 5.3 to arrive*cough*) , but one thing I have noticed about admin tools in general is that they take away from the learning expierence, and make people too dependant on them to

take the time to learn how to do things the "hard way"... regarding this particular situation, I dont know what yast is supposed to do with the cdrom, so I wont even attempt to determine the root of the problem, but can it really be more difficult than typing "mount /dev/cdrom" (assuming you have the corresponding entry in your /etc/fstab, mabye since I dont know what functionality yast plays with the cdrom I am stepping out of bounds, but it really couldnt be *that* much of a timesaver could it? </MY> I can install with the method you have suggested but that isn't the

I agree. point. The point is that something is wrong with the admin tool that suse is known for... I simply would like to know why it is giving me problems, and *learn* how to fix it. I really couldn't agree with you more on these automagic tools taking away from the learning experience...I don't want windoze. I've only had my own computer for about a year and a half and have only switched to linux in July (only linux, no windoze:) I must say that I have learned more in the past month or so than ever before, all thanks to linux. I'm sorry that I can't be the guru you seem to be. regards Harry

zens

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

You're correct that using special setup tools take away much of the learning experience by insulating the user from the system configuration, but you don't have to use them. You can turn off SuSEconfig so that it doesn't run. Also, SuSEconfig alerts me when I manually change a file that it normally sets up and leaves it alone. Right now the only activities I use yast for are installation of multiple rpms, setup of apsfilter (which doesn't need yast to work anyway), and setting up X (ditto comment). Other than that I muck around in the files, because that's how the HOWTOS are written. As for the post by Rihmez, I never even knew yast could set up one's cd-rom drive. Is this new in 5.3? All one has to do is read a the mount manage, check out their existing /etc/fstab, and ask a few questions here and you're in business! Mark --- zens wrote:

<MY VALUE="$0.02"> just a quick observation, I dont know anything about the yast admin tool suse being one of the few linux distributions I havent run yet (*cough*still waiting for my copy of 5.3 to arrive*cough*) , but one thing I have noticed about admin tools in general is that they take away from the learning expierence, and make people too dependant on them to take the time to learn how to do things the "hard way"... regarding this particular situation, I dont know what yast is supposed to do with the cdrom, so I wont even attempt to determine the root of the problem, but can it really be more difficult than typing "mount /dev/cdrom" (assuming you have the corresponding entry in your /etc/fstab, mabye since I dont know what functionality yast plays with the cdrom I am stepping out of bounds, but it really couldnt be *that* much of a timesaver could it? </MY>

- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

Hubert Mantel wrote:
> 
> Hi,
> 
> On Fri, Sep 04, Rihmez wrote:
> 
> > I'm having problems with getting my cd-rom to work with yast. I recently
> > changed the installation media to a directory and when I tried changing
> > back to cd-rom it gave me a list of cd-rom drives that i don't have. The
> 
> Well, what kind of CD-ROM DO you have? This info is needed for people to
> be able to help you.
> 
> There are four major groups of CD-ROM drives:
> 
> 1. ATAPI (EIDE) ones. They are connected to the EIDE controller and This worked! Thanks for your help:) 
harry

named
>    /dev/hda to /dev/hdd
> 2. SCSI drives. They are attached to a SCSI adapter and named /dev/scd0
>    or /dev/scd1 (some people prefer the names /dev/sr0 and /dev/sr1)
> 3. Parallel port drives. Starting with 5.3 they are named /dev/pcd0 to
>    /dev/pcd4 (need protocol modules dependant of the manufacturer)
> 4. Proprietary drives (with own interface card). They are called /dev/mcd,
>    /dev/optcd, /dev/sbpcd and so on.
> 
> > closest thing is the creative cd-rom but that wouldn't mount it either.
> > I can still mount the drive outside of yast with mount -t iso9660
> > /dev/cdrom /cdrom. Anyone have a clue?
> 
> This means /dev/cdrom is pointing to the correct device. Just do a
> 
> ls -l /dev/cdrom
> 
> and look where it points to. That is your CD-ROM drive to use.
> 
> > Originally setup configured the drive for yast.
> >
> > TIA,
> > Harry
>                                                                   -o)
>     Hubert Mantel                                                 /\\
>                                                                  _\_v
> -
> To get out of this list, please send email to majordomo@suse.com with
> this text in its body: unsubscribe suse-linux-e
-
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e