From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] I (user) can write to / ... but why?
Date: Tue, 16 Aug 2005 21:26:35 +1200 [thread overview]
Message-ID: <1124184395.2213.24.camel@sf.rout.dyndns.org> (raw)
In-Reply-To: <43018F27.6020702@gmail.com>
On Tue, 2005-08-16 at 09:00 +0200, Ralph Slooten wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dirk Heinrichs wrote:
> > No. It isn't mounted by you. You own it (at least this directory). Use
> >
> > find / -xdev -uid 1000
>
> Ahh, so what you are saying is that I own the "/" directory. Hmm, how
> could that have happened, and on 2 separate machines? I never thought of
> "/" being a directory,
this is unix, everything is a file, so / is a file, it just happens to
be the filetype that is a directory.
Sorry I have no idea how you came to own it though.
> more like the base there initial directories were
> placed on. Anyway, when I get home today from work I'll check and change
> the permissions. Thanks for the heads-up.
>
>
--
Nick Rout <nick@rout.co.nz>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-16 9:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 18:27 [gentoo-user] I (user) can write to / ... but why? Ralph Slooten
2005-08-15 19:12 ` Daniel da Veiga
2005-08-15 20:21 ` Christoph Gysin
2005-08-15 20:45 ` Neil Bothwick
2005-08-16 1:07 ` Nick Rout
2005-08-16 5:21 ` Ralph Slooten
2005-08-16 5:17 ` Ralph Slooten
2005-08-16 5:41 ` Dirk Heinrichs
2005-08-16 7:00 ` Ralph Slooten
2005-08-16 7:17 ` Dirk Heinrichs
2005-08-16 10:21 ` Michael Kintzios
2005-08-16 9:26 ` Nick Rout [this message]
2005-08-16 9:47 ` Frank Schafer
2005-08-16 13:33 ` Ralph Slooten
2005-08-16 7:14 ` Christoph Gysin
2005-08-16 7:42 ` Neil Bothwick
2005-08-16 16:09 ` [gentoo-user] I (user) can write to / ... but why? (solved) Ralph Slooten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1124184395.2213.24.camel@sf.rout.dyndns.org \
--to=nick@rout.co.nz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox