1 |
On Wed, 18 Jun 2014 03:31:30 +0000 (UTC) |
2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
3 |
|
4 |
> |
5 |
> While I strongly disagree with your position, I equally strongly respect |
6 |
> you for knowing what you want and sticking to it ... |
7 |
> |
8 |
> As to the disagreement, I guess I'm a single-human-user desktop system |
9 |
> user too. But I recognize the benefits of running various daemons as |
10 |
> their own (non-human) user ... |
11 |
> |
12 |
> So quite in contrast to you, I don't normally even escalate to superuser |
13 |
> even when I'm doing admin tasks ... |
14 |
> |
15 |
|
16 |
It's amazing how people become nearly apoplectic whenever they encounter |
17 |
a case of a user running entirely as root. |
18 |
|
19 |
For me it's no big deal. I've been doing it happily, and without problem, |
20 |
since since 1997 (when I first discovered Linux). It also un-complicates |
21 |
things greatly. |
22 |
|
23 |
For me there is only one user, and that's the guy who owns and operates |
24 |
the machine (root). What could be simpler? |
25 |
|
26 |
But I've learned not to discuss such behavior with others. They will |
27 |
always react in alarmist ways. |
28 |
|
29 |
I won't even mention that, until recently, I used to boot my machine |
30 |
directly into a bash shell, skipping all that SysV (or other) initialization |
31 |
nonsense. Fortunately, the Linux kernel allows one to do just that. |
32 |
It always has and hopefully always will. Booting into bash is very |
33 |
simple. All that is required is to define some environmental variables |
34 |
in the bashrc and one is good to go. All other configuration can |
35 |
be done as needed (or if needed). This is Linux at its very best, IMO. |
36 |
|
37 |
But, as I already indicated, these things cannot be freely discussed. |
38 |
People will react strongly and begin to adduce all sorts of reasons |
39 |
why such behavior is dangerous. So, for me, it is always a case of don't |
40 |
talk and don't listen. |
41 |
|
42 |
Frank Peters |