Re: GLSAs: Put the name of the affected packg in front of the title?!

Re: GLSAs: Put the name of the affected packg in front of the title?!

On Tue, Jun 01, 2004 at 04:51:31PM +0200 or thereabouts, Jean-Fran?ois Maeyhieux wrote:
>  I'm agree too since i use the RDF format in evolution mail client on my
> start page:
> 
>      I think the name should take in consideration the name of the
> package and until wich version the security alert 
> is valid as:
> 
> GLSA 200405-24 (high) media-video/mplayer (<0.92.4)

We have already started placing the package name in the title.  At this
point, we have no plans to add additional information.  At some point, you
have to draw the line between trying to stuff all possible information into
the subject and actually reading the advisory itself.  We have chosen to
draw the line where it stands currently.

--kurt

[Fwd: Re: [gentoo-hardened] grsecurity in trouble]

-----Forwarded Message-----
From: Ned Ludd <solar <at> gentoo.org>
To: Aiko Barz <aiko <at> chroot.de>
Cc: gentoo-hardened <at> lists.gentoo.org, grsecurity <at> grsecurity.net
Subject: Re: [gentoo-hardened] grsecurity in trouble
Date: 01 Jun 2004 13:29:24 -0400

On Tue, 2004-06-01 at 11:46, Aiko Barz wrote:
> Read http://www.grsecurity.org/

You can show your support by sending the project donations. He is a 
student and a sponsor that had previously made arraignments to help him
out was unable to fulfill a previous commitment. This now forces him to
go out and get a job. Going to school fulltime and working a job will
leave him little to no to develop grsecurity any farther. While we can
try to limp along and maintain the code for a while. We "won't" be able
to deal with the complexities of the rbac system without somebody like
spender driving. This means that the acl/rbac system will die just as it
was so nearing completion. So feel free to show your love and support
out of the pockets of your IT budgets so the grsecurity project can
remain alive and active. Nobody should have to barrow money just to eat.

> 
> Bis denne,
>         Aiko
--

-- 
Ned Ludd <solar <at> gentoo.org>
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer

broken pstree

Hello,
For some time, pstree gives this error:

/bin/pstree: line 3: syntax error near unexpected token `case'
/bin/pstree: line 3: `  case SNDRV_SEQ_EVENT_SAMPLE_POSITION:'

I don't know what this is about. I presume the hard drive failed...I got some 
kernel oopses, but then again...bad things may be happening.

Did anyone have this kind of problem?

btw, pstree.X11 gives me this error:

/bin/pstree.x11: line 1: /b: Permission denied
/bin/pstree.x11: line 2: BACK: command not found
/bin/pstree.x11: line 3: syntax error near unexpected token `('
/bin/pstree.x11: line 3: ` *   Copyright (c) 1998 by Frank van de Pol 
<fvdpol <at> coil.demon.nl>'

And could please anyone tell me what ebuild is pstree in, because I couldn't 
find anywhere.

Thanks in advance,
Dadi

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

Hello Dadi,

i have never encoutered such a problem; however pstree is in 
sys-apps/psmisc ebuild (qpkg -f `which pstree `).
qpkg is part of the gentoolkit package (app-portage/gentoolkit)
that you should consider to install on all of your gentoo installations.

cheers, sequel

On Tue, 2004-06-01 at 17:02, Dadi wrote:
> Hello,
> For some time, pstree gives this error:
> 
> /bin/pstree: line 3: syntax error near unexpected token `case'
> /bin/pstree: line 3: `  case SNDRV_SEQ_EVENT_SAMPLE_POSITION:'
> 
> I don't know what this is about. I presume the hard drive failed...I got some 
> kernel oopses, but then again...bad things may be happening.
> 
> Did anyone have this kind of problem?
> 
> btw, pstree.X11 gives me this error:
> 
> /bin/pstree.x11: line 1: /b: Permission denied
> /bin/pstree.x11: line 2: BACK: command not found
> /bin/pstree.x11: line 3: syntax error near unexpected token `('
> /bin/pstree.x11: line 3: ` *   Copyright (c) 1998 by Frank van de Pol 
> <fvdpol <at> coil.demon.nl>'
> 
> And could please anyone tell me what ebuild is pstree in, because I couldn't 
> find anywhere.
> 
> Thanks in advance,
> Dadi
> 
> --
> gentoo-security <at> gentoo.org mailing list
> 

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

Am Dienstag, 1. Juni 2004 23:02 schrieb Dadi:
> /bin/pstree: line 3: syntax error near unexpected token `case'
> /bin/pstree: line 3: `  case SNDRV_SEQ_EVENT_SAMPLE_POSITION:'

pstree is normally a Linux ELF-executable. The above out means that the file 
pstree contains part of a C source (which, I guess you understand, shouldn't 
be there). This source is interpreted by the shell (bash), which complains 
about a syntax error. The error about pstree.x11 is pretty similar.

I guess your harddrive is seriously broken, or something else happened to your 
filesystem which borked this (like an error in the kernel filesystem code, 
are you running Reiser4?). Check your root filesystem with the appropriate 
fsck.*, and if that doesn't help, reinstall pstree by reinstalling psmisc 
like someone else told you to.

You'd better also check for other filesystem corruptions, where other programs 
got replaced by invalid replacements.

HTH!

Heiko.

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

I got some kernel oopses when I was playing with ipw2100...this was some time 
ago. However, I have noticed the pstree problem but neglected it because 
there were always better things to do.
I think I am using reiser4 because I use kernel 2.6.5 and the ~x86 
reisertools.

I have checked it, but nothing seems wrong.

Regarding reiser, some friends of mine were telling me that it's notorious for 
breaking files when unexpected things happen. Is this true? I mean I had my 
share of trouble with reiser also on other harddisks but always lived with 
the thought that it was a hardware problem more then a fs problem. Now it's 
all coming together and starting to make sense.

If this is so...what is the most reliable jurnalised fs? ....I also saw some 
tests and the fastest would be reiser, and jfs and xfs following....with ext3 
coming on last.

Also, is there anyway I can convert the fs...with my data sitting on it?

Thanks to the DeadManMoving also...I have reinstalled psmisc and it works.

...come to think about it there were also some time ago some broken libs...
resierfs is starting to give me the creeps, since I lost to it a few good Gigs 
of music on another drive.

Thanks again,
Dadi

On Wednesday 02 June 2004 01:25, Heiko Wundram wrote:
> Am Dienstag, 1. Juni 2004 23:02 schrieb Dadi:
> > /bin/pstree: line 3: syntax error near unexpected token `case'
> > /bin/pstree: line 3: `  case SNDRV_SEQ_EVENT_SAMPLE_POSITION:'
>
> pstree is normally a Linux ELF-executable. The above out means that the
> file pstree contains part of a C source (which, I guess you understand,
> shouldn't be there). This source is interpreted by the shell (bash), which
> complains about a syntax error. The error about pstree.x11 is pretty
> similar.
>
> I guess your harddrive is seriously broken, or something else happened to
> your filesystem which borked this (like an error in the kernel filesystem
> code, are you running Reiser4?). Check your root filesystem with the
> appropriate fsck.*, and if that doesn't help, reinstall pstree by
> reinstalling psmisc like someone else told you to.
>
> You'd better also check for other filesystem corruptions, where other
> programs got replaced by invalid replacements.
>
> HTH!
>
> Heiko.
>
> --
> gentoo-security <at> gentoo.org mailing list

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

Dadi wrote:
> Regarding reiser, some friends of mine were telling me that it's notorious for 
> breaking files when unexpected things happen. Is this true? I mean I had my 
> share of trouble with reiser also on other harddisks but always lived with 
> the thought that it was a hardware problem more then a fs problem. Now it's 
> all coming together and starting to make sense.

A lot of people like to blame ReiserFS for their problems. It seems that 
it did have reliability problems in the early days and since it is much 
younger than EXT2, these problems may be fresher in people's minds.

I have been using ReiserFS as my primary filesystem on all my machines 
for several years now. I have had some breakage, but most of it was 
connected to hardware problems and I was always able to fix the 
filesystem using the tools. In total, I've probably lost fewer than ten 
files. My experience doesn't suggest that ReiserFS is significantly less 
reliable than any other, though I haven't done careful tests.

I also ask what is resonable to expect from a filesystem in the face of 
hardware errors. As far as I know, all Linux filesystem drivers expect 
reliable media. Several of them do journaling, which may protect 
filesystem structure more than non-journaling ones, but doesn't 
necessarily protect the state of data since applications don't use 
transactions. To protect against hardware problems, you probably have to 
add redundancy, like with RAID-5. Also, remember that nothing can 
substitute for a good backup policy.

Jonathan Rogers

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

On Wed, 2 Jun 2004 09:57:13 +0300
Dadi <thewalrus <at> dadi.kicks-ass.org> wrote:

<...> 
> Regarding reiser, some friends of mine were telling me that it's notorious for 
> breaking files when unexpected things happen. Is this true? I mean I had my 
> share of trouble with reiser also on other harddisks but always lived with 
> the thought that it was a hardware problem more then a fs problem. Now it's 
> all coming together and starting to make sense.
> 

Well the current stable reiserfs (that is, not v.4) is pretty safe from this kind of trouble in my
experience. One of my servers gets a lot of unexpected reboots because it's located at a really bad spot (on
the floor under a desk, power-button easily accessible). It's been running reiserfs for well over a year
and lost files have not happened to me (that I know) and the box is working without any trouble.

What happens to some people is that reierfs sometimes saves up on stuff to write to disk, and when power
disappears there is no time for the buffer to get written to the disk. That would account for some of the lost
files I guess. I run the command 'sync' when I wans to make sure stuff ends up on the disk, like after etc-update.

Regards,
Daniel

--
gentoo-security <at> gentoo.org mailing list

Re: broken pstree

On Wed, 2 Jun 2004 09:57:13 +0300
Dadi <thewalrus <at> dadi.kicks-ass.org> wrote:

> Regarding reiser, some friends of mine were telling me that it's
> notorious for breaking files when unexpected things happen. Is this
> true? I mean I had my share of trouble with reiser also on other
> harddisks but always lived with the thought that it was a hardware
> problem more then a fs problem. Now it's all coming together and
> starting to make sense.
> 

There seems to be a common misconception regarding journaling filesystems.
Normally, they only guarantee filesystem inegrity, *not* data integrity as
many seem to believe.
So, if your machine crashes, unflushed data is lost and the affected
files are corrupted. The filesystem however will be correct after log
replay, so all files which were closed or flushed to disk at crash time
are unaffected.
This is true for reiserfs, jfs and xfs. ext3 is slightly better when using
the data=ordered option and it can even guarantee data integrity through
the data=journal option. However this severly decreases write performance.

It is important to note, that all journaling filesystems rely on data
ordering. If you are using your hard-disk's write cache, things can break
badly. This is probably the main reason for reiserfs' bad reputation.

Regards

--
gentoo-security <at> gentoo.org mailing list