Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[Reco]

Hi.

On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 03:19:44 pm Reco wrote:
> 
> > On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> > > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > >
> > > >  > > > "you", below>
> > > >
> > > > > You are determined to exterminate any and all users of a hosts
> > > > > file, staticly defined network. Its ideal for small home
> > > > > networks.
> > > >
> > > > Hmm, that's interesting -- is there an analog to or replacement
> > > > for the hosts file on ipv6?
> > >
> > > According to the default comments in that file, yes. But easy to
> > > read and understand docs on how to actually do it are somewhat
> > > hidden on the machine or on the net.
> >
> > hosts(5). You'll probably need a text editor too.
> 
> Thats fine, shows the loop local stuff, but how does one determine the 
> ipv6 address for picnc.coyote.den for instance.

In another news, it also does not show how to 'determine' IPv4 address
of the host. Yet you manage to do it somehow.

Reco

Re: Debian Stretch, no password prompt for luks-encrypted home partition during boot

[Sergey Belyashov]

My problem is about than year old or more. With default options (without
plymouth) only information about root partition mount or fsck. Later it
replaced by partition waiting "progress" (moving red asterisks). I have try
to wait about a minute and try to enter luks password, but no any changes.
I think, problem is in complex setup luks on mdraid.

Best regards,
Sergey Belyashov

вт, 28 мая 2019 г., 6:26 Ross Boylan :

> For at least the last couple of weeks I've had the screen go
> completely blank during bootup, after displaying initial messages (I
> changed from "quiet" to "debug" for kernel startup).  This is with a
> luks encrypted root.  I saw it under jessie and buster.  I blamed
> failing hardware (I can't get into the BIOS on boot because the screen
> goes black), though I noticed the same behavior in a VM.
>
> I've discovered that if I type my pass-phrase (waiting long enough
> that I think things have settled down), the system boots.
>
> So, you might try typing your luks passphrase and see if it helps.
>
> And maybe something has changed in the tools or kernel that's causing
> the misbehavior, although jessie hasn't been changing much recently.
>
> Ross
>

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[tomas]

On Mon, May 27, 2019 at 05:06:24PM -0400, Gene Heskett wrote:

[...]

> Thats fine, shows the loop local stuff, but how does one determine the 
> ipv6 address for picnc.coyote.den for instance. I think it somehow 
> related to picnc's mac address, but thats just a WAG.

There's not THE ip address. A host can have (and actually typically
has, under IPv6) several addresses.

That said, what you're talking about is probably the link local address [1],
which under IPv6 is derived from the MAC address, to have some guarantee
of uniqueness.

Since under IPv6 a host can announce its address and the routers can
propagate this, the schema Just Works (TM) without central instances
to dole out addresses à la DHCP.

Cheers

[1] https://en.wikipedia.org/wiki/Link-local_address

-- tomás


signature.asc
Description: Digital signature

Re: Insidious systemd

[Felmon Davis]

On Mon, 27 May 2019, bw wrote:


In-Reply-To: <131c2112-376a-5c46-0d00-7f643168e...@cloud85.net>

Here's further argument that computer programs are not capable of being
insidious.  Using the word this way is IMO incorrect, but then most of the
world is stuck in misuse of language.


diseases can be insidious. drugs can be insidious. anything that 
sneaks up on you posing a threat is 'insidious'.


including computer programs - think viruses.


Let's go the whole nine yards, and agree to toe the line when it come to
trying to right this ship, or we may all fall off the wagon?


nice mixed metaphors! "nine yards"/"toe the line"; "right this 
ship"/"fall off the wagon". love it!


but language is fluid. but few drown. well, maybe sometimes.

I am not adept at systemd; I seem to have remnants of it on my main 
laptop which is sysvinit. need to read up more before I purge. but I 
am not adverse to living with systemd either. rock the boat or toe the 
line - not sure.


f.



https://duckduckgo.com/html/?q=anthropomorphism
https://literarydevices.net/hyperbole/




--
Felmon Davis

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Joe Pfeiffer]

Gene Heskett  writes:

> On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:
>
>> Quoting Gene Heskett (2019-05-27 19:42:46)
>>
>> > On Monday 27 May 2019 03:46:00 am Curt wrote:
>> > > On 2019-05-27,   wrote:
>> > > > If Network Manager is giving you grief, please go bark up /that/
>> > > > tree (I can't say much about N-M, because I banned it from my
>> > > > boxes about ten years ago: I was at a customer's, in his LAN via
>> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
>> > > > window and said "oh, let's go online over there" and obliterated
>> > > > my network setting in favor of some seedy captive portal. That
>> > > > was when I decided that N-M and me, we aren't made for each
>> > > > other).
>> > >
>> > > This is a grave bug. I suppose we can assume from your description
>> > > that the seedier the wifi portal, the more likely it is to
>> > > spontaneously occur, despite any and all user configuration or
>> > > intervention.
>> >
>> > This would appear to be more common, but as far as filing a bug
>> > report, I logged in to do something in 2015, creating a new account
>> > at the time, so now it refuses to let me in because the username
>> > content rules have been changed and my username is now invalid.  And
>> > because it knows my email address, it won't let me create a new
>> > account. So its the classic chicken v egg. I am locked out, so I
>> > rant on this list.
>>
>> Account? You need no account to report bugs in Debian:
>> https://www.debian.org/Bugs/Reporting
>>
> So that indicates I should have apt install reportbug, so I did. 
> Configured it on 1st run. then became me and ran it again.  It never 
> heard of NetworkManager or Network-Manager.  WTH?

Debian package names are all lower case, and for better or worse the
package management software is case-sensitive.

snowball:532$ reportbug
Please enter the name of the package in which you have found a problem, or type 
'other' to report a more general problem. If you don't know what package the 
bug is in, please contact debian-user@lists.debian.org for
assistance.
> network-manager
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the 
submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Joe Pfeiffer ' as your from address.
Getting status for network-manager...
Checking for newer versions at madison...

Your version (1.14.6-2) of network-manager appears to be out of date.
The following newer release(s) are available in the Debian archive:
  experimental: 1.18.0-1
Please try to verify if the bug you are about to report is already addressed by 
these releases.  Do you still want to file a report [y|N|q|?]? 

(at which point I entered a ^C since I didn't actually want to report a
bug)

Re: Debian Stretch, no password prompt for luks-encrypted home partition during boot

[Ross Boylan]

For at least the last couple of weeks I've had the screen go
completely blank during bootup, after displaying initial messages (I
changed from "quiet" to "debug" for kernel startup).  This is with a
luks encrypted root.  I saw it under jessie and buster.  I blamed
failing hardware (I can't get into the BIOS on boot because the screen
goes black), though I noticed the same behavior in a VM.

I've discovered that if I type my pass-phrase (waiting long enough
that I think things have settled down), the system boots.

So, you might try typing your luks passphrase and see if it helps.

And maybe something has changed in the tools or kernel that's causing
the misbehavior, although jessie hasn't been changing much recently.

Ross

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[mick crane]

On 2019-05-27 22:22, Gene Heskett wrote:


Then what was I looking at 3 hours ago, looked like a login form to me,
wanted my username, my real name and my email address. That popped up
and denied me access when I clicked on add bug in the upper right 
corner

of the screen? It flat refused to let me proceed without a valid login.
Yet you're telling me it should sail right on by just by clicking on 
the

add button?



This might be an issue with your browser.

mick

--
Key ID4BFEBB31

Re: lightweight wifi UI (Was: Insidious systemd)

[arne]

On Mon, 27 May 2019 09:29:46 +0200
Jonas Smedegaard  wrote:

> Quoting Patrick Bartek (2019-05-27 03:49:06)
> > Needing to convert this box from wired ethernet to wireless, I 
> > searched for a suitable network manager and wicd looked good: No 
> > desktop environment dependencies (I use a window manager Openbox
> > and single lxpanel), compatibility with Openbox, etc.  
> 
> [ unneeded systemd details snipped ]
> 
> > After more investigating, I came across wifi-radar whose simulated 
> > install doesn't muck my system.  Any suggestions for something
> > better? I could just go with iwconfig or iw?  No big deal.  I've
> > done it before.  But being lazy, if I can find an app to do the
> > work, so much the better.  
> 
> Here are the options I know of which provides a UI with wifi strength 
> and being more lightweight than network-manager, listed in order of 
> personal preference for install on Buster (some, iwd in particular,
> is notably less mature on Stretch):
> 
> iwd is extremely lightweight console-only tool yet provides
> interactive probing of wifi strength.  It integrates fine with
> network-manager and systemd if a) explicitly telling those systems to
> use it and b) explicitly turned off wpasupplicant.
> 
> connman is in my experience more reliable than wicd but looks ugly.
> 
> wicd felt unreliable in my experience - but possibly I didn't give it 
> enough attention (see above about disabling wpasupplicant).
> 
> iw + wifi-radar if all else fails. :-)
> 
> 
>  - Jonas
> 
> 
> P.S. At first I skipped this excellent question due to it being 
> presented as a rant about systemd.  I dearly recommend to _avoid_
> mixing rants with questions, as you then are more likely to miss
> valuable input.
> 
On a headless system I want connection on preferred system, when not
available to another system.
I want this without GUI

I tried wicd and hate networkmanager.

Any hints on cli is welcome!

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 06:45:42 pm Brian wrote:

> On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:25:21 pm Brian wrote:
> > > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > > On 2019-05-27,   wrote:
> > > > > > If Network Manager is giving you grief, please go bark up
> > > > > > /that/ tree (I can't say much about N-M, because I banned it
> > > > > > from my boxes about ten years ago: I was at a customer's, in
> > > > > > his LAN via an Ethernet, when N-M suddenly saw a WLAN out
> > > > > > there, out the window and said "oh, let's go online over
> > > > > > there" and obliterated my network setting in favor of some
> > > > > > seedy captive portal. That was when I decided that N-M and
> > > > > > me, we aren't made for each other).
> > > > >
> > > > > This is a grave bug. I suppose we can assume from your
> > > > > description that the seedier the wifi portal, the more likely
> > > > > it is to spontaneously occur, despite any and all user
> > > > > configuration or intervention.
> > > >
> > > > This would appear to be more common, but as far as filing a bug
> > > > report, I logged in to do something in 2015, creating a new
> > > > account at the time, so now it refuses to let me in because the
> > > > username content rules have been changed and my username is now
> > > > invalid.  And because it knows my email address, it won't let me
> > > > create a new account. So its the classic chicken v egg. I am
> > > > locked out, so I rant on this list.
> > >
> > > Let's get this totally straight. Whatever you logged into was not
> > > the BTS. No account needs to be set up to report a bug. You can
> > > rant as much as you want, but whatever you did is now unknown and
> > > it is extremely doubtful you can supply details.
> >
> > Then what was I looking at 3 hours ago, looked like a login form to
> > me, wanted my username, my real name and my email address. That
> > popped up and denied me access when I clicked on add bug in the
> > upper right corner of the screen? It flat refused to let me proceed
> > without a valid login. Yet you're telling me it should sail right on
> > by just by clicking on the add button?
>
> You know the pack drill. Give a link to what you were looking at.

The link came from a post to this list, 2 or so days back.  And my 
plastic eyes are fogging up from lack of sleep, so I am not going to try 
to find it yet tonight.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[Dan Purgert]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

rhkra...@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
>> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
> below>
>
>> You are determined to exterminate any and all users of a hosts file,
>> staticly defined network. Its ideal for small home networks.
>
> Hmm, that's interesting -- is there an analog to or replacement for the hosts 
> file on ipv6?

No, the hosts file is also used for v6.


-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzsg8YACgkQjhHd8xJ5
ooE4JggAkZnfi7HCegea7xPF+k2V9OeK4dQhLBbXSfbaCYVzsNgP/rIV6JVAn1GW
12UO7Aw8yYToMe4u/u2HO6muIr++pSLS9/JAXP9oN1XcRMh86PfNM6co6SqxIB3g
J2vryaDMz8YwOXXP22gG4qn1KYRMYY9OES7Qx8iweKaR3MQbPOsjAqOgE1epwyA3
nLndj6B1hFc71bAuvF34Sdm0tYGuEsKeu33g1cQAGnsZ9akkT9XbaYvxm5OESCYd
peU8aPI80QFUBnvcjaDg3wkkROMJQk8Km1EXc/MBOnd9g6X8IplqDRDGFzTa6MOZ
O7BePZWODWOMcyTzcdGO3ci2bKxo6g==
=obcR
-END PGP SIGNATURE-

-- 
|_|O|_| 
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5  4AEE 8E11 DDF3 1279 A281

Re: lightweight wifi UI (Was: Insidious systemd)

[Patrick Bartek]

On Mon, 27 May 2019 13:00:37 -0400 (EDT)
bw  wrote:

> In-Reply-To: <20190527090258.213ecf5a@debian9>
> 
> >From: Patrick Bartek 
> >My post WAS initially a report of anamolous behavior during
> >an install.  I had read of other systemd quirks.  (If no one knows, how
> >can it be fixed?)  The last paragraph asking for network manager
> >recommendations other than wicd was an afterthought.  You are correct:
> >I should have made it two posts.  
> 
> Not so much a report of anomolous behavior by your computer, but an 
> anomolous setup, since you have "converted" stretch in a way that you 
> don't explain.  You also still haven't shown the apt output that made you 
> believe installing wicd tempts systemd to behave insidiuously...

The conversion to sysvinit was the approved method in Debian's own docs:
apt (or apt-get) install sysvinit-core.

On the simulated install of wicd, the only important items were that
systemd-sysv was being INSTALLED and sysvinit-core REMOVED.  That was
good enough for me not to do it. The point is, it shouldn't have
happened at all.

> You say you have read of other systemd quirks.  Like what?  I'd suspect 
> you have been flirting with disaster and trying to figure out if you can 
> totally remove it?  

I haven't removed all of systemd. Except for systemd-sysv which was
removed by the conversion process, all the systemd libraries remain. I
researched its total removal from places like systemdless.org, etc.,
and discovered all the hoops I'd have to jump through to make it work,
deduced potential problems it would cause, and decided to just use
Debian's "approved" method of replacing systemd as init.  And in the
process, recovered 6 to 7 MB of RAM.

As far as quirks, from my own experience when I initially tested
Stretch (as a late RC in 2017 IIRC) by installing in VirtualBox, and
after installing sysvinit, on update/upgrades,  it would try to
reinstall systemd-sysv. I reinstalled Stretch a couple times thinking I
may be at fault, but after about 2 weeks, it accepted the conversion to
sysvinit and never tried to reinstall systemd-sysv under any
circumstances until now.

As far as what I've read, much of it was on this list both with
Jessie and Stretch: reading/executing sysv scripts incorrectly or not
reading them at all, problems booting, applications not running or
crashing, etc. These are my general recollections.  I wrote much of the
problems off due to infamiliarity with systemd, but some of it at
the time I considered to be systemd immaturity.  

> Isn't it possibly insidious of you to not provide any details in your post 
> after creating an inflammatory title for it?

No.  Based on my past experiences and research with systemd, I now
always have do simulated installs with everything just to be sure
nothing untoward happens.  The Subject Title was appropriate.

B

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Brian]

On Mon 27 May 2019 at 17:22:30 -0400, Gene Heskett wrote:

> On Monday 27 May 2019 03:25:21 pm Brian wrote:
> 
> > On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > > On 2019-05-27,   wrote:
> > > > > If Network Manager is giving you grief, please go bark up /that/
> > > > > tree (I can't say much about N-M, because I banned it from my
> > > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > > window and said "oh, let's go online over there" and obliterated
> > > > > my network setting in favor of some seedy captive portal. That
> > > > > was when I decided that N-M and me, we aren't made for each
> > > > > other).
> > > >
> > > > This is a grave bug. I suppose we can assume from your description
> > > > that the seedier the wifi portal, the more likely it is to
> > > > spontaneously occur, despite any and all user configuration or
> > > > intervention.
> > >
> > > This would appear to be more common, but as far as filing a bug
> > > report, I logged in to do something in 2015, creating a new account
> > > at the time, so now it refuses to let me in because the username
> > > content rules have been changed and my username is now invalid.  And
> > > because it knows my email address, it won't let me create a new
> > > account. So its the classic chicken v egg. I am locked out, so I
> > > rant on this list.
> >
> > Let's get this totally straight. Whatever you logged into was not the
> > BTS. No account needs to be set up to report a bug. You can rant as
> > much as you want, but whatever you did is now unknown and it is
> > extremely doubtful you can supply details.
> 
> Then what was I looking at 3 hours ago, looked like a login form to me, 
> wanted my username, my real name and my email address. That popped up 
> and denied me access when I clicked on add bug in the upper right corner 
> of the screen? It flat refused to let me proceed without a valid login.  
> Yet you're telling me it should sail right on by just by clicking on the 
> add button?

You know the pack drill. Give a link to what you were looking at.

-- 
Brian.

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 03:42:52 pm Jonas Smedegaard wrote:

> Quoting Gene Heskett (2019-05-27 19:42:46)
>
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27,   wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about N-M, because I banned it from my
> > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > window and said "oh, let's go online over there" and obliterated
> > > > my network setting in favor of some seedy captive portal. That
> > > > was when I decided that N-M and me, we aren't made for each
> > > > other).
> > >
> > > This is a grave bug. I suppose we can assume from your description
> > > that the seedier the wifi portal, the more likely it is to
> > > spontaneously occur, despite any and all user configuration or
> > > intervention.
> >
> > This would appear to be more common, but as far as filing a bug
> > report, I logged in to do something in 2015, creating a new account
> > at the time, so now it refuses to let me in because the username
> > content rules have been changed and my username is now invalid.  And
> > because it knows my email address, it won't let me create a new
> > account. So its the classic chicken v egg. I am locked out, so I
> > rant on this list.
>
> Account? You need no account to report bugs in Debian:
> https://www.debian.org/Bugs/Reporting
>
So that indicates I should have apt install reportbug, so I did. 
Configured it on 1st run. then became me and ran it again.  It never 
heard of NetworkManager or Network-Manager.  WTH?
>
>  - Jonas


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Insidious systemd

[Patrick Bartek]

On Mon, 27 May 2019 20:25:11 +0200
deloptes  wrote:

> Patrick Bartek wrote:
> 
> >> You could switch to Devuan - it's like a Debian but without this
> >> SystemD crap of 1.2 million code lines.
> >> https://www.phoronix.com/scan.php?page=news_item=Systemd-1.2-Million  
> > 
> > I am aware of Devuan, but at the time I installed Stretch (about a
> > year ago after long term support of Wheezy ceased), Devuan ASCII was not
> > ready. Plus, I was wary of Devuan's support. That opinion has changed
> > since ASCII's release.
> > 
> > Thanks for your input.  
> 
> depending on how systemd free you want to be - I use 
> 
> sysv-rc
> sysvinit-core
> sysvinit-utils
> 
> which automatically makes old init the default init, which is the most
> important part. I don't mind systemd staying around.

I used the "approved" conversion documented on Debian's web site
somewhere: apt (or apt-get) install sysvinit-core.  The other files you
listed above were installed as dependencies, but I knew they were
needed from my research. The install REMOVED systemd-sysv and put
sysvinit in its place, and did all the conversion stuff.  Totally
automatic. All of systemd's libraries remained along with udev and a
couple others I don't recall.  It freed up about 6 or 7 MB of RAM over a
systemd boot.

I did the conversion on a minimal terminal only system after the
install reboot before installing X, Openbox, etc. to build my final
system.

I haven't checked to see if Buster will be the same.

B  

Re: reboot stuff doesn't start

[Gene Heskett]

On Monday 27 May 2019 03:31:42 pm Reco wrote:

> On Mon, May 27, 2019 at 02:00:49PM -0400, Gene Heskett wrote:
> > > > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by
> > > > peer
> > >
> > > ...
> > >
> > > > None of which gives me the faintest clue whats wrong with it.
> > >
> > > It does for me.
> > >
> > > First,
> > >
> > > > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> > > > #!/bin/sh -e
> > >
> > > Any execution error will terminate the script.
> > >
> > >
> > > Second,
> > >
> > > > # mount the sshfs shares. Suggested way didn't work,
> > > > # so changed syntax to this, which does
> > > > su gene -c "sshfs gene@shop:/ /sshnet/shop"
> > >
> > > It fails here, or at any of the later sshfs invocations.
> > > Either your resolver is broken or remote sshd does not function.
> > >
> > > Note - you're doing it wrong by configuring per-user mounts at
> > > systemwide level. They invented systemd user-level services just
> > > for that.
> >
> > humm how about anls -l /sshnet/*
>
> And that's supposed to prove what exactly?
> That sshfs works once you configured your NICs and have the resolver
> working and run all this stuff by hand?
> rc-local.service formally depends on network.target, but that does not
> mean all your interfaces are configured by the time /etc/rc.local is
> actually run.
>
> > > Also,
> > >
> > > > # Now, udev is being a cast iron bitch,
> > >
> > > But overriding it this way will only work until the first 'udevadm
> > > trigger' or USB device hotplug.
> > > They invented 'dialout' group (and use it by default) to avoid
> > > such kludges, consider using it.
> >
> > So I should make heyu a member of group dialout?  It is not now:
> > gene@coyote:~$ grep dialout /etc/group
> > dialout:x:20:gene
>
> Your rc.local contents do not contain any hint on why would you need
> 0666 permission on /dev/ttyUSB0. Sure, you needed it for something.
> Maybe it even solved some problem.
> You do not name your problem so I cannot comment on whenever adding a
> certain custom user to dialout group can solve it or not.

heyu did not like the seriel ports default params, so I asked on the heyu 
list, about 2 years ago, Ed Dipold, a regular on that list suggested I 
try 0666 and chown it to me. Worked flawlessly UNTIL I bought a new 2T 
drive and installed stretch 3 weeks ago.  And has worked only 
intermittently since.

Right now its as if the cm-11a has died, and I note its not running more 
than a degree or so over ambient, not as warm as before. If I get some 
spare time tomorrow I'll open it and check for smoked parts. I hate to 
do that as those things make even old radio shack stuff look like 
Cadillac quality stuff.

FWIW, I have what used to be a 1st phone FCC license, and I am a C.E.T. 
and I know which end of a soldering iron gets hot as I have several, 
also a dual trace 1GHS/a sec scope and all the other tools of the trade. 
I also sat in the CE's chair at the local cbs affiliate from 1984 to 
2002.  The chair never got fully warmed up though, as I did it by myself 
at least half of that time.

I'll shut my horn off now.

> > > And,
> > >
> > > > # Now, need some heyu stuff run
> > > > su gene -c "/usr/local/bin/heyu engine &"
> > > > su gene -c "/usr/local/bin/heyu monitor &"
> > >
> > > this just cries 'put me into systemd unit'.
> > > Abusing shell's background in rc.local is good for all those
> > > enterprisey "i-dont-know-what-im-doing" devopses. Don't be like
> > > them.
> >
> > And the docs on how to do that are where?
>
> Google. [1] may or may not be of help.

It wasn't.

> Any *service file at /lib/systemd/system can serve as a template.
>
> Reco

Buried under a pyramid, no wonder I couldn't find it. Thanks a bunch.

> [1] https://wiki.debian.org/systemd

That too.  Thanks Reco.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 03:25:21 pm Brian wrote:

> On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 03:46:00 am Curt wrote:
> > > On 2019-05-27,   wrote:
> > > > If Network Manager is giving you grief, please go bark up /that/
> > > > tree (I can't say much about N-M, because I banned it from my
> > > > boxes about ten years ago: I was at a customer's, in his LAN via
> > > > an Ethernet, when N-M suddenly saw a WLAN out there, out the
> > > > window and said "oh, let's go online over there" and obliterated
> > > > my network setting in favor of some seedy captive portal. That
> > > > was when I decided that N-M and me, we aren't made for each
> > > > other).
> > >
> > > This is a grave bug. I suppose we can assume from your description
> > > that the seedier the wifi portal, the more likely it is to
> > > spontaneously occur, despite any and all user configuration or
> > > intervention.
> >
> > This would appear to be more common, but as far as filing a bug
> > report, I logged in to do something in 2015, creating a new account
> > at the time, so now it refuses to let me in because the username
> > content rules have been changed and my username is now invalid.  And
> > because it knows my email address, it won't let me create a new
> > account. So its the classic chicken v egg. I am locked out, so I
> > rant on this list.
>
> Let's get this totally straight. Whatever you logged into was not the
> BTS. No account needs to be set up to report a bug. You can rant as
> much as you want, but whatever you did is now unknown and it is
> extremely doubtful you can supply details.

Then what was I looking at 3 hours ago, looked like a login form to me, 
wanted my username, my real name and my email address. That popped up 
and denied me access when I clicked on add bug in the upper right corner 
of the screen? It flat refused to let me proceed without a valid login.  
Yet you're telling me it should sail right on by just by clicking on the 
add button?

One of us is full of it.

I'd much rather believe your ethernet chips MAC is your passwd because 
you've told it to keep you logged in.

But I am all for hammering on this till it does work...

> And, to make it clear - the BTS is open to anyone without setting up
> an account. Please do not downplay the importance of this when it
> comes to user involvement. Chicken and eggs have nothing to do with
> it; your vague, FUDDY stuff does a disservice to yourself and Debian.

It denied me access. So what the heck am I supposed to do next?  I'm all 
ears.

> > So if your are scanning the bugs looking for my submissions, taint
> > gonna happen. I have emailed admin and postmaster to ask that my
> > account be expunged so I can create a new one, but like most such
> > emails its been dumped to /dev/null, or at least ignored. I never
> > got a bounce msg.
>
> What account?
>
> > Those bounces I do get are because my ISP's spam filtering is a hell
> > of a lot better than bendels. I have looked at the message bendel
> > claimed was bounced, and with an exception in the last since wheezy
> > time scale, every one of those bounced messages were spam/phishing.
> > So my isp bounces it, and then I get a msg threatening to unsub me
> > from bendel.
>
> Totally irrelevant.
>
> > We've also had this discussion several times since 2015. Fix it so I
> > can file a bug report, and you will get bug reports.  Till
> > then...
>
> Nothing on the Debian side needs to be fixed. We have tried to fix
> users but some are unfixable. :)


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[Gene Heskett]

On Monday 27 May 2019 03:19:44 pm Reco wrote:

> On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> > On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> > > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > >
> > >  > > "you", below>
> > >
> > > > You are determined to exterminate any and all users of a hosts
> > > > file, staticly defined network. Its ideal for small home
> > > > networks.
> > >
> > > Hmm, that's interesting -- is there an analog to or replacement
> > > for the hosts file on ipv6?
> >
> > According to the default comments in that file, yes. But easy to
> > read and understand docs on how to actually do it are somewhat
> > hidden on the machine or on the net.
>
> hosts(5). You'll probably need a text editor too.
>
> Reco

Thats fine, shows the loop local stuff, but how does one determine the 
ipv6 address for picnc.coyote.den for instance. I think it somehow 
related to picnc's mac address, but thats just a WAG.
 

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Brian]

On Mon 27 May 2019 at 10:19:45 -0700, Jimmy Johnson wrote:

> On 05/27/2019 12:46 AM, Curt wrote:
> > On 2019-05-27,   wrote:
> > > 
> > > 
> > > If Network Manager is giving you grief, please go bark up /that/ tree
> > > (I can't say much about N-M, because I banned it from my boxes about
> > > ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> > > N-M suddenly saw a WLAN out there, out the window and said "oh, let's
> > > go online over there" and obliterated my network setting in favor of
> > > some seedy captive portal. That was when I decided that N-M and me,
> > > we aren't made for each other).
> > > 
> > 
> > This is a grave bug. I suppose we can assume from your description that
> > the seedier the wifi portal, the more likely it is to spontaneously
> > occur, despite any and all user configuration or intervention.
> > 
> > Would it be possible to post the link to your bug report? To your
> > knowledge has the bug been fixed since you reported it a decade ago?  As
> > many users here including myself rely on the N-M app, I'm sure we would
> > all be interested in knowing where we stand.
> 
> Who needs NetworkManager and why?

Curt's query was concise and to the point. You are obviously unable
to respond to it in a manner which advances the discusion. Hence your
pathetic attempt at topic divergence.

Please try to read and respond sympathetically to the posts in -user.

-- 
Brian.

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Jonas Smedegaard]

Quoting Gene Heskett (2019-05-27 19:42:46)
> On Monday 27 May 2019 03:46:00 am Curt wrote:
> 
> > On 2019-05-27,   wrote:
> > > If Network Manager is giving you grief, please go bark up /that/ 
> > > tree (I can't say much about N-M, because I banned it from my 
> > > boxes about ten years ago: I was at a customer's, in his LAN via 
> > > an Ethernet, when N-M suddenly saw a WLAN out there, out the 
> > > window and said "oh, let's go online over there" and obliterated 
> > > my network setting in favor of some seedy captive portal. That was 
> > > when I decided that N-M and me, we aren't made for each other).
> >
> > This is a grave bug. I suppose we can assume from your description 
> > that the seedier the wifi portal, the more likely it is to 
> > spontaneously occur, despite any and all user configuration or 
> > intervention.
> 
> This would appear to be more common, but as far as filing a bug 
> report, I logged in to do something in 2015, creating a new account at 
> the time, so now it refuses to let me in because the username content 
> rules have been changed and my username is now invalid.  And because 
> it knows my email address, it won't let me create a new account. So 
> its the classic chicken v egg. I am locked out, so I rant on this 
> list.

Account? You need no account to report bugs in Debian: 
https://www.debian.org/Bugs/Reporting


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: reboot stuff doesn't start

[Reco]

On Mon, May 27, 2019 at 02:00:49PM -0400, Gene Heskett wrote:
> > > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by peer
> >
> > ...
> >
> > > None of which gives me the faintest clue whats wrong with it.
> >
> > It does for me.
> >
> > First,
> >
> > > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> > > #!/bin/sh -e
> >
> > Any execution error will terminate the script.
> >
> >
> > Second,
> >
> > > # mount the sshfs shares. Suggested way didn't work,
> > > # so changed syntax to this, which does
> > > su gene -c "sshfs gene@shop:/ /sshnet/shop"
> >
> > It fails here, or at any of the later sshfs invocations.
> > Either your resolver is broken or remote sshd does not function.
> >
> > Note - you're doing it wrong by configuring per-user mounts at
> > systemwide level. They invented systemd user-level services just for
> > that.
> humm how about anls -l /sshnet/*

And that's supposed to prove what exactly?
That sshfs works once you configured your NICs and have the resolver
working and run all this stuff by hand?
rc-local.service formally depends on network.target, but that does not
mean all your interfaces are configured by the time /etc/rc.local is
actually run.


> > Also,
> >
> > > # Now, udev is being a cast iron bitch,
> >
> > But overriding it this way will only work until the first 'udevadm
> > trigger' or USB device hotplug.
> > They invented 'dialout' group (and use it by default) to avoid such
> > kludges, consider using it.
> 
> So I should make heyu a member of group dialout?  It is not now:
> gene@coyote:~$ grep dialout /etc/group
> dialout:x:20:gene

Your rc.local contents do not contain any hint on why would you need 0666
permission on /dev/ttyUSB0. Sure, you needed it for something. Maybe it
even solved some problem.
You do not name your problem so I cannot comment on whenever adding a
certain custom user to dialout group can solve it or not.


> > And,
> >
> > > # Now, need some heyu stuff run
> > > su gene -c "/usr/local/bin/heyu engine &"
> > > su gene -c "/usr/local/bin/heyu monitor &"
> >
> > this just cries 'put me into systemd unit'.
> > Abusing shell's background in rc.local is good for all those
> > enterprisey "i-dont-know-what-im-doing" devopses. Don't be like them.
> 
> And the docs on how to do that are where?

Google. [1] may or may not be of help.
Any *service file at /lib/systemd/system can serve as a template.

Reco

[1] https://wiki.debian.org/systemd

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Brian]

On Mon 27 May 2019 at 13:42:46 -0400, Gene Heskett wrote:

> On Monday 27 May 2019 03:46:00 am Curt wrote:
> 
> > On 2019-05-27,   wrote:
> > > If Network Manager is giving you grief, please go bark up /that/
> > > tree (I can't say much about N-M, because I banned it from my boxes
> > > about ten years ago: I was at a customer's, in his LAN via an
> > > Ethernet, when N-M suddenly saw a WLAN out there, out the window and
> > > said "oh, let's go online over there" and obliterated my network
> > > setting in favor of some seedy captive portal. That was when I
> > > decided that N-M and me, we aren't made for each other).
> >
> > This is a grave bug. I suppose we can assume from your description
> > that the seedier the wifi portal, the more likely it is to
> > spontaneously occur, despite any and all user configuration or
> > intervention.
> 
> This would appear to be more common, but as far as filing a bug report, I 
> logged in to do something in 2015, creating a new account at the time, 
> so now it refuses to let me in because the username content rules have 
> been changed and my username is now invalid.  And because it knows my 
> email address, it won't let me create a new account. So its the classic 
> chicken v egg. I am locked out, so I rant on this list.

Let's get this totally straight. Whatever you logged into was not the
BTS. No account needs to be set up to report a bug. You can rant as much
as you want, but whatever you did is now unknown and it is extremely
doubtful you can supply details.

And, to make it clear - the BTS is open to anyone without setting up an
account. Please do not downplay the importance of this when it comes to
user involvement. Chicken and eggs have nothing to do with it; your
vague, FUDDY stuff does a disservice to yourself and Debian.

> So if your are scanning the bugs looking for my submissions, taint gonna 
> happen. I have emailed admin and postmaster to ask that my account be 
> expunged so I can create a new one, but like most such emails its been 
> dumped to /dev/null, or at least ignored. I never got a bounce msg.

What account?
> 
> Those bounces I do get are because my ISP's spam filtering is a hell of a 
> lot better than bendels. I have looked at the message bendel claimed was 
> bounced, and with an exception in the last since wheezy time scale, 
> every one of those bounced messages were spam/phishing. So my isp 
> bounces it, and then I get a msg threatening to unsub me from bendel.

Totally irrelevant.

> We've also had this discussion several times since 2015. Fix it so I can 
> file a bug report, and you will get bug reports.  Till then...

Nothing on the Debian side needs to be fixed. We have tried to fix users
but some are unfixable. :)

-- 
Brian

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[Reco]

On Mon, May 27, 2019 at 02:09:45PM -0400, Gene Heskett wrote:
> On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:
> 
> > On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> >
> >  > "you", below>
> >
> > > You are determined to exterminate any and all users of a hosts file,
> > > staticly defined network. Its ideal for small home networks.
> >
> > Hmm, that's interesting -- is there an analog to or replacement for
> > the hosts file on ipv6?
> >
> According to the default comments in that file, yes. But easy to read and 
> understand docs on how to actually do it are somewhat hidden on the 
> machine or on the net.

hosts(5). You'll probably need a text editor too.

Reco

Re: lightweight wifi UI

[Mart van de Wege]

bw  writes:

> In-Reply-To: <20190527090258.213ecf5a@debian9>
>
>>From: Patrick Bartek 
>>My post WAS initially a report of anamolous behavior during
>>an install.  I had read of other systemd quirks.  (If no one knows, how
>>can it be fixed?)  The last paragraph asking for network manager
>>recommendations other than wicd was an afterthought.  You are correct:
>>I should have made it two posts.
>
> Not so much a report of anomolous behavior by your computer, but an 
> anomolous setup, since you have "converted" stretch in a way that you 
> don't explain.  You also still haven't shown the apt output that made you 
> believe installing wicd tempts systemd to behave insidiuously...
>
Are we sure it's not libsystemd0 that Patrick is objecting against?
Because that is the only systemd related Depends: in wicd's dependency
chain (pulled in via wicd-daemon -> dbus).

Mart

-- 
"We will need a longer wall when the revolution comes."
--- AJS, quoting an uncertain source.

Re: NIC Bonding 802.3ad LACP without switch

[deloptes]

Sven Hartge wrote:

>> also on a network card with 2 NIC's
> 
>> srv-a nic ens2f0  ens2f0 srv-b
>> ens2f1  ens2f1
> 
>> Can I use a switch that only supoort static LAC to speedup my
>> connection? For example tp-link TL-SG108E ? Or must it support LACP?
> 
> For this direct connection you should use "balance-rr" or mode 0.
> This will get you a true 2GBit connection even with only one active
> flow.
> 
> All other modes will only use one connection per flow, limiting you to
> 1GBit.

+1

Re: NIC Bonding 802.3ad LACP without switch

[deloptes]

basti wrote:

> I want to speedup my network connection beween srv-a and srv-b. There is
> only a 1:1 connection.
> I have try to use balance-alb and copy some files from a to b with only
> 112 MB/s with dd and netcat.


In the RHEL Network Guide [1] it says that LACP is supported only with
switch as counterpart. I never tried this on Debian and without a switch,
but there are few other modes and ways to configure. 

LACP is mode 4 you need mode 0 or balancing

[1]
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-using_channel_bonding

Re: Insidious systemd

[deloptes]

Patrick Bartek wrote:

>> You could switch to Devuan - it's like a Debian but without this
>> SystemD crap of 1.2 million code lines.
>> https://www.phoronix.com/scan.php?page=news_item=Systemd-1.2-Million
> 
> I am aware of Devuan, but at the time I installed Stretch (about a
> year ago after long term support of Wheezy ceased), Devuan ASCII was not
> ready. Plus, I was wary of Devuan's support. That opinion has changed
> since ASCII's release.
> 
> Thanks for your input.

depending on how systemd free you want to be - I use 

sysv-rc
sysvinit-core
sysvinit-utils

which automatically makes old init the default init, which is the most
important part. I don't mind systemd staying around.

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[Gene Heskett]

On Monday 27 May 2019 08:58:14 am rhkra...@gmail.com wrote:

> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
>
>  "you", below>
>
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
>
> Hmm, that's interesting -- is there an analog to or replacement for
> the hosts file on ipv6?
>
According to the default comments in that file, yes. But easy to read and 
understand docs on how to actually do it are somewhat hidden on the 
machine or on the net.

> Aside / background: AFAIK, I am not using IPV6 on either my Wheezy or
> Jessie system, but, I haven't really transitioned to the Jessie system
> as my everyday machine -- I don't really "surf the net" there, but
> instead tend to search for specific technically oriented pages related
> to the (development) work I'm trying to do on that Jessie system -- I
> don't notice much advertising -- it's probably because of the pages I
> view.

yup, been known to back out of such sites that "have an ax to sharpen" in 
5 secs or less myself.  Usually its an invitation to subscribe for 
around $80 a seat/year.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: reboot stuff doesn't start

[Gene Heskett]

On Monday 27 May 2019 05:11:29 am Reco wrote:

>   Hi.
>
> On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> > On Sunday 26 May 2019 12:13:38 pm john doe wrote:
> > > On 5/26/2019 5:32 PM, Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > > New stretch install about 2 weeks ago, cleaning up the remains.
> > > > Fresh disk, so no leftovers. But lots of stuff has been copied
> > > > over from the wheezy disk since
> > > >
> > > > I have spamassassin enabled in my rc5.d, and I start heyu engine
> > > > and heyu monitor in my rc.local for several years , but neither
> > > > one is actually being started now.
> > > >
> > > > I can restart spamassassin once logged it, ditto for heyu and
> > > > friends.
> > > >
> > > > Why don't they start when they're supposed to?
> > >
> > > Look at the service 'rc.local'.:
> > >
> > > $ systemctl status/enable rc.local
> >
> > hum:
> > root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
>
> ...
>
> > May 25 12:03:03 coyote rc.local[884]: read: Connection reset by peer
>
> ...
>
> > None of which gives me the faintest clue whats wrong with it.
>
> It does for me.
>
> First,
>
> > root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> > #!/bin/sh -e
>
> Any execution error will terminate the script.
>
>
> Second,
>
> > # mount the sshfs shares. Suggested way didn't work,
> > # so changed syntax to this, which does
> > su gene -c "sshfs gene@shop:/ /sshnet/shop"
>
> It fails here, or at any of the later sshfs invocations.
> Either your resolver is broken or remote sshd does not function.
>
> Note - you're doing it wrong by configuring per-user mounts at
> systemwide level. They invented systemd user-level services just for
> that.
humm how about anls -l /sshnet/*
gene@coyote:~$ ls -l /sshnet/*
/sshnet/GO704:
total 96
drwxr-xr-x 1 root   root4096 Jun  3  2018 bin
drwxr-xr-x 1 root   root4096 Mar 23 17:51 boot
drwxr-xr-x 1 root   root3400 Apr 28 16:22 dev
drwxr-xr-x 1 root   root   12288 May 23 22:29 etc
drwxr-xr-x 1 backup backup  4096 Oct  6  2015 GenesAmandaHelper-0.61
drwxr-xr-x 1 root   root4096 Oct  5  2015 home
lrwxrwxrwx 1 root   root  35 Oct 27  2017 
initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae
drwxr-xr-x 1 root   root4096 Jun 20  2017 lib
drwx-- 1 root   root   16384 Oct 27  2017 lost+found
drwxr-xr-x 1 root   root4096 Oct 27  2018 media
drwxr-xr-x 1 root   root4096 Nov 10  2015 opt
dr-xr-xr-x 1 root   root   0 Mar 23 17:53 proc
drwx-- 1 root   root4096 Sep 25  2017 root
drwxr-xr-x 1 root   root1000 May 27 08:09 run
drwxr-xr-x 1 root   root4096 Jun  3  2018 sbin
drwxr-xr-x 1 gene   gene4096 Oct 27  2017 sshnet
dr-xr-xr-x 1 root   root   0 Mar 23 17:53 sys
drwxrwxrwt 1 root   root4096 May 27 13:17 tmp
drwxr-xr-x 1 root   root4096 Mar 23 17:48 usr
drwxr-xr-x 1 root   root4096 Oct 28  2017 var
lrwxrwxrwx 1 root   root  32 Oct 27  2017 
vmlinuz -> /boot/vmlinuz-3.4-9-rtai-686-pae

/sshnet/lathe:
total 108
drwxr-xr-x 1 root   root  4096 Jun  3  2018 bin
drwxr-xr-x 1 root   root  1024 Feb  5  2017 boot
drwxr-xr-x 1 root   root  3340 Apr 28 10:41 dev
drwxr-xr-x 1 root   root 12288 May 23 22:37 etc
drwxr-xr-x 1 backup disk  4096 May  6  2015 GenesAmandaHelper-0.61
drwxr-xr-x 1 root   root  4096 May  8  2015 home
lrwxrwxrwx 1 root   root35 May  6  2015 
initrd.img -> /boot/initrd.img-3.4-9-rtai-686-pae
drwxr-xr-x 1 root   root  4096 Jun 24  2017 lib
drwx-- 1 root   root 16384 May  6  2015 lost+found
drwxr-xr-x 1 root   root  4096 Jul  3  2014 media
drwxr-xr-x 1 root   root  4096 Apr 19  2014 mnt
drwxr-xr-x 1 root   root 0 Mar  7 16:38 net
drwxr-xr-x 1 root   root  4096 Jul  3  2014 opt
dr-xr-xr-x 1 root   root 0 Mar  7 16:38 proc
drwx-- 1 root   root  4096 May  7  2015 root
drwxr-xr-x 1 root   root   920 May 23 22:36 run
drwxr-xr-x 1 root   root  4096 Jun  3  2018 sbin
drwxr-xr-x 1 root   root  4096 Jun 10  2012 selinux
drwxr-xr-x 1 root   root  4096 Jul  3  2014 srv
drwxr-xr-x 1 gene   gene  4096 Sep 24  2015 sshnet
dr-xr-xr-x 1 root   root 0 Mar  7 16:38 sys
drwxrwxrwt 1 root   root  4096 May 27 13:34 tmp
drwxr-xr-x 1 root   root  4096 May  6  2015 usr
drwxr-xr-x 1 root   root  4096 May  6  2015 var
lrwxrwxrwx 1 root   root31 May  6  2015 vmlinuz -> 
boot/vmlinuz-3.4-9-rtai-686-pae

/sshnet/picnc:
total 100
drwxr-xr-x 1 root   root4096 Apr 26 21:09 bin
drwxr-xr-x 1 root   root3072 Dec 31  1969 boot
-rw-r--r-- 1 root   root   4 Nov 15  2016 debian-binary
drwxr-xr-x 1 root   root3640 May 17 16:57 dev
drwxr-xr-x 1 root   root   12288 May 17 16:52 etc
drwxr-xr-x 1 backup backup  4096 Jun 17  2017 GenesAmandaHelper-0.61
drwxr-xr-x 1 root   root4096 Apr 10  2017 home
drwxr-xr-x 1 root   root4096 Sep  4  2017 lib
drwx-- 1 root   root   16384 Apr 10  2017 lost+found
drwxr-xr-x 1 root   root4096 Aug  1  2018 media
drwxr-xr-x 1 root   root4096 Apr 10  2017 mnt
drwxr-xr-x 1 root   root4096 Jun 

Re: reboot stuff doesn't start

[Gene Heskett]

On Monday 27 May 2019 04:50:22 am Curt wrote:

> On 2019-05-26, Gene Heskett  wrote:
> > hum:
> > root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
> > ● rc-local.service - /etc/rc.local Compatibility

And un-noticed 100 lines later in that same log is a report that the 
compatibility had failed.

> >Loaded: loaded (/lib/systemd/system/rc-local.service; static;
> > vendor preset: enabled)
>
> I found this (not sure if it's entirely applicable, or even entirely
> wise, but there you go):
>
> https://www.linuxbabe.com/linux-server/how-to-enable-etcrc-local-with-
>systemd

Here is the full trace of that command above:
root@coyote:~$ systemctl status rc.local
● rc-local.service - /etc/rc.local Compatibility
   Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor 
preset: enabled)
  Drop-In: /lib/systemd/system/rc-local.service.d
   └─debian.conf
   Active: failed (Result: exit-code) since Mon 2019-05-27 09:04:59 EDT; 
4h 42min ago

May 27 09:04:58 coyote su[1341]: + ??? root:gene
May 27 09:04:58 coyote su[1341]: pam_unix(su:session): session opened for 
user gene by (uid=0)
May 27 09:04:58 coyote su[1357]: Successful su for gene by root
May 27 09:04:58 coyote su[1357]: + ??? root:gene
May 27 09:04:58 coyote su[1357]: pam_unix(su:session): session opened for 
user gene by (uid=0)
May 27 09:04:59 coyote rc.local[921]: read: Connection reset by peer
May 27 09:04:59 coyote systemd[1]: rc-local.service: Control process 
exited, code=exited status=1
May 27 09:04:59 coyote systemd[1]: Failed to start /etc/rc.local 
Compatibility.
May 27 09:04:59 coyote systemd[1]: rc-local.service: Unit entered failed 
state.
May 27 09:04:59 coyote systemd[1]: rc-local.service: Failed with 
result 'exit-code'

Make of it what you will.

Thanks.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 03:46:00 am Curt wrote:

> On 2019-05-27,   wrote:
> > If Network Manager is giving you grief, please go bark up /that/
> > tree (I can't say much about N-M, because I banned it from my boxes
> > about ten years ago: I was at a customer's, in his LAN via an
> > Ethernet, when N-M suddenly saw a WLAN out there, out the window and
> > said "oh, let's go online over there" and obliterated my network
> > setting in favor of some seedy captive portal. That was when I
> > decided that N-M and me, we aren't made for each other).
>
> This is a grave bug. I suppose we can assume from your description
> that the seedier the wifi portal, the more likely it is to
> spontaneously occur, despite any and all user configuration or
> intervention.

This would appear to be more common, but as far as filing a bug report, I 
logged in to do something in 2015, creating a new account at the time, 
so now it refuses to let me in because the username content rules have 
been changed and my username is now invalid.  And because it knows my 
email address, it won't let me create a new account. So its the classic 
chicken v egg. I am locked out, so I rant on this list.

So if your are scanning the bugs looking for my submissions, taint gonna 
happen. I have emailed admin and postmaster to ask that my account be 
expunged so I can create a new one, but like most such emails its been 
dumped to /dev/null, or at least ignored. I never got a bounce msg.  

Those bounces I do get are because my ISP's spam filtering is a hell of a 
lot better than bendels. I have looked at the message bendel claimed was 
bounced, and with an exception in the last since wheezy time scale, 
every one of those bounced messages were spam/phishing. So my isp 
bounces it, and then I get a msg threatening to unsub me from bendel.

We've also had this discussion several times since 2015. Fix it so I can 
file a bug report, and you will get bug reports.  Till then...
>
> Would it be possible to post the link to your bug report? To your
> knowledge has the bug been fixed since you reported it a decade ago? 
> As many users here including myself rely on the N-M app, I'm sure we
> would all be interested in knowing where we stand.


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Release netboot installer fails

[Gregory Seidman]

On Mon, May 27, 2019 at 11:32:46AM +0100, Brian wrote:
> On Sun 26 May 2019 at 11:18:52 -0400, Gregory Seidman wrote:
> 
> > This is mostly to document what I encountered, because I haven't had time
> > to put it in a bug. (I don't know if I will get around to it, honestly. If
> > someone else wants to put it in they should feel free and post a response
> > to the list with the bug link.)
[...]
> > I would hope this is fixable.
> 
> Bug #749991?

Cripes, that's a grave bug that's five years old. And yes, that's the
issue. For convenience:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749991

> -- 
> Brian.
--Greg

Re: Problems {PEBKAC?} running mmdebstrap for 1st time

[Richard Owlett]

On 05/27/2019 12:08 PM, Cindy Sue Causey wrote:

On 5/27/19, Richard Owlett  wrote:


Further re-reading of man pages suggests that my command should begin:

mmdebstrap --variant=required --aptopt="APT::Get::AllowUnauthenticated
true" ...


I hesitate to try that on this machine.



Is there any way to attempt a "--dry-run", or is that not offered? Or
it's possibly not even useful in this particular case usage?


The man page for mmdebstrap does mention one.
As its original motivation was to replace a sub-set of multistrap uses, 
I wouldn't be surprised if it exists.


I've just done a Debian install intended for doing dangerous 
experiments. But its lunch time.




I've encountered "--dry-run" as a nice option a couple times lately.
That's why it came to mind just now. Would be nice to see it here,
too.

DISCLAIMER: Where available, "--dry-run" is still not perfect. I've
seen it gloss over, i.e. not mention/reference at all, some forgotten
action that I had specifically needed to test-drive first before
attempting for reals.


That's essentially why I specified a tarball as output. Limits 
collateral damage while I find out what mmdebstrap does or can do.





Cindy :)

Re: Problems {PEBKAC?} running mmdebstrap for 1st time

[Cindy Sue Causey]

On 5/27/19, Cindy Sue Causey  wrote:
> On 5/27/19, Richard Owlett  wrote:
>>
>> Further re-reading of man pages suggests that my command should begin:
>>> mmdebstrap --variant=required --aptopt="APT::Get::AllowUnauthenticated
>>> true" ...
>>
>> I hesitate to try that on this machine.
>
>
> Is there any way to attempt a "--dry-run", or is that not offered? Or
> it's possibly not even useful in this particular case usage?


Sorry about that yet again. I thought it was being funky when it took
too long after clicking "Send". It occurred on the newest Opera-Stable
installed 24 hours ago.

When this occurs, as I've seen it happen for others, too, I THINK it's
possibly about a browser's refresh rate or something similar ("redraw,
whatever that is"?) *hiccup* causing a malfunction in tandem with less
than optimal networking connections.

Websites used to "yell at me", a "whoa, cowboy" kind of deal, where
the'd sometimes even threaten to lock me out a couple years ago. Their
complaint was about the browser being too eager, making too many
refresh requests in too short a time. Opera had something called a
"redraw" [rate] that seemed to be the cause. Back then, it could be
changed slightly but NOT STOPPED, unfortunately. :)

Opera finally evolved to where that hasn't been such an issue. Every
once in a while, though, instances like this newest double-sent email
give a quick peek back at those not so long ago "it's not you, it's
not me, it's THEM" days.

Cindy :)
-- 
* runs with birdseed *

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Jimmy Johnson]

On 05/27/2019 01:51 AM, Jonas Smedegaard wrote:

Quoting Curt (2019-05-27 09:46:00)

On 2019-05-27,   wrote:

If Network Manager is giving you grief, please go bark up /that/
tree (I can't say much about N-M, because I banned it from my boxes
about ten years ago: I was at a customer's, in his LAN via an
Ethernet, when N-M suddenly saw a WLAN out there, out the window and
said "oh, let's go online over there" and obliterated my network
setting in favor of some seedy captive portal. That was when I
decided that N-M and me, we aren't made for each other).



This is a grave bug. I suppose we can assume from your description
that the seedier the wifi portal, the more likely it is to
spontaneously occur, despite any and all user configuration or
intervention.

Would it be possible to post the link to your bug report? To your
knowledge has the bug been fixed since you reported it a decade ago?
As many users here including myself rely on the N-M app, I'm sure we
would all be interested in knowing where we stand.


I fully agree, this is a quite scary and severe bug in network-manager
that I want to inspect closer as Debian Developer.

Please do share information about where it was reported to I can follow
up on it.  I sincerely hope that it has not gone unfixed through these
many years!!!



Who needs it and what for?

Why is NetworkManager installed?
--
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

Re: Re: network installer will not boot

[Blair, Charles E III]

   Thanks for your continuing help.

   I would like to to try "Legacy," but am
not sure how.

   I press F2 at the beginning.  This takes
me to tabs including "Main", "Devices", "Boot".

Under "Devices," there is a box under the
heading "USB Configuration" for "Legacy",
which I have checked with a mouse-click.
Below that are choices involving charging,
which do not seem relevant.

The "Boot" tab is more problematic.  I am
shown panels headed "UEFI Boot Priority" and
"Legacy Boot Priority," each headed by a box
to check.  UEFI is checked, Legacy is not.
I am unable to uncheck UEFI or to check Legacy,
either with a mouse or by moving around
orange frames using the arrow keys. 

-- 
My e-mail is unreliable.
Please try again if no reply in several days.

gpg: F7C9 B577 1E5D C732 63F1  A9D2 A399 D202 50E8 50D1

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Jimmy Johnson]

On 05/27/2019 12:46 AM, Curt wrote:

On 2019-05-27,   wrote:



If Network Manager is giving you grief, please go bark up /that/ tree
(I can't say much about N-M, because I banned it from my boxes about
ten years ago: I was at a customer's, in his LAN via an Ethernet, when
N-M suddenly saw a WLAN out there, out the window and said "oh, let's
go online over there" and obliterated my network setting in favor of
some seedy captive portal. That was when I decided that N-M and me,
we aren't made for each other).



This is a grave bug. I suppose we can assume from your description that
the seedier the wifi portal, the more likely it is to spontaneously
occur, despite any and all user configuration or intervention.

Would it be possible to post the link to your bug report? To your
knowledge has the bug been fixed since you reported it a decade ago?  As
many users here including myself rely on the N-M app, I'm sure we would
all be interested in knowing where we stand.



Who needs NetworkManager and why?

Thanks,
--
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 02:56:07 am to...@tuxteam.de wrote:

> On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
>
> [...]
>
> > I don't think so. ipv6 I'm sure is nice where its available.  Where
> > it is not available, its a pain in the ass because even if you set
> > it up as a static ipv4, N-M will tear it down in 5 minutes or less.
> > And N-M is a dependency because most have a dhcpd running, probably
> > in the router by default.
> >
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
>
> [...]
>
> I've been following this monster thread with one eye (sorry, not
> enough bandwidth at the moment) and I think, Gene, you're barking up
> the wrong tree.
>
> IPv6 can coexist nicely with IPv4 (this is by design). My work laptop
> (which is my only work box) has both stacks up and running. Most
> places I'm at don't even know IPv6 exist. My ISP at home likewise. But
> my home router does, so I can magically "ping6" the more intelligent
> hosts at home, without having had to configure anything.
>
> If Network Manager is giving you grief, please go bark up /that/ tree
> (I can't say much about N-M, because I banned it from my boxes about
> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> N-M suddenly saw a WLAN out there, out the window and said "oh, let's
> go online over there" and obliterated my network setting in favor of
> some seedy captive portal. That was when I decided that N-M and me,
> we aren't made for each other).
>
> Cheers
> -- t
I agree totally Tomas. but its tied up in dependencies so bad it nukes 
the whole system if you try to remove it. Here I am tempted to fire up a 
root session of mc, and wear out the F8 key because I also have 
something going on that kills hid-common, so I have no input system. 
That has limited my uptime to under a week, sometimes under a day.

Whether brute-force killing of N-M will fix the input lockups remains to 
be tested by this method.  It was locked sometime in the night when I 
woke up to feed the missus about 7ish. And both the lack of a 
spamassasin start, bad expired certificate, ditto for clamscand I have 
yet to see the complete lines before the lockup, the log is being 
spammed at about 300 lines a minute, so I will next time set the konsole 
history to unlimited, and tail -fn10 /var/log/syslog.  Maybe that 
will get me back to before the reboot.  Humm, less got me back far 
enough, but what I see is crazy:

May 27 02:53:00 coyote spamd[2309]: prefork: child states: II
May 27 02:54:14 coyote usbhid-ups[775]: libusb_get_report: could not 
claim interface 0: Device or resource busy
May 27 02:56:01 coyote CRON[6375]: (gene) CMD (/home/gene/bin/remindX)
May 27 09:04:37 coyote systemd[1]: Started udev Coldplug all Devices.
May 27 09:04:37 coyote systemd[1]: Starting udev Wait for Complete Device 
Initialization...
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted module 'lp'
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted module 'ppdev'
May 27 09:04:37 coyote systemd[1]: Started Create Static Device Nodes 
in /dev.
May 27 09:04:37 coyote systemd[1]: Starting udev Kernel Device Manager...
May 27 09:04:37 coyote systemd[1]: Started Set the console keyboard 
layout.
May 27 09:04:37 coyote systemd[1]: Reached target Local File Systems 
(Pre).
May 27 09:04:37 coyote systemd-modules-load[307]: Inserted 
module 'parport_pc'
May 27 09:04:37 coyote systemd[1]: Started Load Kernel Modules.
May 27 09:04:37 coyote kernel: [0.00] Linux version 
4.9.0-9-rt-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT RT Debian 
4.9.168-1+deb9u2 (2019-05-13)
May 27 09:04:37 coyote systemd[1]: Starting Apply Kernel Variables...
May 27 09:04:37 coyote kernel: [0.00] Command line: 
BOOT_IMAGE=/vmlinuz-4.9.0-9-rt-amd64 root=UUID=0e698024-1cf3

And there's at least another 500-1000 lines with the clock frozen at 
09:04:37.  Crazy...

The beginning of the crash is the 2nd line of this, usb-common has died.  
Thats all I know for sure right now. I had to use the front panel reset 
button to reboot it, something I've had to do quite a few times since a 
new stretch install 3 weeks ago now.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Jimmy Johnson]

On 05/26/2019 11:03 PM, Andy Smith wrote:


There doesn't seem to be any point in interacting further.



Andy



Andy that's the most helpful thing you've said, you are trolling Gene a 
longtime Debian Linux User who is having problems adjusting to not 
having Debian Linux any longer, like so many others who are longtime 
Debian Users, so please don't troll.


Thanks,
--
Jimmy Johnson

14.2 - KDE - AMD A8-7600 - EXT4 at sda9 - Registered Linux User #380263

Re: Problems {PEBKAC?} running mmdebstrap for 1st time

[Cindy Sue Causey]

On 5/27/19, Richard Owlett  wrote:
>
> Further re-reading of man pages suggests that my command should begin:
>> mmdebstrap --variant=required --aptopt="APT::Get::AllowUnauthenticated
>> true" ...
>
> I hesitate to try that on this machine.


Is there any way to attempt a "--dry-run", or is that not offered? Or
it's possibly not even useful in this particular case usage?

I've encountered "--dry-run" as a nice option a couple times lately.
That's why it came to mind just now. Would be nice to see it here,
too.

DISCLAIMER: Where available, "--dry-run" is still not perfect. I've
seen it gloss over, i.e. not mention/reference at all, some forgotten
action that I had specifically needed to test-drive first before
attempting for reals.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with birdseed *

Re: Problems {PEBKAC?} running mmdebstrap for 1st time

[Richard Owlett]

On 05/27/2019 10:46 AM, Jonas Smedegaard wrote:

Quoting Richard Owlett (2019-05-27 17:23:17)

On 05/26/2019 10:05 AM, Richard Owlett wrote:

On 05/26/2019 09:52 AM, Jonas Smedegaard wrote:

Quoting Richard Owlett (2019-05-26 16:34:17)

I was investigating using multistrap, but it has been orphaned.
mmdebstrap apparently has the desired features of multistrap but
is available only in Buster.

I do not have the available bandwidth to install Buster. In
Stretch perl is 5.24.1-3+deb9u5 but is 5.28.1-6 in Buster.

Is it feasible to run under Stretch? How?


mmdebstrap has no tight dependencies so you should be able to
simply install the Buster package in Stretch and try use it.




My command was:
mmdebstrap --variant=required stretch test1.tar
file:///media/richard/dvds/dvd1.iso

The error received was:

sh: 1: fakechroot: not found
sh: 1: proot: not found
E: unable to pick chroot mode automatically


That was resolved by installing "fakechroot". I had read the man page
as implying the use of a tar file did not require it.

That left me with the problem of telling the instance of apt being run
internally by mmdebstrap that dvd1.iso is trusted. I unsuccessfully
tried using the distribution DVD itself.

What is the proper syntax to use dvd1.iso {preferred} or DVD in drive
{last resort} as my repository?


mmdebstrap (and multistrap which you originally mentioned) are unrelated
to dealing with ISO files.


You misunderstood.
debootstrap, multistrap, mmdebstrap and any future cousins require a 
repository of deb files.


apt and cousins can install from an unsigned repository by EXPLICITLY 
identifying it as "trusted". {see man page for sources.list}


By inference I only need the proper syntax to do same with mmdebstrap.

Further re-reading of man pages suggests that my command should begin:

mmdebstrap --variant=required --aptopt="APT::Get::AllowUnauthenticated true" ...


I hesitate to try that on this machine.






What do you expect to achieve by "investigating using multistrap" and
mmdebstrap?

  - Jonas

Re: lightweight wifi UI (Was: Insidious systemd)

[Patrick Bartek]

On Mon, 27 May 2019 09:29:46 +0200
Jonas Smedegaard  wrote:

> Quoting Patrick Bartek (2019-05-27 03:49:06)
> > Needing to convert this box from wired ethernet to wireless, I 
> > searched for a suitable network manager and wicd looked good: No 
> > desktop environment dependencies (I use a window manager Openbox and 
> > single lxpanel), compatibility with Openbox, etc.  
> 
> [ unneeded systemd details snipped ]
> 
> > After more investigating, I came across wifi-radar whose simulated 
> > install doesn't muck my system.  Any suggestions for something better?  
> > I could just go with iwconfig or iw?  No big deal.  I've done it 
> > before.  But being lazy, if I can find an app to do the work, so much 
> > the better.  
> 
> Here are the options I know of which provides a UI with wifi strength 
> and being more lightweight than network-manager, listed in order of 
> personal preference for install on Buster (some, iwd in particular, is 
> notably less mature on Stretch):
> 
> iwd is extremely lightweight console-only tool yet provides interactive 
> probing of wifi strength.  It integrates fine with network-manager and 
> systemd if a) explicitly telling those systems to use it and b) 
> explicitly turned off wpasupplicant.
> 
> connman is in my experience more reliable than wicd but looks ugly.
> 
> wicd felt unreliable in my experience - but possibly I didn't give it 
> enough attention (see above about disabling wpasupplicant).
> 
> iw + wifi-radar if all else fails. :-)
> 
> 
>  - Jonas
> 
> 
> P.S. At first I skipped this excellent question due to it being 
> presented as a rant about systemd.  I dearly recommend to _avoid_ mixing 
> rants with questions, as you then are more likely to miss valuable 
> input.

My post WAS initially a report of anamolous behavior during
an install.  I had read of other systemd quirks.  (If no one knows, how
can it be fixed?)  The last paragraph asking for network manager
recommendations other than wicd was an afterthought.  You are correct:
I should have made it two posts.

B

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Gene Heskett]

On Monday 27 May 2019 02:03:27 am Andy Smith wrote:

> Hello,
>
> On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > > On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> > > > No Andy, it didn't drink my last beer (Murphy does that), or
> > > > kill any kittens but it did totally disable ipv4. How? Simply by
> > > > refusing to apply a route/gateway to the ipv4 settings we do
> > > > manually.
> > >
> > > Can you show the archive link to the email where it was
> > > established that having IPv6 enabled in the kernel prevented your
> > > IPv4 configuration from being applied?
>
> Somehow you have failed to respond to this very simple request,
> opting instead to just ramble on restating yourself.
>
> There doesn't seem to be any point in interacting further.
>
> It's a shame that you waste everyone's time with these delusions.
> Not just people trying to help you but also those future searchers
> who are having problems with the same software as you and are led on
> a wild goose chase when you report that IPv6 is the root cause,
> amidst pages and page of distraction, yet somehow never get around
> to explaining how or why.
>
> Andy

Because I haven't found the why yet, else I would gladly advise the list 
of my findings, all I have repeatedly observed is the effect, both on 
amd64 and on arm64. Also since jessie on the armhf, but that was 2 years 
back and I don't recall exactly what I did other than removing N-M and 
chattr +i the two files mentioned ad nausium already. My arm64's are all 
newer, and haven't seen a jessie install, but the spi driver isn't 
usable at data rates of 10 megabits, let alone the 40+ a pi3b is doing.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Problems {PEBKAC?} running mmdebstrap for 1st time

[Jonas Smedegaard]

Quoting Richard Owlett (2019-05-27 17:23:17)
> On 05/26/2019 10:05 AM, Richard Owlett wrote:
> > On 05/26/2019 09:52 AM, Jonas Smedegaard wrote:
> >> Quoting Richard Owlett (2019-05-26 16:34:17)
> >>> I was investigating using multistrap, but it has been orphaned. 
> >>> mmdebstrap apparently has the desired features of multistrap but 
> >>> is available only in Buster.
> >>>
> >>> I do not have the available bandwidth to install Buster. In 
> >>> Stretch perl is 5.24.1-3+deb9u5 but is 5.28.1-6 in Buster.
> >>>
> >>> Is it feasible to run under Stretch? How?
> >>
> >> mmdebstrap has no tight dependencies so you should be able to 
> >> simply install the Buster package in Stretch and try use it.
> > 
> 
> My command was:
> mmdebstrap --variant=required stretch test1.tar 
> file:///media/richard/dvds/dvd1.iso
> 
> The error received was:
> > sh: 1: fakechroot: not found
> > sh: 1: proot: not found
> > E: unable to pick chroot mode automatically
> 
> That was resolved by installing "fakechroot". I had read the man page 
> as implying the use of a tar file did not require it.
> 
> That left me with the problem of telling the instance of apt being run 
> internally by mmdebstrap that dvd1.iso is trusted. I unsuccessfully 
> tried using the distribution DVD itself.
> 
> What is the proper syntax to use dvd1.iso {preferred} or DVD in drive 
> {last resort} as my repository?

mmdebstrap (and multistrap which you originally mentioned) are unrelated 
to dealing with ISO files.

What do you expect to achieve by "investigating using multistrap" and 
mmdebstrap?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: NIC Bonding 802.3ad LACP without switch

[Sven Hartge]

basti  wrote:

> also on a network card with 2 NIC's

> srv-a nic ens2f0  ens2f0 srv-b
>   ens2f1  ens2f1

> Can I use a switch that only supoort static LAC to speedup my
> connection? For example tp-link TL-SG108E ? Or must it support LACP?

For this direct connection you should use "balance-rr" or mode 0.
This will get you a true 2GBit connection even with only one active
flow.

All other modes will only use one connection per flow, limiting you to
1GBit.

Source: I've been doing bonding with Linux for as long as the bonding
driver exists. 

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: NIC Bonding 802.3ad LACP without switch

[Sven Hartge]

Reco  wrote:
> On Mon, May 27, 2019 at 01:48:39PM +0200, basti wrote:

>> Can this mode be used in this setup?

> AFAIK standard linux bonding can only use Passive LACP in 802.3ad.

No, it does active LACP.

>> How must I configure the other side?

> That's means you have to use openvswitch on either side as it can be
> configured to send LACPDUs (i.e. you can switch it to Active LACP).

Sorry, wrong.

S!

-- 
Sigmentation fault. Core dumped.

Problems {PEBKAC?} running mmdebstrap for 1st time

[Richard Owlett]

On 05/26/2019 10:05 AM, Richard Owlett wrote:

On 05/26/2019 09:52 AM, Jonas Smedegaard wrote:

Quoting Richard Owlett (2019-05-26 16:34:17)

I was investigating using multistrap, but it has been orphaned.
mmdebstrap apparently has the desired features of multistrap but is
available only in Buster.

I do not have the available bandwidth to install Buster.
In Stretch perl is 5.24.1-3+deb9u5 but is 5.28.1-6 in Buster.

Is it feasible to run under Stretch? How?


mmdebstrap has no tight dependencies so you should be able to simply
install the Buster package in Stretch and try use it.




My command was:
mmdebstrap --variant=required stretch test1.tar 
file:///media/richard/dvds/dvd1.iso


The error received was:

sh: 1: fakechroot: not found
sh: 1: proot: not found
E: unable to pick chroot mode automatically


That was resolved by installing "fakechroot". I had read the man page as 
implying the use of a tar file did not require it.


That left me with the problem of telling the instance of apt being run 
internally by mmdebstrap that dvd1.iso is trusted. I unsuccessfully 
tried using the distribution DVD itself.


What is the proper syntax to use dvd1.iso {preferred} or DVD in drive 
{last resort} as my repository?

Re: NIC Bonding 802.3ad LACP without switch

[basti]

also on a network card with 2 NIC's

srv-a nic ens2f0  ens2f0 srv-b
  ens2f1  ens2f1

Can I use a switch that only supoort static LAC to speedup my
connection? For example tp-link TL-SG108E ? Or must it support LACP?



On 27.05.19 15:49, Reco wrote:
>   Hi.
> 
> On Mon, May 27, 2019 at 03:36:38PM +0200, basti wrote:
>> Hello sven,
>> hello reco,
>>
>> I want to speedup my network connection beween srv-a and srv-b. There is
>> only a 1:1 connection.
> 
> Any bonding mode will utilize a single link in such case.
> The 'catch 22' for active-active bonding is that you can utilize more
> that one link for egress traffic (assuming multiple receivers), but
> ingress traffic will be the same on all links.
> 
> What you need is https://www.multipath-tcp.org/ . Or buy 10Gbps NICs,
> they are relatively cheap these days.
> 
> Reco
> 

Re: Insidious systemd

[Patrick Bartek]

On Mon, 27 May 2019 09:58:50 +0300
Ivan Ivanov  wrote:

> You could switch to Devuan - it's like a Debian but without this
> SystemD crap of 1.2 million code lines.
> https://www.phoronix.com/scan.php?page=news_item=Systemd-1.2-Million

I am aware of Devuan, but at the time I installed Stretch (about a
year ago after long term support of Wheezy ceased), Devuan ASCII was not
ready. Plus, I was wary of Devuan's support. That opinion has changed
since ASCII's release.

Thanks for your input.

B

Re: NIC Bonding 802.3ad LACP without switch

[Reco]

Hi.

On Mon, May 27, 2019 at 04:36:10PM +0200, basti wrote:
> also on a network card with 2 NIC's
> 
> srv-a nic ens2f0  ens2f0 srv-b
>   ens2f1  ens2f1
> 
> Can I use a switch that only supoort static LAC to speedup my
> connection? For example tp-link TL-SG108E ?

They invented balance-alb and balance-tlb just for that.
But - neither of them will do you any good.

>  Or must it support LACP?

LACP is also unable to convert two Gigabit NICs to a single Two-Gigabit
one. You need TCP multipathing or its equivalent.

Reco

Re: NIC Bonding 802.3ad LACP without switch

[basti]

also on a network card with 2 NIC's

srv-a nic ens2f0  ens2f0 srv-b
  ens2f1  ens2f1

Can I use a switch that only supoort static LAC to speedup my
connection? For example tp-link TL-SG108E ? Or must it support LACP?

On 27.05.19 15:49, Reco wrote:
>   Hi.
> 
> On Mon, May 27, 2019 at 03:36:38PM +0200, basti wrote:
>> Hello sven,
>> hello reco,
>>
>> I want to speedup my network connection beween srv-a and srv-b. There is
>> only a 1:1 connection.
> 
> Any bonding mode will utilize a single link in such case.
> The 'catch 22' for active-active bonding is that you can utilize more
> that one link for egress traffic (assuming multiple receivers), but
> ingress traffic will be the same on all links.
> 
> What you need is https://www.multipath-tcp.org/ . Or buy 10Gbps NICs,
> they are relatively cheap these days.
> 
> Reco
> 

Fwd: Debian Stretch, no password prompt for luks-encrypted home partition during boot

[Sergey Belyashov]

I have system with soft raid and /home is encrypted (one of raid1
partitions is encrypted using luks with password). When I boot it using
default boot kernel options (ro quiet) systemd stops on waiting for
partition, but no any password prompt. I try to boot with plymouth (ro
quiet splash), but it does not help me. I may boot only using "recovery
mode". In this case system asks me for password and I may enter it (but
there are lot of kernel messages after prompt).
update-initramfs finishes without errors or warnings.
What I'm doing wrong?

Best regards,
Sergey Belyashov

Additional information:

mdadm.conf:
ARRAY /dev/md0 metadata=0.90 UUID=91f74976:a3538ec7:cb201669:f728008a
ARRAY /dev/md1 metadata=1.2 UUID=d68931c6:642d72fc:b7471e62:33eab4d7
name=my-server:1
ARRAY /dev/md2 metadata=1.2 UUID=c42e4696:cb876ca7:c2773edf:e9b17a82
name=my-server:2

/proc/mdstat:
md0 : active raid1 sda3[0] sdc3[1]
  1462886848 blocks [2/2] [UU]

md1 : active (auto-read-only) raid1 sdc2[1] sda2[0]
  1998848 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sdc1[1] sda1[0]
  248640 blocks super 1.2 [2/2] [UU]

crypttab:
#UUID=e7a2e597-8f57-4faf-b32d-f24b5720ffe5 same as /dev/md0p3
crypto-home UUID=e7a2e597-8f57-4faf-b32d-f24b5720ffe5 none luks

fstab:
/dev/md0p1 /   ext4
 errors=remount-ro 0   1
/dev/md0p2 /varext4
 defaults0   2
/dev/md1 noneswap
 sw  0   0
/dev/md2 /boot   ext4
 defaults0   2
/dev/mapper/crypto-home   /home   autodefaults
   0   2
...

$ egrep "^CRYPTSETUP" /etc/cryptsetup-initramfs/conf-hook
CRYPTSETUP=y

$ uname -a
Linux my-server 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)
x86_64 GNU/Linux

systemd has version: 232-25+deb9u11
cryptsetup has version: 2:1.7.3-4
initramfs-tools has version: 0.130

Re: NIC Bonding 802.3ad LACP without switch

[Reco]

Hi.

On Mon, May 27, 2019 at 03:36:38PM +0200, basti wrote:
> Hello sven,
> hello reco,
> 
> I want to speedup my network connection beween srv-a and srv-b. There is
> only a 1:1 connection.

Any bonding mode will utilize a single link in such case.
The 'catch 22' for active-active bonding is that you can utilize more
that one link for egress traffic (assuming multiple receivers), but
ingress traffic will be the same on all links.

What you need is https://www.multipath-tcp.org/ . Or buy 10Gbps NICs,
they are relatively cheap these days.

Reco

Re: NIC Bonding 802.3ad LACP without switch

[basti]

Hello sven,
hello reco,

I want to speedup my network connection beween srv-a and srv-b. There is
only a 1:1 connection.
I have try to use balance-alb and copy some files from a to b with only
112 MB/s with dd and netcat.

So Im not shure if balance-alb use both interfaces.

On 27.05.19 15:09, Reco wrote:
>   Hi.
> 
> On Mon, May 27, 2019 at 01:48:39PM +0200, basti wrote:
>> Can this mode be used in this setup?
> 
> AFAIK standard linux bonding can only use Passive LACP in 802.3ad.
> 
>> How must I configure the other side?
> 
> That's means you have to use openvswitch on either side as it can be
> configured to send LACPDUs (i.e. you can switch it to Active LACP).
> 
> I'd say it'll be easier to use balance-alb or balance-tlb in such setup.
> 
> Reco
> 

Re: IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[tomas]

On Mon, May 27, 2019 at 08:58:14AM -0400, rhkra...@gmail.com wrote:
> On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> > On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> 
>  below>
> 
> > You are determined to exterminate any and all users of a hosts file,
> > staticly defined network. Its ideal for small home networks.
> 
> Hmm, that's interesting -- is there an analog to or replacement for the hosts 
> file on ipv6?

/etc/hosts. It works fine for both ipv4 and ipv6. Nothing changes
(except the address format, that is). Both can be mixed in /etc/hosts.

Cheers
-- t


signature.asc
Description: Digital signature

Re: NIC Bonding 802.3ad LACP without switch

[Reco]

Hi.

On Mon, May 27, 2019 at 01:48:39PM +0200, basti wrote:
> Can this mode be used in this setup?

AFAIK standard linux bonding can only use Passive LACP in 802.3ad.

> How must I configure the other side?

That's means you have to use openvswitch on either side as it can be
configured to send LACPDUs (i.e. you can switch it to Active LACP).

I'd say it'll be easier to use balance-alb or balance-tlb in such setup.

Reco

Re: NIC Bonding 802.3ad LACP without switch

[Sven Hartge]

basti  wrote:

> I have 2 Servers both of them has an dual port nic, I want to bond this
> and try to configure this in 802.3ad mode. There are no switch beween,
> and there is no crossover cable installed.

"and there is no crossover cable installed"?

Beside the point that Gigabit Ethernet does no longer need special
cross-over cables to work, what do you want to achieve here?

The different bonding protocols have some very special ways of working
and selection the right one depends on what the problem is.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

IPV6 hosts file (was: Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?))

[rhkramer]

On Monday, May 27, 2019 12:41:36 AM Gene Heskett wrote:
> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:



> You are determined to exterminate any and all users of a hosts file,
> staticly defined network. Its ideal for small home networks.

Hmm, that's interesting -- is there an analog to or replacement for the hosts 
file on ipv6?

Aside / background: AFAIK, I am not using IPV6 on either my Wheezy or Jessie 
system, but, I haven't really transitioned to the Jessie system as my everyday 
machine -- I don't really "surf the net" there, but instead tend to search for 
specific technically oriented pages related to the (development) work I'm 
trying to do on that Jessie system -- I don't notice much advertising -- it's 
probably because of the pages I view.

Utilisation de dhclient-up-hooks

[Olivier]

Bonjour,

La doc dhclient-script [1] fait référence à un script
/etc/dhcp/dhclient-up-hooks qui n'est jamais exécuté sur ma machine sous
Stretch.

Sur ma machine, les scripts dans /etc/dhcp/dhclient-enter-hooks.d sont
exécutés mais pas le script /etc/dhcp/dhclient-up-hooks ou des variations
de celui-ci (script /etc/dhcp/dhclient-up-hooks.d/ffobar, ...).

Qui a réussit à faire exécuter ce script ?

Slts

[1] https://linux.die.net/man/8/dhclient-script

NIC Bonding 802.3ad LACP without switch

[basti]

Hello,
I have 2 Servers both of them has an dual port nic, I want to bond this
and try to configure this in 802.3ad mode. There are no switch beween,
and there is no crossover cable installed.

Can this mode be used in this setup?
How must I configure the other side? (I have use this howto,
https://www.snel.com/support/lacp-bonding-on-debian-7-8-9/)

Best Regards,

Re: Insidious systemd

[Richard Owlett]

On 05/26/2019 10:05 PM, bw wrote:

[snip]

It might be a bug if wicd requires systemd as init? but I have not
researched the issue. I think it's a lot of work for little gain
to fight the way things are.  Systemd is here, it has been working fine
for yrs.  It is the default init for debian.  I really dont see why you
would say it is 'insidiuous' because it is widely known to be this way.


Synonyms for insidious include subtle, seductive, treacherous; but 
apparently not secret nor unknown.

https://www.merriam-webster.com/dictionary/insidious

Re: Release netboot installer fails

[Brian]

On Sun 26 May 2019 at 11:18:52 -0400, Gregory Seidman wrote:

> This is mostly to document what I encountered, because I haven't had time
> to put it in a bug. (I don't know if I will get around to it, honestly. If
> someone else wants to put it in they should feel free and post a response
> to the list with the bug link.) I also have a bonus warning regarding
> encrypted root at the end.
> 
> First, the premise I'm working from:
> 
>   The released netboot installer (i.e. netboot.tar.gz) downloadable via
>   https://www.debian.org/distrib/netinst should be capable of
>   installing the stable distribution, and should probably support any
>   options it presents.
> 
> If there isn't agreement on that, well, don't even bother with the rest.
> 
> Using the amd64 netboot (pxelinux.0, etc.), I had my machine PXE boot.
> Everything boots and run fine until it tries to load installer components,
> at which point it apparently loads udebs from the testing distribution with
> kernel modules that don't match the installer kernel. At that point the
> installation cannot proceed since it can't find disks without the drivers
> for them (e.g. sd_mod).
> 
> I would have thought that the udebs for the stable distribution installer
> would remain (wait for it) stable. I'm a little unclear on whether there is
> any segregation of udebs by distribution at all. I haven't delved into the
> details of the installer, and I regret that I don't have time to do so, but
> I would hope this is fixable.

Bug #749991?

-- 
Brian.

Debian Stretch, no password prompt for luks-encrypted home partition during boot

[Sergey Belyashov]

I have system with soft raid and /home is encrypted (luks with password).
When I boot it using default boot kernel options (ro quiet) systemd stops
on waiting for partition, but no any password prompt. I try to boot with
plymouth (ro quiet splash), but it does not help me. I may boot only using
"recovery mode". In this case system asks me for password and I may enter
it (but there are lot of kernel messages after prompt).
update-initramfs finishes without errors or warnings.
What I'm doing wrong?

Best regards,
Sergey Belyashov

Additional information:

mdadm.conf:
ARRAY /dev/md0 metadata=0.90 UUID=91f74976:a3538ec7:cb201669:f728008a
ARRAY /dev/md1 metadata=1.2 UUID=d68931c6:642d72fc:b7471e62:33eab4d7
name=my-server:1
ARRAY /dev/md2 metadata=1.2 UUID=c42e4696:cb876ca7:c2773edf:e9b17a82
name=my-server:2

/proc/mdstat:
md0 : active raid1 sda3[0] sdc3[1]
  1462886848 blocks [2/2] [UU]

md1 : active (auto-read-only) raid1 sdc2[1] sda2[0]
  1998848 blocks super 1.2 [2/2] [UU]

md2 : active raid1 sdc1[1] sda1[0]
  248640 blocks super 1.2 [2/2] [UU]

crypttab:
#UUID=e7a2e597-8f57-4faf-b32d-f24b5720ffe5 same as /dev/md0p3
crypto-home UUID=e7a2e597-8f57-4faf-b32d-f24b5720ffe5 none luks

fstab:
/dev/md0p1 /   ext4
 errors=remount-ro 0   1
/dev/md0p2 /varext4
 defaults0   2
/dev/md1 noneswap
 sw  0   0
/dev/md2 /boot   ext4
 defaults0   2
/dev/mapper/crypto-home   /home   autodefaults
   0   2
...

$ egrep "^CRYPTSETUP" /etc/cryptsetup-initramfs/conf-hook
CRYPTSETUP=y

$ uname -a
Linux my-server 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)
x86_64 GNU/Linux

systemd has version: 232-25+deb9u11
cryptsetup has version: 2:1.7.3-4
initramfs-tools has version: 0.130

Re: reboot stuff doesn't start

[Reco]

Hi.

On Sun, May 26, 2019 at 05:45:56PM -0400, Gene Heskett wrote:
> On Sunday 26 May 2019 12:13:38 pm john doe wrote:
> 
> > On 5/26/2019 5:32 PM, Gene Heskett wrote:
> > > Greetings all;
> > >
> > > New stretch install about 2 weeks ago, cleaning up the remains. 
> > > Fresh disk, so no leftovers. But lots of stuff has been copied over
> > > from the wheezy disk since
> > >
> > > I have spamassassin enabled in my rc5.d, and I start heyu engine and
> > > heyu monitor in my rc.local for several years , but neither one is
> > > actually being started now.
> > >
> > > I can restart spamassassin once logged it, ditto for heyu and
> > > friends.
> > >
> > > Why don't they start when they're supposed to?
> >
> > Look at the service 'rc.local'.:
> >
> > $ systemctl status/enable rc.local
> 
> hum:
> root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
...
> May 25 12:03:03 coyote rc.local[884]: read: Connection reset by peer
...

> None of which gives me the faintest clue whats wrong with it.

It does for me.

First,

> root@coyote:GenesAmandaHelper-0.61$ cat /etc/rc.local
> #!/bin/sh -e

Any execution error will terminate the script.


Second,

> # mount the sshfs shares. Suggested way didn't work,
> # so changed syntax to this, which does
> su gene -c "sshfs gene@shop:/ /sshnet/shop"

It fails here, or at any of the later sshfs invocations.
Either your resolver is broken or remote sshd does not function.

Note - you're doing it wrong by configuring per-user mounts at
systemwide level. They invented systemd user-level services just for
that.

Also,

> # Now, udev is being a cast iron bitch,

But overriding it this way will only work until the first 'udevadm
trigger' or USB device hotplug.
They invented 'dialout' group (and use it by default) to avoid such
kludges, consider using it.

And,

> # Now, need some heyu stuff run
> su gene -c "/usr/local/bin/heyu engine &"
> su gene -c "/usr/local/bin/heyu monitor &"

this just cries 'put me into systemd unit'.
Abusing shell's background in rc.local is good for all those enterprisey
"i-dont-know-what-im-doing" devopses. Don't be like them.


In short, everything in your rc.local does not belong there.

Reco

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Jonas Smedegaard]

Quoting Curt (2019-05-27 09:46:00)
> On 2019-05-27,   wrote:
> > If Network Manager is giving you grief, please go bark up /that/ 
> > tree (I can't say much about N-M, because I banned it from my boxes 
> > about ten years ago: I was at a customer's, in his LAN via an 
> > Ethernet, when N-M suddenly saw a WLAN out there, out the window and 
> > said "oh, let's go online over there" and obliterated my network 
> > setting in favor of some seedy captive portal. That was when I 
> > decided that N-M and me, we aren't made for each other).
> >
> 
> This is a grave bug. I suppose we can assume from your description 
> that the seedier the wifi portal, the more likely it is to 
> spontaneously occur, despite any and all user configuration or 
> intervention.
> 
> Would it be possible to post the link to your bug report? To your 
> knowledge has the bug been fixed since you reported it a decade ago?  
> As many users here including myself rely on the N-M app, I'm sure we 
> would all be interested in knowing where we stand.

I fully agree, this is a quite scary and severe bug in network-manager 
that I want to inspect closer as Debian Developer.

Please do share information about where it was reported to I can follow 
up on it.  I sincerely hope that it has not gone unfixed through these 
many years!!!


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[tomas]

On Mon, May 27, 2019 at 07:46:00AM -, Curt wrote:
> On 2019-05-27,   wrote:
> >
> >
> > If Network Manager is giving you grief, please go bark up /that/ tree

[...]

> This is a grave bug. I suppose we can assume from your description that
> the seedier the wifi portal, the more likely it is to spontaneously
> occur, despite any and all user configuration or intervention.
> 
> Would it be possible to post the link to your bug report? To your
> knowledge has the bug been fixed since you reported it a decade ago?  As
> many users here including myself rely on the N-M app, I'm sure we would
> all be interested in knowing where we stand. 

I'd assume this doesn't happen anymore: the density of open (but captive)
WiFi portals is so high these days that no one would use N-M these days
anymore.

I didn't report that bug at the time.

Happy ifupdown user since then :-)

Cheers
-- tomás


signature.asc
Description: Digital signature

Re: reboot stuff doesn't start

[Curt]

On 2019-05-26, Gene Heskett  wrote:
> hum:
> root@coyote:GenesAmandaHelper-0.61$ systemctl status rc.local
> ● rc-local.service - /etc/rc.local Compatibility
>Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor 
> preset: enabled)

I found this (not sure if it's entirely applicable, or even entirely
wise, but there you go):

https://www.linuxbabe.com/linux-server/how-to-enable-etcrc-local-with-systemd



-- 
“Decisions are never really made – at best they manage to emerge, from a chaos
of peeves, whims, hallucinations and all around assholery.” – Thomas Pynchon

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Curt]

On 2019-05-27,   wrote:
>
>
> If Network Manager is giving you grief, please go bark up /that/ tree
> (I can't say much about N-M, because I banned it from my boxes about
> ten years ago: I was at a customer's, in his LAN via an Ethernet, when
> N-M suddenly saw a WLAN out there, out the window and said "oh, let's
> go online over there" and obliterated my network setting in favor of
> some seedy captive portal. That was when I decided that N-M and me,
> we aren't made for each other).
>

This is a grave bug. I suppose we can assume from your description that
the seedier the wifi portal, the more likely it is to spontaneously
occur, despite any and all user configuration or intervention.

Would it be possible to post the link to your bug report? To your
knowledge has the bug been fixed since you reported it a decade ago?  As
many users here including myself rely on the N-M app, I'm sure we would
all be interested in knowing where we stand. 

-- 
“Decisions are never really made – at best they manage to emerge, from a chaos
of peeves, whims, hallucinations and all around assholery.” – Thomas Pynchon

Re: lightweight wifi UI (Was: Insidious systemd)

[Jonas Smedegaard]

Quoting Patrick Bartek (2019-05-27 03:49:06)
> Needing to convert this box from wired ethernet to wireless, I 
> searched for a suitable network manager and wicd looked good: No 
> desktop environment dependencies (I use a window manager Openbox and 
> single lxpanel), compatibility with Openbox, etc.

[ unneeded systemd details snipped ]

> After more investigating, I came across wifi-radar whose simulated 
> install doesn't muck my system.  Any suggestions for something better?  
> I could just go with iwconfig or iw?  No big deal.  I've done it 
> before.  But being lazy, if I can find an app to do the work, so much 
> the better.

Here are the options I know of which provides a UI with wifi strength 
and being more lightweight than network-manager, listed in order of 
personal preference for install on Buster (some, iwd in particular, is 
notably less mature on Stretch):

iwd is extremely lightweight console-only tool yet provides interactive 
probing of wifi strength.  It integrates fine with network-manager and 
systemd if a) explicitly telling those systems to use it and b) 
explicitly turned off wpasupplicant.

connman is in my experience more reliable than wicd but looks ugly.

wicd felt unreliable in my experience - but possibly I didn't give it 
enough attention (see above about disabling wpasupplicant).

iw + wifi-radar if all else fails. :-)


 - Jonas


P.S. At first I skipped this excellent question due to it being 
presented as a rant about systemd.  I dearly recommend to _avoid_ mixing 
rants with questions, as you then are more likely to miss valuable 
input.

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Re: network installer will not boot

[Thomas Schmitt]

Hi,

>I used F2 to shut off "secure boot".
> Now, there are noises that suggest the
> CD is being read, but nothing displays
> on the monitor--- no warnings, no diagnostics,
> just a blinking cursor in the upper-left
> corner.

Did you alread try legacy CSM (BIOS emulation) ?


Have a nice day :)

Thomas

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[tomas]

On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:

[...]

> I don't think so. ipv6 I'm sure is nice where its available.  Where it is 
> not available, its a pain in the ass because even if you set it up as a 
> static ipv4, N-M will tear it down in 5 minutes or less. And N-M is a 
> dependency because most have a dhcpd running, probably in the router by 
> default.
> 
> You are determined to exterminate any and all users of a hosts file, 
> staticly defined network. Its ideal for small home networks.

[...]

I've been following this monster thread with one eye (sorry, not enough
bandwidth at the moment) and I think, Gene, you're barking up the wrong
tree.

IPv6 can coexist nicely with IPv4 (this is by design). My work laptop
(which is my only work box) has both stacks up and running. Most places
I'm at don't even know IPv6 exist. My ISP at home likewise. But my home
router does, so I can magically "ping6" the more intelligent hosts
at home, without having had to configure anything.

If Network Manager is giving you grief, please go bark up /that/ tree
(I can't say much about N-M, because I banned it from my boxes about
ten years ago: I was at a customer's, in his LAN via an Ethernet, when
N-M suddenly saw a WLAN out there, out the window and said "oh, let's
go online over there" and obliterated my network setting in favor of
some seedy captive portal. That was when I decided that N-M and me,
we aren't made for each other).

Cheers
-- t


signature.asc
Description: Digital signature

Re: That time IPv6 farted in Gene's church (Was Re: forcedeth?)

[Andy Smith]

Hello,

On Mon, May 27, 2019 at 12:41:36AM -0400, Gene Heskett wrote:
> On Sunday 26 May 2019 10:09:49 pm Andy Smith wrote:
> > On Sat, May 25, 2019 at 11:25:26AM -0400, Gene Heskett wrote:
> > > No Andy, it didn't drink my last beer (Murphy does that), or kill
> > > any kittens but it did totally disable ipv4. How? Simply by refusing
> > > to apply a route/gateway to the ipv4 settings we do manually.
> >
> > Can you show the archive link to the email where it was established
> > that having IPv6 enabled in the kernel prevented your IPv4
> > configuration from being applied?

Somehow you have failed to respond to this very simple request,
opting instead to just ramble on restating yourself.

There doesn't seem to be any point in interacting further.

It's a shame that you waste everyone's time with these delusions.
Not just people trying to help you but also those future searchers
who are having problems with the same software as you and are led on
a wild goose chase when you report that IPv6 is the root cause,
amidst pages and page of distraction, yet somehow never get around
to explaining how or why.

Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting