Re: Fwd: Re: [coLinux-users] Port of voyage linux to coLinux.

[Henry N. <Henry.Ne@Arcor.de>]

n schembr schrieb:
> --- Henry Nestler <Henry.Ne@Arcor.de> wrote:
> 
>> n schembr wrote:
>>> It not that ugly. :) voyage linux is a read only
>> file
>>> system. This make it safe for compact Flash
>> installs.
>>> I've used it with real hardware and not seen the
>> login
>>> issue. 
>> Interesting.  Please would you comair (vimdiff) the
>> coLinux kernel 
>> config with the native boot?  Perhaps you need a
>> special option?
> 
> Can you explain a little more about this. 
> mount debian.fs and voyage.fs and vimdiff what?

No.

You have a kernel configuration for native running as base for 
compairing.  It's in kernel source the file .config.  Sometimes readable 
under /proc/config.gz

The other kernel config is inside coLinux sources and also readable in 
running colinux /proc/config.gz

Unpack both files and comair it with diff or vimdiff or simple by your 
human eyes ;-)  You should locking for any special thing that is enabled 
for voyage linux and not activated by coLinux.  But please only some 
software addons or libraries.  Not all the other hardware drivers.

The question is: Need voyage any specials from kernel, to working better 
in your case?

> http://wiki.colinux.org/cgi-bin/VoyageLinux is a work
> in progress, but it's stable to "poor mans vpn."

Yeha, have seen it.  Is 
http://voyage.hk/download/voyage/voyage-0.2pre4.tar.gz the complete 
"voyage"?

Or it is an add on to an existing Debian?

Im not understand: I need the Debian-3.0r2.ext3-mit-backports.1gb (more 
as 200MB ... 1GB) only as base for creation the destination on the stick 
(64MB)?

If you have such image for running on a 64MB stick, I would not do all 
this again.  Can I run your image file.  coLinux Image files are 
portable from one to other host without any changes.

-- 
Henry Nestler