Pages

Search

How to play audio CDs with linux? - Forums Linux

How to play audio CDs with linux? - Forums Linux

How to play audio CDs with linux?

Posted: 06 Jul 2006 07:04 PM PDT

Michael Mauch wrote: 

THANKS! I've done as you suggested and now CD audio works
perfectly for the non-root user. So, everything is now set all right.

Unruh wrote: 

Actually, by running 'gpasswd -a your_user cdrom' user was
added to group cdrom in /etc/gpasswd and /etc/group and this
achieved the objective. As Aragorn pointed out later, I do have
udev on my system, which would reset permissions at bootup.
The system now works fine, so I'm not going to experiment
further with permissions...

Aragorn wrote: 

I want to thank everyone who participated in this thread for all the
precious advice I got here. These newsgroups are truly a goldmine
of knowledge, and you guys are what makes this a reality.

So, to resume the steps which solved the sound problems
in my system:

1) Initially I would get an error message when attempting to run
KsCD to play an audio CD as the non-root user. By running KsCD
as root, which took care of the error message, it was established
that there was an access permission problem. But still there was
no sound.

2) Some suggested that a missing cable between cdrom drive
and sound card could be the problem. Others said it could
not be an issue here. I checked and there was no cable.
I added a cable connecting cdrom drive and cd audio connector
on the motherboard. Still no sound for su. But the music
could be played by plugging a set of earphones directly into
the cdrom drive.

3) Sound for root was made possible by unmuting and turning
up the cd volume control in alsamixer. (Very stupid, isn't it?
but I had overlooked it).

4) Finally, access permissions for non-root user.
'ls -lL /dev/cdrom' produced:

brw-rw---- 1 root cdrom 22, 0 Jul 7 08:25 /dev/cdrom

showing that non-root user had no access to /dev/cdrom.
Non-root user was given access permission and added
to group cdrom by running:

'gpasswd -a user_name cdrom'

After logging out of XWindows then logging in again, audio CD
playing now works perfectly also for the non-root user.

Again, thank you all!!!

Gianni

GRUB advanced configuration

Posted: 06 Jul 2006 11:55 AM PDT

In message <com>
"Nico Kadel-Garcia" <net> wrote:
 

The simple way, and the default in most cases, is to allow the
installer to set up GRUP with a choice of Linux versions plus a
Windows version. Choosing Windows then uses the contents of boot.ini
to present a Windows boot menu. This doesn't get quite what you want,
but it is simple, and pretty standard.

You might find that the installer has detected both windows versions
and put them into GRUB - in that case I would first try editing the
boot.ini in one of the Windows versions to get it to offer a choice,
and when that is successful, change the grub config file so it only
offers that version of Windows (and change the description maybe to
"Windows boot menu")



--
Alan Adams, from Northamptonshire
freeserve.co.uk
http://www.nckc.org.uk/

SATA drives insanely hot and lm-sensors not working

Posted: 06 Jul 2006 03:02 AM PDT

Jean-David Beyer wrote: 

Hmmm. They are not quite painful to touch, but I would say not far off.
IME all SATA drives run at a temp where I can handle them but they feel
noticeably not. I would not call it painful, but it would be painful if
it was only a little hotter.

I guess this is hotter than drives ought to be, but I don't see any
solution. Like I said, *all* my SATA drives run that hot, regardless of
which mfr, which machine they're in, how many fans etc.

CC

How to backup the files printing from graphics window?

Posted: 06 Jul 2006 02:24 AM PDT

The Natural Philosopher <a@b.c> writes:
 
 
 

The unix print jobs go to a print controller which caches the files into a
directory while they are being printed. That directory is /var/spool/cups,
with files starting with c being control files. On my system, those control
files are not erased. This leaves you with the name of the files printed,
the person, the format, the time, etc. (It is a partly text partly binary
file).

Second serial ATA drive does not work

Posted: 04 Jul 2006 04:23 AM PDT

Yes, here everything is up to date. Both drives are listed.
Greetings, Volker

bootup problem

Posted: 04 Jul 2006 03:37 AM PDT

On Fri, 07 Jul 2006 15:23:54 +0000, dave frost wrote:
 

First, let me correct my mis-statement above:
Usually, the root filesystem is mounted readonly, until the kernel is
ready.
 

Apparently, /proc is an exception to the readonly rule. The mount
command for /proc is successful, I guess, because proc is a
pseudo-filesystem which indicates the state of the kernel. The state of
the kernel is dynamic. BTW, for the mount command to be successful, the
mount point /proc must exist. For example, this command fails on a
readonly filesystem:

mkdir /proc

But, this command is successful (if /proc already exists):

mount -n proc /proc -t proc
 
Note: comments inline.

Startup scripts are distribution dependant. The SYSV startup scripts
that are used by most distributions are complex. I don't envy your
task of reinventing all of the startup scripts. Probably, the starting
point is a thorough understanding of the jobs performed by the existing
scripts before attempting to change or replace them. Without proper
startup, your system may lack the functionality that you'd expect. One
way to visualize this is to boot using only the kernel and root
filesystem by performing a simple exercise. Try this: specify the
kernel's init process as the bash shell. (Note: init=/bin/bash can be
specified as a kernel argurment.) Once booted in that environment you'll
be able to see what a minimal system looks like. This shows what the
kernel looks like without runlevels which are managed by the standard
"init" in combination with the startup scripts. You'll see a lot is missing.

More Info
There are two "schools" of startup scripts: SYSV and BSD-style. For me, it
is easier to understand and decipher the BSD-style scripts provided by the
Slackware distribution. IME, before changing the SYSV startup scripts,
you'll need to get a "secret decoder ring"- they're too complex. So,
before jumping right in and rewriting the scripts yourself, study both
styles. Perhaps, the other "school" will be more to your liking. In
any case, the concept of an "init" process and "runlevels" are fundamental
to a unix-like OS. If you stray too far, you might end up with something
else.

--
Douglas Mayne