On Fri, 2013-12-13 at 16:49 +0000, Tom H wrote: > On Fri, Dec 13, 2013 at 4:25 PM, PaulNM <deb...@paulscrap.com> wrote: > > On 12/13/2013 10:03 AM, Tom H wrote: > >> On Tue, Dec 10, 2013 at 1:57 AM, Ralf Mardorf > >> <ralf.mard...@alice-dsl.net> wrote: > >>> On Tue, 2013-12-10 at 02:25 +0100, Ralf Mardorf wrote: > >>>> On Mon, 2013-12-09 at 19:08 +0000, Tom H wrote: > >>>>> > >>>>> The Ubuntu-created grub.cfg cannot be blamed for a GDM problem. If GDM > >>>>> is being launched, grub's job has been done many seconds ago. > >>>> > >>>> This seems to be true here, but you're mistaken, a boot option could > >>>> still cause something when a DE session already is running, e.g. > >>>> "threadsirq", "noatime", sure, "noatime" won't brake something, but > >>>> "threadirqs" at least could slow down GUI performance, assumed it's a > >>>> lowlatency kernel. > >>> > >>> PS: Let alone options such as e.g. "single" ;). > >> > >> The "single" kernel cmdline option would never launch GDM. > > > > I believe that was his point, and the reason for the smiley ;). > > Most would say preventing something from happening is a form of > > affecting it. > > Except that "single" doesn't make GDM fail, it doesn't even launch it. > It's not the same thing.
The result is the same, you won't end up with the option to launch Iceweasel by a launcher on the GNOME desktop ;). It was just an ironical explanation what a single boot option could cause and it's too funny, since the option is called "single". -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386958087.688.236.camel@archlinux
