Re: Akonadi problem

[Gene Heskett]

On Thursday 25 January 2018 22:10:03 Christopher Judd wrote:

> Hi,
>
>
>      For some time now, I haven't been able to use kontact or kmail,
> because Akonadi is not running.  This is on an amd64  testing box. 
> When I issue the command "akonadictl start", I get the following
> output:
>
>
>
> Connecting to deprecated signal
> QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
> org.kde.pim.akonadiserver: database server stopped unexpectedly
> org.kde.pim.akonadiserver: Database process exited unexpectedly during
> initial connection! org.kde.pim.akonadiserver: executable:
> "/usr/sbin/mysqld" org.kde.pim.akonadiserver: arguments:
> ("--defaults-file=/home/judd/.local/share/akonadi/mysql.conf",
> "--datadir=/home/judd/.local/share/akonadi/db_data/",
> "--socket=/tmp/akonadi-judd.TvrP8V/mysql.socket",
> "--pid-file=/tmp/akonadi-judd.TvrP8V/mysql.pid")
> org.kde.pim.akonadiserver: stdout: "" org.kde.pim.akonadiserver:
> stderr: "mysqld: [ERROR] Could not open required defaults file:
> /home/judd/.local/share/akonadi/mysql.conf\nmysqld: [ERROR] Fatal
> error in defaults handling. Program aborted!\n"
> org.kde.pim.akonadiserver: exit code: 1 org.kde.pim.akonadiserver:
> process error: "Unknown error" mysqladmin: connect to server at
> 'localhost' failed error: 'Can't connect to local MySQL server through
> socket '/tmp/akonadi-judd.TvrP8V/mysql.socket' (2)' Check that mysqld
> is running and that the socket:
> '/tmp/akonadi-judd.TvrP8V/mysql.socket' exists!
> org.kde.pim.akonadiserver: Failed to remove runtime connection config
> file org.kde.pim.akonadicontrol: Application 'akonadiserver' exited
> normally...
>
>
>
>
> The file ~/.local/share/akonadi/mysql.conf exists and is readable. 
> Any suggestions as to what is going wrong here?  Thanks.
>
>
> -Chris                     

What version of kde? I am using kmail here, without an akonadi instance 
visible in htop. But this kmail is 1.9, from the TDE desktop, a fork of 
kde at about the 3.5 point, with tons of bugs fixed that kde never had 
the time to listen to. It Just Works now.

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

Re: extracting file with xz file tar.....

[Gene Heskett]

On Thursday 25 January 2018 21:45:46 David Wright wrote:

> On Thu 25 Jan 2018 at 19:54:14 (-0500), Gene Heskett wrote:
> > On Thursday 25 January 2018 15:51:47 Brian wrote:
> > > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote:
> > > [Snipped more]
> > >
> > > > Cheers, Gene Heskett
> > > > The above content, added by Maurice E. Heskett, is Copyright
> > > > 2018 by Maurice E. Heskett.
> > >
> > > I've deleted just about everything in your post because I do not
> > > know whether it is redistributable. Would you please clarify?
> >
> > Yes, my bad, that is intended for the amanda list, whose new owner
> > is attempting to emulate yahoo all those years ago by claiming
> > copyright on everthing the server passes thru. Yahoo got burned at
> > the stake in court over that, and now CARBONITE INC is replaying it.
> > I need to figure out a way to make kmail use an individual signature
> > per list. Without concocting 40+ more identities.
> >
> > In the meantime I'm trying to train this old dog to delete those 2
> > lines when the message is not aimed at the amanda list.
>
> As you may or may not have noticed, I (or, rather, mutt) insert a
> Reply-To: header into all my posts on this list. It's generated by a
> folder-hook triggered by my being in this (deblis) folder.
>
> Perhaps you can coerce your email client to do the same sort of thing
> with headers even if it can't manage it with signatures. Organization:
> might be a suitable header to use.
>
> Cheers,
> David.

I finally did find a place to add it in the folder properties, but its 
above the sig. I never did find an Organization line. I did at one point 
years back have it filled in as "Undetectable" since I've always been an 
event driven type, but it always showed up appended to the address.  One 
of the thousands of bugs kde never fixed.

But I've been running TDE for a gui for quite a while. That's a fork of 
kde at about the 3.5 point, with tons of bugs fixed.

-- 
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: extracting file with xz file tar.....

[Charlie S]

On Thu, 25 Jan 2018 20:51:47 + Brian sent:

> On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote:
> 
> > On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote:
> >   
> > > Dear folks,
> > >
> > > I am trying to extract files from a tar xz file.
> > >
> > > The file is a kernel file.
> > >
> > > I ran the tar -xf command:  
> 
> [Snipped]
> 
> > Cheers, Gene Heskett
> > The above content, added by Maurice E. Heskett, is Copyright 2018
> > by Maurice E. Heskett.  
> 
> I've deleted just about everything in your post because I do not know
> whether it is redistributable. Would you please clarify?
> 
> -- 
> Brian.

After contemplation, my reply is:

[quote] man xz can be quite educational ;-) [end quote]

Is there something wrong with that?

Charlie

Akonadi problem

[Christopher Judd]

Hi,


     For some time now, I haven't been able to use kontact or kmail, because 
Akonadi is not running.  This is on an amd64  testing box.  When I issue the 
command "akonadictl start", I get the following output:



Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
org.kde.pim.akonadiserver: database server stopped unexpectedly                 
                                                                            
org.kde.pim.akonadiserver: Database process exited unexpectedly during initial 
connection!                                                                     
          
org.kde.pim.akonadiserver: executable: "/usr/sbin/mysqld"                       
                                                                                
         
org.kde.pim.akonadiserver: arguments: 
("--defaults-file=/home/judd/.local/share/akonadi/mysql.conf", 
"--datadir=/home/judd/.local/share/akonadi/db_data/", 
"--socket=/tmp/akonadi-judd.TvrP8V/mysql.socket", 
"--pid-file=/tmp/akonadi-judd.TvrP8V/mysql.pid")                                
                                                         
org.kde.pim.akonadiserver: stdout: ""                                           
                                                                                
         
org.kde.pim.akonadiserver: stderr: "mysqld: [ERROR] Could not open required 
defaults file: /home/judd/.local/share/akonadi/mysql.conf\nmysqld: [ERROR] 
Fatal error in defaults handling. Program aborted!\n"                           
                                                                                
                            
org.kde.pim.akonadiserver: exit code: 1                                         
                                                                                
         
org.kde.pim.akonadiserver: process error: "Unknown error"                       
                                                                                
         
mysqladmin: connect to server at 'localhost' failed                             
                                                                                
         
error: 'Can't connect to local MySQL server through socket 
'/tmp/akonadi-judd.TvrP8V/mysql.socket' (2)'                                    
                               
Check that mysqld is running and that the socket: 
'/tmp/akonadi-judd.TvrP8V/mysql.socket' exists!                                 
                                        
org.kde.pim.akonadiserver: Failed to remove runtime connection config file      
                                                                                
         
org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally... 




The file ~/.local/share/akonadi/mysql.conf exists and is readable.  Any 
suggestions as to what is going wrong here?  Thanks.


-Chris                      

Re: extracting file with xz file tar.....

[David Wright]

On Thu 25 Jan 2018 at 19:54:14 (-0500), Gene Heskett wrote:
> On Thursday 25 January 2018 15:51:47 Brian wrote:
> 
> > On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote:
> > [Snipped more]
> >
> > > Cheers, Gene Heskett
> > > The above content, added by Maurice E. Heskett, is Copyright 2018 by
> > > Maurice E. Heskett.
> >
> > I've deleted just about everything in your post because I do not know
> > whether it is redistributable. Would you please clarify?
> 
> Yes, my bad, that is intended for the amanda list, whose new owner is 
> attempting to emulate yahoo all those years ago by claiming copyright on 
> everthing the server passes thru. Yahoo got burned at the stake in court 
> over that, and now CARBONITE INC is replaying it. I need to figure out a 
> way to make kmail use an individual signature per list. Without 
> concocting 40+ more identities.
> 
> In the meantime I'm trying to train this old dog to delete those 2 lines 
> when the message is not aimed at the amanda list.

As you may or may not have noticed, I (or, rather, mutt) insert a Reply-To:
header into all my posts on this list. It's generated by a folder-hook
triggered by my being in this (deblis) folder.

Perhaps you can coerce your email client to do the same sort of thing
with headers even if it can't manage it with signatures. Organization:
might be a suitable header to use.

Cheers,
David.

Re: PDF displayed incorrectly by certain software

[Greg Marks]

Thanks for the replies.  The most recent upgraded versions of Poppler
in Debian 9 (libpoppler64:amd64 0.48.0-2+deb9u2, libpoppler-glib8:amd64
0.48.0-2+deb9u2, poppler-utils 0.48.0-2+deb9u2, libpoppler-qt4-4:amd64
0.48.0-2+deb9u2, libpoppler-qt5-1:amd64 0.48.0-2+deb9u2) do enable
okular and xpdf to display the file

   https://gmarks.org/cklppaper.pdf

correctly.  But qpdfview is still displaying gibberish.

Regards,
Greg Marks

> Date: Thu, 25 Jan 2018 22:05:27 +0100
> From: Michael Lange 
> To: debian-user@lists.debian.org
> Cc: Ionel Mugurel Ciobîcă 
> Subject: [solved]Re: PDF displayed incorrectly by certain software
> 
> Hi,
> 
> On Tue, 23 Jan 2018 14:21:59 +0100
> Ionel Mugurel Ciobîcă  wrote:
> 
> > Downgraded some poppler packages and I can view now all pdf files
> > with xpdf. The difference between the old and new files now (for me)
> > is that they use (visible) different fonts.
> 
> Just for the record, today's upgrade to stretch's poppler packages fixed
> this issue, qdfview and xpdf display the affected pdf-files properly
> again.
> 
> Regards
> 
> Michael
> 
> 
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
> 
> Punishment becomes ineffective after a certain point.  Men become
> insensitive.
>   -- Eneg, "Patterns of Force", stardate 2534.7


signature.asc
Description: PGP signature

Re: PDF displayed incorrectly by certain software

[David Wright]

On Thu 25 Jan 2018 at 22:05:27 (+0100), Michael Lange wrote:
> Hi,
> 
> On Tue, 23 Jan 2018 14:21:59 +0100
> Ionel Mugurel Ciobîcă  wrote:
> 
> > Downgraded some poppler packages and I can view now all pdf files
> > with xpdf. The difference between the old and new files now (for me)
> > is that they use (visible) different fonts.
> 
> Just for the record, today's upgrade to stretch's poppler packages fixed
> this issue, qdfview and xpdf display the affected pdf-files properly
> again.

Not for me. I have the same/a similar issue with Chase credit card
statements. The blue graphical field separators and their text display
correctly, but the items area is blank.

However, if I scroll the pages, the items on the penultimate page
are displayed when I scroll up to it. The items on the first page
are always blank.

But the main difference between the old and new versions (upgraded
today) is that the new version spews error messages from the
configuration files, 152 of them in all.

Here are the first few. (The program stammers.)

Config Error: Unknown config file command 'unicodeMap' 
(/usr/share/xpdf/xpdfrc-arabic:2)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'cidToUnicode' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:2)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'unicodeMap' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:3)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'unicodeMap' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:4)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'unicodeMap' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:5)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'cMapDir' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:6)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'toUnicodeDir' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:7)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf
Config Error: Unknown config file command 'fontFileCC' 
(/usr/share/xpdf/xpdfrc-chinese-simplified:8)
Config Error: Some work needs to be done to suppport this option in the Poppler 
version of xpdf

This is a days-old installation of stretch 9.3 with ~/.xpdfrc hidden.
(Talking of which, they do seem to have fixed many of the interactive
commands (I use zoom, turn & continuous) that were missing throughout
jessie.)

Cheers,
David.

Re: extracting file with xz file tar.....

[Gene Heskett]

On Thursday 25 January 2018 15:51:47 Brian wrote:

> On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote:
> > On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote:
> > > Dear folks,
> > >
> > > I am trying to extract files from a tar xz file.
> > >
> > > The file is a kernel file.
> > >
> > > I ran the tar -xf command:
>
> [Snipped]
>
> > Cheers, Gene Heskett
> > The above content, added by Maurice E. Heskett, is Copyright 2018 by
> > Maurice E. Heskett.
>
> I've deleted just about everything in your post because I do not know
> whether it is redistributable. Would you please clarify?

Yes, my bad, that is intended for the amanda list, whose new owner is 
attempting to emulate yahoo all those years ago by claiming copyright on 
everthing the server passes thru. Yahoo got burned at the stake in court 
over that, and now CARBONITE INC is replaying it. I need to figure out a 
way to make kmail use an individual signature per list. Without 
concocting 40+ more identities.

In the meantime I'm trying to train this old dog to delete those 2 lines 
when the message is not aimed at the amanda list.

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: kernel 4.14.15 compilation using GCC 8 in unstable.......

[Michael Lange]

Hi,

On Thu, 25 Jan 2018 22:23:38 +
Michael Fothergill  wrote:

> Dear All,
> 
> I am continuing the discussion of the kernel 4.14.15 compilation in the
> Question on CVE-2017-5754 on Debian 8.9 post in a new post.
> 
> The reason I am running with this kernel and not the 4.15.0 rc9 kernel
> that is now available on kernel.org is that:
> 
> 1. It is stable
> 
> 2. I have never tried to compile a kernel in Debian before and want to
> make it a bit easier for me the first time would try.
> 
> 3.  kernel 4.14.15 does have the KPTI and retpoline patches in it, so
> it is a fair candidate for the GCC8 compiler to produce a kernel that
> the patch checker could confirm has these meltdown and spectre fixes
> are properly set up and active.

Ok, my advice if you don't want to give up yet :-)

Don't try to force the use of gcc-8 until you know that everything runs
properly with the default compiler.

Maybe you should follow the advice from the previously posted error
message:

"make[2]: Entering directory '/usr/src/linux-4.14.15'
Makefile:942: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y,
please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Stop."
   ^

(Ignore the messages about the debian directory.)
If similar messages as the above appear again, try to figure out what
needs to be additionally installed (some *-dev packages might still be
missing).

Once you get past the first few minutes of the procedure when using the
default compiler and you see how one module after the other is compiled,
hit Ctrl-C, do "make mrproper" and start over again with gcc-8.

This is just my 2¢, but I believe "debugging" one thing at a time is the
more promising approach here.

Good luck (and for now good night :)

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Virtue is a relative term.
-- Spock, "Friday's Child", stardate 3499.1

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

Hi,

On Thu, 25 Jan 2018 22:43:57 +
Michael Fothergill  wrote:

> ​Should it not be ARCH =​x86-64 rather than amd64.
> 
> It is so confusing.

Hmm, to be honest, I don't know. As I said, if you build for amd64 on an
amd64 system, you don't need to care about that, the current system's
architecture is the default.

And fyi, meanwhile I couldn't stop myself from booting siduction once
more. Installing one package or other taht people in archived mailing
lists suggested didn't help. Removing upper case characters from the path
neither. Then I tried and removed my clumsy attempts to force the use of
gcc-8 and found that with gcc-7 everything appears to work fine.
A closer look at what I am doing revealed that even the simple 
'yes ""|  make oldconfig' threw errors when using gcc-8. Seems like there
is a non-trivial problem here. The error message about the
missing /debian directory seems misleading, actually here there was some
C-code snippet underlined in red (printed just above that error message)
which I assume is likely the real problem. Maybe the best bet is to wait
until gcc-7.3 arrives in testing.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

A man either lives life as it happens to him, meets it head-on and
licks it, or he turns his back on it and starts to wither away.
-- Dr. Boyce, "The Menagerie" ("The Cage"), stardate
unknown

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 22:35, Michael Lange  wrote:

> Hi,
>
> On Thu, 25 Jan 2018 21:43:19 +
> Michael Fothergill  wrote:
>
> > > Not sure, but didn't you want the very latest 4.15rc for some
> > > Meltdown/Spectre issues? Are these also in 4.14.15?
> > >
> > > ​
> > >
> >
> > ​I copied the config file from the boot directory for the current 4.15.0
> > rc8 kernel as .config.
> >
> > I then ran make menuconfig and then realised I didn't need to change
> > anything and exited.
> >
> > I didn't run your
> >
> > yes ""|  make oldconfig thing - it seemed a bit peculiar to me.
> >
> > Maybe I should have.
> >
> > Instead I ran the command recommended here:
> >
> > https://wiki.debian.org/BuildADebianKernelPackage
> >
> > which was
> >
> > make ARCH=i386 defconfig
>
> Didn't want to build for amd64? If yes, you should have followed the
> advice from that page saying:
> "Create a defconfig with the following command, please change ARCH=i386
>
to match your target architecture:"
> I only built kernel packages for amd64 on an amd64 system, so I never had
> to explicitely specify ARCH.
>

​Should it not be ARCH =​x86-64 rather than amd64.

It is so confusing.

MF

>
>  >
> > I then ran
> >
> > make-kpkg
> >
> > and it then asked me lots of questions concerning kernel options that I
> > had to answer interactively.
> >
> > I think I should have tried your funny quotation pipe command with the
> > oldconfig option - it would have been better.
>
> Actually I don't remember which tutorial I borrowed this from; as far as
> I know it will set the default values for any new option not present in
> the old config.
>
> >
> > ​​
> >
> > ​Here is some of the output before it crashed:​
> >
> >
> >
> > kexec system call (KEXEC) [Y/n/?] y
> > kexec file based system call (KEXEC_FILE) [N/y/?] n
> > kernel crash dumps (CRASH_DUMP) [Y/n/?] y
> > kexec jump (KEXEC_JUMP) [N/y/?] n
> > Physical address where the kernel is loaded (PHYSICAL_START) [0x100]
> > 0x100
> > Build a relocatable kernel (RELOCATABLE) [Y/n/?] y
> >   Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE)
> > [Y/n/?] y
> > Alignment value to which kernel should be aligned (PHYSICAL_ALIGN)
> > [0x20] 0x20
> > Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y
> > Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y
> >   Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0)
> > [N/y/?] n
> >   Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n
> > vsyscall table for legacy applications
> >   1. Native (LEGACY_VSYSCALL_NATIVE)
> > > 2. Emulate (LEGACY_VSYSCALL_EMULATE)
> >   3. None (LEGACY_VSYSCALL_NONE)
> > choice[1-3?]: 2
> > Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n
> > #
> > # configuration written to .config
> > #
> > make[2]: Leaving directory '/usr/src/linux-4.14.15'
> > make\
> >  ARCH=x86_64  dep
> > make[2]: Entering directory '/usr/src/linux-4.14.15'
> > Makefile:942: *** "Cannot generate ORC metadata for
> > CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or
> > elfutils-libelf-devel".  Stop. make[2]: Leaving directory
> > '/usr/src/linux-4.14.15' debian/ruleset/targets/common.mk:194: recipe
> > for target 'debian/stamp/conf/kernel-conf' failed
> > make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
> > make[1]: Leaving directory '/usr/src/linux-4.14.15'
> > /usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
> > 'debian/stamp/conf/minimal_debian' failed
> > make: *** [debian/stamp/conf/minimal_debian] Error 2
> > Failed to create a ./debian directory:  at /usr/bin/make-kpkg line 970.
> > root@mikef-PC:/usr/src/linux-4.14.15#
>
> Funny thing: just for the sport I tried the same thing on a siduction
> system this evening and ended up with the same error message.
> Had no time to investigate yet, it looks a bit like this one:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804813
>
> but this one's old and claims to be solved.
> Here:
> http://forums.debian.net/viewtopic.php?t=74424
> it is suggested that an upper case letter in the path to the sources
> might be the culprit, but then I have upper case characters here on
> stretch too, which didn't harm.
> Here:
> http://forums.debian.net/viewtopic.php?t=116146
> it is suggested that installing gcc--plugin-dev might help,
> might be worth a try. However here on stretch nothing like this is
> installed, and still it works. Maybe libgcc--dev is missing?
> Here:
> https://superuser.com/questions/677372/error-when-compiling-linux-kernel
> someone suggests that bc must be installed. Got that here on stretch, not
> sure if it might be missing on siduction.
>
> >
> >
> > It has written things to the config file so I think I might be wise to
> > delete it, copy it over again
> > and repeat everything with the Shakespearian pipe command next time.
> >
> >
> >
> > Suggestions on recovering gracefully here are welcome.
>
> I always cleaned up the source directory with
>
> # make mrproper
>
> Afte

kernel 4.14.15 compilation using GCC 8 in unstable.......

[Michael Fothergill]

Dear All,

I am continuing the discussion of the kernel 4.14.15 compilation in the
Question on CVE-2017-5754 on Debian 8.9 post in a new post.

The reason I am running with this kernel and not the 4.15.0 rc9 kernel that
is now available on kernel.org is that:

1. It is stable

2. I have never tried to compile a kernel in Debian before and want to make
it a bit easier for me the first time would try.

3.  kernel 4.14.15 does have the KPTI and retpoline patches in it, so it is
a fair candidate for the GCC8 compiler to produce a kernel that the patch
checker could confirm has these meltdown and spectre fixes are properly set
up and active.

Cheers

Regards

MF

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

Hi,

On Thu, 25 Jan 2018 21:43:19 +
Michael Fothergill  wrote:

> > Not sure, but didn't you want the very latest 4.15rc for some
> > Meltdown/Spectre issues? Are these also in 4.14.15?
> >
> > ​
> >
> 
> ​I copied the config file from the boot directory for the current 4.15.0
> rc8 kernel as .config.
> 
> I then ran make menuconfig and then realised I didn't need to change
> anything and exited.
> 
> I didn't run your
> 
> yes ""|  make oldconfig thing - it seemed a bit peculiar to me.
> 
> Maybe I should have.
> 
> Instead I ran the command recommended here:
> 
> https://wiki.debian.org/BuildADebianKernelPackage
> 
> which was
> 
> make ARCH=i386 defconfig

Didn't want to build for amd64? If yes, you should have followed the
advice from that page saying:
"Create a defconfig with the following command, please change ARCH=i386
to match your target architecture:"
I only built kernel packages for amd64 on an amd64 system, so I never had
to explicitely specify ARCH.

> 
> I then ran
> 
> make-kpkg
> 
> and it then asked me lots of questions concerning kernel options that I
> had to answer interactively.
> 
> I think I should have tried your funny quotation pipe command with the
> oldconfig option - it would have been better.

Actually I don't remember which tutorial I borrowed this from; as far as
I know it will set the default values for any new option not present in
the old config.

> 
> ​​
> 
> ​Here is some of the output before it crashed:​
> 
> 
> 
> kexec system call (KEXEC) [Y/n/?] y
> kexec file based system call (KEXEC_FILE) [N/y/?] n
> kernel crash dumps (CRASH_DUMP) [Y/n/?] y
> kexec jump (KEXEC_JUMP) [N/y/?] n
> Physical address where the kernel is loaded (PHYSICAL_START) [0x100]
> 0x100
> Build a relocatable kernel (RELOCATABLE) [Y/n/?] y
>   Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE)
> [Y/n/?] y
> Alignment value to which kernel should be aligned (PHYSICAL_ALIGN)
> [0x20] 0x20
> Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y
> Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y
>   Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0)
> [N/y/?] n
>   Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n
> vsyscall table for legacy applications
>   1. Native (LEGACY_VSYSCALL_NATIVE)
> > 2. Emulate (LEGACY_VSYSCALL_EMULATE)
>   3. None (LEGACY_VSYSCALL_NONE)
> choice[1-3?]: 2
> Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n
> #
> # configuration written to .config
> #
> make[2]: Leaving directory '/usr/src/linux-4.14.15'
> make\
>  ARCH=x86_64  dep
> make[2]: Entering directory '/usr/src/linux-4.14.15'
> Makefile:942: *** "Cannot generate ORC metadata for
> CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or
> elfutils-libelf-devel".  Stop. make[2]: Leaving directory
> '/usr/src/linux-4.14.15' debian/ruleset/targets/common.mk:194: recipe
> for target 'debian/stamp/conf/kernel-conf' failed
> make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
> make[1]: Leaving directory '/usr/src/linux-4.14.15'
> /usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
> 'debian/stamp/conf/minimal_debian' failed
> make: *** [debian/stamp/conf/minimal_debian] Error 2
> Failed to create a ./debian directory:  at /usr/bin/make-kpkg line 970.
> root@mikef-PC:/usr/src/linux-4.14.15#

Funny thing: just for the sport I tried the same thing on a siduction
system this evening and ended up with the same error message.
Had no time to investigate yet, it looks a bit like this one:

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

but this one's old and claims to be solved.
Here:
http://forums.debian.net/viewtopic.php?t=74424
it is suggested that an upper case letter in the path to the sources
might be the culprit, but then I have upper case characters here on
stretch too, which didn't harm.
Here:
http://forums.debian.net/viewtopic.php?t=116146
it is suggested that installing gcc--plugin-dev might help,
might be worth a try. However here on stretch nothing like this is
installed, and still it works. Maybe libgcc--dev is missing?
Here:
https://superuser.com/questions/677372/error-when-compiling-linux-kernel
someone suggests that bc must be installed. Got that here on stretch, not
sure if it might be missing on siduction.

> 
> 
> It has written things to the config file so I think I might be wise to
> delete it, copy it over again
> and repeat everything with the Shakespearian pipe command next time.
> 
> 
> 
> Suggestions on recovering gracefully here are welcome.

I always cleaned up the source directory with 

# make mrproper

After that you should be able to start over again.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Earth -- mother of the most beautiful women in the universe.
-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 22:04, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

> Dear All,
>
> I ran it again after deleting the .config file, copy the one /boot over
> again
> and running the yes """| oldconfig command and makekpkg
>
> and it ran and crashed again:
>
> https://pastebin.com/GJkEMVvc
>
>
> ​Should I have run make clean or something before repeating everything?
>
> Regards
>
> MF​
>

​Dear All,

I am going to carry on with this discussion in a new post on kernel
compilation.

Thanks

MF​

Re: Question on CVE-2017-5754 on Debian 8.9

[Vincent Lefevre]

On 2018-01-25 21:20:23 +0100, Jochen Spieker wrote:
> You can use apt or aptitude for packages in experimental and I see no
> reason against doing that. You do not even need to pin experimental.
> Packages from experimental are automatically assigned priority 1, except
> upgrades for packages that you installed from experimental.
> 
> That means you can add experimental to your sources.list and apt will
> not automatically upgrade your packages from testing/sid to the versions
> from experimental. But when you manually select a version from
> experimental (using '-t experimantal'), apt will automatically upgrade
> to newer versions available from experimental. And when testing/sid
> contains a newer version, the one from experimental will be replaced by
> that one.

With aptitude, this is not true. See the discussions at:

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

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

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

Dear All,

I ran it again after deleting the .config file, copy the one /boot over
again
and running the yes """| oldconfig command and makekpkg

and it ran and crashed again:

https://pastebin.com/GJkEMVvc


​Should I have run make clean or something before repeating everything?

Regards

MF​

Re: Question on CVE-2017-5754 on Debian 8.9

[Vincent Lefevre]

On 2018-01-25 09:31:27 -0500, Greg Wooledge wrote:
> On Thu, Jan 25, 2018 at 03:24:21PM +0100, Vincent Lefevre wrote:
> > On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote:
> > > To use a package from experimental, you must download it directly, and
> > > install it directly.  You don't use apt or its cousins, unless it's
> > > to backfill dependencies (apt-get -f install) from your actual release.
> > 
> > aptitude installs experimental packages automatically.
> 
> It is terrifying.
> 
> (Seriously, if you've configured it to do that, WHY?!?  Do you hate
> your computer so much that you want it to die?)

No, I certainly haven't configured it to do that. Well, I've added

deb http://ftp.fr.debian.org/debian/ experimental main
deb-src http://ftp.fr.debian.org/debian/ experimental main

to /etc/apt/sources.list, but the goal was just to be able to install
experimental packages *manually*, with an explicit request. The fact
that aptitude assumes that the user may want to upgrade unstable
packages to experimental automatically (in order to satisfy
dependencies) is a really bad feature.

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

Re: How to rebuild a Debian package for a foreign architecture?

[Vincent Lefevre]

On 2018-01-25 14:53:14 +, Curt wrote:
> On 2018-01-25,   wrote:
> >
> > It seems that you are missing the '386 (or more precisely the '686)
> > executables. Perhaps you need the package dpkg-cross.
> >
> >> If I need binutils-i686-linux-gnu, shouldn't dpkg-buildpackage fail
> >> when checking the build dependencies?
> >
> > I'll leave that question to someone more knowledgeable.
> 
> I'm much less so, but I've heard people recommending pbuilder for
> this (chroot).
> 
>  pbuilder --create --architecture i386
>  pbuilder --build mypackage.dsc

IMHO, this is overkill, at least in my case. And I don't like to
require root just to build a package.

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

Re: How to rebuild a Debian package for a foreign architecture?

[Vincent Lefevre]

On 2018-01-25 15:30:02 +0100, to...@tuxteam.de wrote:
> On Thu, Jan 25, 2018 at 02:56:17PM +0100, Vincent Lefevre wrote:
> > To rebuild a Debian package, one can use:
> > 
> >   debuild -i -us -uc -b
> > 
> > But how to rebuild a Debian package for a foreign architecture?
> > In my case for i386 from an amd64 machine. I've tried
> > 
> >   debuild -i -us -uc -b -a i386
> > 
> > but the build fails at some point:
> > 
> > [...]
> > dh_strip -a
> > dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> > dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> > dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> > Can't exec "i686-linux-gnu-strip": No such file or directory at 
> > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 358.
> > [...]
> 
> It seems that you are missing the '386 (or more precisely the '686)
> executables. Perhaps you need the package dpkg-cross.

Installing dpkg-cross just installs: cross-config dpkg-cross
libconfig-auto-perl libdebian-dpkgcross-perl. This is not
sufficient.

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

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

> Not sure, but didn't you want the very latest 4.15rc for some
> Meltdown/Spectre issues? Are these also in 4.14.15?
>
> ​
>

​I copied the config file from the boot directory for the current 4.15.0
rc8 kernel as .config.

I then ran make menuconfig and then realised I didn't need to change
anything and exited.

I didn't run your

yes ""|  make oldconfig thing - it seemed a bit peculiar to me.

Maybe I should have.

Instead I ran the command recommended here:

https://wiki.debian.org/BuildADebianKernelPackage

which was

make ARCH=i386 defconfig

I then ran

make-kpkg

and it then asked me lots of questions concerning kernel options that I had
to answer interactively.

I think I should have tried your funny quotation pipe command with the
oldconfig option - it would have been better.

​​

​Here is some of the output before it crashed:​



kexec system call (KEXEC) [Y/n/?] y
kexec file based system call (KEXEC_FILE) [N/y/?] n
kernel crash dumps (CRASH_DUMP) [Y/n/?] y
kexec jump (KEXEC_JUMP) [N/y/?] n
Physical address where the kernel is loaded (PHYSICAL_START) [0x100]
0x100
Build a relocatable kernel (RELOCATABLE) [Y/n/?] y
  Randomize the address of the kernel image (KASLR) (RANDOMIZE_BASE)
[Y/n/?] y
Alignment value to which kernel should be aligned (PHYSICAL_ALIGN)
[0x20] 0x20
Randomize the kernel memory sections (RANDOMIZE_MEMORY) [Y/n/?] y
Support for hot-pluggable CPUs (HOTPLUG_CPU) [Y/?] y
  Set default setting of cpu0_hotpluggable (BOOTPARAM_HOTPLUG_CPU0) [N/y/?]
n
  Debug CPU0 hotplug (DEBUG_HOTPLUG_CPU0) [N/y/?] n
vsyscall table for legacy applications
  1. Native (LEGACY_VSYSCALL_NATIVE)
> 2. Emulate (LEGACY_VSYSCALL_EMULATE)
  3. None (LEGACY_VSYSCALL_NONE)
choice[1-3?]: 2
Built-in kernel command line (CMDLINE_BOOL) [N/y/?] n
#
# configuration written to .config
#
make[2]: Leaving directory '/usr/src/linux-4.14.15'
make\
 ARCH=x86_64  dep
make[2]: Entering directory '/usr/src/linux-4.14.15'
Makefile:942: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y,
please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Stop.
make[2]: Leaving directory '/usr/src/linux-4.14.15'
debian/ruleset/targets/common.mk:194: recipe for target
'debian/stamp/conf/kernel-conf' failed
make[1]: *** [debian/stamp/conf/kernel-conf] Error 2
make[1]: Leaving directory '/usr/src/linux-4.14.15'
/usr/share/kernel-package/ruleset/minimal.mk:93: recipe for target
'debian/stamp/conf/minimal_debian' failed
make: *** [debian/stamp/conf/minimal_debian] Error 2
Failed to create a ./debian directory:  at /usr/bin/make-kpkg line 970.
root@mikef-PC:/usr/src/linux-4.14.15#


It has written things to the config file so I think I might be wise to
delete it, copy it over again
and repeat everything with the Shakespearian pipe command next time.



Suggestions on recovering gracefully here are welcome.

Regards

MF




> ​
>
>
>
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> It would be illogical to assume that all conditions remain stable.
> -- Spock, "The Enterprise Incident", stardate 5027.3
>
>

Re: extracting file with xz file tar.....

[Roberto C . Sánchez]

On Thu, Jan 25, 2018 at 10:00:08PM +0100, Michael Lange wrote:
> On Thu, 25 Jan 2018 20:14:24 +
> Michael Fothergill  wrote:
> 
> > Dear folks,
> > 
> > I am trying to extract files from a tar xz file.
> 
> Why bother with a command line and not just do it from a gui file
> manager's context menu? Xfe and pcmanfm and probably the others as well
> handle this splendidly.
> 
You, sir, will now have to relinquish your geek card.

I mean, you might as well suggest that he just switch to MS Windows or
Mac OS X.

Regards,

-Roberto

-- 
Roberto C. Sánchez

[solved]Re: PDF displayed incorrectly by certain software

[Michael Lange]

Hi,

On Tue, 23 Jan 2018 14:21:59 +0100
Ionel Mugurel Ciobîcă  wrote:

> Downgraded some poppler packages and I can view now all pdf files
> with xpdf. The difference between the old and new files now (for me)
> is that they use (visible) different fonts.

Just for the record, today's upgrade to stretch's poppler packages fixed
this issue, qdfview and xpdf display the affected pdf-files properly
again.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Punishment becomes ineffective after a certain point.  Men become
insensitive.
-- Eneg, "Patterns of Force", stardate 2534.7

Re: extracting file with xz file tar.....

[Michael Lange]

On Thu, 25 Jan 2018 20:14:24 +
Michael Fothergill  wrote:

> Dear folks,
> 
> I am trying to extract files from a tar xz file.

Why bother with a command line and not just do it from a gui file
manager's context menu? Xfe and pcmanfm and probably the others as well
handle this splendidly.

Just a thought...

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

On my planet, to rest is to rest -- to cease using energy.  To me, it
is quite illogical to run up and down on green grass, using energy,
instead of saving it.
-- Spock, "Shore Leave", stardate 3025.2

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

On Thu, 25 Jan 2018 17:12:48 +
Michael Fothergill  wrote:



> My general strategy is as follows:
> 
> 1. Download the latest stable kernel from the kernel archives; this is
> 4.14.15 - I have done this.

Not sure, but didn't you want the very latest 4.15rc for some
Meltdown/Spectre issues? Are these also in 4.14.15?

> 
> 2. Use the  tar xf /usr/src/linux-source-4.14.15.tar.xz command to
> unpack the kernel source file.
> 
> ​3. cd to the directory where the kernel source lives
> 
> 4.  Reuse the config file from the 4.14.15 rc8 kernel I already have
> installed e.g. cp /boot/config-3.16.0-4-amd64
> ~/kernel/linux-source-3.16/.config
> 
> 5. run make menuconfig (I do this in gentoo) I will make sure
> libncurses5-dev (or does it need to be newer?) is installed to
> configure it using the recycled config file from 4 above.

This shouldn't be necessary, unless you want to enable something that's
turned off by default. That 'yes "" | make oldconfig' thing worked well
here and is surely faster :) 

> 
> 6. Run make-kpkg clean.
> 
> 7. Then run fakeroot make-kpkg --initrd --revision=1.0.custom
> kernel_image.
> 
> 8. Then install the kernel as follows: dpkg -i
> ../linux-image-4.14.15-subarchitecture_1.0.custom_i386.deb.
> 
> 9. Reboot and look for new kernel in grub menu and log in.
> 
> 10. Run the patch checker to see that KPTI and retpoline patched are
> turned on properly.
> 
> Please critique the above list.   I am going to read more documentation
> and improve it before going ahead with this.

Regards

Michael



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It would be illogical to assume that all conditions remain stable.
-- Spock, "The Enterprise Incident", stardate 5027.3

Re: extracting file with xz file tar.....

[Michael Fothergill]

On 25 January 2018 at 20:33, Greg Wooledge  wrote:

> On Thu, Jan 25, 2018 at 08:14:24PM +, Michael Fothergill wrote:
> > root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz
> >
> > Can anyone think of a command that will let me know where the files
> > went/confirm it ran properly?
>
> Use "tar -xvf ..." to get verbose output (filenames) during the extraction.
>

​Many thanks,  I did this and then realised that the creation date of Jan
23rd for the linux 4.14.15 directory created is for this kernel - that is
the date given for it being made on the kernel.org site.

I now what planet I am on here with this.

A trap here was that I already have a kernel installed which is 4.14.15 rc8
so I could have ​mistaken it for that so it was not as simple as looking
for a file with 4.14.15 in it etc in /usr/src etc.

It's OK.

I will try copying the config file from the 4.14.15rc8 kernel (where ever
that might live - I am going to have to learn to find them by sense of
smell) and use it for the compilation.

Cheers

MF




>
> Or, use "tar -tvf ..." to get a table of contents of the archive.
> (You probably want to pipe that through less, or some other pager.)
>
>

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 19:25, Brian  wrote:

> On Thu 25 Jan 2018 at 18:15:29 +, Michael Fothergill wrote:
>
> > Also is fakeroot installed by default or do I need to install it
> > separately?
>
> apt show fakeroot | grep -i priority
>
> What do you think?
>
> > Thanks for the hints here.
>
> Where are we going? It seems a long time getting there. :)
>

​It's OK.  I ran apt show fakeroot | grep -i priority
​
 and got:

root@mikef-PC:/usr/src# apt show fakeroot | grep -i priority

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

Priority: optional
root@mikef-PC:/usr/src#

Also I put the kernel file in /usr/src and then
ran the following:

tar -xaf linux-4.14.15.tar.xz

It seemed to run OK but I don't know where it put the unpacked files.

The creation dates show etc they are not in the /usr/src directory or in a
new directory created in it.

Some docs say you shouldn't put the src files in the src directory - but
others do.

Bit odd.

Comments appreciated.

Regards

MF


--
> Brian.
>
>

Re: extracting file with xz file tar.....

[Brian]

On Thu 25 Jan 2018 at 15:42:15 -0500, Gene Heskett wrote:

> On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote:
> 
> > Dear folks,
> >
> > I am trying to extract files from a tar xz file.
> >
> > The file is a kernel file.
> >
> > I ran the tar -xf command:

[Snipped]

> Cheers, Gene Heskett
> The above content, added by Maurice E. Heskett, is Copyright 2018 by 
> Maurice E. Heskett.

I've deleted just about everything in your post because I do not know
whether it is redistributable. Would you please clarify?

-- 
Brian.

Re: extracting file with xz file tar.....

[Greg Wooledge]

On Thu, Jan 25, 2018 at 03:42:15PM -0500, Gene Heskett wrote:
> running tar xf is asking tar to do something it cannot do, at least not 
> yet.

Says the wheezy user.  The newer tar versions will auto-detect the
compression type and run the appropriate decompression program.

wooledg:~$ tar tvf manpages_3.74.orig.tar.xz | head
drwxr-xr-x mtk/mtk   0 2014-10-02 18:01 man-pages-3.74/
drwxr-xr-x mtk/mtk   0 2014-10-02 18:01 man-pages-3.74/man2/
...

(Don't ask why I have that file; it was simply the first *.tar.xz I
found.)

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

Hi,

On Thu, 25 Jan 2018 18:26:52 +
Michael Fothergill  wrote:

> I have been looking at the web page here:
> 
> https://wiki.debian.org/BuildADebianKernelPackage
> 
> and noticed that the source file is supposed to be put in /usr/src it
> says.
> 
> It thinks the file would have a format like this:
> 
> 
> 
> *linux-source-x.x.tar.bz2*
> The file
> ​ I downloaded from the kernel.org site looks like this:
> 
> ​
> 
> linux-4.14.15.tar.xz
> 
> I think that is the same thing here (please correct me if I am wrong).

the tarball's format doesn't matter, you'll have to unpack it anyway :-)

> 
> It is currently sitting in my Downloads directory.
> 
> I am going to move it to the /usr/src directory and then run the other
> commands.

That doesn't matter either, I have done this from somewhere in ~/ , I
guess /usr/src is just a recommendation where the sources belong. Maybe
you'll need it there if you compile 3rd party modules or something, not
sure about that.


> I couldn't find the option talking about choosing the gcc version you
> mentioned - maybe the language was too coded for me.

It's right at the start of the man page, paragraph "DESCRIPTION":

" Also, please note that some versions of gcc do not interact well with
the kernel sources (gcc 2.95 has problems compiling the kernel without
the flag '-fno-strict-aliasing'. This issue has been taken care of for
recent kernels (2.2 and 2.4 series are fine) (I think you may have to
edit the makefile for older kernels, or something). You may control which
version of gcc used in kernel compilation by setting the Makefile
variables CC and HOSTCC in the top level kernel Makefile. You can do this
simply by setting the environment variable MAKEFLAGS. To observe, try:


  % KBUILD_VERBOSE=1 MAKEFLAGS="CC=gcc-4.4" make-kpkg configure 
"

> 
> Also​
> 
> ​if I use this command:​
> 
> make ARCH=i386 defconfig
> 
> ​should ARCH=amd64 or something be appropriate for me running my amd64
> kaveri box here?​

I never explicitely defined ARCH, I guess you only need to do so if you
e.g. want to compile an i386 kernel on an amd64 machine or vice versa.


> 
> ​Also is fakeroot installed by default or do I need to install it
> separately?

That's a separate package.

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1

Re: extracting file with xz file tar.....

[Roberto C . Sánchez]

On Thu, Jan 25, 2018 at 03:42:15PM -0500, Gene Heskett wrote:
> 
> It would help to run the correct unpacker. xz is relatively new, and the 
> command is: xz -d packagename.xz. If its a tarball, thats what you'll 
> get back.  If it an image for an sd card, that's what you will get back.
> 
> running tar xf is asking tar to do something it cannot do, at least not 
> yet.
> 
> man xz can be quite educational ;-)
> 
>From tar(1), on a Debian stretch system:

   -J, --xz
  Filter the archive through xz(1).

I am relatively confident that it was there at least in jessie versions
of tar as well.

Regards,

-Roberto

-- 
Roberto C. Sánchez

Re: extracting file with xz file tar.....

[Nicolas George]

Gene Heskett (2018-01-25):
> It would help to run the correct unpacker. xz is relatively new, and the 
> command is: xz -d packagename.xz. If its a tarball, thats what you'll 
> get back.  If it an image for an sd card, that's what you will get back.
> 
> running tar xf is asking tar to do something it cannot do, at least not 
> yet.
> 
> man xz can be quite educational ;-)

The 1990's are calling, they want their man pages back.

Even in the 1990's, no competent Unix user would never unpack an archive
as a file, they would use pipelines. And nowadays, tar know how to do
that all by itself, including detecting the archive type.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: extracting file with xz file tar.....

[Gene Heskett]

On Thursday 25 January 2018 15:14:24 Michael Fothergill wrote:

> Dear folks,
>
> I am trying to extract files from a tar xz file.
>
> The file is a kernel file.
>
> I ran the tar -xf command:
>
> root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz
>
> If you look at the date and time then you can see that no directories
> have been created with from it in the directory.
>
> root@mikef-PC:/usr/src# date
> Thu 25 Jan 20:11:23 GMT 2018
> root@mikef-PC:/usr/src# ls -l
> total 12
> drwxrwxr-x 24 root  root   4096 Jan 23 18:58 linux-4.14.15
> -rw-r--r--  1 mikef mikef 100837776 Jan 25 16:43 linux-4.14.15.tar.xz
> drwxr-xr-x  2 root  root   4096 Jan 25 18:02 linux-config-4.14
> drwxr-xr-x  4 root  root   4096 Jan 25 00:01
> linux-headers-4.14.0-3-amd64
> drwxr-xr-x  4 root  root   4096 Jan 25 00:01
> linux-headers-4.14.0-3-common
> drwxr-xr-x  4 root  root   4096 Jan 24 16:32
> linux-headers-4.9.0-4-amd64 drwxr-xr-x  4 root  root   4096 Jan 24
> 16:33
> linux-headers-4.9.0-4-common
> lrwxrwxrwx  1 root  root 24 Jan 14 19:45 linux-kbuild-4.14 ->
> ../lib/linux-kbuild-4.14
> lrwxrwxrwx  1 root  root 24 Jan 15 04:43 linux-kbuild-4.15 ->
> ../lib/linux-kbuild-4.15
> lrwxrwxrwx  1 root  root 23 Aug  6 05:24 linux-kbuild-4.9 ->
> ../lib/linux-kbuild-4.9
> -rw-r--r--  1 root  root 216052 Jan 14 19:45
> linux-patch-4.14-rt.patch.xz
> -rw-r--r--  1 root  root  103701828 Jan 14 19:45
> linux-source-4.14.tar.xz drwxr-xr-x  8 root  root   4096 Nov 18
> 09:15 open-vm-tools-10.1.5 root@mikef-PC:/usr/src#
>
> Can anyone think of a command that will let me know where the files
> went/confirm it ran properly?
>
> Cheers
>
> Michael Fothergill

It would help to run the correct unpacker. xz is relatively new, and the 
command is: xz -d packagename.xz. If its a tarball, thats what you'll 
get back.  If it an image for an sd card, that's what you will get back.

running tar xf is asking tar to do something it cannot do, at least not 
yet.

man xz can be quite educational ;-)

Cheers, Gene Heskett
The above content, added by Maurice E. Heskett, is Copyright 2018 by 
Maurice E. 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: extracting file with xz file tar.....

[Greg Wooledge]

On Thu, Jan 25, 2018 at 08:14:24PM +, Michael Fothergill wrote:
> root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz
> 
> Can anyone think of a command that will let me know where the files
> went/confirm it ran properly?

Use "tar -xvf ..." to get verbose output (filenames) during the extraction.

Or, use "tar -tvf ..." to get a table of contents of the archive.
(You probably want to pipe that through less, or some other pager.)

Re: Question on CVE-2017-5754 on Debian 8.9

[Sven Joachim]

On 2018-01-25 21:20 +0100, Jochen Spieker wrote:

> You can use apt or aptitude for packages in experimental and I see no
> reason against doing that. You do not even need to pin experimental.
> Packages from experimental are automatically assigned priority 1, except
> upgrades for packages that you installed from experimental.

Packages installed from experimental also have priority 1.

> That means you can add experimental to your sources.list and apt will
> not automatically upgrade your packages from testing/sid to the versions
> from experimental. But when you manually select a version from
> experimental (using '-t experimantal'), apt will automatically upgrade
> to newer versions available from experimental.

No, it won't.  For that the priority needs to be at least 100, since
this is the priority of the version which is installed on the system.
See apt_preferences(5) and the blog at [1].

Cheers,
   Sven


1. http://petereisentraut.blogspot.de/2010/07/increasing-priority-of-debian.html

Re: extracting file with xz file tar.....

[Nicolas George]

Michael Fothergill (2018-01-25):
> If you look at the date and time then you can see that no directories have
> been created with from it in the directory.

tar restores the mtime of extracted files and directories. You need to
look at the ctime.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

extracting file with xz file tar.....

[Michael Fothergill]

Dear folks,

I am trying to extract files from a tar xz file.

The file is a kernel file.

I ran the tar -xf command:

root@mikef-PC:/usr/src# tar -xf linux-4.14.15.tar.xz

If you look at the date and time then you can see that no directories have
been created with from it in the directory.

root@mikef-PC:/usr/src# date
Thu 25 Jan 20:11:23 GMT 2018
root@mikef-PC:/usr/src# ls -l
total 12
drwxrwxr-x 24 root  root   4096 Jan 23 18:58 linux-4.14.15
-rw-r--r--  1 mikef mikef 100837776 Jan 25 16:43 linux-4.14.15.tar.xz
drwxr-xr-x  2 root  root   4096 Jan 25 18:02 linux-config-4.14
drwxr-xr-x  4 root  root   4096 Jan 25 00:01
linux-headers-4.14.0-3-amd64
drwxr-xr-x  4 root  root   4096 Jan 25 00:01
linux-headers-4.14.0-3-common
drwxr-xr-x  4 root  root   4096 Jan 24 16:32 linux-headers-4.9.0-4-amd64
drwxr-xr-x  4 root  root   4096 Jan 24 16:33
linux-headers-4.9.0-4-common
lrwxrwxrwx  1 root  root 24 Jan 14 19:45 linux-kbuild-4.14 ->
../lib/linux-kbuild-4.14
lrwxrwxrwx  1 root  root 24 Jan 15 04:43 linux-kbuild-4.15 ->
../lib/linux-kbuild-4.15
lrwxrwxrwx  1 root  root 23 Aug  6 05:24 linux-kbuild-4.9 ->
../lib/linux-kbuild-4.9
-rw-r--r--  1 root  root 216052 Jan 14 19:45
linux-patch-4.14-rt.patch.xz
-rw-r--r--  1 root  root  103701828 Jan 14 19:45 linux-source-4.14.tar.xz
drwxr-xr-x  8 root  root   4096 Nov 18 09:15 open-vm-tools-10.1.5
root@mikef-PC:/usr/src#

Can anyone think of a command that will let me know where the files
went/confirm it ran properly?

Cheers

Michael Fothergill

Re: Question on CVE-2017-5754 on Debian 8.9

[Jochen Spieker]

Greg Wooledge:
> 
> To use a package from experimental, you must download it directly, and
> install it directly.  You don't use apt or its cousins, unless it's
> to backfill dependencies (apt-get -f install) from your actual release.

Everything you wrote is correct but this paragraph.

You can use apt or aptitude for packages in experimental and I see no
reason against doing that. You do not even need to pin experimental.
Packages from experimental are automatically assigned priority 1, except
upgrades for packages that you installed from experimental.

That means you can add experimental to your sources.list and apt will
not automatically upgrade your packages from testing/sid to the versions
from experimental. But when you manually select a version from
experimental (using '-t experimantal'), apt will automatically upgrade
to newer versions available from experimental. And when testing/sid
contains a newer version, the one from experimental will be replaced by
that one.

J.
-- 
I am on the payroll of a company to whom I owe my undying gratitude.
[Agree]   [Disagree]
 


signature.asc
Description: PGP signature

Re: Question on CVE-2017-5754 on Debian 8.9

[Brian]

On Thu 25 Jan 2018 at 18:15:29 +, Michael Fothergill wrote:

> Also is fakeroot installed by default or do I need to install it
> separately?

apt show fakeroot | grep -i priority

What do you think?
 
> Thanks for the hints here.

Where are we going? It seems a long time getting there. :)

-- 
Brian.

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

I have been looking at the web page here:

https://wiki.debian.org/BuildADebianKernelPackage

and noticed that the source file is supposed to be put in /usr/src it says.

It thinks the file would have a format like this:



*linux-source-x.x.tar.bz2*
The file
​ I downloaded from the kernel.org site looks like this:

​

linux-4.14.15.tar.xz

I think that is the same thing here (please correct me if I am wrong).

It is currently sitting in my Downloads directory.

I am going to move it to the /usr/src directory and then run the other
commands.

Cheers

MF

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 17:20, Michael Lange  wrote:

> On Thu, 25 Jan 2018 15:59:04 +
> Michael Fothergill  wrote:
>
> > ​I have become sid and installed a ton of dependencies from the
> > experimental respository and finally installed gcc 8.
>
> Oh, from a quick glance it looked like half a dozen might suffice :-)
>
> >
> > After some rehab I will study the web page on compiling kernels in
> > debian.
> >
> > I need to get the set up to use the GCC 8 compiler I have just
> > installed.
>
> I have done this a lot lately (needed a custom kernel for a new laptop).
> Basically all I had to do was install make-kpkg + a number of other
> related packages. Once all that was in place I just had to pick a source
> tarball from kernel.org and unzip it, copy the latest config I had
> in /boot to linux-/.config , then run
>
> # yes "" | make oldconfig
>
> from within the source-directory and then start compiling with
> something like
>
> # fakeroot make-kpkg --initrd --append-to-version=-
> kernel-image kernel-headers
>
> The man page of make-kpkg gives hints about how to
> force a gcc version in its description paragraph, never tried this
> myself, though.
>

​I installed the kernel-package thing and then looked at the make-kpkg man
entry.

I couldn't find the option talking about choosing the gcc version you
mentioned - maybe the language was too coded for me.

Also​

​if I use this command:​

make ARCH=i386 defconfig

​should ARCH=amd64 or something be appropriate for me running my amd64
kaveri box here?​

​Also is fakeroot installed by default or do I need to install it
separately?

​Thanks for the hints here.

MF





>
> Good luck!!
>
> Michael
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Computers make excellent and efficient servants, but I have no wish to
> serve under them.  Captain, a starship also runs on loyalty to one
> man.  And nothing can replace it or him.
> -- Spock, "The Ultimate Computer", stardate 4729.4
>
>

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 15:59, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

>
>
> On 25 January 2018 at 13:14, Michael Fothergill <
> michael.fotherg...@gmail.com> wrote:
>
>>
>>
>> On 25 January 2018 at 13:01, Greg Wooledge  wrote:
>>
>>> On Thu, Jan 25, 2018 at 12:36:46PM +, Michael Fothergill wrote:
>>> > ​If I become sid and install the kernel correctly, could I go back to
>>> being
>>> > just buster (sounds like an energy drink) and carry on using the new
>>> kernel?
>>>
>>> No.
>>>
>>> ​It seems I have to become sid here.
>>
>
> ​I have become sid and installed a ton of dependencies from the
> experimental respository and finally installed gcc 8.
>
> After some rehab I will study the web page on compiling kernels in debian.
>
> I need to get the set up to use the GCC 8 compiler I have just installed.
>
> Cheers
>
> MF​
>

​OK, I went through the dependency detox program (and had some electrodes
hooked up to my ears etc) and made a good recovery.

I looked at some web pages on the debian way of compiling kernels etc.

My general strategy is as follows:

1. Download the latest stable kernel from the kernel archives; this is
4.14.15 - I have done this.

2. Use the  tar xf /usr/src/linux-source-4.14.15.tar.xz command to unpack
the kernel source file.

​3. cd to the directory where the kernel source lives

4.  Reuse the config file from the 4.14.15 rc8 kernel I already have
installed e.g. cp /boot/config-3.16.0-4-amd64
~/kernel/linux-source-3.16/.config

5. run make menuconfig (I do this in gentoo) I will make sure
libncurses5-dev (or does it need to be newer?) is installed to configure it
using the recycled config file from 4 above.

6. Run make-kpkg clean.

7. Then run fakeroot make-kpkg --initrd --revision=1.0.custom kernel_image.

8. Then install the kernel as follows: dpkg -i
../linux-image-4.14.15-subarchitecture_1.0.custom_i386.deb.

9. Reboot and look for new kernel in grub menu and log in.

10. Run the patch checker to see that KPTI and retpoline patched are turned
on properly.

Please critique the above list.   I am going to read more documentation and
improve it before going ahead with this.

Cheers

MF

















>
>
>
>>
>>
>> MF​
>>
>>
>>
>

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

On Thu, 25 Jan 2018 15:59:04 +
Michael Fothergill  wrote:

> ​I have become sid and installed a ton of dependencies from the
> experimental respository and finally installed gcc 8.

Oh, from a quick glance it looked like half a dozen might suffice :-)

> 
> After some rehab I will study the web page on compiling kernels in
> debian.
> 
> I need to get the set up to use the GCC 8 compiler I have just
> installed.

I have done this a lot lately (needed a custom kernel for a new laptop).
Basically all I had to do was install make-kpkg + a number of other
related packages. Once all that was in place I just had to pick a source
tarball from kernel.org and unzip it, copy the latest config I had
in /boot to linux-/.config , then run

# yes "" | make oldconfig

from within the source-directory and then start compiling with
something like

# fakeroot make-kpkg --initrd --append-to-version=- 
kernel-image kernel-headers

The man page of make-kpkg gives hints about how to
force a gcc version in its description paragraph, never tried this
myself, though.

Good luck!!

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Computers make excellent and efficient servants, but I have no wish to
serve under them.  Captain, a starship also runs on loyalty to one
man.  And nothing can replace it or him.
-- Spock, "The Ultimate Computer", stardate 4729.4

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 13:14, Michael Fothergill <
michael.fotherg...@gmail.com> wrote:

>
>
> On 25 January 2018 at 13:01, Greg Wooledge  wrote:
>
>> On Thu, Jan 25, 2018 at 12:36:46PM +, Michael Fothergill wrote:
>> > ​If I become sid and install the kernel correctly, could I go back to
>> being
>> > just buster (sounds like an energy drink) and carry on using the new
>> kernel?
>>
>> No.
>>
>> ​It seems I have to become sid here.
>

​I have become sid and installed a ton of dependencies from the
experimental respository and finally installed gcc 8.

After some rehab I will study the web page on compiling kernels in debian.

I need to get the set up to use the GCC 8 compiler I have just installed.

Cheers

MF​



>
>
> MF​
>
>
>

Re: Question on CVE-2017-5754 on Debian 8.9

[David Wright]

On Thu 25 Jan 2018 at 09:31:27 (-0500), Greg Wooledge wrote:
> On Thu, Jan 25, 2018 at 03:24:21PM +0100, Vincent Lefevre wrote:
> > On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote:
> > > To use a package from experimental, you must download it directly, and
> > > install it directly.  You don't use apt or its cousins, unless it's
> > > to backfill dependencies (apt-get -f install) from your actual release.
> > 
> > aptitude installs experimental packages automatically.
> 
> It is terrifying.
> 
> (Seriously, if you've configured it to do that, WHY?!?  Do you hate
> your computer so much that you want it to die?)

Perhaps they haven't spotted the depository's symlink

lrwxrwxrwx  1  1176 1176  12 Aug 04  2008 rc-buggy -> experimental

Cheers,
David.

Re: How to rebuild a Debian package for a foreign architecture?

[Curt]

On 2018-01-25,   wrote:
>
> It seems that you are missing the '386 (or more precisely the '686)
> executables. Perhaps you need the package dpkg-cross.
>
>> If I need binutils-i686-linux-gnu, shouldn't dpkg-buildpackage fail
>> when checking the build dependencies?
>
> I'll leave that question to someone more knowledgeable.

I'm much less so, but I've heard people recommending pbuilder for this (chroot).

 pbuilder --create --architecture i386
 pbuilder --build mypackage.dsc

etc...

> Cheers
> - -- tomás
>
>


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

Re: Question on CVE-2017-5754 on Debian 8.9

[Greg Wooledge]

On Thu, Jan 25, 2018 at 03:24:21PM +0100, Vincent Lefevre wrote:
> On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote:
> > To use a package from experimental, you must download it directly, and
> > install it directly.  You don't use apt or its cousins, unless it's
> > to backfill dependencies (apt-get -f install) from your actual release.
> 
> aptitude installs experimental packages automatically.

It is terrifying.

(Seriously, if you've configured it to do that, WHY?!?  Do you hate
your computer so much that you want it to die?)

Re: How to rebuild a Debian package for a foreign architecture?

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jan 25, 2018 at 02:56:17PM +0100, Vincent Lefevre wrote:
> To rebuild a Debian package, one can use:
> 
>   debuild -i -us -uc -b
> 
> But how to rebuild a Debian package for a foreign architecture?
> In my case for i386 from an amd64 machine. I've tried
> 
>   debuild -i -us -uc -b -a i386
> 
> but the build fails at some point:
> 
> [...]
> dh_strip -a
> dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
> Can't exec "i686-linux-gnu-strip": No such file or directory at 
> /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 358.
> [...]

It seems that you are missing the '386 (or more precisely the '686)
executables. Perhaps you need the package dpkg-cross.

> If I need binutils-i686-linux-gnu, shouldn't dpkg-buildpackage fail
> when checking the build dependencies?

I'll leave that question to someone more knowledgeable.

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

iEYEARECAAYFAlpp6eoACgkQBcgs9XrR2kbzfwCfWeMl36zg2mSBoDSuj4s/yam6
/TkAniKmKJKviZoyjwvE5wEDwYXS+Ree
=Z/As
-END PGP SIGNATURE-

Re: Question on CVE-2017-5754 on Debian 8.9

[Vincent Lefevre]

On 2018-01-24 11:19:36 -0500, Greg Wooledge wrote:
> To use a package from experimental, you must download it directly, and
> install it directly.  You don't use apt or its cousins, unless it's
> to backfill dependencies (apt-get -f install) from your actual release.

aptitude installs experimental packages automatically.

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

How to rebuild a Debian package for a foreign architecture?

[Vincent Lefevre]

To rebuild a Debian package, one can use:

  debuild -i -us -uc -b

But how to rebuild a Debian package for a foreign architecture?
In my case for i386 from an amd64 machine. I've tried

  debuild -i -us -uc -b -a i386

but the build fails at some point:

[...]
dh_strip -a
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
dh_strip: Compatibility levels before 9 are deprecated (level 7 in use)
Can't exec "i686-linux-gnu-strip": No such file or directory at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 358.
[...]

If I need binutils-i686-linux-gnu, shouldn't dpkg-buildpackage fail
when checking the build dependencies?

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

Re: Network setup by installer

[Mark Fletcher]

On Sat, Jan 20, 2018 at 10:59:31AM +, Brian wrote:
> 
> The technique just replaces installing over a wireless link from the
> start. I've been wondering why you chose not to do that and avoid the
> extra work.

Sorry for the delay in replying. An early draft of one of my previous 
mails in this thread pre-emptively addressed that question, but I have 
been fairly aggressively self-editing on this thread so as not to 
attract the ire of those who are triggered by being expected to read 
more than a few lines of text.

I had 2 reasons (no claim is made that they were good ones) not to do 
the install via WiFi in the first place -- firstly I wasn't sure if the 
installer would be able to use my WiFi out of the box before trying it 
(eg firmware in contrib or non-free or something) and didn't want the 
hassle of getting into an install and finding it falling over -- I have 
this probably irrational desire to see the install go smoothly first 
time. Probably been working in a corporate IT environment too long.

Secondly I knew the net install would be doing a lot of downloading and 
believed (possibly erroneously) that it would be faster over a wired 
connection, especially if the wireless connection out of the box were in 
any way compromised eg old / dodgy / incorrectly selected firmware. 
The wireless part of my home netwxork is moderately populous, the wired 
part much less so.

Mark

Re: bash array

[Gokan Atmaca]

> ===
> #!/bin/sh
> exec 3< "user.list"
> exec 4< "pass.list"
>
> while IFS= read -r user <&3 && IFS= read -r pass <&4
> do
>   exampleprogram "$user" "$pass"
> done
>
> exec 3<&-
> exec 4<&-

I arranged according to this example. Very thanks.

On Thu, Jan 25, 2018 at 4:34 PM, Greg Wooledge  wrote:
> On Thu, Jan 25, 2018 at 03:35:35PM +0300, Gokan Atmaca wrote:
>> The problem is: I can pull the users one by one. I can not do the same
>> for passwords.
>
> Why not?
>
>> Do I need to use "Mapfile" for this?
>
> How would we know?  You haven't told us what is in the files, or what
> you want to DO with the contents of the files.
>
>> passwords=(cat $pass.list)
>
> Is wrong.
>
>> mapfile -t pass < "$passwords"
>
> Would be OK if $passwords contains the NAME of the file.  Is WRONG if
> $passwords is a string containing the CONTENTS of the file.
>
> Is also WRONG if passwords is an array containing the word "cat" and the
> expansion of "$pass" with the string .list appended to it, which is what
> your previous line created.
>
>> example-script:
>>-- user.list
>>   a
>>   b
>>   c
>>
>>   -- pass.list
>>  xxx
>>  yyy
>>  zzz
>
> With all that whitespace?  Or should I just assume that the "xxx" is
> NOT indented as shown, but is instead an entire line?
>
> What do you want to DO with these files?
>
>> script:
>>
>> #!/bin/bash
>>
>>
>> pass=$(cat pass.list)
>
> Now, you see, this is ENTIRELY DIFFERENT from what you showed up above.
>
> Do you see the difference?  Look at the two lines again:
>
>> passwords=(cat $pass.list)
>
>> pass=$(cat pass.list)
>
> If you can't see the difference, you can't write computer programs.
>
> Moving on
>
>> for i in user=$(cat user.list); do exampleporagram $i $pass; done
>
> Syntax errors.  Logic errors.  Cannot even make SENSE of this.
>
> Are you trying to read ONE USERNAME and ONE PASSWORD at a time, and
> pass each PAIR to your "exampleprogram"?
>
>
>> On Mon, Jan 15, 2018 at 5:39 PM, Greg Wooledge  wrote:
>> > What kind of array do you want?  Why do you even want an array?
>> >
>> > What is your program supposed to do with these users and passwords?
>
> Can't you just write ONE SENTENCE to tell us the objective of the script?
>
> Let's go out on a limb and assume "I want to read one username and
> one password at a time, and pass them as a pair of arguments to
> 'exampleprogram'."
>
> The way you would do that is to open the two files, and then read a
> line at a time from each file, and then close the files.
>
> Like this:
>
> ===
> #!/bin/sh
> exec 3< "user.list"
> exec 4< "pass.list"
>
> while IFS= read -r user <&3 && IFS= read -r pass <&4
> do
>   exampleprogram "$user" "$pass"
> done
>
> exec 3<&-
> exec 4<&-
> ===
>
>
> See the following pages:
>
> http://mywiki.wooledge.org/Quotes
> http://mywiki.wooledge.org/FileDescriptor
> http://mywiki.wooledge.org/BashFAQ/001
>
> Then read this page again, because I know you didn't read it the
> first time:
>
> http://mywiki.wooledge.org/Quotes
>
> Then keep reading it over and over until you UNDERSTAND it.
>
>
> You do not need an array for this.  You don't even need bash features.
> I used pure POSIX sh up there, hence the #!/bin/sh shebang.
>
>
> P.S. read http://mywiki.wooledge.org/Quotes
>
> Also, be sure you quote properly.
>
> I'm serious.
>
> Quotes.
>
> They are NOT optional.
>

Re: bash array

[Greg Wooledge]

On Thu, Jan 25, 2018 at 03:35:35PM +0300, Gokan Atmaca wrote:
> The problem is: I can pull the users one by one. I can not do the same
> for passwords.

Why not?

> Do I need to use "Mapfile" for this?

How would we know?  You haven't told us what is in the files, or what
you want to DO with the contents of the files.

> passwords=(cat $pass.list)

Is wrong.

> mapfile -t pass < "$passwords"

Would be OK if $passwords contains the NAME of the file.  Is WRONG if
$passwords is a string containing the CONTENTS of the file.

Is also WRONG if passwords is an array containing the word "cat" and the
expansion of "$pass" with the string .list appended to it, which is what
your previous line created.

> example-script:
>-- user.list
>   a
>   b
>   c
> 
>   -- pass.list
>  xxx
>  yyy
>  zzz

With all that whitespace?  Or should I just assume that the "xxx" is
NOT indented as shown, but is instead an entire line?

What do you want to DO with these files?

> script:
> 
> #!/bin/bash
> 
> 
> pass=$(cat pass.list)

Now, you see, this is ENTIRELY DIFFERENT from what you showed up above.

Do you see the difference?  Look at the two lines again:

> passwords=(cat $pass.list)

> pass=$(cat pass.list)

If you can't see the difference, you can't write computer programs.

Moving on

> for i in user=$(cat user.list); do exampleporagram $i $pass; done

Syntax errors.  Logic errors.  Cannot even make SENSE of this.

Are you trying to read ONE USERNAME and ONE PASSWORD at a time, and
pass each PAIR to your "exampleprogram"?


> On Mon, Jan 15, 2018 at 5:39 PM, Greg Wooledge  wrote:
> > What kind of array do you want?  Why do you even want an array?
> >
> > What is your program supposed to do with these users and passwords?

Can't you just write ONE SENTENCE to tell us the objective of the script?

Let's go out on a limb and assume "I want to read one username and
one password at a time, and pass them as a pair of arguments to
'exampleprogram'."

The way you would do that is to open the two files, and then read a
line at a time from each file, and then close the files.

Like this:

===
#!/bin/sh
exec 3< "user.list"
exec 4< "pass.list"

while IFS= read -r user <&3 && IFS= read -r pass <&4
do
  exampleprogram "$user" "$pass"
done

exec 3<&-
exec 4<&-
===


See the following pages:

http://mywiki.wooledge.org/Quotes
http://mywiki.wooledge.org/FileDescriptor
http://mywiki.wooledge.org/BashFAQ/001

Then read this page again, because I know you didn't read it the
first time:

http://mywiki.wooledge.org/Quotes

Then keep reading it over and over until you UNDERSTAND it.


You do not need an array for this.  You don't even need bash features.
I used pure POSIX sh up there, hence the #!/bin/sh shebang.


P.S. read http://mywiki.wooledge.org/Quotes

Also, be sure you quote properly.

I'm serious.

Quotes.

They are NOT optional.

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 13:01, Greg Wooledge  wrote:

> On Thu, Jan 25, 2018 at 12:36:46PM +, Michael Fothergill wrote:
> > ​If I become sid and install the kernel correctly, could I go back to
> being
> > just buster (sounds like an energy drink) and carry on using the new
> kernel?
>
> No.
>
> ​It seems I have to become sid here.


MF​

Re: Question on CVE-2017-5754 on Debian 8.9

[Greg Wooledge]

On Thu, Jan 25, 2018 at 12:36:46PM +, Michael Fothergill wrote:
> ​If I become sid and install the kernel correctly, could I go back to being
> just buster (sounds like an energy drink) and carry on using the new kernel?

No.

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

>>
> ​I tried installing gcc 8 on buster.   It needs cpp8 which needs
> ​libmrpfr6
>
> ie this
>
> https://packages.debian.org/unstable/main/libmpfr6
>
> which looks like its about being sid again.​
>
>
> ​I need to go to dependency rehab and sing the dem bones song again.
>
> Suggestions on avoiding becoming sid/krankenhaus/unstable/12 step program
> welcome.
>
> Regards
>
> MF
>

​If I become sid and install the kernel correctly, could I go back to being
just buster (sounds like an energy drink) and carry on using the new kernel?

Cheers

MF



​


>
>
>  ​
>
>
>> Then I guess you would have to compile the kernel from source, which
>> actually isn't too hard with make-kpkg (however I never tried to force
>> make-kpkg to use a certain, non-system-default compiler, but that's surely
>> possible).
>>
>> Regards
>>
>> Michael
>>
>>
>> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>>
>> Every living thing wants to survive.
>> -- Spock, "The Ultimate Computer", stardate 4731.3
>>
>>
>

Re: Debian mate wifi

[Jude DaShiell]

Sure it will Michael on whatever alternate connection he used to send 
these messages in the first place. :D
On Thu, 25 Jan 2018, Jeroen Mathon 
wrote:



Date: Thu, 25 Jan 2018 06:06:23
From: Jeroen Mathon 
To: Jude DaShiell 
Cc: michael caron couturier , debian-user@lists.debian.org
Subject: Re: Debian mate wifi
Resent-Date: Thu, 25 Jan 2018 11:06:41 + (UTC)
Resent-From: debian-user@lists.debian.org

Well Jude,

I think that will wonderfully when the problem he has is that he cannot
establish an Wi-Fi connection.

Michael, Could you try a wired connection to run the report-bug program?

On 23 Jan 2018 10:59 pm, "Jude DaShiell"  wrote:


Best to run the report-bug program if on your system and have an internet
connection open.
On Tue, 23 Jan 2018, michael caron couturier wrote:

Date: Tue, 23 Jan 2018 14:34:21

From: michael caron couturier 
To: debian-user 
Subject: Debian mate wifi
Resent-Date: Tue, 23 Jan 2018 19:51:09 + (UTC)
Resent-From: debian-user@lists.debian.org

How I file a bug ?




--






--

Re: Debian mate wifi

[michael caron couturier]

I'll try. Never used gmail in command line and since I'm more a sysadmin,
I'm mot confident for bugs reports, It's hard to say something to someone
when you dont know what he expect you to do and say in a technical langage
you dont know ... I dont even know for which package I file a bug since,
network-manager, nmtui, ...?

Le 25 janv. 2018 06:06, "Jeroen Mathon"  a
écrit :

> Well Jude,
>
> I think that will wonderfully when the problem he has is that he cannot
> establish an Wi-Fi connection.
>
> Michael, Could you try a wired connection to run the report-bug program?
>
> On 23 Jan 2018 10:59 pm, "Jude DaShiell"  wrote:
>
>> Best to run the report-bug program if on your system and have an internet
>> connection open.
>> On Tue, 23 Jan 2018, michael caron couturier wrote:
>>
>> Date: Tue, 23 Jan 2018 14:34:21
>>> From: michael caron couturier 
>>> To: debian-user 
>>> Subject: Debian mate wifi
>>> Resent-Date: Tue, 23 Jan 2018 19:51:09 + (UTC)
>>> Resent-From: debian-user@lists.debian.org
>>>
>>> How I file a bug ?
>>>
>>>
>>>
>> --
>>
>>

Re: Time of Removal of Installation media

[Ben Oliver]

On 18-01-25 12:00:38, john doe wrote:

On 1/25/2018 10:33 AM, Shehriyar Qureshi wrote:

Hi, I recently installed Debian Stretch and I was confused as if I
installed it correctly. At the end of the installation, I got to the point
where it said "Make sure to remove the installation media so you don't boot
into the installer". I removed the USB at that point and clicked continue
after which it did some small stuff and rebooted. Did I remove the USB at
the correct time or was I not supposed to remove it at that point? Thank
you :)



The step when to remove the installation media is meaningless with a 
usb key.
You could also keep the usb key plugged in and after reboot choose to 
boot on the device you installed Debian  on.


Note that it is not rong to unplug the usb key at that point.


In the past I have been known to try and time the unplugging with the 
exact time of the reboot.

Re: bash array

[Gokan Atmaca]

>> I have the user list and the password list. I shot them with BASH. I
>> want to give passwords to the usernames in these separate files in
>> order.
>>
>> File names:
>> Users.list
>> Passwords.list

Hello

I'm sorry for the late reply.
The problem is: I can pull the users one by one. I can not do the same
for passwords.

Do I need to use "Mapfile" for this?

example-mapfile:

passwords=(cat $pass.list)
mapfile -t pass < "$passwords"


example-script:
   -- user.list
  a
  b
  c

  -- pass.list
 xxx
 yyy
 zzz


script:

#!/bin/bash


pass=$(cat pass.list)

for i in user=$(cat user.list); do exampleporagram $i $pass; done








On Mon, Jan 15, 2018 at 5:39 PM, Greg Wooledge  wrote:
> On Sun, Jan 14, 2018 at 03:46:06PM +0300, Gokan Atmaca wrote:
>> I have the user list and the password list. I shot them with BASH. I
>> want to give passwords to the usernames in these separate files in
>> order.
>>
>> File names:
>> Users.list
>> Passwords.list
>>
>> In a loop, I have to not throw them into users of these passwords.
>
> We need to know the contents of these files, not their names.
>
>> I did this for it, but it did not work.
>>
>> #!bin/bash
>> passwords = $ (cat passwords.list)
>> for i in $ (cat passwordlist); do my program $ i $passwords; done
>
> There are many mistakes here, even without knowing what the files
> contain or what you are trying to do with them.
>
> First, your shebang is wrong.  It must be #!/bin/bash rather than
> #!bin/bash.
>
> Second, your assignment is wrong.  It must be var=value rather than
> var = value.  You CANNOT have spaces around the = sign.
>
> Third, your command substitution is wrong.  It must be $(command)
> rather than $ (command).  You CANNOT have a space between the $ and (.
>
> Fourth, if your passwords.list file contains spaces (which many
> good passwords WILL contain), your entire algorithm is wrong.  Your
> use of $(cat ...) splits the contents of the file on ALL whitespace,
> not just newlines.  A password with a single space in it will be
> treated as two words, and the loop will iterate once for each of
> those words.
>
> Also (let's call this bug number 4.5), any globbing characters in
> the password.list file (like ? or * or [...]) will break things with
> the algorithm you've chosen.
>
> And then there's your for loop ... ugh.  No.  It's just unbearable.
> This isn't valid code.  It's just random characters.
>
>> How do I make an Array? Or how can I solve it?
>
> Start from the beginning: WHAT IS IN EACH FILE?
>
> Suppose users.list looks like this:
>
> fred
> barney
> wilma
> betty
>
> And suppose passwords.list looks like this:
>
> 2^7djfnc5
> yabba dabba doo
> U(n  jv7s^&
> password
>
> Now suppose we are told "each line in users.list is one user, and each
> line in passwords.list is one password".
>
> Suppose we are told "there must be the same number of lines in both
> files".
>
> Suppose we are told "line N of users.list corresponds to line N of
> passwords.list".
>
> THEN you have enough information to actually write a program.
>
> What kind of array do you want?  Why do you even want an array?
>
> What is your program supposed to do with these users and passwords?
>
> Do you just need to create a single output file which combines them
> together?  In that case, you can read a line at a time from each
> file and never store them all in an array.  Just process sequentially.
>
> Do you need to create a lookup table that you will refer to again and
> again during some sort of GUI?  In that case, sure, an array might
> make sense.  But you still need to define what you're doing.  Are you
> planning to look up the password of a user GIVEN the user's name?
> Then use an associative array which is indexed by the user's name and
> contains the passwords.
>
> Do you plan to look up the user's name and password GIVEN an index
> number of some kind, perhaps chosen from a menu?  Then use two
> indexed arrays, one that maps the index number to the username, and
> the other that maps the index number to the password.
>
> Until we know what the input files contain, and what your program is
> supposed to do with them, nobody can tell you how to write your
> program.
>
> Start with these pages:
>
> http://mywiki.wooledge.org/BashGuide
> http://mywiki.wooledge.org/BashPitfalls
> http://mywiki.wooledge.org/BashFAQ/001
>
> Then, later, when you're ready:
>
> http://mywiki.wooledge.org/BashProgramming
>

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

On 25 January 2018 at 09:50, Michael Lange  wrote:

> Hi,
>
> On Thu, 25 Jan 2018 09:15:59 +
> Michael Fothergill  wrote:
>
> > >
> > >
> > > I have the same problem as in Gentoo.
> > >
> > > In order to install gcc 7.3 rc2 I think I would need to be sid.
> > >
> > >
> > > I don't think I want to be sid at present.
> > >
> >
> > ​But if I did want to be sid, would a source file like this suffice:
> >
> > ​
> > deb http://http.us.debian.org/debian/ unstable main contrib non-free
> > deb-src http://http.us.debian.org/debian/ unstable main contrib non-free
> >
> > ​or do I need more?
> >
> > ​If I become sid then I think I would just install the gcc version above
> > the one I have and  then reinstall
> > the 4.15.0 kernel and maybe I would have the full kernel
> > patch.
>
> hmm, I don't think installing the latest compiler does any good if you
> install a kernel package that was compiled with an older compiler version.
>
> And from a quick glance it looks like sid still has only gcc-7.2 .
> There is a gcc-8 package in experimental though; from again a quick
> glance at the dependencies it surely won't easily install on stretch but
> it might be worth a try if it installs on buster.
>

​I tried installing gcc 8 on buster.   It needs cpp8 which needs ​libmrpfr6

ie this

https://packages.debian.org/unstable/main/libmpfr6

which looks like its about being sid again.​


​I need to go to dependency rehab and sing the dem bones song again.

Suggestions on avoiding becoming sid/krankenhaus/unstable/12 step program
welcome.

Regards

MF


 ​


> Then I guess you would have to compile the kernel from source, which
> actually isn't too hard with make-kpkg (however I never tried to force
> make-kpkg to use a certain, non-system-default compiler, but that's surely
> possible).
>
> Regards
>
> Michael
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Every living thing wants to survive.
> -- Spock, "The Ultimate Computer", stardate 4731.3
>
>

Re: Debian mate wifi

[Jeroen Mathon]

Well Jude,

I think that will wonderfully when the problem he has is that he cannot
establish an Wi-Fi connection.

Michael, Could you try a wired connection to run the report-bug program?

On 23 Jan 2018 10:59 pm, "Jude DaShiell"  wrote:

> Best to run the report-bug program if on your system and have an internet
> connection open.
> On Tue, 23 Jan 2018, michael caron couturier wrote:
>
> Date: Tue, 23 Jan 2018 14:34:21
>> From: michael caron couturier 
>> To: debian-user 
>> Subject: Debian mate wifi
>> Resent-Date: Tue, 23 Jan 2018 19:51:09 + (UTC)
>> Resent-From: debian-user@lists.debian.org
>>
>> How I file a bug ?
>>
>>
>>
> --
>
>

Re: Time of Removal of Installation media

[john doe]

On 1/25/2018 10:33 AM, Shehriyar Qureshi wrote:

Hi, I recently installed Debian Stretch and I was confused as if I
installed it correctly. At the end of the installation, I got to the point
where it said "Make sure to remove the installation media so you don't boot
into the installer". I removed the USB at that point and clicked continue
after which it did some small stuff and rebooted. Did I remove the USB at
the correct time or was I not supposed to remove it at that point? Thank
you :)



The step when to remove the installation media is meaningless with a usb 
key.
You could also keep the usb key plugged in and after reboot choose to 
boot on the device you installed Debian  on.


Note that it is not rong to unplug the usb key at that point.

--
John Doe

Re: Time of Removal of Installation media

[Michael Milliman]

Yep. Anytime after the message displays is good. The system reboots when
you press the continue button and you want it to reboot to your hard disk
not the installation disk. You did right.

On Jan 25, 2018 3:59 AM,  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Jan 25, 2018 at 09:33:17AM +, Shehriyar Qureshi wrote:
> > Hi, I recently installed Debian Stretch and I was confused as if I
> > installed it correctly. At the end of the installation, I got to the
> point
> > where it said "Make sure to remove the installation media so you don't
> boot
> > into the installer". I removed the USB at that point and clicked continue
>
> That sounds about right, yes.
>
> > after which it did some small stuff and rebooted. Did I remove the USB at
> > the correct time or was I not supposed to remove it at that point? Thank
> > you :)
>
> I think anytime after this message is shown and before the computer starts
> booting after that is a good time.
>
> Cheers
> - -- tomás
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iEYEARECAAYFAlppqlsACgkQBcgs9XrR2ka7xwCfZ5VJTDtoVMjLTQTJDcteWpqD
> fb4An2zloBdZjdYmfht5pyMr1jLWqIBi
> =L16T
> -END PGP SIGNATURE-
>
>

Re: Time of Removal of Installation media

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, Jan 25, 2018 at 09:33:17AM +, Shehriyar Qureshi wrote:
> Hi, I recently installed Debian Stretch and I was confused as if I
> installed it correctly. At the end of the installation, I got to the point
> where it said "Make sure to remove the installation media so you don't boot
> into the installer". I removed the USB at that point and clicked continue

That sounds about right, yes.

> after which it did some small stuff and rebooted. Did I remove the USB at
> the correct time or was I not supposed to remove it at that point? Thank
> you :)

I think anytime after this message is shown and before the computer starts
booting after that is a good time.

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

iEYEARECAAYFAlppqlsACgkQBcgs9XrR2ka7xwCfZ5VJTDtoVMjLTQTJDcteWpqD
fb4An2zloBdZjdYmfht5pyMr1jLWqIBi
=L16T
-END PGP SIGNATURE-

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Lange]

Hi,

On Thu, 25 Jan 2018 09:15:59 +
Michael Fothergill  wrote:

> >
> >
> > I have the same problem as in Gentoo.
> >
> > In order to install gcc 7.3 rc2 I think I would need to be sid.
> >
> >
> > I don't think I want to be sid at present.
> >
> 
> ​But if I did want to be sid, would a source file like this suffice:
> 
> ​
> deb http://http.us.debian.org/debian/ unstable main contrib non-free
> deb-src http://http.us.debian.org/debian/ unstable main contrib non-free
> 
> ​or do I need more?
> 
> ​If I become sid then I think I would just install the gcc version above
> the one I have and  then reinstall
> the 4.15.0 kernel and maybe I would have the full kernel
> patch.

hmm, I don't think installing the latest compiler does any good if you
install a kernel package that was compiled with an older compiler version.

And from a quick glance it looks like sid still has only gcc-7.2 .
There is a gcc-8 package in experimental though; from again a quick
glance at the dependencies it surely won't easily install on stretch but
it might be worth a try if it installs on buster.
Then I guess you would have to compile the kernel from source, which
actually isn't too hard with make-kpkg (however I never tried to force
make-kpkg to use a certain, non-system-default compiler, but that's surely
possible).

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Every living thing wants to survive.
-- Spock, "The Ultimate Computer", stardate 4731.3

Time of Removal of Installation media

[Shehriyar Qureshi]

Hi, I recently installed Debian Stretch and I was confused as if I
installed it correctly. At the end of the installation, I got to the point
where it said "Make sure to remove the installation media so you don't boot
into the installer". I removed the USB at that point and clicked continue
after which it did some small stuff and rebooted. Did I remove the USB at
the correct time or was I not supposed to remove it at that point? Thank
you :)

Re: Question on CVE-2017-5754 on Debian 8.9

[Michael Fothergill]

>
>
> I have the same problem as in Gentoo.
>
> In order to install gcc 7.3 rc2 I think I would need to be sid.
>
>
> I don't think I want to be sid at present.
>

​But if I did want to be sid, would a source file like this suffice:

​
deb http://http.us.debian.org/debian/ unstable main contrib non-free
deb-src http://http.us.debian.org/debian/ unstable main contrib non-free

​or do I need more?

​If I become sid then I think I would just install the gcc version above
the one I have and  then reinstall
the 4.15.0 kernel and maybe I would have the full kernel patch.

Comments appreciated,




>
> Cheers
>
> MF
>
>
>
> ​
>
>
>
>>
>> Regards
>>
>> Michael
>>
>>
>> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>>
>> War isn't a good life, but it's life.
>> -- Kirk, "A Private Little War", stardate 4211.8
>>
>>
>

Re: Iptables at boot

[Alessandro Vesely]

On Sun 21/Jan/2018 20:53:43 +0100 Ben Caradoc-Davies wrote:
> On 21/01/18 16:05, Mark Fletcher wrote:
>> To get you started [addressing the OP], here is the service file I use:
> 
> Mine is slightly different and has the commands inline:
> 
> 
> $ cat /etc/iptables/iptables.service
> [Unit]
> Description=iptables rules
> After=network.target

Shouldn't that be /network-pre.target/?  I'm not familiar with systemd (I use
sysvinit) but I read "It's primary purpose is for usage with firewall services
that want to establish a firewall before any network interface is up" in:
https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/

Best
Ale