You can subscribe to this list here.
2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Regis N. <re...@ho...> - 2004-04-03 05:01:17
|
Little typo: colinux.nsi line 197 , read "iDl.ini" instead of "test.ini" test.nsi line 94 idem Regis NEBOR ----- Original Message ----- From: "Regis NEBOR" <re...@ho...> To: "Dan Aloni" <da...@co...> Cc: <col...@li...> Sent: Friday, April 02, 2004 8:37 PM Subject: Re: [coLinux-devel] XML configuration > Here it is. I merged my test.nsi in the current colinux.nsi. > I didn't have the setup to test. It should just work or be really close to > it :). > Basically the installer can now download images from sourceforge on a > totally random basis , or depending of the region. > > Regis NEBOR > > ----- Original Message ----- > From: "Dan Aloni" <da...@co...> > To: "Cooperative Linux Development" <col...@li...> > Sent: Friday, April 02, 2004 4:51 AM > Subject: [coLinux-devel] XML configuration > > > > Hello, > > > > Would anyone like to volunteer and create a GUI-based .colinux.xml > > generator/editor ? It could help new users of coLinux and It doesn't > > require any kernel programming experience in order to be developed. > > > > I'd prefer if you use the FLTK toolkit. We can later merge it into > > the FLTK console so it would appear more like VMware from the aspect > > of editing the currently used configuration. > > > > I'd also thank anyone who can send a patch for the colinux.nsi script > > that points the users to the rootfs image download location and > > Wiki site. > > > > Thanks, > > > > -- > > Dan Aloni > > da...@co... > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > |
From: Regis N. <re...@ho...> - 2004-04-03 04:37:46
|
Here it is. I merged my test.nsi in the current colinux.nsi. I didn't have the setup to test. It should just work or be really close to it :). Basically the installer can now download images from sourceforge on a totally random basis , or depending of the region. Regis NEBOR ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Cooperative Linux Development" <col...@li...> Sent: Friday, April 02, 2004 4:51 AM Subject: [coLinux-devel] XML configuration > Hello, > > Would anyone like to volunteer and create a GUI-based .colinux.xml > generator/editor ? It could help new users of coLinux and It doesn't > require any kernel programming experience in order to be developed. > > I'd prefer if you use the FLTK toolkit. We can later merge it into > the FLTK console so it would appear more like VMware from the aspect > of editing the currently used configuration. > > I'd also thank anyone who can send a patch for the colinux.nsi script > that points the users to the rootfs image download location and > Wiki site. > > Thanks, > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: tei <42...@in...> - 2004-04-03 01:01:42
|
JOSE MIGUEL MARTINEZ escribió: > First of all, congratulations and thanks for this great software. > Now I can get rid of vmware and cygwin and use something more useful and > open ;-) > > I wanted to add something to the whislist, it is something I would find > really useful. I use colinux for getting a handy debian system when I > have to work in Windows. But I would like to get rid of the two windows > opened when colinux starts. I do not need them as I connect to colinux > through ssh, and I would thank put them in a small icon in the task bar. > (as messenger and getright do). > > Another thing I would like is having a colinux machine running as a > service, not needing to log in a Windows session to have it runnning and > being started when windows starts. Later I could log in via ssh and this > way I could do a lot of things I like to do on Unix machines (tunnels, > cron jobs...) in Windows machines I cannot migrate. > > Thanks for all and congratulations again for this great piece of software, > txemi. > a user easy workaround is to rename colinux-console-nt.exe to colinux-console-fltk. dbl click on colinux-daemon will open only 1 window, a NT console that you can force FULLSCREEN with the usual alt-enter hotkeys Suerte con eso, Jose. note: I feel very very bad posting this here. I know exist some feedback, wishlish, whatever and forums at sourceforge, I dont want to clutter this mail list with users mails bouncing here and there, so... maybe its need another mail list, a colinux-users@ EXCEPT - IF - developpers are not annoyed by this noise. |
From: Digital I. Inc. <ok...@di...> - 2004-04-02 23:16:06
|
Hello Ian Latter. I think one idea is using sbuml on coLinux. http://sbuml.sourceforge.net/ this is suspending function of user mode linux. and I think same suspending image can share both sbuml on native Linux and sbuml on coLinux on Windows. of course, it runs on user mode. so you can run untrusted VM safely. --- Okajima. |
From: <ch...@to...> - 2004-04-02 19:36:06
|
2 bugs I found 1) Not really a bug but when using telnet to test the shutdown linux configuration the telnet that comes with windows 2k sends cr/lf the read statement in the script leaves the cr as part of $REPLY . I was able to filter this off with if [ ${REPLY:0:6} = 'KILLME' ]; then and this still works fine when using it. The 6 would need to be changed for a different length password 2) I am not getting clean shutdowns when shuting down windows while service is running both when starting the service manualy or automaticly. net stop colinux works great. I'm not shure if the problem is that windows is not waiting till the service gives the ok or if the message is not getting sent. (It's just fscking due to unclean shutdown) I could do further tests to see on monday or tuesday if you can not reproduce this. I'm using an up to date win2k chris > I'm proud to announce that CoLinuxService v0.1 has been released. > > It allows you to run colinux as a Windows service and supports clean > shutdown procedure with elementary authentication. > Any feedback is welcome. Feel free to send patches and I'll include them > in > future versions. > > Jarek |
From: Digital I. Inc. <ok...@di...> - 2004-04-02 19:10:00
|
Umm.. Nobody wants to do it? Okay, It is easy. I will do it. >Hello, > >Would anyone like to volunteer and create a GUI-based .colinux.xml >generator/editor ? It could help new users of coLinux and It doesn't >require any kernel programming experience in order to be developed. > >I'd prefer if you use the FLTK toolkit. We can later merge it into >the FLTK console so it would appear more like VMware from the aspect >of editing the currently used configuration. > >I'd also thank anyone who can send a patch for the colinux.nsi script >that points the users to the rootfs image download location and >Wiki site. > >Thanks, > >-- >Dan Aloni >da...@co... > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Regis N. <re...@ho...> - 2004-04-02 14:54:05
|
I'll modify the installer script. Regis NEBOR ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Cooperative Linux Development" <col...@li...> Sent: Friday, April 02, 2004 4:51 AM Subject: [coLinux-devel] XML configuration > Hello, > > Would anyone like to volunteer and create a GUI-based .colinux.xml > generator/editor ? It could help new users of coLinux and It doesn't > require any kernel programming experience in order to be developed. > > I'd prefer if you use the FLTK toolkit. We can later merge it into > the FLTK console so it would appear more like VMware from the aspect > of editing the currently used configuration. > > I'd also thank anyone who can send a patch for the colinux.nsi script > that points the users to the rootfs image download location and > Wiki site. > > Thanks, > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Florent C. <flo...@un...> - 2004-04-02 14:45:33
|
I have applied the imagecfg patch on the executables, now colinux works perfectly on my P4 3.0C HT. Like Alejandro, I've patched all .exe (I did not try to apply the patch on colinux-deamon only). Florent -----Message d'origine----- De=A0: Alejandro R. Sedeno [mailto:as...@MI...]=20 Envoy=E9=A0: vendredi 2 avril 2004 16:36 =C0=A0: Dan Aloni Cc=A0: Florent CUETO; col...@li... Objet=A0: Re: [coLinux-devel] SMP system freeze completely On Fri, 2004-04-02 at 09:11, Dan Aloni wrote: > On Tue, Mar 30, 2004 at 03:51:29PM -0500, Alejandro R. Sedeno wrote: > > I had the same problem on my work machine (P4, HT). > >=20 > > Until a more permanent fix is made, what you can do is use imagecfg > > (google: imagecfg) to set the colinux binaries to be uniprocessor. > >=20 > > in your colinux dir: > > imagecfg -u *.exe >=20 > Are you saying that applying this modification to the executables > allows to run coLinux on SMP/HT setups? >=20 > If by tying the daemon process to one CPU the sympthoms stop from=20 > occuring, it may give a clue about what is causing the problem. I'm doing that now at work, it seems to work most of the time, including all night last night. I've had a couple issues when starting and stopping it multiple times, but I'd venture to say that's a different problem. Note: I've not tested to see which specific binaries should be uniproc. I think the colinux-daemon would be sufficient, but I just opted to change them all. -Alejandro |
From: Alejandro R. S. <as...@MI...> - 2004-04-02 14:36:02
|
On Fri, 2004-04-02 at 09:11, Dan Aloni wrote: > On Tue, Mar 30, 2004 at 03:51:29PM -0500, Alejandro R. Sedeno wrote: > > I had the same problem on my work machine (P4, HT). > > > > Until a more permanent fix is made, what you can do is use imagecfg > > (google: imagecfg) to set the colinux binaries to be uniprocessor. > > > > in your colinux dir: > > imagecfg -u *.exe > > Are you saying that applying this modification to the executables > allows to run coLinux on SMP/HT setups? > > If by tying the daemon process to one CPU the sympthoms stop from > occuring, it may give a clue about what is causing the problem. I'm doing that now at work, it seems to work most of the time, including all night last night. I've had a couple issues when starting and stopping it multiple times, but I'd venture to say that's a different problem. Note: I've not tested to see which specific binaries should be uniproc. I think the colinux-daemon would be sufficient, but I just opted to change them all. -Alejandro |
From: Dan A. <da...@co...> - 2004-04-02 14:25:37
|
On Mon, Mar 29, 2004 at 09:12:17AM -0800, Tracy R Reed wrote: > I read somewhere that the Japanese version of Knoppix had been modified to > use colinux. Has anyone done the same with the english version? How well > did it work? It would be nice to have a knoppix disk that users don't have > to reboot their PC for, just insert it into the drive and Windows > automatically starts Linux. Is this possible? The Japanese interface is optional (but it is set as default in the images we use). If you specifiy lang=en in the boot parameters you get the regular English verison. Running coLinux from an Autorun CDROM is currently something we are working on. It is basically a minimized bootstrapping root filesystem that uses the cloop.o (compressed loop) kernel module in order to mount the KNOPPIX image that sits inside the KNOPPIX CDROM iso. On startup it copies basic root file system files and set the symlinks for the rest of the directories inside the image. The image itself compressed is only 1.2mb and the only requirement is a KNOPPIX iso file or a real KNOPPIX CDROM in \Device\CdRom0. Besides coLinux itself, an X server would be automatically launched from the CDROM in order to provide a graphic interface. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-04-02 14:11:06
|
On Tue, Mar 30, 2004 at 03:51:29PM -0500, Alejandro R. Sedeno wrote: > I had the same problem on my work machine (P4, HT). > > Until a more permanent fix is made, what you can do is use imagecfg > (google: imagecfg) to set the colinux binaries to be uniprocessor. > > in your colinux dir: > imagecfg -u *.exe Are you saying that applying this modification to the executables allows to run coLinux on SMP/HT setups? If by tying the daemon process to one CPU the sympthoms stop from occuring, it may give a clue about what is causing the problem. -- Dan Aloni da...@co... |
From: <ch...@to...> - 2004-04-02 13:40:58
|
> BTW. The "ssh" would be run in a LocalSystem context - that means: no > profile, no HKEY_CURRENT_USER, and so on. Have you ever used ssh.exe in > this > environment? How would it handle "known_hosts"? I have little understanding of this kind of windows stuff when I give this a try today that will be my first time messing with services in windows for real. For some reason my ideas don't always work out as often in window as they do in Linux. I have not messed with any of the power managemet stuff in linux but what about the powerfail stuff in init? Could coLinux-daemon.exe somehow pass that when told to shutdown. I'm not a programer (yet) so I'm not shure how this would be done. chris |
From: Dan A. <da...@co...> - 2004-04-02 12:51:34
|
Hello, Would anyone like to volunteer and create a GUI-based .colinux.xml generator/editor ? It could help new users of coLinux and It doesn't require any kernel programming experience in order to be developed. I'd prefer if you use the FLTK toolkit. We can later merge it into the FLTK console so it would appear more like VMware from the aspect of editing the currently used configuration. I'd also thank anyone who can send a patch for the colinux.nsi script that points the users to the rootfs image download location and Wiki site. Thanks, -- Dan Aloni da...@co... |
From: Jaroslaw K. <ja...@zd...> - 2004-04-01 22:00:35
|
I'm proud to announce that CoLinuxService v0.1 has been released. It allows you to run colinux as a Windows service and supports clean shutdown procedure with elementary authentication. Full source code & binary is ready for download at http://jaak.sav.net/colinux/CoLinuxService-0.1.zip The code is available under the BSD license. Note that it contains portions of Microsoft sample code by that comes with Visual C++ and I don't think it's GPL-able. Installation instructions can be found inside the archive. Any feedback is welcome. Feel free to send patches and I'll include them in future versions. Jarek |
From: John L. <jo...@su...> - 2004-04-01 20:22:42
|
start colinux with the -d argument. The daemon window will open minimized, and the terminal won't open at all. John JOSE MIGUEL MARTINEZ wrote: >First of all, congratulations and thanks for this great software. >Now I can get rid of vmware and cygwin and use something more useful and >open ;-) > >I wanted to add something to the whislist, it is something I would find >really useful. I use colinux for getting a handy debian system when I >have to work in Windows. But I would like to get rid of the two windows >opened when colinux starts. I do not need them as I connect to colinux >through ssh, and I would thank put them in a small icon in the task bar. >(as messenger and getright do). > >Another thing I would like is having a colinux machine running as a >service, not needing to log in a Windows session to have it runnning and >being started when windows starts. Later I could log in via ssh and this >way I could do a lot of things I like to do on Unix machines (tunnels, >cron jobs...) in Windows machines I cannot migrate. > >Thanks for all and congratulations again for this great piece of software, >txemi. > > > |
From: Jaroslaw K. <ja...@zd...> - 2004-04-01 20:20:14
|
Thanks for your comments, Chris. Regarding the security issue for Stop - I know it's not secure at all. The worst thing is that any network port scanner can shutdown your machine without your "only_from" comment is something that I've just updated in the zip file. As for using ssh to shutdown the machine - I'm not sure if we can guarantee that "ssh" can be safely called because windows may be in the process of shutting down. AFAIR spawning new processes isn't guaranteed to succeed at this moment. I may be wrong though. BTW. The "ssh" would be run in a LocalSystem context - that means: no profile, no HKEY_CURRENT_USER, and so on. Have you ever used ssh.exe in this environment? How would it handle "known_hosts"? I'm not sure I can release my source code to the public because it uses portions of microsoft's sample code "service.c". As soon as I get rid of this, I'll publish the sources so that everyone can play with them. Jarek ----- Original Message ----- From: <ch...@to...> To: "Jaroslaw Kowalski" <ja...@zd...> Cc: <col...@li...> Sent: Thursday, April 01, 2004 9:50 PM Subject: Re: Running CoLinux as a service (WAS Re: [coLinux-devel] Wishlist) > I just downloaded http://jaak.sav.net/colinux/CoLinuxService.zip but don't > have time to try it today. Looks like a really cool idea. One thing that > you might want to add to the readme is that if the machine is setup for > bridged networking then It would be a good idea to add > > only_from = windowsIPaddress > > to the /etc/xinetd.d/shutdown file to add at least a moderate amount of > security. For the truely paranoid it may be a good idea to add the ability > to do something like > > [stop] > cmd ssh -i c:\Coshutdownid 192.168.0.40 shutdown -h now > > of course an unencrypted key pair would need to be generated for this so > it probably would not be much more secure than the current method with the > only_from added unless the id was readable only by the administrator > group. > > chris > > > > Here's my quick and dirty way to run coLinux as a service in a reliable > > manner. > > > > I have written a small service process, called CoLinuxService. When > > started > > it spawns a new instance of "colinux-daemon.exe". The service terminates > > whenever the colinux-daemon.exe dies (something difficult to achieve with > > srvany.exe). > > > > I needed a way to reliably shutdown the coLinux instance, so I developed a > > quick hack. The linux machine has a special "xinetd" listener that listens > > on port 15555 does nothing but shutting down the machine. > > > > With this mechanism in place, whenever CoLinuxService receives "Stop" > > command it just connects to the specified port and this initiates the safe > > shutdown sequence. If "connect()" call fails the colinux-daemon.exe is > > terminated. > > > > The mechanism somewhat proved to reliable and I had no problems with it > > for > > 4, and that's why I decided to publish it. > > > > Binary of CoLinuxService.exe is available at > > http://jaak.sav.net/colinux/CoLinuxService.zip > > Setup instructions inside. > > > > Contact me if you want to get access to the source code. > > > > Jarek > > ----- Original Message ----- > > From: "JOSE MIGUEL MARTINEZ" <tx...@cl...> > > To: <col...@li...>; > > <col...@li...> > > Cc: <tx...@eu...> > > Sent: Thursday, April 01, 2004 6:15 PM > > Subject: [coLinux-devel] Wishlist > > > > > >> > >> First of all, congratulations and thanks for this great software. > >> Now I can get rid of vmware and cygwin and use something more useful and > >> open ;-) > >> > >> I wanted to add something to the whislist, it is something I would find > >> really useful. I use colinux for getting a handy debian system when I > >> have to work in Windows. But I would like to get rid of the two windows > >> opened when colinux starts. I do not need them as I connect to colinux > >> through ssh, and I would thank put them in a small icon in the task bar. > >> (as messenger and getright do). > >> > >> Another thing I would like is having a colinux machine running as a > >> service, not needing to log in a Windows session to have it runnning and > >> being started when windows starts. Later I could log in via ssh and this > >> way I could do a lot of things I like to do on Unix machines (tunnels, > >> cron jobs...) in Windows machines I cannot migrate. > >> > >> Thanks for all and congratulations again for this great piece of > >> software, > >> txemi. > >> > >> -- > >> ______________________________ > >> < hola, soy una firma horrible > > >> ------------------------------ > >> \ ^__^ > >> \ (oo)\_______ > >> (__)\ )\/\ > >> ||----w | > >> || || > >> > >> mail: txemi <tx...@eu...> > >> web: http://txemi.webhop.org > >> mirror: http://txemi2.webhop.org > >> > >> > >> > >> > >> ------------------------------------------------------- > >> This SF.Net email is sponsored by: IBM Linux Tutorials > >> Free Linux tutorial presented by Daniel Robbins, President and CEO of > >> GenToo technologies. Learn everything from fundamentals to system > >> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > >> _______________________________________________ > >> coLinux-devel mailing list > >> coL...@li... > >> https://lists.sourceforge.net/lists/listinfo/colinux-devel > >> > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by: IBM Linux Tutorials > > Free Linux tutorial presented by Daniel Robbins, President and CEO of > > GenToo technologies. Learn everything from fundamentals to system > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > > _______________________________________________ > > coLinux-devel mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > > |
From: Ronald P. <pij...@ds...> - 2004-04-01 19:54:01
|
morfic wrote: > Im very curious about the freezing part As just posted in another mail, the freezing was related to Gentoo accessing the framebuffer. I´ve had no problems in the course of this evening (on a HT machine even). Ronald |
From: Ronald P. <pij...@ds...> - 2004-04-01 19:51:44
|
ch...@to... wrote: > If you set inittab to boot to runlevel 3 that would probably be the > easiest way to find out if X is the problem. If that is it and you later > decide that you would like an X login then the solution I gave for fstab > would work for changing out inittab and if you want to use an xdmcp > solution for cygX or vnc then you could use my method to swap out the > config file for xdm or gdm there is a setting there for not creating a > local display which you could set in the coLinux version of the file. > > chris Hmm... that´s a mighty lot of files in one sentence. I think I understand what you´re getting at. I´ve been reading the Gentoo init documentation, and I´ve got the feeling there´s quite some interesting things to do with that. E.g. I could define a complete extra (soft)runlevel for booting coLinux. With a kernel parameter softlevel=coLinux it would boot into this runlevel. This should allow for doing some of the right things. Combined with your initrd boot option, I should be able to make this work. Thanks for the input. Ronald. |
From: <ch...@to...> - 2004-04-01 19:51:03
|
I just downloaded http://jaak.sav.net/colinux/CoLinuxService.zip but don't have time to try it today. Looks like a really cool idea. One thing that you might want to add to the readme is that if the machine is setup for bridged networking then It would be a good idea to add only_from = windowsIPaddress to the /etc/xinetd.d/shutdown file to add at least a moderate amount of security. For the truely paranoid it may be a good idea to add the ability to do something like [stop] cmd ssh -i c:\Coshutdownid 192.168.0.40 shutdown -h now of course an unencrypted key pair would need to be generated for this so it probably would not be much more secure than the current method with the only_from added unless the id was readable only by the administrator group. chris > Here's my quick and dirty way to run coLinux as a service in a reliable > manner. > > I have written a small service process, called CoLinuxService. When > started > it spawns a new instance of "colinux-daemon.exe". The service terminates > whenever the colinux-daemon.exe dies (something difficult to achieve with > srvany.exe). > > I needed a way to reliably shutdown the coLinux instance, so I developed a > quick hack. The linux machine has a special "xinetd" listener that listens > on port 15555 does nothing but shutting down the machine. > > With this mechanism in place, whenever CoLinuxService receives "Stop" > command it just connects to the specified port and this initiates the safe > shutdown sequence. If "connect()" call fails the colinux-daemon.exe is > terminated. > > The mechanism somewhat proved to reliable and I had no problems with it > for > 4, and that's why I decided to publish it. > > Binary of CoLinuxService.exe is available at > http://jaak.sav.net/colinux/CoLinuxService.zip > Setup instructions inside. > > Contact me if you want to get access to the source code. > > Jarek > ----- Original Message ----- > From: "JOSE MIGUEL MARTINEZ" <tx...@cl...> > To: <col...@li...>; > <col...@li...> > Cc: <tx...@eu...> > Sent: Thursday, April 01, 2004 6:15 PM > Subject: [coLinux-devel] Wishlist > > >> >> First of all, congratulations and thanks for this great software. >> Now I can get rid of vmware and cygwin and use something more useful and >> open ;-) >> >> I wanted to add something to the whislist, it is something I would find >> really useful. I use colinux for getting a handy debian system when I >> have to work in Windows. But I would like to get rid of the two windows >> opened when colinux starts. I do not need them as I connect to colinux >> through ssh, and I would thank put them in a small icon in the task bar. >> (as messenger and getright do). >> >> Another thing I would like is having a colinux machine running as a >> service, not needing to log in a Windows session to have it runnning and >> being started when windows starts. Later I could log in via ssh and this >> way I could do a lot of things I like to do on Unix machines (tunnels, >> cron jobs...) in Windows machines I cannot migrate. >> >> Thanks for all and congratulations again for this great piece of >> software, >> txemi. >> >> -- >> ______________________________ >> < hola, soy una firma horrible > >> ------------------------------ >> \ ^__^ >> \ (oo)\_______ >> (__)\ )\/\ >> ||----w | >> || || >> >> mail: txemi <tx...@eu...> >> web: http://txemi.webhop.org >> mirror: http://txemi2.webhop.org >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: IBM Linux Tutorials >> Free Linux tutorial presented by Daniel Robbins, President and CEO of >> GenToo technologies. Learn everything from fundamentals to system >> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >> _______________________________________________ >> coLinux-devel mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-devel >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: Ronald P. <pij...@ds...> - 2004-04-01 19:45:05
|
John LeSueur wrote: > My guess is that gentoo is trying to start x at that point? or doing > some other framebuffer operation? If so, that is what is causing the > freeze. Colinux doesn't yet support linux trying to use your display > adapter. Yes, you´re very right. Booting with ¨single¨ lets me run Gentoo nicely. In fact, this mail is currently typed from Remote X-ing into Gentoo inside coLinux in WindowsXP :) Getting there... Ronald. |
From: Jaroslaw K. <ja...@zd...> - 2004-04-01 17:05:30
|
Here's my quick and dirty way to run coLinux as a service in a reliable manner. I have written a small service process, called CoLinuxService. When started it spawns a new instance of "colinux-daemon.exe". The service terminates whenever the colinux-daemon.exe dies (something difficult to achieve with srvany.exe). I needed a way to reliably shutdown the coLinux instance, so I developed a quick hack. The linux machine has a special "xinetd" listener that listens on port 15555 does nothing but shutting down the machine. With this mechanism in place, whenever CoLinuxService receives "Stop" command it just connects to the specified port and this initiates the safe shutdown sequence. If "connect()" call fails the colinux-daemon.exe is terminated. The mechanism somewhat proved to reliable and I had no problems with it for 4, and that's why I decided to publish it. Binary of CoLinuxService.exe is available at http://jaak.sav.net/colinux/CoLinuxService.zip Setup instructions inside. Contact me if you want to get access to the source code. Jarek ----- Original Message ----- From: "JOSE MIGUEL MARTINEZ" <tx...@cl...> To: <col...@li...>; <col...@li...> Cc: <tx...@eu...> Sent: Thursday, April 01, 2004 6:15 PM Subject: [coLinux-devel] Wishlist > > First of all, congratulations and thanks for this great software. > Now I can get rid of vmware and cygwin and use something more useful and > open ;-) > > I wanted to add something to the whislist, it is something I would find > really useful. I use colinux for getting a handy debian system when I > have to work in Windows. But I would like to get rid of the two windows > opened when colinux starts. I do not need them as I connect to colinux > through ssh, and I would thank put them in a small icon in the task bar. > (as messenger and getright do). > > Another thing I would like is having a colinux machine running as a > service, not needing to log in a Windows session to have it runnning and > being started when windows starts. Later I could log in via ssh and this > way I could do a lot of things I like to do on Unix machines (tunnels, > cron jobs...) in Windows machines I cannot migrate. > > Thanks for all and congratulations again for this great piece of software, > txemi. > > -- > ______________________________ > < hola, soy una firma horrible > > ------------------------------ > \ ^__^ > \ (oo)\_______ > (__)\ )\/\ > ||----w | > || || > > mail: txemi <tx...@eu...> > web: http://txemi.webhop.org > mirror: http://txemi2.webhop.org > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
From: JOSE M. M. <tx...@cl...> - 2004-04-01 16:15:19
|
First of all, congratulations and thanks for this great software. Now I can get rid of vmware and cygwin and use something more useful and open ;-) I wanted to add something to the whislist, it is something I would find really useful. I use colinux for getting a handy debian system when I have to work in Windows. But I would like to get rid of the two windows opened when colinux starts. I do not need them as I connect to colinux through ssh, and I would thank put them in a small icon in the task bar. (as messenger and getright do). Another thing I would like is having a colinux machine running as a service, not needing to log in a Windows session to have it runnning and being started when windows starts. Later I could log in via ssh and this way I could do a lot of things I like to do on Unix machines (tunnels, cron jobs...) in Windows machines I cannot migrate. Thanks for all and congratulations again for this great piece of software, txemi. -- ______________________________ < hola, soy una firma horrible > ------------------------------ \ ^__^ \ (oo)\_______ (__)\ )\/\ ||----w | || || mail: txemi <tx...@eu...> web: http://txemi.webhop.org mirror: http://txemi2.webhop.org |
From: Wojciech D. <wo...@wi...> - 2004-04-01 13:23:04
|
> The gentoo image is configured to use dhcp I assume from below you are > using the TAP connection. If you do not have your internet conection set > up to be shared then your windows host will not be providing DHCP so you > need to setup gentoo with a static address or share your internet > connection in windows. That is my best guess based on what you said. I use TAP. My internet connection is shared. But will try with static IP. Wojtek |
From: <ch...@to...> - 2004-04-01 11:54:13
|
scp is probably the easiest way to copy files from windows and is usually th e one I use. But that depends on # 3 networking also setting up samba is probably the easiest to use every day once you get it configured also depends on #3 The gentoo image is configured to use dhcp I assume from below you are using the TAP connection. If you do not have your internet conection set up to be shared then your windows host will not be providing DHCP so you need to setup gentoo with a static address or share your internet connection in windows. That is my best guess based on what you said. chris > Hi, > > > I installed coLinux 0.6.0. I'm using gentoo-i686-ext3-1gb.bz2 image as > root fs. (I tried gentoo-i586-ext3-2g-deluxe.bz2 too.) > I'v encountered the following problems during booting up: > > > 1) coLinux can't find module dependencies because there is no directory > /lib/modules/2.4.25-co-0.6.0. > > There is /lib/modules/2.4.24-co in the gentoo image. How can I move > content of vmlinux-modules.tar.gz into image file? Are there any tools to > do this under Cygwin for example? > > > 2) putfont: KDFONTOP: No such file or directory > > > 3) Failed to bring eth0 up > > It hangs for 1-2 minutes during bringing eth0 up. If I look at the state > of tap0 connection (windows side (WinXP)) I can see that some packets are > sent but no packets are received. > coLinux is rather useless without networking. What could be wrong? > > > Wojciech Dec > |
From: Wojciech D. <wo...@wi...> - 2004-04-01 09:08:22
|
Hi, I installed coLinux 0.6.0. I'm using gentoo-i686-ext3-1gb.bz2 image as root fs. (I tried gentoo-i586-ext3-2g-deluxe.bz2 too.) I'v encountered the following problems during booting up: 1) coLinux can't find module dependencies because there is no directory /lib/modules/2.4.25-co-0.6.0. There is /lib/modules/2.4.24-co in the gentoo image. How can I move content of vmlinux-modules.tar.gz into image file? Are there any tools to do this under Cygwin for example? 2) putfont: KDFONTOP: No such file or directory 3) Failed to bring eth0 up It hangs for 1-2 minutes during bringing eth0 up. If I look at the state of tap0 connection (windows side (WinXP)) I can see that some packets are sent but no packets are received. coLinux is rather useless without networking. What could be wrong? Wojciech Dec |