Peter Steele pste...@maxiscale.com wrote:
In my read-only CD-ROM boot case, /var is created as a MFS device
automatically and populated, but a basic directory layout only is
used. Nothing from the CD-ROM /var is copied into the MFS /var
that is created.
I cannot figure out how BSD can do
You might be able to reduce the iso size some by making a tarball of /var
(using tar -y or tar -z) instead of keeping /var2 as a tree.
Granted you would then need to have tar(1) in the iso, which may cancel out
much of the savings if you would not otherwise have needed it.
Actually, /var is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2010 06:28:40, Peter Steele wrote:
I found something else that's missing--/var/db/pkg is empty. It looks
like what the auto-var process does is a construct basic directory
structure but no data. Is there a solution to this? Can I get /var
On Wed, 7 Apr 2010 00:28:40 -0500 Peter Steele wrote:
I found something else that's missing--/var/db/pkg is empty. It looks
like what the auto-var process does is a construct basic directory
structure but no data. Is there a solution to this? Can I get /var to
be populated with the full
Can you write a few shell scripts? You'ld need to create a tarball of the
/var contents you need on the box, and explode it onto
/var at boot time -- if you're using auto-var on MFS all the time, you'll
need to set that up to happen on every reboot.
Obviously I can do that. What I was really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/04/2010 12:09:56, Peter Steele wrote:
Can you write a few shell scripts? You'ld need to create a tarball
of the /var contents you need on the box, and explode it onto /var
at boot time -- if you're using auto-var on MFS all the time,
On 4/6/10, Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
On 07/04/2010 06:28:40, Peter Steele wrote:
I found something else that's missing--/var/db/pkg is empty. It looks
like what the auto-var process does is a construct basic directory
structure but no data. Is there a solution to
I'm probably missing something here, but I'm not sure that's correct. If the
OP wants his own /var, then diskless(8) describes how
/var can be automagically populated (see also /etc/rc.initdiskless). The
nanobsd.sh script (designed with flash drives in mind) uses
this method. I looked into
On 4/6/10, Peter Steele pste...@maxiscale.com wrote:
What incidentally does /var get populated with? Our image has a custom
directory under /var but this did not show up in the MFS versions of this
directory. I can get around this but I wonder what else might not be
included?
I found
Not that I know of, unless you use the advantages of mfs then. Full circle,
bud. Now you're asking for necessities of the mfs or mfsroot systems.
I don't want to go there, and don't need to. I came up with a simple way to
populate /var from the original contents so I'm happy. The CD boots,
If FreeBSD cannot write to /tmp or /var on boot, it automatically
creates a MFS filesystems for those mountpoints and mounts them during boot.
You don't need to do anything.
It works as the same readonly compactflash environments out there.
What incidentally does /var get populated with? Our
On 4/6/10, Peter Steele pste...@maxiscale.com wrote:
If FreeBSD cannot write to /tmp or /var on boot, it automatically
creates a MFS filesystems for those mountpoints and mounts them during
boot. You don't need to do anything.
It works as the same readonly compactflash environments out there.
What incidentally does /var get populated with? Our image has a custom
directory under /var but this did not show up in the MFS versions of this
directory. I can get around this but I wonder what else might not be included?
I found something else that's missing--/var/db/pkg is empty. It looks
On 05/04/2010 18:03, Peter Steele wrote:
We have a USB boot stick based cloning process that we're considering porting
to a DVD based media. I'm not sure though that it's possible due to the
restrictions I've seen in the mfsroot environment we'd have to use. For
example, in our USB disk
It sounds like http://mfsbsd.vx.sk/ would be helpful to you.
(I havent used it yet due to lack of time but it looks good.)
Hmmm, that just might do the trick. I'll check it out, thanks.
___
freebsd-questions@freebsd.org mailing list
On 4/5/10, Peter Steele pste...@maxiscale.com wrote:
We have a USB boot stick based cloning process that we're considering
porting to a DVD based media. I'm not sure though that it's possible due to
the restrictions I've seen in the mfsroot environment we'd have to use. For
example, in our USB
But ... why are you constricting yourself to use mfs_root? I have many times
ran FreeBSD completely from CDrom, which
will give you all 700 (or a DVD, 4.3G) usable space.
I'd be happy to help, if you have questions. but please direct the questions
to the mailing list.
The reason I was
On 4/5/10, Peter Steele pste...@maxiscale.com wrote:
But ... why are you constricting yourself to use mfs_root? I have many
times ran FreeBSD completely from CDrom, which
will give you all 700 (or a DVD, 4.3G) usable space.
I'd be happy to help, if you have questions. but please direct the
If FreeBSD cannot write to /tmp or /var on boot, it automatically creates a
MFS filesystems for those mountpoints
and mounts them during boot. You don't need to do anything.
It works as the same readonly compactflash environments out there.
D'oh! Man, wish I had known that. I just tried it and
On 4/5/10, Peter Steele pste...@maxiscale.com wrote:
If FreeBSD cannot write to /tmp or /var on boot, it automatically creates a
MFS filesystems for those mountpoints
and mounts them during boot. You don't need to do anything.
It works as the same readonly compactflash environments out there.
20 matches
Mail list logo
