Re: [DNG] some ASCII issues

[Rick Moen]

Quoting Alessandro Selli (alessandrose...@linux.com):

> It cannot work if what you need to do is feeding the HD controller some
> proprietary firmware that cannot legally be embedded in the GPL driver.

ITYM that the resulting derivative work cannot be lawfully
redistributed.  But compiling the driver does not redistribute it.

(I'm not necessarily endorsing your view about proprietary firmware.
I'm just pointing out that your conclusion doesn't follow from the
premise.)

If you disagree, kindly point out what reserved right of a copyright
owner is involved in said compilation.  Thanks.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I have a question about libsystemd0 in devuan ascii,

[Bruce Perens]

This might make a little more sense if you still can't understand:

By operating under their previously-stated policy of denying further
service to clients who exercise their right to distribute under the GPL
license, Open Source Security Inc. creates an expectation that exercise of
the re-distribution right required under the terms of the  GPL will lead to
business damage to the customer. This practice effectively is an added term
to the license, and addition of such a term is prohibited under language in
GPL section 6. This leads to termination of the GPL license granted to Open
Source Security Inc., and thus to copyright infringement of the Linux
Kernel by that entity. In addition, the GPL is breached as a contract from
the copyright holders of the Linux software to which Open Source Security
Inc. and the customer are both joined.

On Sun, Jul 2, 2017 at 5:07 PM, Bruce Perens  wrote:

> The specific text breached is "You may not impose any further
> restrictions on the recipients' exercise of the rights granted herein."
>
> On Sun, Jul 2, 2017 at 5:05 PM, Bruce Perens  wrote:
>
>> My legal counsel says it's a direct breach of the license, not of
>> business law.
>>
>> By the way, the next issue of Berkeley Technology Law Journal has this
>> article
>> 
>> which I co-authored with a law teacher at Boalt Hall.
>>
>>
>>
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] some ASCII issues

[Alessandro Selli]

On Mon, 3 Jul 2017 at 01:03:13 +0200
Arnt Karlsen  wrote:

> On Mon, 3 Jul 2017 00:42:52 +0200, Alessandro wrote in message 
> <20170703004252.748a9c7f@ayu>:
> 
>> Il giorno Wed, 28 Jun 2017 19:38:11 +0200
>> Didier Kryn  ha scritto:
>>   
>>> Le 28/06/2017 à 15:40, Stephan Seitz a écrit :  
 And today you should always encrypt your discs. 
>>>
>>>  I don't see any reason to encrypt /usr. You might like to
>>> encrypt /etc because it contains user names and (already encrypted)
>>> passwords. But definitely there is no reason to encrypt everything.  
>> 
>>   Valid reasons to encrypt /usr include:
>> 
>> 1) /usr resides on the same partition as / and/or /home (trivial
>> case); 2) protecting its files from being tampered with when the
>> device is offline;
>> 3) making harder to someone who can access your
>> offline HD understand which partition is /, or /usr or /home, so that
>> the attacker will have to try to decrypt them all;
>> 4) you put stuff in /usr/local that might contain
>> keys/passwords/sensitive information that would better be kept
>> protected.  
> 
> ..if you wanna protect /usr/local, chop that off /usr and 
> encrypt, mount etc them all as you damned please.

  I forgot to mention: leaking your collection of installed software is
sometimes itself leaking personal and possibly sensitive information about
yourself and your business, for the same reasons TCP/IP traffic metadata is
important in it's own right.  Plus, if you travel extensively, you might not
know if the place you're traveling into has enacted some restrictions on the
kind of software you are allowed to own and run.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I have a question about libsystemd0 in devuan ascii,

[Bruce Perens]

The specific text breached is "You may not impose any further restrictions
on the recipients' exercise of the rights granted herein."

On Sun, Jul 2, 2017 at 5:05 PM, Bruce Perens  wrote:

> My legal counsel says it's a direct breach of the license, not of business
> law.
>
> By the way, the next issue of Berkeley Technology Law Journal has this
> article
> 
> which I co-authored with a law teacher at Boalt Hall.
>
>
>
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I have a question about libsystemd0 in devuan ascii,

[Bruce Perens]

My legal counsel says it's a direct breach of the license, not of business
law.

By the way, the next issue of Berkeley Technology Law Journal has this
article

which I co-authored with a law teacher at Boalt Hall.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] some ASCII issues

[Alessandro Selli]

On Mon, 3 Jul at 2017 01:03:13 +0200
Arnt Karlsen  wrote:

> On Mon, 3 Jul 2017 00:42:52 +0200, Alessandro wrote in message 
> <20170703004252.748a9c7f@ayu>:
> 
>> Il giorno Wed, 28 Jun 2017 19:38:11 +0200
>> Didier Kryn  ha scritto:
>>
>>> Le 28/06/2017 à 15:40, Stephan Seitz a écrit :  
>>> > And today you should always encrypt your discs. 
>>>
>>>  I don't see any reason to encrypt /usr. You might like to
>>> encrypt /etc because it contains user names and (already encrypted)
>>> passwords. But definitely there is no reason to encrypt everything.  
>> 
>>   Valid reasons to encrypt /usr include:
>> 
>> 1) /usr resides on the same partition as / and/or /home (trivial
>> case); 2) protecting its files from being tampered with when the
>> device is offline;
>> 3) making harder to someone who can access your
>> offline HD understand which partition is /, or /usr or /home, so that
>> the attacker will have to try to decrypt them all;
>> 4) you put stuff in /usr/local that might contain
>> keys/passwords/sensitive information that would better be kept
>> protected.  
>
> ..if you wanna protect /usr/local, chop that off /usr and 
> encrypt, mount etc them all as you damned please.

  /usr/local was standardized for a reason.  You might do as you like on your
personal PC, maybe you're not as free to do the same on your company's
server/workstation.  You might have /opt bind-mounted on /usr/local, and have
lots of stuff there you don't want to peruse to see if any of it would better
be kept away from prying eyes (like VM images).
  What specific reasons do you have *not* to encrypt /usr in a
machine that has / and /home encrypted?  What do you gain by that?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] OPENRC now works! thank you Svante for your patience

[zap]

Just to make it clear, I have replied once more with the title changed...

I have donated 10$ to devuan as a thanks. I am not super rich, but I
have done what I can. so thank you.


On 07/02/2017 04:34 PM, zap wrote:
>
> On 07/02/2017 04:25 PM, Svante Signell wrote:
>> On Sun, 2017-07-02 at 14:51 -0400, zap wrote:
>>> I appear to be getting conflicts, so I must need sysvinit-utils in
>>> deb
>>> form.
>>> this probably is the last thing I need at the moment to make it
>>> work...
>> Sorry, but you have to show us what conflicts you see... And your
>> /etc/apt/sources.list, and your commands used.
> That makes sense my bad... I just got to the last step. I just have to
> install initscripts. I figured a way out somehow? gdebi isn't as
> reliable I guess..
>
> Edit: I finally got it installed,
>
> at last...
>
> Tell me something though, is it up to testing quality standards yet?
> regardless, though thank you for being paitent, this was kind of
> confusing... heh.  dpkg > gdebi 
>
> for some reason gdebi must have been causing failures aka... hehe.
>

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] some ASCII issues

[Arnt Karlsen]

On Mon, 3 Jul 2017 00:42:52 +0200, Alessandro wrote in message 
<20170703004252.748a9c7f@ayu>:

> Il giorno Wed, 28 Jun 2017 19:38:11 +0200
> Didier Kryn  ha scritto:
> 
> > Le 28/06/2017 à 15:40, Stephan Seitz a écrit :
> > > And today you should always encrypt your discs.   
> >
> >  I don't see any reason to encrypt /usr. You might like to
> > encrypt /etc because it contains user names and (already encrypted)
> > passwords. But definitely there is no reason to encrypt everything.
> 
>   Valid reasons to encrypt /usr include:
> 
> 1) /usr resides on the same partition as / and/or /home (trivial
> case); 2) protecting its files from being tampered with when the
> device is offline;
> 3) making harder to someone who can access your
> offline HD understand which partition is /, or /usr or /home, so that
> the attacker will have to try to decrypt them all;
> 4) you put stuff in /usr/local that might contain
> keys/passwords/sensitive information that would better be kept
> protected.

..if you wanna protect /usr/local, chop that off /usr and 
encrypt, mount etc them all as you damned please.

-- 
..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] some ASCII issues

[Alessandro Selli]

Il giorno Wed, 28 Jun 2017 19:38:11 +0200
Didier Kryn  ha scritto:

> Le 28/06/2017 à 15:40, Stephan Seitz a écrit :
> > And today you should always encrypt your discs.   
>
>  I don't see any reason to encrypt /usr. You might like to encrypt 
> /etc because it contains user names and (already encrypted) passwords. 
> But definitely there is no reason to encrypt everything.

  Valid reasons to encrypt /usr include:

1) /usr resides on the same partition as / and/or /home (trivial case);
2) protecting its files from being tampered with when the device is offline;
3) making harder to someone who can access your offline HD understand which
partition is /, or /usr or /home, so that the attacker will have to try to
decrypt them all;
4) you put stuff in /usr/local that might contain keys/passwords/sensitive
information that would better be kept protected.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] some ASCII issues

[Alessandro Selli]

On Wed, 28 Jun 2017 at 08:09:21 -0700
Rick Moen  wrote:

> Quoting Stephan Seitz (stse+dev...@fsing.rootsland.net):
> 
> > That the kernel can’t find the root filesystem if it is encrypted?
> > And the kernel lacks the capability to ask you for the password.  
>
> If you're correct that a kernal cannot find an encrypted rootfs, then by
> the same token it cannot find an encrypted initrd, either.  So, what
> have you really gained?

  The initramfs does not need to be encrypted, because it does not have the
key to decrypt the HD.  It has the routine that prompts for the decryption
key and uses it to decrypt the root partition.

> In any event, I think you are incorrect.  Here's a runthrough that Pavel
> Kogan wrote, and nothing he describes requires an initrd.  He _does_ 
> use a RAMdisk to store the keyfile after booting, but that's a different
> matter.  http://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/

  Here are the relevant lines:

I tried various methods to get GRUB to load the keyfile into memory
and pass it to the kernel, without success. Then, I realised that the
initrd image is itself something GRUB loads into memory, and
mkinitcpio.conf has a very convenient FILES option…

FILES=/crypto_keyfile.bin

Run mkinitcpio again, and when you reboot, you’ll only need to enter
your password once.


>> >Anyway, I don't want to encrypt all discs on my Linux server for  
>> 
>> Well, server may be a special case.  
>
> It's funny how all the new Linux kiddies keep wanting to dismiss what
> I've been doing since 1993 on Linux (and since the 1980s on other
> *nixes) as a 'special case'.

  Servers are indeed a different matter.  They are usually not kept home,
rather in a secure, dedicated and protected environment.  Thus they are less
susceptible to be:

1) stolen in a house burglary;
2) impounded during a police raid into your home.

  And you usually do not travel with your server inside your case, as
opposed to what you do with your laptop.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Arnt Karlsen]

On Sun, 2 Jul 2017 14:21:04 -0400, zap wrote in message 
<4ab545b8-d9ba-e8d4-df1e-fa8a0c73e...@posteo.de>:

> On 07/02/2017 11:09 AM, Svante Signell wrote:
> > Hi,
> >
> > Seems like max file size is 40k for the mailing list, so the mail to
> > the list is blocked. zap, did the attached files reach your private
> > mail?  
> 
> Well, I think I received them, unless the ones you sent got shrunk. ;)

..one easy way to make sure, is list those attached file's checksums, 
so chey can be chk'ed with e.g. md5sum -c upwards, for "the works",
'aptitude install jacksum' and play around. ;o)

-- 
..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] Beware the Icedove to Thunderbird transition

[Adam Borowski]

On Sun, Jul 02, 2017 at 01:05:06PM -0400, Clark Sideroad wrote:
> My advice: back-up everything related

Bad advice: just do the upgrade normally without any special precautions,
and if your special non-standard $Element$Bird setup gets borked, just
recover from backups you do anyway.  No special backup before an operation
as disruptive as upgrading between De??an releases is needed either, as you,
like anyone without a data loss wish, already backup at least daily.

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] some ASCII issues

[Alessandro Selli]

On Tue, 27 Jun 2017 at 22:57:16 -0700
Rick Moen  wrote:

> Quoting John Morris (jmor...@beau.org):
>
>> Nope, that negates one of the principle reasons to use an initramfs in
>> the first place.  You assume the stock kernel can see the drive where
>> you intend to put this new partition; one of the big drivers of initrd
>> in the first place was exotic hardware, etc. so GRUB uses BIOS
>> (including extension ROMs on controller cards) to load both the kernel
>> and the initrd so it can take whatever steps are needed, i.e load the
>> right modules, start lvm, setup encrypted filesystem magic, etc. to make
>> the main drive/partitions/etc. visible.  Your idea could deal with most
>> everything that didn't need a kernel module but totally fails at that
>> task.  
> 
> Step 1.  Compile a kernel that includes inline all key drivers including
>  those needed to find the root filesystem.
> Step 2.  Profit!
> 
> That's the old-school method.

  It cannot work if what you need to do is feeding the HD controller some
proprietary firmware that cannot legally be embedded in the GPL driver.


Alessandro

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] I have a question about libsystemd0 in devuan ascii,

[Alessandro Selli]

On Sat, 01 Jul 2017 at 23:05:08 +
Bruce Perens  wrote:

> It is the fact that the two actions are connected that makes it a breach.
> There are very many actions that are legal in isolation, but not when one
> is carried out as a consequence of another. The most common instances are
> of course in anti-discrimination law.

  I think you mean such an act goes against national (USA) business law, but
this does not mean that it goes against the GPL licence.  You might be right
that GRSecurity's actions violate some state or national statute, but not
that they violate the GPL licence.

> As an expert witness, I would have no trouble connecting them for a judge
> and showing how they were tantamount to an added term under section 6.

  Do you mean GPL sec. 6, "Conveying Non-Source Forms"?


Alessandro


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

On 07/02/2017 04:25 PM, Svante Signell wrote:
> On Sun, 2017-07-02 at 14:51 -0400, zap wrote:
>> I appear to be getting conflicts, so I must need sysvinit-utils in
>> deb
>> form.
>> this probably is the last thing I need at the moment to make it
>> work...
> Sorry, but you have to show us what conflicts you see... And your
> /etc/apt/sources.list, and your commands used.

That makes sense my bad... I just got to the last step. I just have to
install initscripts. I figured a way out somehow? gdebi isn't as
reliable I guess..

Edit: I finally got it installed,

at last...

Tell me something though, is it up to testing quality standards yet?
regardless, though thank you for being paitent, this was kind of
confusing... heh.  dpkg > gdebi 

for some reason gdebi must have been causing failures aka... hehe.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Svante Signell]

On Sun, 2017-07-02 at 14:51 -0400, zap wrote:
> 
> I appear to be getting conflicts, so I must need sysvinit-utils in
> deb
> form.
> this probably is the last thing I need at the moment to make it
> work...

Sorry, but you have to show us what conflicts you see... And your
/etc/apt/sources.list, and your commands used.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

On 07/02/2017 02:51 PM, zap wrote:
>
> I appear to be getting conflicts, so I must need sysvinit-utils in deb
> form.
> this probably is the last thing I need at the moment to make it work...
Actually, sysvinit-utils and util-linux refuse to upgrade.

I keep getting a dumb error that says:

Error: no longer provides util-linux
>
> On 07/02/2017 11:09 AM, Svante Signell wrote:
>> Hi,
>>
>> Seems like max file size is 40k for the mailing list, so the mail to
>> the list is blocked. zap, did the attached files reach your private
>> mail?
>>
>> On Sun, 2017-07-02 at 16:59 +0200, Svante Signell wrote:
>>> On Sat, 2017-07-01 at 19:54 -0400, zap wrote:
>> Hi zap,
>>
>> As I wrote earlier, you can install openrc by:
>> 0) Enable ascii in /etc/apt/sources.list
>> deb http://auto.mirror.devuan.org/merged ascii main
>>
>> 1) add to /etc/apt/sources.list
>>  deb http://packages.devuan.org/devuan/ ascii-proposed main
>>
>> 2) apt-get update
>>
>> 3) apt-get download sysvinit-utils
>>
>> 4) Build* and install libfdisk1 and util-linux
>> (2.29.21+devuan1).
>> If
>> you are in i386 I can send you them. Otherwise see below.
>>
>> dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
>> 1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb
>>
>> 5) apt-get upgrade: Installs latest initscripts:
>> initscripts (2.88dsf-59.9+devuan2)
>>
>> 6) apt-get -s install openrc
>> Check that all is OK, then remove the -s
>> The following additional packages will be installed:
>>   libeinfo1 librc1
>> The following packages will be REMOVED:
>>   sysv-rc
> Okay, this is a better way to know how to do so. I didn't
> understand the
> instructions before. that's all... thanks
 Actually I have to make an edit, I am using an x86_64 bit
 machine.  and
 some of the packages in the list for needed, debian/control, I
 cannot
 find. odd though it may be...
>>> Attached are the needed .debs for amd64. Just follow the instructions
>>> above. (I hope the attachment limit is too low, file sizes are 221 kB
>>> and 979 kB)
>>>
>>> In point 3) you might have to add -t ascii-proposed to get the right
>>> version. 
>>>
>>> In point 4) do
>>> dpkg -i libfdisk1_2.29.2-1+devuan1_amd64.deb util-linux_2.29.2-\
>>> 1+devuan1_amd64.deb sysvinit-utils_2.88dsf-59.9+devuan2_amd64.deb
>>>
>>> In point 5) do
>>> apt-get install initscripts -t ascii-proposed
>>> or
>>> apt-get upgrade -t ascii-proposed
>>>
>>> HTH
>>>
> ___
> 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] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

I appear to be getting conflicts, so I must need sysvinit-utils in deb
form.
this probably is the last thing I need at the moment to make it work...


On 07/02/2017 11:09 AM, Svante Signell wrote:
> Hi,
>
> Seems like max file size is 40k for the mailing list, so the mail to
> the list is blocked. zap, did the attached files reach your private
> mail?
>
> On Sun, 2017-07-02 at 16:59 +0200, Svante Signell wrote:
>> On Sat, 2017-07-01 at 19:54 -0400, zap wrote:
>>>
> Hi zap,
>
> As I wrote earlier, you can install openrc by:
> 0) Enable ascii in /etc/apt/sources.list
> deb http://auto.mirror.devuan.org/merged ascii main
>
> 1) add to /etc/apt/sources.list
>  deb http://packages.devuan.org/devuan/ ascii-proposed main
>
> 2) apt-get update
>
> 3) apt-get download sysvinit-utils
>
> 4) Build* and install libfdisk1 and util-linux
> (2.29.21+devuan1).
> If
> you are in i386 I can send you them. Otherwise see below.
>
> dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
> 1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb
>
> 5) apt-get upgrade: Installs latest initscripts:
> initscripts (2.88dsf-59.9+devuan2)
>
> 6) apt-get -s install openrc
> Check that all is OK, then remove the -s
> The following additional packages will be installed:
>   libeinfo1 librc1
> The following packages will be REMOVED:
>   sysv-rc
 Okay, this is a better way to know how to do so. I didn't
 understand the
 instructions before. that's all... thanks
>>> Actually I have to make an edit, I am using an x86_64 bit
>>> machine.  and
>>> some of the packages in the list for needed, debian/control, I
>>> cannot
>>> find. odd though it may be...
>> Attached are the needed .debs for amd64. Just follow the instructions
>> above. (I hope the attachment limit is too low, file sizes are 221 kB
>> and 979 kB)
>>
>> In point 3) you might have to add -t ascii-proposed to get the right
>> version. 
>>
>> In point 4) do
>> dpkg -i libfdisk1_2.29.2-1+devuan1_amd64.deb util-linux_2.29.2-\
>> 1+devuan1_amd64.deb sysvinit-utils_2.88dsf-59.9+devuan2_amd64.deb
>>
>> In point 5) do
>> apt-get install initscripts -t ascii-proposed
>> or
>> apt-get upgrade -t ascii-proposed
>>
>> HTH
>>

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[zap]

On 07/02/2017 11:09 AM, Svante Signell wrote:
> Hi,
>
> Seems like max file size is 40k for the mailing list, so the mail to
> the list is blocked. zap, did the attached files reach your private
> mail?

Well, I think I received them, unless the ones you sent got shrunk. ;)

> On Sun, 2017-07-02 at 16:59 +0200, Svante Signell wrote:
>> On Sat, 2017-07-01 at 19:54 -0400, zap wrote:
>>>
> Hi zap,
>
> As I wrote earlier, you can install openrc by:
> 0) Enable ascii in /etc/apt/sources.list
> deb http://auto.mirror.devuan.org/merged ascii main
>
> 1) add to /etc/apt/sources.list
>  deb http://packages.devuan.org/devuan/ ascii-proposed main
>
> 2) apt-get update
>
> 3) apt-get download sysvinit-utils
>
> 4) Build* and install libfdisk1 and util-linux
> (2.29.21+devuan1).
> If
> you are in i386 I can send you them. Otherwise see below.
>
> dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
> 1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb
>
> 5) apt-get upgrade: Installs latest initscripts:
> initscripts (2.88dsf-59.9+devuan2)
>
> 6) apt-get -s install openrc
> Check that all is OK, then remove the -s
> The following additional packages will be installed:
>   libeinfo1 librc1
> The following packages will be REMOVED:
>   sysv-rc
 Okay, this is a better way to know how to do so. I didn't
 understand the
 instructions before. that's all... thanks
>>> Actually I have to make an edit, I am using an x86_64 bit
>>> machine.  and
>>> some of the packages in the list for needed, debian/control, I
>>> cannot
>>> find. odd though it may be...
>> Attached are the needed .debs for amd64. Just follow the instructions
>> above. (I hope the attachment limit is too low, file sizes are 221 kB
>> and 979 kB)
>>
>> In point 3) you might have to add -t ascii-proposed to get the right
>> version. 
>>
>> In point 4) do
>> dpkg -i libfdisk1_2.29.2-1+devuan1_amd64.deb util-linux_2.29.2-\
>> 1+devuan1_amd64.deb sysvinit-utils_2.88dsf-59.9+devuan2_amd64.deb
>>
>> In point 5) do
>> apt-get install initscripts -t ascii-proposed
>> or
>> apt-get upgrade -t ascii-proposed
>>
>> HTH
>>

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Beware the Icedove to Thunderbird transition

[Clark Sideroad]

If you have a non-standard setup the Debian scripted install can make a 
mess and then bring up a text window saying things didn't go as planned.


They say things can't get lost "don't worry", but if you are running an 
ancient, a "Daily" build or non-Debian set-up worry. I'm sure it worked 
for them.


There is a Debian wiki about it but it didn't help my situation.

My advice: back-up everything related including hidden files in the 
users home directory, rename and hide them before pulling the trigger on 
the transition script.


--

Clarke



___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] How long should I expect to wait for openrc to be ready in devuan ascii

[Svante Signell]

Hi,

Seems like max file size is 40k for the mailing list, so the mail to
the list is blocked. zap, did the attached files reach your private
mail?

On Sun, 2017-07-02 at 16:59 +0200, Svante Signell wrote:
> On Sat, 2017-07-01 at 19:54 -0400, zap wrote:
> > 
> > 
> > > > Hi zap,
> > > > 
> > > > As I wrote earlier, you can install openrc by:
> > > > 0) Enable ascii in /etc/apt/sources.list
> > > > deb http://auto.mirror.devuan.org/merged ascii main
> > > > 
> > > > 1) add to /etc/apt/sources.list
> > > >  deb http://packages.devuan.org/devuan/ ascii-proposed main
> > > > 
> > > > 2) apt-get update
> > > > 
> > > > 3) apt-get download sysvinit-utils
> > > > 
> > > > 4) Build* and install libfdisk1 and util-linux
> > > > (2.29.21+devuan1).
> > > > If
> > > > you are in i386 I can send you them. Otherwise see below.
> > > > 
> > > > dpkg -i libfdisk1_2.29.2-1+devuan1_i386.deb util-linux_2.29.2-
> > > > 1+devuan1_i386.deb sysvinit-utils_2.88dsf-59.9+devuan2_i386.deb
> > > > 
> > > > 5) apt-get upgrade: Installs latest initscripts:
> > > > initscripts (2.88dsf-59.9+devuan2)
> > > > 
> > > > 6) apt-get -s install openrc
> > > > Check that all is OK, then remove the -s
> > > > The following additional packages will be installed:
> > > >   libeinfo1 librc1
> > > > The following packages will be REMOVED:
> > > >   sysv-rc
> > > Okay, this is a better way to know how to do so. I didn't
> > > understand the
> > > instructions before. that's all... thanks
> > 
> > Actually I have to make an edit, I am using an x86_64 bit
> > machine.  and
> > some of the packages in the list for needed, debian/control, I
> > cannot
> > find. odd though it may be...
> 
> Attached are the needed .debs for amd64. Just follow the instructions
> above. (I hope the attachment limit is too low, file sizes are 221 kB
> and 979 kB)
> 
> In point 3) you might have to add -t ascii-proposed to get the right
> version. 
> 
> In point 4) do
> dpkg -i libfdisk1_2.29.2-1+devuan1_amd64.deb util-linux_2.29.2-\
> 1+devuan1_amd64.deb sysvinit-utils_2.88dsf-59.9+devuan2_amd64.deb
> 
> In point 5) do
> apt-get install initscripts -t ascii-proposed
> or
> apt-get upgrade -t ascii-proposed
> 
> HTH
> 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Why /command ?

[Steve Litt]

On Sun, 2 Jul 2017 08:21:01 +0200
Didier Kryn  wrote:

> Le 02/07/2017 à 01:37, Steve Litt a écrit :
> > Hi all,
> >
> > I'm writing a document on how to install runit on Devuan, with the
> > hope that some day it will lead to a Devuan package that makes
> > sense and to the best degree possible implements the goals of the
> > software's author.
> >
> > Most of it's pretty straightforward, but the runit install scripts
> > (package/upgrade to be specific) create /command right off the root,
> > and the runit docs suggest I create /package right off the root.
> > These are things that most distros would refuse to do.
> >
> > So I was wondering what the original intent was in having these two
> > directories directly off the root? Is it so the init and supervision
> > can proceed even before partition mounts are complete? Is there some
> > other reason? Can anyone recommend setups that fulfill the reasons
> > for the direct-off-root dirs without having direct-off-root dirs?
> >
> > By the way, if the runit docs go well, I'll do the same thing with
> > s6. 
> 
>  Sysvinit reads its configuration and scripts from directory
> trees in /etc. Therefore, why not put /command and /package somewhere
> there, eg in /etc/runit ? Everybody assumes /etc must be present when
> init starts.
> 
>  Just my first idea. There might be better ones...
> 
>  Didier


Yeah, something like:

/etc/
  runitstuff/
sv/
package/
command/
service/
  runit/
(all the stuff currently in/under /etc/runit)

Sounds good to me, but before I make *any* move I want to know, from
Gerrit Pape and from the rest of the supervision list crowd, why these
things are direct off the root, and always have been, from the days of
djb's daemontools. What was djb's reason for putting them directly off
the root?

By the way, my choices might be constrained to the extent that I'd
greatly prefer NOT to mess with Gerritt's installation scripts, but due
to symlinks pointing to symlinks pointing to symlinks, the more I
change things, the more likely it becomes that I'd need to change his
install scripts.

Thanks,

SteveT




-- 
SteveT

Steve Litt 
June 2017 featured book: The Key to Everyday Excellence
http://www.troubleshooters.com/key
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Error updating ascii today

[Vincent Bentley]

I tried again using: sudo apt update

Get:1 http://packages.devuan.org/merged ascii InRelease [113 kB]
Err:1 http://packages.devuan.org/merged ascii InRelease
  Couldn't create temporary file /tmp/apt.conf.r8vXm3 for passing config
to apt-key
Reading package lists... Done
W: GPG error: http://packages.devuan.org/merged ascii InRelease:
Couldn't create temporary file /tmp/apt.conf.r8vXm3 for passing config
to apt-key
E: The repository 'http://packages.devuan.org/merged ascii InRelease' is
not signed.
N: Updating from such a repository can't be done securely, and is
therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user
configuration details.

For info...

uname -a

Linux ds2 4.9.0-3-686-pae #1 SMP Debian 4.9.30-2 (2017-06-12) i686 GNU/Linux


lsb_release -a

No LSB modules are available.
Distributor ID: Devuan
Description:Devuan GNU/Linux 2.0 (ascii)
Release:2.0
Codename:   ascii


On 02/07/17 12:34, Daniel Reurich wrote:
> Hi Vincent,
> 
> Can you try using apt instead?
> 
> 
> 
> On 2 July 2017 10:35:08 AM NZST, Vincent Bentley  
> wrote:
>> I updated a 32-bit Devuan Jessie system today (Saturday) to Ascii.
>> After
>> rebooting I needed to fix a few package dependency problems and I got
>> the following message when using aptitude to update.
>>
>> sudo aptitude -y update
>>
>> Get: 1 http://packages.devuan.org/merged ascii InRelease [113 kB]
>> Err http://packages.devuan.org/merged ascii InRelease
>> Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
>> to apt-key
>> Fetched 113 kB in 9s (12.2 kB/s)
>> W: GPG error: http://packages.devuan.org/merged ascii InRelease:
>> Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
>> to apt-key
>> E: The repository 'http://packages.devuan.org/merged ascii InRelease'
>> is
>> not signed.
>> E: Failed to download some files
>> W: Failed to fetch
>> http://packages.devuan.org/merged/dists/ascii/InRelease: Couldn't
>> create
>> temporary file /tmp/apt.conf.0TEdzn for passing config to apt-key
>> E: Some index files failed to download. They have been ignored, or old
>> ones used instead.
>>
>> I use tmpfs for /tmp and it was set at 100MB. I get the same error with
>> a 500MB tmpfs. Is this a problem related to the ascii repository
>> problem
>> earlier this week or is it a signing fault?
> 
> 
> 
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 



smime.p7s
Description: S/MIME Cryptographic Signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Error updating ascii today

[Daniel Reurich]

Hi Vincent,

Can you try using apt instead?



On 2 July 2017 10:35:08 AM NZST, Vincent Bentley  
wrote:
>I updated a 32-bit Devuan Jessie system today (Saturday) to Ascii.
>After
>rebooting I needed to fix a few package dependency problems and I got
>the following message when using aptitude to update.
>
>sudo aptitude -y update
>
>Get: 1 http://packages.devuan.org/merged ascii InRelease [113 kB]
>Err http://packages.devuan.org/merged ascii InRelease
> Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
>to apt-key
>Fetched 113 kB in 9s (12.2 kB/s)
>W: GPG error: http://packages.devuan.org/merged ascii InRelease:
>Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
>to apt-key
>E: The repository 'http://packages.devuan.org/merged ascii InRelease'
>is
>not signed.
>E: Failed to download some files
>W: Failed to fetch
>http://packages.devuan.org/merged/dists/ascii/InRelease: Couldn't
>create
>temporary file /tmp/apt.conf.0TEdzn for passing config to apt-key
>E: Some index files failed to download. They have been ignored, or old
>ones used instead.
>
>I use tmpfs for /tmp and it was set at 100MB. I get the same error with
>a 500MB tmpfs. Is this a problem related to the ascii repository
>problem
>earlier this week or is it a signing fault?

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd: good riddance!

[Ron]

On Sat, 1 Jul 2017 18:36:40 -0500
Nate Bargmann  wrote:

> > > fate accompli  
> > "Fate"

> >  is very apposite in the circumstance  
 
> One misspell and a person's reputation is shot forever!
> :-)

And me thinking it was purposefully done  ;-3)
 
Cheers,
 
Ron.
-- 
Have you ever imagined a world
  with no hypothetical situations ?

   -- http://www.olgiati-in-paraguay.org --
 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Error updating ascii today

[Miroslav Rovis]

On 170702-09:18+0200, Alessandro Selli wrote:
> Il giorno Sat, 1 Jul 2017 23:35:08 +0100
> Vincent Bentley  ha scritto:
> 
> > I updated a 32-bit Devuan Jessie system today (Saturday) to Ascii. After
> > rebooting I needed to fix a few package dependency problems and I got
> > the following message when using aptitude to update.
> > 
> > sudo aptitude -y update
> > 
> > Get: 1 http://packages.devuan.org/merged ascii InRelease [113 kB]
> > Err http://packages.devuan.org/merged ascii InRelease
> >   Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
> > to apt-key
> > Fetched 113 kB in 9s (12.2 kB/s)
> > W: GPG error: http://packages.devuan.org/merged ascii InRelease:
> > Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
> > to apt-key
> > E: The repository 'http://packages.devuan.org/merged ascii InRelease' is
> > not signed.
> > E: Failed to download some files
> > W: Failed to fetch
> > http://packages.devuan.org/merged/dists/ascii/InRelease: Couldn't create
> > temporary file /tmp/apt.conf.0TEdzn for passing config to apt-key
> > E: Some index files failed to download. They have been ignored, or old
> > ones used instead.
> > 
> > I use tmpfs for /tmp and it was set at 100MB. I get the same error with
> > a 500MB tmpfs. Is this a problem related to the ascii repository problem
> > earlier this week or is it a signing fault?
> 
>   Here is the (very) likely reason:
WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII
> https://lists.dyne.org/lurker/message/20170628.094825.8a121488.en.html

But that ought to have been solved:
AMPROLLA GLITCH: ISSUE SOLVED -- PLEASE READ CAREFULLY
https://lists.dyne.org/lurker/message/20170628.160400.b98c6ead.en.html
 (that's more than six hours later than the WARNING)

I was able to apt-get update, didn't have issues. This is from my user-made
(just "apt-get update |& tee 

Re: [DNG] Error updating ascii today

[Alessandro Selli]

Il giorno Sat, 1 Jul 2017 23:35:08 +0100
Vincent Bentley  ha scritto:

> I updated a 32-bit Devuan Jessie system today (Saturday) to Ascii. After
> rebooting I needed to fix a few package dependency problems and I got
> the following message when using aptitude to update.
> 
> sudo aptitude -y update
> 
> Get: 1 http://packages.devuan.org/merged ascii InRelease [113 kB]
> Err http://packages.devuan.org/merged ascii InRelease
>   Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
> to apt-key
> Fetched 113 kB in 9s (12.2 kB/s)
> W: GPG error: http://packages.devuan.org/merged ascii InRelease:
> Couldn't create temporary file /tmp/apt.conf.0TEdzn for passing config
> to apt-key
> E: The repository 'http://packages.devuan.org/merged ascii InRelease' is
> not signed.
> E: Failed to download some files
> W: Failed to fetch
> http://packages.devuan.org/merged/dists/ascii/InRelease: Couldn't create
> temporary file /tmp/apt.conf.0TEdzn for passing config to apt-key
> E: Some index files failed to download. They have been ignored, or old
> ones used instead.
> 
> I use tmpfs for /tmp and it was set at 100MB. I get the same error with
> a 500MB tmpfs. Is this a problem related to the ascii repository problem
> earlier this week or is it a signing fault?

  Here is the (very) likely reason:
https://lists.dyne.org/lurker/message/20170628.094825.8a121488.en.html


Alessandro
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Why /command ?

[Didier Kryn]

Le 02/07/2017 à 01:37, Steve Litt a écrit :

Hi all,

I'm writing a document on how to install runit on Devuan, with the hope
that some day it will lead to a Devuan package that makes sense and to
the best degree possible implements the goals of the software's author.

Most of it's pretty straightforward, but the runit install scripts
(package/upgrade to be specific) create /command right off the root,
and the runit docs suggest I create /package right off the root. These
are things that most distros would refuse to do.

So I was wondering what the original intent was in having these two
directories directly off the root? Is it so the init and supervision
can proceed even before partition mounts are complete? Is there some
other reason? Can anyone recommend setups that fulfill the reasons for
the direct-off-root dirs without having direct-off-root dirs?

By the way, if the runit docs go well, I'll do the same thing with s6.



Sysvinit reads its configuration and scripts from directory trees 
in /etc. Therefore, why not put /command and /package somewhere there, 
eg in /etc/runit ? Everybody assumes /etc must be present when init starts.


Just my first idea. There might be better ones...

Didier

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng