Menu
▾
▴
colinux-users
|
From: Dan A. <da...@co...> - 2004-09-10 14:43:24
|
Hello,
I've released a snapshot to bring us a step closer to 0.6.2-final.
http://www.colinux.org/snapshots/coLinux-20040910.exe
The problem with 0.6.2 is that people are expected to move from 2.4.x
based coLinux system to 2.6.x based system on upgrade from 0.6.1 and
prir. Many of the newbie users would wonder why their Gentoo stops
working on this move (technically a script breakage over the /dev/cobdX-
to-/dev/cobd/X notation change caused by devfs).
Actually I think we should come with some sort of standard for a coLinux
root file system, e.g a /etc/colinux file that could hint a fix-me-up
initrd what's going on instead of auto-guessing.
Apropos initrd, this snapshot contains a beta version of an initrd
image that installs the kernel modules for the supplied vmlinux unto
the root filesystem (thanks George). You can test it simply by
adding the element: <initrd path="initrd.gz" />.
Anyway, the list of changes from the last snapshot which was quite a
while ago (20040710) includes:
* If the MAC address is unspecified, a random MAC is choosed
using the familiar TAP prefix (00:FF:XX:XX:XX:XX).
* Bug fix: Reception and delivery of network packets bigger than
2kb.
* Bug fix: Consoles and/or other daemons fail to connect to
colinux-daemon on startup (this is Windows only).
* Bug fix: Stop reboots where different gcc compiler versions are
used to compile linux.sys & vmlinux, with an error/warning
(George Boutwell).
* Enhanced coLinux keyboard handling support (sends raw scan codes
from Windows to linux) (Nuno Lucas).
* Bug fix: bad initialization caused unexpected SIGFPE for programs
compiled with -mpentium4 (me)
You might also want to take a look at the monotone ChangeLog (under
the snapshot directory for the monotone-declined users).
--
Dan Aloni
da...@co...
|
|
From: Ian A. <ia...@ab...> - 2004-09-10 17:11:48
|
On 10/09/2004 15:39, Dan Aloni wrote: > The problem with 0.6.2 is that people are expected to move from 2.4.x > based coLinux system to 2.6.x based system on upgrade from 0.6.1 and > prir. Many of the newbie users would wonder why their Gentoo stops > working on this move (technically a script breakage over the /dev/cobdX- > to-/dev/cobd/X notation change caused by devfs). I'm just wondering what the reason for this notation change is, particularly for aliases. Sure, the /dev/cobd/X notation helps to keep the /dev directory tidy, but /dev/hda/X seems to be going a bit too far as /dev/hda is normally a block special file, not a directory! |
|
From: Nuno L. <lu...@nl...> - 2004-09-10 17:35:08
|
Ian Abbott, dando pulos de alegria, escreveu : > I'm just wondering what the reason for this notation change is, > particularly for aliases. Sure, the /dev/cobd/X notation helps to keep > the /dev directory tidy, but /dev/hda/X seems to be going a bit too far > as /dev/hda is normally a block special file, not a directory! This has to do with devfs naming scheme and Gentoo uses and needs it to run. But devfs is being deprecated in favor of udev. Don't know how the udev naming scheme is. You can have the normal hda? names as symlinks to the others. They simply aren't created by default. Note that this is Gentoo specific (more devfs specific, really). Is not related to coLinux in any way. Regards, ~Nuno Lucas |
|
From: Eric S. J. <es...@ha...> - 2004-09-10 18:01:54
|
Nuno Lucas wrote: > This has to do with devfs naming scheme and Gentoo uses and needs it to > run. > But devfs is being deprecated in favor of udev. Don't know how the udev > naming scheme is. would it be too obnoxious to migrate straight to udev? |
|
From: Nuno L. <nt...@nl...> - 2004-09-11 04:19:31
|
Eric S. Johansson, dando pulos de alegria, escreveu : > Nuno Lucas wrote: > >> This has to do with devfs naming scheme and Gentoo uses and needs it >> to run. >> But devfs is being deprecated in favor of udev. Don't know how the >> udev naming scheme is. > > > would it be too obnoxious to migrate straight to udev? No, there are many who are doing it already. It simply isn't the default for gentoo yet (maybe because the devs were busy replacing XFree with X.Org as the default package ;). Another reason would be because the stable gentoo kernel is still 2.4.26, and udev works better with the 2.6 (or is required?) Look in the gentoo forums. I know there are good tutorials on doing the move, I simply didn't care about it enough. Regards, ~Nuno Lucas |
|
From: Eric S. J. <es...@ha...> - 2004-09-11 12:01:50
|
Nuno Lucas wrote: > Eric S. Johansson, dando pulos de alegria, escreveu : > >> Nuno Lucas wrote: >> >>> This has to do with devfs naming scheme and Gentoo uses and needs it >>> to run. >>> But devfs is being deprecated in favor of udev. Don't know how the >>> udev naming scheme is. >> >> >> >> would it be too obnoxious to migrate straight to udev? > > > No, there are many who are doing it already. It simply isn't the default > for gentoo yet (maybe because the devs were busy replacing XFree with > X.Org as the default package ;). ... apologies. I did not frame the question right. Maybe a better question to ask would be since the world is moving towards udev, would it be appropriate for co-linux to require use of udev as its baseline? no big deal either way I'm just wondering if it would simplify the installation process. ---eric |
|
From: Nuno L. <lu...@nl...> - 2004-09-11 17:23:25
|
Eric S. Johansson, dando pulos de alegria, escreveu : > apologies. I did not frame the question right. Maybe a better question > to ask would be since the world is moving towards udev, would it be > appropriate for co-linux to require use of udev as its baseline? > > no big deal either way I'm just wondering if it would simplify the > installation process. > As it is only more of a Gentoo problem, I don't think we should care much about it than having the problem explained in the Wiki. And it can be very easily solved either with symlinks or with "mknod". I don't see any big problem here. And it's just a question of time to the change occurs. Regards, ~Nuno Lucas |
|
From: Nuno L. <nt...@nl...> - 2004-09-12 13:59:20
|
Nuno Lucas, dando pulos de alegria, escreveu : > Eric S. Johansson, dando pulos de alegria, escreveu : > >> apologies. I did not frame the question right. Maybe a better question >> to ask would be since the world is moving towards udev, would it be >> appropriate for co-linux to require use of udev as its baseline? >> >> no big deal either way I'm just wondering if it would simplify the >> installation process. >> Just for completion, I switched my gentoo to udev today. It's really quite simple: 1) emerge udev 2) change all hdb/? to hdb? in fstab 3) add "gentoo=nodevfs" in the bootparams 4) reboot A litle warning appears because we didn't compiled hotplug in the kernel, but as we don't use it in colinux it doesn't matter. If we get to use it, it's only a kernel recompile away. Regards, ~Nuno Lucas |
|
From: Ian A. <ia...@ab...> - 2004-09-10 21:34:03
|
On 10/09/2004 18:32, Nuno Lucas wrote: > Ian Abbott, dando pulos de alegria, escreveu : > >> I'm just wondering what the reason for this notation change is, >> particularly for aliases. Sure, the /dev/cobd/X notation helps to >> keep the /dev directory tidy, but /dev/hda/X seems to be going a bit >> too far as /dev/hda is normally a block special file, not a directory! > > This has to do with devfs naming scheme and Gentoo uses and needs it to > run. But when I run Gentoo natively with a 2.6.x kernel with devfs enabled, I get the normal /dev/hda1 etc. |
|
From: Ian A. <ia...@ab...> - 2004-09-13 10:19:28
|
On 10/09/2004 21:50, Ian Abbott wrote: > On 10/09/2004 18:32, Nuno Lucas wrote: > >> Ian Abbott, dando pulos de alegria, escreveu : >> >>> I'm just wondering what the reason for this notation change is, >>> particularly for aliases. Sure, the /dev/cobd/X notation helps to >>> keep the /dev directory tidy, but /dev/hda/X seems to be going a bit >>> too far as /dev/hda is normally a block special file, not a directory! >> >> This has to do with devfs naming scheme and Gentoo uses and needs it >> to run. > > But when I run Gentoo natively with a 2.6.x kernel with devfs enabled, I > get the normal /dev/hda1 etc. More specifically, "/dev/hda1" ends up as a symlink to "ide/host0/bus0/target0/lun0/part1". The devfsd daemon is responsible for creating this symlink, using the MKOLDCOMPAT command in /etc/devfsd.conf. I tried using "ide/host0/bus0/target0/lun0/part1" as an alias in the coLinux xml file, but didn't expect it to work. I thought the "part1" bit would end up as "part/1", but the alias was too long and ended up truncated to "ide/host0/bus0/targ". I still maintain that the /dev/hda/1 naming scheme is purely an invention of coLinux (specifically, the cobd_spawn_alias function) and nothing to do with any pre-existing devfs naming scheme. Sure I could create a symlink to /dev/hda1 in /dev/devfsd.conf but that kind of defeats the point - I could create a symlink to /dev/cobd/0 instead. The only thing the aliasing buys me is the use of standard block major device numbers. |
|
From: <sl...@bl...> - 2004-09-13 09:29:19
|
Dan Aloni <da...@co...> writes: > Apropos initrd, this snapshot contains a beta version of an initrd > image that installs the kernel modules for the supplied vmlinux unto > the root filesystem (thanks George). You can test it simply by > adding the element: <initrd path="initrd.gz" />. Where is the initrd.gz file? It does not seem to be in the colinux-0.6.2-pre1.zip file. -- Joe |
|
From: Ian A. <ia...@ab...> - 2004-09-13 13:03:04
|
On 12/09/2004 12:23, Joe Wells wrote: > Dan Aloni <da...@co...> writes: >>Apropos initrd, this snapshot contains a beta version of an initrd >>image that installs the kernel modules for the supplied vmlinux unto >>the root filesystem (thanks George). You can test it simply by >>adding the element: <initrd path="initrd.gz" />. > > Where is the initrd.gz file? It does not seem to be in the > colinux-0.6.2-pre1.zip file. The coLinux-20040910.exe file installs it along with the other binaries. |
|
From: <sl...@bl...> - 2004-09-13 13:54:38
|
Ian Abbott <ia...@ab...> writes: > On 12/09/2004 12:23, Joe Wells wrote: > > Dan Aloni <da...@co...> writes: > >> Apropos initrd, this snapshot contains a beta version of an initrd > >> image that installs the kernel modules for the supplied vmlinux > >> unto the root filesystem (thanks George). You can test it simply by > >> adding the element: <initrd path="initrd.gz" />. > > > Where is the initrd.gz file? It does not seem to be in the > > > colinux-0.6.2-pre1.zip file. > > The coLinux-20040910.exe file installs it along with the other binaries. Is there some way I can extract initrd.gz from coLinux-20040910.exe without running the latter? I would rather not run a large monolithic installer that does a lot of things that I don't understand or need. -- Joe |
|
From: Ian A. <ia...@ab...> - 2004-09-13 16:34:47
|
On 13/09/2004 14:49, Joe Wells wrote: > Ian Abbott <ia...@ab...> writes: >>On 12/09/2004 12:23, Joe Wells wrote: >>>Where is the initrd.gz file? It does not seem to be in the >>>colinux-0.6.2-pre1.zip file. >> >>The coLinux-20040910.exe file installs it along with the other binaries. > > Is there some way I can extract initrd.gz from coLinux-20040910.exe > without running the latter? I would rather not run a large monolithic > installer that does a lot of things that I don't understand or need. None that I'm aware of. Perhaps an "extract only" option could be added to the installer. I suggest renaming your current coLinux directory, then running the installer to install coLinux to your usual coLinux directory (so the registry entries stay the same), but on the "Choose Components" page, deselect everything but the "coLinux" item. After installation, rename the old and new coLinux directories to restore the old coLinux directory's previous name (which was usurped by the new coLinux installation). |
|
From: Nuno L. <lu...@nl...> - 2004-09-13 16:46:15
|
Joe Wells, dando pulos de alegria, escreveu : > Is there some way I can extract initrd.gz from coLinux-20040910.exe > without running the latter? I would rather not run a large monolithic > installer that does a lot of things that I don't understand or need. I have a private build in a zip file. You can get it here: http://xpto.ath.cx/colinux/snapshots/colinux-0.6.2-pre1.zip Regards, ~Nuno Lucas |
|
From: Nuno L. <lu...@nl...> - 2004-09-14 23:30:21
|
Nuno Lucas, dando pulos de alegria, escreveu : > I have a private build in a zip file. You can get it here: > http://xpto.ath.cx/colinux/snapshots/colinux-0.6.2-pre1.zip Only today I realized that my build didn't included initrd.gz. If you are still interested, I have put the initrd.gz file there now: * http://xpto.ath.cx/colinux/snapshots/initrd.gz Sorry about that. Regards, ~Nuno Lucas |
|
From: Jaroslaw K. <ja...@zd...> - 2004-09-13 14:51:03
|
There's a problem with the module installation script in initrd. If i pass "ro root=/dev/cobd0" parameters it fails to isntall the modules. I have to use "root=/dev/cobd0 ro" to be successful. Jarek ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Cooperative Linux Development" <col...@li...> Cc: "Cooperative Linux Users" <col...@li...> Sent: Friday, September 10, 2004 4:39 PM Subject: [coLinux-devel] snapshot 20040910 (0.6.2-pre1) > Hello, > > I've released a snapshot to bring us a step closer to 0.6.2-final. > > http://www.colinux.org/snapshots/coLinux-20040910.exe > > The problem with 0.6.2 is that people are expected to move from 2.4.x > based coLinux system to 2.6.x based system on upgrade from 0.6.1 and > prir. Many of the newbie users would wonder why their Gentoo stops > working on this move (technically a script breakage over the /dev/cobdX- > to-/dev/cobd/X notation change caused by devfs). > > Actually I think we should come with some sort of standard for a coLinux > root file system, e.g a /etc/colinux file that could hint a fix-me-up > initrd what's going on instead of auto-guessing. > > Apropos initrd, this snapshot contains a beta version of an initrd > image that installs the kernel modules for the supplied vmlinux unto > the root filesystem (thanks George). You can test it simply by > adding the element: <initrd path="initrd.gz" />. > > Anyway, the list of changes from the last snapshot which was quite a > while ago (20040710) includes: > > * If the MAC address is unspecified, a random MAC is choosed > using the familiar TAP prefix (00:FF:XX:XX:XX:XX). > * Bug fix: Reception and delivery of network packets bigger than > 2kb. > * Bug fix: Consoles and/or other daemons fail to connect to > colinux-daemon on startup (this is Windows only). > * Bug fix: Stop reboots where different gcc compiler versions are > used to compile linux.sys & vmlinux, with an error/warning > (George Boutwell). > * Enhanced coLinux keyboard handling support (sends raw scan codes > from Windows to linux) (Nuno Lucas). > * Bug fix: bad initialization caused unexpected SIGFPE for programs > compiled with -mpentium4 (me) > > You might also want to take a look at the monotone ChangeLog (under > the snapshot directory for the monotone-declined users). > > -- > Dan Aloni > da...@co... > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
Thanks for helping keep SourceForge clean.
X