1 |
Peter Humphrey wrote: |
2 |
> On Saturday, 6 June 2020 17:16:23 BST Dale wrote: |
3 |
>> Jack wrote: |
4 |
>>> sys-libs/gpm perhaps? |
5 |
>> That should be the one. I have that installed and I use it on those |
6 |
>> rare occasions when the GUI doesn't come up and I need to edit a config |
7 |
>> file by pasting from a error to a file. It comes in handy since typing |
8 |
>> it in manually could result in a typo etc. |
9 |
>> |
10 |
>> I keep mine in the default runlevel. However, if a person finds |
11 |
>> themselves in the boot runlevel, just start the gpm service. I've never |
12 |
>> seen it depend on anything else so it should start with no problem even |
13 |
>> in a otherwise broken system. It should start even if in single user mode. |
14 |
> I have a no-x run-level here, as well as a nonetwork. GPM is in those but not |
15 |
> in default, because GPM used to conflict with display managers in their use of |
16 |
> the mouse. No doubt that was fixed long ago, but old habits die hard. |
17 |
> |
18 |
|
19 |
|
20 |
I've never ran into that here. I put it in default because the howto |
21 |
recommended it. It shouldn't block anything else from starting but some |
22 |
recommend only putting certain things in the lower runlevels. If one |
23 |
wanted, test it in default. If it works fine, move it to the boot |
24 |
runlevel. That way it is available almost anytime the GUI fails. |
25 |
|
26 |
It does come in handy tho. It's saved me some typing on several |
27 |
occasions. While I could live without it, I'd rather have it. lol |
28 |
|
29 |
Dale |
30 |
|
31 |
:-) :-) |