[00:50] I'm running Ubuntu 13.10 Server, and have installed ubuntu-desktop. When the server boots up it goes straight into the Desktop login GUI. I was wondering if its possible to prevent that from happening, and instead be faced with the traditional black login command screen? [00:51] sure it is [00:51] there are a couple of ways you can do that [00:52] you can boot into init 3, which by default doesnt use the gui, second, you can adjust the display manager, such as GDM, MDM or LightDM [00:52] the simplist (not best) way to achieve this is to move the /etc/init.d/gdm file to another name [00:53] I've read suggestions online, however I'm looking for the "safest" method. I'd like to be able to start the desktop from the command screen when and if i need [00:53] sure, that makes sense, working with the display manager is usually best [00:53] typing "startx" will always launch your gui [00:53] as long as you have a gui to launch [00:55] alternatively you can use grub [00:55] GRUB_CMDLINE_LINUX_DEFAULT="text" [00:55] im going to try the grub method first, and then i'll report back [00:56] used to be i just never installed the display manager [03:11] stratus_ss, hi [03:12] hey dark, I have some questions regarding the build process [03:13] I have worked my way through most of the debian maintainers guide, as well as the ubuntu how to [03:13] and several how tos on pbuilder === ph_afk is now known as ph [03:14] however I cant seem to get anything other than simple things ("bc" for example) to actually successfully build [03:14] stratus_ss, do you have the PPA's installed? [03:15] either in the config file, or you can do it runtime when running 'update' [03:15] dark, ---> this one v [03:15] deb http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu trusty main [03:15] or do you mean in the /etc/pbuilderrc [03:16] stratus_ss, I do it like this "pbuilder-dist trusty amd64 update --override-config --othermirror "deb http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu trusty main|deb http://ppa.launchpad.net/gnome3-team/gnome3-next/ubuntu trusty main" [03:17] since I switch between different configs (trusty, trusty+ppa, etc) so its easier to just have a few different update scripts [03:18] stratus_ss, if you do have the ppa installed, pastebin the build log (~/pbuilder/trusty_result/last_operation.log) [03:19] what I am ultimately trying to acheive is understanding the backporting process, which if i understand correctly, is what is used to feed the ppa [03:19] we are not backporting! we are ahead of ubuntu ;) [03:20] ok, i guess to my way of thinking is we are "backporting" the source to deb [03:20] or rather the upstream [03:20] ok, backporting is not really the term [03:21] ok, my appologies [03:21] but the build system mostly handles the source side of things [03:21] then to be more verbose, i want to be able to build the dependencies to be able to provide those to the ppa [03:21] when you do uupdate -v 3.10.2 tarball [03:21] all the dependencies should be there already for 3.10.x [03:22] n00b question -> who creates them in the first place [03:22] btw, just to go back a few steps, you will need to use the saucy pocket to build 3.10.x for the timebeing "i.e. deb http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu saucy main" [03:23] stratus_ss, we update them from ubuntu or debian as required [03:23] stratus_ss, or even better use a saucy pbuilder ;) [03:24] I am going to start copying 3.10 packages into trusty pocket, but haven't started yet. === ph_afk is now known as ph === ph_afk is now known as ph === ph_afk is now known as ph === ph is now known as ph_afk === Guest25333 is now known as jokerdino === jokerdino is now known as Guest92142 === ph_afk is now known as ph === Guest25333 is now known as jokerdino === ph_afk is now known as ph === ph_afk is now known as ph === ph is now known as ph_afk [19:40] hey [19:41] is ubuntu-gnome team have found enough devs to be able to continue the project ?