From: ajpearce <ajp...@gm...> - 2005-01-29 13:54:52
|
Case study: Using coLinux to serve up linux partitions I tried everything. - Ext2 IFS drivers; not stable enough or provide enough support - NFS server for Windows from Windows Services for Unix - OpenAFS and CODA. But both of these store their data on Windows filesystems I asked various mailing lists how I could avoid using NTFS and FAT but they couldn't suggest anything native, even though there's a driver development kit called IFS that is designed exactly for this sort of thing! Then I saw a project called coLinux. Run linux in Windows! That's as impressive as Knoppix! I found that by having my root filesystem as a local file: <block_device index="0" path="\DosDevices\c:\coLinux\root_fs" enabled="true" /> ...I could then also specify raw partition support for my ext3 partition: <block_device index="2" path="\Device\Harddisk1\Partition2" enabled="true" /> ...and give access to that by samba!: `apt-get install samba` / `emerge samba` So I can now do nearly everything linux can but from within Windows, including full distccd, rather than a partially working cross compiled one. I can now chroot into my linux partition remotely and work as normal. In terms of networking I had trouble at first because I was trying to use NAT; InternetConnectionSharing (ICS). The answer was to bridge a colinux TAP interface to my ethernet card using: <network index="0" type="tap"/> ..and WITH COLINUX RUNNING AND THE TAP DEVICE CONNECTED, go to `Network Connections` in Windows, right click TAP and eth0 and BRIDGE connections. You'll be disconnected from the internet as you do this. My network is 192.168.1.x I set the bridged interface IP to 192.168.1.30 I then rebooted coLinux and: - set eth0 to 192.168.1.31 - route del default - route add default gw 192.168.1.1 (my router) - and edited /etc/resolv.conf to match my ISP DNS server - and `ping yahoo.com` to test, and `ping 192.168.1.1` and `ping 192.168.1.30` and `ping 127.0.0.1` if parts go wrong Seeing as this will be running all the time I am now cutting down both the size of the coLinux filesystem (125mb before cutting down), and memory (64mb by default, I'm going to try 32mb. I'll give it access to my swap partition too. Unfortunately though it seems root_fs images can't be resized just like that; you have to make a new image and copy over. Can anyone help improve that? |
From: Ian B. <ib...@gm...> - 2005-01-29 15:35:38
|
There are several utilities for different types of FS's, like ext2, ext3 and reiserfs (some are better than others) to resize "on the fly". I don't necessarily mean while the OS is running, but at least from another partition. Pretty much all of the instructions are in the Wiki. They involve adding extra space to the end of the partition file (if you're using coLinux style partition files), then telling the filesystem it has that much more space. It will format it, and extend itself across the new space. Now if you want TRUE on the fly dynamic resizing, give LVM a look at. You can create a new disk image, let coLinux use it, associate it with LVM, tell LVM its available and then extend an LVM volume across the new space, all while the filesystem is running! Ian On Sat, 29 Jan 2005 13:54:50 +0000, ajpearce <ajp...@gm...> wrote: > Case study: Using coLinux to serve up linux partitions > > I tried everything. > > - Ext2 IFS drivers; not stable enough or provide enough support > - NFS server for Windows from Windows Services for Unix > - OpenAFS and CODA. But both of these store their data on Windows filesystems > > I asked various mailing lists how I could avoid using NTFS and FAT but > they couldn't suggest anything native, even though there's a driver > development kit called IFS that is designed exactly for this sort of > thing! > > Then I saw a project called coLinux. Run linux in Windows! That's as > impressive as Knoppix! > > I found that by having my root filesystem as a local file: > <block_device index="0" path="\DosDevices\c:\coLinux\root_fs" enabled="true" /> > > ...I could then also specify raw partition support for my ext3 partition: > <block_device index="2" path="\Device\Harddisk1\Partition2" enabled="true" /> > > ...and give access to that by samba!: > `apt-get install samba` / `emerge samba` > > So I can now do nearly everything linux can but from within Windows, > including full distccd, rather than a partially working cross compiled > one. > > I can now chroot into my linux partition remotely and work as normal. > > In terms of networking I had trouble at first because I was trying to > use NAT; InternetConnectionSharing (ICS). The answer was to bridge a > colinux TAP interface to my ethernet card using: > <network index="0" type="tap"/> > > ..and WITH COLINUX RUNNING AND THE TAP DEVICE CONNECTED, go to > `Network Connections` in Windows, right click TAP and eth0 and BRIDGE > connections. You'll be disconnected from the internet as you do this. > > My network is 192.168.1.x > I set the bridged interface IP to 192.168.1.30 > I then rebooted coLinux and: > > - set eth0 to 192.168.1.31 > - route del default > - route add default gw 192.168.1.1 (my router) > - and edited /etc/resolv.conf to match my ISP DNS server > - and `ping yahoo.com` to test, and `ping 192.168.1.1` and `ping > 192.168.1.30` and `ping 127.0.0.1` if parts go wrong > > Seeing as this will be running all the time I am now cutting down both > the size of the coLinux filesystem (125mb before cutting down), and > memory (64mb by default, I'm going to try 32mb. I'll give it access to > my swap partition too. > > Unfortunately though it seems root_fs images can't be resized just > like that; you have to make a new image and copy over. > > Can anyone help improve that? > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: ajpearce <ajp...@gm...> - 2005-01-29 18:17:00
|
Very regretably it seems that TAP is extremely slow :( Running a samba server benchmarks at under 2mb/sec (bytes not bits); done with siSandra: http://www.benchmarkhq.ru/english.html?/sandradl_e.html ((hdparm -Tt doesn't work with /dev/cobd* by the way)) Data can be injected but that spoils the point: http://www.colinux.org/wiki/index.php/archiveascobd?PHPSESSID=fb76dd5197529231edc3d0182012d040 And these methods are just copying: http://www.colinux.org/wiki/index.php/ExpandingRoot?PHPSESSID=fb76dd5197529231edc3d0182012d040 So i'll have to check out LVM and see if I can speed up TAP somehow. On Sat, 29 Jan 2005 10:35:13 -0500, Ian Bonnycastle <ib...@gm...> wrote: > There are several utilities for different types of FS's, like ext2, > ext3 and reiserfs (some are better than others) to resize "on the > fly". I don't necessarily mean while the OS is running, but at least > from another partition. Pretty much all of the instructions are in the > Wiki. They involve adding extra space to the end of the partition file > (if you're using coLinux style partition files), then telling the > filesystem it has that much more space. It will format it, and extend > itself across the new space. > > Now if you want TRUE on the fly dynamic resizing, give LVM a look at. > You can create a new disk image, let coLinux use it, associate it with > LVM, tell LVM its available and then extend an LVM volume across the > new space, all while the filesystem is running! > > Ian > > On Sat, 29 Jan 2005 13:54:50 +0000, ajpearce <ajp...@gm...> wrote: > > Case study: Using coLinux to serve up linux partitions > > > > I tried everything. > > > > - Ext2 IFS drivers; not stable enough or provide enough support > > - NFS server for Windows from Windows Services for Unix > > - OpenAFS and CODA. But both of these store their data on Windows filesystems > > > > I asked various mailing lists how I could avoid using NTFS and FAT but > > they couldn't suggest anything native, even though there's a driver > > development kit called IFS that is designed exactly for this sort of > > thing! > > > > Then I saw a project called coLinux. Run linux in Windows! That's as > > impressive as Knoppix! > > > > I found that by having my root filesystem as a local file: > > <block_device index="0" path="\DosDevices\c:\coLinux\root_fs" enabled="true" /> > > > > ...I could then also specify raw partition support for my ext3 partition: > > <block_device index="2" path="\Device\Harddisk1\Partition2" enabled="true" /> > > > > ...and give access to that by samba!: > > `apt-get install samba` / `emerge samba` > > > > So I can now do nearly everything linux can but from within Windows, > > including full distccd, rather than a partially working cross compiled > > one. > > > > I can now chroot into my linux partition remotely and work as normal. > > > > In terms of networking I had trouble at first because I was trying to > > use NAT; InternetConnectionSharing (ICS). The answer was to bridge a > > colinux TAP interface to my ethernet card using: > > <network index="0" type="tap"/> > > > > ..and WITH COLINUX RUNNING AND THE TAP DEVICE CONNECTED, go to > > `Network Connections` in Windows, right click TAP and eth0 and BRIDGE > > connections. You'll be disconnected from the internet as you do this. > > > > My network is 192.168.1.x > > I set the bridged interface IP to 192.168.1.30 > > I then rebooted coLinux and: > > > > - set eth0 to 192.168.1.31 > > - route del default > > - route add default gw 192.168.1.1 (my router) > > - and edited /etc/resolv.conf to match my ISP DNS server > > - and `ping yahoo.com` to test, and `ping 192.168.1.1` and `ping > > 192.168.1.30` and `ping 127.0.0.1` if parts go wrong > > > > Seeing as this will be running all the time I am now cutting down both > > the size of the coLinux filesystem (125mb before cutting down), and > > memory (64mb by default, I'm going to try 32mb. I'll give it access to > > my swap partition too. > > > > Unfortunately though it seems root_fs images can't be resized just > > like that; you have to make a new image and copy over. > > > > Can anyone help improve that? > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > > Tool for open source databases. Create drag-&-drop reports. Save time > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |