colinux-users — coLinux users mailing list

[coLinux-users] Llenate de imagen y sonido

[<ima...@mu...>]

Untitled Document
    =20
    =20
      Al mejor precio, comprobalo!!

-------------------------------------------------------------------------=
-
      Adem=E1s, mir=E1 estas ofertas de: C=E1maras
            Digitales  Accesorios
            p/ Celulares=20
            MP3
            MP4 Guitarras
            El=E9ctricas=20
    =20

      En Multicompras respetamos su privacidad.
      Para darse de baja de futuras comunicaciones, por favor pulse =
aqu=ED.
      =20
    =20

  

Re: [coLinux-users] new PHAkadRMA

[Sosigenes A. <li...@ra...>]

Hi,

Get your meds from our site because it costs much less.

http://www.zo*nrx.com

Remove "*" to make the link working!

--

spiritedly about the World Cup.
Its got to be Ireland,  said Charlie thickly, through a mouthful of
potato. They flattened Peru in the semifinals. 

[coLinux-users] job/trabajo

[Maria S <Le...@ni...>]

Buenos Dias,

Nuestra compania internacional ofrece el trabajo.
Podras ganar 150-300 Euros por dia.
Esto es legal y es seguro.

Nuestras exigencias:
1) Debes vivir en la Espana;
2) Debes tener el tiempo libre por la manana;
3)) Debes ser mas mayor cerca de 20 anos.

Para el recibo de las instrucciones respondan
solamente a este email: BB...@KM...

Un Saludo,
Maria

[coLinux-users] job/trabajo

[Maria S <Fr...@ci...>]

Buenos Dias,

Nuestra compania internacional ofrece el trabajo.
Podras ganar 150-300 Euros por dia.
Esto es legal y es seguro.

Nuestras exigencias:
1) Debes vivir en la Espana;
2) Debes tener el tiempo libre por la manana;
3)) Debes ser mas mayor cerca de 20 anos.

Para el recibo de las instrucciones respondan
solamente a este email: BB...@KM...

Un Saludo,
Maria

Re: [coLinux-users] Allocation of pty refused by openssh server

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

make sure /dev/ptmx is chmod 666

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of =
Ren=E9
> Berber
> Sent: 28 January 2007 17:25
> To: col...@li...
> Subject: Re: [coLinux-users] Allocation of pty refused by openssh =
server
>=20
>=20
> Claude Le D=FB wrote:
>=20
> > Colinux 0.7.1 - Fedora Core5 2006.8 from sourceforge - Putty - Xming
> ------------------^^^^^^^^^^^^^^^^^^^
> This is the problem...
>=20
> > I spend little time to have this set working with Windows XP SP2.
> > I added some packages including kdebase, openssh,server-ssh, =
client-ssh=20
> > using yum.
> > All works fine except one thing I could not fix.
> > I cannot get a connexion with a pty with Putty (Putty on Windows or=20
> > Colinux to openssh on Colinux).
> > "Server refused to allocate pty".
> > 1) I created all  /dev/pty's with MAKEDEV in the colinux /dev =
directory=20
> > but it was not sufficient
> > 2) Launching sshd with "-d" option shows that the function "openpty" =
is=20
> > not available on the Fedora root-fs (?)
> >=20
> > I tried to find which package brings this libary without succes.
> > Can you tell me if I made a mistake? Is there an update to do?
>=20
> This solved the problem for me:
>=20
> http://permalink.gmane.org/gmane.linux.colinux.general/3732
>=20
> --=20
> Ren=E9 Berber
>=20
>=20
> =
-------------------------------------------------------------------------=

> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to=20
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] Allocation of pty refused by openssh server

[<r.b...@co...>]

Claude Le D=FB wrote:

> Colinux 0.7.1 - Fedora Core5 2006.8 from sourceforge - Putty - Xming
------------------^^^^^^^^^^^^^^^^^^^
This is the problem...

> I spend little time to have this set working with Windows XP SP2.
> I added some packages including kdebase, openssh,server-ssh, client-ssh=
=20
> using yum.
> All works fine except one thing I could not fix.
> I cannot get a connexion with a pty with Putty (Putty on Windows or=20
> Colinux to openssh on Colinux).
> "Server refused to allocate pty".
> 1) I created all  /dev/pty's with MAKEDEV in the colinux /dev directory=
=20
> but it was not sufficient
> 2) Launching sshd with "-d" option shows that the function "openpty" is=
=20
> not available on the Fedora root-fs (?)
>=20
> I tried to find which package brings this libary without succes.
> Can you tell me if I made a mistake? Is there an update to do?

This solved the problem for me:

http://permalink.gmane.org/gmane.linux.colinux.general/3732

--=20
Ren=E9 Berber

[coLinux-users] Allocation of pty refused by openssh server

[<led...@ne...>]

Colinux 0.7.1 - Fedora Core5 2006.8 from sourceforge - Putty - Xming

Hi,

I spend little time to have this set working with Windows XP SP2.
I added some packages including kdebase, openssh,server-ssh, client-ssh 
using yum.
All works fine except one thing I could not fix.
I cannot get a connexion with a pty with Putty (Putty on Windows or 
Colinux to openssh on Colinux).
"Server refused to allocate pty".
1) I created all  /dev/pty's with MAKEDEV in the colinux /dev directory 
but it was not sufficient
2) Launching sshd with "-d" option shows that the function "openpty" is 
not available on the Fedora root-fs (?)

I tried to find which package brings this libary without succes.
Can you tell me if I made a mistake? Is there an update to do?

Thanks

Claude Le Du

(for information, in order to have passwords available with Fedora C5 I 
had also to unistall et reinstall craklib-dicts in the root-fs)

[coLinux-users] Very interesting developments

[Zachary K. <zk...@zk...>]

Howdy,
     I've spent the past while trying to figure out tricks for getting
things like CoLinux sound support to work.  I realize this isn't exactly
new--but I just found an application for it which I am not sure that
anyone's explored before.
     Flite, Festival, and the like are some speech engines for Linux.  I
succeeded recently in using Enlightened Sound Daemon on Windows to
redirect that output to the Windows sound card--both on my laptop,
without CoLinux, and on the local Pc which does have it.
I essentially used the esddsp program with the server argument a few
times until it just worked, and now it seems to handle consistently.  
I consider this rather remarkable news mostly because I am a blind
coLinux user, who is very interested in possibilities of Linux
accessibility.  This is just one of those, in my opinion.
Any thoughts on it?
Thanks,
Zack.

Re: [coLinux-users] VirtualBox

[Jonathan P. <jon...@gm...>]

Sort of, yes.  I've actually just started using it myself, so I don't 
know that much about it.  Thus far, it does not seem all that promising, 
esp. since getting any sort of decent performance out of a Linux VM 
requires installing new kernel modules to the guest.  I'll continue 
working with it, though, and I'll try to let this list know what I find.

Jon

> ------------------------------
>
> Message: 2
> Date: Fri, 26 Jan 2007 00:48:06 +0900
> From: Jun OKAJIMA <ok...@di...>
> Subject: [coLinux-users] VirtualBox
> To: col...@li...
> Message-ID: <200...@bb...>
> Content-Type: text/plain; charset=us-ascii
>
>
> http://www.virtualbox.org/
>
> Can this be a GPL equivalent of VMware?
>
>            --- Okajima, Jun. Tokyo, Japan.

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

[Wisut H. <wi...@gm...>]

Add colinux-daemon to DEP exception don't solve my problem. What
colinux version are you using in vista ? Can you write a step-by-step
installation guide for me ?

Have you ever try calling "colinux-daemon kernel=vmlinux
initrd=initrd.gz root=/dev/ram0" (it will boot to the initrd system
with busybox shell) and then "halt" in that linux shell ?


On 1/26/07, George P Boutwell <geo...@gm...> wrote:
> I think I had similiar problems testing on Vista.  I think I solved it
> by adding colinux-daemon.exe and linux.sys to the Vista's Software DEP
> exception list.  I forget where that's at speifically, but it's like
> under start-up options or something.
>
> Have you tried that?
>
> George
>
> On 1/23/07, Wisut Hantanong <wi...@gm...> wrote:
> > I do install coLinux-0.7.1-20070101 with default option and run
> >
> > "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
> >
> > from the command prompt . coLinux is running fine. I can see the
> > initrd file system and do "ls", "cd" command and so on.
> >
> > BUT after call "halt" command it is seem that coLinux was shutdown. I
> > saw something like "System Halted" and then suddenly there is BLUE
> > SCREEN of death say some thing like
> >
> > STOP: 0x0000008e (0xC0000046 ....
> >
> > I wish I can provide you more infomation but I don't know how to do.
> > Please suggess me the way to capture the error if you want it.
> >
> > Error always happen after "halt" command was called.
> > I am using windows vista rtm ultimate edition.
> >
> > Wisut.
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
>
>
> --
> George
>

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

[George P B. <geo...@gm...>]

I think I had similiar problems testing on Vista.  I think I solved it
by adding colinux-daemon.exe and linux.sys to the Vista's Software DEP
exception list.  I forget where that's at speifically, but it's like
under start-up options or something.

Have you tried that?

George

On 1/23/07, Wisut Hantanong <wi...@gm...> wrote:
> I do install coLinux-0.7.1-20070101 with default option and run
>
> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
>
> from the command prompt . coLinux is running fine. I can see the
> initrd file system and do "ls", "cd" command and so on.
>
> BUT after call "halt" command it is seem that coLinux was shutdown. I
> saw something like "System Halted" and then suddenly there is BLUE
> SCREEN of death say some thing like
>
> STOP: 0x0000008e (0xC0000046 ....
>
> I wish I can provide you more infomation but I don't know how to do.
> Please suggess me the way to capture the error if you want it.
>
> Error always happen after "halt" command was called.
> I am using windows vista rtm ultimate edition.
>
> Wisut.
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>


-- 
George

Re: [coLinux-users] VirtualBox

[Jun O. <ok...@di...>]

>> http://www.virtualbox.org/
>> 
>> Can this be a GPL equivalent of VMware?
>> 
>Yes. Looks so. But the usb support is missing from the GPL Version.
>

I hope this could make VMware GPLed.

              --- Okajima, Jun. Tokyo, Japan.

Re: [coLinux-users] VirtualBox

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

Jun OKAJIMA schrieb:
> http://www.virtualbox.org/
> 
> Can this be a GPL equivalent of VMware?
> 
Yes. Looks so. But the usb support is missing from the GPL Version.

[coLinux-users] VirtualBox

[Jun O. <ok...@di...>]

http://www.virtualbox.org/

Can this be a GPL equivalent of VMware?

           --- Okajima, Jun. Tokyo, Japan.

Re: [coLinux-users] Fwd: coLinux-0.7.1-20070101 crash my Vista after linux halted.

[Wisut H. <wi...@gm...>]

I think I should share this ugly workaround to the group. And yes the
halt problem exist only under Vista. I do try the same on my laptop
with windows xp and there is no problem. Thank to Norton Ghost allowed
me to restore my Vista without reinstalling.

This kind of mess is what normally happened when you move to Vista. I
wish you make coLinux be a Vista Ready soon. :)

Wisut Hantanong

On 1/24/07, Henry Nestler <Hen...@ar...> wrote:
> Wisut Hantanong wrote:
> > Sorry if I make you confuse. The JPG file is from my P4 desktop. Other
> > files are from my laptop.
> >
> > Unfortunately I have no much time to try coLinux. Now I (have to) am
> > using Virtual PC 2007 Beta instead for my working. Because I don't
> > want to back to windows XP. coLinux on my XP has no problem.
> >
> > FYI I use linux to develop the embedded system firmware so I only need
> > the linux's core system and some tools (gcc, tftp, telnet, ...) in my
> > work. And I can tell you that you make a wonderful linux framework. I
> > found that your coLinux is faster than one in VPC. :)
>
> I use coLinux for developing embedded systems at work.
> http://www.ssv-embedded.de/ssv/english/home.htm
> http://www.terminal-systems.de/colinux1.htm  (sorry german only)
>
> > Now I am deciding between working in coLinux without "halt" command or
> > use one VPC. I hate killing colinux-daemon without calling "poweroff,
> > init 0, halt".
> >
> > Hope you can fix this little mess soon.
>
> For a ugly workarrount: Locate the "halt" or real "poweroff" in the
> initscripts.  There are mostly some steps with "umount ... sync .. mount
> / -o ro".  After this insert two lines:
>   echo "colinux halt now, or press ENTER"
>   read junk
> Than you can shutdown without real power off and kill the colinux-daemon
> after yousee the message.  CoLinux you can terminate in the FLTK menu.
>
> Can you say: The halt problem exist only under Vista?
> I will install it again and check next weekend.
>
> > In future if you want to chat with me online, I am on windows live
> > messenger with contact #####
>
> I have no such accounts.  I'm more offline.
>
> --
> Henry Nestler
>

Re: [coLinux-users] ArchLinux Serial Devices?

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

Hello Zack,

serial /dev/ttyS0 is working in ArchLinux-0.7.2-ext3-512mb, directly out 
of the archive from sourceforge.  Tested with coLinux 0.7.1-20070101 and 
a GSM modem (mobile fon) on serial port under XP.

Command line (long single line):
colinux-daemon kernel=vmlinux mem=32 initrd=initrd.gz 
hda1=ArchLinux-072-ext3.fs hda2=swap.img hdc=\Device\CdRom0 cofs1=. 
root=/dev/hda1 eth0=slirp ttys0=COM1,"BAUD=9600 PARITY=n DATA=8 STOP=1 
dtr=on rts=on"

-- 
Henry Nestler

Re: [coLinux-users] ArchLinux Serial Devices?

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

Hello Zachary,
> Hello,
> I'm interested in responding to a suggestion from a list member here
> sent to me privately.  That suggestion is to test the CoLinux support
> for Braille terminals and displays--which is something I could possibly
> accomplish with the new serial daemon in 0.7.1.
> ArchLinux doesn't seem to have /dev/ttys0 or any ttys devices, but
> rather ttyS--which it claims to be for serial terminals.  Should I
> manually mknod the former, or is there an easier way to get them?  
> Thanks,
> Zack.

What is the different between your ArchLinux and the image file 
ArchLinux-0.7.2-ext3-512mb.7z from sourceforge.net?

http://downloads.sourceforge.net/colinux/ArchLinux-0.7.2-ext3-512mb.7z?download
I have ArchLinux downloaded from sourceforge.net, and there exist 
/dev/ttyS0, it's a link to /dev/tts/0 and should work.
   [root@myhost ~]# ls -l /dev/ttyS*
   lrwxrwxrwx 1 root root 5 Jul 26 05:39 /dev/ttyS0 -> tts/0
   [root@myhost ~]# ls -l /dev/tts/0
   crw-rw---- 1 root tty 4, 64 Jul 22  2006 /dev/tts/0
The device exist after boot.  Have not tested it.  Have no serial port 
and no USB adapter here in this time.

For CoLinux add these or similars parameters to your configuration:
   ttys0=COM1,"BAUD=115200 PARITY=n DATA=8 STOP=1 dtr=on rts=on"
The full command reference is in this file (starts with "ttysX"): 
http://www.henrynestler.com/colinux/source/0.7.1-doc/colinux-daemon.txt
Mostly of arguments are still forwarded to the Windows command "MODE".

Inside CoLinux you should than use /dev/ttyS0.
Remember: The Windows config needs ttys0 and inside Linux it's ttyS0, 
the difference is the lower and upper letter.

Have you a Braille Terminal and is working under Windows?  My sample 
"COM1" should replace with your Windows device name.  For 
USB-Serial-Adapters you can also use the Windows internaly name that 
beginning with backslashes, for sample "\\.\COM1"

-- 
Henry Nestler

[coLinux-users] ArchLinux Serial Devices?

[Zachary K. <zk...@zk...>]

Hello,
I'm interested in responding to a suggestion from a list member here
sent to me privately.  That suggestion is to test the CoLinux support
for Braille terminals and displays--which is something I could possibly
accomplish with the new serial daemon in 0.7.1.
ArchLinux doesn't seem to have /dev/ttys0 or any ttys devices, but
rather ttyS--which it claims to be for serial terminals.  Should I
manually mknod the former, or is there an easier way to get them?  
Thanks,
Zack.

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

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

Henry Nestler schrieb:
> Holger Krull wrote:
>> Wisut Hantanong schrieb:
>>> I do install coLinux-0.7.1-20070101 with default option and run
>>>
>>> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
>>>
>>
>> root=/dev/ram0 seems a little odd. What do you expect to be there?
>>
>> Usually you would have something like:
>> root=/dev/cobd0
>> cobd0=E:\colinux_test\filesystem.img
> 
> initrd=initrd.gz root=/dev/ram0
> is ok for running a minimal linux from intrd.  The root filesystem is
> the initrd self.
> 
Then i guess, this is the nx-Bit problem.
Wisut, which processor do you use?

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

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

Holger Krull wrote:
> Wisut Hantanong schrieb:
>> I do install coLinux-0.7.1-20070101 with default option and run
>>
>> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
>>
> 
> root=/dev/ram0 seems a little odd. What do you expect to be there?
> 
> Usually you would have something like:
> root=/dev/cobd0
> cobd0=E:\colinux_test\filesystem.img

initrd=initrd.gz root=/dev/ram0
is ok for running a minimal linux from intrd.  The root filesystem is 
the initrd self.

-- 
Henry Nestler

Re: [coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

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

Wisut Hantanong schrieb:
> I do install coLinux-0.7.1-20070101 with default option and run
> 
> "colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"
> 

root=/dev/ram0 seems a little odd. What do you expect to be there?

Usually you would have something like:
root=/dev/cobd0
cobd0=E:\colinux_test\filesystem.img

[coLinux-users] coLinux-0.7.1-20070101 crash my Vista after linux halted.

[Wisut H. <wi...@gm...>]

I do install coLinux-0.7.1-20070101 with default option and run

"colinux-daemon kernel=vmlinux initrd=initrd.gz root=/dev/ram0"

from the command prompt . coLinux is running fine. I can see the
initrd file system and do "ls", "cd" command and so on.

BUT after call "halt" command it is seem that coLinux was shutdown. I
saw something like "System Halted" and then suddenly there is BLUE
SCREEN of death say some thing like

STOP: 0x0000008e (0xC0000046 ....

I wish I can provide you more infomation but I don't know how to do.
Please suggess me the way to capture the error if you want it.

Error always happen after "halt" command was called.
I am using windows vista rtm ultimate edition.

Wisut.

Re: [coLinux-users] Introduction and a few questions

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

Hello Zachary,

> Hello,
>      First a few words of introduction on my part: I'm a blind computer
> user who has had an interest in Linux ever since I first found out about
> it some six or so years back.
> The main problem I've had with Linux is that for the most part the
> hardware I have doesn't make using speech synthesizers and the like to
> do independant installations very easy.
> My computer doesn't come with a serial port--and the only synthesizer I
> have that would let me do that needs one.  USB to serial doesn't seem to
> work, etc.  I settled on using CoLinux and using my existing Windows
> screen reader with the NT console--for some reason the FLTK doesn't work
> so well with it, I don't know why.

NT console is a real console with text only output.  Copy and paste 
works directly from Windows.  All other programs with copy & paste can 
read the text from this console.

The FLTK console is a graphic application with a drawed text in the 
client area.  That's why you can not copy and past, and no put it to a 
synthesizer.

>      Now to my questions...I have taken a real liking to ArchLinux: it's
> simple, and very useable for what I'd like so far.  
> However, the problem comes when upgrading: the latest upgrades recommend
> that I use kernel 2.6.17 to take advantage of UDev support.  I can work
> around this, but really I wonder if there's an advantage to using it?

The image file for ArchLinux was modifired to run without UDev.  There 
exist a fallback for coLinux kernels without UDev.  I can not say about 
it's using Udev or not.  I have tested the ArchLinux image with coLinux 
Kernel 2.6.17, it's running nice for my basics test.  The ArchLinux 
image file is indipend from coLinux version and should run with all 
known coLinux kernels 2.6

With Udev the directory /dev/ has more entries, I'm afraid.  The 
fallback creates only the most wanted devices tty*, cofs*, null, zero 
and some other basics.

> If so...Is it possible to use 2.6.18 with CoLinux, and if that's
> possible how would I compile it, and patch it?  Would an initrd be
> enough?

After anybody would upgrade our coLinux kernel patches from 2.6.17 to 
2.6.18, than a new file vmlinux-modules.tar.gz would enought.  Initrd 
will install the modules from that file.

CoLinux has very hard changes on the kernel low level memory mamagment, 
so it's not easy to upgrade, and you can not use an older patch for 
newer kernel.

-- 
Henry

Re: [coLinux-users] Introduction and a few questions

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

George P Boutwell schrieb:
>> The notes for the 0.7.1 test release say that it has been tested with newer kernels.
>> http://sourceforge.net/project/shownotes.php?release_id=476227&group_id=98788
>>
>> I can't help with compiling, sorry.
>>   
> Yes. the Release Notes mentions 2.6.17 and 2.6.18 BUT as Linux as Host
> (ie those number are the host kernel numbers).  Zack's situation is an
> Windows as host, and so the guest kernel is the version we are
> discussing.  0.7.1 is still only a 2.6.12 and that is all that will be
> supported for it, unfortunately.

Sorry to read that, i misunderstood the release notes.

Re: [coLinux-users] Introduction and a few questions

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

> However, the problem comes when upgrading: the latest upgrades recommend
> that I use kernel 2.6.17 to take advantage of UDev support.  I can work
> around this, but really I wonder if there's an advantage to using it?
> If so...Is it possible to use 2.6.18 with CoLinux, and if that's
> possible how would I compile it, and patch it?  Would an initrd be
> enough?

The notes for the 0.7.1 test release say that it has been tested with newer kernels.
http://sourceforge.net/project/shownotes.php?release_id=476227&group_id=98788

I can't help with compiling, sorry.