Incoming from Brett Furlong:
> Soz, to pester.
> Got spam though debian security list again...
>
> Was from "Jalousies M. Pseudonyms" <[EMAIL PROTECTED]>
>
> Not winging @ Deb Mail Crew, You guys rock.
> But yeh, is there a way, we can have a human filter all the eMails before they
> are allowe
Soz, to pester.
Got spam though debian security list again...
Was from "Jalousies M. Pseudonyms" <[EMAIL PROTECTED]>
Not winging @ Deb Mail Crew, You guys rock.
But yeh, is there a way, we can have a human filter all the eMails before they
are allowed to be sent to all of us?
Like, It's not th
On Sat, Mar 27, 2004 at 11:32:09PM +, Brian Brazil wrote:
I assume you meant chown, not chmod but what I said holds.
mkdir /LFS
chroot /LFS #Pretend there's a shell etc.
chown -R 0.0 * .* #There were some dotfiles
This resulted in my entire directory structure being owned by root -
whic
On Sat, Mar 27, 2004 at 08:25:52PM +0100, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > Of course Linux chroot is broken. Found that out after doing chown -R 0.0
> > .. in a chroot while I was compiling LFS. (Was running SuSE 7.0 at the
> > time - 2.4.19).
>
> Well linux c
On Sat, Mar 27, 2004 at 11:32:09PM +, Brian Brazil wrote:
I assume you meant chown, not chmod but what I said holds.
mkdir /LFS
chroot /LFS #Pretend there's a shell etc.
chown -R 0.0 * .* #There were some dotfiles
This resulted in my entire directory structure being owned by root -
which b
On Sat, Mar 27, 2004 at 08:25:52PM +0100, Bernd Eckenfels wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > Of course Linux chroot is broken. Found that out after doing chown -R 0.0
> > .. in a chroot while I was compiling LFS. (Was running SuSE 7.0 at the
> > time - 2.4.19).
>
> Well linux c
How're you doing?Perfection of means and confusion of goals seem -- in my opinion -- to characterize our age.
Debian, looking for a source to shop for medicatiEOon?Exceptional ViagErza and CialoPis.
Quick weight (bestrowed mojarra) loss and antidepressant medicatiRnon!Best cost on Valiudvm and X
In article <[EMAIL PROTECTED]> you wrote:
> Of course Linux chroot is broken. Found that out after doing chown -R 0.0
> .. in a chroot while I was compiling LFS. (Was running SuSE 7.0 at the
> time - 2.4.19).
Well linux chroot has a limited set of capabilties. Especially it does not
protect you fr
How're you doing?Perfection of means and confusion of goals seem -- in my opinion -- to characterize our age.
Debian, looking for a source to shop for medicatiEOon?Exceptional ViagErza and CialoPis.
Quick weight (bestrowed mojarra) loss and antidepressant medicatiRnon!Best cost on Valiudvm and X
In article <[EMAIL PROTECTED]> you wrote:
> Of course Linux chroot is broken. Found that out after doing chown -R 0.0
> .. in a chroot while I was compiling LFS. (Was running SuSE 7.0 at the
> time - 2.4.19).
Well linux chroot has a limited set of capabilties. Especially it does not
protect you fr
On Fri, Mar 26, 2004 at 07:53:49PM +0200, Costas Magkos wrote:
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
/proc/pid/root
Of course Linux chroot is broken. Found that out aft
On Fri, Mar 26, 2004 at 07:53:49PM +0200, Costas Magkos wrote:
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
/proc/pid/root
Of course Linux chroot is broken. Found that out aft
On Fri, 2004-03-26 at 18:53, Costas Magkos wrote:
[...]
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
use lsof
# lsof -p [pid number of bind process]
check:
- if the loaded l
On Fri, 2004-03-26 at 18:53, Costas Magkos wrote:
[...]
> Is there a way to test whether a chroot works? Does anyone know if the
> above syslog option is really needed? According to the man page of
> syslog it is needed.
use lsof
# lsof -p [pid number of bind process]
check:
- if the loaded l
14 matches
Mail list logo
