Re: [DNG] rc.local removed from Debian 9, rly?
On 20/11/17 11:30, Jaromil wrote: 1- it [ rc.local ] is not created by default It exists on my stretch systems. As Olaf Meeuwissen said it is created by initscripts.postinst: # # Create /etc/rc.local on first time install and when upgrading from # versions before "2.86.ds1-16" # if dpkg --compare-versions "$PREV_VER" lt "2.86.ds1-16" then if [ ! -e /etc/rc.local ]; then cat << EOF > /etc/rc.local # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. exit 0 EOF # make sure it's enabled by default. chmod 755 /etc/rc.local fi fi 2- it is not executed in Debian Stretch (9) even if existing I, as you might have guessed, use systemd, so rc.local is started by rc-local.service: ● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor preset: Drop-In: /lib/systemd/system/rc-local.service.d └─debian.conf Active: active (exited) since Mon 2017-10-30 11:03:59 CET; 3 weeks 1 days ago Process: 655 ExecStart=/etc/rc.local start (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) CGroup: /system.slice/rc-local.service The service rc-local.service is: # This unit gets pulled automatically into multi-user.target by # systemd-rc-local-generator if /etc/rc.local is executable. [Unit] Description=/etc/rc.local Compatibility ConditionFileIsExecutable=/etc/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.local start TimeoutSec=0 RemainAfterExit=yes GuessMainPID=no # This unit gets pulled automatically into multi-user.target by # systemd-rc-local-generator if /etc/rc.local is executable. [Unit] Description=/etc/rc.local Compatibility ConditionFileIsExecutable=/etc/rc.local After=network.target [Service] Type=forking ExecStart=/etc/rc.local start TimeoutSec=0 RemainAfterExit=yes GuessMainPID=no The source of the generator, systemd-rc-local-generator, is at https://github.com/systemd/systemd/blob/master/src/rc-local-generator/rc-local-generator.c please correct me if I'm wrong. That would help. I think you're wrong. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] hotplug of SD cards fails on Jessie
Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017, John Hughes wrote: >On 20/11/17 11:30, Jaromil wrote: > > 1- it [ rc.local ] is not created by default > >It exists on my stretch systems. I always and only mean Debian 9. So I will reformulate: 1- /etc/rc.local does not exist by default on Debian 9. this is not a major problem since most scripts won't fail. > 2- it is not executed in Debian Stretch (9) even if existing > >I, as you might have guessed, use systemd, so rc.local is started by >rc-local.service: is it the case that one must run two systemctl commands in order for rc.local to be processed, or will rc.local just be found and executed? I know about rc-local.service, my point is not about that being available. I believe both points 1 and 2 are regressions. 2 is a breaking regression in most setups. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] hotplug of SD cards fails on Jessie
Hi Didier, On 11/21/2017 12:59 PM, Didier Kryn wrote: Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier I'm using vdev in combination with pmount on jessie and both work fine for me; however, i've never tested them in a SD card. But, if the nodes are created in /dev, they should work. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] hotplug of SD cards fails on Jessie
Hi again Didier, On 11/20/2017 02:23 PM, aitor_czr wrote: Hi Didier, On 11/21/2017 12:59 PM, Didier Kryn wrote: Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier I'm using vdev in combination with pmount on jessie and both work fine for me; however, i've never tested them in a SD card. But, if the nodes are created in /dev, they should work. Cheers, Aitor. I misunderstood your question, i thought you were trying to mount an USB device on a system *installed* in a SD card. Forget what i said so far :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Error when updating from jessie to ascii 32bit
The problem persists I come from: debian whezy to debian jessie debian jessie to devuan jessie devuan jessie to devuan ascii * root@(none):/mnt/datos/sistemas/linux/devuan# sh rdascii.sh = Actualizando los repositorios DEVUAN 'merged'; main/debian-installer, main, contrib, non-free = Mirroring to /mnt/datos/sistemas/linux/devuan/ascii/ascii from http://packages.devuan.org/merged// Arches: i386,amd64 Dists: ascii Sections: main/debian-installer,main,contrib,non-free Pdiff mode: none Will clean up after mirroring. Attempting to get lock ... Not able to use rsync to update remote trace files ... Getting meta files ... [ 0%] Getting: dists/ascii/Release... #** GET http://packages.devuan.org/merged//dists/ascii/Release ==> 200 OK (2s) ok [ 0%] Getting: dists/ascii/InRelease... #** GET http://packages.devuan.org/merged//dists/ascii/InRelease ==> 200 OK (1s) ok [ 0%] Getting: dists/ascii/Release.gpg... #** GET http://packages.devuan.org/merged//dists/ascii/Release.gpg ==> 200 OK (1s) ok [GNUPG:] ERROR add_keyblock_resource 33554433 [GNUPG:] NEWSIG [GNUPG:] ERROR keydb_search 33554445 [GNUPG:] ERRSIG 94532124541922FB 1 8 00 1511247849 9 [GNUPG:] NO_PUBKEY 94532124541922FB gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/root/.gnupg/trustedkeys.kbx': General error gpgv: Firmado el mar 21 nov 2017 02:04:09 CST gpgv:usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/Release.gpg signature does not verify. [GNUPG:] ERROR add_keyblock_resource 33554433 [GNUPG:] NEWSIG [GNUPG:] ERROR keydb_search 33554445 [GNUPG:] ERRSIG 94532124541922FB 1 8 01 1511247843 9 [GNUPG:] NO_PUBKEY 94532124541922FB gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/root/.gnupg/trustedkeys.kbx': General error gpgv: Firmado el mar 21 nov 2017 02:04:03 CST gpgv:usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/InRelease signature does not verify. [ 0%] Getting: dists/ascii/main/debian-installer/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Packages.xz ==> 200 OK (2s) ok [ 0%] Getting: dists/ascii/main/debian-installer/binary-i386/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Packages.gz ==> 200 OK ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-i386/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Release ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Packages.xz ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Packages.gz ==> 200 OK ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Release ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Packages.xz ==> 200 OK (336s) ok [ 7%] Getting: dists/ascii/main/binary-i386/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Packages.gz ==> 200 OK (502s) ok [ 50%] Getting: dists/ascii/main/binary-i386/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Release ==> 200 OK ok [ 50%] Getting: dists/ascii/main/binary-amd64/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Packages.xz ==> 200 OK (354s) ok [ 56%] Getting: dists/ascii/main/binary-amd64/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Packages.gz ==> 200 OK (415s) ok [ 99%] Getting: dists/ascii/main/binary-amd64/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Release ==> 200 OK (1s) ok [ 99%] Getting: dists/ascii/contrib/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/contrib/binary-i386/Packages.xz ==> 200 OK (1s) ok [ 99%] Getting: dists/ascii/contrib/binary-i386/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/contrib/binary-i386/Packages.gz ==> 200 OK (2s) ok [ 99%] Getting: dists/ascii/contrib/binary-i386/Release... #** GET http://packages.devuan.org/merged//dists/ascii/contrib/binary-i386/Release ==> 200 OK (1s) ok [ 99%] Getting: dists/ascii/contrib/binar
Re: [DNG] rc.local removed from Debian 9, rly?
Hi Jaromil, list,
Jaromil writes:
> dear Olaf,
>
> On Mon, 20 Nov 2017, Olaf Meeuwissen wrote:
>
>> Crying wolf like this time and again is not doing Devuan any good.
>
> No, I am the wolf.
I do not mean this personally. I just recalled the mail that set off
the redis discussion and this one and noticed one thing in common: a
lack of backing up claims without proper investigation. If anyone wants
to make a claim about anyone else "sabotaging" non-systemd systems, just
show some cold, hard facts to back it up before pointing fingers one way
or another.
# FTR, I've been using Debian since 1998 and switched all my machines to
# Devuan in 2017 because, eh, I think systemd is getting in *my* way.
>> FWIW, I just modified the /etc/rc.local on two of my Devuan ASCII
>> machines to fix up ownership on an ext4 mount and that worked just
>> fine. But then again, initscripts *is* devuanized ;-)
>>
>> Hope this helps,
>
> It doesn't: you are bringing confusion.
Actually, with respect to the quoted paragraph, you're probably right.
I should have left that out. It detracts from the rest of what I wrote.
> You have checked Devuan. I'm talking about Debian 9 "Stretch"
In the same mail you replied to, I also wrote:
>> Just a simple `grep -rl rc.local /var/lib/dpkg/info` is all that it took
>> me to find this out on my Devuan Jessie. To cross check, I went over to
>> package.debian.org to have a look at their initscripts package. stretch
>> has 2.88dsf-59.9, buster and sid have 2.88dsf-50.10. Pulled the debian/
>> directory tarball and checked initscripts.postinst. Nothing changed and
>> rc.local will still be created.
So, yes, I *did* check Stretch and Buster and Sid. To make really sure,
I just eyeballed the initscripts.postinst files again and they *create*
an /etc/rc.local file 'on first install and when upgrading from versions
before "2.86.ds1-16"'. To make absolutely really sure, I checked the
Debian Docker images for Stretch and Buster. Neither has an initscripts
package installed and /etc/rc.local is missing. I installed initscripts
on both and in both cases an /etc/rc.local file was created.
# FTR, both the Debian Stretch and Buster Docker images come *without*
# systemd installed. This is due to the nature of containers as they
# are supposed to run just a task-specific, dedicated program as their
# PID1. For the Debian containers that is /bin/bash, BTW.
> Here the rumors I've heard from bitcoin core development: a CI script
> was broken for three reasons, of which the mandatory activation of
> rc.local via systemctl is just one.
> https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-debian.md
>
> also "rumors" of "deprecation" are all around the web with a search:
> https://stackoverflow.com/questions/44797694/where-is-rc-local-in-debian-9-debian-stretch
> http://www.itechlounge.net/2017/10/linux-how-to-add-rc-local-in-debian-9/
I cannot say I have really *read* these but I have at least skimmed them
and the problem seems to be that they assume /etc/rc.local is provided
by some package that is installed by default. Until Jessie, initscripts
was Priority: required so it was installed by default. As of Stretch,
it has become Priority: optional and will not be installed by default.
A quick check of the packages that would pull it in (as per massaged
`apt-cache rdepends`) on Stretch gives:
$ apt-cache rdepends initscripts | sed -n '/^ /p' | while read pkg; do \
echo $pkg ; apt-cache depends $pkg | grep initscripts; done \
| sed -n '/^[^ ]/{ H; N; /Depends/P }'
sysvinit-core
debian-edu-config
console-setup-linux
console-setup-freebsd
console-log
but note that there are a fair number of packages that declare a Breaks:
or Conflicts: which may warrant further investigation.
As for Devuan, it flags sysvinit-core as Priority: important and
therefore the initscripts package will be pulled in.
> there is no official mention on Debian about a "deprecation", which
> I'd consider vandalism. I am very happy of that and I'm asking if its
> real or not that is "deprecated" as others write and if anyone knows
> more about Debian's long term intention with rc.local, since its
> function has already changed:
>
> 1- it is not created by default
Please note the that the /etc/rc.local that is created by default is no
more than
#!/bin/sh -e
exit 0
once you remove the documentation. Anyone that knows about and needs an
rc.local can whip up something more meaningful in, what?, 10 seconds.
> 2- it is not executed in Debian Stretch (9) even if existing
Now, here is something I am not sure about but the content of the pages
in your last two links seem to suggests that it is *systemd* that no
longer honours a /etc/rc.local by default and requires you to explicitly
enable it. If that's the case, I would not call that Debian vandalism
but systemd vandalism and every distribution that defaults to systemd
will be affected alike, not just Debia
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 14:21, Jaromil wrote: On Tue, 21 Nov 2017, John Hughes wrote: On 20/11/17 11:30, Jaromil wrote: 1- it [ rc.local ] is not created by default It exists on my stretch systems. I always and only mean Debian 9. So I will reformulate: 1- /etc/rc.local does not exist by default on Debian 9. Debian Stretch is Debian 9. /etc/rc.local exists by default on Debian 9 this is not a major problem since most scripts won't fail. 2- it is not executed in Debian Stretch (9) even if existing I, as you might have guessed, use systemd, so rc.local is started by rc-local.service: is it the case that one must run two systemctl commands in order for rc.local to be processed, or will rc.local just be found and executed? No, no systemctl commands are needed, systemd-rc-local-generator will enable rc-local.service if /etc/rc.local is executable, which it is by default on Debian Stretch (AKA Debian 9). I know about rc-local.service, my point is not about that being available. I believe both points 1 and 2 are regressions. 2 is a breaking regression in most setups. What regressions? https://upload.wikimedia.org/score/i/x/ixrxdpiezwcsj11b0mb4buzmt7p4025/ixrxdpie.ogg ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017 14:48:49 +0100 John Hughes wrote: > > No, no systemctl commands are needed, systemd-rc-local-generator will > enable rc-local.service if /etc/rc.local is executable, which it is > by default on Debian Stretch (AKA Debian 9). > Yes, but will 'systemd-rc-local-generator' exist on a Devuan OS where no systemd components are loaded by default ?? Rowland ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 11:58, Olaf Meeuwissen wrote:
A quick check of the packages that would pull [ initscripts ] in (as per
massaged
`apt-cache rdepends`) on Stretch gives:
$ apt-cache rdepends initscripts | sed -n '/^ /p' | while read pkg; do \
echo $pkg ; apt-cache depends $pkg | grep initscripts; done \
| sed -n '/^[^ ]/{ H; N; /Depends/P }'
sysvinit-core
Aha. My systems have mostly been upgraded from Jessie -- I guess that's
why they have initscripts installed, it seems nothing else would force
them to have it.
So, it seems to me that the actual state of /etc/rc.local in Debian 9 is:
If you have the initscripts package installed then /etc/rc.local will be
created for you (if it doesn't exist) and it will be run (if you are
using sysvinit or systemd at least).
If you don't install initscripts (i.e. if you're using systemd and you
don't explicitly install it or something that depends on it) then
/etc/rc.local will not be created for you, but will be automatically run
if it does exist (and is executable).
I'll be installing some new Stretch systems later this week, if I find
anything different I'll get back to the list.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 14:54, Rowland Penny wrote: On Tue, 21 Nov 2017 14:48:49 +0100 John Hughes wrote: No, no systemctl commands are needed, systemd-rc-local-generator will enable rc-local.service if /etc/rc.local is executable, which it is by default on Debian Stretch (AKA Debian 9). Yes, but will 'systemd-rc-local-generator' exist on a Devuan OS where no systemd components are loaded by default ?? Obviously not. But what does that have to do with the price of eggs in China? If you're using sysvinit instead of systemd then, on a Debian 9 system /etc/init.d/rc.local will run /etc/rc.local. (How this works for other init systems is left as an exercise for the implementer). ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
dear John and Olaf, Thanks for proving me wrong, this is exactly what I hoped for. In fact my mail was perhaps badly worded and contained already a rant, but was really about asking this list for a critical analysis. For 2 main reasons: 1) there are very knowledgeable people (like you both) that often are capable of checking better than me 2) I am a lazy wolf and prefer writing a mail than checking myself. I also note as you point out that this behavior may be counterproductive for the public perception of this project: a way or another I also represent Devuan and maybe I should hold off this attitude and post only things that I am sure of. This is difficult for me, since I conceive spaces for debate as this and other mailinglists as spaces where to share doubts, fears, needs and dreams even more than findings and announcements, for which an article or a twit @DevuanOrg may be better. anyway, point taken. I know well that I'm wrong sometimes, just like now. So now I agree that considering this and the other discussion about redis, there is no real "vandalism" happening in Debian. About redis was just a maintainer fumbling around broken scripts through releases, while the rc.local case its just that people don't care about the regressions introduced by systemd. Then I believe we also agree that rc.local is a serious regressions? because it now needs to be activated via two new systemctl commands, forcing millions of people around the world to go lookup those commands instead of keeping the default. I believe defaults should be kept intact. In the worst case there should be clear documentation of their change. In Debian right now I don't even see a debate, only rumors of "deprecation" in other avenues. Whatever that may mean for Debian and its future. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, Nov 21, 2017 at 03:07:07PM +0100, John Hughes wrote: [cut] > > If you have the initscripts package installed then /etc/rc.local will be > created for you (if it doesn't exist) and it will be run (if you are using > sysvinit or systemd at least). > > If you don't install initscripts (i.e. if you're using systemd and you don't > explicitly install it or something that depends on it) then /etc/rc.local > will not be created for you, but will be automatically run if it does exist > (and is executable). As Olaf explained, the problem seems to originate in the fact that the initscripts package is not any more marked as important. Hence, if you don't have it, you won't get it by default. I personally agree on the fact that this is somehow a regression. Also, it is not clear to me *when* the automagic systemd tool that should create the systemd service (if rc.local is executable) is run. *If* it's only run during systemd's postinst, this means that no rc.local is created or honoured by default by systemd (unless it already exists in the system when the systemd package is installed), but we need to double-check it. What matters is that we need to retain initscripts as "important". > > I'll be installing some new Stretch systems later this week, if I find > anything different I'll get back to the list. Great. Thanks. HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 15:20, Jaromil wrote: dear John and Olaf, Thanks for proving me wrong, this is exactly what I hoped for. I'm not actually sure you've been "proved wrong" -- in the case of a Debian 9 system without the initscripts package installed (i.e. a fresh install with systemd as pid 1 for example) then /etc/rc.local will not be automatically created. However if it *is* created then systemd will run it. I also note as you point out that this behavior may be counterproductive for the public perception of this project: a way or another I also represent Devuan and maybe I should hold off this attitude and post only things that I am sure of. This is difficult for me, since I conceive spaces for debate as this and other mailinglists as spaces where to share doubts, fears, needs and dreams even more than findings and announcements, for which an article or a twit @DevuanOrg may be better. There can be nothing wrong in admitting ignorance or searching for information. However making strong, even aggressive or insulting, statements based on partial knowledge seems unlikely to advance the cause of Peace on Earth. :-) while the rc.local case its just that people don't care about the regressions introduced by systemd. Except that systemd introduces no regressions with rc.local. In fact it's systemd that includes the compatibility code to make sure that /etc/rc.local is run if it exists. This comes from the systemd team, not from Debian: rc-local-generator.c Copyright 2010 Lennart Poettering Copyright 2011 Michal Schmidt Then I believe we also agree that rc.local is a serious regressions? What regression? because it now needs to be activated via two new systemctl commands, No it doesn't. The systemd-rc-local-generator is run by systemd, users don't need to worry about it. https://www.freedesktop.org/software/systemd/man/systemd.generator.html In Debian right now I don't even see a debate, A debate about what? Whether rc.local should be run? Whoever said it shouldn't be? Or that it won't be in the future? only rumors of "deprecation" in other avenues. Whatever that may mean for Debian and its future. Rumors. From some of the least reliable tech sites on the web (stackoverflow! Ack Pfft!). Did you see any of these "rumors" on an actual Debian site or mailing list? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 15:53, KatolaZ wrote: Also, it is not clear to me *when* the automagic systemd tool that should create the systemd service (if rc.local is executable) is run. man systemd.generator ... Generators are small binaries that live in /usr/lib/systemd/user-generators/ and other directories listed above. systemd(1) will execute those binaries very early at bootup and at configuration reload time — before unit files are loaded. ... What matters is that we need to retain initscripts as "important". If you have sysvinit then it's a damn site more than "important", it's a dependency for sysvinit-core. -- John Hughes, CalvaEDI S.A.S. -- An Esker Company +33 1 4313 3131 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, Nov 21, 2017 at 04:05:47PM +0100, John Hughes wrote: > On 21/11/17 15:53, KatolaZ wrote: > > > >Also, it is not clear to me *when* the automagic systemd tool that > >should create the systemd service (if rc.local is executable) is > >run. > > man systemd.generator > ... > Generators are small binaries that live in > /usr/lib/systemd/user-generators/ and other directories listed >above. > systemd(1) will execute those binaries very early at bootup and >at configuration reload time — before unit files are loaded. > ... > Thanks for clarifying that. > > >What matters is that we need to retain initscripts as "important". > > If you have sysvinit then it's a damn site more than "important", it's a > dependency for sysvinit-core. > I was not referring only to sysvinit. Since the expectation for any "pluggable" init system is to not break anything that works (at least in Devuan), this point must be taken into account by any candidate alternative init system (at least in Devuan). HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017, John Hughes wrote: > > Then I believe we also agree that rc.local is a serious regressions? > > What regression? the fact that besides creating it and making it executable, one must also activate the service unit. > > In Debian right now I don't even see a debate, > > A debate about what? Whether rc.local should be run? Whoever said it > shouldn't be? Or that it won't be in the future? I am afraid that is not enough to create /etc/rc.local to have it ran by default. just afraid, not checked enough, hence asking > Rumors. From some of the least reliable tech sites on the web > (stackoverflow! Ack Pfft!). Did you see any of these "rumors" on > an actual Debian site or mailing list? no, the "rumors" I refer to are, as I said, coming from an upstream project whose CI has broken. I'm glad we also have an important take away for Devuan as Katolaz points out: to mark the initscripts package as important. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] hotplug of SD cards fails on Jessie
Le 20/11/2017 à 14:37, aitor_czr a écrit : Hi again Didier, On 11/20/2017 02:23 PM, aitor_czr wrote: Hi Didier, On 11/21/2017 12:59 PM, Didier Kryn wrote: Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier I'm using vdev in combination with pmount on jessie and both work fine for me; however, i've never tested them in a SD card. But, if the nodes are created in /dev, they should work. Cheers, Aitor. I misunderstood your question, i thought you were trying to mount an USB device on a system *installed* in a SD card. Forget what i said so far :) Aitor. I mean: when I insert an USB memory key, an associated icon pops up on my desktop, but when I insert an SD card, nothing shows up. The system is on a disk. I don't know how xfce is informed of the presence of a new device. I'm afraid it's by dbus. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 16:19, Jaromil wrote: On Tue, 21 Nov 2017, John Hughes wrote: Then I believe we also agree that rc.local is a serious regressions? What regression? the fact that besides creating it and making it executable, one must also activate the service unit. No, you don't. systemd runs systemd-rc-local-generator at boot time and after any systemd configuration change. You don't have to activate the unit, that's done for you. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017, John Hughes wrote: > On 21/11/17 16:19, Jaromil wrote: > > On Tue, 21 Nov 2017, John Hughes wrote: > > > > > > Then I believe we also agree that rc.local is a serious regressions? > > > What regression? > > the fact that besides creating it and making it executable, one must > > also activate the service unit. > > No, you don't. systemd runs systemd-rc-local-generator at boot time and > after any systemd configuration change. You don't have to activate the > unit, that's done for you. OK, then I'm wrong. I'm very happy of that too! thanks. The new issue about initscripts is orthogonal to my arguments. The issue on bitcoin-core I guess we have only because of other deprecations. Again, that's really what this discussion list is very useful for. No representative of Devuan should go making public statements of such importance without grinding them here first. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 16:19, Jaromil wrote: no, the "rumors" I refer to are, as I said, coming from an upstream project whose CI has broken. You said: Here the rumors I've heard from bitcoin core development: a CI script was broken for three reasons, of which the mandatory activation of rc.local via systemctl is just one https://github.com/bitcoin-core/docs/blob/master/gitian-building/gitian-building-setup-gitian-debian.md I followed your link to "gitian-building-setup-gitian-debian.md" Which says that you need to create the rc.local and reboot. I see no mention of systemctl. Am I looking in the wrong place? I'm glad we also have an important take away for Devuan as Katolaz points out: to mark the initscripts package as important. That'll ensure that rc.local exists and is executable, but not that it's run -- that'll depend on the init system you're using. If it's systemd or sysvinit it'll work, for others, maybe, maybe not. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017, John Hughes wrote: >I followed your link to "gitian-building-setup-gitian-debian.md" > >Which says that you need to create the rc.local and reboot. I see no >mention of systemctl. Am I looking in the wrong place? nono, as I wrote: that script doesn't works anymore, if ran on a freshly debootstrapped version of Debian 9. It seemed that rc.local wasn't executed anymore. But there is some confusion, since both brctl and ifconfig are legitimately deprecated. Assuming you have done better checking, then the failure may be caused by them bailing out. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 17:53, Jaromil wrote:
On Tue, 21 Nov 2017, John Hughes wrote:
I followed your link to "gitian-building-setup-gitian-debian.md"
Which says that you need to create the rc.local and reboot. I see no
mention of systemctl. Am I looking in the wrong place?
nono, as I wrote: that script doesn't works anymore, if ran on a
freshly debootstrapped version of Debian 9. It seemed that rc.local
wasn't executed anymore. But there is some confusion, since both brctl
and ifconfig are legitimately deprecated. Assuming you have done
better checking, then the failure may be caused by them bailing out.
Ok, I'll try a test:
root@cufic:~# aptitude purge initscripts
The following packages will be REMOVED:
initscripts{p}
0 packages upgraded, 0 newly installed, 1 to remove and 7 not upgraded.
Need to get 0 B of archives. After unpacking 213 kB will be freed.
Do you want to continue? [Y/n/?]
(Reading database ... 188141 files and directories currently installed.)
Removing initscripts (2.88dsf-59.9) ...
Processing triggers for systemd (232-25+deb9u1) ...
Processing triggers for man-db (2.7.6.1-2) ...
(Reading database ... 188123 files and directories currently installed.)
Purging configuration files for initscripts (2.88dsf-59.9) ...
dpkg: warning: while removing initscripts, directory '/var/lib/urandom' not
empty so not removed
Processing triggers for systemd (232-25+deb9u1) ...
root@cufic:~# ls -l /etc/rc.local
-rwxr-xr-x 1 root root 306 Jan 31 2017 /etc/rc.local
root@cufic:~# rm /etc/rc.local
root@cufic:~# systemctl reboot
...
... it boots up ...
john@cufic:~$ systemctl status rc-local.service
● rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor
preset:
Drop-In: /lib/systemd/system/rc-local.service.d
└─debian.conf
Active: inactive (dead)
Seems it wasn't run 'cos rc.local doesn't exist.
Make a rc.local:
root@cufic:~# cat > /etc/rc.local
#! /bin/sh
# Test rc.local
echo Hello from rc.local
exit 0
^D
root@cufic:~# chmod a=rx /etc/rc.local
root@cufic:~# ls -l /etc/rc.local
-r-xr-xr-x 1 root root 62 Nov 21 18:08 /etc/rc.local
root@cufic:~# systemctl reboot
...
... it boots up.
root@cufic:~# systemctl status rc-local.service
● rc-local.service - /etc/rc.local Compatibility
Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor
preset:
Drop-In: /lib/systemd/system/rc-local.service.d
└─debian.conf
Active: active (exited) since Tue 2017-11-21 18:10:23 CET; 1min 9s ago
Process: 595 ExecStart=/etc/rc.local start (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
CGroup: /system.slice/rc-local.service
Nov 21 18:10:23 cufic systemd[1]: Starting /etc/rc.local Compatibility...
Nov 21 18:10:23 cufic rc.local[595]: Hello from rc.local
Nov 21 18:10:23 cufic systemd[1]: Started /etc/rc.local Compatibility.
So, it looks to me if /etc/rc.local exists and is executable then
systemd runs it as I thought.
If it didn't work for the bitcoin guys then the problem is somewhere else.
(Damn but the systemd journal is great :-))
Come to think about it, if the problem was that their rc.local was
failing somewhere then they should be able to see that in the output of
systemctl or journalctl.
Assuming they're using systemd, of course. :-)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Error when updating from jessie to ascii 32bit
When I check the file does not exist: /root/.gnupg/trustedkeys.kbx But I do not know when and how it is created Bets Regards -- Ismael Devuan User : http://distrowatch.com/table.php?distribution=devuan - Original Message - From: "Ismael L. Donis Garcia" To: Sent: Tuesday, November 21, 2017 8:10 AM Subject: Re: [DNG] Error when updating from jessie to ascii 32bit The problem persists I come from: debian whezy to debian jessie debian jessie to devuan jessie devuan jessie to devuan ascii * root@(none):/mnt/datos/sistemas/linux/devuan# sh rdascii.sh = Actualizando los repositorios DEVUAN 'merged'; main/debian-installer, main, contrib, non-free = Mirroring to /mnt/datos/sistemas/linux/devuan/ascii/ascii from http://packages.devuan.org/merged// Arches: i386,amd64 Dists: ascii Sections: main/debian-installer,main,contrib,non-free Pdiff mode: none Will clean up after mirroring. Attempting to get lock ... Not able to use rsync to update remote trace files ... Getting meta files ... [ 0%] Getting: dists/ascii/Release... #** GET http://packages.devuan.org/merged//dists/ascii/Release ==> 200 OK (2s) ok [ 0%] Getting: dists/ascii/InRelease... #** GET http://packages.devuan.org/merged//dists/ascii/InRelease ==> 200 OK (1s) ok [ 0%] Getting: dists/ascii/Release.gpg... #** GET http://packages.devuan.org/merged//dists/ascii/Release.gpg ==> 200 OK (1s) ok [GNUPG:] ERROR add_keyblock_resource 33554433 [GNUPG:] NEWSIG [GNUPG:] ERROR keydb_search 33554445 [GNUPG:] ERRSIG 94532124541922FB 1 8 00 1511247849 9 [GNUPG:] NO_PUBKEY 94532124541922FB gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/root/.gnupg/trustedkeys.kbx': General error gpgv: Firmado el mar 21 nov 2017 02:04:09 CST gpgv:usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/Release.gpg signature does not verify. [GNUPG:] ERROR add_keyblock_resource 33554433 [GNUPG:] NEWSIG [GNUPG:] ERROR keydb_search 33554445 [GNUPG:] ERRSIG 94532124541922FB 1 8 01 1511247843 9 [GNUPG:] NO_PUBKEY 94532124541922FB gpgv: unknown type of key resource 'trustedkeys.kbx' gpgv: keyblock resource '/root/.gnupg/trustedkeys.kbx': General error gpgv: Firmado el mar 21 nov 2017 02:04:03 CST gpgv:usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/InRelease signature does not verify. [ 0%] Getting: dists/ascii/main/debian-installer/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Packages.xz ==> 200 OK (2s) ok [ 0%] Getting: dists/ascii/main/debian-installer/binary-i386/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Packages.gz ==> 200 OK ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-i386/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-i386/Release ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Packages.xz ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Packages.gz ==> 200 OK ok [ 1%] Getting: dists/ascii/main/debian-installer/binary-amd64/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/debian-installer/binary-amd64/Release ==> 200 OK (1s) ok [ 1%] Getting: dists/ascii/main/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Packages.xz ==> 200 OK (336s) ok [ 7%] Getting: dists/ascii/main/binary-i386/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Packages.gz ==> 200 OK (502s) ok [ 50%] Getting: dists/ascii/main/binary-i386/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-i386/Release ==> 200 OK ok [ 50%] Getting: dists/ascii/main/binary-amd64/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Packages.xz ==> 200 OK (354s) ok [ 56%] Getting: dists/ascii/main/binary-amd64/Packages.gz... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Packages.gz ==> 200 OK (415s) ok [ 99%] Getting: dists/ascii/main/binary-amd64/Release... #** GET http://packages.devuan.org/merged//dists/ascii/main/binary-amd64/Release ==> 200 OK (1s) ok [ 99%] Getting: dists/ascii/contrib/binary-i386/Packages.xz... #** GET http://packages.devuan.org/merged//dists/ascii/contrib/binary-i386/Packages.xz ==> 200 OK (1s) ok
Re: [DNG] hotplug of SD cards fails on Jessie
Hi Didier, On 11/21/2017 04:37 PM, Didier Kryn wrote: Le 20/11/2017 à 14:37, aitor_czr a écrit : Hi again Didier, On 11/20/2017 02:23 PM, aitor_czr wrote: Hi Didier, On 11/21/2017 12:59 PM, Didier Kryn wrote: Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier I'm using vdev in combination with pmount on jessie and both work fine for me; however, i've never tested them in a SD card. But, if the nodes are created in /dev, they should work. Cheers, Aitor. I misunderstood your question, i thought you were trying to mount an USB device on a system *installed* in a SD card. Forget what i said so far :) Aitor. I mean: when I insert an USB memory key, an associated icon pops up on my desktop, but when I insert an SD card, nothing shows up. The system is on a disk. I don't know how xfce is informed of the presence of a new device. I'm afraid it's by dbus. Didier If you want to avoid dbus, then i recommend you to use pmount instead of udisks/udisks2. I have had a system detecting physical devices without dbus (using, as i said, vdev and pmount). RecentIy i uploaded an image of gnuinos including both of them. Dbus also has been removed from the dependencies of the network manager (simple-netaid instead of wicd) but dbus is still present in the system due to gvfs :( Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Error when updating from jessie to ascii 32bit
Hi Ismael, On 11/21/2017 06:18 PM, Ismael L. Donis Garcia wrote: gpgv: Firmado el mar 21 nov 2017 02:04:03 CST gpgv: usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/InRelease signature does not verify. Parsing Packages and Sources files ... Get Translation files ... Get DEP-11 metadata files ... Files to download: 0 B Downloaded 221 kiB in 24s at 9.21 kiB/s. Everything OK. Moving meta files ... Not able to use rsync to update remote trace files ... Cleanup mirror. All done. root@(none):/mnt/datos/sistemas/linux/devuan# One detail: you have set to *none* your hostname. Why? Have a look at your /bin/hostname..., is it a binary or a script? Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017, John Hughes wrote: >Come to think about it, if the problem was that their rc.local >was failing somewhere then they should be able to see that in the >output of systemctl or journalctl. > >Assuming they're using systemd, of course. :-) Not really. Its not just me, systemd is not considered to be safe for use by any security expert I know of (and I know more than I wish...) a legendary Bitcoin core developer (luke-jr) is explicitly encouraging the switch to Devuan, while many already use it to run full nodes using bitcoin-knots. One day we may even release a Devuan-based distro for this. ciao ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] hotplug of SD cards fails on Jessie
Le 20/11/2017 à 19:13, aitor_czr a écrit : Hi Didier, On 11/21/2017 04:37 PM, Didier Kryn wrote: Le 20/11/2017 à 14:37, aitor_czr a écrit : Hi again Didier, On 11/20/2017 02:23 PM, aitor_czr wrote: Hi Didier, On 11/21/2017 12:59 PM, Didier Kryn wrote: Hello. On my HP EliteBook laptop, where I've just upgraded from Debian-Wheezy to Devuan-Jessie, the SD cards don't show up on the Xfce desktop, while USB devices still do. I have checked that /dev/mmcblk0p1 is created - when there is only one partition. On my HP desktop with the same OS, installed ~ a year ago, it is even worse: the device isn't created. It worked out-of-the-box on Wheezy. Any clue? Didier I'm using vdev in combination with pmount on jessie and both work fine for me; however, i've never tested them in a SD card. But, if the nodes are created in /dev, they should work. Cheers, Aitor. I misunderstood your question, i thought you were trying to mount an USB device on a system *installed* in a SD card. Forget what i said so far :) Aitor. I mean: when I insert an USB memory key, an associated icon pops up on my desktop, but when I insert an SD card, nothing shows up. The system is on a disk. I don't know how xfce is informed of the presence of a new device. I'm afraid it's by dbus. Didier If you want to avoid dbus, then i recommend you to use pmount instead of udisks/udisks2. I have had a system detecting physical devices without dbus (using, as i said, vdev and pmount). RecentIy i uploaded an image of gnuinos including both of them. Dbus also has been removed from the dependencies of the network manager (simple-netaid instead of wicd) but dbus is still present in the system due to gvfs :( The tool which allows mounting/unmounting of hot-plug device in xfce is using gvfs. I have watched the uevent netlink and I see that Udev reacts to the insertion/removal by sending events to libudev, and I think this is part of the way used to inform xfce, because libudev contains call-backs or something like that for applications to get informed of events. Having an icon poping on the desktop on insertion of a hotplud device is a very confortable and sensible way to manage external devices; I'm not yet ready to give this up, even at the cost of keeping gvfs, and dbus. What I wonder for now is why this doesn't work for SD cards while it works for USB. There are other ways of being informed of the creation/deletion of a device and mounting/unmounting it: inotify can be used to be warned, and sudo to the get the permission, instead of policykit. I'm just too lazzy to write an application with a GUI to do this, unless I find some simple enough graphics toolkit. Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017 14:53:28 + KatolaZ wrote: > As Olaf explained, the problem seems to originate in the fact that the > initscripts package is not any more marked as important. Hence, if you > don't have it, you won't get it by default. I personally agree on the > fact that this is somehow a regression. If this is in any way a regression, or in fact if it's at all likely to provide unexpected behavior or breakage for Devuan users, why not do the following within the installation script: if test -f /etc/rc.local; then echo '#!/bin/sh -e' > /etc/rc.local echo 'exit 0' > /etc/rc.local fi # CREATE syvinit-style /etc/init.d/S99zz_rclocal # with its start case running /etc/rc.local # Use sysvinit style daemon controllers (update-rc.d I suspect) # to create the necessary level symlinks Do that, and no matter what Debian does to rc.local in the future, it works perfectly in Devuan. SteveT Steve Litt November 2017 featured book: Troubleshooting: Just the Facts http://www.troubleshooters.com/tjust ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ifconfig deprecated?
On Tue, Nov 21, 2017 at 05:53:49PM +0100, Jaromil wrote: > > nono, as I wrote: that script doesn't works anymore, if ran on a > freshly debootstrapped version of Debian 9. It seemed that rc.local > wasn't executed anymore. But there is some confusion, since both brctl > and ifconfig are legitimately deprecated. Assuming you have done > better checking, then the failure may be caused by them bailing out. ifconfig is deprecated? What is to be used instead? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On Mon, 20 Nov 2017 22:55:36 -0500 Hendrik Boom wrote: > > nono, as I wrote: that script doesn't works anymore, if ran on a > > freshly debootstrapped version of Debian 9. It seemed that rc.local > > wasn't executed anymore. But there is some confusion, since both > > brctl and ifconfig are legitimately deprecated. Assuming you have > > done better checking, then the failure may be caused by them > > bailing out. > > ifconfig is deprecated? What is to be used instead? ip R. -- richard lucassen http://contact.xaq.nl/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] ifconfig deprecated?
the official line is that the "ip" command replaces "ifconfig". I only use the Busybox version of ifconfig. You could use the Busybox version in the interim. The ip command is cool, though. jacksprat ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On Mon, 20 Nov 2017 22:55:36 -0500 Hendrik Boom wrote: > On Tue, Nov 21, 2017 at 05:53:49PM +0100, Jaromil wrote: > > > > nono, as I wrote: that script doesn't works anymore, if ran on a > > freshly debootstrapped version of Debian 9. It seemed that rc.local > > wasn't executed anymore. But there is some confusion, since both > > brctl and ifconfig are legitimately deprecated. Assuming you have > > done better checking, then the failure may be caused by them > > bailing out. > > ifconfig is deprecated? What is to be used instead? A program called ip. It has commands such as ip route, ip addr, ip link, and several others. It's confusing and underdocumented, but so is ifconfig (which I never even began to master). I've been using ip for about 2 years now: Starting when I wrote the Manjaro Experiments. SteveT Steve Litt November 2017 featured book: Troubleshooting: Just the Facts http://www.troubleshooters.com/tjust ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Error when updating from jessie to ascii 32bit
- Original Message - From: aitor_czr To: dng@lists.dyne.org ; Ismael L. Donis Garcia Sent: Monday, November 20, 2017 1:40 PM Subject: Re: [DNG] Error when updating from jessie to ascii 32bit Hi Ismael, On 11/21/2017 06:18 PM, Ismael L. Donis Garcia wrote: gpgv: Firmado el mar 21 nov 2017 02:04:03 CST gpgv:usando RSA clave 94532124541922FB gpgv: Imposible comprobar la firma: No public key .temp/.tmp/dists/ascii/InRelease signature does not verify. Parsing Packages and Sources files ... Get Translation files ... Get DEP-11 metadata files ... Files to download: 0 B Downloaded 221 kiB in 24s at 9.21 kiB/s. Everything OK. Moving meta files ... Not able to use rsync to update remote trace files ... Cleanup mirror. All done. root@(none):/mnt/datos/sistemas/linux/devuan# One detail: you have set to *none* your hostname. Why? Have a look at your /bin/hostname..., is it a binary or a >script? Aitor. /bin/hostname it's a binary Thanks -- Ismael Devuan User : http://distrowatch.com/table.php?distribution=devuan ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On Tue, Nov 21, 2017 at 10:32:34PM +, jacksprat wrote: > the official line is that the "ip" command replaces "ifconfig". I only use > the Busybox version of ifconfig. You could use the Busybox version in the > interim. The ip command is cool, though. No one is removing ifconfig yet, it's merely not installed by default anymore -- so if you insist, just "apt install net-tools". ifconfig is inadequate for a number of widespread setups, though, and will provide bad output without a warning. You had two decades to migrate -- this is about the slowest deprecation I've seen, as it has been degraded from priority:important to priority:optional only now. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out, ⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven big-ass trumpets are playing in the ⠈⠳⣄ sky. Your cat demands food. The priority should be obvious... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On Tue, 2017-11-21 at 23:50 +0100, Adam Borowski wrote: > > No one is removing ifconfig yet, it's merely not installed by default > anymore -- so if you insist, just "apt install net-tools". > > ifconfig is inadequate for a number of widespread setups, though, and will > provide bad output without a warning. You had two decades to migrate -- > this is about the slowest deprecation I've seen, as it has been degraded > from priority:important to priority:optional only now. You also have inetutils-ifconfig, from inetutils source, which also works on other architectures than GNU/Linux. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
I find it quite confusing to have a collection of "commands" with space in the name, as if it would be a single command with lots of sub commands in it. But then, "the colour of the button isn't that important" -- it all hangs on the documentation. Apparently there an "IP Command reference ip-cref.ps" somewhere, though the wanting is left guessing. Ralph. Svante Signell wrote on 22/11/17 10:14: On Tue, 2017-11-21 at 23:50 +0100, Adam Borowski wrote: No one is removing ifconfig yet, it's merely not installed by default anymore -- so if you insist, just "apt install net-tools". ifconfig is inadequate for a number of widespread setups, though, and will provide bad output without a warning. You had two decades to migrate -- this is about the slowest deprecation I've seen, as it has been degraded from priority:important to priority:optional only now. You also have inetutils-ifconfig, from inetutils source, which also works on other architectures than GNU/Linux. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On Tue, Nov 21, 2017 at 05:34:15PM -0500, Steve Litt wrote: > On Mon, 20 Nov 2017 22:55:36 -0500 > Hendrik Boom wrote: > > > On Tue, Nov 21, 2017 at 05:53:49PM +0100, Jaromil wrote: > > > > > > nono, as I wrote: that script doesn't works anymore, if ran on a > > > freshly debootstrapped version of Debian 9. It seemed that rc.local > > > wasn't executed anymore. But there is some confusion, since both > > > brctl and ifconfig are legitimately deprecated. Assuming you have > > > done better checking, then the failure may be caused by them > > > bailing out. > > > > ifconfig is deprecated? What is to be used instead? > > A program called ip. It has commands such as ip route, ip addr, ip > link, and several others. It's confusing and underdocumented, but so is > ifconfig (which I never even began to master). I've never mastered ifconfig either. But I've noticed that the simple command ifconfig tells me what interfaces are up at the moment and the packet counts tell me whether they are actually functioning. It's a very simple way to diagnose the most common netweok conectivity of all. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, Nov 21, 2017 at 03:47:26PM -0500, Steve Litt wrote: > On Tue, 21 Nov 2017 14:53:28 + > KatolaZ wrote: > > > As Olaf explained, the problem seems to originate in the fact that the > > initscripts package is not any more marked as important. Hence, if you > > don't have it, you won't get it by default. I personally agree on the > > fact that this is somehow a regression. > > If this is in any way a regression, or in fact if it's at all likely to > provide unexpected behavior or breakage for Devuan users, why not do > the following within the installation script: > > if test -f /etc/rc.local; then > echo '#!/bin/sh -e' > /etc/rc.local > echo 'exit 0' > /etc/rc.local > fi > # CREATE syvinit-style /etc/init.d/S99zz_rclocal > # with its start case running /etc/rc.local > # Use sysvinit style daemon controllers (update-rc.d I suspect) > # to create the necessary level symlinks > It's already there, in initscripts.postinst :) HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
Quoting Steve Litt (sl...@troubleshooters.com): > A program called ip. It has commands such as ip route, ip addr, ip > link, and several others. It's confusing and underdocumented, but so is > ifconfig (which I never even began to master). I have a knowledgebase item 'iproute2 transition' on http://linuxmafia.com/kb/Network_Other/ pointing to a good LWN.net article on this subject. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] ifconfig deprecated?
On 11/20/2017 10:55 PM, Hendrik Boom wrote: > On Tue, Nov 21, 2017 at 05:53:49PM +0100, Jaromil wrote: >> >> nono, as I wrote: that script doesn't works anymore, if ran on a >> freshly debootstrapped version of Debian 9. It seemed that rc.local >> wasn't executed anymore. But there is some confusion, since both brctl >> and ifconfig are legitimately deprecated. Assuming you have done >> better checking, then the failure may be caused by them bailing out. > > ifconfig is deprecated? What is to be used instead? > > -- hendrik ifconfig is supplied by net-tools which is no longer installed by default. If you want ifconfig, route, netstat and a few others, install net-tools. fsmithred ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Tue, 21 Nov 2017 18:21:14 +0100, John wrote in message : > (Damn but the systemd journal is great :-)) ..is there a way to decode and read those binary systemd journal logs on classic POSIX/Unix etc forensic systems _not_ running systemd? -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Wed, Nov 22, 2017 at 02:59:11AM +0100, Arnt Karlsen wrote: > On Tue, 21 Nov 2017 18:21:14 +0100, John wrote in message > : > > > (Damn but the systemd journal is great :-)) > > ..is there a way to decode and read those binary systemd journal logs > on classic POSIX/Unix etc forensic systems _not_ running systemd? > No, there is no way to do that, and we are probably spiralling down another flame... :( HND KatolaZ -- [ ~.,_ Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab ] [ "+. katolaz [at] freaknet.org --- katolaz [at] yahoo.it ] [ @) http://kalos.mine.nu --- Devuan GNU + Linux User ] [ @@) http://maths.qmul.ac.uk/~vnicosia -- GPG: 0B5F062F ] [ (@@@) Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ ] signature.asc Description: Digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 22/11/17 02:59, Arnt Karlsen wrote: On Tue, 21 Nov 2017 18:21:14 +0100, John wrote in message : (Damn but the systemd journal is great :-)) ..is there a way to decode and read those binary systemd journal logs on classic POSIX/Unix etc forensic systems _not_ running systemd? Is there any way to read a file in format X without a program that reads format X? I suppose you could scatter iron filings on the disk the use a scanning electron microscope to examine their positions and, using paper, pencil and a copy of the systemd doc work out the contents by hand. Or, being endowed with the minimum level of foresight necessary for survival have a forensic system that includes tools for reading the file formats you're likely to find on the system you want to post-mortem. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 22/11/17 06:50, KatolaZ wrote: On Wed, Nov 22, 2017 at 02:59:11AM +0100, Arnt Karlsen wrote: ..is there a way to decode and read those binary systemd journal logs on classic POSIX/Unix etc forensic systems _not_ running systemd? No, there is no way to do that, and we are probably spiralling down another flame... :( No way to do that? Seriously? No way at all? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On 21/11/17 19:46, Jaromil wrote: On Tue, 21 Nov 2017, John Hughes wrote: Come to think about it, if the problem was that their rc.local was failing somewhere then they should be able to see that in the output of systemctl or journalctl. Assuming they're using systemd, of course. :-) Not really. Its not just me, systemd is not considered to be safe for use by any security expert I know of (and I know more than I wish...) a legendary Bitcoin core developer (luke-jr) is explicitly encouraging the switch to Devuan, while many already use it to run full nodes using bitcoin-knots. One day we may even release a Devuan-based distro So, this whole /etc/rc.local kerfuffle, it happened on a system with systemd or sysvinit? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
On Wed, 22 Nov 2017 02:59:11 +0100 Arnt Karlsen wrote: > On Tue, 21 Nov 2017 18:21:14 +0100, John wrote in message > : > > > (Damn but the systemd journal is great :-)) A T SteveT Steve Litt November 2017 featured book: Troubleshooting: Just the Facts http://www.troubleshooters.com/tjust ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] rc.local removed from Debian 9, rly?
Le 22/11/2017 à 07:19, John Hughes a écrit : Is there any way to read a file in format X without a program that reads format X? The question is why use yet another "proprietary format"? Just to force people to be use systemd for every task they need to do with their computer. The logfiles in any non-systemd Linux system can be read with a variety of standard Unix tools: more, less, cat, grep, awk, vi, emacs (longer list of editors in case you need). Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
