| 1 |
On Wed, Mar 23, 2016 at 07:46:09AM +0100, J. Roeleveld wrote |
| 2 |
> On Tuesday, March 22, 2016 04:51:52 PM Grant Edwards wrote: |
| 3 |
> |
| 4 |
> > You're probably right, the magick sysrq feature pretty much obviates |
| 5 |
> > the need to boot to console to protect against buggy X11 servers. But, |
| 6 |
> > it's fairly recent and Linux-specific. So, the boot-to-console trait |
| 7 |
> > (which evolved pre-sysrq -- and even pre-Linux, and has very little |
| 8 |
> > "cost") hasn't died out yet... |
| 9 |
> |
| 10 |
> Yes, but it Xorg isn't that buggy to warrant the inconvience of |
| 11 |
> a console boot on a desktop/laptop. Even with proprietary nvidia |
| 12 |
> drivers. |
| 13 |
|
| 14 |
How much inconvenience is it, really? I have a short script ~/bin/x |
| 15 |
|
| 16 |
#! /bin/bash |
| 17 |
startx -- -nosilk -config ${1}xorg.conf & |
| 18 |
|
| 19 |
At the commandline I simply type "x" and hit the {ENTER} key. Note |
| 20 |
the "-config ${1}xorg.conf". The default (i.e. no parameters passed to |
| 21 |
script) is to go with the regular xorg.conf. But if I want to go with a |
| 22 |
lower resolution (e.g. 640x480) from "640xorg.conf", I would start with |
| 23 |
|
| 24 |
x 640 |
| 25 |
|
| 26 |
This allows me to easily start up not only with different resolutions, |
| 27 |
but different colour depths, etc. |
| 28 |
|
| 29 |
-- |
| 30 |
Walter Dnes <waltdnes@××××××××.org> |
| 31 |
I don't run "desktop environments"; I run useful applications |
Archives