On Sun, Aug 30, 2020 at 05:24:39PM +1000, Mark Trickett wrote:
I did not choose Wayland, nor systemd, but that is now the Debian defaults. There are good reasons behind the changes, or at least I have seen some support that I will concur with on why Wayland over xwindows. However I do not find benefit in systemd,
most of my machines run systemd now. all but one, which just fails to boot at all if i try to boot it with systemd rather than sysvinit. I'm not entirely happy with that but i've given up fighting against it, i just don't have the energy for that. I don't actually mind systemd as an init system, i.e. starting and stopping services - it's pretty good at that. it's all the other stuff (like ntp and dns and cron) that it tries to do that pisses me off, especially since it does such a shitty job of them. I just disable as much of that systemd borg shit as I can and run the required services as extra daemons, like ntpd for ntp and unbound for dns resolution (I still use bind9 on a different IP address for serving my zones) and vixie cron.
the current install (Debian 10.5) is missing a piece of firmware, but I cannot read the message in time during boot, nor find it in the logs. I think it is for the network on the motherboard.
try something like 'journalctl -xe -b0', or 'dmesg | less'. You may be able to find the message you want by searching through that.
From my reading of pages found by a google search, there is a choice by the development team based on (in)security of casual copy and paste. I thought that it was likely a configuration issue, but cannot find. I tried a number of teminals, but not a lot, to find one that appears to be reasonable. I still need to do more research, when life leaves the time from the real world.
that would be kind of fucked up if they've disabled copy-paste into terminals or text editors entirely. so fucked up that that i can't believe anyone would do that deliberately...there has to be some way to do it, or some way to re-enable it. off-by-default is merely annoying, but no big deal. off-forever would be inexcusable.
I cannot make sense of a line of perl at this time,
perl's really not that hard. if you have some basic scripting capability (or an ability to understand algorithms and flow control), and some passing familiarity with shell scripts or sed or awk, then perl is easy. it's nowhere near as difficult as some people like to make out. and learning some perl is at least as useful as learning sh and sed and awk put together. just ignore all the dickheads who say bullshit like "perl is write-only" or that it "looks like line-noise". they have no idea what they're talking about - at best, they're just scared of the sight of regexps as operators - beware the wild regexp, cage it in a function call or it'll get you.
but there are some folks I will trust, such as you and Russel Coker. I do not expect you to be perfect, but that you do know more than I, and from what I have seen, not malicious. I do try to comprehend even your examples first, but have to trust that you do know that much more in the subject of concern.
oh. I didn't mean me. you can trust anything i say, i'm perfect and never make a mistake. btw, i have a nice bridge i'd like to sell you cheap. craig -- craig sanders <cas@taz.net.au>