On Wednesday 03 April 2019 09:56:09 Dr. Nikolaus Klepp
wrote:
Anno domini 2019 Wed, 3 Apr 08:48:05 -0400
Gene Heskett scripsit:
On Wednesday 03 April 2019 03:09:11 Dr. Nikolaus
Klepp wrote:
Anno domini 2019 Tue, 2 Apr 14:11:04 -0400
Gene Heskett scripsit:
> The install didn't switch it, and gnome won't show me the tools.
Yes, the gnomes won't let you go :-)
I think the installers only other choice is xfce, which I'll do this
time. gnomes paranoia wears thin, very quickly. Even what they call
a Konsole has been castrated. Thats unforgivable. I built this
machine from scratch about a decade back, and I won't stand for
their paranoia that just gets in the way of doing what I do with it.
:(
It's not paranoia, it's "making it easy". Guess, somebody is paying
someone a lot of money for doing so.
The hell its not being paranoid, Nik. Every time I get something working
well, some paranoid sob plugs that hole in the next version as a
security risk. Dammit, its my local network, all behind a dd-wrt router.
In 15 years no one has come in from the outside tha I didn't invite and
gave them the login credentials to do it with, no exceptions. So let me
do as I please on my own local net.
I'll give you the ssh -Y remote cli login as a prime example. It wasn't
user sensitive 10 years ago so a login Just Worked even if you've become
root since logging in. Now we get "can't open display :10" errors unless
you are first user all thru the systems, which I am not, there is no way
on a raspian pi install to be other than pi as the first user #1000.
BTDT spent weeks trying to work around that, finally gave up and just
use ssh -Y pi@picnc.
So if I want to run synaptic on the pi, I either have to goto its
keyboard, a back and neck killing standup job, or more recently I've
found gksudo works. But login as pi, and simply "sudo synaptic" gets the
display opening error. And even that doesn't work when I'm logged into a
rock64 running stretch. Its MY local network, get the hell out of my way
and let me see if I can actually get what s/b a pi killer, to do
anything but browse the internet. I've built realtime kernels on that
rock64 4 or 5 times now, but the instant I sudo -i to try to figure out
how to install one of those realtime kernels, I'm blocked from doing
almost anything but an ls -l. Its enough to make one clear out the stray
cats in the neighborhood.
The point is, I build or buy this stuff for ME to use, whats wrong with
that?
And despite going into this stretch netinstall with a well formatted
drive ready for the install, the installer would NOT proceed past the
partitioning AND formatting stage, so I was forced to do it again,
losing the partition labels in the process.
Except I just ran blkid, and my labels survived!!!!!!! 'splain that one,
but I like it! But mount -l can't find them... I had to use
the /dev/sdb1 and sdb3 designators to mount them. Me, goes off
scratching my thinning hair over that. Anyway, I've started copying
stuff over, iuncludng the /opt directory. That oughtto be fun & games
letting synaptic update all of the /opt/trinity directory to 64 bit
stuff. :)
Thanks Nik, for reading my rant.
Sorr, I missed a part of the original
conversation. Which distribution
are you going to install?
Nik
Stretch, amd64 version. Just did but have not rebooted to it yet,
thought I'd check the mail first.
Ok ... thing one: don't use "sudo", use "su". "sudo" is
like a choir of castrates: useless by default, unless you invest hords of time to set up
things correctly and solve a problem that does not exist in the first place.
Second thing, IMO Debian bites you. All that workarounds to get systemd+gnome kindof
working kill your "user experience". Note: if it works, you are fine, a bit slow
when booting but you get shiny surface ... at least till it breaks, then the fun starts ..
and break it will ..
(I already hear the bonfires roaring ..)
Nik
> > > Help!
> > >
> > > Cheers, Gene Heskett
>
> Cheers, Gene Heskett
Cheers, Gene Heskett
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...