My server is running on a mini-ITX board with a VIA C3 1GHz CPU. With
512MB RAM, and it works quite OK.
Took a while to install, however, since I did a stage 1 install. And I
used to have that machine as my desktop earlier, running X(.org),
Firefox and all. No problems whatsoever, besides the fact
Hi there!
I've done exactly this for quite some time. And I even implemented
something resembling a program to do it for me, without the need for
locking or other more advanced functionality. Ran it automatically
every night, without supervision, and it worked fine for me.
If you're interested, t
Hi there!
I think it'd be CONFIG_BLK_DEV_LOOP, yes. But if you set it to "y",
it's compiled into kernel and isn't a module.
If you want it to be a module, set it to "m".
In menuconfig, it's Device Drivers -> Block Devices -> Loopback device support.
At least in 6.11.x.
Regards,
/M
On 4/14/05
Hi!
Try not using the /dev/loop0. If I remember correctly, the default for
loop is to look up a free loop-device.
So, try...
mount -t iso9660 /mnt/packages-x86-2005.0.iso /mnt/iso -o loop
>From the man-page:
"If no explicit loop device is mentioned (but just an option `-o loop'
is given), the
I'm guessing V.C.S in this case refers to "Version Control System",
which cvs is an example of.
/Magnus
On Apr 7, 2005 4:19 AM, Zhang Weiwu <[EMAIL PROTECTED]> wrote:
> Robert G. Hays wrote:
>
> > Note if you're not used to V.C.S.'s :: you can get tings without
> > *officially* checking them out
5 matches
Mail list logo
