On Sun, Jun 8, 2014 at 4:21 AM, Otto Moerbeek <o...@drijf.net> wrote:
> On Sun, Jun 08, 2014 at 02:59:08AM -0430, Andres Perera wrote:
>
>> On Sun, Jun 8, 2014 at 2:24 AM, Janne Johansson <icepic...@gmail.com> wrote:
>> > I don't think there is a word for "chroot back".
>>
>> I don't think you read, understood, and executed the sample.
>>
>> After chroot("/"), or chroot(FOO), you can't mknod(2), therefore the
>> description is wrong.
>
> What part is wrong?
>
> "alternate" directory might happen to be / itself. While that's silly
> to do it's still an alternate to an unchrooted /.
>
> -Otto
>
AS a victim, the only documentation improve would to point this into
the mknod(8) man page,
the alternate root explanation was ok, even if <in a chrooted
environnement mknod return einval> would thwart
the sillly(?) chroot / case.
Creation of /dev/wd* or /dev/sd* could defeat the chroot, but creating
/dev/stdin ...
does that mean vnconfig is also not possible ?
--
---------------------------------------------------------------------------------------------------------------------
() ascii ribbon campaign - against html e-mail
/\
