colinux-users — coLinux users mailing list

RE: [coLinux-users] [ANN] Mandrake 10.0 image for coLinux - final

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

are debian and gentoo really the only distros that support upgrading without
reinstalling?

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of David
> Burela
> Sent: 25 October 2004 00:07
> To: col...@li...
> Subject: RE: [coLinux-users] [ANN] Mandrake 10.0 image for coLinux -
> final
>
>
> And now that mandrake 10.1 just got released you can start over again :P
> Seriously though, nice work man!
>
> -Dave
>
> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...] On Behalf Of Olivier
> Souiry
> Sent: Monday, 25 October 2004 8:25 AM
> To: col...@li...
> Subject: [coLinux-users] [ANN] Mandrake 10.0 image for coLinux - final
>
> Hello people,
>
> after two release candidates, here is the final release of my filesystem
> image for Mandrake 10.0 Official, built from scratch with Mandrake RPMs.
>
> at 37 Mb compressed, it includes full rpm and urpmi support, loadkey
> support, vi, nano, sshd and man pages among other things. no X
> for this one.
>
> more information is available there :
>
> http://www.colinux.org/wiki/index.php/MandrakeForColinux
>
>
> just by using URPMI you can easily install X clients like rpmdrake and use
> VNC for best performances (pango makes many things slow).
>
>
> Regards, Olivier Souiry
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to
> find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

RE: [coLinux-users] [ANN] Mandrake 10.0 image for coLinux - final

[David B. <db...@so...>]

And now that mandrake 10.1 just got released you can start over again :P
Seriously though, nice work man!

-Dave 

-----Original Message-----
From: col...@li...
[mailto:col...@li...] On Behalf Of Olivier
Souiry
Sent: Monday, 25 October 2004 8:25 AM
To: col...@li...
Subject: [coLinux-users] [ANN] Mandrake 10.0 image for coLinux - final

Hello people,

after two release candidates, here is the final release of my filesystem
image for Mandrake 10.0 Official, built from scratch with Mandrake RPMs.

at 37 Mb compressed, it includes full rpm and urpmi support, loadkey
support, vi, nano, sshd and man pages among other things. no X for this one.

more information is available there :

http://www.colinux.org/wiki/index.php/MandrakeForColinux


just by using URPMI you can easily install X clients like rpmdrake and use
VNC for best performances (pango makes many things slow).


Regards, Olivier Souiry




-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] [ANN] Mandrake 10.0 image for coLinux - final

[Olivier S. <co...@a-...>]

Hello people,

after two release candidates, here is the final release of my filesystem
image for Mandrake 10.0 Official, built from scratch with Mandrake RPMs.

at 37 Mb compressed, it includes full rpm and urpmi support, loadkey
support, vi, nano, sshd and man pages among other things. no X for this one.

more information is available there :

http://www.colinux.org/wiki/index.php/MandrakeForColinux


just by using URPMI you can easily install X clients like rpmdrake and use
VNC for best performances (pango makes many things slow).


Regards, Olivier Souiry

Re: [coLinux-users] cofs problem...

[Paradise <par...@gm...>]

hmm..wired....it is monotone version that I am using, and the kernel
is enable cofs
linux-config:CONFIG_COFUSE_FS=y


On Sun, 24 Oct 2004 11:53:08 -0400, Ian Bonnycastle <ib...@gm...> wrote:
> On Sun, 24 Oct 2004 22:26:59 +0800, Paradise <par...@gm...> wrote:
> > ':rel path' is optional stated on src/doc/cofs
> > and there is example " mount -t cofs 0 /mnt/windows"
> 
>    Ohh... ok... I didn't realize what the 0 there was representing.. I
> get it now.
> 
> > this doesnt work too
> > colinux root # mount -t cofs cofs0:/ /mnt/d
> > mount: wrong fs type, bad option, bad superblock on cofs0:/,
> >       or too many mounted file systems
> 
>     I've seen this error too, and I can't remember what I did to fix
> it. It was like the filesystem wasn't recognized by the kernel. I do
> know, though, that the latest snapshot *may* include it, but the
> latest monotone build definitely includes it.
> 
> Ian
> 


-- 
Regards,
Paradise

Re: [coLinux-users] cofs problem...

[Ian B. <ib...@gm...>]

On Sun, 24 Oct 2004 22:26:59 +0800, Paradise <par...@gm...> wrote:
> ':rel path' is optional stated on src/doc/cofs
> and there is example " mount -t cofs 0 /mnt/windows"

   Ohh... ok... I didn't realize what the 0 there was representing.. I
get it now.

> this doesnt work too
> colinux root # mount -t cofs cofs0:/ /mnt/d
> mount: wrong fs type, bad option, bad superblock on cofs0:/,
>       or too many mounted file systems

    I've seen this error too, and I can't remember what I did to fix
it. It was like the filesystem wasn't recognized by the kernel. I do
know, though, that the latest snapshot *may* include it, but the
latest monotone build definitely includes it.

Ian

Re: [coLinux-users] cofs problem...

[Paradise <par...@gm...>]

Hi thanks for quick response.

':rel path' is optional stated on src/doc/cofs
and there is example " mount -t cofs 0 /mnt/windows"

I did the everything correctly that stated on cofs document already

this doesnt work too
colinux root # mount -t cofs cofs0:/ /mnt/d
mount: wrong fs type, bad option, bad superblock on cofs0:/,
       or too many mounted file systems

maybe there is something wrong with the kernel, but I am using the
correct kernel from the snapshot or ' my compile version' , both do
not work..

On Sun, 24 Oct 2004 08:54:26 -0400, Ian Bonnycastle <ib...@gm...> wrote:
> On Sun, 24 Oct 2004 17:46:46 +0800, Paradise <par...@gm...> wrote:
> > Kernel command line: root=/dev/cobd/0 cofs0=\Dos\Devices\d:
> > -----------------------------------------------------------------------------------------
> > colinux root # mount -t cofs 0 /mnt/d
> > mount: wrong fs type, bad option, bad superblock on 0,
> >       or too many mounted file systems
> 
>     The actual correct syntax is:
> 
> mount -t cofs <cofs#>:<rel path> <mountpoint> [-o <options>]
> 
> <cofs#> is the cofs device parameter you have in your kernel command
> line (in this case cofs0); <rel path> is the relative path into cofs0
> that you want to mount (if you want the whole thing, use a <rel path>
> of /); <mountpoint> is where in your linux tree you want the mount and
> [-o <options>] are any number of the optional parameters that Dan
> outlined in his docs that you can use with cofs (including dmask'ing,
> fmask'ing, uid'ing and gid'ing the files).
> 
> Hope this helps,
> 
> Ian
> 


-- 
Regards,
Paradise

Re: [coLinux-users] cofs problem...

[Ian B. <ib...@gm...>]

On Sun, 24 Oct 2004 17:46:46 +0800, Paradise <par...@gm...> wrote:
> Kernel command line: root=/dev/cobd/0 cofs0=\Dos\Devices\d:
> -----------------------------------------------------------------------------------------
> colinux root # mount -t cofs 0 /mnt/d
> mount: wrong fs type, bad option, bad superblock on 0,
>       or too many mounted file systems

    The actual correct syntax is:

mount -t cofs <cofs#>:<rel path> <mountpoint> [-o <options>]

<cofs#> is the cofs device parameter you have in your kernel command
line (in this case cofs0); <rel path> is the relative path into cofs0
that you want to mount (if you want the whole thing, use a <rel path>
of /); <mountpoint> is where in your linux tree you want the mount and
[-o <options>] are any number of the optional parameters that Dan
outlined in his docs that you can use with cofs (including dmask'ing,
fmask'ing, uid'ing and gid'ing the files).

Hope this helps,

Ian

[coLinux-users] cofs problem...

[Paradise <par...@gm...>]

Hello, 

I have problem on using the cofs from newest version pre5 and monotone...
I cannot mount the cofs on D:
Anyone know the problem?
---------------------------------------------------------------------------------------
D:\coLinux>colinux-daemon.exe -c colinux.default.xml
Cooperative Linux Daemon, 0.6.2-pre5
Compiled on Sun Oct 24 16:44:05 2004

Linux version 2.6.8.1-co-0.6.2-pre5 (cantona@colinux) (gcc version 3.3.4 2004062
3 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)) #1 Sun Oct 24 17:07:11 HKT 20
04
64MB LOWMEM available.
On node 0 totalpages: 16384
  DMA zone: 0 pages, LIFO batch:1
  Normal zone: 16384 pages, LIFO batch:4
  HighMem zone: 0 pages, LIFO batch:1
Built 1 zonelists
Kernel command line: root=/dev/cobd/0 cofs0=\Dos\Devices\d:
-----------------------------------------------------------------------------------------
colinux root # mount -t cofs 0 /mnt/d
mount: wrong fs type, bad option, bad superblock on 0,
       or too many mounted file systems


Thanks,
Paradise.

[coLinux-users] Looking for a colinux installation executable built with gcc 3.4

[Milind K. <mb...@ya...>]

Has anyone built the colinux installation files with
gcc 3.4? I am using the 20041007 snapshot. I built a
vmlinux for colinux under Archlinux, but realized that
the colinux snapshot has been built using gcc 3.3, and
Archlinux has moved on to 3.4.

Thanks
Milind


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com

[coLinux-users] Colinux with Debian Sarge

[<lu...@gm...>]

If someone need I'm preparing a new Debian Sarge inst with 1Gb filesystem.

I used the instructions found at
http://www.oracolo.com/colinux/colinux_and_debian.htm

Re: [coLinux-users] parport support

[Henry N. <Hen...@Ar...>]

Zbynek Winkler wrote:

> Hello.
> 
> If I follow the instructions on how to build custom kernel and enable 
> parport support - will it work?
> 
> I've searched the mailing list archives and the colinux.org site but I 
> haven't found any info suggesting either way.
> 
> Thanks.
> 
> Zbynek
> 

Parport don't work. CoLinux have no direct hardware access.
But it's a nice idea for new daemon. What do you plan to connect on 
parport? A printer?

-- 
Henry Nestler

[coLinux-users] parport support

[Zbynek W. <zw...@us...>]

Hello.

If I follow the instructions on how to build custom kernel and enable 
parport support - will it work?

I've searched the mailing list archives and the colinux.org site but I 
haven't found any info suggesting either way.

Thanks.

Zbynek

-- 
http://zw.matfyz.cz/     http://robotika.cz/
Faculty of Mathematics and Physics, Charles University, Prague, Czech Republic

[coLinux-users] Fwd: [coLinux-devel] Strange thing with XP SP2

[Ian B. <ib...@gm...>]

Whoops.. forwarded to the wrong list.. :( My bad again.. I 
apolgize.

---------- Forwarded message ----------
From: Ian Bonnycastle <ib...@gm...>
Date: Wed, 20 Oct 2004 08:41:10 -0400
Subject: Re: [coLinux-devel] Strange thing with XP SP2
To: Marko Bozikovic <bo...@ks...>


This DOES sound like a network issue. Can you telnet to other ports?
What happens when you do so? (I mean, do you get the usual protocol
header, or does it just hang?) How are you running sshd on the coLinux
box? Is it by inetd or via a daemon process? If its by inetd, is sshd
being started properly? Is there a CPU spike when you telnet into port
22? There are a varying number of factors that could cause sshd to
sieze up when "woken up" or started by inetd. Often, in my experience,
they point to CPU or network issues that are very obscure, and
sometimes hard to track down. In this case, it could be the fact that
XP SP2 is having its way with the WinPCAP driver for some odd reason.
Does the same thing occur with the TapTUN driver? Give it a try, and
let me know, I'd be interested in finding out the differences.

Ian




On Wed, 20 Oct 2004 09:35:59 +0200, Marko Bozikovic <bo...@ks...> wrote:
> Hi!
>
> I've just installed a fresh system with WinXP SP2, and the strangest things
> happen...
>
> coLinux version is 20040710 (newer snapshots won't start as services, even on
> Win2k system, no idea why), Winpcap 3.1 beta 3.
>
> coLinux is up and running, debian-unstable, copied from my old machine (where
> it worked fine). I can ping coLinux from Windows, I can't ssh to it, but I
> *can* telnet to port 22. ssh'ing from another machine works fine. I've tried
> this with XP firewall service on and off, no change.
>
> Can anyone help? :)
>
> TIA,
> --
> Marko
> ICQ: 5990814
>
> I'm not under the alkafluence of inkahol
> that some thinkle peep I am.
> It's just the drunker I sit here the longer I get.
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

[coLinux-users] Fwd: [coLinux-devel] Strange thing with XP SP2

[Ian B. <ib...@gm...>]

Whoops.. forgot to forward this reply to the list.

---------- Forwarded message ----------
From: Ian Bonnycastle <ib...@gm...>
Date: Wed, 20 Oct 2004 08:41:10 -0400
Subject: Re: [coLinux-devel] Strange thing with XP SP2
To: Marko Bozikovic <bo...@ks...>


This DOES sound like a network issue. Can you telnet to other ports?
What happens when you do so? (I mean, do you get the usual protocol
header, or does it just hang?) How are you running sshd on the coLinux
box? Is it by inetd or via a daemon process? If its by inetd, is sshd
being started properly? Is there a CPU spike when you telnet into port
22? There are a varying number of factors that could cause sshd to
sieze up when "woken up" or started by inetd. Often, in my experience,
they point to CPU or network issues that are very obscure, and
sometimes hard to track down. In this case, it could be the fact that
XP SP2 is having its way with the WinPCAP driver for some odd reason.
Does the same thing occur with the TapTUN driver? Give it a try, and
let me know, I'd be interested in finding out the differences.

Ian




On Wed, 20 Oct 2004 09:35:59 +0200, Marko Bozikovic <bo...@ks...> wrote:
> Hi!
>
> I've just installed a fresh system with WinXP SP2, and the strangest things
> happen...
>
> coLinux version is 20040710 (newer snapshots won't start as services, even on
> Win2k system, no idea why), Winpcap 3.1 beta 3.
>
> coLinux is up and running, debian-unstable, copied from my old machine (where
> it worked fine). I can ping coLinux from Windows, I can't ssh to it, but I
> *can* telnet to port 22. ssh'ing from another machine works fine. I've tried
> this with XP firewall service on and off, no change.
>
> Can anyone help? :)
>
> TIA,
> --
> Marko
> ICQ: 5990814
>
> I'm not under the alkafluence of inkahol
> that some thinkle peep I am.
> It's just the drunker I sit here the longer I get.
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

[coLinux-users] coLinux on linux distribution

[Ian B. <ib...@gm...>]

I know its pretty shaky still, but I was wondering if there was any
plans on releasing colinux-on-linux for a particular compiler set.
I.E. If someone has been successful in compiling, and getting to work,
colinux-on-linux for Debian testing (latest apt-get dist-upgrade) or
Debian stable (latest apt-get dist-upgrade), that would insure the
right source/compiler were used to compile it.

If anyone has the above binaries, it would be greatly appreciated, as
I want to get it to work, but I'm having such a headache compiling it,
I'm about to go crazy.

Ian

[coLinux-users] snmp

[Glen J. <gle...@al...>]

Has anyone experienced net-snmp issues with coLinux?   I have coLinux/FC1 
running on several machines and after a day or two, the net-snmp-utils (and 
php-snmp) stop working.  MRTG works fine, however.

Below is the problem:

[root@colinux root]# snmpwalk -cprivate -v2c cisco-2620 .1
Timeout: No Response from cisco-2620

When tcpdump is running, the following shows up:

[root@colinux root]# tcpdump -i eth0 port snmp
tcpdump: listening on eth0
13:34:58.4270111812 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270112360 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270112722 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270113430 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270113765 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270114092 colinux.4012 > cisco-2620.snmp:  C=private 
GetNextRequest(21)  .0.1 (DF)
13:34:58.4270141472 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]
13:34:58.4270141862 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]
13:34:58.4270142166 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]
13:34:58.4270151797 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]
13:34:58.4270152200 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]
13:34:58.4270152484 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(29)  .1.3.6.1.2.1.1.1.0=[|snmp]

And MRTG (which works fine) firing three seconds later.

13:35:01.4270109119 colinux.4012 > cisco-2620.snmp:  C=private 
GetRequest(32)  .1.3.6.1.2.1.31.1.1.1.1.1 [|snmp] (DF)
13:35:01.4270125274 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(32)  .1.3.6.1.2.1.31.1.1.1.1.1="S"
13:35:01.4270287981 colinux.4012 > cisco-2620.snmp:  C=private 
GetRequest(32)  .1.3.6.1.2.1.31.1.1.1.1.2 [|snmp] (DF)
13:35:01.4270305528 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(32)  .1.3.6.1.2.1.31.1.1.1.1.2="F"
13:35:01.4270368060 colinux.4012 > cisco-2620.snmp:  C=private 
GetRequest(32)  .1.3.6.1.2.1.31.1.1.1.1.6 [|snmp] (DF)
13:35:01.4270385641 cisco-2620.snmp > colinux.4012:  C=private 
GetResponse(32)  .1.3.6.1.2.1.31.1.1.1.1.6="S"
13:35:02.4270497226 colinux.4013 > cisco-2924.snmp:  C=private 
GetRequest(32)  .1.3.6.1.2.1.31.1.1.1.1.1 [|snmp] (DF)
13:35:02.4270517074 cisco-2924.snmp > colinux.4013:  C=private 
GetResponse(32)  .1.3.6.1.2.1.31.1.1.1.1.1="V"
13:35:02.4270599669 colinux.4013 > cisco-2924.snmp:  C=private 
GetRequest(32)  .1.3.6.1.2.1.31.1.1.1.1.3 [|snmp] (DF)
13:35:02.4270617223 cisco-2924.snmp > colinux.4013:  C=private 
GetResponse(32)  .1.3.6.1.2.1.31.1.1.1.1.3="F"

Rebooting the vm makes it work again, for 36 hours or so.

[root@colinux root]# rpm -qa | grep snmp
net-snmp-utils-5.1-2.1
net-snmp-5.1-2.1
php-snmp-4.3.8-1.1

coLinux 0.61

Anyone with like experience?

Glen 

Re: [coLinux-users] is it possible?

[Doctor B. <do...@gm...>]

Yes.  Of course gentoo is possible.  You can either download an image
file, or you can bootstrap with the coLinux tools.  Note:  I do not
know if the coLinux tools will work with the bleeding edge version of
Colinux 0.6.2-pre4.  I try to keep my system at stable levels, so the
next version of the coLinux tools will probably be released 5-7 days
after the 0.6.2 release.  I'm looking forward to the update in
coLinux, as it will use the 2.6 kernels.

I include bootstrapping instructions for installing gentoo with the
coLinux tools.  It should be pretty easy, if the networking works.

The X performance is not that great, but it isn't too bad either.  It
depends on your perspective.  You probably aren't going to play an
games over the X11 connection, but you should have no problems doing
things like web browsing and reading e-mail.  However, unless you
samba mount your windows directories, all you downloaded mail will be
saved on your virtual machine.  That might not be what you want.  One
viable alternative to samba mounting is to copy data with tar to a
block device.  With 0.6.1 I tend to experience file system errors
eventually do to improper shutdowns when I forget and logout of
Windows or such.  So occasionally backing up the data to a tar file
under windows is a very good idea.

                                      Bill





On Mon, 18 Oct 2004 01:32:09 +0200, Holger Krull <hol...@gm...> wrote:
> > Is it possible to install colinux on winxp, and use kmail
> > (kontakt) or evolution as mail client?
> 
> Yes.
> 
> > Is the network transparent for the mail client?
> 
> If you set it up that way.
> 
> > What about the X performance?
> 
> Usable. Feels like 10Mbit even over a 100MBit line. Latency still high.
> Using lbx makes things better a bit.
> 
> > Has anybody tried it with Gentoo? Any install guide? (Sorry,
> > I like Gentoo)
> 
> > How much disk space is required?
> 
> Depends on home much space your gentoo setup needs.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] is it possible?

[Holger K. <hol...@gm...>]

> Is it possible to install colinux on winxp, and use kmail
> (kontakt) or evolution as mail client?

Yes.

> Is the network transparent for the mail client?

If you set it up that way.

> What about the X performance? 

Usable. Feels like 10Mbit even over a 100MBit line. Latency still high. 
Using lbx makes things better a bit.

> Has anybody tried it with Gentoo? Any install guide? (Sorry,
> I like Gentoo)

> How much disk space is required?

Depends on home much space your gentoo setup needs.

[coLinux-users] is it possible?

[<ist...@fr...>]

Hello!

Sorry for the newbie question, but I've found nothing about
this:
Is it possible to install colinux on winxp, and use kmail
(kontakt) or evolution as mail client?
Is the network transparent for the mail client?
What about the X performance? 

Has anybody tried it with Gentoo? Any install guide? (Sorry,
I like Gentoo)
How much disk space is required?

Thanks for the answers...
Istvan

[coLinux-users] CIFS

[<2...@pe...>]

I think it'd be nice to have CIFS included in the snapshots and 
releases. I suggest it because I had to compile a kernel since 
I had various problems mounting shares with smbfs. It'd just 
hang after ~10-20 minutes with "smb_retry: signal failed [-3]" 
and lock everything trying to access /mnt (the share is mounted 
in a subdirectory of it). CIFS is working fine.

-- 
How to contact me - http://www.pervalidus.net/contact.html

Re: [coLinux-users] mkfile utility

[Mark W. <mar...@ma...>]

On 14 Oct 04, at 12:29, Henry Nestler wrote:

> Mark Whidby wrote:
> > I've doubled the size of my root filesystem from 2GB to 4GB using
> > Dan Slater's mkfile utility but what do I need to do in colinux to make
> > the filesystem appear as 4GB?
> > 
> > Forgive my cluelessness...
> 
> Sorry "mkfile" is unknown for me.
> Have you an filesystem on this image? (ext3)
> 
> Have you create only an empty image of 4GB and need help for copy files 
> from old image (2GB) into new image (4GB)?
> 
> Creat a new entry in colinux.config.xml for new image, such as:
> 
>   <block_device index="7" path="\DosDevices\C:\CoLinux\image-4gb.img"
>   enabled="true" />
> 
> Boot colinux from old image.
> Mount your new image and copy all files, but not other mount-points and 
> not the proc:
> 
>   # mkdir /tmp/4gb
>   # mount /dev/cobd7 /tmp/4gb
>   # cd /
>   # cp -ax * /tmp/4gb
>   # umount /tmp/4gb
>   # rmdir /tmp/4gb
> 
> Stop running colinux and reboot from new image.

Thanks for the suggestion. Mkfile is available from the wiki website
and it enlarges filesystem images in situ but doesn't do a resizefs
on the actual filesystem. Instead I got hold of topoenlarge (which is
also mentioned on wiki but the link is broken) which does an enlarge
and a resize in situ.


-- 
Mark Whidby
Faculty of Engineering and Physical Sciences

[coLinux-users] Re: mkfile utility

[Trevor B <tre...@us...>]

Mark Whidby <mark.whidby@...> writes:

> 
> I've doubled the size of my root filesystem from 2GB to 4GB using
> Dan Slater's mkfile utility but what do I need to do in colinux to make
> the filesystem appear as 4GB?
> 
> Forgive my cluelessness...
> 

After you extend the file, you need to extend the file-system. 
You can either do this from within colinux 
(start colinux with your new filesystem as a secondary 
filesystem eg /dev/cobd2 and run resize2fs /dev/cobd2) 
or from dos with the resize2fs.exe program 
(DOS copy available as part of the cygwin e2fsprogs package)

Trevor B

Re: [coLinux-users] mkfile utility

[Henry N. <Hen...@Ar...>]

Mark Whidby wrote:
> I've doubled the size of my root filesystem from 2GB to 4GB using
> Dan Slater's mkfile utility but what do I need to do in colinux to make
> the filesystem appear as 4GB?
> 
> Forgive my cluelessness...

Sorry "mkfile" is unknown for me.
Have you an filesystem on this image? (ext3)

Have you create only an empty image of 4GB and need help for copy files 
from old image (2GB) into new image (4GB)?

Creat a new entry in colinux.config.xml for new image, such as:

  <block_device index="7" path="\DosDevices\C:\CoLinux\image-4gb.img"
  enabled="true" />

Boot colinux from old image.
Mount your new image and copy all files, but not other mount-points and 
not the proc:

  # mkdir /tmp/4gb
  # mount /dev/cobd7 /tmp/4gb
  # cd /
  # cp -ax * /tmp/4gb
  # umount /tmp/4gb
  # rmdir /tmp/4gb

Stop running colinux and reboot from new image.

-- 
Henry Nestler

[coLinux-users] mkfile utility

[Mark W. <mar...@ma...>]

I've doubled the size of my root filesystem from 2GB to 4GB using
Dan Slater's mkfile utility but what do I need to do in colinux to make
the filesystem appear as 4GB?

Forgive my cluelessness...


-- 
Mark Whidby
Faculty of Engineering and Physical Sciences

Re: [coLinux-users] reiserfs error during boot, but I have xfs?

[Ian B. <ib...@gm...>]

Ok, I think what Brian was talking about is why are there errors at
all here. I have a feeling that the way the new 2.6.8 kernel works is
that it doesn't have any filesystem drivers compiled into it, but
instead loads them at boot time. The only way to do that is by loading
an initrd and testing your filesystem for all the different filesystem
types. Hence, the error messages. (I.E. its trying to fsck-like-test
each filesystem driver against your partition, and the only one that
works, is the one that loads). Its a rather brute-force attack, but
its quite good if you want to ship out a generic kernel to a whole
slew of systems and insure that it works on all of them.

Ian

On Wed, 13 Oct 2004 02:23:15 +0100, Nuno Lucas <ml-...@xp...> wrote:
> Brian Krusic, dando pulos de alegria, escreveu :
> [...]
> > FAT: bogus logical sector size 0
> > UMSDOS: msdos_read_super failed, mount aborted.
> > FAT: bogus logical sector size 0
> > FAT: bogus logical sector size 0
> > sh-2021: reiserfs_read_super: can not find reiserfs on cobd(117,7)
> > Kernel panic: VFS: Unable to mount root fs on 75:07
> >
> > My partition layout (being XFS fs);
> [...]
> 
> The current linux kernel has XFS as a module. When it tries to open the
> root partition the modules aren't loaded yet, so it fails (after trying
> the file systems it knows about).
> 
> The solution would be to either use a non-XFS image as root or
> create an initrd image that will allow the xfs module to be loaded.
> 
> Another option is compiling a new kernel with xfs linked into.
> 
> --
> Regards,
> ~Nuno Lucas
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>