colinux-devel — Cooperative Linux development mailing list

[coLinux-devel] Re: Errors reading mounted ext2 filesystem on dual boot machine

[<gr...@vo...>]

John Milton wrote :
>I was able to specify a swap file (which is working fine) and
the native ext2 partition that I dual boot to. This is my
>default.colinux.xml:
>
><?xml version="1.0" encoding="UTF-8"?>
><colinux>
>   <block_device index="0"
path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb"
enabled="true"> >    </block_device>
>    <block_device index="1" path="\DosDevices\c:\coLinux\swap"
enabled="true"> >    </block_device>
>    <block_device index="2" path="\Device\HardDiskVolume2"
enabled="true"> >    </block_device>
>    <bootparams>root=/dev/cobd0</bootparams>
>    <image path="vmlinux"></image>
></colinux>
>
>I mounted the parition read-only:
>
># mount -r /dev/cobd2 /mnt
>
>When I ls /mnt, I see all the files there. When I ls -l /mnt, I
get: >/bin/ls: /mnt/root: Input/output error
>for each directory. On the console, I'm seeing:
>
>attempt to access beyond end of device
>75:02: rw=0, want=393328, limit=133890
>EXT2-fs error (device cobd(117,2)): ext2_read_inode: unable to
read inode block - inode=49801, block=98331 >
>Is there some LBA vs LBA32 vs LARGE sort of geometry thing going
on here? >
>John
>--

I have very analogous experiencies.
It seems that cobdx = "\Device\HardDiskVolume." take their size
from maybe previously defined cobdx = file. When I had cca 110Meg
swap (file) and cca 300Meg /dev/hda8 (= \Device\HardDiskVolume7
;-( ) I've similar errors, without swap (means 1Gig partition =
file) seemd(!)  cobdx (=/dev/hda8) mounted work fine.

Rgds, Zdenek



-- 
Chces kilo? Tak pripoj kamose pres VOLNY.
Vice na http://studentpartner.volny.cz/

[coLinux-devel] mkswapfs

[peter g. <plu...@p1...>]

mkswapfs sees the cobd? devices as haveing 0 size makeing it impossible to
make swap on them

i get the feeling this may also be the cause of problems others are haveing
with reiserfs


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

Re: [coLinux-devel] scp'ing files

[John L. <jo...@su...>]

I assume you're using the latest version of colinux?  The older versions 
had a bug that caused corruption of packets over large transfers.

John

Jason A. Pattie wrote:

> Jason A. Pattie wrote:
>
>> SSH from cygwin works fine.  I haven't had any problems with it 
>> whatsoever.  However, I don't seem to be able to get scp'd files to 
>> work.  Whether it be inside the coLinux environment scp'ing to an 
>> outside server, or from the outside server to the coLinux 
>> environment.  It's also just as bad (with only a few bytes 
>> transferred) scp'ing from the Windows/cygwin environment to the 
>> coLinux machine.  Don't know what's going on.  It seems that most 
>> other networking types work fine (i.e., http, ftp, etc.).
>
>
> Sorry.  I guess the mailing list is a little slow getting back to me,
> but I found something interesting.  After finally getting the kernel
> transferred over, I tried scp'ing the linux patch file, and it worked!
> It's only 116KB.  This may mean something?  Small files are OK, but
> larger ones will fail?
>
>
>

[coLinux-devel] knoppix filesystems and networking

[peter g. <plu...@p1...>]

i have read that you are interested in makeing a colinux based knoppix

the biggest hurdle i see to this is that colinux is not trivial to install
it involves adding a network adaptor to the windows side and setting up
bridgeing fileshareing etc

while this is not really a problem for permanent setup it does seem to
seriously restrict it's uesfullness in a knoppix like system

i think colinux needs the folling features to make it practical

1: some form of host filesystem support something like mount -t hostfs c:/
/c
2: the ability to share the hosts network stack (ie createing an inet or
inet6 domain socket on colinux with this option enabled would create that
socket on the windows side)

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

[coLinux-devel] FreeS/WAN

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I successfully compiled SuperFreeS/WAN 1.99.8 and set it up under
coLinux.  However, pluto (the userland portion of FreeS/WAN) doesn't
stay running.

Does anybody else have FreeS/WAN working on coLinux, yet?

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFANqnluYsUrHkpYtARAvZOAJ9OjU84FvoYvtyc222R3DsfBOEL9QCeMRED
6+MiOywINQpPtnQPM47ydGg=
=jsNj
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] Getting better and better

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> Jason A. Pattie wrote:
>
>> However, NFS does not seem to work properly (another thing I compiled 
>> into my custom kernel).  I was able to get it to mount the directory 
>> from the server, but the moment I issued an 'ls' on the mounted NFS 
>> filesystem, the network traffic indicators for the network 
>> connections had lots of activity, but the 'ls' commands died, cannot 
>> be killed, even with a -9, and umount on the NFS mount point does not 
>> work.  Says the device is busy.
>
>
>
> I think I'm getting closer.  Doing tcpdump's on both ends reveals that 
> my laptop is sending back to the NFS server an 'icmp: <laptop> 
> unreachable - need to frag (mtu 1500)'.  Don't know exactly what this 
> means, but possibly we might need to reduce the mtu size on eth0 in 
> coLinux?


I did an ifconfig on eth0 and noticed that MTU is one of the values.  I 
was able to alter it by specifying 'mtu' and a value on the ifconfig 
commandline.  So, I dropped it to 1400.  This time, I did an ls on a 
directory that I knew existed off the main mount point and had few files 
in it.  It worked!  I then increased the MTU back up to 1500 and did the 
same ls command on the small directory again.  It worked also!  I then 
dropped the MTU back down to 1400 and attempted the ls on the big, main 
mount point directory again, and it locked up again.  Don't know what's 
goin' on.  And I still got fragment messages coming back to the server 
for an (mtu 1500).


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] Getting better and better

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> However, NFS does not seem to work properly (another thing I compiled 
> into my custom kernel).  I was able to get it to mount the directory 
> from the server, but the moment I issued an 'ls' on the mounted NFS 
> filesystem, the network traffic indicators for the network connections 
> had lots of activity, but the 'ls' commands died, cannot be killed, 
> even with a -9, and umount on the NFS mount point does not work.  Says 
> the device is busy.


I think I'm getting closer.  Doing tcpdump's on both ends reveals that 
my laptop is sending back to the NFS server an 'icmp: <laptop> 
unreachable - need to frag (mtu 1500)'.  Don't know exactly what this 
means, but possibly we might need to reduce the mtu size on eth0 in coLinux?


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] Getting better and better

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> Successfully got the coda filesystem working and operational.  It 
> doesn't show realms properly, so you have to know the exact path to 
> your exported filesystems, but other than that it seems to work fine.  
> I can access the files in the exported volumes, so I'm happy.

Looks like a reboot took care of the realms not resolving problem.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] Errors reading mounted ext2 filesystem on dual boot machine

[John M. <joh...@us...>]

I was able to specify a swap file (which is working fine) and the native ext2 partition that I dual boot to. This is my
default.colinux.xml:

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb" enabled="true">
    </block_device>
    <block_device index="1" path="\DosDevices\c:\coLinux\swap" enabled="true">
    </block_device>
    <block_device index="2" path="\Device\HardDiskVolume2" enabled="true">
    </block_device>
    <bootparams>root=/dev/cobd0</bootparams>
    <image path="vmlinux"></image>
</colinux>

I mounted the parition read-only:

# mount -r /dev/cobd2 /mnt

When I ls /mnt, I see all the files there. When I ls -l /mnt, I get:
/bin/ls: /mnt/root: Input/output error
for each directory. On the console, I'm seeing:

attempt to access beyond end of device
75:02: rw=0, want=393328, limit=133890
EXT2-fs error (device cobd(117,2)): ext2_read_inode: unable to read inode block - inode=49801, block=98331

Is there some LBA vs LBA32 vs LARGE sort of geometry thing going on here?

John
--
John Bly Milton IV  (512) w:493-2764, h:323-5622, m:750-1783
Home  joh...@us...  ICQ!  Don't FLAME, inform!  O-

Re: [coLinux-devel] Applications hanging in nanosleep

[Jason A. P. <pat...@pc...>]

John Milton wrote:

>I did an strace of dselect and dselect just stopped in a
>one second call to nanosleep, which was easy to break out of.
>  
>

I noticed this happened when attempting to upgrade libc6.  It did made a 
call to 'init u' and then a 'sleep 1', and just hung there.  So I ended 
up mangling the script to comment that line out, finish the "upgrade", 
and then rebooted with the newer version of libc6 and init.

>The same sort of thing happened in "/usr/bin/tset -s -m 'network:?xterm'"
>
>Perhaps there's some sort of race condition when sleeping for short intervals. Maybe there should be some logic in there to just
>return if the requested interval happens to have already passed.
>
>I am running coLinux on W2K pro, on a PIII/600 laptop.
>  
>
Hmm.  Me too.  :)


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] Applications hanging in nanosleep

[John M. <joh...@us...>]

I did an strace of dselect and dselect just stopped in a
one second call to nanosleep, which was easy to break out of.

The same sort of thing happened in "/usr/bin/tset -s -m 'network:?xterm'"

Perhaps there's some sort of race condition when sleeping for short intervals. Maybe there should be some logic in there to just
return if the requested interval happens to have already passed.

I am running coLinux on W2K pro, on a PIII/600 laptop.

John
--
John Bly Milton IV  (512) w:493-2764, h:323-5622, m:750-1783
Home  joh...@us...  ICQ!  Don't FLAME, inform!  O-

[coLinux-devel] Getting better and better

[Jason A. P. <pat...@pc...>]

Successfully got the coda filesystem working and operational.  It 
doesn't show realms properly, so you have to know the exact path to your 
exported filesystems, but other than that it seems to work fine.  I can 
access the files in the exported volumes, so I'm happy.

However, NFS does not seem to work properly (another thing I compiled 
into my custom kernel).  I was able to get it to mount the directory 
from the server, but the moment I issued an 'ls' on the mounted NFS 
filesystem, the network traffic indicators for the network connections 
had lots of activity, but the 'ls' commands died, cannot be killed, even 
with a -9, and umount on the NFS mount point does not work.  Says the 
device is busy.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] Reiserfs

[Jason A. P. <pat...@pc...>]

Anybody get their native linux partition using reiserfs as the 
filesystem mounted under coLinux?  I recompiled the kernel and selected 
reiserfs as an option.  It gives the following error when attempting to 
mount the parition:

reiserfs: found format "3.6" with standard journal
Filesystem on 75:03 cannot be mounted because it is bigger than the device
You may need to run fsck or increase size of your LVM partition
Or may be you forgot to reboot after fdisk when it told you to
mount: wrong fs type, bad option, bad superblock on /dev/cobd3,
       or too many mounted file systems


Does this mean reiserfs is not supported for the time being?


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

Sorry for replying so many times to my own post, but, this is very 
interesting.  I apt-get install'ed tcpdump and started a dump of eth0.  
The moment I did that, the dd piped through SSH to tar started working.  
An uninterrupted stream has so far ensued.  It's a bit slow, probably 
due to the fact that every packet is being dumped to the coLinux 
console, but at least it's working.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

I'm attempting to transfer the kernel into the Debian 1GB filesystem.  
I've tried 'dd if=linux-2.4.24.tar.bz2 | ssh root@colinux tar -C 
/usr/src -jxf -' as a last ditch effort to maybe uncover whether it's a 
difference between scp and ssh or not.  Apparently, it happens with ssh 
as well.  I noticed an interesting effect, though.  It appears that only 
the first or a few packets are transmitted between the coLinux 
environment and the Windows environment.  Further traffic just ceases.  
I have no idea what's causing this, either, since existing ssh sessions 
continue to work.  I exited one of my ssh sessions while attempting to 
do the above tar command, and my ssh session would not completely exit.  
I had to type '~.' to terminate it and get back to my cygwin prompt.

I find it strange that apt-get install's work fine which use HTTP 
transfers, but scp and/or ssh don't.


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

Jason A. Pattie wrote:

> SSH from cygwin works fine.  I haven't had any problems with it 
> whatsoever.  However, I don't seem to be able to get scp'd files to 
> work.  Whether it be inside the coLinux environment scp'ing to an 
> outside server, or from the outside server to the coLinux 
> environment.  It's also just as bad (with only a few bytes 
> transferred) scp'ing from the Windows/cygwin environment to the 
> coLinux machine.  Don't know what's going on.  It seems that most 
> other networking types work fine (i.e., http, ftp, etc.).

Sorry.  I guess the mailing list is a little slow getting back to me,
but I found something interesting.  After finally getting the kernel
transferred over, I tried scp'ing the linux patch file, and it worked!
It's only 116KB.  This may mean something?  Small files are OK, but
larger ones will fail?



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] scp'ing files

[Jason A. P. <pat...@pc...>]

SSH from cygwin works fine.  I haven't had any problems with it 
whatsoever.  However, I don't seem to be able to get scp'd files to 
work.  Whether it be inside the coLinux environment scp'ing to an 
outside server, or from the outside server to the coLinux environment.  
It's also just as bad (with only a few bytes transferred) scp'ing from 
the Windows/cygwin environment to the coLinux machine.  Don't know 
what's going on.  It seems that most other networking types work fine 
(i.e., http, ftp, etc.).


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] Network question on win2000

[Sonnie H. <son...@ho...>]

hi, I have installed 0.5.3 on Win2000 host with ip 193.55.x.x.
The ip of TAP is 192.168.0.1. I chose the debian root file system image
from sourceforge and successfully installed according to README.
Now I can ping between cL and win host, but failed to ping to the
193.55.x.x except my own ip. Starting/stopping ICS service is useless.
Someone else can ping to the Internet?

best wishes

sh

_________________________________________________________________
享用世界上最大的电子邮件系统― MSN Hotmail。  http://www.hotmail.com  

Re: [coLinux-devel] VFS: failure using existing install

[Thomas F. <tf...@no...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Tim,

you are using an unusual name for to block device. Try using cobd0 instead
of codb0. You must also add dev-files and fstab enties. For this staps you
can look in the image-script I send to the list.

Thomas

> I have been trying to use an existing (working) Debian install on my
> notebook.  The kernel isn't able to mount the root device.  Any ideas?
> Thnx - --tim
>
> Here is a PartionMagic dump of the disk:
> ==========================================================
> Partition Information for Disk 1:    38,154.4 Megabytes
> Volume         PartType    Status    Size MB    PartSect
> ==========================================================
> C:             NTFS        Pri,Boot 18,104.5           0
>                ExtendedX   Pri      20,049.9           0
>                EPBR        Log      10,652.5        None -
> E:             FAT32       Log      10,652.4  37,078,020
>                EPBR        Log       8,879.7  37,078,020
>                Linux Ext2  Log       8,879.6  58,894,290
>                EPBR        Log         517.7  58,894,290
> *:SWAPSPACE2   Linux Swap  Log         517.7  77,079,870
>
> Using the following config file:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <colinux>
>     <block_device index="0" path="\Device\Harddisk1\Volume2"
> enabled="true">
>     </block_device>
>     <memory size="64"></memory>
>     <bootparams>root=/dev/codb0</bootparams>
>     <image path="vmlinux"></image>
> </colinux>
>
> I get (note Kernel Panic near end):
>
> Cooperative Linux daemon
> Manager not opened
> Removing driver leftover
> Stopping driver service
> Removing driver service
> Installing kernel driver
> daemon: creating monitor
> co_message_switch: setting callback rule for 7
> co_message_switch: setting callback rule for 2
> co_message_switch: setting callback rule for 6
> co_message_switch: setting callback rule for 3
> co_message_switch: setting callback rule for 0
> co_message_switch: setting callback rule for 4
> daemon: launching net daemon
> daemon: launching console
> Linux version 2.4.24 (ka...@ca...) (gcc version 3.3.3
> 20040125 (prerelease) (Debian)) #498 Sat Feb 14 11:15:16 IST 2004
> 64MB LOWMEM available.
> On node 0 totalpages: 16384
> zone(0): 0 pages.
> zone(1): 16384 pages.
> zone(2): 0 pages.
> Kernel command line: root=/dev/codb0
> Initializing CPU#0
> Setting proxy interrupt vectors
> Console: colour VGA+ 80x25
> Calibrating delay loop... daemon: module connected: conet0
> co_message_switch: setting callback rule for 8
> 1228.80 BogoMIPS
> Memory: 62000k/65536k available (817k kernel code, 0k reserved, 53k
> data, 48k init, 0k highmem)
> Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
> Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
> Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
> CPU: Trace cache: 12K uops, L1 D cache: 8K
> CPU: L2 cache: 256K
> CPU:     After generic, caps: bfebf9ff 00000000 00000000 00000000
> CPU:             Common caps: bfebf9ff 00000000 00000000 00000000
> CPU: Intel Mobile Intel(R) Celeron(R) CPU 1.80GHz stepping 07
> Enabling fast FPU save and restore... done.
> daemon: module connected: console
> co_message_switch: setting callback rule for 6
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... OK.
> Checking for popad bug... OK.
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapdEnabling TAP-Win32...
> pipe client 0/8: Connecting to daemon...
> pipe client 0/8: Connection established
> Pipe broken, exiting
>
> Journalled Block Device driver loaded
> devfs: v1.12c (20020818) Richard Gooch (rg...@at...)
> devfs: boot_options: 0x0
> pty: 256 Unix98 ptys configured
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> cobd: loaded (max 8 devices)
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 4096 bind 8192)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Cannot open root device "codb0" or 00:00
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 00:00
>  daemon: monitor terminated, reason 3
> switch_message: freed message a040488 (2 to 4)
> daemon: module disconnected: conet0
> switch_message: freed message a040488 (2 to 4)
> daemon: module disconnected: console
> daemon: monitor shutting down
> daemon: daemon cleanup
> Removing kernel driver
> Stopping driver service
> Removing driver service
> pipe client 0/6: Connecting to daemon...
> pipe client 0/6: Connection established
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFANdQhnwJBIFTVIqwRAgoNAKCSIwDL0ZHdI1KroxIOycYHTgCQjACgtIRa
UiGbydYGnoxcYFheFHFKhBA=
=tYMV
-----END PGP SIGNATURE-----

Re: [coLinux-devel] RedHat on coLinux ?

[Sugree P. <su...@hp...>]

You might need to increase memory size or add more swap.

<memory size="32"></memory>

Good luck,

Sugree Phatanapherom
su...@hp...

----- Original Message ----- 
From: "Rob McDonald" <ro...@as...>
To: "Sugree Phatanapherom" <su...@hp...>;
<col...@li...>
Sent: Thursday, February 19, 2004 10:26 PM
Subject: Re: [coLinux-devel] RedHat on coLinux ?


> Thanks for making that image available.
>
> It seems to work good for starters, but when I try to do an apt-get
update,
> it downloads the release and pkglist files, and then crashes with an alloc
> failure while it is trying to read the package lists.
>
> I tried adding
>
> APT::Cache-Limit "8388608";
>
> to the /etc/apt/apt.conf
>
> And I tried removing some of the servers from (to make the package list
> smaller)
>
> /etc/apt/sources.list
>
> Did you have this problem?  Any ideas for a solution?
>
> I am running the latest binary release of coLinux.
>
> Thanks again,
>
>            Rob
>
>
> > I am using coLinux with RedHat 9.0. If you want to try (49 MB):
> >
> > http://amata.cpe.ku.ac.th/~sugree/dload/colinux/redhat-9.0.ext3.1gb.bz2
> >
> > It contains only based packages. Man is installed but no man pages for
> APIs
> > at all. Anyway, you can use apt-get to install anythings you want
easily.
> > The pre-configured sources are pointing to freshrpms and dag
repositories.
> > So the first step is to modify /etc/resolv.conf and run apt-get update
to
> > get the packages list.
> >
> > Actually, you can build your own root image by rpm command (like me).
For
> > example:
> >
> > dd if=/dev/zero of=redhat-9.0.ext3.1gb bs=1024 count=1048576
> > mkfs.ext3 redhat-9.0.ext3.1gb
> > mkdir root
> > mount -o loop redhat-9.0.ext3.1gb root
> > rpm --initdb --root=$PWD/root
> >
> > At this point, you can install whatever you want. All rpm commands must
be
> > added --root option. That's all and then bzip2 it.
> >
> > umount root
> > bzip2 -k -9 redhat-9.0.ext3.1gb
> >
> > Good luck,
> >
> >
> > > Installing a "normal" distribution on coLinux - "The Slackware on
> coLinux
> > > HOWTO"I am very impressed with the power of coLinux.  Great work for a
> > > 1-month old (public) project.
> > >
> > > Has anyone attempted or succeeded in getting a recent RedHat install
> done
> > > through coLinux?  I've read the threads started by Nir Perry about his
> > > experiences with Slackware, but I am not experienced enough with Linux
> > > administration to try to duplicate them, much less apply them to
RedHat.
> > >
> > > I've had a lot of luck with the Debian starter image, but some of my
> > > programs behave very strangely (crash).  The behavior looks like it
> could
> > be
> > > due to incompatibilities between compiler and library versions, or
they
> > > might be due to coLinux.  I really can't tell, and would like to take
> the
> > > distribution differences out of the loop to isolate the problem.
> > >
> > > I realize that the coLinux developers have lots to do, but
fortunately,
> > the
> > > images aren't impacted by coLinux development.  Is there another
source
> of
> > > images out there? (vmware users)  Is there enough interest to start a
> > projct
> > > compiling a library of images?  Or is it just easier to focus effort
on
> > > getting coLinux to boot generic install CD's, and go from there?
> > >
> > > Any help would be appretiated.
> > >
> > >          Rob
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > > Build and deploy apps & Web services for Linux with
> > > a free DVD software kit from IBM. Click Now!
> > > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > > _______________________________________________
> > > coLinux-devel mailing list
> > > coL...@li...
> > > https://lists.sourceforge.net/lists/listinfo/colinux-devel
> >
> >
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel

[coLinux-devel] VFS: failure using existing install

[Tim D. <td...@sp...>]

I have been trying to use an existing (working) Debian install on my
notebook.  The kernel isn't able to mount the root device.  Any ideas?
Thnx - --tim

Here is a PartionMagic dump of the disk:
==========================================================
Partition Information for Disk 1:    38,154.4 Megabytes
Volume         PartType    Status    Size MB    PartSect  
==========================================================
C:             NTFS        Pri,Boot 18,104.5           0  
               ExtendedX   Pri      20,049.9           0  
               EPBR        Log      10,652.5        None -
E:             FAT32       Log      10,652.4  37,078,020  
               EPBR        Log       8,879.7  37,078,020  
               Linux Ext2  Log       8,879.6  58,894,290  
               EPBR        Log         517.7  58,894,290  
*:SWAPSPACE2   Linux Swap  Log         517.7  77,079,870  

Using the following config file:

<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <block_device index="0" path="\Device\Harddisk1\Volume2"
enabled="true">
    </block_device>
    <memory size="64"></memory>
    <bootparams>root=/dev/codb0</bootparams>
    <image path="vmlinux"></image>
</colinux>

I get (note Kernel Panic near end):

Cooperative Linux daemon
Manager not opened
Removing driver leftover
Stopping driver service
Removing driver service
Installing kernel driver
daemon: creating monitor
co_message_switch: setting callback rule for 7
co_message_switch: setting callback rule for 2
co_message_switch: setting callback rule for 6
co_message_switch: setting callback rule for 3
co_message_switch: setting callback rule for 0
co_message_switch: setting callback rule for 4
daemon: launching net daemon
daemon: launching console
Linux version 2.4.24 (ka...@ca...) (gcc version 3.3.3
20040125 (prerelease) (Debian)) #498 Sat Feb 14 11:15:16 IST 2004
64MB LOWMEM available.
On node 0 totalpages: 16384
zone(0): 0 pages.
zone(1): 16384 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/codb0
Initializing CPU#0
Setting proxy interrupt vectors
Console: colour VGA+ 80x25
Calibrating delay loop... daemon: module connected: conet0
co_message_switch: setting callback rule for 8
1228.80 BogoMIPS
Memory: 62000k/65536k available (817k kernel code, 0k reserved, 53k
data, 48k init, 0k highmem)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 16384 (order: 4, 65536 bytes)
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 256K
CPU:     After generic, caps: bfebf9ff 00000000 00000000 00000000
CPU:             Common caps: bfebf9ff 00000000 00000000 00000000
CPU: Intel Mobile Intel(R) Celeron(R) CPU 1.80GHz stepping 07
Enabling fast FPU save and restore... done.
daemon: module connected: console
co_message_switch: setting callback rule for 6
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapdEnabling TAP-Win32...
pipe client 0/8: Connecting to daemon...
pipe client 0/8: Connection established
Pipe broken, exiting

Journalled Block Device driver loaded
devfs: v1.12c (20020818) Richard Gooch (rg...@at...)
devfs: boot_options: 0x0
pty: 256 Unix98 ptys configured
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
cobd: loaded (max 8 devices)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Cannot open root device "codb0" or 00:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 00:00
 daemon: monitor terminated, reason 3
switch_message: freed message a040488 (2 to 4)
daemon: module disconnected: conet0
switch_message: freed message a040488 (2 to 4)
daemon: module disconnected: console
daemon: monitor shutting down
daemon: daemon cleanup
Removing kernel driver
Stopping driver service
Removing driver service
pipe client 0/6: Connecting to daemon...
pipe client 0/6: Connection established

Re: [coLinux-devel] my comments on colinux

[Tim L. <ti...@ke...>]

On Thu, Feb 19, 2004 at 06:50:59PM -0000, peter green wrote:
> i have not been useing distro sources it's been vanilla all the way :)
> is there any easy way to rind all .rej files in a current dir and it's
> subdirs on linux ls -r *.rej seems not to work

Try:
  find ./ -name "*.rej"
You can substitute a directory other
than the current "./" if you wish.

--Tim Larson

RE: [coLinux-devel] my comments on colinux

[peter g. <plu...@p1...>]

i have not been useing distro sources it's been vanilla all the way :)
is there any easy way to rind all .rej files in a current dir and it's
subdirs on linux ls -r *.rej seems not to work

-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of Robert
Stonehouse
Sent: 19 February 2004 18:42
To: Alejandro R. Sedeno
Cc: peter green; col...@li...
Subject: RE: [coLinux-devel] my comments on colinux


Why not use the cobuild.sh script from the colinux source package?
This will download a clean source of all the required components
including a clean 2.4.24 source.

Remember that other distributions often have custom patched kernels and
this may be why you are having problems

On Thu, 19 Feb 2004, Alejandro R. Sedeno wrote:

> I saw this error when I was using Debian's 2.4.24 kernel source package.
> The patch fails to add a line to linux/arch/i386/config.in, if I
> remember correctly. It should have left you a config.in.rej. Check it
> out, finish applying the patch by hand, and see if it works then.

---
Rob Stonehouse


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.592 / Virus Database: 375 - Release Date: 18/02/2004

RE: [coLinux-devel] my comments on colinux

[Robert S. <rj...@ze...>]

Why not use the cobuild.sh script from the colinux source package?
This will download a clean source of all the required components
including a clean 2.4.24 source.

Remember that other distributions often have custom patched kernels and
this may be why you are having problems

On Thu, 19 Feb 2004, Alejandro R. Sedeno wrote:

> I saw this error when I was using Debian's 2.4.24 kernel source package.
> The patch fails to add a line to linux/arch/i386/config.in, if I
> remember correctly. It should have left you a config.in.rej. Check it
> out, finish applying the patch by hand, and see if it works then.

---
Rob Stonehouse

RE: [coLinux-devel] my comments on colinux

[Alejandro R. S. <as...@MI...>]

I saw this error when I was using Debian's 2.4.24 kernel source package.
The patch fails to add a line to linux/arch/i386/config.in, if I
remember correctly. It should have left you a config.in.rej. Check it
out, finish applying the patch by hand, and see if it works then.

-Alejandro

On Thu, 2004-02-19 at 07:57, peter green wrote:
> well i did a dist-upgrade to sarge to get gcc 3.x
> 
> i now get a different error in the same line
> 
> colinux:~/colinux-20040214/linux# make vmlinux
> gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
> types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
> er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> c -o init/main.o init/main.c
> In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
>                  from
> /root/colinux-20040214/linux/include/linux/blkdev.h:11,
>                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
>                  from init/main.c:25:
> /root/colinux-20040214/linux/include/linux/cooperative.h:233:21: missing ')'
> in macro parameter list
> make: *** [init/main.o] Error 1
> colinux:~/colinux-20040214/linux#
> 
> here is the line in question
> #define co_debug(...args)         do {} while(0)
> 
> 
> -----Original Message-----
> From: Robert Stonehouse [mailto:rj...@ze...]
> Sent: 19 February 2004 12:10
> To: peter green
> Cc: col...@li...
> Subject: RE: [coLinux-devel] my comments on colinux
> 
> 
> On Thu, 19 Feb 2004, peter green wrote:
> 
> > colinux:~/colinux-20040214/linux# make vmlinux
> > gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -o
> > scripts/split-include scripts/split-include.c
> > scripts/split-include include/linux/autoconf.h include/config
> >
> gcc -D__KERNEL__ -I/root/colinux-20040214/linux/include -Wall -Wstrict-proto
> >
> types -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-point
> >
> er -pipe -mpreferred-stack-boundary=2 -march=i686   -DKBUILD_BASENAME=main -
> > c -o init/main.o init/main.c
> > In file included from /root/colinux-20040214/linux/include/asm/io.h:5,
> >                  from
> > /root/colinux-20040214/linux/include/linux/blkdev.h:11,
> >                  from /root/colinux-20040214/linux/include/linux/blk.h:4,
> >                  from init/main.c:25:
> > /root/colinux-20040214/linux/include/linux/cooperative.h:233: badly
> > punctuated parameter list in `#define'
> > make: *** [init/main.o] Error 1
> > colinux:~/colinux-20040214/linux#
> >
> > any ideas what causes this?
> 
> Try using GCC version 3.x rather than 2.x
> You can override the default compiler from your path with something like
> make vmlinux CC=/some/path/bin/gcc_3_3_2
> 
> --
> Rob Stonehouse
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.560 / Virus Database: 352 - Release Date: 08/01/2004
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>