On Mon, 6 Mar 2000, Jan Harkes wrote:
> Also cfs/repair etc. will stop working as they talk to venus through a
> special control file in /coda. Is your cache stored in that ram-disk as
> well? Why not avoid the chroot and create some symlinks like:
>
> /usr -> /coda/usr
> /home -> /coda/home
>
On Mon, Mar 06, 2000 at 07:09:46AM -0500, Laszlo Vecsey wrote:
> I've tried running venus with '-rvmt 3' as was suggested on this list for
> a diskless coda client machine, but it causes venus to die with an error
> I've pasted below. This is with glibc and a Linu
Laszlo Vecsey wrote:
>
> The next thing I'm working on is chroot'ing into the /coda partition, but
> I've run into a problem. 'mknod' files don't appear on it, and so I'm at a
> loss as to what to do with the devices in /dev. I thought of mounting
> another ram drive as /dev, but in order to do t
Keith Winstein <[EMAIL PROTECTED]> ,in message <[EMAIL PROTECTED]
.edu>, wrote:
> One easy solution is to create an ext2 filesystem with your devices
> in it, stick that in Coda, and then mount that loopback onto /dev.
Dear god. The image would be in cache till the machine went down
On Mon, Mar 06, 2000 at 07:09:46AM -0500, Laszlo Vecsey wrote:
> The next thing I'm working on is chroot'ing into the /coda partition, but
> I've run into a problem. 'mknod' files don't appear on it, and so I'm at a
> loss as to what to do with the devices in /dev. I thought of mounting
> another
I've tried running venus with '-rvmt 3' as was suggested on this list for
a diskless coda client machine, but it causes venus to die with an error
I've pasted below. This is with glibc and a Linux 2.2.14 kernel, coda
5.3.5.
I'm actually posting this from a diskless coda
