Menu
▾
▴
colinux-users
|
From: Crack, J. <jc...@yo...> - 2004-06-04 14:56:31
|
Hi, I think CoLinux is the best idea since sliced bread for those who want to use linux but don't want a dual boot or dedicated linux system. However as a newcommer to the world of linux I'm finding it a little hard to get things up and running. I've installed/downloaded all the necessary bits but double clicking on colinux-daemon.exe doesn't do anything. HELP!? Any chance of a tutorial or some form of step by step guide for new commers? Cheers, Jason |
|
From: Vitaly B. <vi...@01...> - 2004-06-04 15:05:04
|
Hello JC, I found this tutorial the most helpful: http://www.colinux.org/wiki/index.php/GettingStartedLong Regards, Vitaly Belman ICQ: 1912453 AIM: VitalyB1984 MSN: tmd...@ho... Yahoo!: VitalyBe Friday, June 4, 2004, 5:56:15 PM, you wrote: CJ> Hi, CJ> I think CoLinux is the best idea since sliced bread for those who want CJ> to use linux CJ> but don't want a dual boot or dedicated linux system. CJ> However as a newcommer to the world of linux I'm finding it a little CJ> hard to get things CJ> up and running. I've installed/downloaded all the necessary bits but CJ> double clicking on CJ> colinux-daemon.exe doesn't do anything. HELP!? CJ> Any chance of a tutorial or some form of step by step guide for new CJ> commers? CJ> Cheers, CJ> Jason CJ> ------------------------------------------------------- CJ> This SF.Net email is sponsored by the new InstallShield X. CJ> From Windows to Linux, servers to mobile, InstallShield X is the one CJ> installation-authoring solution that does it all. Learn more and CJ> evaluate today! http://www.installshield.com/Dev2Dev/0504 CJ> _______________________________________________ CJ> coLinux-users mailing list CJ> coL...@li... CJ> https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Robert C. <rw...@al...> - 2004-06-04 15:15:26
|
On Friday, Jun 4, 2004, at 09:56 US/Central, Crack, JC wrote: > However as a newcommer to the world of linux I'm finding it a little > hard to get things up and running. I've installed/downloaded all the > necessary bits but > double clicking on colinux-daemon.exe doesn't do anything. HELP!? > > Any chance of a tutorial or some form of step by step guide for new > commers? I agree. Which is why I created a colinux bundle with the binaries, a filesytem, and some networking tweaks. Have a look on the wiki: colinux.org/wiki/index.php/PreBuiltBundles They are not perfect and not the bleeding edge, but they do get you up to speed quickly. Once you are familiar with how colinux operates, then changing the pieces (e.g. the binaries, the filesystem, the networking) becomes much simpler. For more detailed notes, including how to get X11 w/VNC working, have a look here: http://cwelug.org/cgi-bin/wiki.cgi?CoLinux Give it a try and the let list know how it goes. Regards, - Robert |
|
From: Chuck A. <ch...@da...> - 2004-06-04 15:53:46
|
Robert Citek wrote: > I agree. Which is why I created a colinux bundle with the binaries, a > filesytem, and some networking tweaks. Have a look on the wiki: > > colinux.org/wiki/index.php/PreBuiltBundles Being that the most difficult part of getting coLinux working is the networking, I can imagine the prebuiltbundles are useful to a point ... I use coLinux in a work environment on win XP, so I couldn't go reassigning my NIC interface the way the bloody stupid crippled ICS wants to, but I found that installing the TAP driver and using the network bridging in XP to bridge it to my real connection works like a charm. You'll want to set the TAP driver to "always on" tho, or it'll be kicked out of the bridge on reboot. Another thing to note for new users: the TAP driver can take a LONG time to install during which the add device control panel will just hang with no feedback. Be patient, it will eventually install. coLinux is definitely awesome. I can't wait for the patch to become accepted into the mainstream kernel, or failing that, at least as a USE flag in gentoo... chuck |
|
From: Robert C. <rw...@al...> - 2004-06-04 16:47:46
|
On Friday, Jun 4, 2004, at 10:53 US/Central, Chuck Adams wrote: > Robert Citek wrote: >> I agree. Which is why I created a colinux bundle with the binaries, >> a filesytem, and some networking tweaks. Have a look on the wiki: >> colinux.org/wiki/index.php/PreBuiltBundles > > Being that the most difficult part of getting coLinux working is the > networking, I can imagine the prebuiltbundles are useful to a point > ... Yup, networking is the most difficult, with XP being a more difficult host than 2000, which is why I had to write the networking section as instructions on the wiki page. I wish I knew more on how to automate the configuration process. As for being useful to a point, absolutely correct. They are not meant to be a one-size-fits-all end-solution. I created them as starting points, so that people could get something working quickly and learn how the various pieces to colinux fit together. Hopefully, as users get more familiar with colinux, they will then tweak colinux to their heart's content, e.g changing filesystems, adding swap, adding/modifying installed applications, trying newer binaries, etc. I'm curious to know what in particular did you find difficult about configuring networking? I'd like to know so that I can incorporate those changes in the next bundle. Thanks in advance for any feedback. Regards, - Robert |
|
From: Chuck A. <ch...@da...> - 2004-06-04 20:59:26
|
Robert Citek wrote: > I'm curious to know what in particular did you find difficult about > configuring networking? I'd like to know so that I can incorporate > those changes in the next bundle. Confusion of the concepts of "bridged networking", for starters -- coLinux uses it in the sense that VMware does, whereas it means something quite different in XP (in XP it's a sort of poor-man's VLAN). I never got bridged networking to work (not certain whether it was due to my struggles with ICS), so I ended up using the TAP driver and bridging it. The TAP driver took ages to install, during which it just hung for a while. I was certain it had locked up, so I had killed the process it a couple times in my initial attempts. Also the advice to ensure that it's "always connected" was something I found elsewhere. I wrestled with ICS for a while but it always wanted to change the IP of my network interface to a hardwired 192.168.0.1 ... I don't think my 10.0.0.0 LAN would care much for that. I was unfamiliar with XP's bridging, so it took me a little while to understand it. Install the TAP driver, set it to "always connected", bridge it, set it on the linux side to use DHCP, and it works splendidly (assuming you install dhcpcd or pump and have a DHCP server on the network). It was just the trial and error of discovering those steps that was tricky. chuck |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X