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: Gregory M. T. <gmt...@am...> - 2004-04-20 06:46:32
|
On Tuesday 20 April 2004 01:16 am, morfic wrote: > is mkreiserfs supposed to work properly with this snapshot? > i can format a raw partition with ext3, no problem, i can then mount it, > access it, bench it, you get the idea > when i use mkreiserfs, i get an error telling me it can't make a device > that small (0 blocks) and exits <AOL> me too </AOL> Although I have not tried the snapshots lately, it's been this way for every version I've tried. strace shows it using 64-bit api's, if that matters. -- gmt |
From: morfic <mo...@bb...> - 2004-04-20 06:16:36
|
is mkreiserfs supposed to work properly with this snapshot? i can format a raw partition with ext3, no problem, i can then mount it, access it, bench it, you get the idea when i use mkreiserfs, i get an error telling me it can't make a device that small (0 blocks) and exits the people who now use reiserfs were those existing partitions? or did anyone successfully use mkreiserfs with this snapshot? if you DID use mkreiserfs, was this the binary snapshot or source snapshot? yes my last question is in regards to the (2) after the snapshot on the irc channels topic bottom line is, mkreiserfs --format 3.6 /dev/cobd3 fails due to 0 block size of cobd3 while mke2fs -j /dev/cobd3 works flawless and i can mount and enjoy this partition with ext3 on it thank you all in advance for any info on this |
From: John N. <jo...@mo...> - 2004-04-20 06:13:00
|
Kevin J. Menard, Jr. wrote: > Oh ok. That's good to know. I use a gentoo system, so I've just been > using devfs anyway. > > > On Apr 19, 2004, at 9:03 PM, Sergey Okhapkin wrote: > > Devfs successor udev can do exactly the same. Udev won't work under 2.4 kernels, so it should only be remembered for when we all have colinux-2.6 running. Devfs, although obsolete, will continue to work for the foreseeable future. |
From: Kevin J. M. Jr. <nir...@ne...> - 2004-04-20 05:42:21
|
Oh ok. That's good to know. I use a gentoo system, so I've just been using devfs anyway. -- Kevin On Apr 19, 2004, at 9:03 PM, Sergey Okhapkin wrote: > Devfs successor udev can do exactly the same. |
From: Robert C. <rw...@al...> - 2004-04-20 05:19:34
|
Hello all, I'm trying to build coLinux from source. But am running into some issues. I have the 2.4.26 kernel ( http://www.kernel.org/pub/linux/kernel/v2.4/linux-2.4.26.tar.bz2 ) and the 20040417 colinux snapshot ( http://colinux.org/snapshots/colinux-20040417.tar.gz ). Below is a transcript of the steps I did, using ellipses for brevity. I got two questions when applying the patch. The kernel seemed to compile OK, but is there any simple way to test it? Regards, - Robert ----- $ tree -L 2 -d ./colinux ./colinux |-- colinux-20040417 | |-- bin | |-- conf | |-- doc | |-- patch | `-- src `-- linux |-- Documentation |-- arch |-- crypto |-- drivers |-- fs |-- include |-- init |-- ipc |-- kernel |-- lib |-- mm |-- net `-- scripts $ cd colinux/linux $ patch -p1 < ../colinux-20040417/patch/linux patching file CREDITS patching file Documentation/devices.txt patching file arch/i386/config.in ... patching file mm/swapfile.c Reversed (or previously applied) patch detected! Assume -R? [n] n Apply anyway? [n] y Hunk #1 FAILED at 1006. Hunk #2 FAILED at 1044. 2 out of 2 hunks FAILED -- saving rejects to file mm/swapfile.c.rej patching file mm/vmalloc.c $ cp ../colinux-20040417/conf/linux-config .config $ make oldconfig # seemed to work fine ... $ make dep # seemed to work fine ... $ make vmlinux # seemed to work fine ... |
From: Dan A. <da...@co...> - 2004-04-20 04:59:10
|
On Mon, Apr 19, 2004 at 10:11:18AM -0400, Daniel R. Slater wrote: > The only real reason I can see for wanting to build under windows is if you > wanted to try and use Visual Studio and the Microsoft DDK to build. However, > this would involve a considerable number of changes as the compiler switches > are different, the source tree layout for device drivers is different, and > finally, the inline assembly syntax is different (Intel syntax vs. AT&T). > > On the other hand, if linux.sys were built with the Microsoft DDK, you could > source debug it with the Microsoft tools. Currently I don't believe there > is any way to source debug linux.sys since WinDbg doesn't know how to read > gcc symbols and there are no GNU tools for kernel debugging Windows. It seems that microsoft has recently released their compilers as Free Software, probably to promote Windows programmers. http://msdn.microsoft.com/visualc/vctoolkit2003/ I haven't read their EULA yet, but if it doesn't mean problems with GPL software, coLinux's binaries can be built with it. BTW, we only need their linker in order to build linux.sys along with a corresponding linux.pdb file. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-04-20 04:51:43
|
On Sun, Apr 18, 2004 at 11:45:46PM -0500, Tony Bierman wrote: > I?ve started a project to create a coLinux service and manager > application. The working Beta code launches coLinux as a Windows service > (localsystem account), and allows users to manage/connect to the coLinux > process through a system-tray based interface. > > I?m looking for a few testers to participate in a controlled Beta > testing phase. Please email me at bie...@bi... if you?re > interested. > > For more info, please see the screenshots located at this link: > > http://www.biermana.org/index.php?p=54 This looks really nice. Is it mergable to the coLinux source tree? I'd really like to add it in. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-04-20 04:44:03
|
On Mon, Apr 19, 2004 at 11:43:51AM -0500, Richard Goodwin wrote: > Alright, this is my first ever diff/patch of any kind, so please be gentle. > It's basically to get the README up to a more current state, and to give > some additional help on first time installations on Windows. I don't have > the CVS dirs, so the files are specified simply as README in the patch. > > Comments/feedback requested! Looks very good, applied. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-04-20 04:40:24
|
On Mon, Apr 19, 2004 at 12:22:41PM -0500, Richard Goodwin wrote: > Patched the XML file to include some comments, good for first time users? Thanks, it's applied. -- Dan Aloni da...@co... |
From: Dan A. <da...@co...> - 2004-04-20 04:38:09
|
On Mon, Apr 19, 2004 at 09:47:02PM +0100, Tony Hoyle wrote: > I've been having fun getting colinux to work on XP SP2 with AMD64. > > Generally it works... I have it stable with 256MB of RAM, but: > > 1. The XP SP2 firewall is a complete nazi so you'll have to do some > fiddling to get ping/traceroute to work. (For some reason best known to > Microsoft it opens the NetBIOS ports by default, but blocks most of the > useful types of ping... the other way around would have made more sense to > me, but whatever...) > 2. I had to upgrade winpcap to 3.0 as the one that ships with colinux > didn't work (3.1 doesn't work either but that's a beta so no surprise). Sounds like a good idea to ship pcap 3.0 with the release. > 3. TAP-Win32 is nonfunctional (known bug - see > http://groups.google.com/groups?threadm=4b2b7f04.0404121135.7a0b6b08%40posting.google.com) > 4. On AMD64 the DEP (Data Execution Protection) just completely barfs > colinux. I'm not really up on how it works, but AFAIK it puts the > processor into PAE mode and enables the NX (No execute) bit on all > allocated memory, and to execute within memory you have to change the > protection. With DEP enabled the machine reboots just after reading the > config file (doesn't bluescreen or anything, just falls over). You can put > executables into an exception list but it looks like colinux operates at > too low a level for the exceptions to operate. coLinux doesn't currently work on PAE setups. It actually assumes that the host didn't enable PAE. As long as the demand for it is low, it's also low in my long list of TODOs. However, the next release will check for PAE and refuse to work if it's enabled. -- Dan Aloni da...@co... |
From: Sergey O. <so...@so...> - 2004-04-20 01:02:19
|
Kevin J. Menard, Jr. wrote: > But isn't devfs deprecated? I know it'll work, but is this really the > best solution? > Devfs successor udev can do exactly the same. -- Sergey Okhapkin Somerset, NJ |
From: Kevin J. M. Jr. <nir...@ne...> - 2004-04-20 00:33:09
|
But isn't devfs deprecated? I know it'll work, but is this really the best solution? -- Kevin Sergey Okhapkin wrote: > That was not my suggestion but you forced me to think a little bit... > The solution is simple! Don't reinvent the wheel but... use devfs:-) |
From: Sergey O. <so...@so...> - 2004-04-19 23:54:34
|
John Nelson wrote: > This solution, although practical, does have one theoretical drawback: > eventually we'll have fsck working again, and the fact that this > approach requires us to modify the file system before checking it stinks > a bit. We could duplicate the check, but that is redundant. The best > long-term solution, IMHO, is to go with Sergey Okhapkin's suggestion (in > this same thread) and find a way to make the colinux daemon "educate" > the kernel at boot time that certain major/minor numbers devices are > actually aliases for other ones (so, for example, we could make > /dev/hdb1 and /dev/cobd2 become the same thing), but only when running > in hosted -- not native -- mode. That was not my suggestion but you forced me to think a little bit... The solution is simple! Don't reinvent the wheel but... use devfs:-) Here is a fragment of my dual-boot compatible (now :-) fstab: /dev/hda2 /boot ext2 noauto,noatime 1 1 /dev/hda6 / ext3 noatime 0 0 /dev/hda7 none swap sw 0 0 And the additional lines in /etc/devfsd.conf: #coLinux stuff REGISTER ^cobd0$ CFUNCTION GLOBAL mksymlink $devname hda6 UNREGISTER ^cobd0$ CFUNCTION GLOBAL unlink hda6 REGISTER ^cobd3$ CFUNCTION GLOBAL mksymlink $devname hda2 UNREGISTER ^cobd3$ CFUNCTION GLOBAL unlink hda2 REGISTER ^cobd1$ CFUNCTION GLOBAL mksymlink $devname hda7 UNREGISTER ^cobd1$ CFUNCTION GLOBAL unlink hda7 Huh? -- Sergey Okhapkin Somerset, NJ |
From: peter g. <plu...@p1...> - 2004-04-19 23:24:40
|
the good news is apart from porting to coserial (which does not exist yet) conenction trapping is virtuall finished for both tcp and udp the bad new is the iptables featre i need seems to be broken on 2.4.26 i had previosly been testing on vmware because colinux at the stage was not shipping with the modules i needed the vmware system in question had a 2.4.20 kernel i checked it on anoter vmware system which i consider more sacrificial which has a 2.4.22 kernel and the iptables feature i needed worked fine i then upgraded that system to 2.4.24 and the feature i needed still worked fine (i picked .24 because it's midway between .22 and .26) tomorrow i will install 2.4.25 and try that once i have found the major kernel release i will then need to track it in more detail and hopefully find a patch i can reverse out --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 |
From: John N. <jo...@mo...> - 2004-04-19 23:06:33
|
Ronald Pijnacker wrote: >On Mon, Apr 19, 2004 at 01:17:51PM -0400, Daniel R. Slater wrote: > > >>Very interesting, >> I wasn't aware you could do this - you learn something new evey day :). >>Would it be possible to use this method to dynamically change /etc/fstab >>during startup? i.e. you could have something like /etc/fstab.native, >>/etc/fstab.colinux and then early in your startup code have something like: >> >>rm /etc/fstab >> >>if [ x"$BOOTSYSTEM" == x"colinux"]; then >> ln -s /etc/fstab.colinux /etc/fstab >>else >> ln -s /etc/fstab.native /etc/fstab >>fi >> >>or does the linux startup process read /etc/fstab before executing any of >>it's startup scripts? >> >> > >In fact, I have written something like that. I use the "init=/root/preinit" >kernel parameter, where /root/preinit is a script that `fixes' things. >See attachment. If people find this useful, please add to the wiki. > >Comments are welcome. > >Ronald. > > A most excellent idea! Much superior to my approach, since you can effectively do everything all in one script, rather than relying on individual changes here and there throughout the system. This solution, although practical, does have one theoretical drawback: eventually we'll have fsck working again, and the fact that this approach requires us to modify the file system before checking it stinks a bit. We could duplicate the check, but that is redundant. The best long-term solution, IMHO, is to go with Sergey Okhapkin's suggestion (in this same thread) and find a way to make the colinux daemon "educate" the kernel at boot time that certain major/minor numbers devices are actually aliases for other ones (so, for example, we could make /dev/hdb1 and /dev/cobd2 become the same thing), but only when running in hosted -- not native -- mode. |
From: gboutwel <gbo...@pr...> - 2004-04-19 22:43:37
|
Attached are 2 files. 1 is an 'complete' build-colinux.sh, except that when I test it I get an error during the make of colinux-daemon.exe, having to do with unresolved externals. I've checked and I don't see why the unresolved externals should be happening. Anyways, maybe someone else can test and have success with the new build-colinux.sh... If anyone has an idea of what my unresolved external problem is that would be great. I'm attaching a bunch of make logs and ls outputs if you want to take a stab at it. HTH, George ------------------------------------------- Looking for Great Christian Shopping Ideas? http://www.praize.com/shopping/ |
From: Robert C. <rw...@al...> - 2004-04-19 22:11:34
|
On Monday, April 19, 2004, at 03:21 PM, Robert Citek wrote: > I hope to first figure out how to build it on Linux and then (maybe, > eventually) on Windows. See the example I've put on the wiki page > with how I've setup my build environment: > http://colinux.org/wiki/index.php/CygwinToolchain Finished creating the build environment and put my notes on the wiki. It contains a few tree drawings of the directory structure and a script that sets up the build environment on Linux. The next question is, how do I build colinux? That is, where should I put the colinux source code? Couldn't find any info on the wiki. Thanks in advance for any guidance. Regards, - Robert |
From: Daniel R. S. <dan...@ya...> - 2004-04-19 21:31:50
|
I have this successfully working using Win XP. What you need to do is share your LAN connection with the Win-TAP adapter. The DHCP server on your LAN shouldn't cause a problem because in this case, your LAN is the "internet" while your Win-TAP adapter is the LAN. FC1 will then get it's NAT'd IP address from the W2k box. -----Original Message----- From: col...@li... [mailto:col...@li...] On Behalf Of Robert Pang Sent: Monday, April 19, 2004 4:59 PM To: col...@li... Subject: [coLinux-devel] NAT routing HOWTO? Hi folks I have set up colinux 0.6.0 with Fedora Core 1 on Windows 2000 workstation. I am using Wincap driver and FC1 is obtaining its IP address via DHCP to the DHCP server in the LAN. The W2k has its static IP address. I have been thinking about somehow "sharing" the same static with FC1. I don't think real sharing is possible. Instead, I am thinking about doing a NAT translation in W2k to forward ports (e.g. ssh port 22) to FC1. I suspect that it should be possible with Windows 2000 Internet Connection Sharing (ICS) but I had no luck enabling ICS in W2k. I read in the net that ICS won't be possible if there is already a DHCP server in the LAN. Does anyone how about this? And assuming that I succeed in setting up ICS, how do I set up NAT to forward port 22 from W2k to FC1? Thanks. Rob ------------------------------------------------------- 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: Robert P. <rob...@ho...> - 2004-04-19 20:59:00
|
Hi folks I have set up colinux 0.6.0 with Fedora Core 1 on Windows 2000 workstation. I am using Wincap driver and FC1 is obtaining its IP address via DHCP to the DHCP server in the LAN. The W2k has its static IP address. I have been thinking about somehow "sharing" the same static with FC1. I don't think real sharing is possible. Instead, I am thinking about doing a NAT translation in W2k to forward ports (e.g. ssh port 22) to FC1. I suspect that it should be possible with Windows 2000 Internet Connection Sharing (ICS) but I had no luck enabling ICS in W2k. I read in the net that ICS won't be possible if there is already a DHCP server in the LAN. Does anyone how about this? And assuming that I succeed in setting up ICS, how do I set up NAT to forward port 22 from W2k to FC1? Thanks. Rob |
From: Tony H. <tm...@no...> - 2004-04-19 20:47:19
|
I've been having fun getting colinux to work on XP SP2 with AMD64. Generally it works... I have it stable with 256MB of RAM, but: 1. The XP SP2 firewall is a complete nazi so you'll have to do some fiddling to get ping/traceroute to work. (For some reason best known to Microsoft it opens the NetBIOS ports by default, but blocks most of the useful types of ping... the other way around would have made more sense to me, but whatever...) 2. I had to upgrade winpcap to 3.0 as the one that ships with colinux didn't work (3.1 doesn't work either but that's a beta so no surprise). 3. TAP-Win32 is nonfunctional (known bug - see http://groups.google.com/groups?threadm=4b2b7f04.0404121135.7a0b6b08%40posting.google.com) 4. On AMD64 the DEP (Data Execution Protection) just completely barfs colinux. I'm not really up on how it works, but AFAIK it puts the processor into PAE mode and enables the NX (No execute) bit on all allocated memory, and to execute within memory you have to change the protection. With DEP enabled the machine reboots just after reading the config file (doesn't bluescreen or anything, just falls over). You can put executables into an exception list but it looks like colinux operates at too low a level for the exceptions to operate. Tony |
From: Robert C. <rw...@al...> - 2004-04-19 20:22:01
|
On Monday, April 19, 2004, at 02:37 AM, Robert Citek wrote: > It seems as though these instructions are for building coLinux on > Linux. I hope to first figure out how to build it on Linux and then (maybe, eventually) on Windows. See the example I've put on the wiki page with how I've setup my build environment: http://colinux.org/wiki/index.php/CygwinToolchain It's not complete, but it is a start. My machine is slow and is still compiling. Thanks to all who've replied. Regards, - Robert |
From: Steven E. <ste...@ya...> - 2004-04-19 19:39:46
|
Hello, --- Matt Behrens <ma...@zi...> wrote: > Unless something has changed that I've missed, you can't yet build > on Windows. You currently cant build vmlinux but you should be able to build everything else. I think one of the ReactOS developers tested this. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25¢ http://photos.yahoo.com/ph/print_splash |
From: peter g. <plu...@p1...> - 2004-04-19 19:19:26
|
in order to make the tap work in the latest snapshot i have to load it by hand how come? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 |
From: Richard G. <ric...@ri...> - 2004-04-19 19:16:52
|
Of course, add the requisite space checks, and confirmations :-) Also, you may want to add an advanced button on the download step for proxy configuration (i THINK NSIS supports this..?). ----- Original Message ----- From: "peter green" <plu...@p1...> To: <col...@li...> Sent: Monday, April 19, 2004 2:02 PM Subject: [coLinux-devel] installer extraction and sparseness > i notice that the installer downloads the image but does not extract it i > presume this is because of incompleteness > > may i suggest that when you add image extraction you make it extract them > sparse to save hdd space > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 > > > > ------------------------------------------------------- > 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: peter g. <plu...@p1...> - 2004-04-19 19:02:35
|
i notice that the installer downloads the image but does not extract it i presume this is because of incompleteness may i suggest that when you add image extraction you make it extract them sparse to save hdd space --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.659 / Virus Database: 423 - Release Date: 15/04/2004 |