:Matthew Dillon wrote:
:> So this patch is a hack. It returns special devices directly whenever
:> possible but must still synthesize temporary vnodes for them for
:> RENAME and DELETE operations. But short of rewriting a big chunk of
:> the device tracking infrastructure there i
Matthew Dillon wrote:
> So this patch is a hack. It returns special devices directly whenever
> possible but must still synthesize temporary vnodes for them for
> RENAME and DELETE operations. But short of rewriting a big chunk of
> the device tracking infrastructure there is no o
Cameron and I have been working through some of the more blatent bugs.
Here is an intermediate patch for -stable, for both unionfs and nullfs.
There are still plenty of bugs left but this patch should fix the
major issues with devices.
Basically what is going on is that speci
:>
:> It should be calling VOP_BMAP through the VP stored in the VM
:> object, which will be the underlying file, not the nullfs.
:
:Probably, but it's not doing that. The NULLFS implement VOP_BMAP
:as vop_eopnotsupp; it doesn't fall through. Even if it did fall
:through, the vfs_defaul
The Anarcat wrote:
> On Wed Nov 13, 2002 at 05:00:24PM -0800, Terry Lambert wrote:
> > The Anarcat wrote:
> > > On Tue Nov 12, 2002 at 11:11:54PM -0800, Terry Lambert wrote:
> > > > 1)Use devfs instead.
> > >
> > > On -stable?
> >
> > Yes.
>
> Wasn't -stable devfs retired some time ago?
No.
Matthew Dillon wrote:
> :VOP_GETVOBJECT is a different name, but the VOP was my suggestion,
> :to allow an upper layer to obtain a backing object, and to
> :collapse intermediate layers.
> :
> :The issue is that the NULLFS getpages falls through the the
> :vfs_default.c vop_stdgetpages(), which cal
Pawel Jakub Dawidek wrote:
> On Wed, Nov 13, 2002 at 03:28:22PM -0800, Terry Lambert wrote:
> +> Don't worry about it. It's only a problem for mmap'ed files
> +> which are also read/written. Sheesh.
>
> I have found one little bug in nullfs. I've send it some time ago
> to hackers@, but without
On Wed Nov 13, 2002 at 05:00:24PM -0800, Terry Lambert wrote:
> The Anarcat wrote:
> > On Tue Nov 12, 2002 at 11:11:54PM -0800, Terry Lambert wrote:
> > > 1)Use devfs instead.
> >
> > On -stable?
>
> Yes.
Wasn't -stable devfs retired some time ago?
A.
--
From the age of uniformity, from th
The Anarcat wrote:
> On Tue Nov 12, 2002 at 11:11:54PM -0800, Terry Lambert wrote:
> > Cameron Grant wrote:
> > > null mounts, in -stable at least, are broken for this purpose. on
> > > connection, sshd revoke()s some device- its pty, i assume, and when this
> > > hits the nullfs layer a null poin
:> I'm fairly sure the VM issues were fixed when VOP_GETVOBJECT was
:> added. A file accessed via a null mount will have the same VM object
:> as the file in the original filesystem. I'm not 100% sure about
:> that, I wasn't the one who did it, but I seem to recall it being
:>
On Wed, Nov 13, 2002 at 03:28:22PM -0800, Terry Lambert wrote:
+> Don't worry about it. It's only a problem for mmap'ed files
+> which are also read/written. Sheesh.
I have found one little bug in nullfs. I've send it some time ago
to hackers@, but without any respond.
Here it is, maybe someone
On Wed, Nov 13, 2002 at 12:27:35PM -0800, Hans Zaunere wrote:
+> [...] I'm also looking forward to the next "version" of jail
+> implementation!
You're talking about jailNG? If I understand everything correct there
will be no jailNG. TrustedBSD features will handle with jail-things.
I'm wrong?
--
Pawel Jakub Dawidek wrote:
> On Tue, Nov 12, 2002 at 07:08:47PM -0800, Hans Zaunere wrote:
> +> -- mount_null seems to be the answer, however the warning at the end of
> +> the man page is scary.
> +>
> +> Is there any combination of these (or anything I'm forgetting) that
> +> could help me here?
Matthew Dillon wrote:
> :> Try using null mounts. The warning is in there because making the
> :> null mount code work is a real hack and the authors aren't entirely
> :> sure that everything's gotten covered. That said, use of a null mount
> :> is certainly a lot safer if the stu
--- Terry Lambert <[EMAIL PROTECTED]> wrote:
> Hans Zaunere wrote:
> > I want to allow the users the ability to compile and use their own
> > instances of Apache and MySQL from within the jail. But instead of
> > duplicating the basic system libs and bins, I'd like to maintain a
> > single reposi
On Tue, 12 Nov 2002, Hans Zaunere wrote:
HZ> After much searching and contemplation, I've decided to ask the
HZ> question directly:
HZ>
HZ> I'm implementing a jail server, which will provide a very limited set
HZ> of resources (Apache/MySQL/PHP). Setup is going well, however I've run
HZ> into a l
On Tue Nov 12, 2002 at 11:11:54PM -0800, Terry Lambert wrote:
> Cameron Grant wrote:
> > null mounts, in -stable at least, are broken for this purpose. on
> > connection, sshd revoke()s some device- its pty, i assume, and when this
> > hits the nullfs layer a null pointer is dereferenced. if i ha
On Tue, Nov 12, 2002 at 07:08:47PM -0800, Hans Zaunere wrote:
+> -- mount_null seems to be the answer, however the warning at the end of
+> the man page is scary.
+>
+> Is there any combination of these (or anything I'm forgetting) that
+> could help me here? Is mount_null stable?
I'm using moun
:> Try using null mounts. The warning is in there because making the
:> null mount code work is a real hack and the authors aren't entirely
:> sure that everything's gotten covered. That said, use of a null mount
:> is certainly a lot safer if the stuff behind the mount is mostly
Cameron Grant wrote:
> null mounts, in -stable at least, are broken for this purpose. on
> connection, sshd revoke()s some device- its pty, i assume, and when this
> hits the nullfs layer a null pointer is dereferenced. if i had vfs-clue i'd
> have fixed it when i found the panic about two weeks
Matthew Dillon wrote:
> Try using null mounts. The warning is in there because making the
> null mount code work is a real hack and the authors aren't entirely
> sure that everything's gotten covered. That said, use of a null mount
> is certainly a lot safer if the stuff behind th
Hans Zaunere wrote:
> I want to allow the users the ability to compile and use their own
> instances of Apache and MySQL from within the jail. But instead of
> duplicating the basic system libs and bins, I'd like to maintain a
> single repository of this, which can then be read-only from within th
:> is certainly a lot safer if the stuff behind the mount is mostly
:> static.
:
:null mounts, in -stable at least, are broken for this purpose. on
:connection, sshd revoke()s some device- its pty, i assume, and when this
:hits the nullfs layer a null pointer is dereferenced. if i had vf
> Try using null mounts. The warning is in there because making the
> null mount code work is a real hack and the authors aren't entirely
> sure that everything's gotten covered. That said, use of a null mount
> is certainly a lot safer if the stuff behind the mount is mostly
>
Try using null mounts. The warning is in there because making the
null mount code work is a real hack and the authors aren't entirely
sure that everything's gotten covered. That said, use of a null mount
is certainly a lot safer if the stuff behind the mount is mostly
static.
On Wed, 2002-11-13 at 14:17, Hans Zaunere wrote:
> Two issues arise:
> 1) I'd like to be able to link an entire directory for convience and
> maintenance purposes.
Write a script :)
> 2) Cross partition links not possible.
>
> Number 2 is really the kicker, as far as I can tell. Is there some
> > I've had an account on a jail server which had /shared visible
> > within the jail, and symlinks to /bin, /usr/lib and such. I'm not
> > sure how this was actually implemented, and I'd be interested if
> > anyone has seen or heard of any solutions to this type of problem.
>
> You should be a
On Wed, 2002-11-13 at 13:38, Hans Zaunere wrote:
> -- Symlinks won't work because of the chroot.
> -- Mounts from within the jail aren't allowed, plus a single partition
> can't be mounted multiple times, AFAIK.
> -- I don't have NFS setup, and I would like to avoid it as much as
> possible.
> -- m
28 matches
Mail list logo
