From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <1dc3dbdc0c9e0ecbc86047c58e0a2d33@hamnavoe.com> <6c0a6fdef3589e5cb13618f19d9ac9fc@chula.quanstro.net> <27cbf24b3414cf47835e99ecbbd97e6d@brasstown.quanstro.net> Date: Mon, 10 Oct 2011 06:15:14 -0400 Message-ID: From: slash To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] copying fossil filesystem to a bigger disk Topicbox-Message-UUID: 356093ce-ead7-11e9-9d60-3106f5b1d025 > that's a good question. =A0if you just want to copy everything, i use the= shell > idiom > =A0 =A0 =A0 =A0disk/mkfs .... <{echo +} I ran this in /usr/bootes/ as bootes: su# disk/mkfs -a -s / <{echo +} > arch processing /fd/7 mkfs: /fd/7:1: can't open //dev/consctl: '//dev/consctl' permission denied mkfs: /fd/7:1: can't open //dev/kprint: '//dev/kprint' device or object already in use I guess it wasn't the brightest idea, because the arch file grew much bigger than all my files put together on the old drive. Should I mount the new drive to /n/kfs and not use the -a option? I was a little confused about these references to kfs while my filesystem is fossil.