Menu
▾
▴
colinux-users — coLinux users mailing list
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: Thierry L. <tl...@ya...> - 2004-07-01 22:15:57
|
In the meantime I saw another post in dev list mentionning same problem as me. I tried recent snapshot as suggested (coLinux-20040620.exe) and it works! :) Thanks anyway for your help. It makes me look more carefully on the devel mailing list :) Guy Gascoigne - Piggford wrote: > Actually I still think that this might be the same problem. > > You need to edit you config.xml file (whatever you've called yours), > add the init=/bin/bash option to the bootparams section. > > I don't have access to the box that I fixed this on right now so I'm > working from memory, anyway, IIRC I ended out looking at the archives > (there's a link on the colinux page) of the dev mailing list, and > someone else mentioned simply editing the fstab file to point to the > right device. I did try the link method, but found that the link > didn't persist over a reboot on my setup. > > Guy > > Thierry Legras wrote: > >> Mmm, not sure i have the same problem. In my case I can't even boot. >> So i have no way to launch any command like ln or something else. Did >> i missed something? >> >> I just tried official coLinux-0.6.1.exe with either default debian or >> gentoo distrib out of the box. >> >> Thierry. >> >> Guy Gascoigne-Piggford wrote: >> >>> Take a look at the colinux-devel list archives, this has come up >>> there, but not on this list. Anyway, the message that gave me the >>> hint I needed to get working was: >>> >>> From: colinux-devel-admin@li... >>> [mailto:colinux-devel-admin@li...]On Behalf Of Peng Li >>> Sent: dinsdag 22 juni 2004 17:59 >>> To: colinux-devel@li... >>> Subject: [coLinux-devel] RE: bad superblock error when using snapshot >>> 20040620 >>> >>> >>> The problem is that fsck cannot find /dev/cobd0 >>> or something.... here is a quick fix: >>> >>> Boot with the option init=/bin/bash >>> >>> cd /dev >>> ln -sf cobd/0 cobd0 >>> >>> reboot >>> >>> >>> Hope that it sets you looking in the right direction. >>> >>> Guy >>> >>> >>> Thierry Legras wrote: >>> >>>> Hi, >>>> >>>> I tried coLinux with both Debian and Gentoo and i always get this >>>> error at startup: >>>> > FAT: bogus logical sector size 56932 >>>> >>>> Then after few consecutive errors, colinux shuts down. >>>> >>>> coLinux is installed on an NTFS partition. Maybe NTFS is not >>>> supported? >>>> Any ideas? >>>> >>>> Thierry. >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------- >>>> This SF.Net email sponsored by Black Hat Briefings & Training. >>>> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>> digital self defense, top technical experts, no vendor pitches, >>>> unmatched networking opportunities. Visit www.blackhat.com >>>> _______________________________________________ >>>> coLinux-users mailing list >>>> coL...@li... >>>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>>> . >>>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email sponsored by Black Hat Briefings & Training. >>> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>> digital self defense, top technical experts, no vendor pitches, >>> unmatched networking opportunities. Visit www.blackhat.com >>> _______________________________________________ >>> coLinux-users mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>> >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email sponsored by Black Hat Briefings & Training. >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital >> self defense, top technical experts, no vendor pitches, unmatched >> networking opportunities. Visit www.blackhat.com >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> >> > |
|
From: Guy G. - P. <gu...@wy...> - 2004-07-01 21:38:29
|
Actually I still think that this might be the same problem. You need to edit you config.xml file (whatever you've called yours), add the init=/bin/bash option to the bootparams section. I don't have access to the box that I fixed this on right now so I'm working from memory, anyway, IIRC I ended out looking at the archives (there's a link on the colinux page) of the dev mailing list, and someone else mentioned simply editing the fstab file to point to the right device. I did try the link method, but found that the link didn't persist over a reboot on my setup. Guy Thierry Legras wrote: > Mmm, not sure i have the same problem. In my case I can't even boot. > So i have no way to launch any command like ln or something else. Did > i missed something? > > I just tried official coLinux-0.6.1.exe with either default debian or > gentoo distrib out of the box. > > Thierry. > > Guy Gascoigne-Piggford wrote: > >> Take a look at the colinux-devel list archives, this has come up >> there, but not on this list. Anyway, the message that gave me the >> hint I needed to get working was: >> >> From: colinux-devel-admin@li... >> [mailto:colinux-devel-admin@li...]On Behalf Of Peng Li >> Sent: dinsdag 22 juni 2004 17:59 >> To: colinux-devel@li... >> Subject: [coLinux-devel] RE: bad superblock error when using snapshot >> 20040620 >> >> >> The problem is that fsck cannot find /dev/cobd0 >> or something.... here is a quick fix: >> >> Boot with the option init=/bin/bash >> >> cd /dev >> ln -sf cobd/0 cobd0 >> >> reboot >> >> >> Hope that it sets you looking in the right direction. >> >> Guy >> >> >> Thierry Legras wrote: >> >>> Hi, >>> >>> I tried coLinux with both Debian and Gentoo and i always get this >>> error at startup: >>> > FAT: bogus logical sector size 56932 >>> >>> Then after few consecutive errors, colinux shuts down. >>> >>> coLinux is installed on an NTFS partition. Maybe NTFS is not supported? >>> Any ideas? >>> >>> Thierry. >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email sponsored by Black Hat Briefings & Training. >>> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>> digital self defense, top technical experts, no vendor pitches, >>> unmatched networking opportunities. Visit www.blackhat.com >>> _______________________________________________ >>> coLinux-users mailing list >>> coL...@li... >>> https://lists.sourceforge.net/lists/listinfo/colinux-users >>> . >>> >> >> >> ------------------------------------------------------- >> This SF.Net email sponsored by Black Hat Briefings & Training. >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital >> self defense, top technical experts, no vendor pitches, unmatched >> networking opportunities. Visit www.blackhat.com >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
|
From: Peng <rin...@gm...> - 2004-07-01 21:30:25
|
I once attempted to do some hack with the "init=" boot option to make colinux boot with a different init script. But it turns out that colinux is running so well that I never needed to boot my "real" linux again... so I haven't actually tried it yet :P On Fri, 2 Jul 2004 01:03:59 +0800, Samir Kuthiala <sam...@gm...> wrote: > > Hi > > Thanks for all the suggestions. I finally got it to work... sort of. > basically in short I had to remove allr eferences in /etc/fstab to > /dev/*. Also I had to enable fastboot in /etc/rc.d/rc/sysinit > > There are still some errors regarding some fonts, inability to load > usb drivers and at every bootup my system keeps prompting me to change > hardware config etc. but the system as such is working fine. I am able > to connect to an external Xserver and run my programs. > > However I had to modify my fstab quite a bit to make my dual boot > work. (to a point where I am unable to load linux normally :( > > Does anyone know of a way to switch fstabs depending on which kernel > is loaded? or maybe another mechanism to handle device differences > between different bootup sequences. > > Thanks > Samir > > > > > On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote: > > > > I am pretty sure that the problem is caused by fsck attempting to > > access /dev/hda3. Try to find out where this hda3 comes from, and > > change it to /dev/cobd0. > > > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala > > > > <sam...@gm...> wrote: > > > > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i > > > tried doing cat /etc/mtab and the partition which is mounted is > > > /dev/hda3 > > > > > > > > > > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote: > > > > > > > > Oops. Try the following: > > > > > > > > give root password and enter the "repair fs" shell > > > > > > > > ls -l /dev/cobd0 > > > > > > > > see if that device exists.... sometime devfs put that device into /dev/cobd/0 > > > > if that's the case, you can either modify fstab or create a symbolic link from > > > > /dev/cobd0 --> /dev/cobd/0 > > > > > > > > let me know if it works... > > > > > > > > -- Peng > > > > > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala > > > > > > > > <sam...@gm...> wrote: > > > > > > > > > > I have already tried that. no difference. It stops at loading the root > > > > > partition which is pretty funny considering that afterwards it throws > > > > > me into the "Repair Filesystem" shell. And I can see the entire linux > > > > > partition and browse through it from within co-linux. > > > > > > > > > > > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > > > > > > > > > Try: > > > > > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" > > > > > > /> > > > > > > > > > > > > And disable your swap partition. Once the basic system works you can keep going > > > > > > and add the swap thing... > > > > > > > > > > > > Good luck, > > > > > > > > > > > > Peng > > > > > > > > > > > > > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > > > > > <sam...@gm...> wrote: > > > > > > > > > > > > > > Hi > > > > > > > > > > > > > > I have been trying to get the colinux to work on my dual boot system > > > > > > > (win2k pro + RH9) for the last few days but with no success. heres a > > > > > > > summary of what I have done so far > > > > > > > > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > > > > > > > modified the config file to this... > > > > > > > =============================================== > > > > > > > <colinux> > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > > > > > > > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > <image path="vmlinux" /> > > > > > > > <memory size="64" /> > > > > > > > <network index="0" type="tap" name="tap" /> > > > > > > > </colinux> > > > > > > > =============================================== > > > > > > > 3. copied the kernel modules packaged along with colinux into the > > > > > > > /lib/modules dir > > > > > > > > > > > > > > I then tried to boot the colinux. failed with some error about unable > > > > > > > to locate /dev/hda3 (thats my root partition). I assumed this was due > > > > > > > to me not having modified fstab. I then modified fstab to remove all > > > > > > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > > > > > > /dev/cobd1 as swap. However the bootup sequence still fails with some > > > > > > > error message about invalid superblock. > > > > > > > > > > > > > > I have gone through the website/forums/wiki and am just about to give > > > > > > > up. Can somebody help me figure out whats going wrong? > > > > > > > > > > > > > > Thanks > > > > > > > Samir > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > > > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > > > > > digital self defense, top technical experts, no vendor pitches, > > > > > > > unmatched networking opportunities. Visit www.blackhat.com > > > > > > > _______________________________________________ > > > > > > > coLinux-users mailing list > > > > > > > coL...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > > > > > > > > > > > > > > > > > > > > > > > |
|
From: Thierry L. <tl...@ya...> - 2004-07-01 21:22:09
|
Mmm, not sure i have the same problem. In my case I can't even boot. So i have no way to launch any command like ln or something else. Did i missed something? I just tried official coLinux-0.6.1.exe with either default debian or gentoo distrib out of the box. Thierry. Guy Gascoigne-Piggford wrote: > Take a look at the colinux-devel list archives, this has come up > there, but not on this list. Anyway, the message that gave me the > hint I needed to get working was: > > From: colinux-devel-admin@li... > [mailto:colinux-devel-admin@li...]On Behalf Of Peng Li > Sent: dinsdag 22 juni 2004 17:59 > To: colinux-devel@li... > Subject: [coLinux-devel] RE: bad superblock error when using snapshot > 20040620 > > > The problem is that fsck cannot find /dev/cobd0 > or something.... here is a quick fix: > > Boot with the option init=/bin/bash > > cd /dev > ln -sf cobd/0 cobd0 > > reboot > > > Hope that it sets you looking in the right direction. > > Guy > > > Thierry Legras wrote: > >> Hi, >> >> I tried coLinux with both Debian and Gentoo and i always get this >> error at startup: >> > FAT: bogus logical sector size 56932 >> >> Then after few consecutive errors, colinux shuts down. >> >> coLinux is installed on an NTFS partition. Maybe NTFS is not supported? >> Any ideas? >> >> Thierry. >> >> >> >> >> ------------------------------------------------------- >> This SF.Net email sponsored by Black Hat Briefings & Training. >> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital >> self defense, top technical experts, no vendor pitches, unmatched >> networking opportunities. Visit www.blackhat.com >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> . >> > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Patrick W. <pa...@im...> - 2004-07-01 17:40:05
|
I ran into similar probelms with Win2000, colinux 0.6.0 and RH EL3.. tracked it down to the size of the physical partition being reported to colinux as 0. The zero size causes fsck of root to fail (even through the blocks can actually be accessed), which causes the boot to fail. I think the physical partition size reporting problem has been fixed in later versions. Fastboot skips the fsck on root, so that's probably why it makes things work. This solution would worry me because if the root partition ever gets corrupted, you'll never be able to fix it without booting natively. Might be worthwhile upgrading to a version with the physical partition size reporting fix. later, patbob On Thursday 01 July 2004 5:03 pm, Samir Kuthiala wrote: > Hi > > Thanks for all the suggestions. I finally got it to work... sort of. > basically in short I had to remove allr eferences in /etc/fstab to > /dev/*. Also I had to enable fastboot in /etc/rc.d/rc/sysinit > > There are still some errors regarding some fonts, inability to load > usb drivers and at every bootup my system keeps prompting me to change > hardware config etc. but the system as such is working fine. I am able > to connect to an external Xserver and run my programs. > > However I had to modify my fstab quite a bit to make my dual boot > work. (to a point where I am unable to load linux normally :( > > Does anyone know of a way to switch fstabs depending on which kernel > is loaded? or maybe another mechanism to handle device differences > between different bootup sequences. > > Thanks > Samir > > On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote: > > I am pretty sure that the problem is caused by fsck attempting to > > access /dev/hda3. Try to find out where this hda3 comes from, and > > change it to /dev/cobd0. > > > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala > > > > <sam...@gm...> wrote: > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i > > > tried doing cat /etc/mtab and the partition which is mounted is > > > /dev/hda3 > > > > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote: > > > > Oops. Try the following: > > > > > > > > give root password and enter the "repair fs" shell > > > > > > > > ls -l /dev/cobd0 > > > > > > > > see if that device exists.... sometime devfs put that device into > > > > /dev/cobd/0 if that's the case, you can either modify fstab or create > > > > a symbolic link from /dev/cobd0 --> /dev/cobd/0 > > > > > > > > let me know if it works... > > > > > > > > -- Peng > > > > > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala > > > > > > > > <sam...@gm...> wrote: > > > > > I have already tried that. no difference. It stops at loading the > > > > > root partition which is pretty funny considering that afterwards it > > > > > throws me into the "Repair Filesystem" shell. And I can see the > > > > > entire linux partition and browse through it from within co-linux. > > > > > > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > > > Try: > > > > > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" > > > > > > enabled="true" /> > > > > > > > > > > > > And disable your swap partition. Once the basic system works you > > > > > > can keep going and add the swap thing... > > > > > > > > > > > > Good luck, > > > > > > > > > > > > Peng > > > > > > > > > > > > > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > > > > > > > > > > > <sam...@gm...> wrote: > > > > > > > Hi > > > > > > > > > > > > > > I have been trying to get the colinux to work on my dual boot > > > > > > > system (win2k pro + RH9) for the last few days but with no > > > > > > > success. heres a summary of what I have done so far > > > > > > > > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo > > > > > > > image. modified the config file to this... > > > > > > > =============================================== > > > > > > > <colinux> > > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" > > > > > > > enabled="true" /> <block_device index="1" > > > > > > > path="\Device\HarddiskVolume3" enabled="true" /> > > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > > <image path="vmlinux" /> > > > > > > > <memory size="64" /> > > > > > > > <network index="0" type="tap" name="tap" /> > > > > > > > </colinux> > > > > > > > =============================================== > > > > > > > 3. copied the kernel modules packaged along with colinux into > > > > > > > the /lib/modules dir > > > > > > > > > > > > > > I then tried to boot the colinux. failed with some error about > > > > > > > unable to locate /dev/hda3 (thats my root partition). I assumed > > > > > > > this was due to me not having modified fstab. I then modified > > > > > > > fstab to remove all references to /dev/hd* and added in > > > > > > > /dev/cobd0 (as root) and /dev/cobd1 as swap. However the bootup > > > > > > > sequence still fails with some error message about invalid > > > > > > > superblock. > > > > > > > > > > > > > > I have gone through the website/forums/wiki and am just about > > > > > > > to give up. Can somebody help me figure out whats going wrong? > > > > > > > > > > > > > > Thanks > > > > > > > Samir > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > > > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > > > > > digital self defense, top technical experts, no vendor pitches, > > > > > > > unmatched networking opportunities. Visit www.blackhat.com > > > > > > > _______________________________________________ > > > > > > > coLinux-users mailing list > > > > > > > coL...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Samir K. <sam...@gm...> - 2004-07-01 17:04:02
|
Hi Thanks for all the suggestions. I finally got it to work... sort of. basically in short I had to remove allr eferences in /etc/fstab to /dev/*. Also I had to enable fastboot in /etc/rc.d/rc/sysinit There are still some errors regarding some fonts, inability to load usb drivers and at every bootup my system keeps prompting me to change hardware config etc. but the system as such is working fine. I am able to connect to an external Xserver and run my programs. However I had to modify my fstab quite a bit to make my dual boot work. (to a point where I am unable to load linux normally :( Does anyone know of a way to switch fstabs depending on which kernel is loaded? or maybe another mechanism to handle device differences between different bootup sequences. Thanks Samir On Thu, 1 Jul 2004 06:41:59 -0400, Peng <rin...@gm...> wrote: > > I am pretty sure that the problem is caused by fsck attempting to > access /dev/hda3. Try to find out where this hda3 comes from, and > change it to /dev/cobd0. > > On Thu, 1 Jul 2004 18:33:15 +0800, Samir Kuthiala > > <sam...@gm...> wrote: > > > > tried both /dev/cobd0 and /dev/cobd/0. no change. in the repair fs i > > tried doing cat /etc/mtab and the partition which is mounted is > > /dev/hda3 > > > > > > > > On Thu, 1 Jul 2004 05:55:36 -0400, Peng <rin...@gm...> wrote: > > > > > > Oops. Try the following: > > > > > > give root password and enter the "repair fs" shell > > > > > > ls -l /dev/cobd0 > > > > > > see if that device exists.... sometime devfs put that device into /dev/cobd/0 > > > if that's the case, you can either modify fstab or create a symbolic link from > > > /dev/cobd0 --> /dev/cobd/0 > > > > > > let me know if it works... > > > > > > -- Peng > > > > > > On Thu, 1 Jul 2004 17:51:19 +0800, Samir Kuthiala > > > > > > <sam...@gm...> wrote: > > > > > > > > I have already tried that. no difference. It stops at loading the root > > > > partition which is pretty funny considering that afterwards it throws > > > > me into the "Repair Filesystem" shell. And I can see the entire linux > > > > partition and browse through it from within co-linux. > > > > > > > > > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > > > > > > > Try: > > > > > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" > > > > > /> > > > > > > > > > > And disable your swap partition. Once the basic system works you can keep going > > > > > and add the swap thing... > > > > > > > > > > Good luck, > > > > > > > > > > Peng > > > > > > > > > > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > > > > <sam...@gm...> wrote: > > > > > > > > > > > > Hi > > > > > > > > > > > > I have been trying to get the colinux to work on my dual boot system > > > > > > (win2k pro + RH9) for the last few days but with no success. heres a > > > > > > summary of what I have done so far > > > > > > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > > > > > > modified the config file to this... > > > > > > =============================================== > > > > > > <colinux> > > > > > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > > > > > > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > > > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > > > <image path="vmlinux" /> > > > > > > <memory size="64" /> > > > > > > <network index="0" type="tap" name="tap" /> > > > > > > </colinux> > > > > > > =============================================== > > > > > > 3. copied the kernel modules packaged along with colinux into the > > > > > > /lib/modules dir > > > > > > > > > > > > I then tried to boot the colinux. failed with some error about unable > > > > > > to locate /dev/hda3 (thats my root partition). I assumed this was due > > > > > > to me not having modified fstab. I then modified fstab to remove all > > > > > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > > > > > /dev/cobd1 as swap. However the bootup sequence still fails with some > > > > > > error message about invalid superblock. > > > > > > > > > > > > I have gone through the website/forums/wiki and am just about to give > > > > > > up. Can somebody help me figure out whats going wrong? > > > > > > > > > > > > Thanks > > > > > > Samir > > > > > > > > > > > > ------------------------------------------------------- > > > > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > > > > digital self defense, top technical experts, no vendor pitches, > > > > > > unmatched networking opportunities. Visit www.blackhat.com > > > > > > _______________________________________________ > > > > > > coLinux-users mailing list > > > > > > coL...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > > > > > > > > > > > > > > > > |
|
From: Samir K. <sam...@gm...> - 2004-07-01 11:23:36
|
hmm the wiki does have some instructions to convert a linux install to colinux. i have followed all the steps on it so far. On Thu, 1 Jul 2004 12:37:39 +0200, Leeuw van der, Tim <tim...@nl...> wrote: > > If you're using 0.6.1, then your boot-device would be /dev/cobd, no matter what distribution. > Is your distro using devfs? > > I don't know what else should be done to an existing linux installation to convert it to a coLinux install, what instructions are there on the wiki for converting a linux install to coLinux? > > --Tim > > > > -----Original Message----- > From: Samir Kuthiala [mailto:sam...@gm...] > Sent: donderdag 1 juli 2004 12:34 > To: Leeuw van der, Tim > Cc: Peng; col...@li... > Subject: Re: [coLinux-users] help setting up a dual boot system > > coLinux 0.6.1. > hmm I am not sure which is my boot device. I have tried creating both. > but no difference. > > On Thu, 1 Jul 2004 12:03:55 +0200, Leeuw van der, Tim > <tim...@nl...> wrote: > > > > Which version of coLinux are you using, actually? 0.6.1, or the later snapshots? Is your boot-device /dev/cobd0, or /dev/cobd/0 ? > > > > --Tim > > > > > > > > -----Original Message----- > > From: col...@li... > > [mailto:col...@li...]On Behalf Of Samir > > Kuthiala > > Sent: donderdag 1 juli 2004 11:51 > > To: Peng > > Cc: col...@li... > > Subject: Re: [coLinux-users] help setting up a dual boot system > > > > I have already tried that. no difference. It stops at loading the root > > partition which is pretty funny considering that afterwards it throws > > me into the "Repair Filesystem" shell. And I can see the entire linux > > partition and browse through it from within co-linux. > > > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > > > Try: > > > > > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" > > > /> > > > > > > And disable your swap partition. Once the basic system works you can keep going > > > and add the swap thing... > > > > > > Good luck, > > > > > > Peng > > > > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > > <sam...@gm...> wrote: > > > > > > > > Hi > > > > > > > > I have been trying to get the colinux to work on my dual boot system > > > > (win2k pro + RH9) for the last few days but with no success. heres a > > > > summary of what I have done so far > > > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > > > > modified the config file to this... > > > > =============================================== > > > > <colinux> > > > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > > > > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > > > > <bootparams>root=/dev/cobd0</bootparams> > > > > <image path="vmlinux" /> > > > > <memory size="64" /> > > > > <network index="0" type="tap" name="tap" /> > > > > </colinux> > > > > =============================================== > > > > 3. copied the kernel modules packaged along with colinux into the > > > > /lib/modules dir > > > > > > > > I then tried to boot the colinux. failed with some error about unable > > > > to locate /dev/hda3 (thats my root partition). I assumed this was due > > > > to me not having modified fstab. I then modified fstab to remove all > > > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > > > /dev/cobd1 as swap. However the bootup sequence still fails with some > > > > error message about invalid superblock. > > > > > > > > I have gone through the website/forums/wiki and am just about to give > > > > up. Can somebody help me figure out whats going wrong? > > > > > > > > Thanks > > > > Samir > > > > > > > > ------------------------------------------------------- > > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > > digital self defense, top technical experts, no vendor pitches, > > > > unmatched networking opportunities. Visit www.blackhat.com > > > > _______________________________________________ > > > > coLinux-users mailing list > > > > coL...@li... > > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-07-01 10:37:51
|
If you're using 0.6.1, then your boot-device would be /dev/cobd, no = matter what distribution. Is your distro using devfs? I don't know what else should be done to an existing linux installation = to convert it to a coLinux install, what instructions are there on the = wiki for converting a linux install to coLinux? --Tim -----Original Message----- From: Samir Kuthiala [mailto:sam...@gm...] Sent: donderdag 1 juli 2004 12:34 To: Leeuw van der, Tim Cc: Peng; col...@li... Subject: Re: [coLinux-users] help setting up a dual boot system coLinux 0.6.1. hmm I am not sure which is my boot device. I have tried creating both. but no difference. On Thu, 1 Jul 2004 12:03:55 +0200, Leeuw van der, Tim <tim...@nl...> wrote: >=20 > Which version of coLinux are you using, actually? 0.6.1, or the later = snapshots? Is your boot-device /dev/cobd0, or /dev/cobd/0 ? >=20 > --Tim >=20 >=20 >=20 > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On Behalf Of Samir > Kuthiala > Sent: donderdag 1 juli 2004 11:51 > To: Peng > Cc: col...@li... > Subject: Re: [coLinux-users] help setting up a dual boot system >=20 > I have already tried that. no difference. It stops at loading the root > partition which is pretty funny considering that afterwards it throws > me into the "Repair Filesystem" shell. And I can see the entire linux > partition and browse through it from within co-linux. >=20 > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > Try: > > > > <block_device index=3D"0" path=3D"\Device\HarddiskVolume3" = enabled=3D"true" > > /> > > > > And disable your swap partition. Once the basic system works you = can keep going > > and add the swap thing... > > > > Good luck, > > > > Peng > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > <sam...@gm...> wrote: > > > > > > Hi > > > > > > I have been trying to get the colinux to work on my dual boot = system > > > (win2k pro + RH9) for the last few days but with no success. heres = a > > > summary of what I have done so far > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo = image. > > > modified the config file to this... > > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > <colinux> > > > <block_device index=3D"0" path=3D"\Device\HarddiskVolume2" = enabled=3D"true" /> > > > <block_device index=3D"1" path=3D"\Device\HarddiskVolume3" = enabled=3D"true" /> > > > <bootparams>root=3D/dev/cobd0</bootparams> > > > <image path=3D"vmlinux" /> > > > <memory size=3D"64" /> > > > <network index=3D"0" type=3D"tap" name=3D"tap" /> > > > </colinux> > > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > > 3. copied the kernel modules packaged along with colinux into the > > > /lib/modules dir > > > > > > I then tried to boot the colinux. failed with some error about = unable > > > to locate /dev/hda3 (thats my root partition). I assumed this was = due > > > to me not having modified fstab. I then modified fstab to remove = all > > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > > /dev/cobd1 as swap. However the bootup sequence still fails with = some > > > error message about invalid superblock. > > > > > > I have gone through the website/forums/wiki and am just about to = give > > > up. Can somebody help me figure out whats going wrong? > > > > > > Thanks > > > Samir > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > digital self defense, top technical experts, no vendor pitches, > > > unmatched networking opportunities. Visit www.blackhat.com > > > _______________________________________________ > > > coLinux-users mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > >=20 > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Samir K. <sam...@gm...> - 2004-07-01 10:35:40
|
coLinux 0.6.1. hmm I am not sure which is my boot device. I have tried creating both. but no difference. On Thu, 1 Jul 2004 12:03:55 +0200, Leeuw van der, Tim <tim...@nl...> wrote: > > Which version of coLinux are you using, actually? 0.6.1, or the later snapshots? Is your boot-device /dev/cobd0, or /dev/cobd/0 ? > > --Tim > > > > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On Behalf Of Samir > Kuthiala > Sent: donderdag 1 juli 2004 11:51 > To: Peng > Cc: col...@li... > Subject: Re: [coLinux-users] help setting up a dual boot system > > I have already tried that. no difference. It stops at loading the root > partition which is pretty funny considering that afterwards it throws > me into the "Repair Filesystem" shell. And I can see the entire linux > partition and browse through it from within co-linux. > > On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > > > Try: > > > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" > > /> > > > > And disable your swap partition. Once the basic system works you can keep going > > and add the swap thing... > > > > Good luck, > > > > Peng > > > > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > > <sam...@gm...> wrote: > > > > > > Hi > > > > > > I have been trying to get the colinux to work on my dual boot system > > > (win2k pro + RH9) for the last few days but with no success. heres a > > > summary of what I have done so far > > > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > > > modified the config file to this... > > > =============================================== > > > <colinux> > > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > > > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > > > <bootparams>root=/dev/cobd0</bootparams> > > > <image path="vmlinux" /> > > > <memory size="64" /> > > > <network index="0" type="tap" name="tap" /> > > > </colinux> > > > =============================================== > > > 3. copied the kernel modules packaged along with colinux into the > > > /lib/modules dir > > > > > > I then tried to boot the colinux. failed with some error about unable > > > to locate /dev/hda3 (thats my root partition). I assumed this was due > > > to me not having modified fstab. I then modified fstab to remove all > > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > > /dev/cobd1 as swap. However the bootup sequence still fails with some > > > error message about invalid superblock. > > > > > > I have gone through the website/forums/wiki and am just about to give > > > up. Can somebody help me figure out whats going wrong? > > > > > > Thanks > > > Samir > > > > > > ------------------------------------------------------- > > > This SF.Net email sponsored by Black Hat Briefings & Training. > > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > > digital self defense, top technical experts, no vendor pitches, > > > unmatched networking opportunities. Visit www.blackhat.com > > > _______________________________________________ > > > coLinux-users mailing list > > > coL...@li... > > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-07-01 10:04:14
|
Which version of coLinux are you using, actually? 0.6.1, or the later = snapshots? Is your boot-device /dev/cobd0, or /dev/cobd/0 ? --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Samir Kuthiala Sent: donderdag 1 juli 2004 11:51 To: Peng Cc: col...@li... Subject: Re: [coLinux-users] help setting up a dual boot system I have already tried that. no difference. It stops at loading the root partition which is pretty funny considering that afterwards it throws me into the "Repair Filesystem" shell. And I can see the entire linux partition and browse through it from within co-linux. On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: >=20 > Try: >=20 > <block_device index=3D"0" path=3D"\Device\HarddiskVolume3" = enabled=3D"true" > /> >=20 > And disable your swap partition. Once the basic system works you can = keep going > and add the swap thing... >=20 > Good luck, >=20 > Peng >=20 >=20 > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > <sam...@gm...> wrote: > > > > Hi > > > > I have been trying to get the colinux to work on my dual boot system > > (win2k pro + RH9) for the last few days but with no success. heres a > > summary of what I have done so far > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo = image. > > modified the config file to this... > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > <colinux> > > <block_device index=3D"0" path=3D"\Device\HarddiskVolume2" = enabled=3D"true" /> > > <block_device index=3D"1" path=3D"\Device\HarddiskVolume3" = enabled=3D"true" /> > > <bootparams>root=3D/dev/cobd0</bootparams> > > <image path=3D"vmlinux" /> > > <memory size=3D"64" /> > > <network index=3D"0" type=3D"tap" name=3D"tap" /> > > </colinux> > > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > 3. copied the kernel modules packaged along with colinux into the > > /lib/modules dir > > > > I then tried to boot the colinux. failed with some error about = unable > > to locate /dev/hda3 (thats my root partition). I assumed this was = due > > to me not having modified fstab. I then modified fstab to remove all > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > /dev/cobd1 as swap. However the bootup sequence still fails with = some > > error message about invalid superblock. > > > > I have gone through the website/forums/wiki and am just about to = give > > up. Can somebody help me figure out whats going wrong? > > > > Thanks > > Samir > >=20 > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20 digital self defense, top technical experts, no vendor pitches,=20 unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Samir K. <sam...@gm...> - 2004-07-01 09:51:22
|
I have already tried that. no difference. It stops at loading the root partition which is pretty funny considering that afterwards it throws me into the "Repair Filesystem" shell. And I can see the entire linux partition and browse through it from within co-linux. On Thu, 1 Jul 2004 05:43:54 -0400, Peng <rin...@gm...> wrote: > > Try: > > <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" > /> > > And disable your swap partition. Once the basic system works you can keep going > and add the swap thing... > > Good luck, > > Peng > > > On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala > <sam...@gm...> wrote: > > > > Hi > > > > I have been trying to get the colinux to work on my dual boot system > > (win2k pro + RH9) for the last few days but with no success. heres a > > summary of what I have done so far > > > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > > modified the config file to this... > > =============================================== > > <colinux> > > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > > <bootparams>root=/dev/cobd0</bootparams> > > <image path="vmlinux" /> > > <memory size="64" /> > > <network index="0" type="tap" name="tap" /> > > </colinux> > > =============================================== > > 3. copied the kernel modules packaged along with colinux into the > > /lib/modules dir > > > > I then tried to boot the colinux. failed with some error about unable > > to locate /dev/hda3 (thats my root partition). I assumed this was due > > to me not having modified fstab. I then modified fstab to remove all > > references to /dev/hd* and added in /dev/cobd0 (as root) and > > /dev/cobd1 as swap. However the bootup sequence still fails with some > > error message about invalid superblock. > > > > I have gone through the website/forums/wiki and am just about to give > > up. Can somebody help me figure out whats going wrong? > > > > Thanks > > Samir > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > _______________________________________________ > > coLinux-users mailing list > > coL...@li... > > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > |
|
From: Peng <rin...@gm...> - 2004-07-01 09:43:56
|
Try: <block_device index="0" path="\Device\HarddiskVolume3" enabled="true" /> And disable your swap partition. Once the basic system works you can keep going and add the swap thing... Good luck, Peng On Thu, 1 Jul 2004 17:35:41 +0800, Samir Kuthiala <sam...@gm...> wrote: > > Hi > > I have been trying to get the colinux to work on my dual boot system > (win2k pro + RH9) for the last few days but with no success. heres a > summary of what I have done so far > > 1. create /dev/cobd0 to /dev/cobd7 using mknod > 2. installed colinux 0.6.1without downloading the Debian/Gentoo image. > modified the config file to this... > =============================================== > <colinux> > <block_device index="0" path="\Device\HarddiskVolume2" enabled="true" /> > <block_device index="1" path="\Device\HarddiskVolume3" enabled="true" /> > <bootparams>root=/dev/cobd0</bootparams> > <image path="vmlinux" /> > <memory size="64" /> > <network index="0" type="tap" name="tap" /> > </colinux> > =============================================== > 3. copied the kernel modules packaged along with colinux into the > /lib/modules dir > > I then tried to boot the colinux. failed with some error about unable > to locate /dev/hda3 (thats my root partition). I assumed this was due > to me not having modified fstab. I then modified fstab to remove all > references to /dev/hd* and added in /dev/cobd0 (as root) and > /dev/cobd1 as swap. However the bootup sequence still fails with some > error message about invalid superblock. > > I have gone through the website/forums/wiki and am just about to give > up. Can somebody help me figure out whats going wrong? > > Thanks > Samir > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > |
|
From: Samir K. <sam...@gm...> - 2004-07-01 09:36:46
|
Hi
I have been trying to get the colinux to work on my dual boot system
(win2k pro + RH9) for the last few days but with no success. heres a
summary of what I have done so far
1. create /dev/cobd0 to /dev/cobd7 using mknod
2. installed colinux 0.6.1without downloading the Debian/Gentoo image.
modified the config file to this...
===============================================
<colinux>
<block_device index="0" path="\Device\HarddiskVolume2" enabled="true" />
<block_device index="1" path="\Device\HarddiskVolume3" enabled="true" />
<bootparams>root=/dev/cobd0</bootparams>
<image path="vmlinux" />
<memory size="64" />
<network index="0" type="tap" name="tap" />
</colinux>
===============================================
3. copied the kernel modules packaged along with colinux into the
/lib/modules dir
I then tried to boot the colinux. failed with some error about unable
to locate /dev/hda3 (thats my root partition). I assumed this was due
to me not having modified fstab. I then modified fstab to remove all
references to /dev/hd* and added in /dev/cobd0 (as root) and
/dev/cobd1 as swap. However the bootup sequence still fails with some
error message about invalid superblock.
I have gone through the website/forums/wiki and am just about to give
up. Can somebody help me figure out whats going wrong?
Thanks
Samir
|
|
From: Guy Gascoigne-P. <gu...@wy...> - 2004-07-01 01:09:55
|
Take a look at the colinux-devel list archives, this has come up there, but not on this list. Anyway, the message that gave me the hint I needed to get working was: From: colinux-devel-admin@li... [mailto:colinux-devel-admin@li...]On Behalf Of Peng Li Sent: dinsdag 22 juni 2004 17:59 To: colinux-devel@li... Subject: [coLinux-devel] RE: bad superblock error when using snapshot 20040620 The problem is that fsck cannot find /dev/cobd0 or something.... here is a quick fix: Boot with the option init=/bin/bash cd /dev ln -sf cobd/0 cobd0 reboot Hope that it sets you looking in the right direction. Guy Thierry Legras wrote: > Hi, > > I tried coLinux with both Debian and Gentoo and i always get this > error at startup: > > FAT: bogus logical sector size 56932 > > Then after few consecutive errors, colinux shuts down. > > coLinux is installed on an NTFS partition. Maybe NTFS is not supported? > Any ideas? > > Thierry. > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital > self defense, top technical experts, no vendor pitches, unmatched > networking opportunities. Visit www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > . > |
|
From: Thierry L. <tl...@ya...> - 2004-06-30 19:55:42
|
Hi, I tried coLinux with both Debian and Gentoo and i always get this error at startup: > FAT: bogus logical sector size 56932 Then after few consecutive errors, colinux shuts down. coLinux is installed on an NTFS partition. Maybe NTFS is not supported? Any ideas? Thierry. |
|
From: Milind K. <mb...@ya...> - 2004-06-30 16:05:46
|
I too use debian (testing). So I guess I do not have to be concerned with changing my fstab. So can anyone using debian inform me how exactly they upgraded to the 20040622 snapshot? --- "Leeuw van der, Tim" <tim...@nl...> wrote: > Hi, > > I guess it does. I use the gentoo image. > > regards, > > --Tim > > -----Original Message----- > From: peter green [mailto:plu...@p1...] > Sent: woensdag 30 juni 2004 16:30 > To: Leeuw van der, Tim; Milind Kamble; > col...@li... > Subject: RE: [coLinux-users] Recommended procedure > for upgrading to > latest snapshot > > > does this /dev issue only effect distors that use > devfs > ive never had any such problems with debian woody > > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On > Behalf Of Leeuw van > der, Tim > Sent: 30 June 2004 15:08 > To: Milind Kamble; > col...@li... > Subject: RE: [coLinux-users] Recommended procedure > for upgrading to > latest snapshot > > > Hi, > > My first coLinux install was 0.6.1 so perhaps the > installer scripts changed; > but I never did an uninstall before > upgrading/downgrading between 0.6.1 and > the later snapshots. > The TAP driver is automatically installed from the > coLinux installer and > will be upgraded/downgraded along with coLinux. > > Keep in mind that your system might not come up > properly after the upgrade > because the coLinux partitions might be named > differently: /dev/cobd/0 > instead of /dev/cobd0. That's what happened to me > when going from 0.6.1 to > the latest snapshot. > Symptom: failing fsck > Remedy: fix your /etc/fstab. Easiest way is to do > that the last time you > boot into the old installation, rather than having > to do it from a > single-user console on a read-only mounted root > partition ... ;-) > > success, > > --Tim > > > -----Original Message----- > From: col...@li... > [mailto:col...@li...]On > Behalf Of Milind > Kamble > Sent: woensdag 30 juni 2004 16:03 > To: col...@li... > Subject: [coLinux-users] Recommended procedure for > upgrading to latest > snapshot > > > I have WinXP-Pro on a Pentium4 hardware. > I am planning to upgrade from coLinux-20040417 to > coLinux-20040622. I think coLinux-20040417 was a > development snapshot after release 0.6. So > essentially > I am going to skip release 0.6.1. What is the > recommended procedure to do the upgrade. > > Should I do an uninstall of coLinux via Control > Panel->Add/Remove->coLinux ? I don't see any entry > for > the TAP driver in the Add/Remove list. > > Thanks. > Milind > > > > __________________________________ > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! > http://promotions.yahoo.com/new_mail > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & > Training. > Attend Black Hat Briefings & Training, Las Vegas > July 24-29 - > digital self defense, top technical experts, no > vendor pitches, > unmatched networking opportunities. Visit > www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & > Training. > Attend Black Hat Briefings & Training, Las Vegas > July 24-29 - > digital self defense, top technical experts, no > vendor pitches, > unmatched networking opportunities. Visit > www.blackhat.com > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system > (http://www.grisoft.com). > Version: 6.0.712 / Virus Database: 468 - Release > Date: 27/06/2004 > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system > (http://www.grisoft.com). > Version: 6.0.712 / Virus Database: 468 - Release > Date: 27/06/2004 > > __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-06-30 14:32:05
|
Hi, I guess it does. I use the gentoo image. regards, --Tim -----Original Message----- From: peter green [mailto:plu...@p1...] Sent: woensdag 30 juni 2004 16:30 To: Leeuw van der, Tim; Milind Kamble; col...@li... Subject: RE: [coLinux-users] Recommended procedure for upgrading to latest snapshot does this /dev issue only effect distors that use devfs ive never had any such problems with debian woody -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Leeuw van der, Tim Sent: 30 June 2004 15:08 To: Milind Kamble; col...@li... Subject: RE: [coLinux-users] Recommended procedure for upgrading to latest snapshot Hi, My first coLinux install was 0.6.1 so perhaps the installer scripts = changed; but I never did an uninstall before upgrading/downgrading between 0.6.1 = and the later snapshots. The TAP driver is automatically installed from the coLinux installer and will be upgraded/downgraded along with coLinux. Keep in mind that your system might not come up properly after the = upgrade because the coLinux partitions might be named differently: /dev/cobd/0 instead of /dev/cobd0. That's what happened to me when going from 0.6.1 = to the latest snapshot. Symptom: failing fsck Remedy: fix your /etc/fstab. Easiest way is to do that the last time you boot into the old installation, rather than having to do it from a single-user console on a read-only mounted root partition ... ;-) success, --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Milind Kamble Sent: woensdag 30 juni 2004 16:03 To: col...@li... Subject: [coLinux-users] Recommended procedure for upgrading to latest snapshot I have WinXP-Pro on a Pentium4 hardware. I am planning to upgrade from coLinux-20040417 to coLinux-20040622. I think coLinux-20040417 was a development snapshot after release 0.6. So essentially I am going to skip release 0.6.1. What is the recommended procedure to do the upgrade. Should I do an uninstall of coLinux via Control Panel->Add/Remove->coLinux ? I don't see any entry for the TAP driver in the Add/Remove list. Thanks. Milind __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 |
|
From: peter g. <plu...@p1...> - 2004-06-30 14:29:58
|
does this /dev issue only effect distors that use devfs ive never had any such problems with debian woody -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Leeuw van der, Tim Sent: 30 June 2004 15:08 To: Milind Kamble; col...@li... Subject: RE: [coLinux-users] Recommended procedure for upgrading to latest snapshot Hi, My first coLinux install was 0.6.1 so perhaps the installer scripts changed; but I never did an uninstall before upgrading/downgrading between 0.6.1 and the later snapshots. The TAP driver is automatically installed from the coLinux installer and will be upgraded/downgraded along with coLinux. Keep in mind that your system might not come up properly after the upgrade because the coLinux partitions might be named differently: /dev/cobd/0 instead of /dev/cobd0. That's what happened to me when going from 0.6.1 to the latest snapshot. Symptom: failing fsck Remedy: fix your /etc/fstab. Easiest way is to do that the last time you boot into the old installation, rather than having to do it from a single-user console on a read-only mounted root partition ... ;-) success, --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Milind Kamble Sent: woensdag 30 juni 2004 16:03 To: col...@li... Subject: [coLinux-users] Recommended procedure for upgrading to latest snapshot I have WinXP-Pro on a Pentium4 hardware. I am planning to upgrade from coLinux-20040417 to coLinux-20040622. I think coLinux-20040417 was a development snapshot after release 0.6. So essentially I am going to skip release 0.6.1. What is the recommended procedure to do the upgrade. Should I do an uninstall of coLinux via Control Panel->Add/Remove->coLinux ? I don't see any entry for the TAP driver in the Add/Remove list. Thanks. Milind __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.712 / Virus Database: 468 - Release Date: 27/06/2004 |
|
From: Leeuw v. d. T. <tim...@nl...> - 2004-06-30 14:08:42
|
Hi, My first coLinux install was 0.6.1 so perhaps the installer scripts = changed; but I never did an uninstall before upgrading/downgrading = between 0.6.1 and the later snapshots. The TAP driver is automatically installed from the coLinux installer and = will be upgraded/downgraded along with coLinux. Keep in mind that your system might not come up properly after the = upgrade because the coLinux partitions might be named differently: = /dev/cobd/0 instead of /dev/cobd0. That's what happened to me when going = from 0.6.1 to the latest snapshot. Symptom: failing fsck Remedy: fix your /etc/fstab. Easiest way is to do that the last time you = boot into the old installation, rather than having to do it from a = single-user console on a read-only mounted root partition ... ;-) success, --Tim -----Original Message----- From: col...@li... [mailto:col...@li...]On Behalf Of Milind Kamble Sent: woensdag 30 juni 2004 16:03 To: col...@li... Subject: [coLinux-users] Recommended procedure for upgrading to latest snapshot I have WinXP-Pro on a Pentium4 hardware. I am planning to upgrade from coLinux-20040417 to coLinux-20040622. I think coLinux-20040417 was a development snapshot after release 0.6. So essentially I am going to skip release 0.6.1. What is the recommended procedure to do the upgrade. Should I do an uninstall of coLinux via Control Panel->Add/Remove->coLinux ? I don't see any entry for the TAP driver in the Add/Remove list. Thanks. Milind =09 __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail=20 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20 digital self defense, top technical experts, no vendor pitches,=20 unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users |
|
From: Milind K. <mb...@ya...> - 2004-06-30 14:02:50
|
I have WinXP-Pro on a Pentium4 hardware. I am planning to upgrade from coLinux-20040417 to coLinux-20040622. I think coLinux-20040417 was a development snapshot after release 0.6. So essentially I am going to skip release 0.6.1. What is the recommended procedure to do the upgrade. Should I do an uninstall of coLinux via Control Panel->Add/Remove->coLinux ? I don't see any entry for the TAP driver in the Add/Remove list. Thanks. Milind __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail |
|
From: Sarah T. <sar...@ya...> - 2004-06-30 08:32:31
|
"Sarah Tanembaum" <sar...@ya...> wrote in message news:cbtt23$lt4$1...@se...... > The error I got from /var/log/messages is as follows: > > modprobe: Can't open dependencies file /lib/modules/2.4.26-co-0.6.1/modules > > When I checked the directory, there are no > /lib/modules/2.4.26-co-0.6.1/ directory BUT there are > /lib/modules/2.4.25-co-0.6.1/ instead. > > Does the packager forgot to put the current modules in the distribution? > Thanks > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com Well, to get rid of the error, it make a symbolic link to what's there with what expected: ln -s /lib/modules/2.4.25-co-0.6.1/ /lib/modules/2.4.26-co-0.6.1 I don't know if this is right but it gets rid of the errors. |
|
From: Sarah T. <sar...@ya...> - 2004-06-30 08:20:48
|
The error I got from /var/log/messages is as follows: modprobe: Can't open dependencies file /lib/modules/2.4.26-co-0.6.1/modules When I checked the directory, there are no /lib/modules/2.4.26-co-0.6.1/ directory BUT there are /lib/modules/2.4.25-co-0.6.1/ instead. Does the packager forgot to put the current modules in the distribution? Thanks |
|
From: Sarah T. <sar...@ya...> - 2004-06-30 08:16:48
|
"Sarah Tanembaum" <sar...@ya...> wrote in message news:cbtlnv$4kp$1...@se...... > > "Sarah Tanembaum" <sar...@ya...> > wrote in message news:cbtist$va7$1...@se...... > > Hi, I successfully installed coLinux with Fedora1 root image but having > > problem with networking. > > > > I'm using Windows 2003 Server with only one network card connected to a > > router/switch that is connected to the internet. > > > > My windows IP Address is 192.168.5.5 > > My router/gateway is 192.168.5.1 > > TAP-Win32 installed. > > > > First of all, what networking method should I use? > > Bridged? or NAT? How? > > > > Thanks > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email sponsored by Black Hat Briefings & Training. > > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > > digital self defense, top technical experts, no vendor pitches, > > unmatched networking opportunities. Visit www.blackhat.com > > I decided to install the debian root. > The setup pretty much the same with the fedora ... > > Windows 2003 Server IP Address: 192.168.5.5 > My router/gateway IP Address: 192.168.5.1 > TAP-Win32 Installed. > > I bridged my Local Area Connection with TAP-Win32, then I set up the IP > address of the bridge to the following: > 192.168.5.2. > Then, I set the default gateway as 192.168.5.1 on both > Windows and the Debian. > > This works! It can ping each other and go out to the internet. > > But when I try it with fedora1, it did not work. > > Please help. Thanks > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com Now, I got it to work. It turns out that I have to put all the virtual machine in the same subnet as the "Windows 2003 Server" bridge address. Both(debian and fedora1 image) can talk to the host server and out to the internet; but it can't talk to each other(????) |
|
From: Sarah T. <sar...@ya...> - 2004-06-30 06:14:29
|
"Sarah Tanembaum" <sar...@ya...> wrote in message news:cbtist$va7$1...@se...... > Hi, I successfully installed coLinux with Fedora1 root image but having > problem with networking. > > I'm using Windows 2003 Server with only one network card connected to a > router/switch that is connected to the internet. > > My windows IP Address is 192.168.5.5 > My router/gateway is 192.168.5.1 > TAP-Win32 installed. > > First of all, what networking method should I use? > Bridged? or NAT? How? > > Thanks > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by Black Hat Briefings & Training. > Attend Black Hat Briefings & Training, Las Vegas July 24-29 - > digital self defense, top technical experts, no vendor pitches, > unmatched networking opportunities. Visit www.blackhat.com I decided to install the debian root. The setup pretty much the same with the fedora ... Windows 2003 Server IP Address: 192.168.5.5 My router/gateway IP Address: 192.168.5.1 TAP-Win32 Installed. I bridged my Local Area Connection with TAP-Win32, then I set up the IP address of the bridge to the following: 192.168.5.2. Then, I set the default gateway as 192.168.5.1 on both Windows and the Debian. This works! It can ping each other and go out to the internet. But when I try it with fedora1, it did not work. Please help. Thanks |
|
From: Sarah T. <sar...@ya...> - 2004-06-30 06:00:49
|
Hi, I successfully installed coLinux with Fedora1 root image but having problem with networking. I'm using Windows 2003 Server with only one network card connected to a router/switch that is connected to the internet. My windows IP Address is 192.168.5.5 My router/gateway is 192.168.5.1 TAP-Win32 installed. First of all, what networking method should I use? Bridged? or NAT? How? Thanks |
119 messages has been excluded from this view by a project administrator.
