1 |
On Tue, Apr 25, 2017 at 1:57 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
2 |
> |
3 |
> Mark Knecht posted on Mon, 24 Apr 2017 08:36:43 -0700 as excerpted: |
4 |
> |
5 |
> > I certainly could chroot a specific copy of Gentoo and build on my |
6 |
> > machine. I might also be able to build binary packages on my fast |
7 |
> > machine and then do an emerge -k type install and see if it works. |
8 |
> > |
9 |
> > However, in the end how much do I gain for all that work vs installing |
10 |
> > Kubuntu? |
11 |
> |
12 |
> There's some advantage in learning one distro, learning it well, and |
13 |
> using it on everything. That's what you gain, assuming you're keeping |
14 |
> everything else on gentoo, as you then don't need to keep track of the |
15 |
> many distro differences. |
16 |
> |
17 |
> I learned the difficulty of dealing with multiple distros here with my |
18 |
> current router, still an old Linksys wrt54gl (which as I said I intend to |
19 |
> eventually upgrade to an amd64, so I can build for it at the same time as |
20 |
> the rest of my systems, can configure it using the same methods and |
21 |
> tools, etc.), running openwrt. |
22 |
> |
23 |
> I had a horrible time trying to configure its networking system the way I |
24 |
> wanted to, basically having to read a bunch of its init system scripts |
25 |
> and config to figure out what started what, in what order, what and how |
26 |
> to modify that to my liking, etc, pretty much just to figure out what |
27 |
> config file to edit to change a few settings I wanted to change. |
28 |
> |
29 |
> Even then, I felt like I wasn't getting the most out of it, because in |
30 |
> ordered to do that I'd have had to read and understand pretty much the |
31 |
> entire init system. So mainly I just stuck with the defaults instead of |
32 |
> really getting it to work how I wanted, and I never did really /truly/ |
33 |
> understand it. |
34 |
> |
35 |
> Now that version is now long outdated, but I don't want to update or |
36 |
> indeed, to really change the config as I set it up back then, because in |
37 |
> ordered to do so I'm going to have to dive back into things and figure |
38 |
> all that stuff out again. But I'll only be using it on that one thing; |
39 |
> the info and skills gained won't really transfer to anything else, unless |
40 |
> I decide to standardize on openwrt for everything, including my main |
41 |
> machines! |
42 |
> |
43 |
> By contrast, if it was gentoo, I would have already known the basics and |
44 |
> could have gotten right to the task at hand. And I could have and likely |
45 |
> would have done far more with it, because I really do understand the |
46 |
> openrc setup (this was before systemd went mainstream). |
47 |
> |
48 |
> These days of course most distros are standardized on systemd for init, |
49 |
> so learn it once, use it on all. And that's one of the reasons why I |
50 |
> eventually switched to systemd on gentoo. Except, particularly for that |
51 |
> old thing with its extremely limited system image and RAM sizes, I don't |
52 |
> think systemd would fit. Which is probably a good share of the reason |
53 |
> that last I heard anyway, openwrt wasn't switching to systemd. |
54 |
> |
55 |
> Between my dissatisfaction with not being able to truly master the openwrt |
56 |
> system in the time I was willing to devote to it as a one-off, and my |
57 |
> dissatisfaction with having to build separately for my netbook, even if |
58 |
> it was gentoo, I resolved, as I explained, that next time I upgraded |
59 |
> things, I'd standardize on amd64 (Intel or AMD chips either one), and try |
60 |
> to keep things similar enough that at least for most packages, I could |
61 |
> use the same C(XX)FLAGS and USE flags for everything, and just do binpkg- |
62 |
> only emerges on systems other than my primary, for most packages. That |
63 |
> way both the packages and the setup would be the same across everything, |
64 |
> except where I had actual reason to make it different. And I'd really |
65 |
> understand both that setup, and how to change it to accomplish what I |
66 |
> wanted to do, if necessary. |
67 |
> |
68 |
> |
69 |
> Now I'm into customizing enough that I've never met a desktop that I |
70 |
> liked as it was shipped, and I expect I never will. And at least as I |
71 |
> envision things, even if I'm 80 (30 years from now as I just turned 50 |
72 |
> this year) and in a nursing home, if I'm still of sound enough mind and |
73 |
> body to be running computers, now that I know the level to which I can |
74 |
> efficiently customize gentoo, I really can't see myself being happy |
75 |
> within the limitations of a normal binary distro an longer. It's not as |
76 |
> emphatic a "won't ever happen" as the idea of me switching back to |
77 |
> something proprietary like MS Windows or Apple OSX, but for me it would |
78 |
> certainly feel like going in the same direction, and would thus feel like |
79 |
> defeat. At that point, if I can't any longer do gentoo or at least arch, |
80 |
> I may well simply turn in the keyboard and mouse, and if I do that, I |
81 |
> can't imagine I'd have much else to do to keep me happy, so |
82 |
> realistically, I might well wither and die within a few months, figuring |
83 |
> I have little to nothing remaining to live for. |
84 |
> |
85 |
> |
86 |
> Now I'm /not/ saying the answer has to be the same for you. Far from |
87 |
> it! In fact, the above sounds like you may be tilting the other way, |
88 |
> toward making everything (k)ubuntu, and giving up on gentoo. If you're |
89 |
> satisfied with (k)ubuntu, standardizing on it would equally as |
90 |
> effectively solve the problem of having to deal with two different |
91 |
> distros with wildly different ways of doing things. And that may work |
92 |
> very well for you. |
93 |
> |
94 |
> But it definitely wouldn't work for me. I couldn't be happy on (k)ubuntu, |
95 |
> or fedora, or... I left those limitations behind in 2004 when I left |
96 |
> mandrake for gentoo, much as I left the limitations of proprietaryware |
97 |
> behind in 2001, when I left MS as eXPrivacy crossed a line I couldn't and |
98 |
> wouldn't cross, for the land of Linux freedomware, where I'd not be |
99 |
> /asked/ or /expected/ to cross such a line in the first place. |
100 |
> |
101 |
> Of course doing a split across multiple distros is possible too, but it |
102 |
> does have its negatives, which I'm trying to point out here, and for me |
103 |
> anyway, those negatives were high enough that while I lived with them |
104 |
> while I had to, I resolved that when I got new hardware, I wouldn't have |
105 |
> to any longer. |
106 |
> |
107 |
> But of course perhaps that too you'll find less of a problem than I did. |
108 |
> I just don't like being jack of all distros and master of none, is all, |
109 |
> and would prefer to master one distro, ideally a really flexible one like |
110 |
> gentoo, knowing it well enough to comfortably make it do what I want, and |
111 |
> use it everywhere. |
112 |
> |
113 |
|
114 |
I probably should trim this response but I won't. |
115 |
|
116 |
1) Honestly, I don't disagree at all with your views about the problems |
117 |
of running multiple distros. I wish I wasn't getting pushed that way. |
118 |
|
119 |
2) You seem to have discounted the problem that on this i7 laptop it |
120 |
simply takes too much time to build KDE. I don't think most of the rest of |
121 |
Gentoo is too bad, and maybe I can convince my wife to use something |
122 |
else like XFCE. That would likely require a profile change, which is study |
123 |
time, but the answers are probably in the forums somewhere and would |
124 |
allow me to keep Gentoo on that machine. |
125 |
|
126 |
3) Respectfully, I'm not sure your answer encompasses the problems |
127 |
and frustrations of having to maintain OTHER people's computers. I don't |
128 |
hear you speak of that very often. The problem with KDE is on my wife's |
129 |
computer. When it's building KDE it's unavailable to her. In the past 2 |
130 |
weeks I've had two massive builds that each took about 24 hours. That |
131 |
amounts to about 15% downtime on her machine, which personally I don't |
132 |
care about other than I'm the target of the gripes about 'When's my computer |
133 |
going to work again', etc., and truly, what's she really getting with these |
134 |
updates? Answer: Almost nothing, or actually nothing. |
135 |
|
136 |
4) In the case of my wife's machine using Kubuntu means (to me) that I |
137 |
won't do updates. (Or not many) If it works when it's installed then that's |
138 |
mostly what she gets. Chrome, LibreOffice, VLC. I'm not sure she uses |
139 |
anything other than that anyway. It's just a PC. |
140 |
|
141 |
And, no, I'm not thinking of moving my machine away from Gentoo (for |
142 |
now) but I can honestly say that if I had a major hardware failure I don't |
143 |
think I'd just jump in an put Gentoo on a new machine. Neither MatLab nor |
144 |
NVidia Digits are perfectly happy on Gentoo but are fully supported on |
145 |
Ubuntu. |
146 |
|
147 |
Cheers, |
148 |
Mark |