From: Giacomo <ky...@ti...> - 2006-02-10 15:05:44
|
Hi everybody, Is it possible to get net windows information from colinux? I mean, I would like to export DISPLAY variable automatically at colinux startup, but I don't know tap IP address (one user can modify it). How can I do this? thanks -- Giacomo |
From: George P B. <geo...@gm...> - 2006-02-10 15:10:29
|
On 2/10/06, Giacomo <ky...@ti...> wrote: > Is it possible to get net windows information from colinux? I mean, I > would like to export DISPLAY variable automatically at colinux startup, > but I don't know tap IP address (one user can modify it). How can I do th= is? You can pass DISPLAY on the command-line and it'll be passed into the shells and work... If the ip could change after colinux is booted, then maybe pass an hostname instead of an IP? -- George |
From: Giacomo <ky...@ti...> - 2006-02-10 15:24:21
|
George P Boutwell ha scritto: > You can pass DISPLAY on the command-line and it'll be passed into the > shells and work... > If the ip could change after colinux is booted, then maybe pass an > hostname instead of an IP? Like "tap-32"? Is it possible to pass it? -- Giacomo |
From: Giacomo <ky...@ti...> - 2006-02-17 23:15:37
|
George P Boutwell ha scritto: > You can pass DISPLAY on the command-line and it'll be passed into the > shells and work... How? I'm trying without success...=((( -- Giacomo |
From: Holger K. <hol...@gm...> - 2006-02-10 15:14:46
|
Giacomo schrieb: > Hi everybody, > Is it possible to get net windows information from colinux? I mean, I > would like to export DISPLAY variable automatically at colinux startup, > but I don't know tap IP address (one user can modify it). How can I do > this? My way around this problem is to use a dhcp Server to get a IP Adress and tell that server to update the name server. So DISPLAY can be set to a fixed value. |
From: Giacomo <ky...@ti...> - 2006-02-10 15:24:32
|
Holger Krull ha scritto: > My way around this problem is to use a dhcp Server to get a IP Adress > and tell that server to update the name server. So DISPLAY can be set to > a fixed value. Use dhclient into colinux to get IP? Or something else? I didn't understand very well what do you mean? -- Giacomo |
From: Holger K. <hol...@gm...> - 2006-02-10 15:37:17
|
Giacomo schrieb: > Holger Krull ha scritto: >> My way around this problem is to use a dhcp Server to get a IP Adress >> and tell that server to update the name server. So DISPLAY can be set >> to a fixed value. > > Use dhclient into colinux to get IP? Or something else? I didn't > understand very well what do you mean? > If you have an dhcp Server, a nameserver in your network and if you are not using the same image on different windows computers you can set DISPLAY within colinux to a name instead of an ip adress. Like DISPLAY=mywindows.local.domain:0.0 . Windows can update the nameserver itself or the dhcp Server can do that. Other method i can think of is to set a kernel parameter like: colinux-daemon.exe @config.conf DISPLAY=alimana and scan dmesg output for it. |
From: Giacomo <ky...@ti...> - 2006-02-17 22:16:38
|
Holger Krull ha scritto: > Other method i can think of is to set a kernel parameter like: > > colinux-daemon.exe @config.conf DISPLAY=alimana > > and scan dmesg output for it. Can You explain me better this concept? I tried to run colinux with this script but it crushed...=( -- Giacomo |
From: Holger K. <hol...@gm...> - 2006-02-18 17:39:09
|
Giacomo schrieb: > Holger Krull ha scritto: >> Other method i can think of is to set a kernel parameter like: >> >> colinux-daemon.exe @config.conf DISPLAY=alimana >> >> and scan dmesg output for it. > > Can You explain me better this concept? I tried to run colinux with this > script but it crushed...=( I don't know what you mean with script. There is none here. I meant that you will see anything you add on the commandline while starting colinux-daemon in the kernel log in colinux. So it would be possible to extract the info from there. I tested that dmesg will show the DISPLAY=name setting but didn't write an actual script to extract it. |
From: Giacomo <ky...@ti...> - 2006-02-18 18:10:46
|
Holger Krull wrote: > I don't know what you mean with script. There is none here. > I meant that you will see anything you add on the commandline while > starting colinux-daemon in the kernel log in colinux. So it would be > possible to extract the info from there. I tested that dmesg will show > the DISPLAY=name setting but didn't write an actual script to extract it. If I use that code colinux crushes...=( How can I pass parameters to colinux daemon? -- Giacomo |
From: Holger K. <hol...@gm...> - 2006-02-18 18:18:34
|
Giacomo schrieb: > Holger Krull wrote: > > I don't know what you mean with script. There is none here. >> I meant that you will see anything you add on the commandline while >> starting colinux-daemon in the kernel log in colinux. So it would be >> possible to extract the info from there. I tested that dmesg will show >> the DISPLAY=name setting but didn't write an actual script to extract it. > > If I use that code colinux crushes...=( > How can I pass parameters to colinux daemon? > Add them after the path to the configfile. Write how you start your colinux usually, and how you started it so that it crashed. |
From: Giacomo <ky...@ti...> - 2006-02-18 18:25:57
|
Holger Krull wrote: > Add them after the path to the configfile. Write how you start your > colinux usually, and how you started it so that it crashed. Before crush: colinux-daemon.exe -c config.xml After; colinux-daemon.exe -c config.xml DISPLAY=192.168.0.1:0 -- Giacomo |
From: George P B. <geo...@gm...> - 2006-02-18 21:51:58
|
On 2/18/06, Giacomo <ky...@ti...> wrote: > Holger Krull wrote: > > Add them after the path to the configfile. Write how you start your > > colinux usually, and how you started it so that it crashed. > > Before crush: > colinux-daemon.exe -c config.xml > > After; > colinux-daemon.exe -c config.xml DISPLAY=3D192.168.0.1:0 in config.xml, there is a <bootparams>root=3D/dev/<whatever></bootparams> Add DISPLAY=3D<ip> to this line, ie: <bootparams>root=3D/dev/cobd0 DISPLAY=3D192.168.0.1:0</bootparams> And that's all you should have to do... boot coLinux and when you run set from the shell after logging in DISPLAY should be set. If that method doesn't work well for your situation, use the command-line 'config' in 0.6.3 instead of the config file... (read aboug the command-line in README.txt) but basically: colinux-daemon kernel=3Dvmlinux mem=3D64 cobd0=3Drootfs cobd1=3Dswapfs root=3D/dev/cobd0 DISPLAY=3D192.168.0.1:0 George -- George |
From: Giacomo <ky...@ti...> - 2006-02-19 00:05:12
|
George P Boutwell ha scritto: > in config.xml, there is a <bootparams>root=/dev/<whatever></bootparams> > Add DISPLAY=<ip> to this line, ie: > > <bootparams>root=/dev/cobd0 DISPLAY=192.168.0.1:0</bootparams> Right now It doesn't crush but I don't have DISPLAY setted. I have to see the "/proc/cmdline" file to get DISPLAY value... -- Giacomo |
From: Holger K. <hol...@gm...> - 2006-02-18 18:56:16
|
Giacomo schrieb: > Holger Krull wrote: >> Add them after the path to the configfile. Write how you start your >> colinux usually, and how you started it so that it crashed. > Sorry, this method doesn't work with 0.6. I didn't know that. I only tested with 0.7. So you should use a cofs mount to transfer the information. |
From: George P B. <geo...@gm...> - 2006-02-18 21:54:21
|
On 2/18/06, Holger Krull <hol...@gm...> wrote: > > Sorry, this method doesn't work with 0.6. I didn't know that. I only test= ed with 0.7. > So you should use a cofs mount to transfer the information. > 0.6.2 and above have command-line support that looks like the 0.7 config file, however, their config file is still the xml config file.=20 You can use the bootparams node in the xml config, or use the command-line and not use a config file at all, those are pretty much your options ins 0.6.2 and above. -- George |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-02-10 20:16:09
|
Giacomo wrote: > Hi everybody, > Is it possible to get net windows information from colinux? I mean, I > would like to export DISPLAY variable automatically at colinux startup, > but I don't know tap IP address (one user can modify it). How can I do > this? This could be a good feature in /proc directory for next versions. Currently you can do this with sripts. (An idea from David Solomon) Before you starts coLinux, or in the script where you start linux console, redirect output from "ipconfig" or "ipconfig /ALL" into a file. Put this file into a directory, where you have read access with cofs, for sample C:\windows\temp, or C:\coLinux. Configure a cofs to this directory. Please not the complete drive C:\, this is a big user risk. Now inside colinux: Mount this cofs readonly or use a mount you have always mounted with cofs. Grep the file for IP adress of TAP device. For this you need some regexp to the text "TAP-Win32 Adapter V8 (coLinux)" and followd address one or two lines later. Think a good sed command will find it. I have renamed my TAP connection into "TAP-Colinux". This is a typical output from ipconfig for TAP on german windows. >>> snip >>> Ethernetadapter TAP-Colinux: Verbindungsspezifisches DNS-Suffix: Beschreibung. . . . . . . . . . . : TAP-Win32 Adapter V8 (coLinux) <<<=== this is the text trigger Physikalische Adresse . . . . . . : 00-FF-CB-66-22-15 DHCP aktiviert. . . . . . . . . . : Nein IP-Adresse. . . . . . . . . . . . : 192.168.4.200 <<=== this you need Subnetzmaske. . . . . . . . . . . : 255.255.255.0 Standardgateway . . . . . . . . . : <<< snip <<< -- Henry Nestler |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-02-10 20:39:50
|
If you login to coLinux with ssh, then you can use this shell command: set | grep "SSH_CONNECTION" This give current IP from windows side of tap ;-) -- Henry Nestler |
From: Giacomo <ky...@ti...> - 2006-02-10 23:31:57
|
Henry Nestler ha scritto: > Before you starts coLinux, or in the script where you start linux > console, redirect output from "ipconfig" or "ipconfig /ALL" into a file. There is a problem...before I start coLinux the tap driver doesn't have IP (and doesn't exist in "ipconfig" command). -- Giacomo |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-02-12 15:02:25
|
Giacomo schrieb: > Henry Nestler ha scritto: >> Before you starts coLinux, or in the script where you start linux >> console, redirect output from "ipconfig" or "ipconfig /ALL" into a file. > > There is a problem...before I start coLinux the tap driver doesn't have > IP (and doesn't exist in "ipconfig" command). Hups, Yes. I forgotten. -- Henry |
From: Fred C. I. <fr...@gi...> - 2006-02-14 20:42:55
|
I know this is a big evil thing to try, but I'm attempting to install SuSE10 onto a new partition (file) via colinux... Good news is, I was able to get the installation software started via this conf file with 0.7.1-hn8: kernel=vmlinux # The default kernel cobd0=f:\coLinux\root-fs\filesystem\suse10_4095Mb cobd1=f:\coLinux\root-fs\swap\newswap_512Mb cobd2=d:\suse10\SUSE-10.0-CD-OSS-i386-GM-CD1.iso cobd3=e:\ initrd=d:\suse10\initrd mem=128 eth0=tuntap,"coLinux TAP" root=/dev/cobd2 Now, for some reason (perhaps because the initrd is the one off of the install CD) the root filesystem /dev/cobd2 is not loaded. When I try to install with the 'harddrive' option, I cannot mount any of the cobd devices. I try loading file system modules, but I get this error (e.g.): fat: disagrees about version of symbol struct_module I gather this is because initrd is SuSE10 and the kernel is colinux. How can I 'fake out' the installer to get some of the cobd devices mounted? I'm so close I can taste it!!! Fred |
From: George P B. <geo...@gm...> - 2006-02-17 02:57:07
|
On 2/14/06, Fred Calef III <fr...@gi...> wrote: > > I know this is a big evil thing to try, but I'm attempting to install > SuSE10 onto a new partition (file) via colinux... > > Good news is, I was able to get the installation software started via > this conf file with 0.7.1-hn8: > > kernel=3Dvmlinux # The default kernel > cobd0=3Df:\coLinux\root-fs\filesystem\suse10_4095Mb hda1=3Df:\coLinux\root-fs\filesystem\suse10_4095Mb > cobd1=3Df:\coLinux\root-fs\swap\newswap_512Mb hda2=3Df:\coLinux\root-fs\swap\newswap_512Mb > cobd2=3Dd:\suse10\SUSE-10.0-CD-OSS-i386-GM-CD1.iso hdc=3Dd:\suse10\SUSE-10.0-CD-OSS-i386-GM-CD1.iso > cobd3=3De:\ ? cofs0=3De:\, maybe? > initrd=3Dd:\suse10\initrd This should be fine. If you really must/need modules to work loop mount this and extract coLinux's vmlinux-modules.tar.gz file into it. > mem=3D128 > eth0=3Dtuntap,"coLinux TAP" > root=3D/dev/cobd2 root=3D/dev/hdc > > Now, for some reason (perhaps because the initrd is the one off of the > install CD) the root filesystem /dev/cobd2 is not loaded. When I try to > install with the 'harddrive' option, I cannot mount any of the cobd > devices. I try loading file system modules, but I get this error (e.g.): > > fat: disagrees about version of symbol struct_module > > I gather this is because initrd is SuSE10 and the kernel is colinux. How > can I 'fake out' the installer to get some of the cobd devices > mounted? I'm so close I can taste it!!! These should exist for it and all most typical filesystems are already built into the coLinux kernel, if not you'll need to modify the initrd to include the coLinux modules that you need. HTH, -- George |
From: Fred C. I. <fr...@gi...> - 2006-02-20 17:32:10
|
Close! So close! Using the hda, hdb, etc. designations allowed the cdrom iso and other filesystems to be mounted. However, when I select the 'Harddrive' source selection and specify the source drive 'hda' and the source directory '/' it just bounces back to the source seletion screen and does not begin the installation. Am I missing something? Has anyone installed SuSE10 using the harddrive source option? I just don't know if the installation program should be going to a new screen or I'm missing an option from the menu list? Also, does anyone have any ideas on how to specify the cdrom drive to the installer program (which always says 'CDROM not found'). I can mount the CDROM as a drive, but not as the default cdrom device. Fred |
From: George P B. <geo...@gm...> - 2006-02-22 18:58:29
|
coLinux block devices, even when doing an alias such as hda1 do not handled partitions... This trips up about every installer I know of... Most installers allow you top bypass in some whay the partition step... I'd guess from what you wrote that SuSE 10 is trying to partition the cobd device and failing. George On 2/20/06, Fred Calef III <fr...@gi...> wrote: > > Close! So close! > > Using the hda, hdb, etc. designations allowed the cdrom iso and other > filesystems to be mounted. However, when I select the 'Harddrive' source > selection and specify the source drive 'hda' and the source directory > '/' it just bounces back to the source seletion screen and does not > begin the installation. Am I missing something? Has anyone installed > SuSE10 using the harddrive source option? I just don't know if the > installation program should be going to a new screen or I'm missing an > option from the menu list? > > Also, does anyone have any ideas on how to specify the cdrom drive to > the installer program (which always says 'CDROM not found'). I can mount > the CDROM as a drive, but not as the default cdrom device. > > Fred > > > -- George |
From: danny s. <ori...@gm...> - 2006-02-23 21:32:17
|
Suse 10 has a custom partitioning option. You go custom, and then custom again (instead of selecting the hard drive), and you can fully customise the setup. You could then tell it what to mount, and not to partition or format it. I have done a Suse 10 install recently on a virgin machine - and I do remember this aprt of the setup as I wanted to reorder the setup (too small a swap partition in my opinion). Danny On 22/02/06, George P Boutwell <geo...@gm...> wrote: > coLinux block devices, even when doing an alias such as hda1 do not > handled partitions... This trips up about every installer I know > of... Most installers allow you top bypass in some whay the partition > step... I'd guess from what you wrote that SuSE 10 is trying to > partition the cobd device and failing. > > George > > On 2/20/06, Fred Calef III <fr...@gi...> wrote: > > > > Close! So close! > > > > Using the hda, hdb, etc. designations allowed the cdrom iso and other > > filesystems to be mounted. However, when I select the 'Harddrive' sourc= e > > selection and specify the source drive 'hda' and the source directory > > '/' it just bounces back to the source seletion screen and does not > > begin the installation. Am I missing something? Has anyone installed > > SuSE10 using the harddrive source option? I just don't know if the > > installation program should be going to a new screen or I'm missing an > > option from the menu list? > > > > Also, does anyone have any ideas on how to specify the cdrom drive to > > the installer program (which always says 'CDROM not found'). I can moun= t > > the CDROM as a drive, but not as the default cdrom device. > > > > Fred > > > > > > > > > -- > George -- Danny Staple MBCS OrionRobots http://orionrobots.co.uk (Full contact details available through website) |