[00:53] in ubuntu server, i want to set the domain name. that would not be set in hostname would it? [01:10] Ahmuck: that has always been a bit confusing. it may get picked up from /etc/hosts based on IP [01:10] but different apps probably handle it differently. is this for mail? apache? [01:12] system wide, one apache, one mail, dns, etc. [01:13] Ahmuck: well no guarantees that they all take it from /etc/hosts but I think that is a good place to start [01:14] k, thx, i'll look at it [01:17] the way mine was set up after install was with this line for fqdn - note it is not 127.0.0.1...: 127.0.1.1 mine.example.org mine [01:18] and also this 127.0.0.1 localhost [01:21] u know i am using a version of *buntu as my desktop, but the hosts file has nothing about the domain in it. something like "hostname.domainame" === ember_ is now known as ember [05:52] does anyone have knowlage of getting a dhcp server up to serv thin clients [08:07] peanutb, any standards compatible server should work === macd_ is now known as macd [19:12] on the ubuntu-JeOS server, upon using tasksel, after the "server type" such as LAMP, etc. is installed, it never returns to a prompt, and requires a reboot. i assume that i am not the only one experiencing this [19:43] Ahmuck: im trying an install right now. Ill tell you if i run into the same problem [19:43] hmm [19:44] i just get an aptitude failed [19:44] peanutb: just run tasksel. sudo tasksel [19:44] exactly what i am doing [19:45] on the server side, ubuntu, it runs through everything, but never dumps to a prompt on my older machines [19:51] "tasksel: aptitude failed (100) [19:51] ' [19:51] in a vm? [19:52] no [19:52] its a regualr machine [19:52] running edubuntu but a regular machine [19:52] ah, you have ubuntu-JeOS on a regular machine? [19:52] no [19:52] ohh JeOS [19:52] ah, ok [19:52] yep [19:53] i coulld only get JeOS to install into virtual box because ubuntu-server has a default PAE enabled kernel, and virtual box does not yet support PAE [19:53] i have used tasksel on regular server installs in vmware [19:53] and it seemed to work [19:54] in fact, i am guessing this is part what prompted ubuntu to do the JeOS version [19:54] i think it was more, we dont need a million display drivers etcv [19:54] and want a smaller image [19:54] well, it works, but when the install process is done, it just sat there, never dumped back to the prompt, and required a reset on the machine. i had the same problem with ubuntu-server on my older machines as well yesterday [19:55] so i have a blue screen, red progress bar at 100% that just sits there [19:55] yeah [19:56] tasksel seems quite buggy to me [19:56] actually, i had the same issue upon reboot of ubuntu-server, never dropping to a prompt, just sitting there after the last task. only drops to a prompt if i hit a key on the keyboard [19:56] not sure why [19:57] i'm guessing it's the machines problem. [19:57] but i did this on five machines of the same config [19:59] i do have a question however, why do they advise not changing root? it would seem to me if someone could connect to your *buntu box and you had not changed root, with the default user they could change root password and you would be screwed [19:59] the only reason i can think of not changing it is because of apt and configuration issues that are defualt which *buntu has set up to use the root (ubuntu defalt) to setup and configure [20:00] root is disabled [20:00] there is no password [20:00] they suggest not changing it because its simply better to have that extra layer of security of what is that username [20:00] yes, but u can set a password on it using su -i [20:00] disabled? [20:01] so essentially it's not really disabled if you can get to it by su -i correct? [20:01] su -i? [20:01] its login is disabled [20:01] ya, try it. drops you to root after you enter your sudo password [20:01] you can still sudo su to it === ember_ is now known as ember [20:01] yes. thats the point [20:01] you can have root access [20:02] seems like a great opportunity to create a back door user [20:02] at install? [20:02] you have to have sudo rights to be able to set a root password [20:03] yes, it would not take much to set up a distro with a user who had sudo rights and then a notifier when it was installed somewhere [20:04] you should MD5 the iso or image of whatever you are installing [20:04] and make sure its from a trusted source [20:04] sure its possable to have a back door [20:04] but who says you wont just add a user on a regular debian system that has shadow access [20:06] Ahmuck: https://help.ubuntu.com/community/RootSudo?highlight=%28sudo%29 has much better reasons [20:14] what is the min ubuntu-server will run? i am using 64 on my hard machines and 256 on my vm [20:26] nm, i found it [20:34] peanutb: installing ubuntu-server with 64mb ram tasksel won't come up, and requires me to run it after installation [20:35] which i would have expected [20:39] er, which i expected to happen on a low mem mode