Menu
▾
▴
colinux-devel — Cooperative Linux development mailing list
You can subscribe to this list here.
| 2004 |
Jan
(64) |
Feb
(530) |
Mar
(266) |
Apr
(580) |
May
(360) |
Jun
(161) |
Jul
(185) |
Aug
(164) |
Sep
(123) |
Oct
(160) |
Nov
(59) |
Dec
(84) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(156) |
Feb
(95) |
Mar
(124) |
Apr
(81) |
May
(79) |
Jun
(179) |
Jul
(35) |
Aug
(64) |
Sep
(56) |
Oct
(57) |
Nov
(18) |
Dec
(41) |
| 2006 |
Jan
(65) |
Feb
(37) |
Mar
(59) |
Apr
(73) |
May
(65) |
Jun
(27) |
Jul
(54) |
Aug
(76) |
Sep
(103) |
Oct
(23) |
Nov
(45) |
Dec
(29) |
| 2007 |
Jan
(41) |
Feb
(47) |
Mar
(61) |
Apr
(24) |
May
(14) |
Jun
(6) |
Jul
(23) |
Aug
(30) |
Sep
(16) |
Oct
(9) |
Nov
(53) |
Dec
(36) |
| 2008 |
Jan
(19) |
Feb
(49) |
Mar
(74) |
Apr
(21) |
May
(24) |
Jun
(5) |
Jul
(9) |
Aug
(53) |
Sep
(26) |
Oct
(23) |
Nov
(32) |
Dec
(19) |
| 2009 |
Jan
(47) |
Feb
(49) |
Mar
(39) |
Apr
(61) |
May
(28) |
Jun
(19) |
Jul
(12) |
Aug
(10) |
Sep
(31) |
Oct
(16) |
Nov
(60) |
Dec
(26) |
| 2010 |
Jan
(17) |
Feb
(9) |
Mar
(32) |
Apr
(11) |
May
(24) |
Jun
(33) |
Jul
(5) |
Aug
(2) |
Sep
(7) |
Oct
(8) |
Nov
(17) |
Dec
(7) |
| 2011 |
Jan
(12) |
Feb
(16) |
Mar
(2) |
Apr
(12) |
May
(5) |
Jun
(10) |
Jul
(3) |
Aug
(3) |
Sep
(2) |
Oct
(1) |
Nov
(17) |
Dec
(1) |
| 2012 |
Jan
(9) |
Feb
(9) |
Mar
(8) |
Apr
(4) |
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(8) |
Sep
(11) |
Oct
(1) |
Nov
(2) |
Dec
(2) |
| 2013 |
Jan
|
Feb
(7) |
Mar
(4) |
Apr
(10) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(3) |
| 2016 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Gregor M. <mi...@ra...> - 2004-02-28 16:54:58
|
>>But the command $ mkswap /dev/cobd1 >>fails. > > Need to know what it says when it fails. $ mkswap /dev/cobd1 mkswap: error: swap needs to be at least 40 KB Usage: mkswap [-c] and so on. >>"swap-space signature": I think this is why mkswap is not working. Does >>anyone has the same problem? > > > That's what you get when you try to swapon something that hasn't > been mkswap'd. It would be expected if you had a swap entry in > your fstab but had not yet mkswap'd the device in question. ok. That's the case. -- | Gregor Mitsch |_ _ _| (0 62 52) 91 04 77 | | www.gmdsoft.de/mitsch | | mobil: 0175 8963520 | |
|
From: Sean B. <sea...@so...> - 2004-02-28 16:48:24
|
On Saturday 28 February 2004 16:13, Dan Aloni wrote: > On Sat, Feb 28, 2004 at 12:30:22PM +0000, Sean Brook wrote: > > On Saturday 28 February 2004 12:11, Dan Aloni wrote: > > > On Sat, Feb 28, 2004 at 12:36:40AM +0000, Sean Brook wrote: > > > > Using coLinux 0.5.24 binary I am getting sporadic seg faults with > > > > the Gentoo image from colinux@sourceforge. This especially happens > > > > during an emerge in the package extraction (tar etc) and the > > > > configure and make stages. > > > > > > > > I have created my own Gentoo build and get the same problem. > > > > Compiling my own coLinux kernel is also giving the same problem with > > > > both images. > > > > > > On what kind of processor you tried to run it? > > > > It is an Athlon 1.4GHz > > Does these segfaults occur with the Debian image from sf? I personally have had no problems at all with the Debian image. Rock solid. |
|
From: Sean B. <sea...@so...> - 2004-02-28 16:35:11
|
On Saturday 28 February 2004 14:57, Leo Amendola wrote: > I have the same problem. It seems like it happens > when there is a large file to untar. I have a 2.4Ghz > Intel Processor with Gentoo in a 5GB image file. Its good to know I am not alone. Also good to know that you are using an Intel processor as opposed to me using an Athlon. My system was borking when merging tcp-wrappers (which is not big at all). A couple of questions if I may: Is this your own image or the one from sourceforge? What are your CFLAGS set to in /etc/make.conf? (I have a hunch that the tar seg faults maybe due to me having -pipe in my CFLAGS). Cheers. > > --- Sean Brook <sea...@so...> wrote: > > On Saturday 28 February 2004 12:11, Dan Aloni wrote: > > > On Sat, Feb 28, 2004 at 12:36:40AM +0000, Sean > > > > Brook wrote: > > > > Using coLinux 0.5.24 binary I am getting > > > > sporadic seg faults with the > > > > > > Gentoo image from colinux@sourceforge. This > > > > especially happens during an > > > > > > emerge in the package extraction (tar etc) and > > > > the configure and make > > > > > > stages. > > > > > > > > I have created my own Gentoo build and get the > > > > same problem. Compiling my > > > > > > own coLinux kernel is also giving the same > > > > problem with both images. > > > > > On what kind of processor you tried to run it? > > > > It is an Athlon 1.4GHz > > > > # cat /proc/cpuinfo > > > > processor : 0 > > vendor_id : AuthenticAMD > > cpu family : 6 > > model : 4 > > model name : AMD Athlon(tm) Processor > > stepping : 4 > > cpu MHz : 1399.803 > > cache size : 256 KB > > fdiv_bug : no > > hlt_bug : no > > f00f_bug : no > > coma_bug : no > > fpu : yes > > fpu_exception : yes > > cpuid level : 1 > > wp : yes > > flags : fpu vme de pse tsc msr pae mce cx8 > > apic sep mtrr pge mca > > cmov pat pse36 mmx fxsr syscall mmxext 3dnowext > > 3dnow > > bogomips : 2791.83 > > ------------------------------------------------------- > > > 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 |
|
From: peter g. <plu...@p1...> - 2004-02-28 16:27:29
|
i'm still getting clock freezes with 0.5.4 and it usually takes a reboot of the host to clear them plugwash --- 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 |
|
From: Sean B. <sea...@so...> - 2004-02-28 16:08:50
|
I have had mixed results with mkswap in coLinux, as you are experiencing. Have not tried 0.5.4 with mkswap though. I have attached a ready made 128mb swap image to this mail to get you up and running. Hope it helps. On Saturday 28 February 2004 15:39, Gregor Mitsch wrote: > > This is colinx-daemon.exe's output during booting: > > > > [...] > > Freeing unused kernel memory: IMPLEMENTATION MISSING > > daemon: module connected: conet0 > > co_message_switch: setting callback rule for 8 > > Unable to find swap-space signature > > Unable to find swap-space signature > > daemon: module connected: console > > co_message_switch: setting callback rule for 6 > > conet0: initialized > > I forgot to mention the following boot output > > [...] > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > loop: loaded (max 8 devices) > cobd0 size: 1048576 kb > cobd1 size: 128000 kb > cobd: loaded (max 8 devices) > [...] > > which indicates that the xml file settings should be ok. > > Gregor > > > ------------------------------------------------------- > 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 |
|
From: Matt B. <ma...@zi...> - 2004-02-28 16:00:15
|
On Sat, Feb 28, 2004 at 04:10:41PM +0100, Gregor Mitsch wrote: > But the command $ mkswap /dev/cobd1 > fails. Need to know what it says when it fails. > "swap-space signature": I think this is why mkswap is not working. Does= =20 > anyone has the same problem? That's what you get when you try to swapon something that hasn't been mkswap'd. It would be expected if you had a swap entry in your fstab but had not yet mkswap'd the device in question. --=20 Matt Behrens <ma...@zi...> <http://www.zigg.com/> Life's too short to recompile what you don't hack. <http://www.debian.org/> |
|
From: Gregor M. <mi...@ra...> - 2004-02-28 15:50:55
|
> This is colinx-daemon.exe's output during booting: > > [...] > Freeing unused kernel memory: IMPLEMENTATION MISSING > daemon: module connected: conet0 > co_message_switch: setting callback rule for 8 > Unable to find swap-space signature > Unable to find swap-space signature > daemon: module connected: console > co_message_switch: setting callback rule for 6 > conet0: initialized I forgot to mention the following boot output [...] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) cobd0 size: 1048576 kb cobd1 size: 128000 kb cobd: loaded (max 8 devices) [...] which indicates that the xml file settings should be ok. Gregor |
|
From: Gregor M. <mi...@ra...> - 2004-02-28 15:21:50
|
Hi, I've created a swap-file as said in the wiki. I modified /etc/fstab But the command $ mkswap /dev/cobd1 fails. This is colinx-daemon.exe's output during booting: [...] Freeing unused kernel memory: IMPLEMENTATION MISSING daemon: module connected: conet0 co_message_switch: setting callback rule for 8 Unable to find swap-space signature Unable to find swap-space signature daemon: module connected: console co_message_switch: setting callback rule for 6 conet0: initialized "swap-space signature": I think this is why mkswap is not working. Does anyone has the same problem? I'm using the latest version of coLinux. Regards, Gregor |
|
From: Sean B. <sea...@so...> - 2004-02-28 12:41:35
|
On Saturday 28 February 2004 12:11, Dan Aloni wrote: > On Sat, Feb 28, 2004 at 12:36:40AM +0000, Sean Brook wrote: > > Using coLinux 0.5.24 binary I am getting sporadic seg faults with the > > Gentoo image from colinux@sourceforge. This especially happens during an > > emerge in the package extraction (tar etc) and the configure and make > > stages. > > > > I have created my own Gentoo build and get the same problem. Compiling my > > own coLinux kernel is also giving the same problem with both images. > > On what kind of processor you tried to run it? It is an Athlon 1.4GHz # cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 4 model name : AMD Athlon(tm) Processor stepping : 4 cpu MHz : 1399.803 cache size : 256 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow bogomips : 2791.83 |
|
From: Dan A. <da...@co...> - 2004-02-28 12:22:13
|
On Sat, Feb 28, 2004 at 12:36:40AM +0000, Sean Brook wrote: > Using coLinux 0.5.24 binary I am getting sporadic seg faults with the Gentoo > image from colinux@sourceforge. This especially happens during an emerge in > the package extraction (tar etc) and the configure and make stages. > > I have created my own Gentoo build and get the same problem. Compiling my own > coLinux kernel is also giving the same problem with both images. On what kind of processor you tried to run it? -- Dan Aloni da...@co... |
|
From: Sean B. <sea...@so...> - 2004-02-28 00:47:29
|
Using coLinux 0.5.24 binary I am getting sporadic seg faults with the Gentoo image from colinux@sourceforge. This especially happens during an emerge in the package extraction (tar etc) and the configure and make stages. I have created my own Gentoo build and get the same problem. Compiling my own coLinux kernel is also giving the same problem with both images. Is anyone else using this image or their own Gentoo image having similar results? |
|
From: Dan A. <da...@gm...> - 2004-02-27 18:23:40
|
URL: http://www.colinux.org/snapshots/ Notes: * These are unformal releases. * They are manually created whenever I see fit. * Can be removed or updated without notice. * The frequency will be higher than formal releases. * On most cases I will not announce about them at all. -- Dan Aloni da...@gm... |
|
From: Dmitriy K. <dm...@ka...> - 2004-02-27 15:40:22
|
Welcome,all
DII> - Virtual Mouse driver
DII> easy. but it should be "seamless" like when you
DII> installed VMware tools to VMware.
- Virtual Serial driver(for external modems, some mices)
--
With regards,
Dmitriy mailto:dm...@ka...
|
|
From: <ch...@to...> - 2004-02-27 15:38:31
|
I forgot to mention that using the setup I am doing relies on the grub based bootloader working on your system for dualboot mode. The nfts driver for grub has problems with some systems but works fine for most. >> get topologilinux from topologilinux.com > > I'll take a look at it, but the purpose of this exercise was to see if I > can > install a distribution from scratch :-) Well if it is an exercise by all means plug ahead. I didn't know it was an exercise just thought you wanted a slackware install that you could add any packages you want. The advantages to topologilinux is that there is no linux system needed. The files are automaticly installed on a loopback but there is still alot of hand work to do. But hopefully the work that I am doing may result in topologilinux being totally coLinux ready in future versions. chris |
|
From: Marko B. <mar...@al...> - 2004-02-27 15:18:12
|
ch...@to... wrote: >>I was trying to install the latest Slackware distribution (9.1) following >>Nir's instructions, but I ran into problems... Here's what I did, step by >>step >>(bear with me, I'm not an expert, and haven't installed a slackware since >>the >>middle of 90's :-) >> > > get topologilinux from topologilinux.com I'll take a look at it, but the purpose of this exercise was to see if I can install a distribution from scratch :-) -- 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. |
|
From: <ch...@to...> - 2004-02-27 14:43:57
|
> I was trying to install the latest Slackware distribution (9.1) following > Nir's instructions, but I ran into problems... Here's what I did, step by > step > (bear with me, I'm not an expert, and haven't installed a slackware since > the > middle of 90's :-) > get topologilinux from topologilinux.com It is most of slackware designed install to a loopback files system. After installing you can make the resulting base.img useable under colinux just by doing all the mknod /dev/cobd? b 117 ? 's and changing fstab to point to . I will be posting a HowTo that provides both coLinux and dual-boot capability redirecting the devices and changing networking as needed to the wiki sometime next week. So you could get it and play around with it a while first. here is the config file I am using so far for using the img under colinux <?xml version="1.0" encoding="UTF-8"?> <colinux> <block_device index="0" path="\DosDevices\c:\tlinux4\base.img" enabled="true"> </block_device> <block_device index="1" path="\DosDevices\c:\coLinux\swap.img" enabled="true"> </block_device> <bootparams>root=cobd0 ro</bootparams> <image path="vmlinux"></image> <memory size="64"></memory> <network index="0" type="tap" name="TAP"></network> </colinux> the coresponding fstab changes would be to change /dev/loop7 to /dev/cobd0 and /dev/loop6 to /dev/cobd1 my HowTo will start from a stock setup that has not been modified at all for colinux. chris |
|
From: Marko B. <mar...@al...> - 2004-02-27 13:52:39
|
I was trying to install the latest Slackware distribution (9.1) following
Nir's instructions, but I ran into problems... Here's what I did, step by step
(bear with me, I'm not an expert, and haven't installed a slackware since the
middle of 90's :-)
[these steps are done on a native linux box]
1. downloaded slackware CD1 ISO image, loop-mounted it to /mnt/slack
2. run 'gzip -cd /mnt/slack/rootdisks/install.1 > rootdisk.image' in the tmp dir
3. loop-mounted rootdisk.image to /mnt/root, cd there, run 'tar zxvf
/mnt/slack/rootdisks/install.2'
4. run from /mnt/root (mounted root image):
mknod dev/cobd0 b 117 0
mknod dev/cobd1 b 117 1
mknod dev/cobd2 b 117 2
- in Nir's HOWTO it's 'mknod /dev/cobd0 b 117 0'; I guess '/dev/cobd0' is a
typo
5. edit usr/lib/setup/setup script, commented out 'if probe' lines (47-56),
added 'echo "/dev/cobd0" > $TMP/SeTplist' line
6. created a blank, 1GB ext2 image, mounted it to /mnt/install, and copied
everything from /mnt/slack (mounted ISO image):
dd if=/dev/zero of=slackware.install.image bs=1024 count=1M
mkfs.ext2 slackware.install.image
mount, copy
7. unmount /mnt/root, /mnt/install, scp slackware.install.image and
rootdisk.image to my windows box (X:\coLinux\)
[these steps are done on the windows box]
8. setup the coLinux XML file; relevant lines:
<block_device index="0" path="\DosDevices\X:\coLinux\slackware9.1.image"
enabled="true"></block_device>
<block_device index="1" path="\DosDevices\X:\coLinux\slackware.install.image"
enabled="true"></block_device>
<block_device index="2" path="\DosDevices\X:\coLinux\rootdisk.image"
enabled="true"></block_device>
<bootparams>root=/dev/cobd2</bootparams>
- slackware9.1.image is an empty, 1GB ext2 image
9. boot coLinux
[these steps are done on coLinux, Slackware image booted]
10. first steps: hit <ENTER> on keyboard map question, logged in as root, run
setup
11. choose target partition from the menu: /dev/cobd0, formatted it again to
ext2 (just in case), 1 inode per 4096 bytes
12. select source from a partition (2): /dev/cobd1, set '/' as the
installation path, got package series selection. Unselected everything except
'A' and 'AP' series
13. selected newbie prompting mode, works for a moment, got messages from the
prompt: '/usr/lib/setup/setup: cannot create /mnt/etc/fstab: No such file or
directory', and got a 'SETUP COMPLETE' dialog
14. created etc dir in /mnt, restarted setup, again waited a bit, got some
errors, got a query for root password (skipped it), and got the 'SETUP
COMPLETE' dialog again; mounted /dev/cobd0 to check it out, there are only
etc, lost+found, proc and var directories
15. mounted /dev/cobd1 into a directory and selected it as a source for setup,
same thing
What am I doing wrong?
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.
|
|
From: <ch...@to...> - 2004-02-27 13:48:40
|
I was wondering can this change fstab? I am assuming that fstab needs to point / to the right device before remounting rw even before fsck. I read the docs on hprofile. I'll take a look at the examples today. chris >> If you want a nice solution to switching files around dependent on your >> environment check out http://hprofile.sourceforge.net >> Essentially what it allows for is determining a profile to be used >> through >> kernel parameters or checking for devices that would exist in one >> environment, but not another etc (you need to customise that through >> scripts). It switches to a runlevel accordingly and takes care of all of >> the >> symlinks for you. Works fantastic. > > Looks interesting. do the kernel parameters pass through coLinux daemon > fine? I saw something a while back that someone couldn't get ro to pass. > right now I am using the fact that topologilinux uses an initrd to boot so > I have links to the real devices on the initrd and the coLinux devices in > the directory that is the mountpoint for the initrd. That seems to work > good for switching / and swap between /dev/cobd? and /dev/loop? I'll > definatly look into hprofile further. > > chris > >> >>> >>> I am taking notes as I do this and should have a good HowTo to post on >>> the >>> wiki (which is looking very nice, very quickly) >>> >>> I am using Topologilinux which runs off of loopback files on the >>> windows >>> partition. Booting both ways so far but I want to get networking and >>> maby >>> floppy and cdrom access (I set them up in the rootfs but need to figure >>> out the colinux.xml setup for them. >>> >>> chris >>> >>> >>> ------------------------------------------------------- >>> 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 >> > > |
|
From: <ch...@to...> - 2004-02-27 13:41:53
|
> >> >>> - Virtual Printer driver >>> print documents from coLinux through Windows. >>> this is easy if you rasterize rightly. >>> so if you can print on linux logically, >>> ( solving font, cups/ghostscript settings...) >>> you can print on coLinux physically. >> >> this can be done already using samba, but a post script virtual printer >> on >> the windows side seems the easiest. perhaps have a virtual printer >> device >> that says it's PS compatible and have it pass the PS file to ghost >> script >> in the host OS. >> > > I think adobe has a post script virtual printer. I think I saw this > mentioned in the cups documentation. I'll have to check on that It may > even be free. Sorry, I should have checked first that adobe driver is a postscript dirver for using cups or lpd as the print server and windows as the client. Setting up a samba printer is as easy as installing the printer directly to linux. > > > ------------------------------------------------------- > 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 > |
|
From: <ch...@to...> - 2004-02-27 13:23:48
|
> >> - Virtual Printer driver >> print documents from coLinux through Windows. >> this is easy if you rasterize rightly. >> so if you can print on linux logically, >> ( solving font, cups/ghostscript settings...) >> you can print on coLinux physically. > > this can be done already using samba, but a post script virtual printer on > the windows side seems the easiest. perhaps have a virtual printer device > that says it's PS compatible and have it pass the PS file to ghost script > in the host OS. > I think adobe has a post script virtual printer. I think I saw this mentioned in the cups documentation. I'll have to check on that It may even be free. |
|
From: <ch...@to...> - 2004-02-27 13:14:44
|
use vnc it has a clipboard I am using the latest version of tight vnc and was able to copy from and rxvt window inside fluxbox to notepad you can also run xvnc from initrd and use xdm or gdm to log in. You can setup different resolutions on different ports. or you can just start the server from the console as a user. In this case it will preserve the session if you close the client then open it back up. I find that setting the server geometry to 1000 by 685 makes for a nice window. chris > Digital Infra, Inc. wrote: > > Copy and paste, drag and drop..... They are definitely necessary. > > So, how to implement it? One proposal is written below. > > > VMWare seems to be able to do it without any special software. Not sure > how though. > > Tony > > > > ------------------------------------------------------- > 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 > |
|
From: Tony H. <tm...@no...> - 2004-02-27 12:42:24
|
Digital Infra, Inc. wrote: > Copy and paste, drag and drop..... They are definitely necessary. > So, how to implement it? One proposal is written below. > VMWare seems to be able to do it without any special software. Not sure how though. Tony |
|
From: Digital I. Inc. <ok...@di...> - 2004-02-27 12:38:30
|
Interaction with Windows and coLinux
Copy and paste, drag and drop..... They are definitely necessary.
So, how to implement it? One proposal is written below.
--- Okajima.
-----
1. Creating /dev/Windows/DnD /dev/Windows/CopyBuffer ....
2. Making KDE/Gnome check it.
|
|
From: Marko B. <mar...@al...> - 2004-02-27 12:32:25
|
Ballard Jonathan wrote: > I put the patch on Sourceforge.net that implements the NT/Linux console. > > Here is a beta release that works with 0.5.4: > > ftp://ftp.drunkencodepoets.com:821/colinux-console.0.5.4.bjh.1.beta.exe.bz2 Hm... How do I use it? I tried replacing the original colinux-console.exe with yours, but when I start the daemon, it behaves strangly (just a small empty console window is shown) I've even tried runninf coLinux with the original console, detaching it when it boots, and running your console, but it disappears immediately. The daemon window shows this message: daemon: module connected: console co_message_switch: setting callback rule for 6 co_message_switch: freeing rule for 6 daemon: module disconnected: console 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. |
|
From: Pat E. <pat...@ma...> - 2004-02-27 11:30:05
|
> - Virtual Sound driver > very easy. agreed > - Virtual Mouse driver > easy. but it should be "seamless" like when you > installed VMware tools to VMware. if we don't implement a frame buffer or a virtual display device, I see no reason for a mouse to be needed. If you mean for copy/paste, I reccomend a proper text console and let the host OS handle copy/paste(much like bjh's console) > - Virtual Printer driver > print documents from coLinux through Windows. > this is easy if you rasterize rightly. > so if you can print on linux logically, > ( solving font, cups/ghostscript settings...) > you can print on coLinux physically. this can be done already using samba, but a post script virtual printer on the windows side seems the easiest. perhaps have a virtual printer device that says it's PS compatible and have it pass the PS file to ghost script in the host OS. > - Virtual Frame buffer > Performance is the key. BitBlt all frame is easy, but slow. > It must bitblt only a region which is updated. How? > And second point is, is this really necessary? > If you use only X, cygwin/X is enough. this could get pretty difficult, having to pass messages back and forth between the host os and the guest os to handle events, clicks etc. I believe our current framework, or a special version of vnc would be better. Perhaps modify vnc to take out the net layer dependance and provide it a mmaped io or a different pipe. but, as always,those are just my opinions. Pat |
81 messages has been excluded from this view by a project administrator.
