From: Dan A. <da...@gm...> - 2004-02-06 17:50:02
|
Hello, Amongst the changes for tomorrow's release, we have: * The daemon is killable like any other Windows process. Closing it, CTRL-C, or ending the task, will all cleanly shutdown the Linux system. * printk()s are routed to the output of the colinux-daemon box, so you can see the kernel as it boots without opening the console. * Some fixes, especially for that BSOD bug lots of you have seen on startup, and for the network packet corruption issue. * The build doesn't depend anymore on the Microsoft DDK. * Overall design improvements. Stay tooned. -- Dan Aloni da...@gm... |
From: Richard G. <ric...@ri...> - 2004-02-06 18:11:37
|
I hope you know my wife will be mad at you because now I have to play with this tomorrow instead of household chores :-) Thanks Dan!! ----- Original Message ----- From: "Dan Aloni" <da...@gm...> To: "Cooperative Linux Development" <col...@li...> Sent: Friday, February 06, 2004 11:49 AM Subject: [coLinux-devel] The upcoming release > Hello, > > Amongst the changes for tomorrow's release, we have: > > * The daemon is killable like any other Windows process. Closing it, > CTRL-C, or ending the task, will all cleanly shutdown the Linux > system. > * printk()s are routed to the output of the colinux-daemon box, so you > can see the kernel as it boots without opening the console. > * Some fixes, especially for that BSOD bug lots of you have seen on > startup, and for the network packet corruption issue. > * The build doesn't depend anymore on the Microsoft DDK. > * Overall design improvements. > > Stay tooned. > > -- > Dan Aloni > da...@gm... > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
From: ePAc <ep...@ko...> - 2004-02-10 17:31:32
|
> Amongst the changes for tomorrow's release, we have: > > * The daemon is killable like any other Windows process. Closing it, > CTRL-C, or ending the task, will all cleanly shutdown the Linux > system. > * printk()s are routed to the output of the colinux-daemon box, so you > can see the kernel as it boots without opening the console. > * Some fixes, especially for that BSOD bug lots of you have seen on > startup, and for the network packet corruption issue. > * The build doesn't depend anymore on the Microsoft DDK. > * Overall design improvements. > could there also be "isofs"/"iso9660" support in kernel ? (so as to be able to mount a CDROM and boot off it.. :o) it would be sweet to be able to boot off a ramdisk from a install CD, load the CD up and install "Your Favorite Distro", which can then be shared with everyone ... :o) Thanks, Jok --- Nothing is foolproof to a sufficiently talented fool... oo ,(..)\ ~~ |
From: Nir P. <ni...@em...> - 2004-02-10 18:09:16
|
Hi, You can't just install any distribution on coLinux, much like you can't do it under UML. It is simply because kernel is modified, and you'll need that kernel after the installation. What you should probably have is a bootable 'floppy' or similar with a coLinux kernel that is compatible with that distribution (for example, have all the modules the installation program depends on), and a few scripts to replace the kernel after installation. I'm affraid you'll have to tweak one such bootable for every distribution (unless they run the same isolinux or installer). Basically, this is just a tip, but someone can go through with it and make such bootables. Maybe someday, even I will try. Nir ePAc wrote: >>Amongst the changes for tomorrow's release, we have: >> >> * The daemon is killable like any other Windows process. Closing it, >> CTRL-C, or ending the task, will all cleanly shutdown the Linux >> system. >> * printk()s are routed to the output of the colinux-daemon box, so you >> can see the kernel as it boots without opening the console. >> * Some fixes, especially for that BSOD bug lots of you have seen on >> startup, and for the network packet corruption issue. >> * The build doesn't depend anymore on the Microsoft DDK. >> * Overall design improvements. >> >> >> > >could there also be "isofs"/"iso9660" support in kernel ? >(so as to be able to mount a CDROM and boot off it.. :o) > >it would be sweet to be able to boot off a ramdisk from a install CD, load >the CD up and install "Your Favorite Distro", which can then be shared >with everyone ... :o) > >Thanks, >Jok > >--- >Nothing is foolproof to a sufficiently talented fool... > oo >,(..)\ > ~~ > > >------------------------------------------------------- >The SF.Net email is sponsored by EclipseCon 2004 >Premiere Conference on Open Tools Development and Integration >See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. >http://www.eclipsecon.org/osdn >_______________________________________________ >coLinux-devel mailing list >coL...@li... >https://lists.sourceforge.net/lists/listinfo/colinux-devel > > |
From: andre <avb...@gm...> - 2004-02-10 20:07:18
|
On Tuesday 10 February 2004 19:08, Nir Perry wrote: > Hi, > > You can't just install any distribution on coLinux, much like you can't > do it under UML. > It is simply because kernel is modified, and you'll need that kernel > after the installation. The kernel is about the only thing that is changed so if you install the colinux kernel than it should work. I think you can even install a real linux installation from inside windows and than start it with the windows boot selector. > > What you should probably have is a bootable 'floppy' or similar with a > coLinux kernel that is compatible with that distribution (for example, > have all the modules the installation program depends on), and a few > scripts to replace the kernel after installation. > I'm affraid you'll have to tweak one such bootable for every > distribution (unless they run the same isolinux or installer). They almost all use the same methode and the number of modules is very limited as in iso9660, cloop & cramfs. Most of them allow X output to another screen and the only real problem is the automatic searching for devices which you often can be done manual and the filesystem selection and formatation can be a problem > > Basically, this is just a tip, but someone can go through with it and > make such bootables. > Maybe someday, even I will try. > |