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: peter g. <plu...@p1...> - 2004-04-09 23:53:15
|
find the most recent cygwin1.dll on your system
copy it to windows\system32
and delete all other copies
-----Original Message-----
From: col...@li...
[mailto:col...@li...]On Behalf Of tei
Sent: 09 April 2004 10:40
To: col...@li...
Subject: [coLinux-devel] bad side effect
I can't start a cygwin bash window with coLinux up, or *any* cygwin dll
based app.
Generate this type of error messages:
c:\bin>man ls
147 [unknown (0x550)] ? 744 shared_info::initialize: size of shared
memory region chan
ged from 47112 to 21008
218197 [main] man 744 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
218851 [main] man 744 open_stackdumpfile: Dumping stack trace to
MAN.EXE.stackdump
some commands break into stackdumps, others warn and run...
Not a problem, IMO, but something that will need to fix for a ulterior
version some day.
This where my ms-dos enviroments vars:
ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINNT
APPDATA=C:\Documents and Settings\t.FIEND\Datos de programa
CommonProgramFiles=C:\Archivos de programa\Archivos comunes
COMPUTERNAME=FIEND
ComSpec=C:\bin\4dos\4NT.EXE
CYGWIN_ROOT=E:\root
HOME=\home\tei
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\t.FIEND
INCLUDE=C:\ARCHIV~1\MICROS~1.NET\VC7\INCLUDE\;%INCLUDE%
KDEDIR=E:\root\opt\kde3
KDEHOME="C:\Documents and Settings\t.FIEND\Datos de programa"
LIB=C:\ARCHIV~1\MICROS~1.NET\VC7\LIB\;%LIB%
LOGONSERVER=\\FIEND
LTDL_LIBRARY_PATH=E:\root\opt\kde3\lib;E:\root\opt\kde3\lib\kde3
MAILENABLE_PATH=C:\bin\MAILEN~1
MSDEV="C:\Archivos de programa\Microsoft Visual Studio
.NET\Common7\IDE\devenv.exe"
NUMBER_OF_PROCESSORS=1
OCAMLLIB=C:\bin\ocalm\lib
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\bin\Mail
Enable\BIN;C:\bin\texmf\miktex\bin;D:\Perl\bin\;C:\WINNT\system32;C:\WINNT;C
:\WINNT\System32\Wbem;"C:\Archivos
de programa\erl5.1\bin";d:\perl\bin;C:\Archivos de programa\Support
Tools\;/e/root/bin;e:/root/bin;C:\Archivos de programa\Archivos
comunes\GTK\2.0\bin;C:\Archivos de
programa\VDMSound\;C:\bin\ocalm\bin;C:\Archivos de programa\ATI
Technologies\ATI Control
Panel;;C:\bin\ocalm\bin;C:\ARCHIV~1\MICROS~1.NET\VC7\BIN\;C:\ARCHIV~1\MICROS
~1.NET\COMMON7\IDE\;"C:\WINNT;c:\bin\4dos\;d:\perl\bin"
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 4 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0402
ProgramFiles=C:\Archivos de programa
PROMPT=$p$g
PYTHONPATH=E:\python
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=c:\tmp
TMP=c:\tmp
USERDOMAIN=FIEND
USERNAME=t
USERPROFILE=C:\Documents and Settings\t.FIEND
VDMSPath=C:\Archivos de programa\VDMSound\
winbootdir=C:\WINNT
windir=C:\WINNT
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
coLinux-devel mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-devel
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
|
|
From: Steven E. <ste...@ya...> - 2004-04-09 23:15:48
|
Hi, --- Regis NEBOR <re...@ho...> wrote: > To apply on top of the 04/09/04 release's colinux.nsi : > config_backup then auto_cygwin_detect If we can dump cygwin in favor of msvcrt then this wont be a issue. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Steven E. <ste...@ya...> - 2004-04-09 21:46:21
|
Hello All, Well here it is in all of its glory. All 5 lines of it. It works but we (ReactOS team) have not tested it beyond booting the kernel. There are a few changes that will need to be made before this can be merged in and we can drop Cygwin I guess. But I beg and plead that we do this so we can drop Cygwin totaly if we are not going to need it for the Xserver. 1. The FLTK console wont build on the Mingw cross-compiler as we lack support for it. I guess we could ship our own copy. 2. The user has to go download/install the mxml sources for the mingw-crosscompiler. Once again its small we could ship this with the coLinux sources. 3. You need to change i*86-cygwin-blah to -*86-mingw32-blah for all of the commands in your makefile to support a mingw cross 4. We need to add some configure like checking for these headers I have added the ifdefs for in this patch. 5. It links to ws2_32 but I have not tested the networking stuff so we will have to adapt the rest to use use Winsock but it will still be faster than using Cygwin->Winsock. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Dan A. <da...@co...> - 2004-04-09 19:24:53
|
On Fri, Apr 09, 2004 at 12:17:37PM -0700, Steven Edwards wrote: > > --- Dan Aloni <da...@co...> wrote: > > Sounds like memory corruption to me. Do you have debug facilities in > > ReactOS > > that allow you to track down stuff like this? > > > > You did implement some sort of BSOD, right? > > Yes but this problem is on Native Windows 2000 not ReactOS. I only had > it installed on this system in this configuration for use in ReactOS. Oh, missed the last line. Machine specs, plus DebugView output of the run would be helpful. -- Dan Aloni da...@co... |
|
From: Dan A. <da...@co...> - 2004-04-09 19:20:46
|
On Fri, Apr 09, 2004 at 08:32:25PM +0200, Jaroslaw Kowalski wrote: > > Hi Dan! > > That's exactly what I was going to release 15 minutes ago ;-))))))))))) > ctrl_alt_del is included. You know what they say, "Great minds think alike" :) > Patch is attached. Can you please review it (I probably have done everything > wrong) and add it to coLinux ? It looks good, I'll add this to the next snapshot. -- Dan Aloni da...@co... |
|
From: Steven E. <ste...@ya...> - 2004-04-09 19:17:38
|
--- Dan Aloni <da...@co...> wrote: > Sounds like memory corruption to me. Do you have debug facilities in > ReactOS > that allow you to track down stuff like this? > > You did implement some sort of BSOD, right? Yes but this problem is on Native Windows 2000 not ReactOS. I only had it installed on this system in this configuration for use in ReactOS. Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Small Business $15K Web Design Giveaway http://promotions.yahoo.com/design_giveaway/ |
|
From: Dan A. <da...@co...> - 2004-04-09 19:13:03
|
On Fri, Apr 09, 2004 at 09:01:42PM +0200, Jaroslaw Kowalski wrote: > In theory - yes. You can create as many services as you like. In practice - > the services get created but I haven't checked if they can work in parallel. Currently coLinux doesn't allow more than one instance of itself, but it was written along with a design that will make this possible with only a few easy modifications to the daemon and the driver. -- Dan Aloni da...@co... |
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-09 19:01:19
|
In theory - yes. You can create as many services as you like. In practice - the services get created but I haven't checked if they can work in parallel. Jarek ----- Original Message ----- From: <ch...@to...> To: "Jaroslaw Kowalski" <ja...@zd...> Cc: "Dan Aloni" <da...@co...>; <col...@li...> Sent: Friday, April 09, 2004 9:00 PM Subject: Re: [coLinux-devel] ANN: CoLinuxService v0.1 released > so does this mean that you can > > colinux -c c:\path\to\config\deb.xml -i coDeb > colinux -c c:\path\to\config\gentoo.xml -i coGentoo > > net start coDeb > net stop coDeb > net start coGentoo > net stop coGentoo > > then someday we can > > net start coDeb > net start coGentoo > net stop coGentoo > net stop coDeb > > chris > > > > > Hi Dan! > > > > That's exactly what I was going to release 15 minutes ago ;-))))))))))) > > ctrl_alt_del is included. > > > > Patch is attached. Can you please review it (I probably have done > > everything > > wrong) and add it to coLinux ? > > > > I did it like that: > > > > INSTALL: > > colinux -c c:\path\to\config\file.xml -i ServiceName > > > > RUN: > > net start ServiceName > > net stop ServiceName > > > > REMOVE: > > colinux -r ServiceName > > > > If you don't provide ServiceName then "CoLinux" is used instead. > > > > Jarek > > > > ----- Original Message ----- > > From: "Dan Aloni" <da...@co...> > > To: "Jaroslaw Kowalski" <ja...@zd...> > > Cc: <col...@li...> > > Sent: Friday, April 09, 2004 8:28 PM > > Subject: Re: [coLinux-devel] ANN: CoLinuxService v0.1 released > > > > > >> On Fri, Apr 02, 2004 at 12:02:47AM +0200, Jaroslaw Kowalski wrote: > >> > I'm proud to announce that CoLinuxService v0.1 has been released. > >> > > >> > It allows you to run colinux as a Windows service and supports clean > >> > shutdown procedure with elementary authentication. > >> > > >> > Full source code & binary is ready for download at > >> > > >> > http://jaak.sav.net/colinux/CoLinuxService-0.1.zip > >> > > >> > The code is available under the BSD license. Note that it contains > > portions > >> > of Microsoft sample code by that comes with Visual C++ and I don't > >> think > >> > it's GPL-able. > >> > > >> > Installation instructions can be found inside the archive. > >> > > >> > Any feedback is welcome. Feel free to send patches and I'll include > >> them > > in > >> > future versions. > >> > >> This looks very nice, and I'd would really like to see this merged into > >> coLinux, but as command line options to the daemon (along with icons set > >> by the installer). > >> > >> Think about the potential: If colinux-daemon.exe is aware that it runs > >> as > > a > >> service, on ServiceStop() it can send an ctrl_alt_del() message to the > >> Linux VM and cause it to shutdown cleanly - this means no xinetd network > >> hacks. > >> > >> I'd like it to go like this: Whenever you install colinux-daemon as > > service > >> using a command line such as: > >> > >> colinux-dameon -s install -n coLinuxServiceName [more paramters] > >> > >> It would take the other parameters and use them on Start. Then, you > >> could > >> do something like: > >> > >> colinux-dameon -s start -n coLinuxServiceName > >> colinux-dameon -s stop -n coLinuxServiceName > >> > >> Instead of using service.cpp it would be better to code something > >> similar > >> only with the needed functionality. > >> > >> -- > >> Dan Aloni > >> da...@co... > >> > > > |
|
From: <ch...@to...> - 2004-04-09 19:00:17
|
so does this mean that you can colinux -c c:\path\to\config\deb.xml -i coDeb colinux -c c:\path\to\config\gentoo.xml -i coGentoo net start coDeb net stop coDeb net start coGentoo net stop coGentoo then someday we can net start coDeb net start coGentoo net stop coGentoo net stop coDeb chris > > Hi Dan! > > That's exactly what I was going to release 15 minutes ago ;-))))))))))) > ctrl_alt_del is included. > > Patch is attached. Can you please review it (I probably have done > everything > wrong) and add it to coLinux ? > > I did it like that: > > INSTALL: > colinux -c c:\path\to\config\file.xml -i ServiceName > > RUN: > net start ServiceName > net stop ServiceName > > REMOVE: > colinux -r ServiceName > > If you don't provide ServiceName then "CoLinux" is used instead. > > Jarek > > ----- Original Message ----- > From: "Dan Aloni" <da...@co...> > To: "Jaroslaw Kowalski" <ja...@zd...> > Cc: <col...@li...> > Sent: Friday, April 09, 2004 8:28 PM > Subject: Re: [coLinux-devel] ANN: CoLinuxService v0.1 released > > >> On Fri, Apr 02, 2004 at 12:02:47AM +0200, Jaroslaw Kowalski wrote: >> > I'm proud to announce that CoLinuxService v0.1 has been released. >> > >> > It allows you to run colinux as a Windows service and supports clean >> > shutdown procedure with elementary authentication. >> > >> > Full source code & binary is ready for download at >> > >> > http://jaak.sav.net/colinux/CoLinuxService-0.1.zip >> > >> > The code is available under the BSD license. Note that it contains > portions >> > of Microsoft sample code by that comes with Visual C++ and I don't >> think >> > it's GPL-able. >> > >> > Installation instructions can be found inside the archive. >> > >> > Any feedback is welcome. Feel free to send patches and I'll include >> them > in >> > future versions. >> >> This looks very nice, and I'd would really like to see this merged into >> coLinux, but as command line options to the daemon (along with icons set >> by the installer). >> >> Think about the potential: If colinux-daemon.exe is aware that it runs >> as > a >> service, on ServiceStop() it can send an ctrl_alt_del() message to the >> Linux VM and cause it to shutdown cleanly - this means no xinetd network >> hacks. >> >> I'd like it to go like this: Whenever you install colinux-daemon as > service >> using a command line such as: >> >> colinux-dameon -s install -n coLinuxServiceName [more paramters] >> >> It would take the other parameters and use them on Start. Then, you >> could >> do something like: >> >> colinux-dameon -s start -n coLinuxServiceName >> colinux-dameon -s stop -n coLinuxServiceName >> >> Instead of using service.cpp it would be better to code something >> similar >> only with the needed functionality. >> >> -- >> Dan Aloni >> da...@co... >> > |
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-09 18:32:12
|
Hi Dan! That's exactly what I was going to release 15 minutes ago ;-))))))))))) ctrl_alt_del is included. Patch is attached. Can you please review it (I probably have done everything wrong) and add it to coLinux ? I did it like that: INSTALL: colinux -c c:\path\to\config\file.xml -i ServiceName RUN: net start ServiceName net stop ServiceName REMOVE: colinux -r ServiceName If you don't provide ServiceName then "CoLinux" is used instead. Jarek ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Jaroslaw Kowalski" <ja...@zd...> Cc: <col...@li...> Sent: Friday, April 09, 2004 8:28 PM Subject: Re: [coLinux-devel] ANN: CoLinuxService v0.1 released > On Fri, Apr 02, 2004 at 12:02:47AM +0200, Jaroslaw Kowalski wrote: > > I'm proud to announce that CoLinuxService v0.1 has been released. > > > > It allows you to run colinux as a Windows service and supports clean > > shutdown procedure with elementary authentication. > > > > Full source code & binary is ready for download at > > > > http://jaak.sav.net/colinux/CoLinuxService-0.1.zip > > > > The code is available under the BSD license. Note that it contains portions > > of Microsoft sample code by that comes with Visual C++ and I don't think > > it's GPL-able. > > > > Installation instructions can be found inside the archive. > > > > Any feedback is welcome. Feel free to send patches and I'll include them in > > future versions. > > This looks very nice, and I'd would really like to see this merged into > coLinux, but as command line options to the daemon (along with icons set > by the installer). > > Think about the potential: If colinux-daemon.exe is aware that it runs as a > service, on ServiceStop() it can send an ctrl_alt_del() message to the > Linux VM and cause it to shutdown cleanly - this means no xinetd network > hacks. > > I'd like it to go like this: Whenever you install colinux-daemon as service > using a command line such as: > > colinux-dameon -s install -n coLinuxServiceName [more paramters] > > It would take the other parameters and use them on Start. Then, you could > do something like: > > colinux-dameon -s start -n coLinuxServiceName > colinux-dameon -s stop -n coLinuxServiceName > > Instead of using service.cpp it would be better to code something similar > only with the needed functionality. > > -- > Dan Aloni > da...@co... > |
|
From: Dan A. <da...@co...> - 2004-04-09 18:28:50
|
On Fri, Apr 02, 2004 at 12:02:47AM +0200, Jaroslaw Kowalski wrote: > I'm proud to announce that CoLinuxService v0.1 has been released. > > It allows you to run colinux as a Windows service and supports clean > shutdown procedure with elementary authentication. > > Full source code & binary is ready for download at > > http://jaak.sav.net/colinux/CoLinuxService-0.1.zip > > The code is available under the BSD license. Note that it contains portions > of Microsoft sample code by that comes with Visual C++ and I don't think > it's GPL-able. > > Installation instructions can be found inside the archive. > > Any feedback is welcome. Feel free to send patches and I'll include them in > future versions. This looks very nice, and I'd would really like to see this merged into coLinux, but as command line options to the daemon (along with icons set by the installer). Think about the potential: If colinux-daemon.exe is aware that it runs as a service, on ServiceStop() it can send an ctrl_alt_del() message to the Linux VM and cause it to shutdown cleanly - this means no xinetd network hacks. I'd like it to go like this: Whenever you install colinux-daemon as service using a command line such as: colinux-dameon -s install -n coLinuxServiceName [more paramters] It would take the other parameters and use them on Start. Then, you could do something like: colinux-dameon -s start -n coLinuxServiceName colinux-dameon -s stop -n coLinuxServiceName Instead of using service.cpp it would be better to code something similar only with the needed functionality. -- Dan Aloni da...@co... |
|
From: Daniel S. <dan...@au...> - 2004-04-09 16:54:27
|
For those of you who are trying to get DHCP working for FC1, here is my kernel image and modules. http://www.geocities.com/dan_slater/colinux/fedora.tar.gz This kernel has socket filtering turned on for DHCP. It also has most of the network file systems ( including smbfs ) enabled as modules. I have been using this kernel to run my dual-boot FC1 installation under colinux. Hope you find it useful. =20 Dan =20 |
|
From: Regis N. <re...@ho...> - 2004-04-09 16:29:57
|
To apply on top of the 04/09/04 release's colinux.nsi : config_backup then auto_cygwin_detect Regis NEBOR |
|
From: <ch...@to...> - 2004-04-09 12:08:31
|
> > Hello Chris, > > I have no reason to stick to Cygwin/X. > So I also consider possiblity of VNC too. > and I will write coLinux frame buffer with DirectX accelarated, > I totally have no reason to stick to Cygwin/X. > > I just want to investigate every possibility > before I do something actually. > I believe that slow start with a right plan reachs the goal faster. I agree 100% Take as many Ideas as possible and pick the best ones investigate everything. That is why my contributions to the X part of the wiki are so different. My opinion so far is that vnc would be better and easier for presenting a linux desktop as a whole in a window. But X has some interesting posibilities for having the applications integrated with windows ( rootless and multiwindow mode ) I have looked into NX a little after seeing the thread about it a few days ago. Looks like the components are GPL but the integration is the only part that is closed. So I may look at some of the components to see if they would be helpfull. > > the biggest problem would be, I have very little knowledge of Linux as > client PC. I use Linux as a desktop alot. I guess some things to think about would be what software to include. That can get trickey expecially the choice of desktop environment. There are choices to make like should something that works just as good on windows like openoffice be included? > I usually use Windows as client, and Linux as server. > For me, Linux means an unfancy window called "Putty" or "Tera Term". > > --- Okajima. > >> chris >>I downloaded startx.zip today and renamed my c:\cygwin It did not work. >>I checked out what is going on with filemonitor and registry monitor from >>sysinternals. >> >>It actually looks for lots of files including /etc/passwd and /etc/groups >>the big problem seems to be the /tmp and the fonts when I created a >>c:\cygwin\tmp it created a log and it seems to be that the fonts are the >>point of failure. >> >>It seems to get c:\cygwin from HKCU I created a new user and when running >>under the new user it started looking for the files in c:\etc.... >>c:\usr...... >> >>I really don't think making cygwin's version of X portable would be a >>trivial matter. >> >>Okajima, >>Do you have a reason for wanting X instead of vnc for coKnoppix? >>The windows vnc client uses the registry too but changing that code to >>skip the startup dialog and use an address passed on the commandline >> would >>probably be trivial ( I don't know that may be posible already >> >>chris >> >>> >>> >>> >>> Hello Chris and Kerver. >>> >>> thanks for advise. >>> >>> I want to confirm one thing - >>> in your env, you can run startx.zip without /cygwin/usr/bin/X11R6 ? >>> for example, you do >>> [Cygwin]$ mv /usr/bin/X11R6 /usr/bin/X11R6.notfound >>> then you can run XWin.exe from startx.zip? >>> >>> at least, it fails in my env. >>> Windows does not complain. Just Xwin.exe fails without any message. >>> and I found that font files in /usr/bin/X11R6/lib/X11/fonts are >>> necessary. >>> and it also requires /tmp. >>> >>> To make Cygwin/X installer, I have to fix what is really necessary. >>> >>> I hope you try it and send me the result. >>> >>> thanks in advance, Okajima. >>> >>> >>>> >>>>> >>>>> and Kerver, I found that your startx.zip needs full Cygwin/X install. >>>>> if you dont understand, change your c:/cygwin/usr/bin/X11R6 to other >>>>> name. >>>>> your zip does not run. you have any idea? >>>>> >>>>> --- Okajima. >>>> >>>> >>>>A little tip I found is that when adding cygwin directories to the >>>> windows >>>>path add them under user variables not under system variables. That way >>>>you can have an account that does not have access to them for testing >>>>unless the program finds the file without using PATH >>>> >>>>Okajima, does windows not complain that it cannot find a certian file? >>>> >>>>chris >>>> >>> >> > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > coLinux-devel mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-devel > |
|
From: Dan A. <da...@co...> - 2004-04-09 11:55:43
|
On Fri, Apr 09, 2004 at 11:40:14AM +0200, tei wrote: > I can't start a cygwin bash window with coLinux up, or *any* cygwin dll > based app. The error below is what happens when two or more versions of cygwin1.dll are installed. That's why the installation of cygwin1.dll in coLinux's setup is optional. > c:\bin>man ls > 147 [unknown (0x550)] ? 744 shared_info::initialize: size of shared > memory region chan > ged from 47112 to 21008 > 218197 [main] man 744 handle_exceptions: Exception: > STATUS_ACCESS_VIOLATION > 218851 [main] man 744 open_stackdumpfile: Dumping stack trace to > MAN.EXE.stackdump -- Dan Aloni da...@co... |
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 11:46:19
|
Hello Chris.
it is same stuff.
try to add "foo=bar" on your boot prompt and see what happens.
anyway, your problem is solved like this:
1. colinux-daemon gets resolution of current screen.
2. if there is <add_resolution> or such in xml, daemon add it as /proc/cmd data.
3. some script inside colinux decide what resolution to use.
--- Okajima.
>not shure what you mean here but I do know that the boot command line is
>avalible in /proc/cmdline
>
>chris
>
>> and for resolution problem, it is easy to pass any value to coLinux as a
>> kernel parameter.
>> I mean, if you run coLinux with <bootparam>res=640x480</bootparam>,
>> you can see it from inside of coLinux with $ set.
>> so it is easy to make your virtual screen fit to real screen resolution.
>>
>> --- Okajima.
>
|
|
From: <ch...@to...> - 2004-04-09 11:29:46
|
not shure what you mean here but I do know that the boot command line is avalible in /proc/cmdline chris > and for resolution problem, it is easy to pass any value to coLinux as a > kernel parameter. > I mean, if you run coLinux with <bootparam>res=640x480</bootparam>, > you can see it from inside of coLinux with $ set. > so it is easy to make your virtual screen fit to real screen resolution. > > --- Okajima. |
|
From: Dan A. <da...@co...> - 2004-04-09 10:27:59
|
Hello,
Latest snapshot inserts a few console (fltk + nt) changes that you may
want to check out:
* FLTK console:
* The cursor is visible again.
* All consoles + cocon:
* Fixed a bug in the clear operation: let it clear with the right video
erase character so that ncurses apps would appear properly.
* Fixed virtual console switching (alt-f1, alt-f2, etc.) so it will
save/redraw the screen like it should.
It should now feel more close to a real VGA console.
--
Dan Aloni
da...@co...
|
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:20:04
|
Yeah, your guessing is right.
and you can read a virtual partition ( = just a big file on NTFS)
from NT.
if you formatted it with FAT32, use filedisk.exe. I felt it is stable.
with ext2, use ext2 IFS driver (under development...).
--- Okajima.
>On Wednesday 07 April 2004 06:25 pm, Digital Infra, Inc. wrote:
>> I have not read whole thread (it is long!),
>> but if what you focus is about writing a loop back partition,
>> I already did it on conoppix.
>>
>> it can write loop back partition on NTFS.
>
>I have not tried it, but considering that the built-in kernel NTFS write
>support had it's "experimental/dangerous" warnings removed from the help in
>Andrew Morton's recent 2.6 kernels, I am guessing that it will simply refuse
>to do anything dangerous, rather than destroying your filesystem... be warned
>that this advice is probably worth what you paid for it.
>
>Anyhow, my educated guess is that if you create a non-compressed,
>non-encrypted large file using cygwin dd, filled with /dev/random data
>instead of /dev/zero (for extra paranoia about any spase-file issues) on an
>NTFS partition, it's totally safe to use linux's built-in NTFS "write"
>support and loop-devices to write to it, no captive NTFS required. I have
>used this technique to fix unbootable colinux partitions successfully, at
>least. I should document this technique in the wiki, I suppose...
>
>> and probably next version of KNOPPIX has "captive",
>> which loads genie NTFS.dll on Linux from c:/windows/system32,
>> so you can write real NTFS, if you have real Windows installed on your C:.
>
>captive NTFS is pretty nifty... makes you wonder about other drivers (I
>believe there has been some promising experimental work with NT display
>drivers and X as well).
>
>--
>gmt
>
>"How prone all human institutions have been to decay; how subject
>the best-formed and most wisely organized governments have been
>to lose their check and totally dissolve; how difficult it has
>been for mankind, in all ages and countries, to preserve their
>dearest rights and best privileges, impelled as it were by an
>irresistible fate of despotism." --James Monroe
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:20:03
|
Hello Peter "plugwash" Green.
I understand who you are.
well, okay, on my XP ( Professional Japanese edition),
it has RRAS on [Service] section.
and I pushed "start", it said it started successfully.
so I think my XP must have the RRAS function, even I dont know how to use it ;-).
you dont have this?
check your control panel again, please.
but I had noticed one issue -
when I googled with Engilish mode, most site says about Windows server.
but I googled with Japanese, they say about just Windows, not focused on server.
so I suppose that there is possiblity that only Japanese edition has RRAS.
Anyway, your invention is good.
Lets keep considering BOTH possiblities.
I think it is not time to fix to one plan.
and probably some guy on the earth has same plan.
so what we have to do now is, googling, googling, googling,,,,.
--- Okajima.
>yeah i tryed slirp but for me at least it plain would not work on cygwin
>(despite info on the web saying it would) and yes i am plugwash on irc
>
>also i'm pretty sure the remote access server is a feature only found in the
>server versions of windows i certainly can't find any mention of it in the
>services section on my xp home system
>
>and i getting the feeling that it would need as much configuration as
>windows internet connection shareing and the tap driver do
>
>there is a big difference between what is workable in a permanent install by
>a knowlageable user and what is workable for a conoppix type system
>
>i can build this system i describe myself all i need from you is a generic
>char mode device linking to stdin and stdout of my windows side app
>
>-----Original Message-----
>From: Digital Infra, Inc. [mailto:ok...@di...]
>Sent: 08 April 2004 14:47
>To: peter green
>Cc: col...@li...
>Subject: Re: [coLinux-devel] RE: coLinux NAT
>
>
>
>Hello green.
>
>You are the guy talked about slirp on irc?
>
>yes, your invention is good.
>but I guess Windows RRAS can do almost same stuff.
>
> --- Okajima.
>
>
>>DNAT is destination NAT an iptables feature
>>
>>DNAT changes the destination (as apposed to the more common snat which
>>changes the source)
>>
>>a daemon runs on the linux side and listens for connections on port 9999
>>
>>adressess like 127.0.0.0/8 are cidr addresses the /8 part means the first 8
>>bits are significant so in this case it would match everthing from
>127.0.0.0
>>to 127.255.255.255
>>
>>a dnat entry redirects all outgoing TCP connections except those to
>>127.0.0.0/8 (and during development 10.0.0.0/8 but that will be removed
>>later) to 127.0.0.1:9999
>>
>>this daemon picks them up and works out thier original destination by
>>reading /proc/net/tcp
>>
>>this will communicate with a daemon on the host side. during initial
>testing
>>i will use tcp (yes i know this defeats the main object but it allows me to
>>test before more suitable mechanisms are in place) but i am hopeing for
>some
>>kind of generic char device that links to the stdin and stdout of a windows
>>side app.
>>
>>the windows side app will make the conenctions like any other windows app.
>>
>>i will probabblly make it so that connecting to 192.0.2.0/24 makes a
>>connection to 127.0.0.0/24 on the host
>>
>>i chose the 192.0.2.0 range because it is not allowed on the public
>internet
>>and with it's documented intended use i find it unlikly that it will be
>used
>>on a private network
>>
>>from rfc 3330
>>192.0.2.0/24 - This block is assigned as "TEST-NET" for use in
>> documentation and example code. It is often used in conjunction with
>> domain names example.com or example.net in vendor and protocol
>> documentation. Addresses within this block should not appear on the
>> public Internet.
>>
>>-----Original Message-----
>>From: Digital Infra, Inc. [mailto:ok...@di...]
>>Sent: 08 April 2004 03:23
>>To: peter green
>>Cc: col...@li...
>>Subject: coLinux NAT
>>
>>
>>
>>what is dnat?
>>
>>... anyway, if you mention about how to share one IP,
>>I think using RRAS
>> ([Control Panel]->[Service]->[Routing and Remote Access] on Win2k/XP)
>>is one candidate.
>>I have not tested it, but I heard that it is generic NAT driver for Win.
>>
>> --- Okajima.
>>
>>
>>>i'm working on an alternative approach which shouldn't require any special
>>>drivers on the host when finished
>>>
>>>the basic idea is to use a dnat to direct all outgoing connections to a
>>>local daemon
>>>
>>>this will pick them up as connections (note connections not packets) and
>>>will then communicate in some manner with a daemon on the host (i've yet
>to
>>>work out exactly how to do this) this daemon will then use normal winsock
>>>calls to connect to the destination.
>>>
>>>-----Original Message-----
>>>From: col...@li...
>>>[mailto:col...@li...]On Behalf Of
>>>ch...@to...
>>>Sent: 08 April 2004 00:44
>>>To: Digital Infra, Inc.
>>>Cc: ch...@to...; Bart Kerver; Cooperative Linux Development
>>>Subject: Re: [coLinux-devel] XML configuration
>>>
>>>
>>>I have not tried it my self but I may give it a try to see what works.
>>>I was just basing my responce on my experience with trying to make
>>>programs that used other programs compiled with cyg.
>>>
>>>IMHO vnc would probably be better for coknoppix because of the single file
>>>viewer.
>>>
>>>Another thing I was thinking about is that the colinux-daemon may need a
>>>post boot command that you can add to the config file that will run after
>>>it is up and ready to accept the connection.
>>>
>>>Or have you already worked out a way to know when to run X so that it is
>>>not coming up before coLinux is ready?
>>>
>>>Is there a way to use the tap driver as a standalone program or will it
>>>have to be installed for the live cd to work. It would be so cool if a gui
>>>would just pop up and be ready to go the first time the cd is inserted
>>>with no interaction.
>>>
>>>chris
>>>
>>>>
>>>>
>>>> Hello Chris and Kerver.
>>>>
>>>> thanks for advise.
>>>>
>>>> I want to confirm one thing -
>>>> in your env, you can run startx.zip without /cygwin/usr/bin/X11R6 ?
>>>> for example, you do
>>>> [Cygwin]$ mv /usr/bin/X11R6 /usr/bin/X11R6.notfound
>>>> then you can run XWin.exe from startx.zip?
>>>>
>>>> at least, it fails in my env.
>>>> Windows does not complain. Just Xwin.exe fails without any message.
>>>> and I found that font files in /usr/bin/X11R6/lib/X11/fonts are
>>necessary.
>>>> and it also requires /tmp.
>>>>
>>>> To make Cygwin/X installer, I have to fix what is really necessary.
>>>>
>>>> I hope you try it and send me the result.
>>>>
>>>> thanks in advance, Okajima.
>>>>
>>>>
>>>>>
>>>>>>
>>>>>> and Kerver, I found that your startx.zip needs full Cygwin/X install.
>>>>>> if you dont understand, change your c:/cygwin/usr/bin/X11R6 to other
>>>>>> name.
>>>>>> your zip does not run. you have any idea?
>>>>>>
>>>>>> --- Okajima.
>>>>>
>>>>>
>>>>>A little tip I found is that when adding cygwin directories to the
>>>>> windows
>>>>>path add them under user variables not under system variables. That way
>>>>>you can have an account that does not have access to them for testing
>>>>>unless the program finds the file without using PATH
>>>>>
>>>>>Okajima, does windows not complain that it cannot find a certian file?
>>>>>
>>>>>chris
>>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> This SF.Net email is sponsored by: IBM Linux Tutorials
>>>> Free Linux tutorial presented by Daniel Robbins, President and CEO of
>>>> GenToo technologies. Learn everything from fundamentals to system
>>>> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>>>> _______________________________________________
>>>> coLinux-devel mailing list
>>>> coL...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by: IBM Linux Tutorials
>>>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>>>GenToo technologies. Learn everything from fundamentals to system
>>>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>>>_______________________________________________
>>>coLinux-devel mailing list
>>>coL...@li...
>>>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>>---
>>>Incoming mail is certified Virus Free.
>>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>>>
>>>---
>>>Outgoing mail is certified Virus Free.
>>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by: IBM Linux Tutorials
>>>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>>>GenToo technologies. Learn everything from fundamentals to system
>>>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>>>_______________________________________________
>>>coLinux-devel mailing list
>>>coL...@li...
>>>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>>
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>>
>>---
>>Outgoing mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by: IBM Linux Tutorials
>>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>>GenToo technologies. Learn everything from fundamentals to system
>>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>>_______________________________________________
>>coLinux-devel mailing list
>>coL...@li...
>>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>
>---
>Incoming mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>
>---
>Outgoing mail is certified Virus Free.
>Checked by AVG anti-virus system (http://www.grisoft.com).
>Version: 6.0.648 / Virus Database: 415 - Release Date: 31/03/2004
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:20:01
|
I also know not so much about NSIS script,
but adding a feature that renaming default.xml -> default.xml.old.001
would be enough.
--- Okajima.
>On Thu, Apr 08, 2004 at 11:42:52PM +0200, Jaroslaw Kowalski wrote:
>
>> I've recently "upgraded" my colinux 0.6.0 with the latest snapshot.
>>
>> I'm not sure if this was the intention, but the installer replaced my
>> default.colinux.xml with the new version, so I've lost my config.
>
>Well, the idea is that you should keep your own configuration file
>*outside* of the installation directory, a place such as your user
>home directory, and give the '-c' option to the daemon along with
>the file pathname.
>
>> This suggest, that perhaps there should be a 'upgrade' option in the
>> installer script.
>
>Good idea, although I'm not that fluent with NSIS's install script
>syntax, so perhaps Regis can send a patch.
>
>--
>Dan Aloni
>da...@co...
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:19:58
|
Hello Chris,
I have no reason to stick to Cygwin/X.
So I also consider possiblity of VNC too.
and I will write coLinux frame buffer with DirectX accelarated,
I totally have no reason to stick to Cygwin/X.
I just want to investigate every possibility
before I do something actually.
I believe that slow start with a right plan reachs the goal faster.
the biggest problem would be, I have very little knowledge of Linux as client PC.
I usually use Windows as client, and Linux as server.
For me, Linux means an unfancy window called "Putty" or "Tera Term".
--- Okajima.
>
>I downloaded startx.zip today and renamed my c:\cygwin It did not work.
>I checked out what is going on with filemonitor and registry monitor from
>sysinternals.
>
>It actually looks for lots of files including /etc/passwd and /etc/groups
>the big problem seems to be the /tmp and the fonts when I created a
>c:\cygwin\tmp it created a log and it seems to be that the fonts are the
>point of failure.
>
>It seems to get c:\cygwin from HKCU I created a new user and when running
>under the new user it started looking for the files in c:\etc....
>c:\usr......
>
>I really don't think making cygwin's version of X portable would be a
>trivial matter.
>
>Okajima,
>Do you have a reason for wanting X instead of vnc for coKnoppix?
>The windows vnc client uses the registry too but changing that code to
>skip the startup dialog and use an address passed on the commandline would
>probably be trivial ( I don't know that may be posible already
>
>chris
>
>>
>>
>>
>> Hello Chris and Kerver.
>>
>> thanks for advise.
>>
>> I want to confirm one thing -
>> in your env, you can run startx.zip without /cygwin/usr/bin/X11R6 ?
>> for example, you do
>> [Cygwin]$ mv /usr/bin/X11R6 /usr/bin/X11R6.notfound
>> then you can run XWin.exe from startx.zip?
>>
>> at least, it fails in my env.
>> Windows does not complain. Just Xwin.exe fails without any message.
>> and I found that font files in /usr/bin/X11R6/lib/X11/fonts are necessary.
>> and it also requires /tmp.
>>
>> To make Cygwin/X installer, I have to fix what is really necessary.
>>
>> I hope you try it and send me the result.
>>
>> thanks in advance, Okajima.
>>
>>
>>>
>>>>
>>>> and Kerver, I found that your startx.zip needs full Cygwin/X install.
>>>> if you dont understand, change your c:/cygwin/usr/bin/X11R6 to other
>>>> name.
>>>> your zip does not run. you have any idea?
>>>>
>>>> --- Okajima.
>>>
>>>
>>>A little tip I found is that when adding cygwin directories to the
>>> windows
>>>path add them under user variables not under system variables. That way
>>>you can have an account that does not have access to them for testing
>>>unless the program finds the file without using PATH
>>>
>>>Okajima, does windows not complain that it cannot find a certian file?
>>>
>>>chris
>>>
>>
>
|
|
From: Digital I. Inc. <ok...@di...> - 2004-04-09 10:19:57
|
Hello Chris,
Wait, wait. dont upset Chris.
it is good idea, but dont stick on it.
you care about a sequence of X server and KNOPPIX.
I dont know topologilinux, but at least KNOPPIX retry many times
if it can not connect X.
so I think it does not matter which runs first, X server or KDE.
and I dont know VNC stuff, but it is also easy to add "retry" function to VNC viewer.
I think your solution is not wrong, but please keep it in your mind that
there is more than one way to do it.
and for resolution problem, it is easy to pass any value to coLinux as a
kernel parameter.
I mean, if you run coLinux with <bootparam>res=640x480</bootparam>,
you can see it from inside of coLinux with $ set.
so it is easy to make your virtual screen fit to real screen resolution.
--- Okajima.
>How is this for a coKnoppix startup sequence?
>
>(the networking problem still needs to be solved)
>
>autorun.inf starts "vncviewer -listen" in that mode the viewer is
>minimized to the tray listening for a connection.
>coLinux daemon is then started. (possibly as a service)
>
>at the end of the boot process an rc script starts vncserver with
>appropriate options then
>vncconnect -display :1 192.168.0.1
>
>the vncviewer then automaticly pops up!
>
>The only problem is figureing out what geometry to start the vncserver with.
>I like
>vncserver -geometry 1000x685 -depth 16
>for a 1024x768 display on windows this is still reasonable but not ideal
>if the user is running larger but what if the user is running 800x600
>one possible solution would be a little windows program that gathers the
>needed info and makes it avaliable on an embedded httpd
>
>(I could probably write this in a tclkit/starkit (there is a tcl httpd
>avaliable and also modules to read the registry) unless someone comes up
>with a better way of doing this) Or someone wants to do it in C++
>
>Let me know If you think you will need it.
>
>It could share a runtime with the frontend that I wrote for e2fstools if
>you choose to include a version of it.
>http://hem.passagen.se/svto/tlinux/files/
> it is called topoenlarge but I could customize it for coKnoppix.
>
>
>
>chris
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: IBM Linux Tutorials
>Free Linux tutorial presented by Daniel Robbins, President and CEO of
>GenToo technologies. Learn everything from fundamentals to system
>administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
>_______________________________________________
>coLinux-devel mailing list
>coL...@li...
>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>
|
|
From: tei <42...@in...> - 2004-04-09 09:39:58
|
I can't start a cygwin bash window with coLinux up, or *any* cygwin dll
based app.
Generate this type of error messages:
c:\bin>man ls
147 [unknown (0x550)] ? 744 shared_info::initialize: size of shared
memory region chan
ged from 47112 to 21008
218197 [main] man 744 handle_exceptions: Exception:
STATUS_ACCESS_VIOLATION
218851 [main] man 744 open_stackdumpfile: Dumping stack trace to
MAN.EXE.stackdump
some commands break into stackdumps, others warn and run...
Not a problem, IMO, but something that will need to fix for a ulterior
version some day.
This where my ms-dos enviroments vars:
ALLUSERSPROFILE=C:\Documents and Settings\All Users.WINNT
APPDATA=C:\Documents and Settings\t.FIEND\Datos de programa
CommonProgramFiles=C:\Archivos de programa\Archivos comunes
COMPUTERNAME=FIEND
ComSpec=C:\bin\4dos\4NT.EXE
CYGWIN_ROOT=E:\root
HOME=\home\tei
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\t.FIEND
INCLUDE=C:\ARCHIV~1\MICROS~1.NET\VC7\INCLUDE\;%INCLUDE%
KDEDIR=E:\root\opt\kde3
KDEHOME="C:\Documents and Settings\t.FIEND\Datos de programa"
LIB=C:\ARCHIV~1\MICROS~1.NET\VC7\LIB\;%LIB%
LOGONSERVER=\\FIEND
LTDL_LIBRARY_PATH=E:\root\opt\kde3\lib;E:\root\opt\kde3\lib\kde3
MAILENABLE_PATH=C:\bin\MAILEN~1
MSDEV="C:\Archivos de programa\Microsoft Visual Studio
.NET\Common7\IDE\devenv.exe"
NUMBER_OF_PROCESSORS=1
OCAMLLIB=C:\bin\ocalm\lib
OS=Windows_NT
Os2LibPath=C:\WINNT\system32\os2\dll;
Path=C:\bin\Mail
Enable\BIN;C:\bin\texmf\miktex\bin;D:\Perl\bin\;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;"C:\Archivos
de programa\erl5.1\bin";d:\perl\bin;C:\Archivos de programa\Support
Tools\;/e/root/bin;e:/root/bin;C:\Archivos de programa\Archivos
comunes\GTK\2.0\bin;C:\Archivos de
programa\VDMSound\;C:\bin\ocalm\bin;C:\Archivos de programa\ATI
Technologies\ATI Control
Panel;;C:\bin\ocalm\bin;C:\ARCHIV~1\MICROS~1.NET\VC7\BIN\;C:\ARCHIV~1\MICROS~1.NET\COMMON7\IDE\;"C:\WINNT;c:\bin\4dos\;d:\perl\bin"
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 6 Model 4 Stepping 2, AuthenticAMD
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=0402
ProgramFiles=C:\Archivos de programa
PROMPT=$p$g
PYTHONPATH=E:\python
SystemDrive=C:
SystemRoot=C:\WINNT
TEMP=c:\tmp
TMP=c:\tmp
USERDOMAIN=FIEND
USERNAME=t
USERPROFILE=C:\Documents and Settings\t.FIEND
VDMSPath=C:\Archivos de programa\VDMSound\
winbootdir=C:\WINNT
windir=C:\WINNT
|
|
From: Jaroslaw K. <ja...@zd...> - 2004-04-09 09:18:34
|
One idea: Rename "default.colinux.xml" to "sample.colinux.xml" or "colinux.xml.sample"This way users will be more likely to copy/rename it before use. Jarek ----- Original Message ----- From: "Dan Aloni" <da...@co...> To: "Jaroslaw Kowalski" <ja...@zd...> Cc: <col...@li...>; <rn...@ho...> Sent: Friday, April 09, 2004 11:16 AM Subject: Re: [coLinux-devel] Installer overwrites config file > On Thu, Apr 08, 2004 at 11:42:52PM +0200, Jaroslaw Kowalski wrote: > > > I've recently "upgraded" my colinux 0.6.0 with the latest snapshot. > > > > I'm not sure if this was the intention, but the installer replaced my > > default.colinux.xml with the new version, so I've lost my config. > > Well, the idea is that you should keep your own configuration file > *outside* of the installation directory, a place such as your user > home directory, and give the '-c' option to the daemon along with > the file pathname. > > > This suggest, that perhaps there should be a 'upgrade' option in the > > installer script. > > Good idea, although I'm not that fluent with NSIS's install script > syntax, so perhaps Regis can send a patch. > > -- > Dan Aloni > da...@co... > |
81 messages has been excluded from this view by a project administrator.
