From: Jago P. <jag...@ca...> - 2004-03-16 14:33:46
|
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/ |
From: Sean B. <sea...@so...> - 2004-03-16 15:34:36
|
>=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. |
From: Robert <ro...@ar...> - 2004-03-16 16:35:54
|
<!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 the password in a hash so that you don't need to type it in every time ('runas /?' for details) Or, using the method I prefer for something like this is to: 1) create a shortcut, open it's properties 2) choose the shortcut tab 3) click advanced, and 4) check the box to have it request alternate credentials to run under. 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’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&alloc_id638&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> |
From: Sean B. <sea...@so...> - 2004-03-16 19:22:41
|
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. |