From: Dan A. <da...@gm...> - 2004-01-31 08:38:51
|
On Thu, Jan 29, 2004 at 11:00:22AM +1000, Ian Latter wrote: > > > Hello Dan, > > > Primarily, the requirement is creating a root block file system (using > > the loopback block device), while changing the disto to use newly added > > devices nodes /dev (cobd0, cobd1, etc...) instead of the /dev/hd* nodes. > > > > The closest examples for this now are the file system images distributed > > with User Mode Linux. However, these images sometimes miss the /dev/console > > node which causes the init process to fail (this also happens with the > > regular non-UML Linux kernel). Creating that node fixes the problem. > > I've just whipped thru the docs again; is there any info on the devices > and their numbering. Are they literally the same as the UML distros? The cooperative device drivers that I wrote, cobd, conet, and cocon are not designed to be the same like the ones you find in the UML distros. cobd and ubd don't even have the same major number. BTW, I've uploaded to sourceforge a root file system that can be used for booting a system under coLinux. It extracts to a 1GB basic debian system that allows you to run 'apt-get' in order to get more packaages. > > Yesterday I was under the impression that the binaries are stable enough > > to be released. I hope to release some example binaries soon, so you > > and the others can experiment with it. > > This would be good. I have never had to build a CYGWIN dev > environment .. this would save a lot of time - methinks. Would the > binary bits be GPL? Yes, all the binary code that I am going to upload today is directly compiled from the tarball source that will be released along. coLinux is entirely under GPL. -- Dan Aloni da...@gm... |