Gerald Hanuer wrote:
> Hello misc@,
>
> Christian wrote:
>
> Well, the ports infrastructure for building those official binaries
> has support for putting pobj on MFS...
>
> WRKOBJDIR_MFS
> Alternate location for the port working directory. The intent
> is
> to us
> > Christian wrote:
> >
> > Well, the ports infrastructure for building those official binaries
> > has support for putting pobj on MFS...
> >
> > WRKOBJDIR_MFS
> > Alternate location for the port working directory. The intent
> > is
> > to use an MFS based filesy
> Hello misc@,
>
> Theo wrote:
>
> I still don't see the use case.
>
> wxallowed is only meant as a temporary[1] measure until all the
> applications are fixed.
>
> Instead, you are trying to use all the features everywhere.
>
> [1] Hopefully within my lifetime
>
>
> Have mfs in the tool kit
Hello misc@,
Christian wrote:
Well, the ports infrastructure for building those official binaries
has support for putting pobj on MFS...
WRKOBJDIR_MFS
Alternate location for the port working directory. The intent
is
to use an MFS based filesystem for small ports w
Hello misc@,
Theo wrote:
I still don't see the use case.
wxallowed is only meant as a temporary[1] measure until all the
applications are fixed.
Instead, you are trying to use all the features everywhere.
[1] Hopefully within my lifetime
Have mfs in the tool kit to take up the read/write sho
On 2016-05-30, Theo de Raadt wrote:
> Well, you are also going to find out you cannot set wxallowed
> on some other filesystems. It only works on real FFS and real
> NFS, and the purpose is for building & installation of official
> binaries.
>
> The goal is that admins won't create filesystems l
> >>85c260a91247e685.b none swap sw
> >>85c260a91247e685.a / ffs rw 1 1
> >>85c260a91247e685.k /home ffs rw,nodev,nosuid 1 2
> >>85c260a91247e685.d /tmp ffs rw,nodev,nosuid 1 2
> >>85c260a91247e685.f /usr ffs rw,nodev 1 2
> >>85c260a91247e685.g /usr/X11R6 ffs rw,nodev 1 2
> >>85c260a91247e68
Hello misc@,
>>85c260a91247e685.b none swap sw
>>85c260a91247e685.a / ffs rw 1 1
>>85c260a91247e685.k /home ffs rw,nodev,nosuid 1 2
>>85c260a91247e685.d /tmp ffs rw,nodev,nosuid 1 2
>>85c260a91247e685.f /usr ffs rw,nodev 1 2
>>85c260a91247e685.g /usr/X11R6 ffs rw,nodev 1 2
>>85c260a91247e68
> >Well, you are also going to find out you cannot set wxallowed
> >on some other filesystems. It only works on real FFS and real
> >NFS, and the purpose is for building & installation of official
> >binaries.
>
> >The goal is that admins won't create filesystems like you are
> >doing here.
>
>
Hello misc@,
>Well, you are also going to find out you cannot set wxallowed
>on some other filesystems. It only works on real FFS and real
>NFS, and the purpose is for building & installation of official
>binaries.
>The goal is that admins won't create filesystems like you are
>doing here.
>Why
Well, you are also going to find out you cannot set wxallowed
on some other filesystems. It only works on real FFS and real
NFS, and the purpose is for building & installation of official
binaries.
The goal is that admins won't create filesystems like you are
doing here.
Why are you doing this?
Hello misc@,
Mount_mfs does not honor wxallowed.
Will mfs follow ffs regarding wxallowed,
if so is this functionality in the works?
Thanks in advanced,
Gerald Hanuer
/bin/cat /etc/fstab
85c260a91247e685.b none swap sw
85c260a91247e685.a / ffs rw 1 1
85c260a91247e685.k /home ffs rw,
12 matches
Mail list logo
