Mailinglist Archive: opensuse (4570 mails)
| < Previous | Next > |
Re: [SLE] manipulating the system speaker
- From: "Carlos E. R." <robin1.listas@xxxxxxxxxx>
- Date: Sat, 5 Nov 2005 15:41:14 +0000 (UTC)
- Message-id: <Pine.LNX.4.61.0511051635080.9742@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Wednesday 2005-11-02 at 19:31 -0800, Carl William Spitzer IV wrote:
> bash: /dev/console: Permission denied
> You have new mail in /var/spool/mail/cwsiv
>
> Seems to give me an error plus an unrelated message.
I already said how to solve that. Read again:
> > Ah, it is documented:
> >
> > What this means is that root can always make beep work (to the best
> > of my knowledge!), and that any local user can make beep work, BUT a
> > non-root remote user cannot use beep in it's natural state. What's
> > worse, an xterm, or other x-session counts, as far as the kernel is
> > concerned, as 'remote', so beep won't work from a non-priviledged
> > xterm either. I had originally chalked this up to a bug, but
> > there's actually nothing I can do about it, and it really is a Good
> > Thing that the kernel does things this way. There is also a
> > solution.
> >
> > (he recommends making it suid)
> plus an unrelated message.
> I had downloaded email ten minutes before and hung up the phone line.
It is not exactly unrelated. Every time you time you press "enter" on a
terminal, it checks to see if you have new _system_ mail. Remember that
cron and other tasks can send you email.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDbNIztTMYHG2NR9URAg4PAJ0WS6/PWonPD8rJ8lHH/NwqrQLgWQCdHXLW
sirZ8bUcAleMmKhlcKW9sos=
=r4Km
-----END PGP SIGNATURE-----
Hash: SHA1
The Wednesday 2005-11-02 at 19:31 -0800, Carl William Spitzer IV wrote:
> bash: /dev/console: Permission denied
> You have new mail in /var/spool/mail/cwsiv
>
> Seems to give me an error plus an unrelated message.
I already said how to solve that. Read again:
> > Ah, it is documented:
> >
> > What this means is that root can always make beep work (to the best
> > of my knowledge!), and that any local user can make beep work, BUT a
> > non-root remote user cannot use beep in it's natural state. What's
> > worse, an xterm, or other x-session counts, as far as the kernel is
> > concerned, as 'remote', so beep won't work from a non-priviledged
> > xterm either. I had originally chalked this up to a bug, but
> > there's actually nothing I can do about it, and it really is a Good
> > Thing that the kernel does things this way. There is also a
> > solution.
> >
> > (he recommends making it suid)
> plus an unrelated message.
> I had downloaded email ten minutes before and hung up the phone line.
It is not exactly unrelated. Every time you time you press "enter" on a
terminal, it checks to see if you have new _system_ mail. Remember that
cron and other tasks can send you email.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDbNIztTMYHG2NR9URAg4PAJ0WS6/PWonPD8rJ8lHH/NwqrQLgWQCdHXLW
sirZ8bUcAleMmKhlcKW9sos=
=r4Km
-----END PGP SIGNATURE-----
| < Previous | Next > |