alternatively - use tar.
What I was trying to achieve, which I haven't done yet, was a smallish dump of the
core system. By that I mean system + ports, without distfiles, etc. Then a
separate dump of user data, which is considerably larger. At this point I am thinking I
should do this:
When I originally set up my SSD, the stuff I was following indicated there was
no need to put anythng on a separate filesystem. I'm now trying to build a
backup system on a usb drive and I want a separate /var and /tmp.
I had originally set the nodump flag on /tmp and /var, so my snapshot is
On 06/16/12 10:19, Wojciech Puchar wrote:
When I originally set up my SSD, the stuff I was following indicated there
was no need to put anythng on a separate filesystem. I'm now trying to
build a backup system on a usb drive and I want a separate /var and /tmp.
I had originally set the
When I originally set up my SSD, the stuff I was following indicated there was
no need to put anythng on a separate filesystem. I'm now trying to build a
backup system on a usb drive and I want a separate /var and /tmp.
I had originally set the nodump flag on /tmp and /var, so my snapshot is
Would rsync or cpdup from single user mode cover your needs? Should cover
everything and then you can just reboot into your newly partitioned system.
___
freebsd-questions@freebsd.org mailing list
2012-06-07 22:05, Gary Aitken skrev:
When I originally set up my SSD, the stuff I was following indicated there was
no need to put anythng on a separate filesystem. I'm now trying to build a
backup system on a usb drive and I want a separate /var and /tmp.
I had originally set the nodump
On Thu, 7 Jun 2012, Gary Aitken wrote:
When I originally set up my SSD, the stuff I was following indicated
there was no need to put anythng on a separate filesystem. I'm now
trying to build a backup system on a usb drive and I want a separate
/var and /tmp.
I had originally set the nodump
