1 |
On 23/03/2016 12:53, waltdnes@××××××××.org wrote: |
2 |
> On Wed, Mar 23, 2016 at 07:46:09AM +0100, J. Roeleveld wrote |
3 |
>> On Tuesday, March 22, 2016 04:51:52 PM Grant Edwards wrote: |
4 |
>> |
5 |
>>> You're probably right, the magick sysrq feature pretty much obviates |
6 |
>>> the need to boot to console to protect against buggy X11 servers. But, |
7 |
>>> it's fairly recent and Linux-specific. So, the boot-to-console trait |
8 |
>>> (which evolved pre-sysrq -- and even pre-Linux, and has very little |
9 |
>>> "cost") hasn't died out yet... |
10 |
>> |
11 |
>> Yes, but it Xorg isn't that buggy to warrant the inconvience of |
12 |
>> a console boot on a desktop/laptop. Even with proprietary nvidia |
13 |
>> drivers. |
14 |
> |
15 |
> How much inconvenience is it, really? I have a short script ~/bin/x |
16 |
> |
17 |
> #! /bin/bash |
18 |
> startx -- -nosilk -config ${1}xorg.conf & |
19 |
> |
20 |
> At the commandline I simply type "x" and hit the {ENTER} key. Note |
21 |
> the "-config ${1}xorg.conf". The default (i.e. no parameters passed to |
22 |
> script) is to go with the regular xorg.conf. But if I want to go with a |
23 |
> lower resolution (e.g. 640x480) from "640xorg.conf", I would start with |
24 |
> |
25 |
> x 640 |
26 |
> |
27 |
> This allows me to easily start up not only with different resolutions, |
28 |
> but different colour depths, etc. |
29 |
|
30 |
|
31 |
|
32 |
Most users in this day and age would probably reply "why do I need to |
33 |
start with different resolutions and colour depth?" |
34 |
|
35 |
It's been many years since I myself fiddled with any of that, all my |
36 |
displays are now LCD where only one resolution makes any sense - native |
37 |
|
38 |
-- |
39 |
Alan McKinnon |
40 |
alan.mckinnon@×××××.com |