Paul de Weerd wrote:
On Mon, Dec 15, 2008 at 06:17:53AM -0600, Ed Ahlsen-Girard wrote:
Well, it's empty until you start using it (by building (parts of) the
tree). That's why the "newfs trick" is a safe way to start from
scratch.
Mine is 2G, but the size depends on a lot of things. What arc
Josh Grosse wrote:
On Mon, 15 Dec 2008 14:24:18 +, Dave Wilson wrote
...I'm trying
to create a 2G MFS for /usr/obj, but if I go much above 200 with
mount_mfs I get an error...
For /usr/obj on i386, my userland build script creates two MFS mounts, builds
sparse files on them, assigns
On Mon, 15 Dec 2008 14:24:18 +, Dave Wilson wrote
> ...I'm trying
> to create a 2G MFS for /usr/obj, but if I go much above 200 with
> mount_mfs I get an error...
For /usr/obj on i386, my userland build script creates two MFS mounts, builds
sparse files on them, assigns the sparse files
Hi!
On Mon, Dec 15, 2008 at 02:24:18PM +, Dave Wilson wrote:
>[...]
>On that note, does anyone know how to poke the restrictions set in
>login.conf on a temporary basis? The existence of datasize-cur and
>datasize-max suggest I should be able to do this, but I can't find the
>relevant command
On Mon, Dec 15, 2008 at 02:24:18PM +, Dave Wilson wrote:
| Paul de Weerd wrote:
| > On Mon, Dec 15, 2008 at 06:17:53AM -0600, Ed Ahlsen-Girard wrote:
| >> 2. In any case, how big does that slice need to be?
| >
| > Mine is 2G, but the size depends on a lot of things. What arch are you
| > bu
Paul de Weerd wrote:
> On Mon, Dec 15, 2008 at 06:17:53AM -0600, Ed Ahlsen-Girard wrote:
>> 2. In any case, how big does that slice need to be?
>
> Mine is 2G, but the size depends on a lot of things. What arch are you
> building for ? Do you only build kernels ? Full make build ? Making
> Xorg
On Mon, Dec 15, 2008 at 06:17:53AM -0600, Ed Ahlsen-Girard wrote:
> I expected that eventually I would be tracking stable and/or current,
> and created a slice for /usr/obj to use the "umount /usr/obj&newfs
> /dev/wd[n][a]" trick.
>
> 1. Is /usr/obj normally EMPTY? It is on all three of my OB
I expected that eventually I would be tracking stable and/or current,
and created a slice for /usr/obj to use the "umount /usr/obj&newfs
/dev/wd[n][a]" trick.
1. Is /usr/obj normally EMPTY? It is on all three of my OBSD boxes.
2. In any case, how big does that slice need to be?
Ed Ahlsen-G
8 matches
Mail list logo
