You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Henry N. <hen...@ar...> - 2009-06-05 08:15:20
|
KOU Hanjun wrote: > Is there a way to use a VMDK directly with coLinux? No. > VDI pre-allocates the disk space when creating the disk file, but VMDK > does it on demand which may save a lot of disk space for me. Use mkfile [1,2] and the sparse option "-s" to create a new empty image. Than copy all files from any pre-installated or running image to that image. See FAQ in the wiki28 [3] with a short step guide. [1] http://colinux.wikia.com/wiki/MkFile [2] http://www.henrynestler.com/colinux/tools/file-utils-mingw-bin-stripped.zip [3] http://colinux.wikia.com/wiki/FAQ#Q28._How_can_I_increase_the_size_of_a_coLinux_block_device_image.3F -- Henry N. |
From: KOU H. <han...@gm...> - 2009-06-05 04:03:51
|
Hi, Is there a way to use a VMDK directly with coLinux? VDI pre-allocates the disk space when creating the disk file, but VMDK does it on demand which may save a lot of disk space for me. |
From: Thomas S. <ste...@gm...> - 2009-05-23 18:36:16
|
On Mon, May 18, 2009 at 12:05 AM, Dave Coventry <dgc...@gm...> wrote: > Both these applications use Ubuntu and while Ubuntu is a great distro, > there are certainly a number of distros which are a lot lighter and > which run better on older machines. As a big fan of Ubuntu I would like to mention the lightweight variety Xubuntu. It needs just 128MB of RAM, and works well even on older machines, especially if you go for the 8.04 LTS version. 9.04 has some improvements, but is not quite as light. Changing an Ubuntu installation into Xubuntu is a very simple process. > I was > wondering how easy it would be to have a small linux distro like slax > that could be run off a USB key without installing. That would be quite nice indeed. Regards, Thomas |
From: <fr...@gm...> - 2009-05-22 14:41:25
|
Thanks Paolo! That fixed it. > Hi, > try this: > 1. execute "colinux-daemon --remove-driver" > 2. execute "colinux-daemon --install-driver" > 3. check the existence of example.conf file. > Now try to run your colinux box. > Bye, > Paolo > On Thu, May 21, 2009 at 11:06 PM, fREW Schmidt fr...@gm...> wrote: > > ok, sorry, had to do the obligatory dramatic title :-) > > > > Anyway, I tried to install coLinux on my Windows XP machine. And after > it > > finished downloading the image it seemed to just stop. After waiting 30 > min > > with no progress bar and no IO diff, I killed it. > > > > Anyway, I tried to run the daemon and got this error: > > > > C:\coLinux>colinux-daemon.exe @example.conf > > Cooperative Linux Daemon, 0.7.4 > > Daemon compiled on Wed Apr 15 18:59:08 2009 > > > > colinux: manager open: The system cannot find the file specified. > > daemon: exit code 82a7480e > > daemon: can't access CoLinuxDriver, please check status driver! > > > > So I figured I would uninstall it and reinstall it. But now when I try > to > > uninstall it gives errors about TAP-Win32. > > > > Any ideas of what I should do to get it to work? > > -- > > fREW Schmidt > > http://blog.afoolishmanifesto.com > > > > > ------------------------------------------------------------------------------ > > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > > is a gathering of tech-side developers & brand creativity professionals. > > Meet > > the minds behind Google Creative Lab, Visual Complexity, Processing, & > > iPhoneDevCamp asthey present alongside digital heavyweights like > Barbarian > > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > |
From: Paolo M. <pao...@gm...> - 2009-05-22 06:32:01
|
Hi, try this: 1. execute "colinux-daemon --remove-driver" 2. execute "colinux-daemon --install-driver" 3. check the existence of example.conf file. Now try to run your colinux box. Bye, Paolo On Thu, May 21, 2009 at 11:06 PM, fREW Schmidt <fr...@gm...> wrote: > ok, sorry, had to do the obligatory dramatic title :-) > > Anyway, I tried to install coLinux on my Windows XP machine. And after it > finished downloading the image it seemed to just stop. After waiting 30 min > with no progress bar and no IO diff, I killed it. > > Anyway, I tried to run the daemon and got this error: > > C:\coLinux>colinux-daemon.exe @example.conf > Cooperative Linux Daemon, 0.7.4 > Daemon compiled on Wed Apr 15 18:59:08 2009 > > colinux: manager open: The system cannot find the file specified. > daemon: exit code 82a7480e > daemon: can't access CoLinuxDriver, please check status driver! > > So I figured I would uninstall it and reinstall it. But now when I try to > uninstall it gives errors about TAP-Win32. > > Any ideas of what I should do to get it to work? > -- > fREW Schmidt > http://blog.afoolishmanifesto.com > > ------------------------------------------------------------------------------ > Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT > is a gathering of tech-side developers & brand creativity professionals. > Meet > the minds behind Google Creative Lab, Visual Complexity, Processing, & > iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian > Group, R/GA, & Big Spaceship. http://www.creativitycat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > |
From: fREW S. <fr...@gm...> - 2009-05-21 21:07:13
|
ok, sorry, had to do the obligatory dramatic title :-) Anyway, I tried to install coLinux on my Windows XP machine. And after it finished downloading the image it seemed to just stop. After waiting 30 min with no progress bar and no IO diff, I killed it. Anyway, I tried to run the daemon and got this error: C:\coLinux>colinux-daemon.exe @example.conf Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 colinux: manager open: The system cannot find the file specified. daemon: exit code 82a7480e daemon: can't access CoLinuxDriver, please check status driver! So I figured I would uninstall it and reinstall it. But now when I try to uninstall it gives errors about TAP-Win32. Any ideas of what I should do to get it to work? -- fREW Schmidt http://blog.afoolishmanifesto.com |
From: Dave C. <dgc...@gm...> - 2009-05-17 23:06:08
|
I see there are a couple of implementations of Colinux: andColinux :- http://www.andlinux.org/index.php and Portable Linux :- http://portableubuntu.demonccc.com.ar/ which allow linux to be run under Windows without actually installing Colinux and (As far as I can tell) or a TAP adapter. Therefore it can run off a USB key. Is this reasonably easy to implement? Both these applications use Ubuntu and while Ubuntu is a great distro, there are certainly a number of distros which are a lot lighter and which run better on older machines. I've been using Slax (slax.org) which is a Slackware derivative and which runs really nicely on an older machine I have, and I was wondering how easy it would be to have a small linux distro like slax that could be run off a USB key without installing. Regards, Dave Coventry |
From: Henry N. <hen...@ar...> - 2009-05-17 21:17:59
|
Johann Pascher wrote: > Plesase could somone explain or ponit to the coresponding information: > > The kernel moduls are not the same kernel version as the Ubunto 9.04. > or in Debian 5.0 > > I im usung the latest devel coLIUNX version. > > Shoud the kernal version of coLinux be the same as the kernel version > of the Linuxinstllation? > No. coLinux comes with a special Kernel version, currently it is 2.6.22.18-co-0.7.4. You needs to use the kernel and modules published with coLinux. Please unpack the modules from coLinux installation, for example: tar -xzf modules-2.6.22.18-co-0.7.4.tgz -C / The distribution have other version and no support for running under Windows. So, this you never can use under coLinux. Kernel version does not claim on a distribution, so you can mostly downgrade or upgrade the kernel. -- Henry N. |
From: Marwan Al-S. <ma...@co...> - 2009-05-16 18:52:54
|
you might want to try out Portable Ubuntu http://portableubuntu.demonccc.cloudius.com.ar it's an easy way to run Ubuntu Linux in Windows without too much difficulty and it runs on colinux. There are some nice screenshots of it running in the media section of the website. On Sat, May 16, 2009 at 4:45 PM, Gordon Stewart <gor...@gm...> wrote: > > Hi, > > I'm running WINXP, & want to install Ubuntu on my machine - running > via windows (at the same time)... > > >From the screen shots, CoLinux seems to be the tool I need (I've not > downloaded it yet...) > > Basically, the install instructions indicate, I need to use linux to > programme certian command lines to install it, & reading on network > etc.. & "Slirp" (& other complex commands to enter into the > console...) > > > I am *very* new to Linux (IE next to nothing knowledge )..... - But > am a fast learner. > > Q. Is there a tutorial on the MINIMUM process I need to install > Co-Linux without the "extras" ? > > Q. Is "Slirp" an extra ? & looking for "network" ?? > > Basically, i am just ONE PC running WinXP - No networked systems > > I'll assume the above are extras & not needed to run ?? > > (I'll assume i need to install ubuntu first - Then CoLinux > > > Thank you...... > > -- > G > Freecycle Auckland :- > http://www.freecycle.org/ > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
From: Gordon S. <gor...@gm...> - 2009-05-16 14:09:35
|
Hi, I'm running WINXP, & want to install Ubuntu on my machine - running via windows (at the same time)... >From the screen shots, CoLinux seems to be the tool I need (I've not downloaded it yet...) Basically, the install instructions indicate, I need to use linux to programme certian command lines to install it, & reading on network etc.. & "Slirp" (& other complex commands to enter into the console...) I am *very* new to Linux (IE next to nothing knowledge )..... - But am a fast learner. Q. Is there a tutorial on the MINIMUM process I need to install Co-Linux without the "extras" ? Q. Is "Slirp" an extra ? & looking for "network" ?? Basically, i am just ONE PC running WinXP - No networked systems I'll assume the above are extras & not needed to run ?? (I'll assume i need to install ubuntu first - Then CoLinux Thank you...... -- G Freecycle Auckland :- http://www.freecycle.org/ |
From: Johann P. <joh...@gm...> - 2009-05-16 07:35:41
|
Plesase could somone explain or ponit to the coresponding information: The kernel moduls are not the same kernel version as the Ubunto 9.04. or in Debian 5.0 I im usung the latest devel coLIUNX version. Shoud the kernal version of coLinux be the same as the kernel version of the Linuxinstllation? -- Mit freundlichen Grüßen, Johann Pascher |
From: Henry N. <hen...@ar...> - 2009-05-15 19:57:51
|
Cooperative Linux version 0.7.4 was released now. Release: 0.7.4 Kernel: 2.6.22.18 Build date: 15-April-2009 Lots of bugs are fixed. New device scsi for whole disk, faster kernel mode bridged network, cofs supports unix file attributes, variable size for boot console, and some small things more. Please check the project file release and wiki for information, updates and progress. Downloads: http://sourceforge.net/projects/colinux/files Changes: http://colinux.wikia.com/wiki/Version_0.7.4 Wiki: http://colinux.wikia.com Snapshots: http://www.colinux.org/snapshots ---- NEWS Filesystem: * New: cofs rename allows to overwrite files with ReadOnly attrib. * New: cofs supports flat file modes "rwx" for owner. Mount option "noattrib" disables these attribute mapping for older compatibility. * Use "setcobd=async" to enable asynchronous mode for cobd devices. * Bug #2013435: cobd supports read-only files now. * Bug #2152550: cofs atime and mtime was swapped on time set. * Bug #2176188: File sync wrong on cofs, command after mv/rename fails. Network: * pcap-bridge: Fix suspend problems. Reconnect after loosing adapter. * New network "ndis-bridge" works in kernel mode and is the faster alternative to pcap-bridge. (Ligong Liu) * Bug #1396539: Fixing the "eth0: duplicate address detected!". New filter rule for ndis-bridge and pcap-bridge is: "(ether dst MAC) or (multicast and not ether src MAC)" * Bug #2055697: Crashing SLiRP under heavy usage ktorrent. (Shai Vaingast) * Bug #2357494,#2365031: ndis-bridge was not working with PPPoE, AoE and others types as IP and ARP packets. Type filter removed now. Console and daemons: * New: Added "cocon=COLSxROWS" to use console size, other than 80x25. * Bug #1117788: Fix sticky ALT after system menu from ALT-Space. * Bug #2013501: Stop with error message on empty parameters. * Bug #2593186: FLTK console command prompt display problems. (Shai Vaingast) * Bugfix: Enclose spaces in current directory for install-service. Kernel: * scsi: New device for images with partition tables and works async. Usage "scsi0=disk,file.img" or "scsi1=cdrom,file.iso" (Steve Shoecraft) * Added virtual pci device handling. "lspci" is working (Steve Shoecraft) * Add PG_co_host_mapped, save many OS switching times: speed up coLinux. * New: /proc/colinux/stats show counts of OS switches. * unionfs-2.2.4 added as module. (Marwan Al-Sabbagh) * Add sysenter / sysexit restoration support, for cpu with SEP feature. * Bug #2524658: GPF on raid5/6 md array by accessing MMX/XMM-registers. * Feature req #2114493: Add iscsi kernel support (CONFIG_ISCSI_TCP). Installer: * New images: Fedora 10, Ubuntu 7.10 Debugging: * Enable host kernel debug via registry [HKLM\SOFTWARE\coLinux] "Debug" Updated libraries and tools: * mingw 3.14 * w32api 3.11 -- Henry N. |
From: David K. <da...@gi...> - 2009-05-10 05:55:29
|
Hi Mark, Mark Allums wrote: > Can we expect coLinux to run well under Windows 7? Perhaps under the > newly announced XP mode? I ran coLinux on Vista (with heavy, daily use) for several months before upgrading to System 7 beta and coLinux runs just fine on both for me. System 7 has had some seriously unpleasant issues with Samba clients though (blue screens, a hotfix, now system freezes) but these are not specific to coLinux -- they are affecting all System 7 users who try to mount Samba shares from any linux/bsd system. > Separate question: Is compatibility with 64-bit Vista possible? Now, > or in the future? I don't know -- I'm still limping along on just 32 bits -- but I'd like to know. I'd sure love to be able to run a 64 Windows with 8Gigs of ram and be able to give coLinux 4 of them! Henry? Why is it we can't give coLinux all the gigs of RAM it deserves, again? -dave |
From: Joe P. <joe...@gm...> - 2009-05-09 12:21:21
|
Joseph A. Pederson e-mail: joe...@gm... blog: http://averynight.blogspot.com/ phone: 920.574.2552 On Sat, May 9, 2009 at 7:03 AM, <col...@li... > wrote: > Send coLinux-users mailing list submissions to > col...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/colinux-users > or, via email, send a message with subject or body 'help' to > col...@li... > > You can reach the person managing the list at > col...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of coLinux-users digest..." > > > Today's Topics: > > 1. Re: Newer kernels ... (Fr?d?ric L. W. Meunier) > 2. Re: Newer kernels ... (Michael McStarfighter) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 8 May 2009 18:36:48 -0300 (BRST) > From: Fr?d?ric L. W. Meunier <lis...@pe...> > Subject: Re: [coLinux-users] Newer kernels ... > To: col...@li... > Message-ID: <alpine.LNX.2.00.0905081836110.1852@pervalidus> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > I think it's starting to get old, because 2.6.22 was released almost two > years ago (8 july 2007). > > But while 2.6.22 works fine for me, even using it with my Linux partition, > in the near future a recent kernel will be badly needed, because ext4 will > be the default filesystem on most distributions. > > Anyway, to the developers. Does the task to port coLinux to a new kernel > becomes way harder if you don't follow all releases ? I guess that if > 2.6.25 wasn't an easy task - > http://www.henrynestler.com/colinux/testing/kernel-2.6.25/ -, moving from > 2.6.22 to 2.6.29 would be much harder. > > On Thu, 7 May 2009, Paolo Minazzi wrote: > > Hi Micheal, > porting a new kernel is not an easy task. > We need some time to test a kernel version and the first releases > obviously will have bugs. > The actual configuration is very stable, so I think that for now > 2.6.22 is not old. > Bye, > Paolo > > > On Wed, May 6, 2009 at 3:28 PM, Michael McStarfighter wrote: > > A little question > > > > When will there be a newer kernel then the 2.6.22? Or are there any > reasons > > to do this not? > > > > Thanks for an answer ... > > > > > > Regards from Germany. > > > > ------------------------------ > > Message: 2 > Date: Sat, 9 May 2009 00:42:04 +0200 > From: Michael McStarfighter <mcs...@gm...> > Subject: Re: [coLinux-users] Newer kernels ... > To: col...@li... > Message-ID: > <66c...@ma...> > Content-Type: text/plain; charset="iso-8859-1" > > That was one of the resons I asked. New filesystems like ext4, brtfs, and > some other nice things ... And also some new distributions gets enough > errors because the actual colinux doesn't understand some calls and so one > ... These are only examples ... > > 2009/5/8 Fr?d?ric L. W. Meunier <lis...@pe...> > > > I think it's starting to get old, because 2.6.22 was released almost two > > years ago (8 july 2007). > > > > But while 2.6.22 works fine for me, even using it with my Linux > partition, > > in the near future a recent kernel will be badly needed, because ext4 > will > > be the default filesystem on most distributions. > > > > Anyway, to the developers. Does the task to port coLinux to a new kernel > > becomes way harder if you don't follow all releases ? I guess that if > > 2.6.25 wasn't an easy task - > > http://www.henrynestler.com/colinux/testing/kernel-2.6.25/ -, moving > from > > 2.6.22 to 2.6.29 would be much harder. > > > > On Thu, 7 May 2009, Paolo Minazzi wrote: > > > > Hi Micheal, > > porting a new kernel is not an easy task. > > We need some time to test a kernel version and the first releases > > obviously will have bugs. > > The actual configuration is very stable, so I think that for now > > 2.6.22 is not old. > > Bye, > > Paolo > > > > > > On Wed, May 6, 2009 at 3:28 PM, Michael McStarfighter wrote: > > > A little question > > > > > > When will there be a newer kernel then the 2.6.22? Or are there any > > reasons > > > to do this not? > > > > > > Thanks for an answer ... > > > > > > > > > Regards from Germany. > > > > > > > ------------------------------------------------------------------------------ > > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > > production scanning environment may not be a perfect world - but thanks > to > > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > > i700 > > Series Scanner you'll get full speed at 300 dpi even with all image > > processing features enabled. http://p.sf.net/sfu/kodak-com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > > ------------------------------ > > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > End of coLinux-users Digest, Vol 37, Issue 3 > ******************************************** > |
From: Michael M. <mcs...@gm...> - 2009-05-08 22:42:09
|
That was one of the resons I asked. New filesystems like ext4, brtfs, and some other nice things ... And also some new distributions gets enough errors because the actual colinux doesn't understand some calls and so one ... These are only examples ... 2009/5/8 Frédéric L. W. Meunier <lis...@pe...> > I think it's starting to get old, because 2.6.22 was released almost two > years ago (8 july 2007). > > But while 2.6.22 works fine for me, even using it with my Linux partition, > in the near future a recent kernel will be badly needed, because ext4 will > be the default filesystem on most distributions. > > Anyway, to the developers. Does the task to port coLinux to a new kernel > becomes way harder if you don't follow all releases ? I guess that if > 2.6.25 wasn't an easy task - > http://www.henrynestler.com/colinux/testing/kernel-2.6.25/ -, moving from > 2.6.22 to 2.6.29 would be much harder. > > On Thu, 7 May 2009, Paolo Minazzi wrote: > > Hi Micheal, > porting a new kernel is not an easy task. > We need some time to test a kernel version and the first releases > obviously will have bugs. > The actual configuration is very stable, so I think that for now > 2.6.22 is not old. > Bye, > Paolo > > > On Wed, May 6, 2009 at 3:28 PM, Michael McStarfighter wrote: > > A little question > > > > When will there be a newer kernel then the 2.6.22? Or are there any > reasons > > to do this not? > > > > Thanks for an answer ... > > > > > > Regards from Germany. > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
From: Frédéric L. W. M. <lis...@pe...> - 2009-05-08 21:37:18
|
I think it's starting to get old, because 2.6.22 was released almost two years ago (8 july 2007). But while 2.6.22 works fine for me, even using it with my Linux partition, in the near future a recent kernel will be badly needed, because ext4 will be the default filesystem on most distributions. Anyway, to the developers. Does the task to port coLinux to a new kernel becomes way harder if you don't follow all releases ? I guess that if 2.6.25 wasn't an easy task - http://www.henrynestler.com/colinux/testing/kernel-2.6.25/ -, moving from 2.6.22 to 2.6.29 would be much harder. On Thu, 7 May 2009, Paolo Minazzi wrote: Hi Micheal, porting a new kernel is not an easy task. We need some time to test a kernel version and the first releases obviously will have bugs. The actual configuration is very stable, so I think that for now 2.6.22 is not old. Bye, Paolo On Wed, May 6, 2009 at 3:28 PM, Michael McStarfighter wrote: > A little question > > When will there be a newer kernel then the 2.6.22? Or are there any reasons > to do this not? > > Thanks for an answer ... > > > Regards from Germany. |
From: Paolo M. <pao...@gm...> - 2009-05-07 06:31:34
|
Hi Micheal, porting a new kernel is not an easy task. We need some time to test a kernel version and the first releases obviously will have bugs. The actual configuration is very stable, so I think that for now 2.6.22 is not old. Bye, Paolo On Wed, May 6, 2009 at 3:28 PM, Michael McStarfighter <mcs...@gm...> wrote: > A little question > > When will there be a newer kernel then the 2.6.22? Or are there any reasons > to do this not? > > Thanks for an answer ... > > > Regards from Germany. |
From: Michael M. <mcs...@gm...> - 2009-05-06 13:28:31
|
A little question When will there be a newer kernel then the 2.6.22? Or are there any reasons to do this not? Thanks for an answer ... Regards from Germany. |
From: Mark A. <ma...@al...> - 2009-05-03 18:32:36
|
Can we expect coLinux to run well under Windows 7? Perhaps under the newly announced XP mode? Separate question: Is compatibility with 64-bit Vista possible? Now, or in the future? I am running coLinux as Portable Ubuntu under less than ideal conditions. A 64-bit port would be dandy. I would contribute, but I know nothing about linux kernels or any kind of device driver, and not much about programming 64-bit (specifics). Mark Allums |
From: Christopher D. C. <ccl...@ac...> - 2009-04-30 01:10:03
|
GuyBrush <guy...@gm...> wrote: > According to Microsoft, Windows Server 2008 Enterprise 32-bit, > supports up to 64 GB of ram. > http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_server_2008 > Would Colinux work with it? > Has anyone tried this? If one had such a machine, why would they install the 32-bit OS? Why would they not just install the 64-bit OS and run Hyper-V and run Linux in a VM where it would be significantly less likely to crash the system. (This assumes that any system that could support that much RAM also had the VT processor support to run HyperV.) Also, I believe it was mentioned that coLinux itself has a hard limit of around 1GB of memory. (I think this is a limitation upon how large a contiguous chunk of memory can be allocated by a kernel-level process on the 32-bit OS where the kernel itsel can only address 2GB and windows itself obviously needs some memory.) I'm not authoritative on these statements though... <<CDC -- Christopher D. Clausen |
From: GuyBrush <guy...@gm...> - 2009-04-29 15:39:07
|
According to Microsoft, Windows Server 2008 Enterprise 32-bit, supports up to 64 GB of ram. http://msdn.microsoft.com/en-us/library/aa366778.aspx#physical_memory_limits_windows_server_2008 Would Colinux work with it? Has anyone tried this? Thanks. |
From: Henry N. <hen...@ar...> - 2009-04-24 19:52:20
|
Frank Church wrote: > Can 0.73, 0.74 and 0.80 coexist on the same system. No, not at same time. You can install it in different directories. To switch between these versions needs to change into the directory and run these two commands: colinux-daemon.exe --remove-driver colinux-daemon.exe --install-driver Switching between 0.8.x and 0.7.4 you not need. Both are exactly the same code with an other version number only. -- Henry N. |
From: Louis <net...@ya...> - 2009-04-24 17:11:03
|
Well, my CoLinux setup is minimalist, I boot into it, mount the Ubuntu partition that the computer can also dual-boot into (/dev/sda7) and chroot into it and then run the programs I have there. Reading about 9.04, I feel like upgrading, but I'm wondering if that Ubuntu will run using the old 2.6.12 kernel which I have in my disk image (Debian-3.0r2.ext3-mit-backports). I suppose I should be asking this in the Ubuntu forums, but perhaps someone's got experience? Thanks, Louis |
From: Frank C. <vfc...@go...> - 2009-04-24 16:48:58
|
2009/4/22 Henry Nestler <hen...@ar...>: > Am 22.04.2009 21:33, schrieb Frank Church: >> >> Is it possible to install setup a Linux distribution from CD ROM? >> >> I have an Ubuntu 7.10 coLinux setup, and I want to create new Ubuntu >> 8.04 and 8.10 from ISO images. >> >> Is it possible to mount the CDROMs and install them, or use some kind >> of debootstrap system which >> can install from a local FTP created from loop mounted ISO? >> >> What I mean is if the coLinux cannot install an image from the CDROM, >> is it possible to extract >> debootstrap from the ISO image, and use it to install the rest of the >> files from the ISO image mounted >> as an FTP location? > > Here is an interesing stepguide for CentOS bootstrapping: > http://blog.gbraad.nl/2009/03/manually-installing-centos-52-on.html > > In wiki http://colinux.wikia.com/wiki/UbuntuBase exist a very old script. > Perhaps it is very outdated? > > Newer coLinux version 0.7.4-rc2 has an option for cdrom, like this: > scsi1=cdrom,C:\image.iso > or > scsi1=cdrom,\Device\Cdrom0 > > Please read also comments from Bill about Fedora here: > http://tinyurl.com/cnovnz > And my answers: http://tinyurl.com/csw9nr, http://tinyurl.com/cr9ene > > -- > Henry N. > The http://colinux.wikia.com/wiki/UbuntuBase worked okay for me, but I had to make some adjustments do install from a file://cdrom/Ubuntu. I am yet to try the Centos one, but that is my preferred server distro. Can 0.73, 0.74 and 0.80 coexist on the same system. Thanks |
From: Henry N. <hen...@ar...> - 2009-04-22 22:13:11
|
Hello Frank, Frank Church wrote: > On 20/04/2009, Henry Nestler<hen...@ar...> wrote: >> ColdShine wrote: >> >>> Henry Nestler wrote: >> >> Frank Church wrote: >> >>> Is there a way to set the title of the console in the colinux.conf >> >>> file i the command options. >> >> no, you can't. The title line will be update from console depends on the >> >> current state (attached or detached). >> > >> > I'd like that to be implemented, too. I think it could be set using a >> > special sequence for PS1, like you do in Xterm. I think >> > colinux-console already has a parser for the escape sequences, right? >> >> >> coLinux use the kernel "struct consw" in same way all other video >> drivers used it (frame less graphic cards). There is no option for >> title, as I known. Xterm uses other ways and more subfunctions. >> >> To add a title to coLinux console, needs to change directly in the user >> land console programs on host side. >> >> >> -- >> Henry N. >> > >>> To add a title to coLinux console, needs to change directly in the user >>> land console programs on host side. > > Could that be done from the command line or with a Windows utility? > No. coLinux console is changed the title line after starting the colinux-console-nt.exe or colinux-console-fltk.exe. You can set the titly by windows and disable the console spawning and than run colinux console from explorer or from other command prompt. Than you would have a title line, but only for the colinux-daemon, not for the console. C:\> title "your text" C:\> colinux-daemon -d ... open second prompt C:\> colinux-console-nt.exe -- Henry N. |