Joey Hess wrote:
Mike McCarty wrote:
That is naive, is it not? The apps themselves have to be SELinux-
aware. So, one can remove the policy packages, but not SELinux.
-rw-r--r-- 1 root root 82K Jul 10 14:11 /lib/libselinux.so.1
If you're worried by this amount of space use, you probably have
Manoj Srivastava wrote:
That is not the case. All core libraries and packages have
already been patched and are functional in Etch. You did not even
notice it, because they are optional.
libselinux and libsepol are required and are not optional.
I bet that selinux is of no use for
Kevin Mark wrote:
The extent to which SELinux 'infests' Debian is a minor one. For proper
SELinux support you only have to alter a handful of basic packages and
the kernel, so that's like .001% of its packages.
but it runs deep. those handful are required packages.
--
To UNSUBSCRIBE, email t
I have songs in the apple lossless format. Rhythmbox can play them
back, but it often generates unpleasant scratching noise at the end
of a song.
I'd like to know if this is a known problem.
Thanks
T.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
nicolas wrote:
> i have install kernel 2.6.22 on debian etch, every thing works fine
> except when i shutdown de computer it shows me an error on the sata,
> it say i have a problem with my shutdown utility, and shows me a web
> site, but in the web site it says nothing. any one knows what to
>
Paul Scott wrote:
> $ stat /dev/ptmx
> [...snip...]
ptmx looks fine to me.
> mountpoint says /dev/pts is not a mount point
You need to mount devpts filesystem at /dev/pts.
pts(4) manpage says:
;; The Linux support for the above (known as Unix98 pty naming) is
;; done using the devpts filesyst
Paul Scott wrote:
>> looks different from the previous pty error. Have you fixed that?
>
> I don't know enough to know why it should have changed with all
> stock updates or enough to fix it at this point.
You reported that legacy pty support is turned off in the new kernel.
That is one change f
Paul Scott wrote:
Here's the end of the strace. It doesn't tell me anything we don't
already know. Maybe someone else will see more:
So what do you already know? For instance, this
[...]
write(2, "xterm Xt error: Can\'t open displ"...,
[...]
looks different from the previous pty error. H
Do you get a bell in a text console? IIRC, there is no longer a beep
module in the kernel.
I do. The module is pcspkr.ko.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Frank McCormick wrote:
>>> Well, I always store there all the sources related with my kernel,
>>> modules, etc... I haven't get any problem... BTW, remember doing
>>> the symlink to /usr/src/linux from your kernel-source.
>>
>> Well then why the warning from the Kernel developers? And what's
>> t
Jose Luis Rivas Contreras wrote:
>
> [EMAIL PROTECTED]:~$ eclipse
> searching for compatible vm...
> testing /usr/lib/jvm/java-gcj...found
> GC Warning: Repeated allocation of very large block (appr. size
262144000):
> May lead to memory leak and poor performance.
>
> [EMAIL
Anton Piatek wrote:
Does anyone have any advice on what to try to get this card to do
[EMAIL PROTECTED] ?
Andrew summarized what he's done to make the driver honour his
modeline in another message. Check it out if you haven't seen it:
http://lists.debian.org/debian-user/2007/08/msg00414.htm
Jonathan Kaye wrote:
Yes, Takehiko. I removed all the font paths from xorg.conf and now
my Xorg.0.log looks exactly like yours and the fonts seem ok so
far. You were perfectly correct. Thanks I learned something.
I merely observed that [a] I never touched FontPath and my xorg.conf
doesn't have
Zach wrote:
> Someone said the new version of the X.Org xserver no longer puts the
> Font lines in the xorg.conf file. I wonder where it puts them? I just
> remember one of the packages that it upgraded was xserver-xorg yet it
> didn't show anything on stdout indicating it was changing font
> dir
Andrei Popescu wrote:
# ~/.bash_profile: executed by bash(1) for login shells.
Set gnome-terminal to use a login shell.
Doh! Thanks.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
# Sorry, I sent a mail directly to you.
Andrei Popescu wrote:
> Instead of a ~/script dir I use a ~/bin dir and didn't need to change
> anything because ~/.bash_profile already contains:
>
> # set PATH so it includes user's private bin if it exists
> if [ -d ~/bin ] ; then
> PATH=~/bin:"${PA
I pulled the latest xf86-video-intel source from freedesktop.org,
and it magically cured the symptom.
My Xorg.0.log still shows the same error entries as before:
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
So, at least they are not the culprit. Now that the pain is gone,
Andrew J. Barr wrote:
> The file /var/log/Xorg.0.log would help with diagnostics.
only if I know how to interpret it...
There are in total 10 entries marked 'EE', all identical:
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
Is this normal? ... OK, silly question. Errors
Andrew Sackville-West wrote:
>> Since I updated xserver-xorg-video-intel, my LCD started to complain
>> that it is in a non-preset mode, that is, the monitor displayed a
>> message "Nonpreset Mode" for 5 seconds when X started.
>
> does the monitor then recover?
Yes. Except for the message, the
[ package: xserver-xorg-video-intel version 2:2.1.0-2 ]
Since I updated xserver-xorg-video-intel, my LCD started to complain
that it is in a non-preset mode, that is, the monitor displayed a
message "Nonpreset Mode" for 5 seconds when X started.
The resolution is set to the native 1280x1024. How
20 matches
Mail list logo
