Re: Ethernet is not started at boot

[Michelle Konzack]

Hi Richard,

Am 2018-02-07 hackte Richard Hector in die Tasten:
> On 07/02/18 04:54, Michelle Konzack wrote:
>> Sorry, I ment dbus-x11
>
> "apt-rdepends blueman" (you might want to install apt-rdepends) doesn't
> list dbus-x11 anywhere. If blueman really needs it, then either it or
> one of its other dependencies is failing to declare it, which would be a
> bug.

And it is.  Confirmed by the Maintainer!

The other thing is, I can not figure out, what gthumb is missing
and lead to a SEGFAULT at startup...

If I have more time and a Monitor for my two Mini-ITX, I will redo
the installation based on what I have on the T400 to fugure out,
which depends are missing.

Note:  I know apt-rdepends and use it since quiet a time

> Richard

Have a nice day

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Ethernet is not started at boot

[Michelle Konzack]

Hello Richard,

Am 2018-02-07 hackte Richard Hector in die Tasten:
> On 07/02/18 08:07, Brian wrote:
>> netmask and network are not needed. ifupdown will compute them. Note
>> there are no examples in interfaces(5) which use these parameters.
>
> The examples use CIDR notation instead, eg "address 192.168.1.1/24".
>
> The netmask line is an alternative to that. You need to tell it
> _somehow_ how big the subnet is.

Thankyou, it seems, people have forgotten for what it is.

Because douing routing over several networks is to much work, I decide
to have all IP Sensors and cameras in a network with 512 IP adresses.

> Richard

Have a nice day

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Ethernet is not started at boot

[Michelle Konzack]

Hi,

Am 2018-02-07 hackte Brian in die Tasten:
> On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
>
>> On Tuesday 06 February 2018 14:07:55 Brian wrote:
>> >
>> > 1. auto enp0s25
>> >  iface enp0s25 inet
>> > static address 192.168.0.202
>> > netmask 255.255.255.0
>> > gateway 192.168.0.1
>> > network 192.168.0.0
>> >
>> > netmask and network are not needed. ifupdown will compute them. Note
>> > there are no examples in interfaces(5) which use these parameters.
>> >
>> You should go and read that man page again.
>
> I didn't have to but I did. A line beginning "netmask" is not required".
>
> Some reading for you:
>
> https://manpages.debian.org/stretch/ifupdown/interfaces.5.en.html

...and if you have a network with 512 IP adresses?
Section "The static Method" say definitively that I can use "netmask"
because auto configuration created to many problems in the past.

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Ethernet is not started at boot

[Michelle Konzack]

Good morning,

Am 2018-02-07 hackte Gene Heskett in die Tasten:
> On Tuesday 06 February 2018 14:07:55 Brian wrote:
>> 1. auto enp0s25
>>  iface enp0s25 inet
>> static address 192.168.0.202
>> netmask 255.255.255.0
>> gateway 192.168.0.1
>> network 192.168.0.0
>>
>> netmask and network are not needed. ifupdown will compute them. Note
>> there are no examples in interfaces(5) which use these parameters.
>>
> You should go and read that man page again.

Who do you mean?

I have als a network with

auto eth2
iface eth2 inet static
address 192.168.4.12
netmask 255.255.127.0
gateway 192.168.4.1
network 192.168.4.0

So, it is not so good idea to leafe it out

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Ethernet is not started at boot

[Michelle Konzack]

Good morning,

Am 2018-02-07 hackte Brian in die Tasten:
> Would you post the URL(s) for the instructions you refer to.

It is in the official install tutorial (Debian website) and they also
suggested some free Windows tools to do this.

I downloaded "rufus-2.18p.exe" to write the Iso to the USB Stick because
Windows 7 refused to let me execute "win32diskimager"

> Which ISOs have you downloaded?

amd64

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: How to safely hold kernel packages ?

[Jimmy Johnson]

On 02/06/2018 09:00 AM, Stéphane Rivière wrote:

Hi all,

I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also 
known as KPTI or kaiser CPU flaw. In my specific context, these patches 
are useless or even harmful.




Before applying an aptitude update/upgrade to all the servers and VMs 
I'm in charge, I've done a little test on a Debian 9 stable workstation, 
with the kernel linux-image-4.9.0-4-amd64 release 4.9.51-1


So, after an aptitude search ~i~linux- I hold theses meta-packages :

aptitude hold linux-image-amd64
aptitude hold linux-headers-amd64

Then I check the applied holds :

aptitude search ~ahold

ihA linux-headers-amd64
ih  linux-image-amd64

then... aptitude update/upgrade



After that... I discover a kernel change :

linux-image-4.9.0-4-amd64 release 4.9.65-3 (instead of previously 4.9.51-1)

Reading : 
http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_4.9.65-3+deb9u2_changelog 



I discovered I've perfectly applied the patch I wished to avoid.

linux (4.9.65-3+deb9u2) stretch-security; urgency=high
.../...
   * [amd64] Implement Kernel Page Table Isolation (KPTI, aka KAISER)
     (CVE-2017-5754)

Hopefully, there is a new "nokaiser" boot option !
(happy end).



So it seems I just learn that 'hold' aptitude command is for packet 
version (i.e 4.9.0-4), not for package security fixes versions 
(4.9.65-3)...


But is there a way to really *freeze* a packet (block all updates) ?

Is it the 'keep' aptitude option ? (can't really see the difference with 
'hold')


Or may be it's better to apply security patches and use the new 
"nokaiser" boot option...




Thanks a lot in advance for your advices ;)


All the best from France...


I would use 'apt-mark'.  # apt-mark hold 'package-name'
and # apt-mark unhold 'package-name'

Cheers,
--
Jimmy Johnson

Debian Stretch - KDE Plasma 5.8.6 - AMD A8-7600 - EXT4 at sda6
Registered Linux User #380263

Re: ODBC MariaDB Excel

[Paynalton]

Muchas gracias, allí estaba la solución.

Para el archivo:

Edité el fichero: /etc/mysql/mariadb.conf.d/50-server.cnf

y agregué las siguientes líneas en la sección [mysqld]

table_open_cache = 16384
table_definition_cache =16384
tmp_table_size =64M
join_buffer_size =512k



El vie., 2 de feb. de 2018 a la(s) 14:36, Galvatorix Torixgalva <
galvatorix2...@gmail.com> escribió:

> Hola,
>
> ¿has probado con esto? https://bugs.mysql.com/bug.php?id=42041
> ​
> Saludos
>

Re: getting the right and complete firmware

[Anil Duggirala]

> > I believe I have done a standard stretch install, yet /sbin/modinfo
> > ath10k_pci :
> > 
> > filename:   /lib/modules/4.9.0-5-
> > amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
> > firmware:   ath10k/QCA9377/hw1.0/board.bin
> > firmware:   ath10k/QCA9377/hw1.0/firmware-5.bin
> 
> [...]
> 
> I get this too.
> 
> If the device works with stretch's firmware-atheros I'd let things
> be.
> 
I guess I will let things be then, for now. Is it possible that a
future update to firmware-atheros will solve the problem? Is this
driver bluetooth related? My wifi works, I have not tested bluetooth
though.

Re: Installing Debian on Chuwi Hi12 Tablet

[Chris Dunn]

On Mon, 29 Jan 2018 20:08:05 +0100
Michael Lange  wrote :

>I don't know if the Debian Live system will handle the 32bit uefi issue
> properly when installing, but this can , if necessary be fixed later.
> I had the same problem with a similar machine. Of course I could  remove
> windows completely.
> I am not sure if the installer's auto-partitioning works properly, I used
> the manual partitioning. You must make sure that you have a small (I
> think 100 MB or so is sufficient) FAT partition with the "Boot" flag set,
> which will be mounted to /boot/efi . The rest of the disk can be used
> as usual for "/" and swap.
> If the installer actually fails to install the proper 32bit-efi-grub, that
> does not mean that your device is bricked. This can be easyly fixed by
> booting a live system again, doing a chroot into the installed system and
> install the required grub packages manually (that's what I had to do ;)

Michael thanks for your guidance. I eventually got around to installing
Debian Buster as I thought it was most likely to have my wifi driver (and
it did), so the install was much easier.

I guess the installer is continually evolving so things change fairly
quickly. The 32 bit uefi question never cropped up so I believe the
installer is just set to handle that without raising it.

I chose guided partitioning of the whole disk and it gave me 1mb free space
+ a 500+ mb EPT? partition + the bulk of the electronic drive for / + some
swap space 4mb? + another 1 mb of free space. Pressed go and held my
breath. It worked.

At the point of installing grub there was a slightly scary message to the
effect that on some hardware the uefi setups cannot be guaranteed to handle
grub properly so recommending installing grub to a separate partition as
that was almost certain to work and letting me choose which option. Chose
the separate partition and ended up with a successful install.

Thanks again for your help.

Now when I boot up the device I get 10 seconds of Android loading graphics
before it kicks into Debian. Android was removed months ago. Now if you can
give me some guidance as to how to remove the annoying Android graphics
..

Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-07 13:17:21 +1300, Richard Hector wrote:
> On 07/02/18 02:18, Vincent Lefevre wrote:
> > On 2018-02-06 14:36:31 +1300, Richard Hector wrote:
> >> The behaviour and policy of this list, when followed, does what I want.
> > 
> > But the other users cannot know what you want if you do not set
> > "Mail-Followup-To:".
> 
> It's not really up to me, is it. If you're replying to my mail, it's
> ultimately up to you to decide whether it's better to send to the list,
> or to me.

The "Mail-Followup-To:" header has no influence on this decision
(reply to the list with optional Cc's or private reply).

It allows the MUA to decide between:
  * send the mail to the list only;
  * send the mail to the list + Cc to you.
Actually, this is even more complex because other participants
of the discussion are also involved in the construction of the
"Mail-Followup-To:" header.

> My client (Thunderbird, at the moment) has a "Reply" button and a
> "Reply List" button, so I can make that choice.

Yes, but this is not what "Mail-Followup-To:". This header concerns
only "Reply List". The goal is that users who wish to be Cc'ed will
automatically be Cc'ed. And in case of a "Reply to all" (I suppose
that your MUA also has such a feature), the users who do not wish
to be Cc'ed will not be Cc'ed.

> What's important is that that choice isn't restricted. If you set
> Mail-Followup-To, you're attempting to make that choice for me (I
> haven't been following who sets what headers, so I'm not sure what
> Thunderbird does with it).

But this is precisely what the users want: "please Cc me in replies",
"please do not Cc me in replies". This is the goal of Mail-Followup-To
to handle this automatically.

> What's also reasonably important is that people don't accidentally send
> a private reply to the list, so any header (whether added by the sender
> or by the list) that causes the replying MUA to do that automatically
> is, IMHO, a mistake.

I repeat: the "Mail-Followup-To:" header has absolutely no influence
on that. A private reply will never consider this header.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Ethernet is not started at boot

[Michael Stone]

On Wed, Feb 07, 2018 at 01:26:05AM +, Brian wrote:

On Wed 07 Feb 2018 at 13:42:04 +1300, Richard Hector wrote:

The examples use CIDR notation instead, eg "address 192.168.1.1/24".

The netmask line is an alternative to that. You need to tell it
_somehow_ how big the subnet is.


As a changelog from May 2012 says:

 * Calculate netmask internally, so even if a user haven't supplied
   one or have used CIDR notation, hook scripts will have it properly
   specified in IF_NETMASK environment variable.


Richard is correct here. The changelog is saying that the IF_NETMASK 
environment variable will reflect the defaults even if they aren't 
specified in the configuration (this differs from the documentation 
which otherwise states that the environment will reflect the 
configuration file contents). It is *not* saying that ifupdown will 
somehow guess what the correct netmask is. As I said earlier, it 
defaults to setting the mask based on the address class, as defined in 
RFC 791 back in 1981. So, for example, a 10. IP will use a /8 netmask, a 
172. address will use a /16 netmask, etc. If you use a 192. address you 
might get lucky because those IPs were in the class C space and the 
netmask will default to /24--which is a common configuration for 
consumer network devices. But IP classes are obsolete and have been 
since the early 90s--so it's best not to rely on them being correct when 
setting up your network.


Mike Stone

Re: Ethernet is not started at boot

[Richard Hector]

On 07/02/18 14:29, Brian wrote:
> On Tue 06 Feb 2018 at 20:23:13 -0500, Michael Stone wrote:
> 
>> On Wed, Feb 07, 2018 at 01:16:28AM +, Brian wrote:
>>> On Tue 06 Feb 2018 at 19:53:16 -0500, Michael Stone wrote:
>>>
 On Tue, Feb 06, 2018 at 11:00:12PM +, Brian wrote:
> On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
>> On Tuesday 06 February 2018 14:07:55 Brian wrote:
>>>
>>> 1. auto enp0s25
>>>  iface enp0s25 inet
>>> static address 192.168.0.202
>>> netmask 255.255.255.0
>>> gateway 192.168.0.1
>>> network 192.168.0.0
>>>
>>> netmask and network are not needed. ifupdown will compute them. Note
>>> there are no examples in interfaces(5) which use these parameters.
>>>
>> You should go and read that man page again.
>
> I didn't have to but I did. A line beginning "netmask" is not required".

 If you don't specify a netmask it will default to something that was 
 correct
 in the 80s and is probably wrong on your network. The "netmask line" isn't
 required, but if you don't have a netmask line you should specify the
 netmask in the address line (using "ip/netmask" syntax).
>>>
>>> Indeed. But a netmask line (while not necessary) doesn't do any harm.
>>
>> More than that: either a separate netmask entry or a netmask specified as
>> part of the address are almost certainly required for proper operation. It's
>> not technically required, but it is practically required.
> 
> The changelog says:
> 
>   * Calculate netmask internally, so even if a user haven't supplied
> one or have used CIDR notation, hook scripts will have it properly
> specified in IF_NETMASK environment variable.
> 
> What is the significance of "...so even if a user haven't supplied ..."?

Calculate how? Using ancient classful addressing rules? Sounds like that
change is a bug, to me. Lack of a mask or prefix length should trigger
an error.

Richard



signature.asc
Description: OpenPGP digital signature

Re: Reply semantics (was Re: policy around 'wontfix' bug tag)

[Vincent Lefevre]

On 2018-02-06 10:47:30 -0500, The Wanderer wrote:
> On 2018-02-06 at 10:00, Vincent Lefevre wrote:
> 
> > On 2018-02-06 08:49:01 -0500, The Wanderer wrote:
> > 
> >> On 2018-02-06 at 08:18, Vincent Lefevre wrote:
> 
> >>> This is not contradictory with the setting of
> >>> "Mail-Followup-To:".
> >> 
> >> Arguably, if the mailing list does not default replies back to it
> >> normally, a responder who wishes to send a private reply may not
> >> be expecting that Reply will go to the mailing list, and so (when
> >> Mail-Followup-To is set to the list address) may fail to notice
> >> that adjusting the addressee list is needed.
> > 
> > If this is a private reply, the user should just use the "reply"
> > feature of his mailer. The reply will never go to the list. There is
> > no need to adjust anything.
> 
> That conflicts with the idea that the "reply" feature should always go
> to the correct place by default.

No! The "reply" feature *ALWAYS* goes to the correct place, whether
this is a mailing-list or not: to the "Reply-To:" address if present,
else to the "From:" address.

> When replying to a message from a mailing list, unless someone has taken
> actions to cause a different result, "reply" should direct the message
> to that mailing list.

No, this is a "list reply", not a "reply". A "list reply" should go
to the "Mail-Followup-To:" if present (typically the list + users who
wish to be Cc'ed), else to the list only (assuming that the message
has been posted to only one list).

> That is what "replies should go to the list by default" means.

There's no default. There are 3 separate, usual kinds of replies:
reply, list reply (both mentioned above), and group reply, a.k.a.
reply to all (reply to the "Mail-Followup-To:" if present, else
to all, i.e. sender + recipients).

> In fact, I've been assuming in this discussion that setting
> Mail-Followup-To will cause the "reply" feature to direct the reply to
> the address specified in that header. If that is the case, then using
> "reply" will not always produce a private reply; if it is not the case,
> then I'm not sure what good that header would be.

"Mail-Followup-To:" is just for list or group replies, which can
actually be the same in this case.

Note: There is actually a slight difference in Mutt: with list-reply,
Mutt will add the list address if it is not present in the
"Mail-Followup-To:" header; but normally, the list address should be
in this header, unless the goal is to redirect the discussion to a
different mailing-list (e.g. from an announce mailing-list to a user
mailing-list), though unfortunately one needs to use the "Reply-To:"
in practice, for MUA's that do not honor the "Mail-Followup-To:"
header.

> > Users don't want to have to look at the signature. They don't want
> > to add addresses manually. If a user requests that he wants to be
> > Cc'ed and I notice it, then I will tend to do a group-reply instead
> > of a list-reply.
> 
> Using "Reply to All" on a mailing list is usually the wrong thing to
> do, indeed.

No, this is typically what should be used for "bugs" mailing-lists,
and other mailing-lists where most users tend not to be subscribed.

> > unless the Mail-Followup-To is set up correctly, in which case
> > everything is fine: the users who do not want to be Cc'ed won't be
> > Cc'ed; the other users will be Cc'ed. Unfortunately some mailers
> > lose Mail-Followup-To information, but in general, this is better
> > than nothing.
> 
> Can you define what "correctly" would be, in this context, in your view,
> for someone who wants to receive replies only through the list unless
> the person replying is specifically attempting to draw that someone's
> attention?

The "Mail-Followup-To:" is a wish from the user who posted the
message. If he wants to receive replies only via the list, he
will configure his MUA not to put his address there. If some
other user wants to reply to the list and Cc the original user
despite the "Mail-Followup-To:", then he can always add the Cc
manually. But this is not something that should normally be done,
and this is probably useless. If you really want to draw the
original user's attention, then you should do a list reply + a
separate private reply mentioning the post to the list.

> The thing is: no matter what the configuration is, there will sometimes
> be cases when some people have to do manual work to get the right result.

But the point is that this should not be the common case.

> In the overwhelming majority of cases, the correct destination for a
> reply to a message posted on a public discussion mailing list is that
> mailing list. Cases which require private replies (either CCed or
> exclusive) are the exception, rather than the rule.

No. But note that "Mail-Followup-To:" covers the reply to the
list + optional Cc automatically. The only thing the user has
to think is whether he wants to send a reply to the list (+
automatic Cc if need be) or privately.

For instance, since you do not 

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 20:23:13 -0500, Michael Stone wrote:

> On Wed, Feb 07, 2018 at 01:16:28AM +, Brian wrote:
> > On Tue 06 Feb 2018 at 19:53:16 -0500, Michael Stone wrote:
> > 
> > > On Tue, Feb 06, 2018 at 11:00:12PM +, Brian wrote:
> > > > On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
> > > > > On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > > > > >
> > > > > > 1. auto enp0s25
> > > > > >  iface enp0s25 inet
> > > > > > static address 192.168.0.202
> > > > > > netmask 255.255.255.0
> > > > > > gateway 192.168.0.1
> > > > > > network 192.168.0.0
> > > > > >
> > > > > > netmask and network are not needed. ifupdown will compute them. Note
> > > > > > there are no examples in interfaces(5) which use these parameters.
> > > > > >
> > > > > You should go and read that man page again.
> > > >
> > > > I didn't have to but I did. A line beginning "netmask" is not required".
> > > 
> > > If you don't specify a netmask it will default to something that was 
> > > correct
> > > in the 80s and is probably wrong on your network. The "netmask line" isn't
> > > required, but if you don't have a netmask line you should specify the
> > > netmask in the address line (using "ip/netmask" syntax).
> > 
> > Indeed. But a netmask line (while not necessary) doesn't do any harm.
> 
> More than that: either a separate netmask entry or a netmask specified as
> part of the address are almost certainly required for proper operation. It's
> not technically required, but it is practically required.

The changelog says:

  * Calculate netmask internally, so even if a user haven't supplied
one or have used CIDR notation, hook scripts will have it properly
specified in IF_NETMASK environment variable.

What is the significance of "...so even if a user haven't supplied ..."?

-- 
Brian.

Re: Ethernet is not started at boot

[Brian]

On Wed 07 Feb 2018 at 13:42:04 +1300, Richard Hector wrote:

> On 07/02/18 08:07, Brian wrote:
> > netmask and network are not needed. ifupdown will compute them. Note
> > there are no examples in interfaces(5) which use these parameters.
> 
> The examples use CIDR notation instead, eg "address 192.168.1.1/24".
> 
> The netmask line is an alternative to that. You need to tell it
> _somehow_ how big the subnet is.

As a changelog from May 2012 says:

  * Calculate netmask internally, so even if a user haven't supplied
one or have used CIDR notation, hook scripts will have it properly
specified in IF_NETMASK environment variable.

-- 
Brian.

Re: Ethernet is not started at boot

[Michael Stone]

On Wed, Feb 07, 2018 at 01:16:28AM +, Brian wrote:

On Tue 06 Feb 2018 at 19:53:16 -0500, Michael Stone wrote:


On Tue, Feb 06, 2018 at 11:00:12PM +, Brian wrote:
> On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > >
> > > 1. auto enp0s25
> > >  iface enp0s25 inet
> > > static address 192.168.0.202
> > > netmask 255.255.255.0
> > > gateway 192.168.0.1
> > > network 192.168.0.0
> > >
> > > netmask and network are not needed. ifupdown will compute them. Note
> > > there are no examples in interfaces(5) which use these parameters.
> > >
> > You should go and read that man page again.
>
> I didn't have to but I did. A line beginning "netmask" is not required".

If you don't specify a netmask it will default to something that was correct
in the 80s and is probably wrong on your network. The "netmask line" isn't
required, but if you don't have a netmask line you should specify the
netmask in the address line (using "ip/netmask" syntax).


Indeed. But a netmask line (while not necessary) doesn't do any harm.


More than that: either a separate netmask entry or a netmask specified 
as part of the address are almost certainly required for proper 
operation. It's not technically required, but it is practically 
required.


Mike Stone

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 19:53:16 -0500, Michael Stone wrote:

> On Tue, Feb 06, 2018 at 11:00:12PM +, Brian wrote:
> > On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
> > > On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > > >
> > > > 1. auto enp0s25
> > > >  iface enp0s25 inet
> > > > static address 192.168.0.202
> > > > netmask 255.255.255.0
> > > > gateway 192.168.0.1
> > > > network 192.168.0.0
> > > >
> > > > netmask and network are not needed. ifupdown will compute them. Note
> > > > there are no examples in interfaces(5) which use these parameters.
> > > >
> > > You should go and read that man page again.
> > 
> > I didn't have to but I did. A line beginning "netmask" is not required".
> 
> If you don't specify a netmask it will default to something that was correct
> in the 80s and is probably wrong on your network. The "netmask line" isn't
> required, but if you don't have a netmask line you should specify the
> netmask in the address line (using "ip/netmask" syntax).

Indeed. But a netmask line (while not necessary) doesn't do any harm.

-- 
Brian.

Re: Ethernet is not started at boot

[Richard Hector]

On 07/02/18 04:54, Michelle Konzack wrote:
> Sorry, I ment dbus-x11

"apt-rdepends blueman" (you might want to install apt-rdepends) doesn't
list dbus-x11 anywhere. If blueman really needs it, then either it or
one of its other dependencies is failing to declare it, which would be a
bug.

Richard



signature.asc
Description: OpenPGP digital signature

Re: Ethernet is not started at boot

[Michael Stone]

On Tue, Feb 06, 2018 at 11:00:12PM +, Brian wrote:

On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:

On Tuesday 06 February 2018 14:07:55 Brian wrote:
>
> 1. auto enp0s25
>  iface enp0s25 inet
> static address 192.168.0.202
> netmask 255.255.255.0
> gateway 192.168.0.1
> network 192.168.0.0
>
> netmask and network are not needed. ifupdown will compute them. Note
> there are no examples in interfaces(5) which use these parameters.
>
You should go and read that man page again.


I didn't have to but I did. A line beginning "netmask" is not required".


If you don't specify a netmask it will default to something that was 
correct in the 80s and is probably wrong on your network. The "netmask 
line" isn't required, but if you don't have a netmask line you should 
specify the netmask in the address line (using "ip/netmask" syntax).


Mike Stone

Re: Ethernet is not started at boot

[Richard Hector]

On 07/02/18 08:07, Brian wrote:
> netmask and network are not needed. ifupdown will compute them. Note
> there are no examples in interfaces(5) which use these parameters.

The examples use CIDR notation instead, eg "address 192.168.1.1/24".

The netmask line is an alternative to that. You need to tell it
_somehow_ how big the subnet is.

Richard



signature.asc
Description: OpenPGP digital signature

coreutils date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

[Vincent Lefevre]

On 2018-02-06 13:07:53 -0300, Lucas Castro wrote:
> Em 06-02-2018 10:38, Vincent Lefevre escreveu:
> > On 2018-02-06 13:48:19 +0100, Vincent Lefevre wrote:
> > > This is completely crazy:
> > > 
> > > zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
> > > 2003-09-30
> > > zira% date +%Y-%m-%d -d '2003-09-01 1 day ago'
> > > 2003-08-31
> > > zira% date +%Y-%m-%d -d '2003-08-31 + 1 month'
> > > 2003-10-01
> > > 
> > > So, while '2003-09-01 1 day ago' gives 2003-08-31, the following
> > > are not equivalent:
> > >* '2003-09-01 1 day ago + 1 month'
> > >* '2003-08-31 + 1 month'
> > > 
> > > Where is the logic behind that?
> > Other ones:
> > 
> > zira% date +%Y-%m-%d -d '2003-02-01 - 1 month'
> > 2003-01-01
> > zira% date +%Y-%m-%d -d '2003-02-01 - 31 days'
> > 2003-01-01
> > zira% date +%Y-%m-%d -d '2003-02-01 - 31 days + 1 month'
> > 2003-01-29
> I guess first step done is the sum and then, subtract 31 days.
> So, as the fev is a month just with 28 days, end up at 2003-01-29.

According to --debug, it seems that operations on years are done
first, then months, then days. But this is not documented in the
Coreutils manual.

> > zira% date +%Y-%m-%d -d '2003-02-01 - 1 month + 1 month'
> > 2003-02-01

There's a bug on the same subject:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26101

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Ethernet is not started at boot

[Gene Heskett]

On Tuesday 06 February 2018 18:00:12 Brian wrote:

> On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > > 1. auto enp0s25
> > >  iface enp0s25
> > > inet static address 192.168.0.202
> > > netmask 255.255.255.0
> > > gateway 192.168.0.1
> > > network 192.168.0.0
> > >
> > > netmask and network are not needed. ifupdown will compute them.
> > > Note there are no examples in interfaces(5) which use these
> > > parameters.
> >
> > You should go and read that man page again.
>
> I didn't have to but I did. A line beginning "netmask" is not
> required".
>
For dynamic, but for static, read on down the page some more.

> Some reading for you:
>
> https://manpages.debian.org/stretch/ifupdown/interfaces.5.en.html

I am going by the man pages installed by stretch on a rock64. And looking 
at it just now as its building an rt-kernel, I see when its done, I need 
to do a make clean and see just why its building all the nouveau stuffs.  
It should only be building for dual mali cores. menuconfig isn't the 
best tool, it hides too much stuff.  Sigh...


-- 
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: policy around 'wontfix' bug tag

[Richard Hector]

On 07/02/18 02:18, Vincent Lefevre wrote:
> On 2018-02-06 14:36:31 +1300, Richard Hector wrote:
>> On 06/02/18 02:11, Vincent Lefevre wrote:
>>> You should set up a "Mail-Followup-To:" for that. This is entirely
>>> your problem.
>>
>> I could do that, I'm sure (though I'm not sure how) - but I'd rather
>> that someone intending to send me a private reply didn't send it to the
>> list by mistake. Having to (in my case) click 'Reply to List' helps me
>> not send to the list by mistake.
> 
> This is not contradictory with the setting of "Mail-Followup-To:".
> 
>> The behaviour and policy of this list, when followed, does what I want.
> 
> But the other users cannot know what you want if you do not set
> "Mail-Followup-To:".

It's not really up to me, is it. If you're replying to my mail, it's
ultimately up to you to decide whether it's better to send to the list,
or to me.

My client (Thunderbird, at the moment) has a "Reply" button and a "Reply
List" button, so I can make that choice.

What's important is that that choice isn't restricted. If you set
Mail-Followup-To, you're attempting to make that choice for me (I
haven't been following who sets what headers, so I'm not sure what
Thunderbird does with it).

What's also reasonably important is that people don't accidentally send
a private reply to the list, so any header (whether added by the sender
or by the list) that causes the replying MUA to do that automatically
is, IMHO, a mistake.

Nobody here (for a change) seems to be suggesting that the list adds the
Reply-To header, which is good - that can break private replies entirely.

Richard



signature.asc
Description: OpenPGP digital signature

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 17:11:03 -0500, Greg Wooledge wrote:

> On Tue, Feb 06, 2018 at 05:06:36PM -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > > netmask and network are not needed. ifupdown will compute them. Note
> > > there are no examples in interfaces(5) which use these parameters.
> > >
> > You should go and read that man page again.
> 
> In stretch, Brian is correct.

The OP has installed stretch. What other distribution would I be talking
about?
 
> In jessie and wheezy, Gene is correct.

Only with netmask. I suppose being half-misleading is better than being
totally misleading.

> Both of them seriously needs to learn how to delete lines of text.

Is that the best that can be done in response? A mini lecture on
trimming? Talk about shifting the goalposts; they are on their way to
becoming invisible!

At least two people are in total agreement that

 >  No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
 >  both.

Is this the accepted wisdom for now? auto and allow-hotplug cannot be
used at the same time? What happens if they are?

-- 
Brian.

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 17:06:36 -0500, Gene Heskett wrote:

> On Tuesday 06 February 2018 14:07:55 Brian wrote:
> >
> > 1. auto enp0s25   
> >  iface enp0s25 inet
> > static address 192.168.0.202
> > netmask 255.255.255.0
> > gateway 192.168.0.1
> > network 192.168.0.0
> >
> > netmask and network are not needed. ifupdown will compute them. Note
> > there are no examples in interfaces(5) which use these parameters.
> >
> You should go and read that man page again.

I didn't have to but I did. A line beginning "netmask" is not required".

Some reading for you:

https://manpages.debian.org/stretch/ifupdown/interfaces.5.en.html

-- 
Brian.

wicd vs network-manager

[RODARY Jacques]

Hi
I got rid of  network-manager: it endlessly  came back to the config it got 
when I installed Stretch,  and couldn't even resolve the URL of the debian 
repositories. 
But I have a problem with wicd: it knows about my two wired interfaces, but 
doesn't allow me to configure a connection on one of them and another on the 
second one. Where are the interfaces declared? 
Jacques

Re: systemd 237-1: problem starting dnsmasq

[Stefan Pietsch]

On 02.02.2018 21:20, Sven Hartge wrote:
> Stefan Pietsch  wrote:
> 
>> after the systemd upgrade from 236-3 to 237-1 (Debian sid) the dnsmasq
>> service does not start correctly.
> 
> I reported this as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144
> 
> It also affects munin-node
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889073 and ulogd2,
> quite possible other daemons as well.

dnsmasq 2.78-2 fixes the problem:
https://tracker.debian.org/news/930524


Regards,
Stefan

Re: Ethernet is not started at boot

[Greg Wooledge]

On Tue, Feb 06, 2018 at 05:06:36PM -0500, Gene Heskett wrote:
> On Tuesday 06 February 2018 14:07:55 Brian wrote:
> > netmask and network are not needed. ifupdown will compute them. Note
> > there are no examples in interfaces(5) which use these parameters.
> >
> You should go and read that man page again.

In stretch, Brian is correct.

In jessie and wheezy, Gene is correct.

Both of them seriously needs to learn how to delete lines of text.

Re: BUG depuis deux versions du noyau de testing

[Étienne Mollier]

Bonsoir,

Joël Bertrand, le 2018-05-02 :
>   Est-ce que je suis le seul à avoir des problèmes avec les
> noyaux de testing ?

J'utilise un noyau compilé maison, mais pas de problème de mon
côté du temps où il était en version 4.14.13.  Je n'ai pas
l'usage d'Apache 2 par contre.

> J'ai assez souvent la charge de mon serveur de test qui monte à
> plus de 500 (!) avec une occupation CPU de 0 et les logs
> remplis de :
>
> [226324.616534] BUG: Bad page map in process apache2 pte:0080
[...]
> [226324.616593] file:mod_reqtimeout.so fault:ext4_filemap_fault [ext4] 
> mmap:ext4_file_mmap [ext4] readpage:ext4_readpage [ext4]
> [226324.616597] CPU: 7 PID: 16832 Comm: apache2 Not tainted 4.14.0-3-amd64 #1 
> Debian 4.14.13-1
[...]
> [226324.616655] Disabling lock debugging due to kernel taint
[...]
> [233970.944487] file:liblber-2.4.so.2.10.8 fault:ext4_filemap_fault [ext4] 
> mmap:ext4_file_mmap [ext4] readpage:ext4_readpage [ext4]

Apparemment, l'erreur rencontrée est suffisament sérieuse pour
teinter le noyau.  Elle est provoquée lors de la montée en
mémoire du contenu de bibliothèques nécessaires au fonctionnement
d'apache2, ou tout du moins, du module concernant l'expiration
des requêtes...  Mais peut-être aussi que tout ce qui se raporte
de près ou de loin à LDAP est concerné :

$ find /usr/lib/ -name 'liblber*'
[...]
/usr/lib/x86_64-linux-gnu/liblber-2.4.so.2.10.8
$ dpkg -S /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2.10.8
libldap-2.4-2:amd64: /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2.10.8

>   Aucun autre symptôme, pas de swap anormal. La machine en
> question est un i7 3770 avec 16Go de mémoire. Pas d'erreur
> mémoire (memtest ne renvoie strictement rien). Seule solution,
> redémarrer la machine.

Le problème ne viendrait donc pas de la mémoire, c'est toujours
ça de pris.  Quand vous dites « aucun autre symptôme », le
service est-il toujours rendu par Apache ?

>   Lorsque le système part en vrille comme ça, je me
> retrouve avec plus de 2000 processus (contre 300 à 350 en
> fonctionnement normal). Mais un ps ne rend jamais la main, ce
> qui fait que je n'arrive même pas à isoler le fautif.  Je
> suspecte apache2 car le premier message d'erreur est toujours :
>
>   Bad page map in process apache2
>
>   Une idée ?

J'ai quelques idées de pertinence très inégale :

- Peut-être s'agit-il de problèmes de corruption de données sur
  disque.  Avez-vous eu l'occasion de contrôler l'état de la
  partition système via fsck, ou l'état du ou des disques
  sous-jacents ?

- Sinon, ça pourrait être un bug dans la pile d'appel au système
  de fichier ext4, mais j'y crois moyennement.  Le pilote ext4
  n'a pas reçu de mise à jour particulière entre les noyaux
  4.14.13 et 4.14.16 et étant donné sa large utilisation, ça se
  serait probablement vu.  Ou alors dans la gestion de la mémoire
  virtuelle, ce qui pourrait expliquer le blocage de ps ?...

- Pour élargir un peu le spectre, est ce que les autres journaux
  d'erreur mentionnent d'autres fichiers que mod_reqtimeout.so ou
  liblber-2.4.so.2.10.8, ou bien est ce que toutes les erreurs
  tournent autour de ces deux fichiers ?


Haricophile, le 2018-02-05 :
> Si c'était le kernel, je dirais un rapport avec le bugs Intel
> sur le calcul parallèle prédictif ? Un test en désactivant le
> patch je ne sais plus comment au démarrage (je n'ai pas suivi
> de près).

La remarque est pertinente étant donné la vitesse à laquelle les
patches ont dû être intégrés.

*À fin de débug* vous pouvez faire sauter le mécanisme en éditant
la commande de démarrage dans Grub.  Appuyez sur E pour éditer,
puis modifiez la commande linux pour ajouter « pti=off » pour
faire sauter le mécanisme Kaiser, permettant de se prémunir
contre Meltdown, et « spectre_v2=off » pour couper les mécanismes
de Retpolines, permettant de se prémunir contre la seconde
variante de Spectre.

Si vous n'avez pas facilement la main sur la console au
démarrage, vous pouvez toujours placer ces options dans
/etc/default/grub, dans la variable GRUB_CMDLINE_LINUX et lancer
un update-grub.

Si le noyau est assez récent, vous pouvez contrôler l'état de
protection contre les vulnérabilités CPU comme suit:

$ grep . /sys/devices/system/cpu/vulnerabilities/*

Sinon, il est aussi possible de consulter le journal de démarrage
du noyau pour vérifier l'état des patches via la commande
suivante :

$ sudo dmesg | grep -i 'spectre\|isolation'

*Rétablissez les patches de sécurité quand vous avez fini.*


À plus,
-- 
Étienne Mollier 

Re: Ethernet is not started at boot

[Gene Heskett]

On Tuesday 06 February 2018 14:07:55 Brian wrote:

> On Tue 06 Feb 2018 at 09:01:21 -0500, Greg Wooledge wrote:
> > On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
> > > On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
> > > > auto enp0s25
> > > > iface enp0s25 inet static
> > > > address 192.168.0.202
> > > > netmask 255.255.255.0
> > > > gateway 192.168.0.1
> > > > network 192.168.0.0
> > > >
> > > > allow-hotplug enp0s25
> > >
> > >   ^
> > > Doesn't the above line belong ABOVE the iface line? It has been in
> > > every example I've looked at. I am not using that line as its
> > > static, not dhcpd.
> >
> > No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but
> > not both.
>
> On the basis that whatever is not forbidden is allowed, I cannot see
> what the basis for this statement is from a reading of interfaces(5).
>
> (And what is wrong with having either auto or allow-hotplug below the
> iface line?)
>
> > If the interface is *important*, and you want services to wait for
> > it before starting, then you should use "auto".
>
> It is (in systemd terms) obliged to be run before network.target is
> reached.
>
> > If you use "allow-hotplug", this tells Debian that the interface is
> > optional, and services should feel free to start up before the
> > interface is ready.  This breaks ALL KINDS of shit on a traditional
> > workstation that participates in a network.  It's even worse on a
> > server.
>
> If you could use both - best of both worlds.
>
> > For some reason, Debian defaults to "allow-hotplug", perhaps because
> > they think most people are installing on laptops.
>
> I wonder whether it does the same as auto at boot time? Testing time?
>
> Two other points arising from other posts (reducing the number of
> moving parts should please someone):
>
> 1. auto enp0s25   
>  iface enp0s25 inet
> static address 192.168.0.202
> netmask 255.255.255.0
> gateway 192.168.0.1
> network 192.168.0.0
>
> netmask and network are not needed. ifupdown will compute them. Note
> there are no examples in interfaces(5) which use these parameters.
>
You should go and read that man page again.

> 2. auto lo
>iface lo inet loopback
>
> can be removed. ifupdown sorts this out all by itself. The stanza is
> put in by the installer because it has always done it; bug #836016.
>
> No example for loopback in interfaces(5) either.



-- 
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: Ethernet is not started at boot

[Bernd Gruber]

Hello Michell,
To try out, I just set up a new debian stretch on an VM (qemu/kvm):
I used the netinstall CD, because I didn't want to download full DVDs.

I had no problem configuring the network manually with ip-address and 
everything (only I didn't know exactly the addresses that are used by qemu, 
so in the end I had no connection and used the automatic setup, but the 
installer let me put in the values)
First I Installed only the base system.
Then installed the packages you mentioned (with APT::Install-Rcommends no; 
as thomas suggested).
I had everything done automatically. No problem.
The used disk-space is 1,4 GiB !

I know:
Grub instead of LILO and systemd instead of sys-v, if you relly do need 
these, I have no experience. You might try devuan.

Maybe there's a problem with your install medium or the repo on it.
Some time ago I had a directory as a local repository (only for self-built 
packages) to be used by apt, so I think this might ba a solution for your 
Problem with the usb-stick. I don't remeber exactly ho to configure this, 
but it wasn' too difficult (otherwise I wouldn' have done it).

Hope this can help you somehow.

Bernd

P.S: We have been to Estonia two years ago and liked it very much! Our 
daughter was studying in Tartu. And it was summer.



Michelle Konzack wrote:
> 
> The dependendies are only satisfait if you install a full DE like Gnome,
> KDE or  other defaults by Debian.
> 
> If you install the bare minimum like
> 
> Debian base
> xorg
> wdm
> fvwmg
fvwm
> thumb
gthumb 
> blueman
> alsa
no package alsa, took alsa-tools
> mc
> 
> you have a non-working system!
> 
>>> 11 Packages are now working and I try to figure out, WHICH  depends  are
>>> missing to write the appropriated Bug Reports.

Re: policy around 'wontfix' bug tag

[Brian]

On Mon 05 Feb 2018 at 22:55:51 -0500, The Wanderer wrote:

> On 2018-02-05 at 13:47, Brian wrote:
> 
> > On Mon 05 Feb 2018 at 10:24:14 -0500, The Wanderer wrote:
> 
> >> If there's an ongoing discussion on that mailing list, and one of
> >> the participants wants to draw in a third person who also
> >> subscribes, it's entirely appropriate to CC a reply to that third
> >> party.
> > 
> > Definitely (whether they are known to subscribe or not).
> > 
> > Which brings us back to - how does one know someone is subscribed to
> > a Debian mailing list?

I'll answer my own question; you side-stepped it: in the absence of
LDOSUBSCRIBER it is not possible to know.
 
> I still fail to see why that's something we would need to know.

Your implied question (a different one from mine) is: why might it be
useful to know whether a mail is from a subscribed user?

Replying to a list mail requires some effort on the part of reponders.
Knowing a user is subscribed gives no guarantee he will read the replies
or engage in the conversation he started, although obervation suggests
it is nearly always the case that most subscribed users do participate
in response to mails they send to the list. The effort a user puts into
responding is worth it.

Sending a mail which you have no idea (no LDOSUBSCRIBER) will be read by
the OP is a waste of time and effort.

There is no technical solution which can help in your making a decision
whether to reply or not. "Is he subscribed" leads to a judgement based
on a complete lack of evidence.

> Whether or not the person who posted a given message is subscribed does
> not change the correct replying behavior. In both cases, unless the
> poster has in some way requested otherwise, replies should go to the
> mailing list.

I am not arguing that point (I agree with it).

-- 
Brian.

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 15:53:24 +0200, Michelle Konzack wrote:

> I was following the instructions from the Debian Website and downloaded
> a Windows tool, which extract the content of an ISO image and copy it
> bootable on the USB Stick.
> 
> The second DVD was copied into a subfolder DVD2/
> 
> I could boot from USB, installed the base and rebooted.
> And now I could not more access the USB stick even if it was registered
> in /etc/apt/sources.list because apt want to mount a DVD Rom and not an
> USB Stick.
> 
> So, something is wrong in the install instructions

Would you post the URL(s) for the instructions you refer to.

Which ISOs have you downloaded?

-- 
Brian.

Conférence HYPNOSE - Comment transFormer vos peurs en élan vital

[[Hippocrate]]

 

Bonjour ,

 

VOUS VOUS SENTEZ BLOQUÉ(E) INTÉRIEUREMENT, C’EST LOURD ET CELA
VOUS EMPÊCHE D’AVANCER ?

Ca tombe bien... Car je vous prépare pour JEUDI 15 FÉVRIER UN
WEBINAIRE AVEC UN HOMME QUI VA VOUS APPRENDRE EN LIVE À TRANSFORMER
VOS PEURS, vos colères et vos poids en élan vital, grâce aux
ressources qui dorment en vous.

Cet homme, c’est GUILLAUME ANDREUX, PRATICIEN D’UNE AUTO-HYPNOSE
FACILE ET INTUITIVE.

En fait, il a décidé de VOUS DONNER SES OUTILS POUR AMÉLIOREZ VOS
ÉTATS GÊNANTS GRÂCE À UN LANGAGE INTÉRIEUR qui Change vos
Obstacles en Cadeaux.

 

Cliquez ici pour assister au webinaire « Améliorez vos Etats
Gênants grâce à un Langage Intérieur qui Change vos Obstacles en
Cadeaux »
[http://links.learnymail.fr/c/i5_/F2Mo/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/7c59bdc0

 

Je suis impatient de vous retrouver pour cette conférence qui va
CASSER AU MOINS UNE DE VOS CROYANCES LIMITANTES car Guilaume va vous
démontrer que :

 

_“L’AUTO-HYPNOSE N’EST PAS UN ÉTAT DE PERTE DE CONSCIENCE, MAIS
UNE HYPERCONSCIENCE DE VOS POSSIBILITÉS”_

Je prends le pari :

A la fin du webinaire, VOUS N’AUREZ PLUS CE GENRE DE CRAINTE : «
SOUS HYPNOSE, JE VAIS ME FAIRE MANIPULER, J’AI PEUR DE PERDRE LE
CONTRÔLE »,

car vous aurez compris qu’AVEC LES NOUVELLES MÉTHODES, PLUS
ACCESSIBLES, VOUS AVEZ AU CONTRAIRE PLUS DE CONTRÔLE SUR VOS
MÉCANISMES INTÉRIEURS et surtout…

… VOUS NE POUVEZ PAS ÊTRE VICTIME DE SUGGESTIONS NON VALIDÉES PAR
VOUS-MÊME car il n’y a pas d’hypnose sans auto-suggestion.

 

Ok, je participe au webinaire « Améliorez vos Etats Gênants grâce
à un Langage Intérieur qui Change vos Obstacles en Cadeaux »
[http://links.learnymail.fr/c/i5_/F2ML/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/c2b7292d

 

Vous savez , plus je parle avec Guillaume et plus je suis
convaincu d’une chose :

L’HYPNOSE N’EST PAS UN MOYEN DE VOUS MANIPULER À VOTRE INSU, MAIS
DE VOUS AUTO-INFLUENCER POUR DEVENIR MEILLEUR(E).

C’est aussi UN MERVEILLEUX MOYEN DE MIEUX VOUS CONNAÎTRE et de
devenir plus authentique,

Et c’est pour cette raison que je tiens à vous inviter à ce
webinaire « Améliorez vos Etats Gênants grâce à un Langage
Intérieur qui Change vos Obstacles en Cadeaux ».

 

Au jeudi 15  !

Amicalement,

Bertrand Canavy.

Praticien de Santé, Coach certifié en Santé

 

Et Guillaume Andreux

Praticien d’une Hypnose Facile et Intuitive depuis 7 ans

 

PS : , la méthode d’auto-hypnose qu’a développé
Guillaume n’est PAS UNE HYPNOSE DE SPECTACLE, DE RUE OU UNE HYPNOSE
DITE “SPIRITUELLE” où vous voyagez dans vos vies antérieures.

C’est une hypnose facile, naturelle et intuitive où vous allez :

-   CONTACTER, RÉVÉLER ET ACTIVER CE QUE VOTRE INCONSCIENT
GARDE précieusement et que votre conscient ne perçoit pas

-   ET RENCONTRER VOTRE IMAGINATION, votre ressenti et votre
langage intérieur pour les connecter à votre histoire…

Si vous voulez expérimenter cette hypnose qui se vit dans la pratique
et qui a pour but d’AUGMENTER VOTRE BIEN ÊTRE EN TRANSFORMANT VOTRE
CONSCIENCE, réservez tout de suite votre soirée du 15 février en
suivant ce lien :

Cliquez ici pour réserver votre place pour le webinaire « Améliorez
vos Etats Gênants grâce à un Langage Intérieur qui Change vos
Obstacles en Cadeaux »
[http://links.learnymail.fr/c/i5_/F2Mi/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/f9a5eb4d

 

Chaleureusement,

L'équipe HIPPOCRATE
cli...@hippocrate.net
[http://links.learnymail.fr/c/i5_/F2M7/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/256b9421
http://links.learnymail.fr/c/i5_/F2M2/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/0fd16aca
[http://links.learnymail.fr/c/i5_/F2MX/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/685cd281

 

  

Vous recevez cet e-mail car vous êtes référencé sur notre base de données.
Conformément à l'article 34 de la loi Informatique et Liberté du 6 janvier 1978,
vous disposez d'un droit d'accès, de modification, de rectification et de 
suppression
des données vous concernant.


Si vous souhaitez vous désinscrire, merci d'utiliser le lien suivant.
http://links.learnymail.fr/c/i5_/F2M6/iTn0sr4_8IGguYMfMo66R3/cbV/LySD/40560c03

Re: Package pinning on origin AND version

[Adam Cecile]

On 02/06/2018 02:16 PM, The Wanderer wrote:

On 2018-02-06 at 07:52, Adam Cecile wrote:


On 02/06/2018 01:46 PM, The Wanderer wrote:


Pin: version 1.3.*, release o=packages.le-vert.net

Hello,

Thanks for the answer, sadly it's not working:

mesos:
Installed: 1.3.1-1+Debian-stretch-9.1
Candidate: 1.4.1-1+Debian-stretch-9.1

Not sure what may be causing that. Just as a stab in the dark, maybe try
it with 'Pin-Priority: 1001', in case something else is setting the
priority of the 1.4.x version to 1000? (Again per 'man apt_preferences',
when two versions have equal priority, the higher version number wins
out.)

Note that a priority greater than 1000 will lead the matching version to
be considered even when it would be a version-number downgrade from the
installed version. That may be what you want (it often is, for me), but
it's something that's good to be aware of.

If you're interested in testing yourself, it's pretty easy both 
repositories are public:


echo "deb http://packages.le-vert.net/mesos/debian stretch main" > 
/etc/apt/sources.list.d/packages.le-vert.net_mesos.list
echo "deb http://repos.mesosphere.io/debian jessie main" > 
/etc/apt/sources.list.d/mesosphere.list


I guess the coma works only if you're using subfilters of "release", 
like as stated in the documentation.
So maybe what I'm trying to do is simply not supported, but I'd like to 
have a confirmation before I seek for a different solution (any hint 
would be appreciated...)


Regards, Adam.

Re: systemd 237-1: problem starting dnsmasq

[Stefan Pietsch]

On 06.02.2018 13:08, Maxim Gorbachyov wrote:
> Hi Stefan,
> 
> I've just hit the issue you mentioned in debian-user ML:
> https://lists.debian.org/debian-user/2018/01/msg01331.html
> 
> Have you got any feedback on that? I'm just running dnsmasq in
> terminal at the moment.. Do you have a better solution?

There's a Debian bug ID:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889144

My workaround is to run "dnsmasq -d".

Re: Ethernet is not started at boot

[Brian]

On Tue 06 Feb 2018 at 09:01:21 -0500, Greg Wooledge wrote:

> On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
> > > auto enp0s25 
> > > iface enp0s25 inet static
> > > address 192.168.0.202
> > > netmask 255.255.255.0
> > > gateway 192.168.0.1
> > > network 192.168.0.0
> > >
> > > allow-hotplug enp0s25
> >   ^
> > Doesn't the above line belong ABOVE the iface line? It has been in every 
> > example I've looked at. I am not using that line as its static, not 
> > dhcpd.
> 
> No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
> both.

On the basis that whatever is not forbidden is allowed, I cannot see
what the basis for this statement is from a reading of interfaces(5).

(And what is wrong with having either auto or allow-hotplug below the
iface line?)

> If the interface is *important*, and you want services to wait for it
> before starting, then you should use "auto".

It is (in systemd terms) obliged to be run before network.target is
reached.
 
> If you use "allow-hotplug", this tells Debian that the interface is
> optional, and services should feel free to start up before the
> interface is ready.  This breaks ALL KINDS of shit on a traditional
> workstation that participates in a network.  It's even worse on a
> server.

If you could use both - best of both worlds.

> For some reason, Debian defaults to "allow-hotplug", perhaps because
> they think most people are installing on laptops.

I wonder whether it does the same as auto at boot time? Testing time?

Two other points arising from other posts (reducing the number of moving
parts should please someone):

1. auto enp0s25 
iface enp0s25 inet static
address 192.168.0.202
netmask 255.255.255.0
gateway 192.168.0.1
network 192.168.0.0

netmask and network are not needed. ifupdown will compute them. Note
there are no examples in interfaces(5) which use these parameters.

2. auto lo
   iface lo inet loopback

can be removed. ifupdown sorts this out all by itself. The stanza is put
in by the installer because it has always done it; bug #836016.

No example for loopback in interfaces(5) either.

-- 
Brian.

Re: How to safely hold kernel packages ?

[Stéphane Rivière]

At first thanks you all for you good advices.

I will follow them, update kernels and apply the appropriate options 
(thanks for the link). I did not find what exactly is the nokaiser 
option and I will use nopti.


I agree dpkg-jiu-jitsu is an uncomfortable sport and understand i've 
hold the wrong (meta) packages.


All the best from here...

Stef

-

Finally, just for fun, my reasoning (for what it's worth), about 
avoiding these patches


Theses incompletes and CPU consuming patchs are *mandatory* if using 
(for example):


- A VM in a public cloud (wild neighborhood ;)
- A VM in a dedicated server which host others VM of different security 
level (datas, users and admins of different security levels)
- A multi-user system with users handling information at different 
levels of security


In my use case:

- Servers are real dedicated ones (no public or private cloud)
- Hypervisors and VMs are under control of people of same level security
- All VM are equal in a security point of view (datas & people involved)

Keep in mind theses flaws are (perhaps) useable if, and only if a VM is 
already infected (theses flaws needs a local running process !)


My reasoning is that if I have a wild running process in a VM, then this 
VM is compromised and I must simply destroy it !


I'm really concerned about security, performance and reliability. I talk 
about this with a lot of others OVH sysadmins customers (we share an ML 
called b...@ml.ovh.net (in french). But I do not pretend to be right, and 
also open to different points of view.


In any case :
- These hardware bugs are simply catastrophic.
- The patches applied are partial, with bads side-effects
- Some of the bugs can't be correcting (whithout changing the CPU)

--
Stéphane Rivière
Ile d'Oléron - France

Re: Causes, cures and prevention of orphaned inodes?

[Stephen P. Molnar]

On Tue, 2018-02-06 at 09:56 +1300, Ben Caradoc-Davies wrote:
> On 06/02/18 04:52, Stephen P. Molnar wrote:
> > I installed memtest86+ and ran it with all of the defaults.  It
> > took
> > over an hour, but no errors were reported.
> 
> Please try parallel memtester and stress. These found memory errors
> for 
> me that were not found by memtest86+.
> 
> In *eight* terminal windows as root run (noting that you have 8GB
> RAM):
> 
> memtester 768M
> 
> In one terminal window run (nothing that the FX-8320 has only 4 FPUs
> and 
> stress -c spins on sqrt):
> 
> stress -c 4
> 
> You can also tell memtester to use multiple iterations:
> 
> memtester 768M 10
> 
> > I am rather hesitant about updating the BIOS/UFEI.  In fact I can't
> > seem to find an upgrade for the FX-8320 on the AMD web site.
> 
> The BIOS/UEFI upgrade is an upgrade for your motherboard and can be 
> obtained from your motherboard vendor. For the Asus M5A97 R2.0:
> https://www.asus.com/us/Motherboards/M5A97_R20/HelpDesk_BIOS/
> 
> You are currently running "Version 2006 2013/10/16".
> Please try upgrading to "Version 2603 2015/07/24".
> 
> Note the multiple entries entitled "Improve system stability".
> 
> > Also, I'm rather hesitant about installing the amd64-package.
> 
> wat? Why? Modern CPUs are released full of microcode bugs. AMD
> release 
> new microcode that they wrote to fix these bugs in their microcode
> and 
> that they recommend. Why would you not use it?
> 
> Kind regards,
> 
-- 

Thank you for your fine and detailed email.  It has set my mind at ease.

Stephen P. Molnar, Ph.D.
Consultant
www.molecular-modeling.net
(614)312-7528 (c)
Skype: smolnar1

Re: How to safely hold kernel packages ?

[The Wanderer]

On 2018-02-06 at 12:00, Stéphane Rivière wrote:

> Hi all,
> 
> I wanted to avoid kernel updates after the Spectre/Meltdown 'bug',
> also known as KPTI or kaiser CPU flaw. In my specific context, these
> patches are useless or even harmful.

As indicated by Andy Smith, you should probably upgrade anyway and apply
a kernel command-line option to disable this behavior, since there are
other fixes included in the updated kernels.

> Before applying an aptitude update/upgrade to all the servers and VMs
> I'm in charge, I've done a little test on a Debian 9 stable
> workstation, with the kernel linux-image-4.9.0-4-amd64 release
> 4.9.51-1
> 
> So, after an aptitude search ~i~linux- I hold theses meta-packages :
> 
> aptitude hold linux-image-amd64 aptitude hold linux-headers-amd64
> 
> Then I check the applied holds :
> 
> aptitude search ~ahold
> 
> ihA linux-headers-amd64 ih  linux-image-amd64
> 
> then... aptitude update/upgrade
> 
> 
> 
> After that... I discover a kernel change :
> 
> linux-image-4.9.0-4-amd64 release 4.9.65-3 (instead of previously
> 4.9.51-1)

> So it seems I just learn that 'hold' aptitude command is for packet 
> version (i.e 4.9.0-4), not for package security fixes versions
> (4.9.65-3)...
> 
> But is there a way to really *freeze* a packet (block all updates) ?

There is. 'hold' should do it; I think you just held the wrong packages.

As I understand matters, linux-image-amd64 is a metapackage, or
something similar to one. It does not contain any actual kernel; it just
depends on another package, which does contain a kernel.

For example, linux-image-amd64 version 4.9* will depend on a
linux-image-4.9.*-amd64 package, and linux-image-amd64 version 4.14*
will depend on a linux-image-4.14*-amd64 package.

The "below" packages can get new versions even when the "above" package
doesn't; in fact, they very commonly do, since AFAIK most of the time
there's no need for a new linux-image-amd64 version except when
switching from e.g. 4.9.x to 4.14.x.

Once that other package is installed, if it has a new version available,
a mass "upgrade" command will cause that other package to be upgraded to
a new version - even if linux-image-amd64 itself doesn't have a new version.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: How to safely hold kernel packages ?

[Sven Hartge]

Stéphane Rivière  wrote:

> I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also 
> known as KPTI or kaiser CPU flaw.

No, it is not known as this.

> In my specific context, these patches are useless or even harmful.

Possible. You do know you can just add "pti=off" to the kernel command
line and switch it off, do you? 

No need to do dpkg-jiu-jitsu to prevent any packages from updating.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

Re: How to safely hold kernel packages ?

[Andy Smith]

Hello,

On Tue, Feb 06, 2018 at 06:00:16PM +0100, Stéphane Rivière wrote:
> So, after an aptitude search ~i~linux- I hold theses meta-packages :
> 
> aptitude hold linux-image-amd64
> aptitude hold linux-headers-amd64

I think you also would need to hold package
linux-image-4.9.0-4-amd64.

> Hopefully, there is a new "nokaiser" boot option !
> (happy end).

"pti=off", or "nopti":


> Or may be it's better to apply security patches and use the new "nokaiser"
> boot option...

This sounds like a better option because each kernel update will fix
a lot of other things, not only Meltdown.

Cheers,
Andy

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

Re: Ethernet is not started at boot

[Michelle Konzack]

Am 2018-02-06 hackte to...@tuxteam.de in die Tasten:
> On Tue, Feb 06, 2018 at 05:54:08PM +0200, Michelle Konzack wrote:
>> Sorry, I ment dbus-x11

> Ah, ok. No, it's not installed on my machine (I managed to avoid
> dbus up to now). But since you are doing bluetooth stuff, you are
> going to need dbus. And dbus-x11 is just the infrastructure to
> get the dbus user session started at the X11 login (other DEs
> like Gnome and KDE have other methods). So yes, dbus-x11 does
> make sense for you.

;-)

> I *guess* you might get away without dbus-x11, but then you'd
> have to start your dbus user session yourself (and somehow pass
> the relevant tidbits to all relevant environments, so the
> applications can "find" the dbus session). But I'm far from an
> expert here, since I've been avoiding that for years ;-)

Hmmm, if I find the time, I will look into it.  Sounds interesting

>> Recommends are not Depends and blueman depends on dbus-x11
>
> Not directly, as far as I can see... perhaps indirectly. Perhaps
> "aptitude why" sheds some light on that.

>> > Shudder :-)
>>
>> Such thing happen if someone is sitting the whole day in front of a
>> screen...  Hihihi!  Look for some puppies and o walking twice a day!
>
> I'm just an exported flowerpot from much farther south, and then,
> age brings the old cat in me which only
>
>> 
>>
>> They where born on 2017-11-20 and need very much attention!
>
> Nice. The "heat wave of +5°C" sounds most attractive :-)

In some days will will have again this heatwave... around 0-3°C!
The whole snow will melt and transform again anything into mud!

>> append="net.ifnames=0"
>>
>> However, I can not find in /proc or /sys the Kernel commandline.
>> In the older kernels the file was named "comandline" but it is
>> not more there.
>
> Oh, yes, it should be there: /proc/cmdline

Ah, that it was, and yes, the "append" stuff is not shown, because
I have setuop in Lilo three startup methods (runlevel 2, 3 and 4)
but it is not shown in /proc/cmdline.

I have only

BOOT_IMAGE=Home ro root=802

So, there is something wrong with "append"

> Yes, you might want to fix that first before decorating your
> kernel command line further.
>
>> In case of problems with runlevel 2 I want to boot directly into
>> another one and also I have a runlevel which launch a very special
>> environment, which can not be done trough telinit and I do not want
>> to do this as root.
>
> I see.

SELinux disallow it

>> I have still my CDs from Hamm, and on a DVD I have Buzz Rex and Bo.
>> Long time ago!
>
> :)
>
>> True, but currently anything is working fine.
>> Hmmm, what is the lifetime of 3Com 100base-TX Network adapters?
>
> No idea. Perhaps hundred years?

I wonder since many years why they do not break.

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Corte de energia y DRBD

[Ricky Gutierrez]

El día 6 de febrero de 2018, 10:57, Erick Ocrospoma
 escribió:
> Como esta armado el disco drbd0 ?

te refieres al disco ? , lo tengo montado en una partición secundaria por LVM ,

> Ahí claramente dice que en el nodo01 no hay disco, has revisado eso?
>
el disco lo tiene el node-01

/dev/drbd0   1.4T  6.2G  1.4T   1% /optnew





-- 
rickygm

http://gnuforever.homelinux.com

How to safely hold kernel packages ?

[Stéphane Rivière]

Hi all,

I wanted to avoid kernel updates after the Spectre/Meltdown 'bug', also 
known as KPTI or kaiser CPU flaw. In my specific context, these patches 
are useless or even harmful.




Before applying an aptitude update/upgrade to all the servers and VMs 
I'm in charge, I've done a little test on a Debian 9 stable workstation, 
with the kernel linux-image-4.9.0-4-amd64 release 4.9.51-1


So, after an aptitude search ~i~linux- I hold theses meta-packages :

aptitude hold linux-image-amd64
aptitude hold linux-headers-amd64

Then I check the applied holds :

aptitude search ~ahold

ihA linux-headers-amd64
ih  linux-image-amd64

then... aptitude update/upgrade



After that... I discover a kernel change :

linux-image-4.9.0-4-amd64 release 4.9.65-3 (instead of previously 4.9.51-1)

Reading : 
http://metadata.ftp-master.debian.org/changelogs/main/l/linux/linux_4.9.65-3+deb9u2_changelog


I discovered I've perfectly applied the patch I wished to avoid.

linux (4.9.65-3+deb9u2) stretch-security; urgency=high
.../...
  * [amd64] Implement Kernel Page Table Isolation (KPTI, aka KAISER)
(CVE-2017-5754)

Hopefully, there is a new "nokaiser" boot option !
(happy end).



So it seems I just learn that 'hold' aptitude command is for packet 
version (i.e 4.9.0-4), not for package security fixes versions (4.9.65-3)...


But is there a way to really *freeze* a packet (block all updates) ?

Is it the 'keep' aptitude option ? (can't really see the difference with 
'hold')


Or may be it's better to apply security patches and use the new 
"nokaiser" boot option...




Thanks a lot in advance for your advices ;)


All the best from France...

--
Stéphane Rivière
Ile d'Oléron - France

Re: Corte de energia y DRBD

[Erick Ocrospoma]

Como esta armado el disco drbd0 ?

Ahí claramente dice que en el nodo01 no hay disco, has revisado eso?

On Tue, Feb 6, 2018 at 7:15 AM Galvatorix Torixgalva <
galvatorix2...@gmail.com> wrote:

> Me temo que no, ya que lo que mencionas no lo conozco.
>
> Te pongo el link a una lista de livecd, a ver si hay suerte y alguna te
> resulta util.
>
> https://livecdlist.com/
> ​
>
-- 


Erick.


---
IRC :   zerick
Blog: http://zerick.me
About :  http://about.me/zerick
Linux User ID :  549567

Re: pipe como variable en bash

[Erick Ocrospoma]

Lo mejor que podrias hacer es comentar que es lo que quieres lograr, no
como crees que debes hacerlo y no te funciona :-)

Creo que te funcionaria como argumento si usas xargs:

# rtl_fm -f 43350 -s 20 -r 96000 -g 19.7 2>/dev/null | Efergy |
xargs MiScript.sh

Luego capturas el argumento en una variable (dentro del script)

On Sun, Feb 4, 2018 at 4:52 PM petrohs el compa obrero 
wrote:

> a mi se me ocurre
>
> export variable="$(rtl_fm -f 43350 -s 20 -r 96000 -g 19.7
> 2>/dev/null | Efergy)";
>
> y ya podrias usar la variable dentro de MiScript.sh
>

Otra forma también seria Esta de arriba, aunque debería ser ir asi:

export variable=$(rtl_fm -f 43350 -s 20 -r 96000 -g 19.7
2>/dev/null | Efergy)

Lo puedes guardar en el /etc/bash.bashrc, luego cargas dicha variable
dentro de tu script asi (lo puedes poner debajo del shebang, la primera
línea del script):

#!/bin.bash
. /etc/bash.bashrc


> On Sun, Feb 4, 2018 at 3:34 PM, fernando sainz <
> fernandojose.sa...@gmail.com> wrote:
>
>> El día 4 de febrero de 2018, 21:32, Josu Lazkano
>>  escribió:
>> > Buenas,
>> >
>> > Tengo un pequeño problema de scripting que no se como resolver.
>> > Dispongo de un comando que me da el consumo eléctrico de mi casa:
>> >
>> > # rtl_fm -f 43350 -s 20 -r 96000 -g 19.7 2>/dev/null | Efergy
>> >
>> > Lo que quiero es redirigir esta salida a un script en bash y tratar la
>> > salida como una variable. Algo así:
>> >
>> > # rtl_fm -f 43350 -s 20 -r 96000 -g 19.7 2>/dev/null | Efergy
>> > | MiScript.sh
>
>
>> >
>> > El problema es que no se como capturar la variable, he probado con
>> > "$1" pero solo sirve para argumentos.
>> >
>> > ¿Alguien me pude ayudar?
>> >
>> > Gracias por todo y un saludo.
>> >
>> > --
>> > Josu Lazkano
>> >
>>
>> No entiendo muy bien lo que preguntas.
>> Creo que podrías poner en tu script llamadas a "read" (man bash) que
>> lee una linea de la entrada estándar.
>>
>>
>>read [-ers] [-a aname] [-d delim] [-i text] [-n nchars] [-N
>> nchars] [-p
>>prompt] [-t timeout] [-u fd] [name ...]
>>   One line is read from the  standard  input,  or  from  the
>> file
>>   descriptor  fd supplied as an argument to the -u option,
>> and the
>>   first word is assigned to the first name, the second word
>> to the
>>   second  name, and so on, with leftover words and their
>> interven‐
>>   ing separators assigned to the last name.  If  there  are
>> fewer
>>   words read from the input stream than names, the remaining
>> names
>>   are assigned empty values.  The characters in IFS  are
>> used  to
>>   split  the  line  into words using the same rules the shell
>> uses
>>   for expansion (described above under Word Splitting).  The
>> back‐
>>   slash  character  (\)  may be used to remove any special
>> meaning
>>   for the next character read and for line continuation.
>> Options,
>>   if supplied, have the following meanings:
>>
>> S2.
>>
>>
>
>
> --
> "Cada cual según sus fuerzas, cada quien según sus necesidades..."
>
-- 


Erick.


---
IRC :   zerick
Blog: http://zerick.me
About :  http://about.me/zerick
Linux User ID :  549567

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 05:54:08PM +0200, Michelle Konzack wrote:
> Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
> > On Tue, Feb 06, 2018 at 03:53:24PM +0200, Michelle Konzack wrote:
> >> Do you have glib-x11 installed on your system?
> >
> > Hm. I don't find any library/package which has a similar name. I guess
> > you mean libglib, but I might guess wrong.
> 
> Sorry, I ment dbus-x11

[...]

Ah, ok. No, it's not installed on my machine (I managed to avoid
dbus up to now). But since you are doing bluetooth stuff, you are
going to need dbus. And dbus-x11 is just the infrastructure to
get the dbus user session started at the X11 login (other DEs
like Gnome and KDE have other methods). So yes, dbus-x11 does
make sense for you.

> The question is only, which package must pull in dbus-x11?

I don't see the explicit dependency at the moment, but you
can ask with

  aptitude why dbus-x11

> I assume blueman, because bluez can be also used without blueman.

I don't think so: all of bluez is deeply dependent on dbus.

> >> But glib-x11 has nothing to du with Recommends, because it is essential
> >> for a working blueman..
> >
> > Hm. Sorry. I can't find that package.
> 
> loock for dbus-x11

I *guess* you might get away without dbus-x11, but then you'd
have to start your dbus user session yourself (and somehow pass
the relevant tidbits to all relevant environments, so the
applications can "find" the dbus session). But I'm far from an
expert here, since I've been avoiding that for years ;-)

> 
> >> > [fine tuning of your package system]
> >>
> >> "fine tuning" is good, if you even don't know, what is missing!
> >
> > Seems you had already got rid of Recommends...
> 
> Recommends are not Depends and blueman depends on dbus-x11

Not directly, as far as I can see... perhaps indirectly. Perhaps
"aptitude why" sheds some light on that.

[...]

> > Shudder :-)
> 
> Such thing happen if someone is sitting the whole day in front of a
> screen...  Hihihi!  Look for some puppies and o walking twice a day!

I'm just an exported flowerpot from much farther south, and then,
age brings the old cat in me which only

> 
> 
> They where born on 2017-11-20 and need very much attention!

Nice. The "heat wave of +5°C" sounds most attractive :-)


> 
> > I see. I haven't much experience there: I'll have to look that up.
> > Perhaps someone with more experience can chime in here.
> 
> >> He sayed unknown device
> >
> > Yes. It seems that for some reason, the init script is trying
> > to bring up the device under its old name. So you might try to
> > boot once appending " net.ifnames=0" to your kernel command
> > line (I forgot how that is done with LILO, but I guess you know).
> 
> append="net.ifnames=0"
> 
> However, I can not find in /proc or /sys the Kernel commandline.
> In the older kernels the file was named "comandline" but it is
> not more there.

Oh, yes, it should be there: /proc/cmdline

> I was séarching for it, because I have to boot from LILO prompt in a
> non-default runlevel by using
> 
> append="3"
> 
> but it does not boot into runlevel 3.  It is always the default 2.
> 
> I do not know, where the error is.

Yes, you might want to fix that first before decorating your
kernel command line further.

> In case of problems with runlevel 2 I want to boot directly into
> another one and also I have a runlevel which launch a very special
> environment, which can not be done trough telinit and I do not want
> to do this as root.

I see.

[...]

> I have still my CDs from Hamm, and on a DVD I have Buzz Rex and Bo.
> Long time ago!

:)

> True, but currently anything is working fine.
> Hmmm, what is the lifetime of 3Com 100base-TX Network adapters?

No idea. Perhaps hundred years?

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

iEYEARECAAYFAlp53HkACgkQBcgs9XrR2kYYuQCfYzvst0JpeE+LtsilaISFh+/l
AewAniljIvpqhOptmbc/r+183jSECW+I
=Okli
-END PGP SIGNATURE-

Re: policy around 'wontfix' bug tag

[Lucas Castro]

Em 06-02-2018 10:38, Vincent Lefevre escreveu:

On 2018-02-06 13:48:19 +0100, Vincent Lefevre wrote:

This is completely crazy:

zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
2003-09-30
zira% date +%Y-%m-%d -d '2003-09-01 1 day ago'
2003-08-31
zira% date +%Y-%m-%d -d '2003-08-31 + 1 month'
2003-10-01

So, while '2003-09-01 1 day ago' gives 2003-08-31, the following
are not equivalent:
   * '2003-09-01 1 day ago + 1 month'
   * '2003-08-31 + 1 month'

Where is the logic behind that?

Other ones:

zira% date +%Y-%m-%d -d '2003-02-01 - 1 month'
2003-01-01
zira% date +%Y-%m-%d -d '2003-02-01 - 31 days'
2003-01-01
zira% date +%Y-%m-%d -d '2003-02-01 - 31 days + 1 month'
2003-01-29

I guess first step done is the sum and then, subtract 31 days.
So, as the fev is a month just with 28 days, end up at 2003-01-29.

zira% date +%Y-%m-%d -d '2003-02-01 - 1 month + 1 month'
2003-02-01


--
Lucas Castro

Re: Ethernet is not started at boot

[Michelle Konzack]

Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
> On Tue, Feb 06, 2018 at 03:53:24PM +0200, Michelle Konzack wrote:
>> Do you have glib-x11 installed on your system?
>
> Hm. I don't find any library/package which has a similar name. I guess
> you mean libglib, but I might guess wrong.

Sorry, I ment dbus-x11

>   Depends: libbluetooth3 (>= 4.91), libc6 (>= 2.4), libglib2.0-0 (>=
> 2.31.8),
> libpython3.5 (>= 3.5.0~b1), dconf-gsettings-backend |
> gsettings-backend,
> python3 (<< 3.6), python3 (>= 3.5~), dbus, bluez (>= 4.61),
> obexd-client
> (>= 0.47) | bluez-obexd, obexd-server (>= 0.47) | bluez-obexd,
> python3-dbus, python3-gi, notification-daemon, librsvg2-common,
> gnome-icon-theme, libpulse-mainloop-glib0, gir1.2-gtk-3.0,
> gir1.2-gdkpixbuf-2.0, gir1.2-glib-2.0, gir1.2-pango-1.0,
> gir1.2-notify-0.7, python3-cairo, python3-gi-cairo,
> gir1.2-appindicator3-0.1
>   Recommends: policykit-1

> No glib-x11 around, either...

dbus-x11 too

The question is only, which package must pull in dbus-x11?

I assume blueman, because bluez can be also used without blueman.

>> But glib-x11 has nothing to du with Recommends, because it is essential
>> for a working blueman..
>
> Hm. Sorry. I can't find that package.

loock for dbus-x11

>> > [fine tuning of your package system]
>>
>> "fine tuning" is good, if you even don't know, what is missing!
>
> Seems you had already got rid of Recommends...

Recommends are not Depends and blueman depends on dbus-x11

> Yes, but what/where is glib-x11? No package with this name, no package
> containing a file named like this (all on Debian Stretch, aka 9, aka
> stable). What am I missing?

Mistake be me:  dbus-x11


>> >> It is a huge work, especially when I currently work in my 5,6ha
>> forest
>> >> on my BioFarm in Estonia (-10°C and 30cm snow).
>> >
>> > That sounds like some amount of fun (I always complaing about Berlin
>> being
>> > too cold :-/
>>
>> :-D
>>
>> Normally our winter is colder up to -30°C (not very often, but it
>> happen)
>
> Shudder :-)

Such thing happen if someone is sitting the whole day in front of a
screen...  Hihihi!  Look for some puppies and o walking twice a day!



They where born on 2017-11-20 and need very much attention!

> I see. I haven't much experience there: I'll have to look that up.
> Perhaps someone with more experience can chime in here.

>> He sayed unknown device
>
> Yes. It seems that for some reason, the init script is trying
> to bring up the device under its old name. So you might try to
> boot once appending " net.ifnames=0" to your kernel command
> line (I forgot how that is done with LILO, but I guess you know).

append="net.ifnames=0"

However, I can not find in /proc or /sys the Kernel commandline.
In the older kernels the file was named "comandline" but it is
not more there.

I was séarching for it, because I have to boot from LILO prompt in a
non-default runlevel by using

append="3"

but it does not boot into runlevel 3.  It is always the default 2.

I do not know, where the error is.

In case of problems with runlevel 2 I want to boot directly into
another one and also I have a runlevel which launch a very special
environment, which can not be done trough telinit and I do not want
to do this as root.

> To be fair, hardware beneath this has changed *a lot*, although we
> perceive those boxes as just "PCs" from the outside. And nowadays
> network interfaces, mass storage, etc. "come and go" even on low
> end hardware. So I do understand how that has come. But OTOH, learning
> and hacking has become more difficult.

True

>> Seufz, I liked the time of Debian Slink 2.1 in 1999!
>> Anything was s easy!
>
> :-)

I have still my CDs from Hamm, and on a DVD I have Buzz Rex and Bo.
Long time ago!

>> I nailed in the past the ethN on the HWAddress.
>
> This is a good idea, but it has its downsides too: Whenever you
> exchange the network card (or move the disk to another "identical"
> box), things stop working. Sometimes it does what you want,
> sometimes it doesn't :-)

True, but currently anything is working fine.
Hmmm, what is the lifetime of 3Com 100base-TX Network adapters?

Long time ago, they where the best on the market and ALL of my
computers (which do not have Ethernet on board) have them...

At least since 18 years

> Cheers
> - -- tomás

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Reply semantics (was Re: policy around 'wontfix' bug tag)

[The Wanderer]

On 2018-02-06 at 10:00, Vincent Lefevre wrote:

> On 2018-02-06 08:49:01 -0500, The Wanderer wrote:
> 
>> On 2018-02-06 at 08:18, Vincent Lefevre wrote:

>>> This is not contradictory with the setting of
>>> "Mail-Followup-To:".
>> 
>> Arguably, if the mailing list does not default replies back to it
>> normally, a responder who wishes to send a private reply may not
>> be expecting that Reply will go to the mailing list, and so (when
>> Mail-Followup-To is set to the list address) may fail to notice
>> that adjusting the addressee list is needed.
> 
> If this is a private reply, the user should just use the "reply"
> feature of his mailer. The reply will never go to the list. There is
> no need to adjust anything.

That conflicts with the idea that the "reply" feature should always go
to the correct place by default.

When replying to a message from a mailing list, unless someone has taken
actions to cause a different result, "reply" should direct the message
to that mailing list. That is what "replies should go to the list by
default" means.

In fact, I've been assuming in this discussion that setting
Mail-Followup-To will cause the "reply" feature to direct the reply to
the address specified in that header. If that is the case, then using
"reply" will not always produce a private reply; if it is not the case,
then I'm not sure what good that header would be.

>>> But the other users cannot know what you want if you do not set 
>>> "Mail-Followup-To:".
>> 
>> They should not have to.
>> 
>> They should be able to assume that you have taken all necessary
>> actions to ensure that you see any replies you want to see.
>> 
>> That could involve setting the header, or it could involve
>> subscribing to the mailing list, or it could involve requesting
>> explicitly (in the body of the mail or in your signature) to be
>> CCed, or it could involve something else.
> 
> Users don't want to have to look at the signature. They don't want
> to add addresses manually. If a user requests that he wants to be
> Cc'ed and I notice it, then I will tend to do a group-reply instead
> of a list-reply.

Using "Reply to All" on a mailing list is usually the wrong thing to do,
indeed.

> This means that other users of the discussion will also be Cc'ed,

Unless you then go in and delete from your reply's To/CC list the
addresses of anyone who has not requested CCs, which admittedly is a bit
of a pain.

> unless the Mail-Followup-To is set up correctly, in which case
> everything is fine: the users who do not want to be Cc'ed won't be
> Cc'ed; the other users will be Cc'ed. Unfortunately some mailers
> lose Mail-Followup-To information, but in general, this is better
> than nothing.

Can you define what "correctly" would be, in this context, in your view,
for someone who wants to receive replies only through the list unless
the person replying is specifically attempting to draw that someone's
attention?


(Warning: wall of text incoming.)

The thing is: no matter what the configuration is, there will sometimes
be cases when some people have to do manual work to get the right result.

In the overwhelming majority of cases, the correct destination for a
reply to a message posted on a public discussion mailing list is that
mailing list. Cases which require private replies (either CCed or
exclusive) are the exception, rather than the rule.


If replies go to the poster by default, then achieving this correct
destination requires special action by either every single reply-er
(adjusting To:/Cc: by hand, or using a special reply function, different
from what would be used in replying to non-list mail), or potentially
even every single poster (configuring things so that Mail-Followup-To
gets set correctly, whatever "correctly" may be).

The effort involved in doing this may be minor, and spread out across
large numbers of people, but it still adds up to be a lot.

When this does not happen, there are two failure states. The less severe
is that people who are subscribed to the mailing list will get two
copies of the mail; the more severe is that replies which were intended
to be posted publicly will instead be sent privately. How bad either of
these things are is probably a matter of opinion.

(There's also the failure state when Mail-Followup-To settings get lost
or not respected, because one of the participants in the discussion is
using a mail client which does not handle them correctly, but that's
beyond my ability to properly assess.)


If replies go to the mailing list by default, then only a subset of
posters need to take special action: people who want private copies of
replies, people who reply to the first kind of person, and people who
want to reply privately.

The effort involved in doing this is in any given instance is
noticeable, and potentially irritating, but it is limited to only the
instances where any special action is needed. In the overwhelming
majority of cases, no effort will be required.

When the first type of 

Re: mac en rade

[Haricophile]

Le Tue, 06 Feb 2018 13:20:54 +0100,
Thomas Savary  a écrit :

> Et il y a encore des andouilles pour acheter les grosses m… de ces
> enf… !?

Mais certainement. Nous savons qu'il y a mieux, mais c'est moins cher.
Nous avons une image a préserver mon cher mosssieur.

https://www.paroles.net/boris-vian/paroles-j-suis-snob
https://www.youtube.com/watch?v=yFdYZQmQtcs

Re: mac en rade

[Pierre Malard]

Peut être pour plus très longtemps. Il est vrai que je ne suis pas près de 
passer sur la 10.13 à moins qu’Apple entame un virage à 180 ... ce que je ne 
crois guère.

-- 
Pierre Malard

> Le 6 févr. 2018 à 15:20, Stephane Ascoet  a 
> écrit :
> 
>> Le 06/02/2018 à 15:12, Pierre Malard a écrit :
>> Alors je maintiens, cessons de sur-considérer Mac OS X par cette aura de 
>> mystère. C’est bien un Unix et Apple a beau faire ce qu’il veut, il y a 
>> toujours moyen de s’appuyer sur Unix pour déjouer leurs pièges. Démarrez 
>> donc un Mac en mode « verbeux » ([command]+[V] au boot) vous verrez bien 
>> tous les messages qui s’affichent. Lunixiens, vous reconnaîtrez bien des 
>> choses… Idem lorsqu’il est lancé, ouvrez un terminal et tapez un « ps -ef », 
>> vous verrez que bien des processus vous sont tout à fait connus : cups, 
>> postgres, postfix/dovecot, log, …)
> 
> Tu preches un convaincu, j'etais un pionnier dans l'utilisation d'OS X pour 
> jouer le role qu'un GNU/Linux aurait pu tenir... de version en version, on 
> peut faire de moins en moins de chose: plus de serveur X11, scripts de 
> demarrage verrouilles... et plus du support d'installation de l'OS que l'on 
> souhaite...
> 
> Visiblement tu adores encore cet ecosysteme, tant mieux, mais jusqu'a quand 
> cela durera t-il? La chute risque d'etre severe.
> -- 
> Cordialement, Stephane Ascoet
> 

Debian Wheezy con Exim enviando spam

[Mauro Antivero]

Estimados, actualmente tengo un servidor corriendo Debian 7 Wheezy con 
Exim4 instalado para el envío de correos "internos", es decir una 
configuración básica para que envíe notificaciones sobre el estado del 
RAID, unattended-upgrades y cosas por el estilo.


Resulta que este servidor está enviando spam masivamente y me está 
generando unos buenos dolores de cabeza... Vamos por partes, primero la 
configuración básica que siempre hago con "dpkg-reconfigure exim4-config":


General type of mail configuration: internet site; mail is sent and 
received directly using SMTP.

System mail name: nombre-servidor.dominio
IP-addresses to listen on for incomming SMTP connections:127.0.0.1
Other destinations for which mail is accepted:nombre-servidor.dominio
Domains to relay mail for:en blanco
Machines to relay mail for:   en blanco
Keep number of DNS-queries minimal (Dial-on-Demand)?: No
Delivery method for local mail:   mbox format in /var/mail
Split configuration into small files?:No

Lo primero que pensé es que por algún error en la configuración el 
servidor había quedado configurado como open relay, pero no fue así. De 
hecho esto lo verifico con la siguiente página:


https://mxtoolbox.com/diagnostic.aspx

Y veo que tal como yo deseo el acceso SMTP al equipo está cerrado (solo 
escucha peticiones de localhost como se ve en la configuración de exim). 
Si hago "telnet  25" me rechaza la conexión.


Luego pensé, "hace rato que no lo actualizo (si ya sé, esto está mal, 
pero bueno, son cosas que pasan...), quizás se trate de un agujero de 
seguridad en exim o en algún otro paquete". Así que por supuesto hice:


apt-get update

apt-get -V upgrade (alguien más extraña aptitude???)

Pero nada, vaciaba la cola de exim y a los pocos minutos tenía cientos o 
miles de correos basura en espera de ser enviados...


Entonces sigo buscando y leyendo y caigo en que claro, puedo tener algún 
script alojado en el servidor que esté generando spam, pero cómo lo 
encuentro? Pues bueno, buscando un poco en Google hay mucha información 
al respecto, por ejemplo:


https://blog.twinbeeservers.com/email-sending-scripts-location/

https://www.servernoobs.com/check-spam-on-exim-mail-server/

https://www.inmotionhosting.com/support/email/exim/find-spam-script-location-with-exim

Como veran se trata basicamente (perdon, me anda mal la configuracion 
del teclado y me dejaron de funcionar los acentos!!!) de utilizar el 
siguiente "comandito", el cual esta muy bien explicado en las paginas 
anteriores:


grep cwd /var/log/exim_mainlog | grep -v /var/spool | awk -F"cwd=" 
'{print $2}' | awk '{print $1}' | sort | uniq -c | sort -n


En mi caso los logs de exim estan en /var/log/exim4/mainlog, pero cuando 
ejecuto ese comando sobre este archivo no devuelve absolutamente nada... 
Lo que sucede es que en mis logs de exim no figura en nigun caso (para 
ninguna línea) el parametro "cwd" y por ende el comando anterior no 
arroja ningún resultado. Es por esto que recurro a ustedes a ver si me 
pueden auydar...


Tambien me fije de tener habilitada la opcion "mail.add_x_header = On" 
en el archivo php.ini (de hecho estaba habilitado por defecto) pero en 
la cabecera de los correos no me aparece el bendito "X-PHP-Script" ni 
nada parecido como dicen aca que deberia de aparecer:


https://blog.twinbeeservers.com/email-sending-scripts-location/

https://forum.ivorde.com/find-php-scripts-that-use-mail-function-to-spam-in-your-linux-server-t19753.html

Les mando parte de una cabecera de ejemplo:

exim -Mvh 1ej3zv-0006VP-H0

1ej3zv-0006VP-H0-H
Debian-exim 102 104
<>
1517926403 0
-ident Debian-exim
-received_protocol local
-body_linecount 117
-max_received_linelength 249
-allow_unqualified_recipient
-allow_unqualified_sender
-frozen 1517926409
-localerror
XX
1
n...@replay.com

151P Received: from Debian-exim by clouseau.cepanet.com.ar with local 
(Exim 4.80)

id 1ej3zv-0006VP-H0
for n...@replay.com; Tue, 06 Feb 2018 11:13:23 -0300
037  X-Failed-Recipients: iv...@online.no
029  Auto-Submitted: auto-replied
067F From: Mail Delivery System 
019T To: n...@replay.com
059  Subject: Mail delivery failed: returning message to sender
056I Message-Id: 
038  Date: Tue, 06 Feb 2018 11:13:23 -0300

Como ven no aparece ninguna información del script desde el cual se 
genera el correo (cosa que en las páginas que referencié anteriormente 
si aparece claramente).


Y entonces hasta aca llegue. Les agradeceria mucho si me pueden ayudar 
porque la verdad que de momento no se como avanzar. Por lo pronto le 
paso mas informacion al respecto del servidor en donde se esta dando 
este problema:


uname -a

Linux clouseau 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux

apt-cache show exim4

Package: exim4
Version: 4.80-7+deb7u5

apt-cache show apache2

Package: apache2
Version: 2.2.22-13+deb7u12

Cualquier otra información que pueda ser 

coreutils date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

[Vincent Lefevre]

On 2018-02-06 09:01:58 -0500, rhkra...@gmail.com wrote:
> Just an attempt to get a more informative subject line--maybe
> somebody can improve it.

Corrected the subject. This is not related to bash at all (I'm under
zsh, BTW). The GNU date utility comes from the coreutils.

> On Tuesday, February 06, 2018 08:49:39 AM Greg Wooledge wrote:
> > On Tue, Feb 06, 2018 at 01:48:19PM +0100, Vincent Lefevre wrote:
> > > On 2018-02-05 09:39:12 -0500, Greg Wooledge wrote:
> > > > Anyway, here's what I came up with:
> > > > 
> > > > lastday() {
> > > > 
> > > > date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> > > > 
> > > > }
> > > 
> > > But the exact meaning of "month" seems undocumented, which may
> > > silently break in a future version (e.g. possibly as a consequence
> > > of a bug fix). So this is a good example of what you should *not*
> > > do.
> > 
> > If I have the luxury of writing in a real language, then I prefer
> > to use that language's date/time libraries, if they exist and don't
> > suck.
> > 
> > In bash, you get this, or you get to write your own date/time code
> > by hand.
> > 
> > > This is completely crazy:
> > > 
> > > Where is the logic behind that?
> > 
> > As noted by someone else earlier in this thread, date recently learned
> > a --debug option (this is my first time hearing about it), so let's
> > try that:
> > 
> > wooledg:~$ date --debug +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
> > date: parsed date part: (Y-M-D) 2003-09-01
> > date: parsed relative part: -1 day(s)
> > date: parsed relative part: +1 month(s) -1 day(s)
> > date: input timezone: -05:00 (set from system default)
> > date: warning: using midnight as starting time: 00:00:00
> > date: starting date/time: '(Y-M-D) 2003-09-01 00:00:00 TZ=-05:00'
> > date: warning: when adding relative months/years, it is recommended to
> > specify the 15th of the months date: warning: when adding relative days,
> > it is recommended to specify 12:00pm date: after date adjustment (+0
> > years, +1 months, -1 days),
> > date: new date/time = '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00'
> > date: '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00' = 1064894400 epoch-seconds
> > date: output timezone: -05:00 (set from system default)
> > date: final: 1064894400.0 (epoch-seconds)
> > date: final: (Y-M-D) 2003-09-30 04:00:00 (UTC0)
> > date: final: (Y-M-D) 2003-09-30 00:00:00 (output timezone TZ=-05:00)
> > 2003-09-30
> > 
> > So, it adds "a month" first, then subtracts "a day" second.  I suppose
> > I could have rearranged the sub-arguments to make that clearer, but
> > honestly, I stopped tweaking it once I had a working invocation.  It's
> > so fragile that I didn't want to change *anything* for fear of breaking
> > it.
> > 
> > In some cases, I dealt with this stuff using a truly ancient version
> > of GNU date from the sh-utils package, before coreutils existed.  Some
> > of the more modern invocations didn't work with the older program, so
> > I often had to find different tricks that would work.  I don't know
> > whether this was one such case.  It could have been.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Ethernet is not started at boot

[Michelle Konzack]

Am DATE hackte AUTHOR in die Tasten: Greg Wooledge
> On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
>> On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
>> > allow-hotplug enp0s25
>>   ^
>> Doesn't the above line belong ABOVE the iface line? It has been in every
>> example I've looked at. I am not using that line as its static, not
>> dhcpd.
>
> No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
> both.

I have already removed it.

> If the interface is *important*, and you want services to wait for it
> before starting, then you should use "auto".

> If you use "allow-hotplug", this tells Debian that the interface is
> optional, and services should feel free to start up before the
> interface is ready.  This breaks ALL KINDS of shit on a traditional
> workstation that participates in a network.  It's even worse on a
> server.

Grmpf!

> For some reason, Debian defaults to "allow-hotplug", perhaps because
> they think most people are installing on laptops.

Welcome to Windian.

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Reply semantics (was Re: policy around 'wontfix' bug tag)

[Vincent Lefevre]

On 2018-02-06 08:49:01 -0500, The Wanderer wrote:
> On 2018-02-06 at 08:18, Vincent Lefevre wrote:
> > On 2018-02-06 14:36:31 +1300, Richard Hector wrote:
> >> On 06/02/18 02:11, Vincent Lefevre wrote:
> >> 
> >>> You should set up a "Mail-Followup-To:" for that. This is
> >>> entirely your problem.
> >> 
> >> I could do that, I'm sure (though I'm not sure how) - but I'd
> >> rather that someone intending to send me a private reply didn't
> >> send it to the list by mistake. Having to (in my case) click 'Reply
> >> to List' helps me not send to the list by mistake.
> > 
> > This is not contradictory with the setting of "Mail-Followup-To:".
> 
> Arguably, if the mailing list does not default replies back to it
> normally, a responder who wishes to send a private reply may not be
> expecting that Reply will go to the mailing list, and so (when
> Mail-Followup-To is set to the list address) may fail to notice that
> adjusting the addressee list is needed.

If this is a private reply, the user should just use the "reply"
feature of his mailer. The reply will never go to the list. There
is no need to adjust anything.

> > But the other users cannot know what you want if you do not set 
> > "Mail-Followup-To:".
> 
> They should not have to.
> 
> They should be able to assume that you have taken all necessary actions
> to ensure that you see any replies you want to see.
> 
> That could involve setting the header, or it could involve subscribing
> to the mailing list, or it could involve requesting explicitly (in the
> body of the mail or in your signature) to be CCed, or it could involve
> something else.

Users don't want to have to look at the signature. They don't want to
add addresses manually. If a user requests that he wants to be Cc'ed
and I notice it, then I will tend to do a group-reply instead of a
list-reply. This means that other users of the discussion will also be
Cc'ed, unless the Mail-Followup-To is set up correctly, in which case
everything is fine: the users who do not want to be Cc'ed won't be
Cc'ed; the other users will be Cc'ed. Unfortunately some mailers lose
Mail-Followup-To information, but in general, this is better than
nothing.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 09:01:21AM -0500, Greg Wooledge wrote:
> On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
> > > auto enp0s25 
> > > iface enp0s25 inet static
> > > address 192.168.0.202
> > > netmask 255.255.255.0
> > > gateway 192.168.0.1
> > > network 192.168.0.0
> > >
> > > allow-hotplug enp0s25
> >   ^
> > Doesn't the above line belong ABOVE the iface line? It has been in every 
> > example I've looked at. I am not using that line as its static, not 
> > dhcpd.
> 
> No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
> both.
> 
> If the interface is *important*, and you want services to wait for it
> before starting, then you should use "auto".

Yes, totally agreed: I think you want auto and not allow-hotplug.
But then there's still that /etc/init.d/networking throwing an error
as if it were starting the "wrong" interface, while it should be
doing the moral equivalent of "ifup -a". Hmmm.

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

iEYEARECAAYFAlp5wEwACgkQBcgs9XrR2kYGcgCeORPh733f+tYPd+BwPRRQqPMk
0p4AniIJLC40LqLIu/cCTLwsQiQRsRG6
=rGhS
-END PGP SIGNATURE-

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 09:18:20AM -0500, Greg Wooledge wrote:
> On Tue, Feb 06, 2018 at 12:03:15PM +0200, Michelle Konzack wrote:
> > If you install the bare minimum like
> > 
> > Debian base
> > xorg
> > wdm
> > fvwmg
> > thumb
> > blueman
> > alsa
> > mc
> > 
> > you have a non-working system!
> 
> Um, what?  No.  That's not correct.
> 
> > yes, if you know, WHICH package you need, it can be installed manually
> > which is already confirmed by 3 Package  maintainers.
> 
> ... OK.  So, you install the packages you want.  Just like I do.
> No problem.  I even use fvwm.  Never heard of fvwmg though.

I think the 'g' belongs one line further (transpose 'g' and '\n').

> You seem to be doing a lot of weird, low-level, retro-style modifications
> to Debian.  Replacing systemd with sysvinit.  Replacing GRUB with LILO.
> Why?  What's the point of this?  To see how many different ways you can
> break it?

Ohmigod, the horrors =:-o

;-)

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

iEYEARECAAYFAlp5v7QACgkQBcgs9XrR2ka+ewCdEa5GYNMafis3W09mul7Aqs05
XPcAn1q4IeoxqMYsOPPehzBYBGd9YlTR
=pQD7
-END PGP SIGNATURE-

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 03:53:24PM +0200, Michelle Konzack wrote:
> Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
> > On Tue, Feb 06, 2018 at 12:03:15PM +0200, Michelle Konzack wrote:
> >> I do not know currently, except that blueman depends on  glib-x11  which
> >> is confirmed by the maintainer.  It seems gthumb has the same dependency
> >> because sinde blueman is working gthumb too.
> >
> > I can't parse very well your last sentence.
> 
> Do you have glib-x11 installed on your system?

Hm. I don't find any library/package which has a similar name. I guess
you mean libglib, but I might guess wrong.

For reference, here's what apt show has to say about blueman on my
box:

  tomas@trotzki:~$ apt show blueman
  Package: blueman
  Version: 2.0.4-1
  Priority: optional
  Section: x11
  Maintainer: Christopher Schramm 
  Installed-Size: 4959 kB
  Depends: libbluetooth3 (>= 4.91), libc6 (>= 2.4), libglib2.0-0 (>= 2.31.8),
libpython3.5 (>= 3.5.0~b1), dconf-gsettings-backend | gsettings-backend,
python3 (<< 3.6), python3 (>= 3.5~), dbus, bluez (>= 4.61), obexd-client
(>= 0.47) | bluez-obexd, obexd-server (>= 0.47) | bluez-obexd,
python3-dbus, python3-gi, notification-daemon, librsvg2-common,
gnome-icon-theme, libpulse-mainloop-glib0, gir1.2-gtk-3.0,
gir1.2-gdkpixbuf-2.0, gir1.2-glib-2.0, gir1.2-pango-1.0,
gir1.2-notify-0.7, python3-cairo, python3-gi-cairo,
gir1.2-appindicator3-0.1
  Recommends: policykit-1
  Homepage: https://github.com/blueman-project/blueman
  Tag: role::program, uitoolkit::gtk
  Download-Size: 1703 kB
  APT-Sources: http://ftp.de.debian.org/debian stretch/main amd64 Packages
  Description: Graphical bluetooth manager
   Blueman is a GTK+ bluetooth management utility for GNOME using bluez D-Bus

No glib-x11 around, either...

> > Anyway, since I have a similarly minimalistic system [...]

> > So it does try to install quite a bit, but far from the whole Gnome,
> 
> Looks quit the same, if I look in the install log

Ah, OK.

> > Do you have somewhere in your apt configuration an "Install-Recommends
> > no"?
> >
> > I have, for example in /etc/apt/apt.conf.d/95no-recommends:
> >
> >   APT::Install-Recommends no;
> 
> If I would say yes, it would install several 100 MByte more, which I
> absolutely not want.  I have nearly all packages installed, which I also
> had under Wheeze but Stretch is more then twice as bib as Wheeze.
> 
> The partition is 10 GByte big and I have only 1100 MByte left over.

OK, I see. Sorry if I sometimes ask things which may be obvious to
you.

[...]

> But glib-x11 has nothing to du with Recommends, because it is essential
> for a working blueman..

Hm. Sorry. I can't find that package.

> > [fine tuning of your package system]
> 
> "fine tuning" is good, if you even don't know, what is missing!

Seems you had already got rid of Recommends...

> > See above -- you need some tools to understand *why* the package system
> > "wants" to do things. One very nice one is the -s option to apt (or
> > apt-get),
> 
> apt does not tell me (Recommends/Suggests) that I need glib-x11 to get
> something working, because even if you have Recommends/Suggests set to
> no, apt-get show always what can be also installed together.

Yes, but what/where is glib-x11? No package with this name, no package
containing a file named like this (all on Debian Stretch, aka 9, aka
stable). What am I missing?

[...]

> I have just extracted my "base install" into a chroot and tried to
> install blueman but it does not suggest or recommend essential the
> essential package to get blueman working.
> 
> This has absolutely nothing to do with Recommends/Suggests.

Yes agreed, but... where is glib-x11? Is blueman complaining? in which
way?

[...]

> >> It is a huge work, especially when I currently work in my 5,6ha forest
> >> on my BioFarm in Estonia (-10°C and 30cm snow).
> >
> > That sounds like some amount of fun (I always complaing about Berlin being
> > too cold :-/
> 
> :-D
> 
> Normally our winter is colder up to -30°C (not very often, but it happen)

Shudder :-)

> > How did you do that exactly? How do you get two DVDs ont one stick?
> 
> I was following the instructions from the Debian Website and downloaded
> a Windows tool, which extract the content of an ISO image and copy it
> bootable on the USB Stick.
> 
> The second DVD was copied into a subfolder DVD2/
> 
> I could boot from USB, installed the base and rebooted.
> And now I could not more access the USB stick even if it was registered
> in /etc/apt/sources.list because apt want to mount a DVD Rom and not an
> USB Stick.
> 
> So, something is wrong in the install instructions
> 
> > I see... it should be possible to refer APT to a file system instead
> > of a DVD/CDROM.
> 
> But it seems not to work under Stretch, because in the past I have
> created from /var/cache/apt/archives a local mirror for other
> installations.

I see. I 

Re: systemd 237-1: problem starting dnsmasq

[Gene Heskett]

On Tuesday 06 February 2018 07:39:45 Tomasz Nowiński wrote:

> The same appears for me.

Same what? No Context, new thread. No clue what you are asking about.


-- 
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: Firefox lié à Google

[Maxime]

Bonjour,

Le mercredi 31 janvier 2018 à 00:41 +0100, Haricophile a écrit :
> Tu cherche Google dans about:config et tu va comprendre que tu peux
> dégoogleiser firefox :
> 
> Moteur de recherche : exit
> "Protection contre les sites frauduleux..." : exit

Bêtement je n'avait jamais eu l'idée de soupçonner la protection contre les site
frauduleux (du coup sa ma surpris, même si c'était en fait évident, fallait bien
que la vérification se fasse quelque part), alors en effet Mozilla indiques
comuniquer des informations avec ses partenaires dans le cadre de l'utilisation
de cette fonction :

  https://support.mozilla.org/fr/kb/comment-fonctionne-protection-contre-hame%C3
%A7onnage-et-logiciels-malveillants#w_quelles-informations-sont-envoyaees-aa-
mozilla-ou-ses-partenaires-quand-les-protections-contre-lhameadonnage-et-les-
logiciels-malveillants-sont-activaeesa

Mais d’après leurs explications, elles ont l'aire vraiment minimal et ne
semblent par permettre le profilage. Du coup de me demande si dans le cas de la
désactivation de cette fonction de protection, le remède n'est pas pire que le
mal.

Pour complété avec un peut de hors sujet :

- NoScript est bien pratique en permettant de bloquer au cas par cas le
javascript  en fonction des domaines émetteurs dans une page (y compris les
diférents service de google)
- Sous Debian on a le paquet xul-ext-lightbeam qui fournis une extension
permettant d'identifier les interactions entres les différent domaines visités.

On peut aussi se référer à la partis "Analyse et optimisation:" de cette page :

  https://www.mozilla.org/fr/privacy/websites/

-- 
Maxime.
PGP : B8D0 6988 5DAC DA7B 7751  FD11 6AF9 C36F 6E55 E3E6
Ğ1 : 7vAhNi1mAjQZAD9kmioVVaDqcJedAHBXx84Tn5YtArhL

signature.asc
Description: This is a digitally signed message part

Re: mac en rade

[Stephane Ascoet]

Le 06/02/2018 à 15:12, Pierre Malard a écrit :

Alors je maintiens, cessons de sur-considérer Mac OS X par cette aura de 
mystère. C’est bien un Unix et Apple a beau faire ce qu’il veut, il y a 
toujours moyen de s’appuyer sur Unix pour déjouer leurs pièges. Démarrez donc 
un Mac en mode « verbeux » ([command]+[V] au boot) vous verrez bien tous les 
messages qui s’affichent. Lunixiens, vous reconnaîtrez bien des choses… Idem 
lorsqu’il est lancé, ouvrez un terminal et tapez un « ps -ef », vous verrez que 
bien des processus vous sont tout à fait connus : cups, postgres, 
postfix/dovecot, log, …)


Tu preches un convaincu, j'etais un pionnier dans l'utilisation d'OS X 
pour jouer le role qu'un GNU/Linux aurait pu tenir... de version en 
version, on peut faire de moins en moins de chose: plus de serveur X11, 
scripts de demarrage verrouilles... et plus du support d'installation de 
l'OS que l'on souhaite...


Visiblement tu adores encore cet ecosysteme, tant mieux, mais jusqu'a 
quand cela durera t-il? La chute risque d'etre severe.

--
Cordialement, Stephane Ascoet

Re: Ethernet is not started at boot

[Greg Wooledge]

On Tue, Feb 06, 2018 at 12:03:15PM +0200, Michelle Konzack wrote:
> If you install the bare minimum like
> 
> Debian base
> xorg
> wdm
> fvwmg
> thumb
> blueman
> alsa
> mc
> 
> you have a non-working system!

Um, what?  No.  That's not correct.

> yes, if you know, WHICH package you need, it can be installed manually
> which is already confirmed by 3 Package  maintainers.

... OK.  So, you install the packages you want.  Just like I do.
No problem.  I even use fvwm.  Never heard of fvwmg though.

> They  assumed,
> that Debian User install always  a  complete  system,  but  where  not
> thinking on users which do not need a full DE.

Baloney.  I install without a DE all the time.  I've got two stretch
systems (one at work, one at home) that I installed without a DE.  I'm
writing this email on one of them.

> Hence, some packages missing dependencies.

Nonsense.  There is literally NO "apt-get install" command you can issue
that will cause your system to have "missing dependencies".  If apt can't
find all the dependencies for your requested packages, it does nothing.

You've broken something some OTHER way.  Perhaps by "removing systemd"?

It would help a whole lot if you told us HOW you "removed systemd" and
what you replaced it with.  Exactly how.  Step by step.  Every single
command you issued, in order.

Or, try this experiment: do a base install and LEAVE SYSTEMD ALONE.
Then install the packages you want (fvwm, etc.).

Be sure to change "allow-hotplug" to "auto" in /e/n/i and reboot.

Does it work?  Does your network interface consistently come up
before your network-dependent services?

Now that you have a working Debian system with systemd and your desired
packages, you can either leave it alone, or attempt to replace systemd
with your desired init system.  If this step causes the breakage that
you reported earlier, THEN we know that the problem comes from whatever
crazy steps you are performing to replace your init system.  And we can
move on from there.

> I will install a second stretch in a VM and install only  the  minimum
> and then Package by Package to  figure  out,  which  dependencies  are
> missing.

OK.  Sounds like a reasonable approach.  Be sure to keep a log of all
your steps.  No "writing it down".  Use script(1) or something.

> Yes, because Debian Stretch does not more boot and I can not see the
> Lilo command prompt

You should be using GRUB, not LILO.

You seem to be doing a lot of weird, low-level, retro-style modifications
to Debian.  Replacing systemd with sysvinit.  Replacing GRUB with LILO.
Why?  What's the point of this?  To see how many different ways you can
break it?

Re: mac en rade

[Pierre Malard]

> Le 6 févr. 2018 à 13:10, Belaïd  a écrit :
> 
> Au faite c'etait déjà le cas depuis sierra,  ils transferent le Bureau ainsi 
> que le dossier Document sur le compte iCloud , et c'est pas vraiment cool

Ben ça, pour le coup, c’est bien ce que je disais : ça tient du mystère et de 
la magie dont on entoure le Mac.
Je travaille aussi sur Mac, sous Sierra (10.12), et jamais mon bureau, ni mon 
dossier « Document » n’ont été déplacés. Je me souviens que l’installation 
demande et promeut l’utilisation d’iCloud pour ses données personnelles 
(documents, trousseau d’accès, …), personne n’est obligé d’accepter, j’ai 
refusé. En tout état de cause, tout est chez moi et pas chez Apple à part ce 
que je veux bien y mettre : rien.

Pour ce qui est des installations, il est vrai qu’Apple emm.. le monde en 
refusant d’installer un paquet non signé par eux d’emblée, il suffit d’aller 
dans les préférence et cliquer sur le bouton « installer quand même » pour que 
ça marche et on peut même lui dire de fermer sa gueule définitivement avec un « 
sudo spctl --master-disable » dans un terminal. Pas très compliqué… 
(http://www.macbookcity.fr/astuces/3575/ouvrir-les-apps-non-identifiees-sur-macos-sierra).

Alors je maintiens, cessons de sur-considérer Mac OS X par cette aura de 
mystère. C’est bien un Unix et Apple a beau faire ce qu’il veut, il y a 
toujours moyen de s’appuyer sur Unix pour déjouer leurs pièges. Démarrez donc 
un Mac en mode « verbeux » ([command]+[V] au boot) vous verrez bien tous les 
messages qui s’affichent. Lunixiens, vous reconnaîtrez bien des choses… Idem 
lorsqu’il est lancé, ouvrez un terminal et tapez un « ps -ef », vous verrez que 
bien des processus vous sont tout à fait connus : cups, postgres, 
postfix/dovecot, log, …)

Codialement

> 
> Le 6 févr. 2018 11:17, "Stephane Ascoet"  > a écrit :
> Le 06/02/2018 à 11:14, Pierre Malard a écrit :
> Tout à fait d’accord sur le verrouillage (Apple, M$, Google même combat) mais 
> je ne vois pas le rapport avec ce qui était écrit. Je voulais juste exprimer 
> le fait qu’il y a toujours un parfum de mystère dès qu’on évoque un Mac alors 
> que c’est tout simplement un ordinateur qui fonctionne, au fond, comme tous 
> les
> 
> Justement non, ce n'est plus le cas. On ne peut absolument plus installer ce 
> que l'on veut.
> 
> D'ailleurs, s'il y a des macounets qui lisent ceci, mefiez-vous: il 
> semblerait que High Sierra *deplace* le contenu du dossier personnel sur les 
> serveurs Apple sans preavis. Plein de gens auraient tout perdu...
> --
> Cordialement, Stephane Ascoet
> 

--
Pierre Malard

   « Je n'ai jamais séparé la République des idées de justice sociale,
 sans laquelle elle n'est qu'un mot »
  Jean Jaures - 
1887
   |\  _,,,---,,_
   /,`.-'`'-.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ 
(  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 
24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--



signature.asc
Description: Message signed with OpenPGP

bash date behavior (buggy) (was: Re: policy around 'wontfix' bug tag)

[rhkramer]

Just an attempt to get a more informative subject line--maybe somebody can 
improve it.

On Tuesday, February 06, 2018 08:49:39 AM Greg Wooledge wrote:
> On Tue, Feb 06, 2018 at 01:48:19PM +0100, Vincent Lefevre wrote:
> > On 2018-02-05 09:39:12 -0500, Greg Wooledge wrote:
> > > Anyway, here's what I came up with:
> > > 
> > > lastday() {
> > > 
> > > date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> > > 
> > > }
> > 
> > But the exact meaning of "month" seems undocumented, which may
> > silently break in a future version (e.g. possibly as a consequence
> > of a bug fix). So this is a good example of what you should *not*
> > do.
> 
> If I have the luxury of writing in a real language, then I prefer
> to use that language's date/time libraries, if they exist and don't
> suck.
> 
> In bash, you get this, or you get to write your own date/time code
> by hand.
> 
> > This is completely crazy:
> > 
> > Where is the logic behind that?
> 
> As noted by someone else earlier in this thread, date recently learned
> a --debug option (this is my first time hearing about it), so let's
> try that:
> 
> wooledg:~$ date --debug +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
> date: parsed date part: (Y-M-D) 2003-09-01
> date: parsed relative part: -1 day(s)
> date: parsed relative part: +1 month(s) -1 day(s)
> date: input timezone: -05:00 (set from system default)
> date: warning: using midnight as starting time: 00:00:00
> date: starting date/time: '(Y-M-D) 2003-09-01 00:00:00 TZ=-05:00'
> date: warning: when adding relative months/years, it is recommended to
> specify the 15th of the months date: warning: when adding relative days,
> it is recommended to specify 12:00pm date: after date adjustment (+0
> years, +1 months, -1 days),
> date: new date/time = '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00'
> date: '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00' = 1064894400 epoch-seconds
> date: output timezone: -05:00 (set from system default)
> date: final: 1064894400.0 (epoch-seconds)
> date: final: (Y-M-D) 2003-09-30 04:00:00 (UTC0)
> date: final: (Y-M-D) 2003-09-30 00:00:00 (output timezone TZ=-05:00)
> 2003-09-30
> 
> So, it adds "a month" first, then subtracts "a day" second.  I suppose
> I could have rearranged the sub-arguments to make that clearer, but
> honestly, I stopped tweaking it once I had a working invocation.  It's
> so fragile that I didn't want to change *anything* for fear of breaking
> it.
> 
> In some cases, I dealt with this stuff using a truly ancient version
> of GNU date from the sh-utils package, before coreutils existed.  Some
> of the more modern invocations didn't work with the older program, so
> I often had to find different tricks that would work.  I don't know
> whether this was one such case.  It could have been.

Re: Ethernet is not started at boot

[Greg Wooledge]

On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
> On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
> > auto enp0s25 
> > iface enp0s25 inet static
> > address 192.168.0.202
> > netmask 255.255.255.0
> > gateway 192.168.0.1
> > network 192.168.0.0
> >
> > allow-hotplug enp0s25
>   ^
> Doesn't the above line belong ABOVE the iface line? It has been in every 
> example I've looked at. I am not using that line as its static, not 
> dhcpd.

No.  You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
both.

If the interface is *important*, and you want services to wait for it
before starting, then you should use "auto".

If you use "allow-hotplug", this tells Debian that the interface is
optional, and services should feel free to start up before the
interface is ready.  This breaks ALL KINDS of shit on a traditional
workstation that participates in a network.  It's even worse on a
server.

For some reason, Debian defaults to "allow-hotplug", perhaps because
they think most people are installing on laptops.

Re: policy around 'wontfix' bug tag

[David Wright]

On Tue 06 Feb 2018 at 16:38:53 (+1100), Erik Christiansen wrote:

> […] is python that monstrosity which
> lacks code block delimiting, and so uses indenting in lieu?

Nice to see your criticism is so shallow.

Cheers,
David.

Re: policy around 'wontfix' bug tag

[Michael Stone]

On Tue, Feb 06, 2018 at 04:38:53PM +1100, Erik Christiansen wrote:

On 05.02.18 10:02, Michael Stone wrote:

IIRC it started out as a YACC function in the late 80s, and is now a Bison
(YACC+GNU extensions) library.


In that case it has a precise grammar, expressed in BNF (Backus Naur
Form), though the lexer (I've always used lex together with
yacc/bison) could add a bit of elastic if the designer had a
free-wheeling approach. The existing flexibility then arises primarily
from explicit alternatives in grammar rules.


That's what makes it "explainable but not predictable" for the average
human. It's certainly possible to rationalize any given output (it's not 
coming from a random number generator) but it's too complicated for most 
people to easily predict the syntax that will give them the result they 
want.


Mike Stone

Re: policy around 'wontfix' bug tag

[David Wright]

On Tue 06 Feb 2018 at 13:48:19 (+0100), Vincent Lefevre wrote:
> On 2018-02-05 09:39:12 -0500, Greg Wooledge wrote:
> > (*) One specific shell script use case was "Get the last date of a given
> > month."  Now, obviously you can just set up an array of hard-coded month
> > ending dates, and then write a function to determine whether the current
> > year is a leap year for the February case.  But if you want to do it with
> > GNU date -d, then you have to guess a magic incantation that actually
> > works.  Usually by trial and error.
> > 
> > Anyway, here's what I came up with:
> > 
> > lastday() {
> > date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> > }
> 
> But the exact meaning of "month" seems undocumented, which may
> silently break in a future version (e.g. possibly as a consequence
> of a bug fix). So this is a good example of what you should *not*
> do.
> 
> This is completely crazy:
> 
> zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
> 2003-09-30

Don't say you weren't warned; I demonstrated the --debug flag
(in https://lists.debian.org/debian-user/2018/02/msg00101.html)
which gives, for your example:

$ date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month' --debug
date: parsed date part: (Y-M-D) 2003-09-01
date: parsed relative part: -1 day(s)
date: parsed relative part: +1 month(s) -1 day(s)
date: input timezone: -06:00 (set from TZ="US/Central" environment value)
date: warning: using midnight as starting time: 00:00:00
date: starting date/time: '(Y-M-D) 2003-09-01 00:00:00 TZ=-06:00'
date: warning: when adding relative months/years, it is recommended to specify 
the 15th of the months
date: warning: when adding relative days, it is recommended to specify 12:00pm
date: after date adjustment (+0 years, +1 months, -1 days),
date: new date/time = '(Y-M-D) 2003-09-30 00:00:00 TZ=-06:00'
date: '(Y-M-D) 2003-09-30 00:00:00 TZ=-06:00' = 1064898000 epoch-seconds
date: output timezone: -06:00 (set from TZ="US/Central" environment value)
date: final: 1064898000.0 (epoch-seconds)
date: final: (Y-M-D) 2003-09-30 05:00:00 (UTC0)
date: final: (Y-M-D) 2003-09-30 00:00:00 (output timezone TZ=-06:00)
2003-09-30
$ 

Most of the examples were begging for off-by-one errors.

Cheers,
David.

Re: Ethernet is not started at boot

[Michelle Konzack]

Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
> On Tue, Feb 06, 2018 at 12:03:15PM +0200, Michelle Konzack wrote:
>> I do not know currently, except that blueman depends on  glib-x11  which
>> is confirmed by the maintainer.  It seems gthumb has the same dependency
>> because sinde blueman is working gthumb too.
>
> I can't parse very well your last sentence.

Do you have glib-x11 installed on your system?

> Anyway, since I have a similarly minimalistic system as you have (I think
> I'm a tad worse: I tend to avoid DBUS when I can. I think it's ugly), I
> tried a simulated install of blueman:



> So it does try to install quite a bit, but far from the whole Gnome,

Looks quit the same, if I look in the install log

> Do you have somewhere in your apt configuration an "Install-Recommends
> no"?
>
> I have, for example in /etc/apt/apt.conf.d/95no-recommends:
>
>   APT::Install-Recommends no;

If I would say yes, it would install several 100 MByte more, which I
absolutely not want.  I have nearly all packages installed, which I also
had under Wheeze but Stretch is more then twice as bib as Wheeze.

The partition is 10 GByte big and I have only 1100 MByte left over.

Looks like I have installed Windows 10 light!

> This is the only way to preserve sanity if you do care about a
> minimalistic install, as you seem to do (the default is made for
> people who want a "kinda-works-out-of-the-box" thing, which is
> fine, but one should be aware of that).

But glib-x11 has nothing to du with Recommends, because it is essential
for a working blueman..

> See above. For such a system (I've myself Fvwm too, heh) some fine
> tuning of your package system seems necessary.

"fine tuning" is good, if you even don't know, what is missing!

> See above -- you need some tools to understand *why* the package system
> "wants" to do things. One very nice one is the -s option to apt (or
> apt-get),

apt does not tell me (Recommends/Suggests) that I need glib-x11 to get
something working, because even if you have Recommends/Suggests set to
no, apt-get show always what can be also installed together.

> which means "simulate": there you can see what is going
> to be installed. Another is apt show"  which will tell
> you what's in the package, which others it depends on (and which other
> are "recommended" or "suggested", which may also be installed
> automatically depending on your packager config: my hunch is that
> this is what's happening to you).

I have just extracted my "base install" into a chroot and tried to
install blueman but it does not suggest or recommend essential the
essential package to get blueman working.

This has absolutely nothing to do with Recommends/Suggests.

>> I will install a second stretch in a VM and install only  the  minimum
>> and then Package by Package to  figure  out,  which  dependencies  are
>> missing.
>>
>> It is a huge work, especially when I currently work in my 5,6ha forest
>> on my BioFarm in Estonia (-10°C and 30cm snow).
>
> That sounds like some amount of fun (I always complaing about Berlin being
> too cold :-/

:-D

Normally our winter is colder up to -30°C (not very often, but it happen)

> How did you do that exactly? How do you get two DVDs ont one stick?

I was following the instructions from the Debian Website and downloaded
a Windows tool, which extract the content of an ISO image and copy it
bootable on the USB Stick.

The second DVD was copied into a subfolder DVD2/

I could boot from USB, installed the base and rebooted.
And now I could not more access the USB stick even if it was registered
in /etc/apt/sources.list because apt want to mount a DVD Rom and not an
USB Stick.

So, something is wrong in the install instructions

> I see... it should be possible to refer APT to a file system instead
> of a DVD/CDROM.

But it seems not to work under Stretch, because in the past I have
created from /var/cache/apt/archives a local mirror for other
installations.

> Heh. You can have that back (I personally don't like those new
> network names -- see below[1]).
>
>> I get an error "Device unknown"
>>
>> ifup enp0s25
>
> So "ifup -a" leads to "Device unknown", did I understand you there?

"ifup eth0" gaved it.

> That would at least explain why the init script isn't working. So
> you might want to try what john doe proposed: stop your network (yes
> it won't work) with the init script:
>
>   sudo /etc/init.d/networking stop
>
> ...and then start it again:
>
>   sudo /etc/init.d/networking start
>
> Watch carefully for error messages.

He sayed unknown device

if I vet the prompt and log into as root and then type

   ifup enp0s25

it works.

>> > How should we know? Is the broken display important?
>>
>> Yes, because Debian Stretch does not more boot and I can not see the
>> Lilo command prompt
>
> Hm. This is, of course, nasty.

Unfortunately I have not my old P4 here, because the HDD is booting in
it properly.  But the compay HDD do not boot in the T400

> Uh... are 

Reply semantics (was Re: policy around 'wontfix' bug tag)

[The Wanderer]

(I should probably have changed the Subject: line in my initial reply,
but I didn't expect it to spark an entire lengthy subthread like this. I
apologize for having introduced thread-subject confusion.)

On 2018-02-06 at 08:18, Vincent Lefevre wrote:

> On 2018-02-06 14:36:31 +1300, Richard Hector wrote:
> 
>> On 06/02/18 02:11, Vincent Lefevre wrote:
>> 
>>> You should set up a "Mail-Followup-To:" for that. This is
>>> entirely your problem.
>> 
>> I could do that, I'm sure (though I'm not sure how) - but I'd
>> rather that someone intending to send me a private reply didn't
>> send it to the list by mistake. Having to (in my case) click 'Reply
>> to List' helps me not send to the list by mistake.
> 
> This is not contradictory with the setting of "Mail-Followup-To:".

Arguably, if the mailing list does not default replies back to it
normally, a responder who wishes to send a private reply may not be
expecting that Reply will go to the mailing list, and so (when
Mail-Followup-To is set to the list address) may fail to notice that
adjusting the addressee list is needed.

This boils down to expectations of default behavior, and as I said at (I
think) the outset here, there are two incompatible philosophies about
what the default should be.

>> The behaviour and policy of this list, when followed, does what I
>> want.
> 
> But the other users cannot know what you want if you do not set 
> "Mail-Followup-To:".

They should not have to.

They should be able to assume that you have taken all necessary actions
to ensure that you see any replies you want to see.

That could involve setting the header, or it could involve subscribing
to the mailing list, or it could involve requesting explicitly (in the
body of the mail or in your signature) to be CCed, or it could involve
something else.

But all of those actions should be on your part. The person who is
replying should be able to assume that just hitting Reply will do the
right thing, unless you have explicitly conveyed information to indicate
otherwise.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: policy around 'wontfix' bug tag

[Greg Wooledge]

On Tue, Feb 06, 2018 at 01:48:19PM +0100, Vincent Lefevre wrote:
> On 2018-02-05 09:39:12 -0500, Greg Wooledge wrote:
> > Anyway, here's what I came up with:
> > 
> > lastday() {
> > date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> > }
> 
> But the exact meaning of "month" seems undocumented, which may
> silently break in a future version (e.g. possibly as a consequence
> of a bug fix). So this is a good example of what you should *not*
> do.

If I have the luxury of writing in a real language, then I prefer
to use that language's date/time libraries, if they exist and don't
suck.

In bash, you get this, or you get to write your own date/time code
by hand.

> This is completely crazy:

> Where is the logic behind that?

As noted by someone else earlier in this thread, date recently learned
a --debug option (this is my first time hearing about it), so let's
try that:

wooledg:~$ date --debug +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
date: parsed date part: (Y-M-D) 2003-09-01
date: parsed relative part: -1 day(s)
date: parsed relative part: +1 month(s) -1 day(s)
date: input timezone: -05:00 (set from system default)
date: warning: using midnight as starting time: 00:00:00
date: starting date/time: '(Y-M-D) 2003-09-01 00:00:00 TZ=-05:00'
date: warning: when adding relative months/years, it is recommended to specify 
the 15th of the months
date: warning: when adding relative days, it is recommended to specify 12:00pm
date: after date adjustment (+0 years, +1 months, -1 days),
date: new date/time = '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00'
date: '(Y-M-D) 2003-09-30 00:00:00 TZ=-05:00' = 1064894400 epoch-seconds
date: output timezone: -05:00 (set from system default)
date: final: 1064894400.0 (epoch-seconds)
date: final: (Y-M-D) 2003-09-30 04:00:00 (UTC0)
date: final: (Y-M-D) 2003-09-30 00:00:00 (output timezone TZ=-05:00)
2003-09-30

So, it adds "a month" first, then subtracts "a day" second.  I suppose
I could have rearranged the sub-arguments to make that clearer, but
honestly, I stopped tweaking it once I had a working invocation.  It's
so fragile that I didn't want to change *anything* for fear of breaking
it.

In some cases, I dealt with this stuff using a truly ancient version
of GNU date from the sh-utils package, before coreutils existed.  Some
of the more modern invocations didn't work with the older program, so
I often had to find different tricks that would work.  I don't know
whether this was one such case.  It could have been.

Email discussion (was: Re: policy around 'wontfix' bug tag)

[rhkramer]

Just changing the subject--maybe someone can make a more specific subject line.

On Tuesday, February 06, 2018 08:34:11 AM Vincent Lefevre wrote:
> On 2018-02-05 18:01:08 +, Brian wrote:
> > Now you have problems (or could have). The first problem is that the
> > "duplicates" are not duplicates because the headers are different. The
> > second problem is - which one do you wish to keep? The third problem
> > (related to the second one) is the order in which the messages arrive.
> > Is it the mailing list reply first or the Cc:?
> > 
> > Users of mutt have it easy:
> > 
> > send-hook . 'unmy_hdr Message-ID:'
> > send-hook 'debian-user@lists\.debian\.org' 'my_hdr Message-ID:<`date
> > +"%Y%m%d%H%M%S"`noccsple...@example.com>'
> > 
> > A mail with NoCcsPlease in its In-Reply-To or References headers can
> > only have had the mailing list mail as its source. However, the CC will
> > not contain a List-ID: header. This makes it possible to distinguish
> > between a list mail and a CC. Procmail recipes based on these two
> > conditions can now file list mail with certainty and, if desired, delete
> > CCs.
> 
> If this is just a private reply, you will lose mail, unless the
> procmail recipe also tests the To/Cc headers against the list address
> (hoping the list server doesn't drop mail for some reason).

Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-06 13:48:19 +0100, Vincent Lefevre wrote:
> This is completely crazy:
> 
> zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
> 2003-09-30
> zira% date +%Y-%m-%d -d '2003-09-01 1 day ago'
> 2003-08-31
> zira% date +%Y-%m-%d -d '2003-08-31 + 1 month'
> 2003-10-01
> 
> So, while '2003-09-01 1 day ago' gives 2003-08-31, the following
> are not equivalent:
>   * '2003-09-01 1 day ago + 1 month'
>   * '2003-08-31 + 1 month'
> 
> Where is the logic behind that?

Other ones:

zira% date +%Y-%m-%d -d '2003-02-01 - 1 month'
2003-01-01
zira% date +%Y-%m-%d -d '2003-02-01 - 31 days'
2003-01-01
zira% date +%Y-%m-%d -d '2003-02-01 - 31 days + 1 month'
2003-01-29
zira% date +%Y-%m-%d -d '2003-02-01 - 1 month + 1 month'
2003-02-01

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-05 18:01:08 +, Brian wrote:
> Now you have problems (or could have). The first problem is that the
> "duplicates" are not duplicates because the headers are different. The
> second problem is - which one do you wish to keep? The third problem
> (related to the second one) is the order in which the messages arrive.
> Is it the mailing list reply first or the Cc:?
> 
> Users of mutt have it easy:
> 
> send-hook . 'unmy_hdr Message-ID:'
> send-hook 'debian-user@lists\.debian\.org' 'my_hdr Message-ID:<`date 
> +"%Y%m%d%H%M%S"`noccsple...@example.com>'
> 
> A mail with NoCcsPlease in its In-Reply-To or References headers can
> only have had the mailing list mail as its source. However, the CC will
> not contain a List-ID: header. This makes it possible to distinguish
> between a list mail and a CC. Procmail recipes based on these two
> conditions can now file list mail with certainty and, if desired, delete
> CCs.

If this is just a private reply, you will lose mail, unless the
procmail recipe also tests the To/Cc headers against the list address
(hoping the list server doesn't drop mail for some reason).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: mac en rade

[fab]

'lut,


Et il y a encore des andouilles pour acheter les grosses m… de ces enf… !?
Ben... environ 99% des gens. Mais tous ne sont pas des andouilles, juste 
des gens à qui tu n'as pas encore expliqué le sens de la vie ;)


f.




Thomas Savary
Le Grand Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
www.correctionpro.fr
www.compo85.fr




Le 6 févr. 2018 11:17, "Stephane Ascoet"  a

écrit :

Le 06/02/2018 à 11:14, Pierre Malard a écrit :

Tout à fait d’accord sur le verrouillage (Apple, M$, Google même combat)
mais je ne vois pas le rapport avec ce qui était écrit. Je voulais juste
exprimer le fait qu’il y a toujours un parfum de mystère dès qu’on évoque
un Mac alors que c’est tout simplement un ordinateur qui fonctionne, au
fond, comme tous les


Justement non, ce n'est plus le cas. On ne peut absolument plus installer
ce que l'on veut.

D'ailleurs, s'il y a des macounets qui lisent ceci, mefiez-vous: il
semblerait que High Sierra *deplace* le contenu du dossier personnel sur
les serveurs Apple sans preavis. Plein de gens auraient tout perdu...
--
Cordialement, Stephane Ascoet

Re: mac en rade

[Stephane Ascoet]

Le 06/02/2018 à 13:20, Thomas Savary a écrit :



Ce sera quoi, la prochaine étape ? La fin des disques durs internes ? Avant
celle des périphériques de stockage ?


Tres certainement. Il n'y a plus aucun connecteur sur les derniers 
portables de la marque, plus de prise reseau depuis des annees... 
Certains modeles ont en fait la meme carte mere que l'idiotphone ou la 
tablette de la marque. Leur but est d'en faire des terminaux passifs 
connectes à leurs serveurs en wi-fi.


Et il y a encore des andouilles pour acheter les grosses m… de ces enf… !?


Ben ouais, ils sont tout fins, tout dores, c'est trop la classe pour frimer.
--
Cordialement, Stephane Ascoet

Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-06 14:36:31 +1300, Richard Hector wrote:
> On 06/02/18 02:11, Vincent Lefevre wrote:
> > You should set up a "Mail-Followup-To:" for that. This is entirely
> > your problem.
> 
> I could do that, I'm sure (though I'm not sure how) - but I'd rather
> that someone intending to send me a private reply didn't send it to the
> list by mistake. Having to (in my case) click 'Reply to List' helps me
> not send to the list by mistake.

This is not contradictory with the setting of "Mail-Followup-To:".

> The behaviour and policy of this list, when followed, does what I want.

But the other users cannot know what you want if you do not set
"Mail-Followup-To:".

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Package pinning on origin AND version

[The Wanderer]

On 2018-02-06 at 07:52, Adam Cecile wrote:

> On 02/06/2018 01:46 PM, The Wanderer wrote:
>
>> Pin: version 1.3.*, release o=packages.le-vert.net
> 
> Hello,
> 
> Thanks for the answer, sadly it's not working:
> 
> mesos:
>Installed: 1.3.1-1+Debian-stretch-9.1
>Candidate: 1.4.1-1+Debian-stretch-9.1

Not sure what may be causing that. Just as a stab in the dark, maybe try
it with 'Pin-Priority: 1001', in case something else is setting the
priority of the 1.4.x version to 1000? (Again per 'man apt_preferences',
when two versions have equal priority, the higher version number wins
out.)

Note that a priority greater than 1000 will lead the matching version to
be considered even when it would be a version-number downgrade from the
installed version. That may be what you want (it often is, for me), but
it's something that's good to be aware of.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: Package pinning on origin AND version

[Adam Cecile]

On 02/06/2018 01:46 PM, The Wanderer wrote:

Pin: version 1.3.*, release o=packages.le-vert.net


Hello,

Thanks for the answer, sadly it's not working:

mesos:
  Installed: 1.3.1-1+Debian-stretch-9.1
  Candidate: 1.4.1-1+Debian-stretch-9.1

Re: What went wrong with my GeForce GTX 1050 Ti driver installation?

[tv.deb...@googlemail.com]

On 06/02/2018 17:08, Erkko Lahnajärvi wrote:

Hi,


I fetched a new computer few days ago. The equipment are:

Motherboard: Gigabyte AB350-Gaming
CPU: Amd Ryzen 3 1300x
RAM: 16Gb
Video card: GeForce GTX 1050 Ti
Hard disk: WD green 240 Gb

On this computer I installed Debian-9.3.0-amd64.
I've first tried to install the video card. I found a particular driver for
Linux from Ndivia's website. And then I bigan to install it... It didn't
work so I asked your help via email yesterday.  You gave me this kind of a
guide:

"Hi, you really don't need to download drivers from Nvidia website, it is
quite the opposite since doing so will probably result in a much less
stable system and difficulty to update.

Start by reading the relevant Debian documentation [1], your card is fully
supported by the Nvidia driver available in Debian 9 [2] so you are in luck!
All you need is to add "non-free" to your /etc/apt/sources.list file, and
install the package "linux-headers-amd64" and "nvidia-driver". See link
[1], it's all explained there."

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

[2] http://us.download.nvidia.com/XFree86/Linux-x86_64/375.66/RE
ADME/supportedchips.html

--
I reinstalled "stretch" and then I followed the instructions you gave. With
one little exception. I added also the "contrib" to every line after
"main". That was the guide of the link.

After that the rest of the installation seemed to go well. Then I rebooted
and all I confronted was empty dark screen. Computer still had the power
on.  I didn't get any further.

Now I have reinstalled Debian again. What should I do to make my video card
running?




Hi, you are on the right track, but next time don't reinstall from zero 
if you get a black screen, it is most likely fixable.


You probably missed the step where you need to create a "xorg.conf" file:

"Configuration

As the nvidia driver is not autodetected by Xorg, a configuration file 
is required to be supplied.[...]


Automatic

Install the nvidia-xconfig package, then run it with sudo. It will 
automatically generate a Xorg configuration file at /etc/X11/xorg.conf"


That's the relevant info from [1]. In short you need to install the 
"nvidia-xconfig" package, and run it without any option or argument as 
root (or using "sudo"):


sudo nvidia-xconfig


and check that you now have a file /etc/X11/xorg.conf.


As an added measure you can blacklist "nouveau" which is the free driver 
for Nvidia but unfortunately often struggles to work or keep up with new 
hardware. (Short story, Nvidia is not helping and developers have to 
reverse-engineer the driver, not an easy task). I think it is done for 
you upon installation of the Nvidia driver, but you can do it manually 
by adding a file in /etc/modprobe.d directory, for example create a file 
named "blacklist-nouveau.conf" with this content:


blacklist nouveau

and apply the change with:

sudo update-initramfs -u -k all

It is also possible to add a kernel boot parameter if you get a black 
screen like you did, in grub edit the kernel boot entry by pressing the 
"e" key, and add this at the end of the "linux" line:


nouveau.modeset=0 modprobe.blacklist=nouveau


Hope you get it to work this time.


[1] https://wiki.debian.org/NvidiaGraphicsDrivers#configure

Re: systemd 237-1: problem starting dnsmasq

[Tomasz Nowiński]

The same appears for me.

Re: mac en rade

[Thomas Savary]

mardi 6 février 2018, à 13:10:36 CET, Belaïd a écrit :
> Au faite c'etait déjà le cas depuis sierra,  ils transferent le Bureau
> ainsi que le dossier Document sur le compte iCloud , et c'est pas vraiment
> cool

Déjà que je trouvais lamentable l’insidieux dossier Onedrive de Microsoft 
(l’expérience m’ayant montré que certains utilisateurs n’avaient pas 
conscience qu’il ne s’agissait pas d’un emplacement de leur disque dur), mais 
là, les bras m’en tombent… Le klaoude par défaut ! « Votre bureau est à nous. 
Vos données sont nos données. »

Ce sera quoi, la prochaine étape ? La fin des disques durs internes ? Avant 
celle des périphériques de stockage ?

Et il y a encore des andouilles pour acheter les grosses m… de ces enf… !?

Thomas Savary
Le Grand Plessis
F-85340 L’Île-d’Olonne
Tél. 06 22 82 61 34
www.correctionpro.fr
www.compo85.fr


> 
> Le 6 févr. 2018 11:17, "Stephane Ascoet"  a
> 
> écrit :
> > Le 06/02/2018 à 11:14, Pierre Malard a écrit :
> >> Tout à fait d’accord sur le verrouillage (Apple, M$, Google même combat)
> >> mais je ne vois pas le rapport avec ce qui était écrit. Je voulais juste
> >> exprimer le fait qu’il y a toujours un parfum de mystère dès qu’on évoque
> >> un Mac alors que c’est tout simplement un ordinateur qui fonctionne, au
> >> fond, comme tous les
> > 
> > Justement non, ce n'est plus le cas. On ne peut absolument plus installer
> > ce que l'on veut.
> > 
> > D'ailleurs, s'il y a des macounets qui lisent ceci, mefiez-vous: il
> > semblerait que High Sierra *deplace* le contenu du dossier personnel sur
> > les serveurs Apple sans preavis. Plein de gens auraient tout perdu...
> > --
> > Cordialement, Stephane Ascoet

Re: [Was: Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-06 12:32:06 +1100, Erik Christiansen wrote:
> On 05.02.18 09:39, Greg Wooledge wrote:
> > (*) One specific shell script use case was "Get the last date of a given
> > month."  Now, obviously you can just set up an array of hard-coded month
> > ending dates, and then write a function to determine whether the current
> > year is a leap year for the February case.  But if you want to do it with
> > GNU date -d, then you have to guess a magic incantation that actually
> > works.  Usually by trial and error.
> > 
> > Anyway, here's what I came up with:
> > 
> > lastday() {
> > date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> > }
> ...
> 
> > How does it work?  Who knows!
> 
> That's quite straightforward, I submit. Omitting the "+ 1 month", your
> expression is equivalent to: (with $1 substituted for example 1)
> 
> $ date +%Y-%m-%d -d "2016-03-01 - 1 day"
> 2016-02-29
> 
> which simply steps backward from first of the month to last of the
> previous. Then stepping forward a month merely avoids the need to input
> first of next month for last of this one.

Your explanation is incorrect (see my other mail on this subject).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: policy around 'wontfix' bug tag

[Vincent Lefevre]

On 2018-02-05 09:39:12 -0500, Greg Wooledge wrote:
> (*) One specific shell script use case was "Get the last date of a given
> month."  Now, obviously you can just set up an array of hard-coded month
> ending dates, and then write a function to determine whether the current
> year is a leap year for the February case.  But if you want to do it with
> GNU date -d, then you have to guess a magic incantation that actually
> works.  Usually by trial and error.
> 
> Anyway, here's what I came up with:
> 
> lastday() {
> date +%Y-%m-%d -d "$1 1 day ago + 1 month"
> }

But the exact meaning of "month" seems undocumented, which may
silently break in a future version (e.g. possibly as a consequence
of a bug fix). So this is a good example of what you should *not*
do.

This is completely crazy:

zira% date +%Y-%m-%d -d '2003-09-01 1 day ago + 1 month'
2003-09-30
zira% date +%Y-%m-%d -d '2003-09-01 1 day ago'
2003-08-31
zira% date +%Y-%m-%d -d '2003-08-31 + 1 month'
2003-10-01

So, while '2003-09-01 1 day ago' gives 2003-08-31, the following
are not equivalent:
  * '2003-09-01 1 day ago + 1 month'
  * '2003-08-31 + 1 month'

Where is the logic behind that?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Re: Package pinning on origin AND version

[The Wanderer]

On 2018-02-06 at 03:01, Adam Cecile wrote:

> Hello,
> 
> I'd like to do something like this:
> 
> Package: mesos
> Pin: version 1.3.*
> Pin: release o=packages.le-vert.net
> Pin-Priority: 1000
> 
> But sadly the last "Pin:" line overrides the previous one.

Try:

Package: mesos
Pin: version 1.3.*, release o=packages.le-vert.net
Pin-Priority: 1000

This is documented in 'man apt_preferences', at the end of the section
"The Effect of APT Preferences"; the comma in a Pin: line functions as
an "and" operator. (There's a caveat mentioned there, but it shouldn't
apply in your case.)

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Package pinning on origin AND version

[Adam Cecile]

Hello,

I'd like to do something like this:

Package: mesos
Pin: version 1.3.*
Pin: release o=packages.le-vert.net
Pin-Priority: 1000

But sadly the last "Pin:" line overrides the previous one.


My problem here is that I'd like the version 
"1.3.1-1+Debian-stretch-9.1" to be the candidate one. Depending on which 
"Pin:" line is the latest one I get either "1.4.1-1+Debian-stretch-9.1" 
or "1.3.2-2.0.1".


mesos:
  Installed: 1.3.1-1+Debian-stretch-9.1
  Candidate: 1.4.1-1+Debian-stretch-9.1
  Version table:
 1.4.1-1+Debian-stretch-9.1 1000
    500 http://packages.le-vert.net/mesos/debian stretch/main amd64 
Packages

 1.4.1-2.0.1 500
    500 http://repos.mesosphere.io/debian jessie/main amd64 Packages
 1.4.0-2.0.1 500
    500 http://repos.mesosphere.io/debian jessie/main amd64 Packages
 1.3.2-2.0.1 500
    500 http://repos.mesosphere.io/debian jessie/main amd64 Packages
 *** 1.3.1-1+Debian-stretch-9.1 1000
    500 http://packages.le-vert.net/mesos/debian stretch/main amd64 
Packages

    100 /var/lib/dpkg/status
 1.3.1-2.0.1 500
    500 http://repos.mesosphere.io/debian jessie/main amd64 Packages
 1.3.0-2+Debian-stretch-9.0 1000
    500 http://packages.le-vert.net/mesos/debian stretch/main amd64 
Packages

 1.3.0-1+Debian-stretch-9.0 1000


Thanks in advance,

Adam

Re: policy around 'wontfix' bug tag

[Erik Christiansen]

On 06.02.18 19:16, Richard Hector wrote:
> On 06/02/18 18:38, Erik Christiansen wrote:
> > Perl is the quintessential write-only language, which with a bit of luck
> > will die out before it catches on
> 
> Now you're getting to fighting talk ... :-)

Whoops, forgot the <$0.02> ...  markers. 
But planning to replace a formal BNF grammar with perl/python/ruby/...
spaghetti would be a most dubious design strategy, IME.

Around 23 years ago, I bought three O'reilly perl books - the cookbook,
the nutshell, and another one, but couldn't stand the language, despite
the investment. Never had that trouble with awk, sed, lex, yacc/bison,
bash, expect, C, makefiles, ld linker scripts, assembler for half a
dozen targets, postscript, ...

Erik

-- 
Once, adv.:
   Enough.
   - Ambrose Bierce, "The Devil's Dictionary"

Re: Corte de energia y DRBD

[Galvatorix Torixgalva]

Me temo que no, ya que lo que mencionas no lo conozco.

Te pongo el link a una lista de livecd, a ver si hay suerte y alguna te
resulta util.

https://livecdlist.com/
​

Re: mac en rade

[Belaïd]

Au faite c'etait déjà le cas depuis sierra,  ils transferent le Bureau
ainsi que le dossier Document sur le compte iCloud , et c'est pas vraiment
cool

Le 6 févr. 2018 11:17, "Stephane Ascoet"  a
écrit :

> Le 06/02/2018 à 11:14, Pierre Malard a écrit :
>
>> Tout à fait d’accord sur le verrouillage (Apple, M$, Google même combat)
>> mais je ne vois pas le rapport avec ce qui était écrit. Je voulais juste
>> exprimer le fait qu’il y a toujours un parfum de mystère dès qu’on évoque
>> un Mac alors que c’est tout simplement un ordinateur qui fonctionne, au
>> fond, comme tous les
>>
>
> Justement non, ce n'est plus le cas. On ne peut absolument plus installer
> ce que l'on veut.
>
> D'ailleurs, s'il y a des macounets qui lisent ceci, mefiez-vous: il
> semblerait que High Sierra *deplace* le contenu du dossier personnel sur
> les serveurs Apple sans preavis. Plein de gens auraient tout perdu...
> --
> Cordialement, Stephane Ascoet
>
>

Re: Ethernet is not started at boot

[Gene Heskett]

On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:

> #  Do not Cc: me, I am on THE LIST and I do not need 
> ## #  messages twice which make it very hard to
> answer.  ##
>
>
> Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
>
> > This is all? No "lo" stanza? Hm.
>
> it is:
>
> auto lo
> iface lo inet loopback
>
> > In that case, it looks more or less correct. Issuing "ifup -a"
> > should bring up your enp0s25 interface. Does it?
>
> Yes, it is up.
>
> The problem since Jessie is, that my PostgreSQL instances (I have 4)
> and the nfs mounts plus VPN are ALWAYS started before the network and
> exit with errors.
>
> I have to start ALL services by hand in order!
>
> If PostgreSQL can not start, then NO USER can log into the systenm!
>
> > But in this case it isn't clear what is triggering your DHCP
> > client.
>
> I have already deinstalled the isc-dhcp-client.
>
> > Nothing else in some subdirectory /etc/network/interfaces.d?
>
> No.
>
> I have now moved the config for ethernet to
>
> /etc/network/interfaces.d/enp0s25
>
> So the content of the files show
>
> [ /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/*
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
> --
IF lack of a gateway "UG" entry in route -n is the problem, try this.

> [ /etc/network/interfaces.d/enp0s25
> ]

> auto enp0s25 
> iface enp0s25 inet static
> address 192.168.0.202
> netmask 255.255.255.0
> gateway 192.168.0.1
> network 192.168.0.0
>
> allow-hotplug enp0s25
  ^
Doesn't the above line belong ABOVE the iface line? It has been in every 
example I've looked at. I am not using that line as its static, not 
dhcpd.

I just went thru around 3 days of screwing around with a 'static' setup 
on an arm64 rockchip, could not get it to take a gateway assignment so I 
couldn't go anyplace out of my home network, until I added this last 
line to /etc/network/interfaces.d/eth0:

up route add default gw 192.168.xx.1

The usual gw assignment seems to be broken in stretch, but now it works 
as shown by a route -n. And has continued to work over several reboots.

[...]

-- 
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 

What went wrong with my GeForce GTX 1050 Ti driver installation?

[Erkko Lahnajärvi]

Hi,


I fetched a new computer few days ago. The equipment are:

Motherboard: Gigabyte AB350-Gaming
CPU: Amd Ryzen 3 1300x
RAM: 16Gb
Video card: GeForce GTX 1050 Ti
Hard disk: WD green 240 Gb

On this computer I installed Debian-9.3.0-amd64.
I've first tried to install the video card. I found a particular driver for
Linux from Ndivia's website. And then I bigan to install it... It didn't
work so I asked your help via email yesterday.  You gave me this kind of a
guide:

"Hi, you really don't need to download drivers from Nvidia website, it is
quite the opposite since doing so will probably result in a much less
stable system and difficulty to update.

Start by reading the relevant Debian documentation [1], your card is fully
supported by the Nvidia driver available in Debian 9 [2] so you are in luck!
All you need is to add "non-free" to your /etc/apt/sources.list file, and
install the package "linux-headers-amd64" and "nvidia-driver". See link
[1], it's all explained there."

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

[2] http://us.download.nvidia.com/XFree86/Linux-x86_64/375.66/RE
ADME/supportedchips.html

--
I reinstalled "stretch" and then I followed the instructions you gave. With
one little exception. I added also the "contrib" to every line after
"main". That was the guide of the link.

After that the rest of the installation seemed to go well. Then I rebooted
and all I confronted was empty dark screen. Computer still had the power
on.  I didn't get any further.

Now I have reinstalled Debian again. What should I do to make my video card
running?


-- 
With friendly regards

Erkko Lahnajärvi

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 12:10:36PM +0100, john doe wrote:
> On 2/6/2018 11:42 AM, Michelle Konzack wrote:

[...]

> >[ /etc/network/interfaces.d/enp0s25 ]---
> >auto enp0s25
> >iface enp0s25 inet static
> > address 192.168.0.202
> > netmask 255.255.255.0
> > gateway 192.168.0.1
> > network 192.168.0.0
> >
> >allow-hotplug enp0s25
> >
> 
> Not sure if it makes any difference but I would put 'allow-hotplug
> ...' beneath 'auto ...' and not at the end of the file:
> 
> https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html

I would throw out this allow-hotplug altogether. This one is waiting
for udev detecting the hardware coming up -- if I understood you
right, the eth is built-in. Not needed, then (and one moving part
less).

If it is an eth USB dongle, OTOH... you might need it.

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

iEYEARECAAYFAlp5kI4ACgkQBcgs9XrR2kbiMwCdHfENeMa1dWI/BzghampzvpGV
nqUAnjMa/C75zenjJI5Y4wzJJV7E6gyt
=nrZn
-END PGP SIGNATURE-

Re: Ethernet is not started at boot

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, Feb 06, 2018 at 12:03:15PM +0200, Michelle Konzack wrote:
>  DO not Cc: me, I am on THE LIST and I do not need 
>  messages twice which make it very hard to ansewer 
> 
> Hello Tomas,
> 
> Am 2018-02-06 hackte to...@tuxteam.de in die Tasten:
> >> I have installed on my ThinkPad T400 recently Stretch (base, xorg,  wdm,
> >> fvwm, gthumb, blueman, alsa...) only to discover, that 17 Packages  have
> >> missing Dependencies!
> >
> > the missing dependencies?
> 
> I do not know currently, except that blueman depends on  glib-x11  which
> is confirmed by the maintainer.  It seems gthumb has the same dependency
> because sinde blueman is working gthumb too.

I can't parse very well your last sentence.

Anyway, since I have a similarly minimalistic system as you have (I think
I'm a tad worse: I tend to avoid DBUS when I can. I think it's ugly), I
tried a simulated install of blueman:

  tomas@trotzki:~$ apt -s install blueman 
  NOTE: This is only a simulation!
apt needs root privileges for real execution.
Keep also in mind that locking is deactivated,
so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
bluez bluez-obexd dbus gir1.2-appindicator3-0.1 gir1.2-gtk-3.0
gir1.2-notify-0.7 libapparmor1 libappindicator3-1 libbluetooth3
libdbusmenu-glib4 libdbusmenu-gtk3-4 libical2 libindicator3-7
libnotify4 libpulse-mainloop-glib0 notification-daemon python3-cairo
python3-dbus python3-gi python3-gi-cairo
  Suggested packages:
pulseaudio-module-bluetooth default-dbus-session-bus | dbus-session-bus
python-dbus-doc python3-dbus-dbg
  Recommended packages:
policykit-1
  The following NEW packages will be installed:
blueman bluez bluez-obexd dbus gir1.2-appindicator3-0.1 gir1.2-gtk-3.0
gir1.2-notify-0.7 libapparmor1 libappindicator3-1 libbluetooth3
libdbusmenu-glib4 libdbusmenu-gtk3-4 libical2 libindicator3-7 libnotify4
libpulse-mainloop-glib0 notification-daemon python3-cairo python3-dbus
python3-gi python3-gi-cairo
  [...]

So it does try to install quite a bit, but far from the whole Gnome,
Do you have somewhere in your apt configuration an "Install-Recommends
no"?

I have, for example in /etc/apt/apt.conf.d/95no-recommends:

  APT::Install-Recommends no;

This is the only way to preserve sanity if you do care about a
minimalistic install, as you seem to do (the default is made for
people who want a "kinda-works-out-of-the-box" thing, which is
fine, but one should be aware of that).

> The dependendies are only satisfait if you install a full DE like Gnome,
> KDE or  other defaults by Debian.
> 
> If you install the bare minimum like
> 
> Debian base
> xorg
> wdm
> fvwmg
> thumb
> blueman
> alsa
> mc
> 
> you have a non-working system!

See above. For such a system (I've myself Fvwm too, heh) some fine
tuning of your package system seems necessary.

[...]

> yes, if you know, WHICH package you need, it can be installed manually
> which is already confirmed by 3 Package  maintainers.   They  assumed,
> that Debian User install always  a  complete  system,  but  where  not
> thinking on users which do not need a full DE.
> 
> Hence, some packages missing dependencies.

See above -- you need some tools to understand *why* the package system
"wants" to do things. One very nice one is the -s option to apt (or
apt-get), which means "simulate": there you can see what is going
to be installed. Another is apt show"  which will tell
you what's in the package, which others it depends on (and which other
are "recommended" or "suggested", which may also be installed
automatically depending on your packager config: my hunch is that
this is what's happening to you).

> I will install a second stretch in a VM and install only  the  minimum
> and then Package by Package to  figure  out,  which  dependencies  are
> missing.
> 
> It is a huge work, especially when I currently work in my 5,6ha forest
> on my BioFarm in Estonia (-10°C and 30cm snow).

That sounds like some amount of fun (I always complaing about Berlin being
too cold :-/

> > Is this your problem? Would you like to install (mostly) from a set of
> > ISOs on an USB stick or similar?
> 
> My T400 was under Windows 7 and had a "hardware" error which refuse to
> burn ANY DVDs. So I installed the ISO bootable on the  USB  Stick  and
> added the second ISO to it.
> 
> But it does not work.

How did you do that exactly? How do you get two DVDs ont one stick?

> Since my Interanet Server is also not running, I can not even install
> a local mirror.

I see... it should be possible to refer APT to a file system instead
of a DVD/CDROM.

> > Is this your problem? You can set a fixed IP address at install time,
> > or...
> 
> This was exactly what was not working!
> The Installer 

Re: Ethernet is not started at boot

[john doe]

On 2/6/2018 11:42 AM, Michelle Konzack wrote:

#  Do not Cc: me, I am on THE LIST and I do not need  ##
#  messages twice which make it very hard to answer.  ##


Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de

This is all? No "lo" stanza? Hm.


it is:

auto lo
iface lo inet loopback


In that case, it looks more or less correct. Issuing "ifup -a"
should bring up your enp0s25 interface. Does it?


Yes, it is up.

The problem since Jessie is, that my PostgreSQL instances (I have 4) and
the nfs mounts plus VPN are ALWAYS started before the network and exit
with errors.

I have to start ALL services by hand in order!

If PostgreSQL can not start, then NO USER can log into the systenm!


But in this case it isn't clear what is triggering your DHCP
client.


I have already deinstalled the isc-dhcp-client.


Nothing else in some subdirectory /etc/network/interfaces.d?


No.

I have now moved the config for ethernet to

/etc/network/interfaces.d/enp0s25

So the content of the files show

[ /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/*

# The loopback network interface
auto lo
iface lo inet loopback


[ /etc/network/interfaces.d/enp0s25 ]---
auto enp0s25
iface enp0s25 inet static
 address 192.168.0.202
 netmask 255.255.255.0
 gateway 192.168.0.1
 network 192.168.0.0

allow-hotplug enp0s25



Not sure if it makes any difference but I would put 'allow-hotplug ...' 
beneath 'auto ...' and not at the end of the file:


https://manpages.debian.org/jessie/ifupdown/interfaces.5.en.html

--
John Doe

Re: Corte de energia y DRBD

[Ricky Gutierrez]

El El mar, 6 de feb. de 2018 a las 02:13, Galvatorix Torixgalva <
galvatorix2...@gmail.com> escribió:

>
> Hola,
>
> lo que voy a decirte no se si te servira, y puede que ya lo conozcas, pero
> por si acaso lo digo.
>
> Has probado con distribuciones de rescate?, me refiero a las
> distribuciones que se usan en forma de LiveCD o de LiveDVD y son por y para
> cuando ocurren desastres de diverso tipo.
>
> Logicamente no hacen milagros, pero si pueden ser una ayuda importante en
> ciertos casos.
>
>


> Hola , la verdad no , alguna en especial?
-- 
rickygm

http://gnuforever.homelinux.com

Re: policy around 'wontfix' bug tag

[Curt]

On 2018-02-06, David Wright  wrote:
>
> Ah, OK, the timestamps. There's no need to worry about that. Every
> email I send to my wife, sitting at the same table, crosses the
> Atlantic twice, typically in under a minute, and sometimes much less.
>

You're not on speaking terms, is that it?

Or is it to show you'd cross the Atlantic twice for her (à la nage!).



-- 
“True terror is to wake up one morning and discover that your high school class
is running the country.” – Kurt Vonnegut

Re: Ethernet is not started at boot

[Michelle Konzack]

#  Do not Cc: me, I am on THE LIST and I do not need  ##
#  messages twice which make it very hard to answer.  ##


Am DATE hackte AUTHOR in die Tasten: to...@tuxteam.de
> This is all? No "lo" stanza? Hm.

it is:

auto lo
iface lo inet loopback

> In that case, it looks more or less correct. Issuing "ifup -a"
> should bring up your enp0s25 interface. Does it?

Yes, it is up.

The problem since Jessie is, that my PostgreSQL instances (I have 4) and
the nfs mounts plus VPN are ALWAYS started before the network and exit
with errors.

I have to start ALL services by hand in order!

If PostgreSQL can not start, then NO USER can log into the systenm!

> But in this case it isn't clear what is triggering your DHCP
> client.

I have already deinstalled the isc-dhcp-client.

> Nothing else in some subdirectory /etc/network/interfaces.d?

No.

I have now moved the config for ethernet to

/etc/network/interfaces.d/enp0s25

So the content of the files show

[ /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/*

# The loopback network interface
auto lo
iface lo inet loopback


[ /etc/network/interfaces.d/enp0s25 ]---
auto enp0s25
iface enp0s25 inet static
address 192.168.0.202
netmask 255.255.255.0
gateway 192.168.0.1
network 192.168.0.0

allow-hotplug enp0s25


> OK. Let's try to debug that: since you're doing SysV init, the
> whole magic is done in  /etc/init.d/networking. This one is controlled
> by parameters set in /etc/default/networking. What is in there?

[ /etc/default/networking ]-
# Configuration for networking init script being run during
# the boot sequence

# Set to 'no' to skip interfaces configuration on boot
CONFIGURE_INTERFACES=yes

# Don't configure these interfaces. Shell wildcards supported/
#EXCLUDE_INTERFACES=

# Set to 'yes' to enable additional verbosity
VERBOSE=yes


> Next time you boot: could you watch your boot process and see whether
> you see anything special around "Configuring network interfaces" (that
> should be the message issued by /etc/init.d/networking). Perhaps there
> is something enlightening around that.
>
> Cheers

Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400

Re: Ethernet is not started at boot

[Michelle Konzack]

Am DATE hackte AUTHOR in die Tasten: john doe
> On 2/6/2018 10:27 AM, Michelle Konzack wrote:
>> Am DATE hackte AUTHOR in die Tasten: john doe
>>> - Are you using '/etc/network/interfaces' or
>>> /etc/systemd/network/INT-NAME.network?
>>
>> I have removed systemd from Stretch!
>>
>>> - What is the content of your interface file?
>>
>> auto enp0s25
>> iface enp0s25 inet static
>>  address 192.168.0.202
>>  netmask 255.255.255.0
>>  gateway 192.168.0.1
>>  network 192.168.0.0
>>
>
> Do you get any errors while doing:
>
> $/etc/init.d/networking restart

The usually messages for stoping and starting the network  and not more

> Do you get any error related to this issue in the log?

This is WHY I ask here, there are no error messages.


Thanks in advance

-- 
Michelle KonzackMiila ITSystems @ TDnet
GNU/Linux Developer 00372-54541400