Re: [Buster]: KDE wierdness: missing window titlebars + more

[local10]

Aug 27, 2018, 6:00 PM by cyaiple...@sitesplace.net:

> I had that happen not too long ago in Stretch. I just rebooted and it was OK.
>
A reboot didn't do it for me, the issue still persist.


> You may want to also check your settings in Display - Compositor. You may 
> have to change to a different rendering backend. Also you might want to 
> uncheck any experimental options if you have them checked.
>
What's even stranger I can't find the KDE System Preferences app (what package 
is it in, by the way?), so I can't even find a way to change  
display/keyboard/mouse/etc KDE settings. I installed buster fresh, that is, 
there were no left over libs/config files/etc that would affect the new KDE 
installation yet something is very screwed up with either KDE on my PC or with 
KDE packages in testing.

Anyone using KDE in buster? If so, are you experiencing any issues with KDE 
like missing window titlebars, missing apps, etc.?

Thanks

Re: mailing list vs "the futur"

[John Hasler]

David writes:
> I didn't know they were asking the ISP to *host* the newsgroups, just
> to allow NNTP stuff to pass from whoever is hosting it to the user,
> who pays for the usage they make of it.

The user pays a fixed monthly fee and was promised a certain bandwidth
(*bandwidth*, not monthly total data usage).  Of course he expects to
never see less than that and of course marketing will have overpromised.
This leads to pressure to find ways to cut down peak bandwidth without
angering very many customers.  Somebody notices that peak bandwidth
usage by NNTP users (the ones who download binary groups, which is what
the ISP management thinks is all there is to Usenet) is well above
average and that there aren't very many of them...
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: sometimes i go huh (grep result)

[songbird]

Greg Wooledge wrote:
> On Mon, Aug 27, 2018 at 10:36:12AM -0400, songbird wrote:
>> me@ant(25)$ env | grep -F "-g"
>> grep: invalid option -- 'g'
>
> You want either -- or -e.
>
> grep -F -- -g
> grep -F -e -g

  i just found it interesting that after this many years
of linux/unix i'd not remembered this issue.  my golden
years are ahead a bit yet so i sure hope this isn't a
mental issue!  lol


  songbird

Re: Autologin not working (lightdm, openbox)

[Shea Alterio]

On Mon, Aug 27, 2018 at 4:50 AM Alexandre Rossi 
wrote:

> Hi,
>
> > Before anyone asks, i've looked all over the wiki and every other post
> online so i'm not sure why this isn't working. When I start up my machine X
> starts up fine. and it goes to the lightdm login screen, but it still makes
> me put in the password.
> >
> > My user is in the autologin and nopasswdlogin groups, i've made the
> right changes to both the files listed below as A and B sources.
>
> I've always had no problem with autologin with lightdm, all I ever had
> to do was to set autologin-user in the [Seat:*] in
> /etc/lightdm/lightdm.conf . Another option that I have used
> successfuly is using lightdm-autologin-greeter and setting up
> autologin-user in
> /etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf
>
> I guess you already checked this but double check you are able to
> login with that user using a password.
>
> Alex
>

Thanks for the reply, Alex.  I haven't messed with it since yesterday, but
i'll try restoring the config files to their defaults and start over from
there.

I'm not sure if it matters, but  usually when I want any graphical system
with Debian, i install one of the desktop environments during the initial
setup. This install is for a very limited thin client with only 4gb
internal storage, so i had to install only SSH server and standard system
utilities, then install X / Openbox / LightDM after the fact. I found out
the hard way when I ran out of disk space trying to install LXDE as well. I
may be missing some packages needed to help facilitate autologin, not sure.

If your suggestions don't fix it i will reply to this thread later tonight
with my findings.

Thanks again,
Shea

Re: iproute, NM and ifupdown

[Gene Heskett]

On Monday 27 August 2018 15:59:09 David Wright wrote:

> On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> > On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
> > > > Most recently on a stretch install on a rock64 I had to erect
> > > > immutable attributes to resolv.conf after making it a real file,
> > > > and e-n-i to make networking Just Work.
> > >
> > > /etc/resolv.conf is a rather different topic, because it is not
> > > related to a specific interface and may be written by several
> > > pieces of software, including but not limited to NetworkManager
> > > when configuring *any* interface. I would suggest using resolvconf
> > > but I suspect you would not like it either.
> >
> > Ohkaay, but where's the docs on this mysterious resolvconf?
> >
> > What we do have is missing (wheezy) or horribly incomplete (jessie).
> >
> > But I'll have to take that back, my apologies. I just read the
> > stretch version on that rock64.  And as man pages go, its decent.
> > And I'll have to do some experimenting as its possible I can train
> > it to behave.
> >
> > And curious I blink compared the jessie vs stretch versions,
> > stretch's is both longer AND more complete, and two different
> > authors and formatted completely different. And wheezy doesn't even
> > have the man page. I don't even know if it should, maybe not for
> > wheezy, lots of water has been recycled since those installs were
> > made, so I'll plead oldtimers.
>
> This is very strange. I just did (in 80 column xterms):
>
> $ man resolvconf > /tmp/resolvconf-stretch
>
> and the same for jessie and wheezy on the appropriate computers.
>
> $ diff /tmp/resolvconf-[sj]*
> 3,4d2
> <
> <
> 278d275
> <
> 295,296d291
> <
> <
> $
>
> so a few blank lines have been removed between jessie and stretch.
> As for wheezy not having a man page:
>
> $ wc /tmp/resolvconf-wheezy
>   301  1748 14876 /tmp/resolvconf-wheezy
> $ cat /etc/debian_version
> 7.11
> $ dpkg -l resolvconf
> Desired=Unknown/Install/Remove/Purge/Hold
>
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/T
> |rig-pend / Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> |
> ||/ NameVersionArchitecture   Description
>
> +++-===-==-==-
>=== ii  resolvconf  1.67   all 
>   name server information handler $ dpkg -L resolvconf | grep
> /man./
> /usr/share/man/man8/resolvconf.8.gz
> /usr/share/man/man5/interface-order.5.gz
> $
>
> So one can't help wondering exactly what is installed on your machines
> if things don't match. Note that there are significant differences
> between the different versions, so following the stretch/jessie man
> page could give you problems on a wheezy machine. (I haven't checked
> out backports.)
>
> Cheers,
> David.

What is installed on 4 of the 6 boxes here, is a wheezy install thats 
been tweaked to A: put a realtime kernel on it so it can run linuxcnc on 
real hardware. The stretch I'll install here after my new drive cage 
arrives, and I found today that newegg's fedex is a week for delivery, 
its not expected to arrive here before Thursday evening, has also been 
tweaked to run LinuxCNC, probably by a real time kernel replacement..

Thanks David, gotta run the mussus just called on the intercom.  Later.

-- 
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: mailing list vs "the futur"

[Gene Heskett]

On Monday 27 August 2018 13:07:27 David Wright wrote:

> On Mon 27 Aug 2018 at 11:37:48 (-0400), Gene Heskett wrote:
> > On Monday 27 August 2018 11:11:37 David Wright wrote:
> > > On Sat 25 Aug 2018 at 14:27:38 (-0500), John Hasler wrote:
> > > > David writes:
> > > > > Or are you talking about some type of "shared channel" of
> > > > > which I have no knowledge?
> > > >
> > > > Cable providers may have a great many customers on a single
> > > > cable with large (but limited) bandwidth.
> > >
> > > Oh, like me, you mean. When we wanted to get our cable strung from
> > > the pole with the least obstructed view of our house, the linesman
> > > first told us that all the terminations were taken, but on ringing
> > > the office, he found that one line was not subscribed to, so we
> > > were able to connect to that pole. When I walk down the back
> > > alleys, I can see other poles connected to the same main coax feed
> > > that links the poles.
> > >
> > > I'm still scratching my head why subscribing to NNTP newsgroups
> > > should lead to bandwidth problems rather than usage ones. I can
> > > hit my bandwidth limits in many other ways like downloading
> > > youtube videos, watching TV, etc, but the hard limit is my usage,
> > > where I would end up paying money for any excess.
> >
> > That bandwidth limit is not on your side of the isp, its the
> > bandwidth from the main trunk lines to the isp. NNTP is a huge
> > bandwidth hog regardless of how much of it your isp accepts for
> > spooling on local disk to serve you.
>
> I didn't know they were asking the ISP to *host* the newsgroups,
> just to allow NNTP stuff to pass from whoever is hosting it to
> the user, who pays for the usage they make of it.
>
> > > > Some rural providers may have limited backhaul bandwidth.  They
> > > > make promises to customers based on optimistic estimates of peak
> > > > usage.
> >
> > Here at least, thats gradually getting better.
>
> I read that improvements are very patchy in the US.
>
> > > Now it appears that you're using "usage" where I would write
> > > "bandwidth". Am I in a minority of one here? Bandwidth is the rate
> > > of transfer of bits, whereas usage is the quantity of bits
> > > transferred irrespective of how fast they accumulated.
> >
> > Thats a pretty good view of the differences.
>
> But I get the impression that we have another baud/bitrate muddle.
>
> Cheers,
> David.

Likely, David.  The number of folks that understand the difference in any 
given crowd is a rather low percentage.


-- 
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: mailing list vs "the futur"

[Gene Heskett]

On Monday 27 August 2018 12:28:35 Dan Ritter wrote:

> On Mon, Aug 27, 2018 at 11:37:48AM -0400, Gene Heskett wrote:
> > That bandwidth limit is not on your side of the isp, its the
> > bandwidth from the main trunk lines to the isp. NNTP is a huge
> > bandwidth hog regardless of how much of it your isp accepts for
> > spooling on local disk to serve you.
>
> This is not the case.
>
> The NNTP server-to-server algorithm is analogous to rsync,
> if you think of:
>
> - each message is a file
> - each newsgroup is a directory
> - if the receiver doesn't have a directory, it won't be
>   sync'd over from the sender
> - the sender/receiver don't bother looking at contents
>   of each file to decide whether to update, just the
> name-timestamp
>
> And it always goes in exactly one direction; when the receiver
> wants to send messages back upstream, that's a different
> connection in which they swap places.
>
My knowledge is based on a conversation I had with my then isp in about 
1993 or so, so its entirely possible that the protocol has been changed 
since then. What they had then struck me as very very wastefull of 
resources. Because I was such a PITA, they actually built another 
machine for NNTP and had at bring in another oc3 circuit to feed it. I 
had what was a full house Amiga 2000 with 64 megs of ram on a PP 040 
board, had a pair of 1GB scsi seagates, their machine had a 47GB drive, 
which was filled in just an hour or so, so the expire was set at 8 
hours. So the last thing I did at night was dial them up and grab what I 
wanted that was new, and the first thing in the morning, the same.

Sheer economics has likely driven some major changes in how NNTP works 
today. And I expect thats a hell of a lot better for the average ma & pa 
isp. By the time I built a new machine and put red hat 5 on it, in 1998 
I think, NNTP had degenerated to 90% spam, so I never rejoined that pool 
party, it was too polluted for me. Email was easier to filter, and here 
I am still, almost 20 years later, and older too, I'll be 84 in a couple 
more months if I don't miss morning roll call first.

> NNTP is a bandwidth hog in exactly the same proportion as the
> space it occupies on disk.
>
> I have simplified for the sake of a familiar analogy.
>
> -dsr-

Take care Dan.

-- 
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: [Buster]: KDE wierdness: missing window titlebars + more

[cyaiplexys]

On 08/27/2018 04:55 PM, local10 wrote:

Hi,

Am experiencing a wierd issue with KDE after installing kde-standard package. 
KDE starts fine but shows an almost completely empty desktop: no taskbar, no 
launcher, no clock... just in the upper right conner there's a small rectangle  
that opens a menu allowing to add widgets and activities to the desktop. What's 
even stranger when ap app is launched its window does not even have a titlebar. 
There appears to be no way to minimize, maximize, move or even close the 
window. The app can be closed from its internal menu, if it has one, but that's 
about it.

Did I do something wrong or KDE is really that screwed up in testing at the 
moment?

Installed LXDE and LXDE performs as expected, normally looking windows, 
taskbar, etc.

Any ideas? Thanks


# aptitude show kde-standard
Package: kde-standard
Version: 5:102
State: installed
Automatically installed: no
Priority: optional
Section: metapackages
Maintainer: Debian Qt/KDE Maintainers mailto:debian-qt-...@lists.debian.org>>
Architecture: amd64
Uncompressed Size: 21.5 k
Depends: akregator (>= 4:17.12.3), ark (>= 4:17.08.3), dragonplayer (>= 4:17.08.3), gwenview (>= 
4:17.08.3), juk (>= 4:17.08.3), kaddressbook (>= 4:17.12.3), kate (>= 4:17.08.3), kcalc (>= 
4:17.08.3), kde-plasma-desktop (>= 5:102), kde-spectacle (>= 17.08.3), khelpcenter
  (>= 4:17.08.3), kmail (>= 4:17.12.3), knotes (>= 4:17.12.3), kopete (>= 4:17.08.3), 
korganizer (>= 4:17.12.3), kwalletmanager (>= 4:17.08.3), okular (>= 4:17.08.3), 
plasma-dataengines-addons (>= 4:5.10), plasma-pa (>= 5.10) | kmix (>= 4:17.08.3),
  plasma-runners-addons (>= 4:5.10), plasma-wallpapers-addons (>= 4:5.10), 
plasma-widgets-addons (>= 4:5.10), polkit-kde-agent-1 (>= 4:5.10), sweeper (>= 
4:17.08.3)
Recommends: konq-plugins (>= 4:17.08.3), plasma-nm (>= 4:5.10)


I had that happen not too long ago in Stretch. I just rebooted and it 
was OK.


You may want to also check your settings in Display - Compositor. You 
may have to change to a different rendering backend. Also you might want 
to uncheck any experimental options if you have them checked.


Sometimes though, when things update, old themes or window decorations 
aren't updated to support any new features. Try going back to the 
default window decoration and style. If it is in the default 
decoration/style maybe try a different one?

[Buster]: KDE wierdness: missing window titlebars + more

[local10]

Hi,

Am experiencing a wierd issue with KDE after installing kde-standard package. 
KDE starts fine but shows an almost completely empty desktop: no taskbar, no 
launcher, no clock... just in the upper right conner there's a small rectangle  
that opens a menu allowing to add widgets and activities to the desktop. What's 
even stranger when ap app is launched its window does not even have a titlebar. 
There appears to be no way to minimize, maximize, move or even close the 
window. The app can be closed from its internal menu, if it has one, but that's 
about it.

Did I do something wrong or KDE is really that screwed up in testing at the 
moment?

Installed LXDE and LXDE performs as expected, normally looking windows, 
taskbar, etc.

Any ideas? Thanks


# aptitude show kde-standard
Package: kde-standard   
Version: 5:102
State: installed
Automatically installed: no
Priority: optional
Section: metapackages
Maintainer: Debian Qt/KDE Maintainers mailto:debian-qt-...@lists.debian.org>>
Architecture: amd64
Uncompressed Size: 21.5 k
Depends: akregator (>= 4:17.12.3), ark (>= 4:17.08.3), dragonplayer (>= 
4:17.08.3), gwenview (>= 4:17.08.3), juk (>= 4:17.08.3), kaddressbook (>= 
4:17.12.3), kate (>= 4:17.08.3), kcalc (>= 4:17.08.3), kde-plasma-desktop (>= 
5:102), kde-spectacle (>= 17.08.3), khelpcenter
 (>= 4:17.08.3), kmail (>= 4:17.12.3), knotes (>= 4:17.12.3), kopete 
(>= 4:17.08.3), korganizer (>= 4:17.12.3), kwalletmanager (>= 4:17.08.3), 
okular (>= 4:17.08.3), plasma-dataengines-addons (>= 4:5.10), plasma-pa (>= 
5.10) | kmix (>= 4:17.08.3),
 plasma-runners-addons (>= 4:5.10), plasma-wallpapers-addons (>= 
4:5.10), plasma-widgets-addons (>= 4:5.10), polkit-kde-agent-1 (>= 4:5.10), 
sweeper (>= 4:17.08.3)
Recommends: konq-plugins (>= 4:17.08.3), plasma-nm (>= 4:5.10)

Re: mailing list vs "the futur"

[Dan Ritter]

On Mon, Aug 27, 2018 at 04:13:30PM -0400, Michael Stone wrote:
> On Mon, Aug 27, 2018 at 12:28:35PM -0400, Dan Ritter wrote:
> > On Mon, Aug 27, 2018 at 11:37:48AM -0400, Gene Heskett wrote:
> > > 
> > > That bandwidth limit is not on your side of the isp, its the bandwidth
> > > from the main trunk lines to the isp. NNTP is a huge bandwidth hog
> > > regardless of how much of it your isp accepts for spooling on local disk
> > > to serve you.
> > > 
> > 
> > This is not the case.
> 
> Yes it is. 

No, it's not.

"NNTP is a huge bandwidth hog regardless of how much of it your
ISP accepts for spooling on local disk to serve you."

Your irrelevant text storm is *entirely* about the case when
the ISP tries to accept and propagate binary froups.

Which you then go on to acknowledge:

> full newsfeed hit 1TB/day in the early 2000s, and most of the ISPs who were
...
> server. At this point I think a full newsfeed is pushing toward 50TB/day.
...
> In theory you can still use an NNTP client (vs a server) to follow a limited
> number of text-only groups fairly efficiently. In practice there's just not

That theory is practice. I have about five "upstream" NNTP
servers feeding me the groups I want; none of them do binary
groups at all. I pay one of them (ten Euros a year).



-dsr-

[SOLVED] Re: [Buster]: Can't start X: no screens found(EE)

[local10]

Aug 27, 2018, 12:35 PM by mrma...@earthlink.net:

> These suggest you are missing a firmware package for your Radeon HD 4200.
> firmware-linux & firmware-linux-non-free are meta packages. Likely you only 
> need
> firmware-amd-graphics and/or firmware-linux-free and/or firmware-misc-nonfree.
>

"firmware-linux-free" did not help but installing "firmware-amd-graphics" 
resoved the issue. Thanks

Re: mailing list vs "the futur"

[Michael Stone]

On Mon, Aug 27, 2018 at 12:28:35PM -0400, Dan Ritter wrote:

On Mon, Aug 27, 2018 at 11:37:48AM -0400, Gene Heskett wrote:


That bandwidth limit is not on your side of the isp, its the bandwidth
from the main trunk lines to the isp. NNTP is a huge bandwidth hog
regardless of how much of it your isp accepts for spooling on local disk
to serve you.



This is not the case.


Yes it is. Most ISPs stopped supporting NNTP because of the ridiculous 
bandwidth (and disk space) demands. Your rebuttal skipped over the part 
about people posting off-topic junk all over the place, and the fact 
that (the couple of cranks who actually just wanted to read comp.misc or 
whatever aside) most people who wanted "newsgroups" really wanted the 
high volume binary groups with pirated software or movies or 
whatever--so if an ISP dropped the high volume part of the NNTP feed, 
they basically had no reason not to drop the whole thing. Back in the 
late 90s when the handwriting was on the wall it was pushing toward 
100GB/day to keep up with a full newsfeed. Remember, disk was a heck of 
a lot more expensive then. A large ISP could drop a million dollars on a 
disk array, and only be able to retain a few days worth of traffic.  
Performance was lousy due to the churn, and people got into the habit of 
reposting everything basically constantly to counter the fact that 
retention was so low (driving the load higher and higher). A full 
newsfeed hit 1TB/day in the early 2000s, and most of the ISPs who were 
still trying to provide the service threw the towel in at that point. 
The costs were through the roof, the fraction of customers who used the 
service was miniscule, and almost nobody canceled because they turned 
off the news server. At this point I think a full newsfeed is pushing 
toward 50TB/day. That's a much, much, much smaller fraction of available 
bandwidth than it was 20 years ago, but here's the thing--the vast 
majority of everything on the news feed *is never looked at by a human*. 
That makes the case for keeping a server around really hard to justify 
for most ISPs. It's a wasteful and inefficient protocol that basically 
moves enormous quantities of bits around the world, then throws them 
away.


There's a reason usenet is effectively dead. It was a great idea 
technically, on a "safe" network. It's completely incapable of dealing 
with abuse on the open internet.


In theory you can still use an NNTP client (vs a server) to follow a 
limited number of text-only groups fairly efficiently. In practice 
there's just not that much left worth following because the experience 
got to be so bad, and because so few people are even aware it exists 
anymore. If you purchase newsgroup service as a standalone from a 
specialized company you typically get a somewhat more curated experience 
(for a pretty sizable fraction of the total price of your internet 
connection, to pay the costs outlined above). The reality is that the 
primary use of these services is downloading pirated software and other 
binaries.

Re: iproute, NM and ifupdown

[David Wright]

On Sun 26 Aug 2018 at 14:24:23 (-0400), Gene Heskett wrote:
> On Sunday 26 August 2018 13:36:41 Pascal Hambourg wrote:
> > Le 26/08/2018 à 17:24, Gene Heskett a écrit :
> > > Most recently on a stretch install on a rock64 I had to erect
> > > immutable attributes to resolv.conf after making it a real file, and
> > > e-n-i to make networking Just Work.
> >
> > /etc/resolv.conf is a rather different topic, because it is not
> > related to a specific interface and may be written by several pieces
> > of software, including but not limited to NetworkManager when
> > configuring *any* interface. I would suggest using resolvconf but I
> > suspect you would not like it either.
> Ohkaay, but where's the docs on this mysterious resolvconf?
> 
> What we do have is missing (wheezy) or horribly incomplete (jessie). 
> 
> But I'll have to take that back, my apologies. I just read the stretch 
> version on that rock64.  And as man pages go, its decent. And I'll have 
> to do some experimenting as its possible I can train it to behave.
> 
> And curious I blink compared the jessie vs stretch versions, stretch's is 
> both longer AND more complete, and two different authors and formatted 
> completely different. And wheezy doesn't even have the man page. I don't 
> even know if it should, maybe not for wheezy, lots of water has been 
> recycled since those installs were made, so I'll plead oldtimers.

This is very strange. I just did (in 80 column xterms):

$ man resolvconf > /tmp/resolvconf-stretch

and the same for jessie and wheezy on the appropriate computers.

$ diff /tmp/resolvconf-[sj]*
3,4d2
< 
< 
278d275
< 
295,296d291
< 
< 
$ 

so a few blank lines have been removed between jessie and stretch.
As for wheezy not having a man page:

$ wc /tmp/resolvconf-wheezy 
  301  1748 14876 /tmp/resolvconf-wheezy
$ cat /etc/debian_version 
7.11
$ dpkg -l resolvconf
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture   Description
+++-===-==-==-===
ii  resolvconf  1.67   allname server information 
handler
$ dpkg -L resolvconf | grep /man./
/usr/share/man/man8/resolvconf.8.gz
/usr/share/man/man5/interface-order.5.gz
$ 

So one can't help wondering exactly what is installed on your machines
if things don't match. Note that there are significant differences
between the different versions, so following the stretch/jessie man
page could give you problems on a wheezy machine. (I haven't checked
out backports.)

Cheers,
David.

Re: A reliable SIP registrar?

[Dan Ritter]

On Mon, Aug 27, 2018 at 10:52:35AM -0700, pe...@easthope.ca wrote:
> Hi,
> 
> For the Ekiga client in Debian, the Ekiga SIP registrar always works.  
> For other systems the Ekiga registrar can fail.  Mikhail Zabaluev  
> comments in https://sourceforge.net/p/sofia-sip/bugs/102/ at 
> 2009-06-08, "The restriction imposed by the proxy is arbitrary. It 
> does not follow any specification or best practice published by IETF 
> that I'm aware of."
> 
> Diamondcard.us works for any system I use but is paid gateway to the 
> PSTN.  Can anyone recommend a SIP registrar for general use beyond 
> Debian?
> 

Cheap but not free: voip.ms

-dsr-

Re: Curiositat sobre les IP assignades pels proveïdors

[Pau Ibars]

Igual de bé en el sentit "plug-and-play" segurament no, caldrà
configurar-hi les VLANs i el pppoe o el que sigui que fa que connecti amb
internet (compte, suposo que ha quedat clar que en cas aquest, això del
CG-NAT no es resoldria ni amb un router diferent), però a nivell de
rendiment, i microtalls o inclús latència segur que millora.

Salut!

Pau Ibars

Missatge de Orestes Mas  del dia dl., 27 d’ag. 2018 a
les 18:30:

> On 27/08/18 16:49, Pau Ibars wrote:
>
> Canvia de router, Eloi! Que de passada, tindràs millor rendiment. El
> hardware que posen els operadors semblen cafeteres!
>
> Pau Ibars
>
> Hola Pau,
>
> Creus que es pot canviar tranquil·lament de router garantint que un de
> genèric nou es connectarà igual de bé amb l'operadora?
>
> Cordialment,
>
> Orestes.
>
>
> Missatge de Eloi  del dia dl., 27 d’ag. 2018 a les
> 16:23:
>
>> El 27/8/18 a les 12:36, Orestes Mas ha escrit:
>> > Hola a tothom,
>> >
>> > Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
>> > ha trobat.
>> >
>> > Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
>> > per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
>> > amb el proveïdor antic i no tenia cap problema, però ara amb el router
>> > nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
>> > "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>> >
>> > Però com que no em funcionava m'hi he barallat una estona i al final
>> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>> > interna (una classe B, suposo, amb adreces de l'interval
>> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>> > compartides entre diversos usuaris.
>> >
>> > Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
>> > Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
>> > errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
>> > iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
>> > Suposo que funcionarà entre usuaris de la xarxa privada, però com que
>> > només són 65536 això no és massa esperançador...
>> >
>> > Orestes
>>
>> Has provat si només tens problemes amb el port 22 i no amb un
>> d'aleatori? La majoria de routers d'operadors que he vist tenen
>> precisament el port 22 (en models més antics, el 23... sí, telnet)
>> reservat i limitat a un rang d'IPs per a administració remota. En
>> particular, això ho fa Telefónica (Movistar). En models més antics sí
>> que podies arribar a tancar l'administració remota via SSH, però en
>> l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part superior
>> gris fosc i que engloba també el VoIP) això ja no és possible.
>>
>> La implicació de tot plegat és que el router, al final, l'acaba
>> controlant l'operador i no tu.
>>
>> D'altres operadors no puc parlar.
>>
>>
>>
>

A reliable SIP registrar?

[peter]

Hi,

For the Ekiga client in Debian, the Ekiga SIP registrar always works.  
For other systems the Ekiga registrar can fail.  Mikhail Zabaluev  
comments in https://sourceforge.net/p/sofia-sip/bugs/102/ at 
2009-06-08, "The restriction imposed by the proxy is arbitrary. It 
does not follow any specification or best practice published by IETF 
that I'm aware of."

Diamondcard.us works for any system I use but is paid gateway to the 
PSTN.  Can anyone recommend a SIP registrar for general use beyond 
Debian?

Thanks,... Peter E.
-- 
Message composed and transmitted by software designed to avoid the 
need, overhead and vulnerability of antivirus software.

123456789 123456789 123456789 123456789 123456789 123456789 123456789
Tel: +1 360 639 0202 
http://easthope.ca/Peter.html  Bcc: peter at easthope. ca

Re: [Buster]: Can't start X: no screens found(EE)

[Patrick Bartek]

On Mon, 27 Aug 2018 18:07:18 +0200 (CEST)
local10  wrote:

> Hi,
> 
> Am trying to upgrade a Debian Wheezy PC to Buster. The PC was
> successfully running Wheezy with KDE as desktop, in terms of hardware
> there are no changes. Initially, sddm was intalled to start KDE but
> that did not work for some reason, so now I starting KDE manually
> with startx.
> 
> Any ideas? Thanks
> 
> [snip]

Yes. Did you read and follow the instructions for distribution
upgrading? (Probably not) Was your dist-upgrade path wheezy -> jessie
-> stretch -> buster? (Probably not). Or did you just change wheezy's
apt's sources.list to buster's, then apt-get update; apt-get
dist-upgrade? (Probably, yes). Hence, the SNAFU.

I suggest you don't waste anymore time trying to fix things, just back
up your data and other important files, do a clean install of
stretch and following the instructions, of course, dist-upgrade to
buster. This is the recommended "safe" procedure by Debian instead of
using buster's current installer which is still in alpha. It's all in
the instructions.

B

Re: Curiositat sobre les IP assignades pels proveïdors

[Iker Bilbao]

Per als modem de fibra la recomanació és posar-lo en modo bridge (aprofitar
només l ONT, q només faci de modem) i tenir la IP pública a un router
darrera.
El rendiment i estabilitat millor molt, de forma notable.

Iker.

El lun., 27 ago. 2018 20:17, Eloi  escribió:

> (cadena de cites reordenada)
>
> El 27/8/18 a les 18:38, Pere Nubiola Radigales ha escrit:
>
>
> El dl., 27 d’ag. 2018, 18:30, Orestes Mas  va
> escriure:
>
>> On 27/08/18 16:49, Pau Ibars wrote:
>>
>> Canvia de router, Eloi! Que de passada, tindràs millor rendiment. El
>> hardware que posen els operadors semblen cafeteres!
>>
>> Pau Ibars
>>
>> Hola Pau,
>>
>> Creus que es pot canviar tranquil·lament de router garantint que un de
>> genèric nou es connectarà igual de bé amb l'operadora?
>>
>> Cordialment,
>>
>> Orestes.
>>
>> Jo fair servir un asus i va perfecte, amb tele i tot. L'únic es que amb
> movistar.
>
>> Pels routers ADSL sens dubte, el blanc de Telefónica que donaven anys
> enrere era una castanya, després de canviar-lo dos cops per mal
> funcionament i veient que el tercer anava igual o pitjor, al final vaig
> arreplegar un model bastant més antic també de Telefónica però que
> funcionava la mar de bé i, sobretot, no tenia res capat.
>
> El que tinc ara de fibra no va malament, i tampoc sé fins a quin punt
> seria prudent canviar el router que no només em dóna Internet sinó
> telèfon... també val a dir que em connecto amb Ethernet, i de fet el primer
> que vaig fer va ser apagar el wifi, puix no l'uso.
>
> A casa els meus pares sí que la història és diferent: el router és un
> model més antic (també blanc, d'aspecte similar al que deia d'ADSL, però
> enorme) i la senyal va per wifi perquè l'ordinador està a l'altra punta de
> casa, allà cada dos per tres hi ha talls però vés a saber qui n'és el
> responsable (el router, el receptor wifi, les parets de la casa o el motor
> de l'ascensor que està a 3m en línia recta), allà el que haig de fer és
> tirar cable Ethernet, però sempre dic "ja ho faré" i mai ho acabo fent ¬¬'
>

Targeted Global B2B Companies emails list

[sandra . wood]

Hi,

I just wanted to check if you would be interested in a list of Managed  
Service Providers (MSPs) and Managed Security Service Providers (MSSPs)?


We also have the data intelligence of:

•   Managed Service Providers (MSP’s) – 25,000 unique companies
•   Managed Security Service Providers (MSSP’s) – 7,520 unique companies
•   IT Decision Makers – 6million across all industry
•   Business Decision Makers – 10 million across all industry
•   Value Added Resellers- VARs
•   Independent Software Vendors- ISVs
•   System Integrators- SIs
•   VoIP Service Providers.
•   Telecommunications Service Providers (TSPs)
•   Application Service Providers (ASPs)
•   IT Managed Services Providers (ITMSP)
•   Storage Service Providers (SSPs)

Kindly review and let me know if I can share more information on this.

I look forward to hearing from you.

Regards,
Sandra
Marketing Specialist

If you don't want to include yourself in our mailing list, please reply  
back “Leave Out" in a subject line.

Re: canvis en el su.

[Eloi]

El 27/8/18 a les 16:58, Pere Nubiola Radigales ha escrit:
> Algú sap el perqué del canvis del su?
> .
> Fins ara amb la crida su es reinicialitzaba el path  amb el del usuari
> root, mantenint la resta del entorn.
> Ara si vols el path de root, necessites fer su -, reinicialitzant tot
> l'entorn.
>
> Pere Nubiola Radigales
> Telf: +34 656316974
> e-mail: p...@nubiola.cat 
>            pnubi...@fsfe.org 
>            pere.nubi...@gmail.com 
>
Enganxo la nota enviada per apt-listchanges al correu local explicant el
canvi

util-linux (2.32-0.4) unstable; urgency=medium

  The util-linux implementation of /bin/su is now used, replacing the
  one previously supplied by src:shadow (shipped in login package), and
  bringing Debian in line with other modern distributions. The two
  implementations are very similar but have some minor differences (and
  there might be more that was not yet noticed ofcourse), e.g.

  - new 'su' (with no args, i.e. when preserving the environment) also
    preserves PATH and IFS, while old su would always reset PATH and IFS
    even in 'preserve environment' mode.
  - su '' (empty user string) used to give root, but now returns an error.
  - previously su only had one pam config, but now 'su -' is configured
    separately in /etc/pam.d/su-l

  The first difference is probably the most user visible one. Doing
  plain 'su' is a really bad idea for many reasons, so using 'su -' is
  strongly recommended to always get a newly set up environment similar
  to a normal login. If you want to restore behaviour more similar to
  the previous one you can add 'ALWAYS_SET_PATH yes' in /etc/login.defs.

 -- Andreas Henriksson   Fri, 03 Aug 2018 10:52:22 +0200

Re: sometimes i go huh (grep result)

[Joe Pfeiffer]

What's tripping you up is that some processing is being done by the
shell before grep ever sees your pattern.  Taking that into account,
what grep is seeing is:

songbird  writes:

> me@ant(25)$ env | grep -F "-g"
grep -F -g
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(26)$ env | grep -F '-g'
grep -F -g
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(27)$ env | grep -F 'CFL'
> CFLAGS=-g
grep -F CFL
> me@ant(28)$ env | grep '\-g'
> CFLAGS=-g
grep \-g
(I'll note that in this case you need the quotes or the shell would have
stripped the \ .  I'm guessing this one is doing what you want)
> me@ant(29)$ env | grep '-g'
grep -g
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(30)$ env | grep "-g"
grep -g
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
>
>
> songbird

Re: canvis en el su.

[Josep Lladonosa]

Ha canviat, sí, ja que han canviat de binari "su" i actua diferent.

Solució:
Afegir a /etc/login.defs: ALWAYS_SET_PATH yes

Remenant vaig trobar això relativament relacionat:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905564

On Mon, 27 Aug 2018, 16:58 Pere Nubiola Radigales,  wrote:

> Algú sap el perqué del canvis del su?
> .
> Fins ara amb la crida su es reinicialitzaba el path  amb el del usuari
> root, mantenint la resta del entorn.
> Ara si vols el path de root, necessites fer su -, reinicialitzant tot
> l'entorn.
>
> Pere Nubiola Radigales
> Telf: +34 656316974
> e-mail: p...@nubiola.cat
>pnubi...@fsfe.org
>pere.nubi...@gmail.com
>
>

Re: linux 4.19 scsi-mq default?

[Reco]

Hi.

On Sun, Aug 26, 2018 at 07:47:54PM -0400, Boyan Penkov wrote:
> Hello folks,
> 
> Likely not the exact right list to ask, but likely someone here knows — did 
> scsi-mq by default make it into linux 4.19?
> 
> http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224.htm

4.19-rc1 has SCSI_MQ_DEFAULT defined as "y" - [1].
Whenever they build it in Debian that way remains to be seen.

Reco

[1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/scsi/Kconfig?h=v4.19-rc1

Re: processing order for configuration files in /etc/network/interfaces.d

[Reco]

Hi.

On Mon, Aug 27, 2018 at 11:46:37AM -0500, David Wright wrote:
> On Mon 27 Aug 2018 at 19:24:01 (+0300), Reco wrote:
> > Hi.
> > 
> > On Mon, Aug 27, 2018 at 12:01:23PM -0400, Greg Wooledge wrote:
> > > On Mon, Aug 27, 2018 at 06:41:25PM +0300, Reco wrote:
> > > > Last sentence says to me that wordexp output should be always sorted.
> > > 
> > > This only tells us that it *reads* the config files in glob-sorted order.
> > > And peeking into the actual source code of ifupdown, yes, it appears to
> > > do this.  (File config.c starting at line 436, in the stretch source.)
> > > It even uses wordexp() as advertised.
> > > 
> > > What's less clear to me at this moment is what happens *after* the
> > > interface configuration file(s) have been read into memory.
> > > 
> > > Moving over to main.c, it looks like it reads the interfaces (line 639),
> > > and that function was called from line 1190.  After line 1190, it loops
> > > over the "target_iface" array, and processes them in the order they appear
> > > in that array.
> > > 
> > > So... next question is how they get packed into that array.
> > > 
> > > Returning to the select_interfaces function, it looks like the ordering
> > > is created by a call to find_allowup.
> > > 
> > > And... this is where I stopped reading, because it got confusing.  Maybe
> > > someone else can take a stab at deciphering that part.
> > 
> > select_interfaces() is called on "ifup -a" invocation.
> > read_interfaces() is called by it.
> > read_interfaces() calls read_interfaces_defn().
> > read_interfaces_defn() parses "iface" and "source" directives, and calls
> > read_interfaces_defn() once again on each file specified by "source" in
> > order defined by wordexp(3).
> > 
> > Therefore defn[] array should be filled in this order (assuming that one
> > specifies "source" only at /e/n/i):
> > 
> > 1) any interface definition at /e/n/i in order encountered, until
> > "source" directive.
> > 2) any interface definition provided by "source" directive in order
> > defined by wordexp(3).
> > 3) any interface definition at /e/n/i in order encountered, after the
> > "source" directive.
> > 
> > I'd use ltrace(1) to check it, but building test environment is
> > something that I lack the time to do.
> 
> That's still the order in which the stanzas are read. Don't we now
> need to know what the contents of each stanza is, ie is it an "auto"
> or an "allow-hotplug" stanza, etc?

I simplified things. After defn[] is filled at read_interfaces(),
find_allowup() is called, defn[] being the first argument.
find_allowup() iterates on defn[], using a pointer to defn->allowups.
defn->allowups, unless I'm reading it wrong, is filled by the same
read_interfaces_defn(), in the same order that /e/n/i and "source" are
evaluated.
This filling is done by add_allow_up() each time one specifies "auto" or
"allow-" stanzas.

Reco

Re: mailing list vs "the futur"

[David Wright]

On Mon 27 Aug 2018 at 11:37:48 (-0400), Gene Heskett wrote:
> On Monday 27 August 2018 11:11:37 David Wright wrote:
> 
> > On Sat 25 Aug 2018 at 14:27:38 (-0500), John Hasler wrote:
> > > David writes:
> > > > Or are you talking about some type of "shared channel" of which I
> > > > have no knowledge?
> > >
> > > Cable providers may have a great many customers on a single cable
> > > with large (but limited) bandwidth.
> >
> > Oh, like me, you mean. When we wanted to get our cable strung from the
> > pole with the least obstructed view of our house, the linesman first
> > told us that all the terminations were taken, but on ringing the
> > office, he found that one line was not subscribed to, so we were able
> > to connect to that pole. When I walk down the back alleys, I can see
> > other poles connected to the same main coax feed that links the poles.
> >
> > I'm still scratching my head why subscribing to NNTP newsgroups should
> > lead to bandwidth problems rather than usage ones. I can hit my
> > bandwidth limits in many other ways like downloading youtube videos,
> > watching TV, etc, but the hard limit is my usage, where I would end up
> > paying money for any excess.
> >
> That bandwidth limit is not on your side of the isp, its the bandwidth 
> from the main trunk lines to the isp. NNTP is a huge bandwidth hog 
> regardless of how much of it your isp accepts for spooling on local disk 
> to serve you.

I didn't know they were asking the ISP to *host* the newsgroups,
just to allow NNTP stuff to pass from whoever is hosting it to
the user, who pays for the usage they make of it.

> > > Some rural providers may have limited backhaul bandwidth.  They make
> > > promises to customers based on optimistic estimates of peak usage.
> Here at least, thats gradually getting better.

I read that improvements are very patchy in the US.

> > Now it appears that you're using "usage" where I would write
> > "bandwidth". Am I in a minority of one here? Bandwidth is the rate of
> > transfer of bits, whereas usage is the quantity of bits transferred
> > irrespective of how fast they accumulated.
> 
> Thats a pretty good view of the differences.

But I get the impression that we have another baud/bitrate muddle.

Cheers,
David.

VPS and network traffic

[Nick]

This isn't strictly a debian issue but perhaps there are enough people
here running debian on VPSs that someone can explain...

I configured monit on a low traffic 'stretch' VPS to alert me about
upload or downloads that exceed 1.2MB in a ten minute period.  For
uploads it works.  For downloads it doesn't because monit sees
downloads continuously at a rate of about 6MB per 10m (it fluctuates
around there in range of typically 1 - 2MB).

I ran 'nethogs' and saw an unexpected (to me) result.  nethogs reports
bandwidth between ip addresses where neither address is on my VPS.
For example (reformatted and with the addresses changed),

   PID USERPROGRAM
   ?   root90.94.130.147:80-47.35.225.43:33034

   DEVSENT  RECEIVED
  0.000  1.285 KB/sec

Whenever I've checked, 'whois' reports one or both ip addressses as
belonging to my VPS provider.  nethogs reports dozens of lines like
this at a time, i.e. with alien ips, no PID and no DEV.  (nethogs has
a switch for "sniff in promiscious mode" which I didn't use).  I asked
my VPS provider what was going on and in summary they said

   It seems we've a small number of packets being broadcast by the
   switch/host
   It's not an urgent priority, as it's not directly an error (a switch
   is allowed to behave as a hub).
   We only bill for traffic that leaves our network so it makes no
   difference to your quota.

I'm not a networking expert so I'm willing to take their word for it.
Sadly for me it seems to mean I can't monitor my own download traffic
accurately due to this unwanted 'background noise'.  My questions
are...

Are these broadcast packets the culprit for monit thinking I'm
downloading so much?

Why is the linux kernel seeing broadcast packets as downloads to my
VPS?

Or is monit (which I guess gets its numbers from the kernel) looking
at the wrong thing?

Is there a way to stop those packets contributing to what monit sees
as download traffic?

Thanks
-- 
Nick

Re: processing order for configuration files in /etc/network/interfaces.d

[David Wright]

On Mon 27 Aug 2018 at 19:24:01 (+0300), Reco wrote:
>   Hi.
> 
> On Mon, Aug 27, 2018 at 12:01:23PM -0400, Greg Wooledge wrote:
> > On Mon, Aug 27, 2018 at 06:41:25PM +0300, Reco wrote:
> > > Last sentence says to me that wordexp output should be always sorted.
> > 
> > This only tells us that it *reads* the config files in glob-sorted order.
> > And peeking into the actual source code of ifupdown, yes, it appears to
> > do this.  (File config.c starting at line 436, in the stretch source.)
> > It even uses wordexp() as advertised.
> > 
> > What's less clear to me at this moment is what happens *after* the
> > interface configuration file(s) have been read into memory.
> > 
> > Moving over to main.c, it looks like it reads the interfaces (line 639),
> > and that function was called from line 1190.  After line 1190, it loops
> > over the "target_iface" array, and processes them in the order they appear
> > in that array.
> > 
> > So... next question is how they get packed into that array.
> > 
> > Returning to the select_interfaces function, it looks like the ordering
> > is created by a call to find_allowup.
> > 
> > And... this is where I stopped reading, because it got confusing.  Maybe
> > someone else can take a stab at deciphering that part.
> 
> select_interfaces() is called on "ifup -a" invocation.
> read_interfaces() is called by it.
> read_interfaces() calls read_interfaces_defn().
> read_interfaces_defn() parses "iface" and "source" directives, and calls
> read_interfaces_defn() once again on each file specified by "source" in
> order defined by wordexp(3).
> 
> Therefore defn[] array should be filled in this order (assuming that one
> specifies "source" only at /e/n/i):
> 
> 1) any interface definition at /e/n/i in order encountered, until
> "source" directive.
> 2) any interface definition provided by "source" directive in order
> defined by wordexp(3).
> 3) any interface definition at /e/n/i in order encountered, after the
> "source" directive.
> 
> I'd use ltrace(1) to check it, but building test environment is
> something that I lack the time to do.

That's still the order in which the stanzas are read. Don't we now
need to know what the contents of each stanza is, ie is it an "auto"
or an "allow-hotplug" stanza, etc?

Cheers,
David.

Cannot Install/Uninstall sendmail

[Luis Finotti]

Hi everyone,

I'm having trouble installing/removing sendmail in Debian Sid (well,
aptosid -- http://www.aptosid.com -- actually).

I tried to install and it failed: https://pastebin.com/Qu2jRqsn

'apt -f install' did not fix it, nor did 'dpkg --configure -a'.

Since it was not essential (and did not install correctly), I tried to
uninstall it, but it also fails:

-
# apt remove procmail sendmail sendmail-base sendmail-bin sendmail-cf
sensible-mda
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  procmail sendmail sendmail-base sendmail-bin sendmail-cf sensible-mda
0 upgraded, 0 newly installed, 6 to remove and 2 not upgraded.
4 not fully installed or removed.
After this operation, 4,213 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 1537409 files and directories currently installed.)
Removing sendmail (8.15.2-11) ...
Removing sensible-mda (8.15.2-11) ...
Removing sendmail-bin (8.15.2-11) ...
Removing sendmail-base (8.15.2-11) ...
update-inetd: error: --group is only relevant with --add
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned
error exit status 255
Removing procmail (3.22-26) ...
Removing sendmail-cf (8.15.2-11) ...
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)


One notices in the failed install attempt (the pastebin link above):

--
adduser: Warning: The home directory `/var/lib/sendmail' does not belong to
the user you are currently creating.
update-inetd: warning: cannot add service, /etc/inetd.conf does not exist
--

I had:
--
# ls -ld /var/lib/sendmail
drwx-- 2 smmta smmta 4096 Aug 22 15:06 /var/lib/sendmail/
--

Changing ownership to root did not allow me to uninstall it.

Aptosid itself does not come with a mail daemon installed, so I must have
installed at some point some daemon that created the /var/lib/sendmail.
(If I were to try to install again, I'd probably opt for a lighter
alternative, something like ssmtp.  So, right now, I just want to remove
sendmail.)  So, I have sendmail-base stuck as not fully installed.

It was recommended I install 'openbsd-inetd' (it was not installed, neither
was xinetd), but it still fails to install: https://pastebin.com/sStYqMYi
(I also still cannot uninstall it...)

Any help would be greatly appreciated!

Re: Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

On 27/08/18 14:53, Jordi Miguel wrote:
> Hola Orestes,
>
> El que comentes que fa el teu proveïdor s'anomena "Carrier-grade NAT"
> i és una pràctica que s'ha estès bastant degut a l'esgotament de les
> adreces IPv4. Es d'esperar que quan lo habitual sigui IPv6 aquests
> proveïdors tornaran a donar IPs públiques als seus usuaris.
> En quant a obrir ports per poder accedir a serveis que tinguis a les
> teves màquines internes des de Internet ho tens bastant negre.
> Bàsicament les solucions passen per obtenir una adreça IP pública que
> si que puguis controlar i utilitzar-la per publicar els serveis als
> que vols accedir des d'Internet. Possibles solucions:
> - Obtenir una adreça d'un proveïdor de VPN que suporti publicar serveis.
> - Si el teu proveïdor tmb t'esta donant una IPv6, i si aquesta és
> pública (això segon seria bastant probable) utilitzar-la per publicar
> els teus serveis. L'únic "desavantatge" és que els usuaris que només
> tinguin un accés IPv4 no podran accedir directament als teus serveis,
> hauran d'utilitzar miredo o altres solucions.
> - Si disposes d'un servidor amb IP pública fer un tunel entre la teva
> màquina i la màquina externa i publicar els serveis utilitzant la IP
> del servidor públic. (algo similar a lo que s'explica aquí [1])
Si, les solucions al problema més o menys les tinc clares. De fet tinc
la sort de disposar a la feina (UPC) una màquina permanentment engegada
amb una IP pública, i ja utilitzo un túnel ssh amb una màquina per una
qüestió molt diferent.

El que no era conscient és que ara s'ha posat de moda de fer NAT a
nivell d'operadora. Ho trobo un abús fer-ho sense informar, ja que
trenca coses que donaves per suposades anteriorment.

Miraré de queixar-me, a veure si ho solvento. Gràcies de nou.

Cordialment,
Orestes
>
> Espero que aquesta informació et serveixi d'alguna cosa.
>
> Per cert, estic molt d'acord amb el Pedro que els proveïdors haurien
> de deixar ben clar si la connexió que contractes està darrera un NAT o
> no. Desconec si el teu proveïdor ha deixat clara aquesta informació
> abans d'adquirir el producte, tanmateix donat que hi ha ISPs que no ho
> diuen fóra bó disposar d'una llista pública on els usuaris puguin
> consultar aquesta informació abans de contractar res.
>
>
> [1] https://amoss.me/2017/05/port-forwarding-behind-a-carrier-grade-nat/
>
> Fins aviat,
> Jordi
> --
> Para ser realmente grande, hay que estar con la gente, no por encima de ella.
> El lun., 27 ago. 2018 a las 13:42, Orestes Mas () 
> escribió:
>> Hola a tothom,
>>
>> Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
>> ha trobat.
>>
>> Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
>> per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
>> amb el proveïdor antic i no tenia cap problema, però ara amb el router
>> nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
>> "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>>
>> Però com que no em funcionava m'hi he barallat una estona i al final
>> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>> interna (una classe B, suposo, amb adreces de l'interval
>> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>> compartides entre diversos usuaris.
>>
>> Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
>> Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
>> errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
>> iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
>> Suposo que funcionarà entre usuaris de la xarxa privada, però com que
>> només són 65536 això no és massa esperançador...
>>
>> Orestes
>>
>>

Re: Curiositat sobre les IP assignades pels proveïdors

[Pere Nubiola Radigales]

Jo fair servir un asus i va perfecte, amb tele i tot. L'únic es que amb
movistar.

El dl., 27 d’ag. 2018, 18:30, Orestes Mas  va escriure:

> On 27/08/18 16:49, Pau Ibars wrote:
>
> Canvia de router, Eloi! Que de passada, tindràs millor rendiment. El
> hardware que posen els operadors semblen cafeteres!
>
> Pau Ibars
>
> Hola Pau,
>
> Creus que es pot canviar tranquil·lament de router garantint que un de
> genèric nou es connectarà igual de bé amb l'operadora?
>
> Cordialment,
>
> Orestes.
>
>
> Missatge de Eloi  del dia dl., 27 d’ag. 2018 a les
> 16:23:
>
>> El 27/8/18 a les 12:36, Orestes Mas ha escrit:
>> > Hola a tothom,
>> >
>> > Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
>> > ha trobat.
>> >
>> > Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
>> > per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
>> > amb el proveïdor antic i no tenia cap problema, però ara amb el router
>> > nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
>> > "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>> >
>> > Però com que no em funcionava m'hi he barallat una estona i al final
>> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>> > interna (una classe B, suposo, amb adreces de l'interval
>> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>> > compartides entre diversos usuaris.
>> >
>> > Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
>> > Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
>> > errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
>> > iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
>> > Suposo que funcionarà entre usuaris de la xarxa privada, però com que
>> > només són 65536 això no és massa esperançador...
>> >
>> > Orestes
>>
>> Has provat si només tens problemes amb el port 22 i no amb un
>> d'aleatori? La majoria de routers d'operadors que he vist tenen
>> precisament el port 22 (en models més antics, el 23... sí, telnet)
>> reservat i limitat a un rang d'IPs per a administració remota. En
>> particular, això ho fa Telefónica (Movistar). En models més antics sí
>> que podies arribar a tancar l'administració remota via SSH, però en
>> l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part superior
>> gris fosc i que engloba també el VoIP) això ja no és possible.
>>
>> La implicació de tot plegat és que el router, al final, l'acaba
>> controlant l'operador i no tu.
>>
>> D'altres operadors no puc parlar.
>>
>>
>>
>

Re: [Buster]: Can't start X: no screens found(EE)

[Felix Miata]

local10 composed on 2018-08-27 18:07 (UTC+0200):

> # grep "(EE)" .local/share/xorg/Xorg.0.log
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [  1102.702] (EE) open /dev/dri/card0: No such file or directory
> [  1102.702] (EE) open /dev/dri/card0: No such file or directory
> [  1102.703] (EE) Unable to find a valid framebuffer device
> [  1102.703] (EE) open /dev/fb0: No such file or directory

These suggest you are missing a firmware package for your Radeon HD 4200.
firmware-linux & firmware-linux-non-free are meta packages. Likely you only need
firmware-amd-graphics and/or firmware-linux-free and/or firmware-misc-nonfree.
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

On 27/08/18 16:49, Pau Ibars wrote:
> Canvia de router, Eloi! Que de passada, tindràs millor rendiment. El
> hardware que posen els operadors semblen cafeteres!
>
> Pau Ibars
Hola Pau,

Creus que es pot canviar tranquil·lament de router garantint que un de
genèric nou es connectarà igual de bé amb l'operadora?

Cordialment,

Orestes.

>
> Missatge de Eloi mailto:entfe...@gmail.com>> del
> dia dl., 27 d’ag. 2018 a les 16:23:
>
> El 27/8/18 a les 12:36, Orestes Mas ha escrit:
> > Hola a tothom,
> >
> > Observo un fenomen curiós, i m'agradaria saber si algú de
> vosaltres s'hi
> > ha trobat.
> >
> > Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del
> router
> > per poder accedir des de fora via ssh a un ordinador. Això ja ho
> feia
> > amb el proveïdor antic i no tenia cap problema, però ara amb el
> router
> > nou no em funcionava. La IP pública, segons m'indiquen webs del
> tipus
> > "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
> >
> > Però com que no em funcionava m'hi he barallat una estona i al final
> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> > interna (una classe B, suposo, amb adreces de l'interval
> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces
> públiques
> > compartides entre diversos usuaris.
> >
> > Les preguntes: Us heu trobat que el proveïdor d'internet faci
> NAT també?
> > Sabeu si com a usuaris ens podem queixar (ja imagino que no...)?
> Vaig
> > errat si dedueixo que això impedirà que funcioni qualsevol accés
> a casa
> > iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
> > Suposo que funcionarà entre usuaris de la xarxa privada, però
> com que
> > només són 65536 això no és massa esperançador...
> >
> > Orestes
>
> Has provat si només tens problemes amb el port 22 i no amb un
> d'aleatori? La majoria de routers d'operadors que he vist tenen
> precisament el port 22 (en models més antics, el 23... sí, telnet)
> reservat i limitat a un rang d'IPs per a administració remota. En
> particular, això ho fa Telefónica (Movistar). En models més antics sí
> que podies arribar a tancar l'administració remota via SSH, però en
> l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part
> superior
> gris fosc i que engloba també el VoIP) això ja no és possible.
>
> La implicació de tot plegat és que el router, al final, l'acaba
> controlant l'operador i no tu.
>
> D'altres operadors no puc parlar.
>
>

Re: mailing list vs "the futur"

[Dan Ritter]

On Mon, Aug 27, 2018 at 11:37:48AM -0400, Gene Heskett wrote:
> 
> That bandwidth limit is not on your side of the isp, its the bandwidth 
> from the main trunk lines to the isp. NNTP is a huge bandwidth hog 
> regardless of how much of it your isp accepts for spooling on local disk 
> to serve you.
> 

This is not the case.

The NNTP server-to-server algorithm is analogous to rsync,
if you think of:

- each message is a file
- each newsgroup is a directory
- if the receiver doesn't have a directory, it won't be
  sync'd over from the sender
- the sender/receiver don't bother looking at contents
  of each file to decide whether to update, just the name-timestamp

And it always goes in exactly one direction; when the receiver
wants to send messages back upstream, that's a different
connection in which they swap places.

NNTP is a bandwidth hog in exactly the same proportion as the
space it occupies on disk.

I have simplified for the sake of a familiar analogy.

-dsr-

Re: Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

On 27/08/18 16:22, Eloi wrote:
> El 27/8/18 a les 12:36, Orestes Mas ha escrit:
>> Hola a tothom,
>>
>> Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
>> ha trobat.
>>
>> Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
>> per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
>> amb el proveïdor antic i no tenia cap problema, però ara amb el router
>> nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
>> "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>>
>> Però com que no em funcionava m'hi he barallat una estona i al final
>> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>> interna (una classe B, suposo, amb adreces de l'interval
>> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>> compartides entre diversos usuaris.
>>
>> Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
>> Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
>> errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
>> iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
>> Suposo que funcionarà entre usuaris de la xarxa privada, però com que
>> només són 65536 això no és massa esperançador...
>>
>> Orestes
> Has provat si només tens problemes amb el port 22 i no amb un
> d'aleatori? La majoria de routers d'operadors que he vist tenen
> precisament el port 22 (en models més antics, el 23... sí, telnet)
> reservat i limitat a un rang d'IPs per a administració remota. En
> particular, això ho fa Telefónica (Movistar). En models més antics sí
> que podies arribar a tancar l'administració remota via SSH, però en
> l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part superior
> gris fosc i que engloba també el VoIP) això ja no és possible.
>
> La implicació de tot plegat és que el router, al final, l'acaba
> controlant l'operador i no tu.
>
> D'altres operadors no puc parlar.
Hola Eloi,

Això que dius ho descarto en el meu cas: He provat de fer port
forwarding amb el 22 i també el , amb igual resultat.
A més, he comprovat realment que la IP pública reportada per serveis web
i la IP que el router indica que té com a "pública" no coincideixen.

Ara bé, això de l'administració remota ja sembla més plausible: un nmap
mostra el port 23 (!) obert (i servidor telnet actiu), sense que sigui
cosa meva. Seran fillsde!!

Orestes.

Re: processing order for configuration files in /etc/network/interfaces.d

[Reco]

Hi.

On Mon, Aug 27, 2018 at 12:01:23PM -0400, Greg Wooledge wrote:
> On Mon, Aug 27, 2018 at 06:41:25PM +0300, Reco wrote:
> > Last sentence says to me that wordexp output should be always sorted.
> 
> This only tells us that it *reads* the config files in glob-sorted order.
> And peeking into the actual source code of ifupdown, yes, it appears to
> do this.  (File config.c starting at line 436, in the stretch source.)
> It even uses wordexp() as advertised.
> 
> What's less clear to me at this moment is what happens *after* the
> interface configuration file(s) have been read into memory.
> 
> Moving over to main.c, it looks like it reads the interfaces (line 639),
> and that function was called from line 1190.  After line 1190, it loops
> over the "target_iface" array, and processes them in the order they appear
> in that array.
> 
> So... next question is how they get packed into that array.
> 
> Returning to the select_interfaces function, it looks like the ordering
> is created by a call to find_allowup.
> 
> And... this is where I stopped reading, because it got confusing.  Maybe
> someone else can take a stab at deciphering that part.

select_interfaces() is called on "ifup -a" invocation.
read_interfaces() is called by it.
read_interfaces() calls read_interfaces_defn().
read_interfaces_defn() parses "iface" and "source" directives, and calls
read_interfaces_defn() once again on each file specified by "source" in
order defined by wordexp(3).

Therefore defn[] array should be filled in this order (assuming that one
specifies "source" only at /e/n/i):

1) any interface definition at /e/n/i in order encountered, until
"source" directive.
2) any interface definition provided by "source" directive in order
defined by wordexp(3).
3) any interface definition at /e/n/i in order encountered, after the
"source" directive.

I'd use ltrace(1) to check it, but building test environment is
something that I lack the time to do.

Reco

Re: Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

On 27/08/18 14:17, Jordi Miguel wrote:
> Hola,
>
> Aquesta resposta sobre les IP's privades no es del tot precisa.
> Existeixen més rangs que no s'enruten a Internet. Entre ells el rang
> que comenta l'Orestes i que pertany al següent RFC:
> https://tools.ietf.org/html/rfc6598
> Si mireu el RFC veureu que es un rang que es va crear precisament per
> fer el que l'Orestes ha detectat en la seva connexió.
>
> D'altre banda, et confirmo que efectivament no és el primer proveïdor
> d'Internet que utilitza NAT amb els seus usuaris.
>
>
> Salutacions,
> Jordi
Hola Jordi. Gràcies per confirmar les meves sospites. Ets un pou de
ciència i d'informació :-)

Orestes.

> --
> Para ser realmente grande, hay que estar con la gente, no por encima de ella.
> El lun., 27 ago. 2018 a las 14:04, Pedro () escribió:
>>> Però com que no em funcionava m'hi he barallat una estona i al final
>>> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>>> interna (una classe B, suposo, amb adreces de l'interval
>>> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>>> compartides entre diversos usuaris.
>> Els prefixos de xarxa privada són:
>>
>>  10.0.0.0-   10.255.255.255  (10/8 prefix)
>>  172.16.0.0  -   172.31.255.255  (172.16/12 prefix)
>>  192.168.0.0 -   192.168.255.255 (192.168/16 prefix)
>>
>> https://tools.ietf.org/html/rfc1918
>>
>>
>> podria ser que el proveïdor bloqueja port 22, per què no proves un altre?
>>
>> fora bo que ens diguis de quin proveïdor es tracta i així ens animarem
>> a posar-lo en les nostres whitelists o blacklists personals
>>

Re: sometimes i go huh (grep result)

[Roberto C . Sánchez]

On Mon, Aug 27, 2018 at 11:26:12AM -0400, Greg Wooledge wrote:
> On Mon, Aug 27, 2018 at 11:20:42AM -0400, Roberto C. Sánchez wrote:
> > env |grep [-]g
> 
> Fails if there is a file named -g in the current directory, as that
> matches the unquoted glob and causes it to expand.  Also fails if failglob
> is turned on, whether the file exists or not (fails differently in the
> two cases).
> 
> Also fails if nullglob is turned on, but that is definitely not
> recommended in interactive shells.
> 
Quite right.  In my haste I forgot the quotes:

env |grep '[-]g'

-- 
Roberto C. Sánchez

Re: [Buster]: Can't start X: no screens found(EE)

[local10]

Attached the correct log file. 
[  1102.295] 
X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
[  1102.295] Build Operating System: Linux 4.9.0-7-amd64 x86_64 Debian
[  1102.295] Current Operating System: Linux tstsrv 4.17.0-3-amd64 #1 SMP 
Debian 4.17.17-1 (2018-08-18) x86_64
[  1102.295] Kernel command line: BOOT_IMAGE=/vmlinuz-4.17.0-3-amd64 
root=UUID=24f9d82e-e43a-6cd8-c1f8-ecd8817e0352 ro quiet
[  1102.296] Build Date: 17 August 2018  08:05:00PM
[  1102.296] xorg-server 2:1.20.1-1 (https://www.debian.org/support) 
[  1102.296] Current version of pixman: 0.34.0
[  1102.296]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[  1102.296] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1102.297] (==) Log file: "/home/luser/.local/share/xorg/Xorg.0.log", Time: 
Mon Aug 27 10:32:54 2018
[  1102.338] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[  1102.382] (==) No Layout section.  Using the first Screen section.
[  1102.382] (==) No screen section available. Using defaults.
[  1102.382] (**) |-->Screen "Default Screen Section" (0)
[  1102.382] (**) |   |-->Monitor ""
[  1102.384] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[  1102.384] (==) Automatically adding devices
[  1102.384] (==) Automatically enabling devices
[  1102.384] (==) Automatically adding GPU devices
[  1102.384] (==) Max clients allowed: 256, resource mask: 0x1f
[  1102.406] (WW) `fonts.dir' not found (or not valid) in 
"/usr/share/fonts/X11/misc".
[  1102.406]Entry deleted from font path.
[  1102.406](Run 'mkfontdir' on "/usr/share/fonts/X11/misc").
[  1102.406] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[  1102.406]Entry deleted from font path.
[  1102.406] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[  1102.406]Entry deleted from font path.
[  1102.406] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[  1102.406]Entry deleted from font path.
[  1102.407] (WW) The directory "/usr/share/fonts/X11/Type1" does not exist.
[  1102.407]Entry deleted from font path.
[  1102.407] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist.
[  1102.407]Entry deleted from font path.
[  1102.407] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist.
[  1102.407]Entry deleted from font path.
[  1102.407] (==) FontPath set to:
built-ins
[  1102.407] (==) ModulePath set to "/usr/lib/xorg/modules"
[  1102.407] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[  1102.407] (II) Loader magic: 0x55d6a99f5de0
[  1102.407] (II) Module ABI versions:
[  1102.407]X.Org ANSI C Emulation: 0.4
[  1102.407]X.Org Video Driver: 24.0
[  1102.407]X.Org XInput driver : 24.1
[  1102.407]X.Org Server Extension : 10.0
[  1102.408] (++) using VT number 2

[  1102.413] (II) systemd-logind: took control of session 
/org/freedesktop/login1/session/_34
[  1102.418] (--) PCI:*(1@0:5:0) 1002:9710:1458:d000 rev 0, Mem @ 
0xd000/268435456, 0xfdfe/65536, 0xfde0/1048576, I/O @ 
0xee00/256, BIOS @ 0x/131072
[  1102.418] (II) LoadModule: "glx"
[  1102.436] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[  1102.497] (II) Module glx: vendor="X.Org Foundation"
[  1102.497]compiled for 1.20.1, module version = 1.0.0
[  1102.497]ABI class: X.Org Server Extension, version 10.0
[  1102.497] (==) Matched ati as autoconfigured driver 0
[  1102.497] (==) Matched modesetting as autoconfigured driver 1
[  1102.497] (==) Matched fbdev as autoconfigured driver 2
[  1102.497] (==) Matched vesa as autoconfigured driver 3
[  1102.497] (==) Assigned the driver to the xf86ConfigLayout
[  1102.497] (II) LoadModule: "ati"
[  1102.497] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[  1102.498] (II) Module ati: vendor="X.Org Foundation"
[  1102.498]compiled for 1.20.1, module version = 18.0.1
[  1102.498]Module class: X.Org Video Driver
[  1102.498]ABI class: X.Org Video Driver, version 24.0
[  1102.602] (II) LoadModule: "radeon"
[  1102.602] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[  1102.643] (II) Module radeon: vendor="X.Org Foundation"
[  1102.643]compiled for 1.20.1, module version = 18.0.1
[  1102.643]Module class: X.Org Video Driver
[  1102.643]ABI class: X.Org Video Driver, version 24.0
[  1102.643] (II) LoadModule: "modesetting"
[  1102.644] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[  1102.670] (II) Module modesetting: vendor="X.Org Foundation"
[  1102.670]compiled for 1.20.1, module version = 1.20.1
[  1102.670]Module class: X.Org Video 

[Buster]: Can't start X: no screens found(EE)

[local10]

Hi,

Am trying to upgrade a Debian Wheezy PC to Buster. The PC was successfully 
running Wheezy with KDE as desktop, in terms of hardware there are no changes. 
Initially, sddm was intalled to start KDE but that did not work for some 
reason, so now I starting KDE manually with startx.

Any ideas? Thanks

# cat .xinitrc
## Begin .xinitrc

exec ck-launch-session dbus-launch --exit-with-session startkde

## End .xinitrc


# lspci | grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880 
[Radeon HD 4200]

# grep "(EE)" .local/share/xorg/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[  1102.702] (EE) open /dev/dri/card0: No such file or directory
[  1102.702] (EE) open /dev/dri/card0: No such file or directory
[  1102.703] (EE) Unable to find a valid framebuffer device
[  1102.703] (EE) open /dev/fb0: No such file or directory
[  1102.703] (EE) Screen 0 deleted because of no matching config section.
[  1102.703] (EE) Screen 0 deleted because of no matching config section.
[  1102.703] (EE) Screen 0 deleted because of no matching config section.
[  1102.721] (EE) VESA(0): Cannot read int vect
[  1102.721] (EE) Screen(s) found, but none have a usable configuration.
[  1102.721] (EE)
[  1102.721] (EE) no screens found(EE)
[  1102.721] (EE)
[  1102.721] (EE) Please also check the log file at 
"/home/izavialo/.local/share/xorg/Xorg.0.log" for additional information.
[  1102.721] (EE)
[  1102.723] (EE) Server terminated with error (1). Closing log file.

On wheezy I don't remember installing any proprietary drivers: The following 
search was done on wheezy system while it was working:

# aptitude search radeon (this was on wheezy!)
i A libdrm-radeon1  
   - Userspace interface to radeon-specific kernel DRM 
services -- runtime   
p   libdrm-radeon1-dbg  
   - Userspace interface to radeon-specific kernel DRM 
services -- debugging symbols 
p   radeontool  
   - utility to control ATI Radeon backlight functions on 
laptops
p   radeontop   
   - Utility to show Radeon GPU utilization 
 
i A xserver-xorg-video-radeon   
   - X.Org X server -- AMD/ATI Radeon display driver
 
p   xserver-xorg-video-radeon-dbg   
   - X.Org X server -- AMD/ATI Radeon display driver 
(debugging symbols)   

The complete .local/share/xorg/Xorg.0.log is attached to the message.

Thanks


x.grep_.EE._.local_share_xorg_Xorg.0.log
Description: Binary data

Re: Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

On 27/08/18 14:04, Pedro wrote:
>> Però com que no em funcionava m'hi he barallat una estona i al final
>> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
>> interna (una classe B, suposo, amb adreces de l'interval
>> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
>> compartides entre diversos usuaris.
> Els prefixos de xarxa privada són:
>
>  10.0.0.0-   10.255.255.255  (10/8 prefix)
>  172.16.0.0  -   172.31.255.255  (172.16/12 prefix)
>  192.168.0.0 -   192.168.255.255 (192.168/16 prefix)
>
> https://tools.ietf.org/html/rfc1918
>
>
> podria ser que el proveïdor bloqueja port 22, per què no proves un altre?
>
> fora bo que ens diguis de quin proveïdor es tracta i així ens animarem
> a posar-lo en les nostres whitelists o blacklists personals
Hola Pedro,

En aquest cas l'operadora és Parlem, però no crec que el fenomen sigui
cosa d'ells directament, sinó del majorista de fibra que subcontracten,
en aquest cas (com he descobert posteriorment) MásMóvil.

Cordialment,
Orestes.

Re: processing order for configuration files in /etc/network/interfaces.d

[Greg Wooledge]

On Mon, Aug 27, 2018 at 06:41:25PM +0300, Reco wrote:
> Last sentence says to me that wordexp output should be always sorted.

This only tells us that it *reads* the config files in glob-sorted order.
And peeking into the actual source code of ifupdown, yes, it appears to
do this.  (File config.c starting at line 436, in the stretch source.)
It even uses wordexp() as advertised.

What's less clear to me at this moment is what happens *after* the
interface configuration file(s) have been read into memory.

Moving over to main.c, it looks like it reads the interfaces (line 639),
and that function was called from line 1190.  After line 1190, it loops
over the "target_iface" array, and processes them in the order they appear
in that array.

So... next question is how they get packed into that array.

Returning to the select_interfaces function, it looks like the ordering
is created by a call to find_allowup.

And... this is where I stopped reading, because it got confusing.  Maybe
someone else can take a stab at deciphering that part.

Re: processing order for configuration files in /etc/network/interfaces.d

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Aug 27, 2018 at 06:41:25PM +0300, Reco wrote:

[...]

> Assuming that glibc stays true to POSIX, 2001 standard - [1] says that:
> 
> The wordexp() function [...] The words shall be in order as described
> in the Shell and Utilities volume of IEEE Std 1003.1-2001, Section
> 2.6, Word Expansions.
> 
> Last sentence says to me that wordexp output should be always sorted.

This seems to settle the case, yes.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluEHNsACgkQBcgs9XrR2kan9QCfQUNK0KiThl1I5+zJ8NEWbJRn
12UAnA0U3zRkVh3+WOeB6WFz5Jq3h01U
=r0MO
-END PGP SIGNATURE-

Re: processing order for configuration files in /etc/network/interfaces.d

[Reco]

Hi.

On Mon, Aug 27, 2018 at 04:49:06PM +0200, to...@tuxteam.de wrote:
> On Mon, Aug 27, 2018 at 04:32:26PM +0300, Reco wrote:
> > Hi.
> > 
> > On Mon, Aug 27, 2018 at 09:08:19AM -0400, Greg Wooledge wrote:
> > > > Hm. Interfaces man page refers to wordexp(3), but this one doesn't say
> > > > anything about sorted results
> > > 
> > > In the absence of such information, the best thing to conclude is that
> > > the order is unspecified.  It may be using the raw unsorted directory
> > > contents from readdir(3), or it may be starting them all in parallel
> > > threads, in which case the order will be nondeterministic.
> > 
> > wordexp(3) invokes glob(3).
> > 
> > glob(3) states that one *needs* to specify GLOB_NOSORT to get resultes
> > pathnames in no particular order, as by default the result will be
> > sorted.
> > 
> > Unless I'm reading glibc source wrong, the only non-default argument
> > that wordexp(3) passes to glob(3) is GLOB_NOCHECK.
> 
> Thanks for looking into the source.
> 
> The remaining problem is, since the doc seems pretty fuzzy about that,
> whether one can rely on this behaviour, or whether this is just an
> implementation detail which can change under one at any time.

Assuming that glibc stays true to POSIX, 2001 standard - [1] says that:

The wordexp() function shall store the number of generated words into
pwordexp->we_wordc and a pointer to a list of pointers to words in
pwordexp->we_wordv. Each individual field created during field splitting
(see the Shell and Utilities volume of IEEE Std 1003.1-2001, Section
2.6.5, Field Splitting) or pathname expansion (see the Shell and
Utilities volume of IEEE Std 1003.1-2001, Section 2.6.6, Pathname
Expansion) shall be a separate word in the pwordexp->we_wordv list. The
words shall be in order as described in the Shell and Utilities volume
of IEEE Std 1003.1-2001, Section 2.6, Word Expansions.

Last sentence says to me that wordexp output should be always sorted.

Latest edition I could find - 2017 standard - [2] contains similar
wording.

Reco

[1] http://pubs.opengroup.org/onlinepubs/009695299/functions/wordexp.html

[2] http://pubs.opengroup.org/onlinepubs/9699919799/

Re: mailing list vs "the futur"

[Gene Heskett]

On Monday 27 August 2018 11:11:37 David Wright wrote:

> On Sat 25 Aug 2018 at 14:27:38 (-0500), John Hasler wrote:
> > David writes:
> > > Or are you talking about some type of "shared channel" of which I
> > > have no knowledge?
> >
> > Cable providers may have a great many customers on a single cable
> > with large (but limited) bandwidth.
>
> Oh, like me, you mean. When we wanted to get our cable strung from the
> pole with the least obstructed view of our house, the linesman first
> told us that all the terminations were taken, but on ringing the
> office, he found that one line was not subscribed to, so we were able
> to connect to that pole. When I walk down the back alleys, I can see
> other poles connected to the same main coax feed that links the poles.
>
> I'm still scratching my head why subscribing to NNTP newsgroups should
> lead to bandwidth problems rather than usage ones. I can hit my
> bandwidth limits in many other ways like downloading youtube videos,
> watching TV, etc, but the hard limit is my usage, where I would end up
> paying money for any excess.
>
That bandwidth limit is not on your side of the isp, its the bandwidth 
from the main trunk lines to the isp. NNTP is a huge bandwidth hog 
regardless of how much of it your isp accepts for spooling on local disk 
to serve you.

> > Some rural providers may have limited backhaul bandwidth.  They make
> > promises to customers based on optimistic estimates of peak usage.
Here at least, thats gradually getting better.
>
> Now it appears that you're using "usage" where I would write
> "bandwidth". Am I in a minority of one here? Bandwidth is the rate of
> transfer of bits, whereas usage is the quantity of bits transferred
> irrespective of how fast they accumulated.

Thats a pretty good view of the differences.
>
> Cheers,
> David.



-- 
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: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

[local10]

Aug 27, 2018, 2:57 AM by b...@fineby.me.uk:

> On Mon, 27 Aug 2018 03:49:14 +0200 (CEST)
> local10 <> loca...@tutanota.com > > wrote:
>
> The two things are unrelated.  The error on boot is "annoying but
> harmless", according what I've read, after a *very* cursory search
> (translation: you could have done this yourself).
>
Sorry about that, kind of struggling right now, the current environment isn't 
very conductive to extensive searches.


> The failure to start SDDM/KDE is probably due to entropy issues, and has
> been discussed on this list recently.
>
Looks like there are bigger problems with X but I'll put it in a separate 
message.

Regards,

Re: sometimes i go huh (grep result)

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Aug 27, 2018 at 11:19:25AM -0400, Greg Wooledge wrote:
> On Mon, Aug 27, 2018 at 10:36:12AM -0400, songbird wrote:
> > me@ant(25)$ env | grep -F "-g"
> > grep: invalid option -- 'g'
> 
> You want either -- or -e.
> 
> grep -F -- -g
> grep -F -e -g

More generally, '--' is convention for "end of option arguments,
normal arguments from here on". Most utilities nowadays stick to
that convention. It was introduced precisely for this case.

Note that quoting, as you do (i.e. "-g") can't work, because the
shell unwraps that level of quotes; grep will still see -g and
think it's an option. This quoting will help to "protect" whitespace:

  grep foo bar

will see two arguments, foo and bar, whereas

  grep "foo bar"

will see one, "foo bar".

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluEGYYACgkQBcgs9XrR2kb6vACfSGHIgX57p5r3oyJ+5vNFQgCX
sVUAn13XlvIHlRGYmzNeLfEpDwaDDFQx
=vMte
-END PGP SIGNATURE-

Re: sometimes i go huh (grep result)

[Nicolas George]

songbird (2018-08-27):
> me@ant(25)$ env | grep -F "-g"
> grep: invalid option -- 'g'

Maybe what you want is an explanation rather than just a solution.

Quotes are for the shell: they protect arguments that contain special
characters, so that commands get them as is.

For example, you need to write:

echo "Fire*Wolf"

because without the quotes, the shell would try to find all the files in
the current directory with a name that matches the pattern.

Since the dash is not special for the shell, the quotes are unnecessary.
They do no harm, but have no consequences here:

grep "-g"
grep '-g'
grep -g
grep ""''""-"g"''

all invoke grep with one extra argument "-g".

The dash is special for programs that understand options (some do not;
some do with a different syntax, for example key=value), and need to be
escaped the way programs expect it. The usual escaping is that an
argument "--" means all following arguments are not options, even if
they start with a dash.

> me@ant(26)$ env | grep -F '-g'
> grep: invalid option -- 'g'

Same as above.

> me@ant(28)$ env | grep '\-g'
> CFLAGS=-g

grep sees the argument starting with a backslash, it is not an option,
therefore it is the regexp. But backshash-dash could have had a special
semantic, like backslash-parentheses.

> me@ant(29)$ env | grep '-g'
> grep: invalid option -- 'g'

Same as above.

> me@ant(30)$ env | grep "-g"
> grep: invalid option -- 'g'

Same as above.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: sometimes i go huh (grep result)

[Greg Wooledge]

On Mon, Aug 27, 2018 at 11:20:42AM -0400, Roberto C. Sánchez wrote:
> env |grep [-]g

Fails if there is a file named -g in the current directory, as that
matches the unquoted glob and causes it to expand.  Also fails if failglob
is turned on, whether the file exists or not (fails differently in the
two cases).

Also fails if nullglob is turned on, but that is definitely not
recommended in interactive shells.

Re: mailing list vs "the futur"

[rhkramer]

On Monday, August 27, 2018 10:18:28 AM dekkz...@gmail.com wrote:
> On 08/27, Dave Sherohman wrote:
> >The only problem I can ever recall seeing with mailing lists and long
> >threads is when people don't trim the posts they're replying to.
> 
> Isn't that usually due to topic drift in which case break the thread under
> a new title?

No, I would say not -- well, maybe topic drift, but, too often I see an email 
with several points or suggestions in it, then someone quotes the entire post 
and says something like "I agree" or "that worked for me" at the bottom.  

Well, which do you agree with, which worked for you?

I try to trim so that only points that I am responding to remain in the post, 
with just enough contextual information so someone can (imho, should) be able 
to make sense of it.

And, even if the agree with everything (or everything worked), why leave all 
that old text in the post -- it is just extra stuff that my eye (and maybe 
brain) has to deal with.

I don't always follow or manage to comply with the following rule, but have it 
as one of my goals:  "The writer should make it easy on the reader -- there is 
only one writer, but there could be millions of readers."

(Now, granted, there is also the aphorisim (right word) that: "I did not have 
time to write you a short letter, so I wrote a long one", and, indeed, 
sometimes I don't take the time to write a short letter (or enough knowledge / 
understanding to do so.)

Hope everyone has a good day!

Re: sometimes i go huh (grep result)

[Roberto C . Sánchez]

On Mon, Aug 27, 2018 at 10:36:12AM -0400, songbird wrote:
> me@ant(25)$ env | grep -F "-g"
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(26)$ env | grep -F '-g'
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(27)$ env | grep -F 'CFL'
> CFLAGS=-g
> me@ant(28)$ env | grep '\-g'
> CFLAGS=-g
> me@ant(29)$ env | grep '-g'
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> me@ant(30)$ env | grep "-g"
> grep: invalid option -- 'g'
> Usage: grep [OPTION]... PATTERN [FILE]...
> Try 'grep --help' for more information.
> 
> 
try this:

env |grep [-]g

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: sometimes i go huh (grep result)

[Greg Wooledge]

On Mon, Aug 27, 2018 at 10:36:12AM -0400, songbird wrote:
> me@ant(25)$ env | grep -F "-g"
> grep: invalid option -- 'g'

You want either -- or -e.

grep -F -- -g
grep -F -e -g

sometimes i go huh (grep result)

[songbird]

me@ant(25)$ env | grep -F "-g"
grep: invalid option -- 'g'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
me@ant(26)$ env | grep -F '-g'
grep: invalid option -- 'g'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
me@ant(27)$ env | grep -F 'CFL'
CFLAGS=-g
me@ant(28)$ env | grep '\-g'
CFLAGS=-g
me@ant(29)$ env | grep '-g'
grep: invalid option -- 'g'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.
me@ant(30)$ env | grep "-g"
grep: invalid option -- 'g'
Usage: grep [OPTION]... PATTERN [FILE]...
Try 'grep --help' for more information.


songbird

Re: mailing list vs "the futur"

[David Wright]

On Sat 25 Aug 2018 at 14:27:38 (-0500), John Hasler wrote:
> David writes:
> > Or are you talking about some type of "shared channel" of which I have
> > no knowledge?
> 
> Cable providers may have a great many customers on a single cable with
> large (but limited) bandwidth.

Oh, like me, you mean. When we wanted to get our cable strung from the
pole with the least obstructed view of our house, the linesman first
told us that all the terminations were taken, but on ringing the
office, he found that one line was not subscribed to, so we were able
to connect to that pole. When I walk down the back alleys, I can see
other poles connected to the same main coax feed that links the poles.

I'm still scratching my head why subscribing to NNTP newsgroups should
lead to bandwidth problems rather than usage ones. I can hit my
bandwidth limits in many other ways like downloading youtube videos,
watching TV, etc, but the hard limit is my usage, where I would end up
paying money for any excess.

> Some rural providers may have limited backhaul bandwidth.  They make
> promises to customers based on optimistic estimates of peak usage.

Now it appears that you're using "usage" where I would write "bandwidth".
Am I in a minority of one here? Bandwidth is the rate of transfer of
bits, whereas usage is the quantity of bits transferred irrespective
of how fast they accumulated.

Cheers,
David.

Re: why is the kernel "unsleeping" a HDD put to sleep with hdparm -Y ?

[Patrick Bartek]

On Mon, 27 Aug 2018 19:48:18 +1000
Zenaan Harkness  wrote:

> So I have a 'spare' internal spinning rust bucket which I only use
> for backups, and so most of the time when I'm not using it I put it
> to sleep with:
> 
> sudo hdparm -Y /dev/sda
> 
> Unfortunately the kernel wakes the drive up again:

Since you don't use it that much, why "sleep" it at all? Just unmount
it. Check fstab, too, to see if it's list, and make it "noauto" or
remove the stanza entirely. That's what I did with a infrequently used
drive.

B

canvis en el su.

[Pere Nubiola Radigales]

Algú sap el perqué del canvis del su?
.
Fins ara amb la crida su es reinicialitzaba el path  amb el del usuari
root, mantenint la resta del entorn.
Ara si vols el path de root, necessites fer su -, reinicialitzant tot
l'entorn.

Pere Nubiola Radigales
Telf: +34 656316974
e-mail: p...@nubiola.cat
   pnubi...@fsfe.org
   pere.nubi...@gmail.com

Re: Curiositat sobre les IP assignades pels proveïdors

[Pau Ibars]

Canvia de router, Eloi! Que de passada, tindràs millor rendiment. El
hardware que posen els operadors semblen cafeteres!

Pau Ibars

Missatge de Eloi  del dia dl., 27 d’ag. 2018 a les
16:23:

> El 27/8/18 a les 12:36, Orestes Mas ha escrit:
> > Hola a tothom,
> >
> > Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
> > ha trobat.
> >
> > Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
> > per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
> > amb el proveïdor antic i no tenia cap problema, però ara amb el router
> > nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
> > "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
> >
> > Però com que no em funcionava m'hi he barallat una estona i al final
> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> > interna (una classe B, suposo, amb adreces de l'interval
> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> > compartides entre diversos usuaris.
> >
> > Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
> > Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
> > errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
> > iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
> > Suposo que funcionarà entre usuaris de la xarxa privada, però com que
> > només són 65536 això no és massa esperançador...
> >
> > Orestes
>
> Has provat si només tens problemes amb el port 22 i no amb un
> d'aleatori? La majoria de routers d'operadors que he vist tenen
> precisament el port 22 (en models més antics, el 23... sí, telnet)
> reservat i limitat a un rang d'IPs per a administració remota. En
> particular, això ho fa Telefónica (Movistar). En models més antics sí
> que podies arribar a tancar l'administració remota via SSH, però en
> l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part superior
> gris fosc i que engloba també el VoIP) això ja no és possible.
>
> La implicació de tot plegat és que el router, al final, l'acaba
> controlant l'operador i no tu.
>
> D'altres operadors no puc parlar.
>
>
>

Re: processing order for configuration files in /etc/network/interfaces.d

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Aug 27, 2018 at 04:32:26PM +0300, Reco wrote:
>   Hi.
> 
> On Mon, Aug 27, 2018 at 09:08:19AM -0400, Greg Wooledge wrote:
> > > Hm. Interfaces man page refers to wordexp(3), but this one doesn't say
> > > anything about sorted results
> > 
> > In the absence of such information, the best thing to conclude is that
> > the order is unspecified.  It may be using the raw unsorted directory
> > contents from readdir(3), or it may be starting them all in parallel
> > threads, in which case the order will be nondeterministic.
> 
> wordexp(3) invokes glob(3).
> 
> glob(3) states that one *needs* to specify GLOB_NOSORT to get resultes
> pathnames in no particular order, as by default the result will be
> sorted.
> 
> Unless I'm reading glibc source wrong, the only non-default argument
> that wordexp(3) passes to glob(3) is GLOB_NOCHECK.

Thanks for looking into the source.

The remaining problem is, since the doc seems pretty fuzzy about that,
whether one can rely on this behaviour, or whether this is just an
implementation detail which can change under one at any time.

Cheers
- -- t 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluED2IACgkQBcgs9XrR2kZF+wCdFpzaW8GZDiKF4LxaJp/RJpG7
3VsAnjHEgqjKgjhu2i9pg+ORE3kqyyF/
=8T3S
-END PGP SIGNATURE-

Re: Curiositat sobre les IP assignades pels proveïdors

[Eloi]

El 27/8/18 a les 12:36, Orestes Mas ha escrit:
> Hola a tothom,
>
> Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
> ha trobat.
>
> Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
> per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
> amb el proveïdor antic i no tenia cap problema, però ara amb el router
> nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
> "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>
> Però com que no em funcionava m'hi he barallat una estona i al final
> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> interna (una classe B, suposo, amb adreces de l'interval
> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> compartides entre diversos usuaris.
>
> Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
> Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
> errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
> iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
> Suposo que funcionarà entre usuaris de la xarxa privada, però com que
> només són 65536 això no és massa esperançador...
>
> Orestes

Has provat si només tens problemes amb el port 22 i no amb un
d'aleatori? La majoria de routers d'operadors que he vist tenen
precisament el port 22 (en models més antics, el 23... sí, telnet)
reservat i limitat a un rang d'IPs per a administració remota. En
particular, això ho fa Telefónica (Movistar). En models més antics sí
que podies arribar a tancar l'administració remota via SSH, però en
l'últim que tinc d'ells (de fibra, quadrat, vora blanca i part superior
gris fosc i que engloba també el VoIP) això ja no és possible.

La implicació de tot plegat és que el router, al final, l'acaba
controlant l'operador i no tu.

D'altres operadors no puc parlar.

Re: Re: mailing list vs "the futur"

[dekkzz78]

On 08/27, Dave Sherohman wrote:

On Fri, Aug 24, 2018 at 07:23:15PM +0100, mick crane wrote:

mailing list are great until one of the threads gets really, really, really
long


...and then they're *REALLY* great.

The only problem I can ever recall seeing with mailing lists and long
threads is when people don't trim the posts they're replying to.


Isn't that usually due to topic drift in which case break the thread under a 
new title?


--
Dave Sherohman



--
regards.

Dekks Herton

Thinkpad T61 2.0Ghz 2GB WSXGA+

Jabber IM: dekkz...@jabber.hot-chilli.net


signature.asc
Description: PGP signature

Re: mailing list vs "the futur"

[Gene Heskett]

On Monday 27 August 2018 07:48:01 rhkra...@gmail.com wrote:

> On Monday, August 27, 2018 04:12:32 AM Dave Sherohman wrote:
> > The only problem I can ever recall seeing with mailing lists and
> > long threads is when people don't trim the posts they're replying
> > to.
>
> That never happens on this list, does it (with tongue deeply in
> cheek).

Don't byte down, guy. You'll be ending your posts with frownies for a 
while. ;-)

-- 
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: df -h shows insufficient precision

[Michael Stone]

On Sun, Aug 26, 2018 at 12:25:44PM +1000, Zenaan Harkness wrote:

df shows bytes, df -h shows only one decimal place, so e.g. on a
1.8TiB drive "1.6T" is the free space, but that resolution/ precision
is insufficient.


Insufficient for what?

Re: why is the kernel "unsleeping" a HDD put to sleep with hdparm -Y ?

[mick crane]

On 2018-08-27 10:48, Zenaan Harkness wrote:

So I have a 'spare' internal spinning rust bucket which I only use
for backups, and so most of the time when I'm not using it I put it
to sleep with:

sudo hdparm -Y /dev/sda


sorry cannot help but I have similar disk and this seems like a good 
idea.

Presume have to unmount disk before putting to sleep ?

mick

--
Key ID4BFEBB31

Re: lots of issues with KDE after update

[Hans]

Hi HDV,

yes, as I am doing full-ugrades nearly every day, I saw this issue very quick. 
But whenever I see an issue, I wait a few days before filing a bug. In many 
cases appeasring bugs are solved within a few days, maybe because the 
developer himself corrects his errors or someone elese found the reason for a 
bug (it is great and impressive, to see, how fast bugs are fixed in debian! Or 
in the open source worrls at all). 

When a bug appears for a longer time, then I ask if someone got the same 
issue. If I knew the buggy poackage, I filoe the bugreport myself.


FYI, I opened a bugreport on the KDE-site to this issue (KDE: general) with 
the hope, the developers know better, which lib or app is responsible.

Great to know, that I am not the only one, so it is sure a bug.

Thankls for confirming this.

Best regards and happy hacking

Hans

 
> 
> Hai Hans,
> 
> It is not just you. I am having the same issues.
> 
> Maybe it is coincidence, but after exactly the same apt-get upgrade with a
> lot of plasma updates pan started acting up as well. However pan is GTK,
> not Qt, so I don't know for sure those problems are related to the same
> issues as plasma is having at the moment.
> 
> P.S. This is on testing with apt-get udate/apt-get upgrade/apt-get
> dist-upgrade being run once every few (about 3) days, so no significant
> backlog in updates. Therefore I presume the problems must originate in a
> library that was updated last Thursday of Friday.
> 
> Grx HdV

Re: processing order for configuration files in /etc/network/interfaces.d

[Reco]

Hi.

On Mon, Aug 27, 2018 at 09:08:19AM -0400, Greg Wooledge wrote:
> > Hm. Interfaces man page refers to wordexp(3), but this one doesn't say
> > anything about sorted results
> 
> In the absence of such information, the best thing to conclude is that
> the order is unspecified.  It may be using the raw unsorted directory
> contents from readdir(3), or it may be starting them all in parallel
> threads, in which case the order will be nondeterministic.

wordexp(3) invokes glob(3).

glob(3) states that one *needs* to specify GLOB_NOSORT to get resultes
pathnames in no particular order, as by default the result will be
sorted.

Unless I'm reading glibc source wrong, the only non-default argument
that wordexp(3) passes to glob(3) is GLOB_NOCHECK.

Reco

Re: processing order for configuration files in /etc/network/interfaces.d

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Aug 27, 2018 at 09:08:19AM -0400, Greg Wooledge wrote:
> On Mon, Aug 27, 2018 at 10:18:29AM +0200, to...@tuxteam.de wrote:
> > On Sun, Aug 26, 2018 at 09:36:30PM +0300, Martin T wrote:
> > > I'm using "source":
> > 
> > Wait a sec... this is not run-parts, then, but the shell builtin 'source'
> > you are using, like in:
> > 
> > > source /etc/network/interfaces.d/*
> 
> It's not a shell's builtin "source" [...]

Er... yes, you are right. That's a config item which is implemented
by wordexp(3), if we believe the interfaces man page. The above is
just leftovers from a post which I corrected (incompletely) after
I found out exactly this. Grmpf.

Note to self: always re-read a third time.

[...]

> In the absence of such information, the best thing to conclude is that
> the order is unspecified.  It may be using the raw unsorted directory
> contents from readdir(3), or it may be starting them all in parallel
> threads, in which case the order will be nondeterministic.

Agreed, although this seems somewhat unfortunate.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluD+3EACgkQBcgs9XrR2kZp4wCeMY7EMt74Q8N5VdzUERSg6Cwp
hiIAn1q5rEwqiINkspih37t730qPqkVL
=20hc
-END PGP SIGNATURE-

Re: processing order for configuration files in /etc/network/interfaces.d

[Greg Wooledge]

On Mon, Aug 27, 2018 at 10:18:29AM +0200, to...@tuxteam.de wrote:
> On Sun, Aug 26, 2018 at 09:36:30PM +0300, Martin T wrote:
> > I'm using "source":
> 
> Wait a sec... this is not run-parts, then, but the shell builtin 'source'
> you are using, like in:
> 
> > source /etc/network/interfaces.d/*

It's not a shell's builtin "source" command either, but rather, something
implemented by the Debian ifupdown software.

> Hm. Interfaces man page refers to wordexp(3), but this one doesn't say
> anything about sorted results

In the absence of such information, the best thing to conclude is that
the order is unspecified.  It may be using the raw unsorted directory
contents from readdir(3), or it may be starting them all in parallel
threads, in which case the order will be nondeterministic.

Re: Curiositat sobre les IP assignades pels proveïdors

[Jordi Miguel]

Hola Orestes,

El que comentes que fa el teu proveïdor s'anomena "Carrier-grade NAT"
i és una pràctica que s'ha estès bastant degut a l'esgotament de les
adreces IPv4. Es d'esperar que quan lo habitual sigui IPv6 aquests
proveïdors tornaran a donar IPs públiques als seus usuaris.
En quant a obrir ports per poder accedir a serveis que tinguis a les
teves màquines internes des de Internet ho tens bastant negre.
Bàsicament les solucions passen per obtenir una adreça IP pública que
si que puguis controlar i utilitzar-la per publicar els serveis als
que vols accedir des d'Internet. Possibles solucions:
- Obtenir una adreça d'un proveïdor de VPN que suporti publicar serveis.
- Si el teu proveïdor tmb t'esta donant una IPv6, i si aquesta és
pública (això segon seria bastant probable) utilitzar-la per publicar
els teus serveis. L'únic "desavantatge" és que els usuaris que només
tinguin un accés IPv4 no podran accedir directament als teus serveis,
hauran d'utilitzar miredo o altres solucions.
- Si disposes d'un servidor amb IP pública fer un tunel entre la teva
màquina i la màquina externa i publicar els serveis utilitzant la IP
del servidor públic. (algo similar a lo que s'explica aquí [1])

Espero que aquesta informació et serveixi d'alguna cosa.

Per cert, estic molt d'acord amb el Pedro que els proveïdors haurien
de deixar ben clar si la connexió que contractes està darrera un NAT o
no. Desconec si el teu proveïdor ha deixat clara aquesta informació
abans d'adquirir el producte, tanmateix donat que hi ha ISPs que no ho
diuen fóra bó disposar d'una llista pública on els usuaris puguin
consultar aquesta informació abans de contractar res.


[1] https://amoss.me/2017/05/port-forwarding-behind-a-carrier-grade-nat/

Fins aviat,
Jordi
--
Para ser realmente grande, hay que estar con la gente, no por encima de ella.
El lun., 27 ago. 2018 a las 13:42, Orestes Mas () escribió:
>
> Hola a tothom,
>
> Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
> ha trobat.
>
> Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
> per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
> amb el proveïdor antic i no tenia cap problema, però ara amb el router
> nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
> "whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).
>
> Però com que no em funcionava m'hi he barallat una estona i al final
> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> interna (una classe B, suposo, amb adreces de l'interval
> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> compartides entre diversos usuaris.
>
> Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
> Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
> errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
> iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
> Suposo que funcionarà entre usuaris de la xarxa privada, però com que
> només són 65536 això no és massa esperançador...
>
> Orestes
>
>

Re: lots of issues with KDE after update

[hdv@gmail]

On 2018-08-27 10:56, Hans wrote:
> Hi folks,
> 
> after lates upgrade of KDE in debian/testing, I found several issues.
> 
> 1. Missing of all applications (icons) inm the taskbar
> 
> 2. Missing of all status icons in the taskbar
> 
> 3. Right mouse click in for desktop settimngs in desktop nbo more working (so 
> I can not add any widgests or change desktop settings). Even unlocking the 
> desktop is thus no more possible.
> 
> 4. The weather plasmoid (widget) disappeared.
> 
> I would have filed a bugreport, but I still copuld not discover, which 
> particular package or libnrary is responsible for this behaviour.
> If someone knows more, I would be happy, if he could give me some clue.
> 
> The system here is runnning debian/testing 32-bit, if this issue appears on a 
> 64-bit system is unknown, as I do not own a 64-bit debian system at the 
> moment.
> 
> It would also help, if these isssue can be confirmeds as known. I googled, 
> but 
> found only issues with Ubuntu, not debian.
> 
> Thanks for any hints.

Hai Hans,

It is not just you. I am having the same issues.

Maybe it is coincidence, but after exactly the same apt-get upgrade with a lot
of plasma updates pan started acting up as well. However pan is GTK, not Qt, so
I don't know for sure those problems are related to the same issues as plasma is
having at the moment.

P.S. This is on testing with apt-get udate/apt-get upgrade/apt-get dist-upgrade
being run once every few (about 3) days, so no significant backlog in updates.
Therefore I presume the problems must originate in a library that was updated
last Thursday of Friday.

Grx HdV

Re: why is the kernel "unsleeping" a HDD put to sleep with hdparm -Y ?

[Marc Auslander]

Zenaan Harkness  writes:

>So I have a 'spare' internal spinning rust bucket which I only use
>for backups, and so most of the time when I'm not using it I put it
>to sleep with:
>
>sudo hdparm -Y /dev/sda
>
>Unfortunately the kernel wakes the drive up again:
>
>Aug 27 19:44:40 eye kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 
>action 0x6
>Aug 27 19:44:40 eye kernel: ata1.00: waking up from sleep
>Aug 27 19:44:40 eye kernel: ata1: hard resetting link
>Aug 27 19:44:41 eye kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 
>300)
>Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
>FEATURES) succeeded
>Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
>FREEZE LOCK) filtered out
>Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
>FEATURES) filtered out
>Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
>FEATURES) succeeded
>Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
>FREEZE LOCK) filtered out
>Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
>FEATURES) filtered out
>Aug 27 19:44:43 eye kernel: ata1.00: configured for UDMA/133
>Aug 27 19:44:43 eye kernel: ata1: EH complete
>
>Why is the kernel doing this, and how do I stop it from happening?
>
>TIA,

I do a similar thing but use hdparm -y.  I never see the drive spin back
up.

I would look in the log for a cron job related to the drive comming back up.

Re: Curiositat sobre les IP assignades pels proveïdors

[Pedro]

Gràcies per la precisió Jordi.

M'alegro de continuar aprenent.

Però si us plau, digueu els proveïdors que estan fent NAT als usuaris!

Que si no dones de baixa el producte en 15 dies te l'has de menjar un
any (permanència).

Re: Curiositat sobre les IP assignades pels proveïdors

[Jordi Miguel]

Hola,

Aquesta resposta sobre les IP's privades no es del tot precisa.
Existeixen més rangs que no s'enruten a Internet. Entre ells el rang
que comenta l'Orestes i que pertany al següent RFC:
https://tools.ietf.org/html/rfc6598
Si mireu el RFC veureu que es un rang que es va crear precisament per
fer el que l'Orestes ha detectat en la seva connexió.

D'altre banda, et confirmo que efectivament no és el primer proveïdor
d'Internet que utilitza NAT amb els seus usuaris.


Salutacions,
Jordi
--
Para ser realmente grande, hay que estar con la gente, no por encima de ella.
El lun., 27 ago. 2018 a las 14:04, Pedro () escribió:
>
> > Però com que no em funcionava m'hi he barallat una estona i al final
> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> > interna (una classe B, suposo, amb adreces de l'interval
> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> > compartides entre diversos usuaris.
>
> Els prefixos de xarxa privada són:
>
>  10.0.0.0-   10.255.255.255  (10/8 prefix)
>  172.16.0.0  -   172.31.255.255  (172.16/12 prefix)
>  192.168.0.0 -   192.168.255.255 (192.168/16 prefix)
>
> https://tools.ietf.org/html/rfc1918
>
>
> podria ser que el proveïdor bloqueja port 22, per què no proves un altre?
>
> fora bo que ens diguis de quin proveïdor es tracta i així ens animarem
> a posar-lo en les nostres whitelists o blacklists personals
>

Re: Curiositat sobre les IP assignades pels proveïdors

[Pere Nubiola Radigales]

Per curiositat he fet un whois de la adreça 100.76.0.1. Aquest es el
resultat
perico@portatil:~$ whois 100.76.0.1

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#
# If you see inaccuracies in the results, please report at
# https://www.arin.net/resources/whois_reporting/index.html
#
# Copyright 1997-2018, American Registry for Internet Numbers, Ltd.
#


NetRange:   100.64.0.0 - 100.127.255.255
CIDR:   100.64.0.0/10
NetName:SHARED-ADDRESS-SPACE-RFCTBD-IANA-RESERVED
NetHandle:  NET-100-64-0-0-1
Parent: NET100 (NET-100-0-0-0-0)
NetType:IANA Special Use
OriginAS:
Organization:   Internet Assigned Numbers Authority (IANA)
RegDate:2012-03-13
Updated:2016-04-11
Comment:This block is used as Shared Address Space. Traffic from
these addresses does not come from IANA. IANA has simply reserved these
numbers in its database and does not use or operate them. We are not the
source of activity you may see on logs or in e-mail records. Please refer
to http://www.iana.org/abuse/
Comment:
Comment:Shared Address Space can only be used in Service Provider
networks or on routing equipment that is able to do address translation
across router interfaces when addresses are identical on two different
interfaces.
Comment:
Comment:This block was assigned by the IETF in the Best Current
Practice document,
Comment:RFC 6598 which can be found at:
Comment:http://tools.ietf.org/html/rfc6598
Ref:https://rdap.arin.net/registry/ip/100.64.0.0



OrgName:Internet Assigned Numbers Authority
OrgId:  IANA
Address:12025 Waterfront Drive
Address:Suite 300
City:   Los Angeles
StateProv:  CA
PostalCode: 90292
Country:US
RegDate:
Updated:2012-08-31
Ref:https://rdap.arin.net/registry/entity/IANA


OrgAbuseHandle: IANA-IP-ARIN
OrgAbuseName:   ICANN
OrgAbusePhone:  +1-310-301-5820
OrgAbuseEmail:  ab...@iana.org
OrgAbuseRef:https://rdap.arin.net/registry/entity/IANA-IP-ARIN

OrgTechHandle: IANA-IP-ARIN
OrgTechName:   ICANN
OrgTechPhone:  +1-310-301-5820
OrgTechEmail:  ab...@iana.org
OrgTechRef:https://rdap.arin.net/registry/entity/IANA-IP-ARIN


Pere Nubiola Radigales
Telf: +34 656316974
e-mail: p...@nubiola.cat
   pnubi...@fsfe.org
   pere.nubi...@gmail.com


El dia 27 d’agost de 2018 a les 14:04, Pedro  ha
escrit:

> > Però com que no em funcionava m'hi he barallat una estona i al final
> > acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> > interna (una classe B, suposo, amb adreces de l'interval
> > 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> > compartides entre diversos usuaris.
>
> Els prefixos de xarxa privada són:
>
>  10.0.0.0-   10.255.255.255  (10/8 prefix)
>  172.16.0.0  -   172.31.255.255  (172.16/12 prefix)
>  192.168.0.0 -   192.168.255.255 (192.168/16 prefix)
>
> https://tools.ietf.org/html/rfc1918
>
>
> podria ser que el proveïdor bloqueja port 22, per què no proves un altre?
>
> fora bo que ens diguis de quin proveïdor es tracta i així ens animarem
> a posar-lo en les nostres whitelists o blacklists personals
>
>

Re: mailing list vs "the futur"

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, Aug 27, 2018 at 07:48:01AM -0400, rhkra...@gmail.com wrote:
> On Monday, August 27, 2018 04:12:32 AM Dave Sherohman wrote:
> > The only problem I can ever recall seeing with mailing lists and long
> > threads is when people don't trim the posts they're replying to.
> 
> That never happens on this list, does it (with tongue deeply in cheek).

Not that I knew of, oh no, Sir ;-)

Cheers
- -- t
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluD6u4ACgkQBcgs9XrR2kZkdgCfSuyuVagjx4yLhrSX/9aCbmri
hjAAnRfVMjX+ZymcCvaV8ojveDoDyLEy
=8IKT
-END PGP SIGNATURE-

Re: Curiositat sobre les IP assignades pels proveïdors

[Pedro]

> Però com que no em funcionava m'hi he barallat una estona i al final
> acabo deduint que el proveïdor d'internet utilitza una xarxa privada
> interna (una classe B, suposo, amb adreces de l'interval
> 100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
> compartides entre diversos usuaris.

Els prefixos de xarxa privada són:

 10.0.0.0-   10.255.255.255  (10/8 prefix)
 172.16.0.0  -   172.31.255.255  (172.16/12 prefix)
 192.168.0.0 -   192.168.255.255 (192.168/16 prefix)

https://tools.ietf.org/html/rfc1918


podria ser que el proveïdor bloqueja port 22, per què no proves un altre?

fora bo que ens diguis de quin proveïdor es tracta i així ens animarem
a posar-lo en les nostres whitelists o blacklists personals

Re: mailing list vs "the futur"

[rhkramer]

On Monday, August 27, 2018 04:12:32 AM Dave Sherohman wrote:
> The only problem I can ever recall seeing with mailing lists and long
> threads is when people don't trim the posts they're replying to.

That never happens on this list, does it (with tongue deeply in cheek).

Curiositat sobre les IP assignades pels proveïdors

[Orestes Mas]

Hola a tothom,

Observo un fenomen curiós, i m'agradaria saber si algú de vosaltres s'hi
ha trobat.

Fa pocs dies m'he posat fibra a casa. Volia obrir el port 22 del router
per poder accedir des de fora via ssh a un ordinador. Això ja ho feia
amb el proveïdor antic i no tenia cap problema, però ara amb el router
nou no em funcionava. La IP pública, segons m'indiquen webs del tipus
"whatismyip" era 93.176.xxx.yyy (canvia si reboto el router).

Però com que no em funcionava m'hi he barallat una estona i al final
acabo deduint que el proveïdor d'internet utilitza una xarxa privada
interna (una classe B, suposo, amb adreces de l'interval
100.76.xxx.yyy). I surt a internet amb unes quantes adreces públiques
compartides entre diversos usuaris.

Les preguntes: Us heu trobat que el proveïdor d'internet faci NAT també?
Sabeu si com a usuaris ens podem queixar (ja imagino que no...)? Vaig
errat si dedueixo que això impedirà que funcioni qualsevol accés a casa
iniciat des de l'exterior (tipus emule, bittorrent,ssh , httpd...)?
Suposo que funcionarà entre usuaris de la xarxa privada, però com que
només són 65536 això no és massa esperançador...

Orestes

Re: why is the kernel "unsleeping" a HDD put to sleep with hdparm -Y ?

[Dan Ritter]

On Mon, Aug 27, 2018 at 07:48:18PM +1000, Zenaan Harkness wrote:
> So I have a 'spare' internal spinning rust bucket which I only use
> for backups, and so most of the time when I'm not using it I put it
> to sleep with:
> 
> sudo hdparm -Y /dev/sda
> 
> Unfortunately the kernel wakes the drive up again:
> 
> Aug 27 19:44:40 eye kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 
> action 0x6
> Aug 27 19:44:40 eye kernel: ata1.00: waking up from sleep
> Aug 27 19:44:40 eye kernel: ata1: hard resetting link
> Aug 27 19:44:41 eye kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 
> 300)
> Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
> FEATURES) succeeded
> Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
> FREEZE LOCK) filtered out
> Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
> FEATURES) filtered out
> Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
> FEATURES) succeeded
> Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
> FREEZE LOCK) filtered out
> Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
> FEATURES) filtered out
> Aug 27 19:44:43 eye kernel: ata1.00: configured for UDMA/133
> Aug 27 19:44:43 eye kernel: ata1: EH complete
> 
> Why is the kernel doing this, and how do I stop it from happening?

How often does it happen?

-dsr-

why is the kernel "unsleeping" a HDD put to sleep with hdparm -Y ?

[Zenaan Harkness]

So I have a 'spare' internal spinning rust bucket which I only use
for backups, and so most of the time when I'm not using it I put it
to sleep with:

sudo hdparm -Y /dev/sda

Unfortunately the kernel wakes the drive up again:

Aug 27 19:44:40 eye kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 
action 0x6
Aug 27 19:44:40 eye kernel: ata1.00: waking up from sleep
Aug 27 19:44:40 eye kernel: ata1: hard resetting link
Aug 27 19:44:41 eye kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 
300)
Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
FEATURES) succeeded
Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
FREEZE LOCK) filtered out
Aug 27 19:44:41 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
FEATURES) filtered out
Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET 
FEATURES) succeeded
Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY 
FREEZE LOCK) filtered out
Aug 27 19:44:43 eye kernel: ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET 
FEATURES) filtered out
Aug 27 19:44:43 eye kernel: ata1.00: configured for UDMA/133
Aug 27 19:44:43 eye kernel: ata1: EH complete

Why is the kernel doing this, and how do I stop it from happening?

TIA,

lots of issues with KDE after update

[Hans]

Hi folks,

after lates upgrade of KDE in debian/testing, I found several issues.

1. Missing of all applications (icons) inm the taskbar

2. Missing of all status icons in the taskbar

3. Right mouse click in for desktop settimngs in desktop nbo more working (so 
I can not add any widgests or change desktop settings). Even unlocking the 
desktop is thus no more possible.

4. The weather plasmoid (widget) disappeared.

I would have filed a bugreport, but I still copuld not discover, which 
particular package or libnrary is responsible for this behaviour.
If someone knows more, I would be happy, if he could give me some clue.

The system here is runnning debian/testing 32-bit, if this issue appears on a 
64-bit system is unknown, as I do not own a 64-bit debian system at the 
moment.

It would also help, if these isssue can be confirmeds as known. I googled, but 
found only issues with Ubuntu, not debian.

Thanks for any hints.

Best regards

Hans

Re: Autologin not working (lightdm, openbox)

[Alexandre Rossi]

Hi,

> Before anyone asks, i've looked all over the wiki and every other post online 
> so i'm not sure why this isn't working. When I start up my machine X starts 
> up fine. and it goes to the lightdm login screen, but it still makes me put 
> in the password.
>
> My user is in the autologin and nopasswdlogin groups, i've made the right 
> changes to both the files listed below as A and B sources.

I've always had no problem with autologin with lightdm, all I ever had
to do was to set autologin-user in the [Seat:*] in
/etc/lightdm/lightdm.conf . Another option that I have used
successfuly is using lightdm-autologin-greeter and setting up
autologin-user in
/etc/lightdm/lightdm.conf.d/lightdm-autologin-greeter.conf

I guess you already checked this but double check you are able to
login with that user using a password.

Alex

Re: processing order for configuration files in /etc/network/interfaces.d

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sun, Aug 26, 2018 at 09:36:30PM +0300, Martin T wrote:
> Hi David,
> 
> > You need to post your evidence, starting with your /etc/network/interfaces
> > file. You say you're using ifup, so we can perhaps discount this paragraph:
> >
> >Currently, "source-directory" isn't supported by
> >network-manager and guessnet.
> >
> > but we don't know whether you're using "source-directory" or "source",
> > for example.
> 
> I'm using "source":

Wait a sec... this is not run-parts, then, but the shell builtin 'source'
you are using, like in:

> # cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
> 
> source /etc/network/interfaces.d/*
> #

Hm. Interfaces man page refers to wordexp(3), but this one doesn't say
anything about sorted results (although it cites glob as cousin which
_by default_ is sorted, although one can switch that off).

That's unfortunate.

> Yes, this is probably a good idea. However, ideally, "man interfaces"
> should state in which order files in /etc/network/interfaces.d/ are
> processed.

Definitely.

Sorry for bringing up "run-parts". That was a red herring.

Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAluDs9UACgkQBcgs9XrR2kYMbgCfRZRIthRQROzHVnqd3WaV4HmZ
MG8An03Oe3OZZm1hJaRgiNBmfPpky4qj
=JATa
-END PGP SIGNATURE-

Re: mailing list vs "the futur"

[Dave Sherohman]

On Fri, Aug 24, 2018 at 07:23:15PM +0100, mick crane wrote:
> mailing list are great until one of the threads gets really, really, really
> long

...and then they're *REALLY* great.

The only problem I can ever recall seeing with mailing lists and long
threads is when people don't trim the posts they're replying to.

-- 
Dave Sherohman

Re: linux 4.19 scsi-mq default?

[Stefan Krusche]

Hi Boyan,

Am Montag, 27. August 2018 schrieb Boyan Penkov:
> Hello folks,
>
> Likely not the exact right list to ask, but likely someone here knows — did
> scsi-mq by default make it into linux 4.19?
>
> http://lkml.iu.edu/hypermail/linux/kernel/1807.0/02224.html
> 

This post on lkml is talking about a kernel option. These options are usually 
documented in /boot/config-4.x.y (according to installed kernels). I can't tell 
for your kernel as I don't have 4.19 installed but you easily can check for 
yourself by running this command (example for my system):

$ grep SCSI_MQ_DEFAULT /boot/config-4.9.0-8-amd64
# CONFIG_SCSI_MQ_DEFAULT is not set

HTH

Kind regards,
Stefan

Re: Wifi : impossible de me connecter en PEAP/MSCHAPv2 [enfin, ça dépend]

[David BERCOT]

Bonjour Christophe,

Pas de souci ;-)

Je cherche encore...

David.

Le 25/08/2018 à 11:51, Christophe Maquaire a écrit :
> Le samedi 25 août 2018 à 10:00 +0200, Christophe Maquaire a écrit :
>>
>> et j'ai trouvé la solution là:
>>
>> https://lists.debian.org/debian-user/2017/06/msg01045.html
>>
> 
> Argh, j'ai lu trop vite, je vois que tu avais déjà essayé cette
> solution sans résultat positif.
> 
> Désolé,
> 
> Christophe 
> 
> 

Autologin not working (lightdm, openbox)

[Shea Alterio]

Hey everyone.
Before anyone asks, i've looked all over the wiki and every other post
online so i'm not sure why this isn't working. When I start up my machine X
starts up fine. and it goes to the lightdm login screen, but it still makes
me put in the password.

My user is in the autologin and nopasswdlogin groups, i've made the right
changes to both the files listed below as A and B sources.

Any help would be greatly appreciated. Thank you all in advance.

I added the following line to the top of /etc/pam.d/lightdm:
authsufficient  pam_succeed_if.so (my user) ingroup autologin

$ /usr/sbin/lightdm --show-config
   [Seat:*]
B  greeter-session=lightdm-greeter
B  greeter-hide-users=false
B  session-wrapper=/etc/X11/Xsession
B  autologin-user=(my user)
B  autologin-user-timeout=0
B  pam-service=lightdm
B  pam-autologin-service=lightdm-autologin
B  autologin-session=openbox-session

   [LightDM]
B  start-default-seat=true

Sources:
A  /usr/share/lightdm/lightdm.conf.d/01_debian.conf
B  /etc/lightdm/lightdm.conf

Re: Migrer un système debian vers un système de fichiers chiffré luks

[dethegeek]

Bonjour,

Le samedi 25 août 2018 à 10:11 +0200, Pascal Hambourg a écrit :
> Le 24/08/2018 à 21:50, dethegeek a écrit :
> > j'ai prévu un seul vg chiffré, contenant tous mes lv sensibles:
> > rootfs
> > et home. J'ai initialement prévu que boot soit non chiffré, mais
> > c'est
> > pas une bone idée. On peut techniquement attaquer ce volume pour y
> > mettre un keylogger.
> > 
> > La bonne pratique est donc de chiffrer /boot, grub , de ce que je
> > lis,
> > le gère
> 
> Oui. Mais la core image de GRUB (qui demande de taper la passphrase
> pour 
> déchiffrer le volume contenant /boot) reste en clair et donc
> vulnérable.
> 
> Si le but est de se protéger de la divulgation des données en cas de 
> perte ou vol de l'ordinateur, alors le chiffrement de /boot n'est
> pas 
> nécessaire, il ne contient pas de donnée sensible.
> 
> Si le but est de se protéger contre une intervention illicite sur 
> l'ordinateur passée inaperçue, alors le chiffrement quel qu'il soit
> ne 
> suffit pas car il reste toujours une partie en clair pour l'amorçage.
> Il 
> faut y ajouter la vérification de l'intégrité.
> 
Bonne remarque. Du coup il faut un certificat pour vérifier GRUB ainsi
que /boot si elle n'est pas chiffrée. Avoir /boot chiffré permettrait
de réduire le volume de données à valider. Un système TPM aiderait.

Re: Buster: ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180313/dspkginit-414)

[Brad Rogers]

On Mon, 27 Aug 2018 03:49:14 +0200 (CEST)
local10  wrote:

Hello local10,

>Am getting the following errors on boot and, probably due to the
>errors, KDE cannot start (kde-plasma-desktop package was installed).

The two things are unrelated.  The error on boot is "annoying but
harmless", according what I've read, after a *very* cursory search
(translation: you could have done this yourself).

The failure to start SDDM/KDE is probably due to entropy issues, and has
been discussed on this list recently.
Options are:
Wait until SDDM starts (can be up to three minutes)
Mash on keyboard until SDDM starts (takes a few seconds)
Install 'haveged' to increase entropy during boot process

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Why do they try to hide our past pulling down houses and build car parks
Bricks & Mortar - The Jam


pgpZmeu4ToSlU.pgp
Description: OpenPGP digital signature

Re: enregistrer une page web avec w3m

[didier gaumet]

Le 27/08/2018 à 04:18, Bernard Schoenacker a écrit :
[...]
> avec (e)links je peut enregistrer une page web 
> au format texte et je recherche à faire de même 
> avec w3m
[...]

d'après http://w3m.sourceforge.net/MANUAL :
 a ou d suivant que tu es en mode natif ou en mode émulation clavier Lynx