colinux-devel — Cooperative Linux development mailing list

Re: [coLinux-devel] Getting started building coLinux.

[Steven E. <ste...@ya...>]

--- Ballard Jonathan <sac...@ho...> wrote:
> It is possible to use only MinGW.  Currently, the source code uses
> standard
> C (stdlib, stdio, etc) conventions and Microsoft API's only have
> limited
> implementation of such conventions.  Microsoft has an optional
> run-time
> library, installed on demand like cygwin1.dll, that could be used
> intead of
> Cygwin or MinGW but the benefits does not change because an extra
> *.dll file
> was required.  The best option is to rewrite the portions of the
> coLinux
> source to use only the native DDK and PlatformSDK conventions and
> procedures.  I do not see such change as a priority issue at this
> time.  As
> coLinux becomes more secure, I project the rewrite to more native OS
> code to
> happen.  The standard C conventions are easier use at this time --
> especially for those that program with linux more.

You could do it from a Mingw-Cross compiler on Linux. I think one of
our developers was able to build CoLinux using the Mingw linker rather
than linking to Cygwin.

Thanks
Steven


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

Re: [coLinux-devel] NT service was: Running as non-admin

[Maxious(Alex Sadleir) <ma...@la...>]

I use firedaemon for colinux and apache as windows services.  They have 
a lite (ie free) version avalible. http://www.firedaemon.com/

Re: [coLinux-devel] NT service was: Running as non-admin

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Crypto wrote:
|>Standard srvany.exe from reskit does not allow to start colinux as
|>service. I suppose it happens because of creating and attaching
|>console.
|
|
| I have been using colinux with srvany as a service from the beginning.
| The -d switch does the trick as it prevents the console from being
| created.
|
| This is how I did it. Srvany just starts a script called start.cmd with
| this contents:
|
| c:
| cd \colinux
| colinux-daemon -d

It would be nice if this could work somehow using cygrunsrv.exe.  I'm
currently moving my coLinux directory into c:\cygwin\coLinux to see if
the path works properly after that, since I'm currently getting System
Log events that state that "The system cannot find the file specified".

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAV2DhuYsUrHkpYtARAiKjAJ0U+fr4kH8qnbAO14sEgiXewPgDKgCbBm5F
qudK7suba8E9OkhvkDPxf4g=
=4GQs
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] NT service was: Running as non-admin

[Crypto <cr...@dv...>]

> Standard srvany.exe from reskit does not allow to start colinux as
> service. I suppose it happens because of creating and attaching
> console.

I have been using colinux with srvany as a service from the beginning. 
The -d switch does the trick as it prevents the console from being 
created.

This is how I did it. Srvany just starts a script called start.cmd with
this contents:

c:
cd \colinux
colinux-daemon -d

--
crypto

Re: [coLinux-devel] Getting started building coLinux.

[Ballard J. <sac...@ho...>]

> >>>3.) Is it dumb to ask if it's possible to use MinGW rather
> >>>than Cygwin to do builds?

> The need for cygwin1.dll is optional.

It is possible to use only MinGW.  Currently, the source code uses standard
C (stdlib, stdio, etc) conventions and Microsoft API's only have limited
implementation of such conventions.  Microsoft has an optional run-time
library, installed on demand like cygwin1.dll, that could be used intead of
Cygwin or MinGW but the benefits does not change because an extra *.dll file
was required.  The best option is to rewrite the portions of the coLinux
source to use only the native DDK and PlatformSDK conventions and
procedures.  I do not see such change as a priority issue at this time.  As
coLinux becomes more secure, I project the rewrite to more native OS code to
happen.  The standard C conventions are easier use at this time --
especially for those that program with linux more.

Re: [coLinux-devel] NT service was: Running as non-admin

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mikhail Gusarov wrote:
~ > Standard srvany.exe from reskit does not allow to start colinux as
| service. I suppose it happens because of creating and attaching
| console.

That's why I pass it the '-d' option to disable the automatic launching
of that console.

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAV1f3uYsUrHkpYtARAjPGAJ9i/GD7gVLqa0rCBQcfq2fQ+tumvQCfaHnW
ptEG1UdTzBsbCPHuSR2Qfrs=
=J6B7
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] NT service was: Running as non-admin

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mikhail Gusarov wrote:
| You (pat...@pc...) wrote:
|
|
|>In my searching, I came across the fact that if you have not purchased a
|>copy of the NT Resource Kit, then you cannot legally use/distribute(?)
|>instsrv.exe and srvany.exe.  I also came across an e-mail in the cygwin
|
|
| Sounds strange. I've freely downloaded a copy of Windows2003 ResKit from
| Micro$oft site.
|

I'm using Win2K.

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAV1eZuYsUrHkpYtARAuiAAJoD/XNpVL0l9vfTsyZISeautwaKRwCeLP7l
yBL8HZtCpkv9QH0Cf67i/Gk=
=KK3f
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

RE: [coLinux-devel] re: Admin, reply

[Sean B. <sea...@so...>]

FWIW I like the idea of running colinux as a service. 
As long as it is still possible to attach a terminal. 
Which I guess it would anyway.

Anyway, this kind of becomes important as and when it
is possible to run multiple concurrent colinux hosts. 
Kind of a gsx server for free on windows.



(sorry Sean, I replied to you rather than the list the first time :) )
- Hey! no problem ;)

Robert

-- 
-Give a man a fire and you keep him warm for a night. Set him on fire
and you keep him warm for the rest of his life. 

RE: [coLinux-devel] NT service was: Running as non-admin

[Sean B. <sea...@so...>]

> 
> > In my searching, I came across the fact that if you have
> not purchased
> > a copy of the NT Resource Kit, then you cannot legally
> > use/distribute(?) instsrv.exe and srvany.exe.  I also came 
> across an
> > e-mail in the cygwin
> 
> Sounds strange. I've freely downloaded a copy of Windows2003
> ResKit from Micro$oft site.

Parts, but not all, of the resource kit have always been
freely available. The full resource kit is a commercial offering.

srvany seems to be available. Is srvany part of the w2k+3 reskit 
that you downloaded?

Re: [coLinux-devel] Getting started building coLinux.

[tei <42...@in...>]

ch...@to... escribió:

>>>3.) Is it dumb to ask if it's possible to use MinGW rather
>>>than Cygwin to do builds?  I know about using Cygwin and
>>>MinGW on Windows as a shell and build environment, but I
>>>don't have any experience using them as a build tool platform
>>>under Linux.  I do at least see that w32api from MinGW is
>>>being used....
>>
>>This might be interesting. I don't know why though. IMO it is
>>best to keep the build environment the same as the devs.
>>
> 
> 
> To the best of my knowlege. If the cygwin1.dll is needed for the posix
> layer it provides then It would not be possible to build under MinGW.
> MinGW is just a port of GCC to windows for programing with the windows api
> Cygwin provides a posix layer for easy porting of *NIX programs to
> windows.
> 
> If the posix layer is not needed then MinGW would be the better build
> environment so that the cygwin1.dll is not required. The cygwin1.dll is
> very sensitive to having multiple versions on machines. I do not know if
> backwards compatibility is always maintained so it may not always be as
> simple as replacing cygwin1.dll in either coLinux or the cygwin install
> with the newer one.
> 
> chris
> 

Hi!

<offtopic>
<info about cygwin>

The need for cygwin1.dll is optional. You can build the same binary from 
  MinGW and Cygwin. Except.. Cygwin provice some extra features on 
Cygwin1.dll, of course, If you use that features, you need that dll.

So, MinGW is cool (the Min means minimal?), and Cygwin is cool. Both are 
cool.

note:
You may already know that, this is a reminder for others.

</info about cygwin>
</offtopic>

Re: [coLinux-devel] NT service was: Running as non-admin

[Mikhail G. <gu...@go...>]

You (pat...@pc...) wrote:

> In my searching, I came across the fact that if you have not purchased a
> copy of the NT Resource Kit, then you cannot legally use/distribute(?)
> instsrv.exe and srvany.exe.  I also came across an e-mail in the cygwin

Sounds strange. I've freely downloaded a copy of Windows2003 ResKit from
Micro$oft site.

-- 
Sincerely yours, Mikhail A Gusarov
Software Engineer
IBM Solutions Group, Axmor Software
ICQ# 111575219

Re: [coLinux-devel] NT service was: Running as non-admin

[Mikhail G. <gu...@go...>]

You (pat...@pc...) wrote:

> I second this motion.  I can devote some time to looking into what it
> will take to run this as a service, although it appears that someone
> already used the approach I was going to try.  That being, find a

Yes, I've tried to do this.

> wrapper program that will allow an ordinary program to be run as a
> service and attempt to use it.

Standard srvany.exe from reskit does not allow to start colinux as
service. I suppose it happens because of creating and attaching
console.


-- 
Sincerely yours, Mikhail A Gusarov
Software Engineer
IBM Solutions Group, Axmor Software
ICQ# 111575219

Re: [coLinux-devel] NT service was: Running as non-admin

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jason A. Pattie wrote:
| ch...@to... wrote:
| | I definatly think that running as a service should be a goal of the
| project.
| | Although there are plenty of uses for it running as a program there are
| | many more that would be better as a service.
|
| I second this motion.  I can devote some time to looking into what it
| will take to run this as a service, although it appears that someone
| already used the approach I was going to try.  That being, find a
| wrapper program that will allow an ordinary program to be run as a
| service and attempt to use it.
|
| I also think it should still be allowed to run the way it does now, too.

In my searching, I came across the fact that if you have not purchased a
copy of the NT Resource Kit, then you cannot legally use/distribute(?)
instsrv.exe and srvany.exe.  I also came across an e-mail in the cygwin
mailing list that discussed this very issue and gave the alternative of
cygrunsrv.exe.  I've started playing with this as a means to freely
install and distribute colinux-daemon.exe as a running service.
Unfortunately, it hasn't worked yet either.  I've attempted the following:

(from cygwin prompt)
cygrunsrv.exe --install coLinux --path
/cygdrive/c/coLinux/colinux-daemon.exe --args '-d'

I've also tried this:

cygrunsrv.exe --install coLinux --path
/cygdrive/c/WINNT/system32/cmd.exe --args '/k
"c:\coLinux\colinux-daemon.exe -d"'

It appears that the service is started when using the first example.
But the colinux-console cannot connect to it, and I can't ping the IP of
the coLinux instance.

For the second example, the following error message is spit out:

cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error
1062: The service has not been started.

Going to try to figure out why the service isn't starting.  Could it
potentially have something to do with requirements of cmd.exe or the
colinux-daemon executable that aren't being met inside the service
environment provided?

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAVzNwuYsUrHkpYtARAo3PAJ4zJY0SA/bN9irLYpR+N7kRdLOrnQCfRZJH
bKEKYCJEi11NAS4PYIQApmE=
=2Qg/
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

Re: [coLinux-devel] re: Admin, reply

[Robert <ro...@ar...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body>
<br>
In case it helps, in XP you can log on as a non-admin and do a 'runas
/user:administrator c:\colinux\colinux-daemon.exe' <br>
There are options to store&nbsp; the password in a hash so that you don't
need to type it in every time ('runas /?' for details)&nbsp; Or, using the
method I prefer for something like this is to: 1) create a shortcut,
open it's properties&nbsp; 2) choose the shortcut tab 3)&nbsp; click advanced,
and&nbsp; 4) check the box to have it request&nbsp; alternate credentials to run
under.&nbsp; This avoids the too common security blunder of logging on and
working as a "root" user, but does maintain the issues of granting
priviledges to a process/program.<br>
<br>
This. of course, does not help if you are not lucky enough to have an
admin account...<br>
<br>
(sorry Sean, I replied to you rather than the list the first time :) )<br>
<br>
Robert<br>
<pre class="moz-signature" cols="72">-- 
-Give a man a fire and you keep him warm for a night. Set him on fire and you keep him warm for the rest of his life. </pre>
<br>
Sean Brook wrote:
<blockquote cite="mid000701c40b6c$2b2b5490$016ca8c0@connor" type="cite">
  <blockquote type="cite">
    <pre wrap=""> It's a shame admin is needed but what I expected. A shame 
because if you have admin you'd likely find coLinux less 
useful; you can reboot, install services etc anyway.
    </pre>
  </blockquote>
  <pre wrap=""><!---->As has been pointed out the nature of colinux requires
Administrator access. This is the nature of Windows security
and is not a colinux issue. I don&#8217;t see how anyone that has 
admin access to their box would find this a problem. To
put it another way: those who do not have admin access do
not have admin access for a reason. I reckon most admins
would not like the thought of people being able to run
a linux box inside their otherwise `secure` environment.

/tongue in cheek:
I am looking forward to a whole new generation of
'worm machines'. Virtual linux boxes with a small
footprint that deal doom to Windows, all running 
as a hidden service. Maniac laughter etc.



-------------------------------------------------------
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_id70&amp;alloc_id638&amp;op=click
_______________________________________________
coLinux-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:coL...@li...">coL...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/colinux-devel">https://lists.sourceforge.net/lists/listinfo/colinux-devel</a>

  </pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">-- 
-Give a man a fire and you keep him warm for a night. Set him on fire and you keep him warm for the rest of his life. 
</pre>
</body>
</html>

Re: [coLinux-devel] image tool

[Olivier S. <co...@a-...>]

----- Original Message -----
From: <ch...@to...>
To: <col...@li...>
Sent: Tuesday, March 16, 2004 1:31 PM
Subject: [coLinux-devel] image tool


> I wrote a program in tcl/tk that can create empty files and provides a gui
> wrapper for mke2fs e2fsck and resize2fs. It will create a new file or
> enlarge an existing image.

for people interested on creating and using such images, see also :

"Create Block Devices With Cygwin" and "Add Swap Partition" on the Wiki :

http://www.colinux.org/wiki/index.php/CreateBlockDevicesWithCygwin

and

http://www.colinux.org/wiki/index.php/AddSwapPartition


Also, a few files of given size (round numbers) were created and are
available there :

http://62.212.109.174/colinux/fs/

http://62.212.109.174/colinux/swap/



O. Souiry

RE: [coLinux-devel] re: Admin, reply

[Sean B. <sea...@so...>]

>=20
>  It's a shame admin is needed but what I expected. A shame=20
> because if you have admin you'd likely find coLinux less=20
> useful; you can reboot, install services etc anyway.
As has been pointed out the nature of colinux requires
Administrator access. This is the nature of Windows security
and is not a colinux issue. I don=92t see how anyone that has=20
admin access to their box would find this a problem. To
put it another way: those who do not have admin access do
not have admin access for a reason. I reckon most admins
would not like the thought of people being able to run
a linux box inside their otherwise `secure` environment.

/tongue in cheek:
I am looking forward to a whole new generation of
'worm machines'. Virtual linux boxes with a small
footprint that deal doom to Windows, all running=20
as a hidden service. Maniac laughter etc.

Re: [coLinux-devel] NT service was: Running as non-admin

[Jason A. P. <pat...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ch...@to... wrote:
| I definatly think that running as a service should be a goal of the
project.
| Although there are plenty of uses for it running as a program there are
| many more that would be better as a service.

I second this motion.  I can devote some time to looking into what it
will take to run this as a service, although it appears that someone
already used the approach I was going to try.  That being, find a
wrapper program that will allow an ordinary program to be run as a
service and attempt to use it.

I also think it should still be allowed to run the way it does now, too.

- --
Jason A. Pattie
pat...@xp...
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQFAVx0MuYsUrHkpYtARAvz6AJ9nvSdSiUY5fKCWwLI0XrMcr5AMfwCeM3St
qxVxxp2dtBxHI9P7gmux5lU=
=j+iO
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

[coLinux-devel] re: Admin, reply

[Jago P. <jag...@ca...>]

 It's a shame admin is needed but what I expected. A shame because if you
have admin you'd likely find coLinux less useful; you can reboot, install
services etc anyway.

 I'll document the error message and what it means in the WIKI. I'm
suprised no one else has experienced the error message before. I guess
nearly everyone justs runs as admin all the time. Windows users are less
likely to run the daemon from the command line so it might be a good idea
to throw up a box that says "Admin rights required - access to X rights"
whatever the exact priverlages are needed.

 Personally I just dual boot at home or just use linux all the time.
coLinux was interesting for me for use at work so I can run linux on
University boxes.

-- 
Catholic.org is just my email provider, my main email.
jag...@ho... is my spammail account.


-----------------------------------------
This email was sent using FREE Catholic Online Webmail!
http://webmail.catholic.org/

RE: [coLinux-devel] Getting started building coLinux.

[<ch...@to...>]

>> 3.) Is it dumb to ask if it's possible to use MinGW rather
>> than Cygwin to do builds?  I know about using Cygwin and
>> MinGW on Windows as a shell and build environment, but I
>> don't have any experience using them as a build tool platform
>> under Linux.  I do at least see that w32api from MinGW is
>> being used....
> This might be interesting. I don't know why though. IMO it is
> best to keep the build environment the same as the devs.
>

To the best of my knowlege. If the cygwin1.dll is needed for the posix
layer it provides then It would not be possible to build under MinGW.
MinGW is just a port of GCC to windows for programing with the windows api
Cygwin provides a posix layer for easy porting of *NIX programs to
windows.

If the posix layer is not needed then MinGW would be the better build
environment so that the cygwin1.dll is not required. The cygwin1.dll is
very sensitive to having multiple versions on machines. I do not know if
backwards compatibility is always maintained so it may not always be as
simple as replacing cygwin1.dll in either coLinux or the cygwin install
with the newer one.

chris

[coLinux-devel] image tool

[<ch...@to...>]

I wrote a program in tcl/tk that can create empty files and provides a gui
wrapper for mke2fs e2fsck and resize2fs. It will create a new file or
enlarge an existing image.

It is still a little raw yet. There is currently a bug with paths to
images that contain spaces but I discovered that at the last minute and
need to devote some time to other things.

I also plan to port mkswap so that It can create swap images.

The program does not create sparce files as my main intention is for it to
be used with systems that can boot the kernel nativly as well.

It does not allow for extra options on mke2fs as my goal was to create a
newbie interface and I figure people who understand those options would
prefer to use mke2fs from the command line.

the program is called topoenlarge and is here
http://hem.passagen.se/svto/tlinux/files/

chris

Re: [coLinux-devel] NT service was: Running as non-admin

[<ch...@to...>]

I definatly think that running as a service should be a goal of the project.
Although there are plenty of uses for it running as a program there are
many more that would be better as a service.

In most situations where it would be installed on a server to provided a
dual os server as a service would be the way to run It so that the machine
does not have to be left with an administrator logged in.

Also there are probably many situations where a user of lesser priveleges
may need to log in or use services running under coLinux from their
windows session.

chris

>
> You (plu...@p1...) wrote:
>
>> for those who read how colinux works it is obvious it will need admin
>> privs
>
> Ok, it seems that you need enough privilegies to run
> coLinux. Administrator has such a rights and services running on the
> machine also could have enough power :) to boot coLinux. It seems
> impossible for now to run coLinux as NT service because its framework
> (startup executable) running interactive programs (yes, I've played
> with "Interactive" frag in services settings), such as initially
> attached console. I've tried to accompish this, but was
> unsuccesfull. I've used srvany.exe from ResKit and the target service
> stopped immediately after starting (I suppose colinux-daemon.exe
> reported some error and stopped). It may be fine to learn coLinux run
> as service and I don't think it will require significant rewrite of
> source code.
>
> --
> Sincerely yours, Mikhail A Gusarov
> Software Engineer
> IBM Solutions Group, Axmor Software
> ICQ# 111575219
>
>
>
> -------------------------------------------------------
> 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
>

RE: [coLinux-devel] Getting started building coLinux.

[Sean B. <sea...@so...>]

> -----Original Message-----
> From: col...@li... 
> [mailto:col...@li...] On Behalf 
> Of Clemmitt M. Sigler
> Sent: Monday, March 15, 2004 9:33 PM
> To: col...@li...
> Subject: [coLinux-devel] Getting started building coLinux.
> 
> 
> Hi all,
> 
> I've read the building and cygwin-cross-build files in the 
> source tarball's doc directory in preparation for trying out 
> a build.  But I have some *really* dumb questions, if anyone 
> would be willing to answer them:
> 
> 1.) I couldn't find this in the building file but, if I understand 
> correctly, the build system for both the coLinux kernel 
> (vmlinux) and the OS daemons and support code is 
> i686-pc-linux.  IOW, you build everything on a running Linux 
> system, not under Windows.  Is this correct?
I would say this is correct. The build host is ???-??-linux.
Creating the cygwin tool chain enables cross compiling to a
a i686-pc-cygwin target

> 
> 2.) Is coLinux self-hosting, that is, can I build colinux on 
> a running (and stable) coLinux system?
Yes, and I think that should be your intention. colinux is
stable enough to do that (use a binary to begin?). 
IMO it goes to avoid some pitfalls like using different 
versions of gcc and compiling modules inside colinux with
headers different from that which you used to compile the
kernel.

> 
> 3.) Is it dumb to ask if it's possible to use MinGW rather 
> than Cygwin to do builds?  I know about using Cygwin and 
> MinGW on Windows as a shell and build environment, but I 
> don't have any experience using them as a build tool platform 
> under Linux.  I do at least see that w32api from MinGW is 
> being used....
This might be interesting. I don't know why though. IMO it is
best to keep the build environment the same as the devs.

> 
> If I have time to work on building, I'll add the info I learn 
> along the way to the Wiki.  TIA.
> 
> 					Clemmitt Sigler
> 
> 
> 
> -------------------------------------------------------
> 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
> 

[coLinux-devel] NT service was: Running as non-admin

[Mikhail G. <gu...@go...>]

You (plu...@p1...) wrote:

> for those who read how colinux works it is obvious it will need admin privs

Ok, it seems that you need enough privilegies to run
coLinux. Administrator has such a rights and services running on the
machine also could have enough power :) to boot coLinux. It seems
impossible for now to run coLinux as NT service because its framework
(startup executable) running interactive programs (yes, I've played
with "Interactive" frag in services settings), such as initially
attached console. I've tried to accompish this, but was
unsuccesfull. I've used srvany.exe from ResKit and the target service
stopped immediately after starting (I suppose colinux-daemon.exe
reported some error and stopped). It may be fine to learn coLinux run
as service and I don't think it will require significant rewrite of
source code.

-- 
Sincerely yours, Mikhail A Gusarov
Software Engineer
IBM Solutions Group, Axmor Software
ICQ# 111575219

Re: [coLinux-devel] Getting started building coLinux.

[Dmitriy K. <dm...@ka...>]

Welcome, Clemmitt.

You wrote 16 Mar 2004 ., 3:32:32:
CMS> 1.) I couldn't find this in the building file but, if I understand
CMS> correctly, the build system for both the coLinux kernel (vmlinux) an=
d
CMS> the OS daemons and support code is i686-pc-linux.  IOW, you build
As I understood, OS daemons/support code are built using
i686-pc-cygwin
CMS> everything on a running Linux system, not under Windows.  Is this
CMS> correct?
no

CMS> 2.) Is coLinux self-hosting, that is, can I build coLinux on a
CMS> running (and stable) coLinux system?
I did it sucessfully with 0.5.4
(I used Debian 1gb image,updated from Debian Woody 3.r1 CDs and
heavily patched cobuild.sh)
(but you need modern(2.95 wasn't worked for me) GCC/binutils installed FI=
RST and build
cross-development CYGWIN toolchain after than



--=20
=D1 =F3=E2=E0=E6=E5=ED=E8=E5=EC,
 Dmitriy                          mailto:dm...@ka...

[coLinux-devel] Getting started building coLinux.

[Clemmitt M. S. <sig...@bl...>]

Hi all,

I've read the building and cygwin-cross-build files in the source
tarball's doc directory in preparation for trying out a build.  But
I have some *really* dumb questions, if anyone would be willing to
answer them:

1.) I couldn't find this in the building file but, if I understand 
correctly, the build system for both the coLinux kernel (vmlinux) and
the OS daemons and support code is i686-pc-linux.  IOW, you build
everything on a running Linux system, not under Windows.  Is this
correct?

2.) Is coLinux self-hosting, that is, can I build coLinux on a
running (and stable) coLinux system?

3.) Is it dumb to ask if it's possible to use MinGW rather than
Cygwin to do builds?  I know about using Cygwin and MinGW on Windows
as a shell and build environment, but I don't have any experience
using them as a build tool platform under Linux.  I do at least see
that w32api from MinGW is being used....

If I have time to work on building, I'll add the info I learn along
the way to the Wiki.  TIA.

					Clemmitt Sigler