<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hey, doesn't it depend on what you want to do? There are some times that sudo works well, and others where it's a good idea to be root. For example, if you're doing a whole raft of command-line commands and you have to be root, it's a whole lot easier to do an su and go to root than to type sudo in front of every command. Yes, it lets you in to the possibility of doing damage, but you have to know the risk. Frankly, I wouldn't use Ubuntu if I couldn't go to root, and I find sudo a pain in the neck. But does this mean it's bad for others? Of course not. cheers, pete Derek Broughton wrote: <blockquote cite="mid:to1bh6-uag.ln1@morgen.pointerstop.ca" type="cite"> <pre wrap="">Jerry Houston wrote: </pre> <blockquote type="cite"> <pre wrap="">On Wednesday 24 June 2009 03:26:30 am Mark Syms wrote: </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">How does one set the root password, or is this never done ? </pre> </blockquote> <pre wrap="">In Ubuntu, this is never done. The first user that is added to the system (the one you created during install) is created as a member of the admin group and this group can use sudo to run anything as root. </pre> </blockquote> <pre wrap="">Heh ... it's done here. </pre> </blockquote> <pre wrap=""> LOL. While I oppose activating root accounts on principle, I would never have said it's "never done" :-) </pre> </blockquote> </body> </html>