Re: [DNG] some ASCII issues

Rick Moen [2017-06-28 20:33]: > Temporary files in /tmp are sometimes a little sensitive and sometimes > greatly so. (It's usually a tmpfs on my systems.) Operational paranoia > suggests keeping it at least cleaned up frequently, if you're going to > bother to have /home as a dmcrypt

Re: [DNG] some ASCII issues

Didier Kryn [2017-06-28 19:38]: > 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. But if you encrypt anything at all, isn't it easier to

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On 06/28/2017 06:23 PM, KatolaZ wrote: > On Wed, Jun 28, 2017 at 05:38:16PM -0400, zap wrote: > > [cut] > >> Oh the irony... >> >> To those on this list who are Christians or some other religious group... >> >> ;) anyways though thank you for helping me apply the fix on my system, >> I don't

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, 28 Jun 2017 15:59:05 -0400, Hendrik wrote in message <20170628195905.ga...@topoi.pooq.com>: > On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote: > > > > ..if apt-get upgrade fails you, aptitude upgrade might work and > > vice versa, they solve package conflicts differently.

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, 2017-06-28 at 17:38 -0400, zap wrote: > > ;)  anyways though thank you for helping me apply the fix on my > system, I don't know what would have happened one way or another, but > thank you. I downgraded successfully! And thank you for reporting this issue so it could be resolved so

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 05:38:16PM -0400, zap wrote: [cut] > > Oh the irony... > > To those on this list who are Christians or some other religious group... > > ;) anyways though thank you for helping me apply the fix on my system, > I don't know what would have happened one way or another,

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 11:53:52PM +0200, Antony Stone wrote: > On Wednesday 28 June 2017 at 23:38:16, zap wrote: > > > Regardless, I thank you for forking debian to remove systemd. I know > > little of it, I only know it is less secure and slower to boot/more > > resource intensive/slower

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wednesday 28 June 2017 at 23:38:16, zap wrote: > Regardless, I thank you for forking debian to remove systemd. I know > little of it, I only know it is less secure and slower to boot/more > resource intensive/slower download speed. but thanks I plan to donate to > your cause perhaps even

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On 06/28/2017 04:49 PM, KatolaZ wrote: > On Wed, Jun 28, 2017 at 01:45:55PM -0700, Bruce Perens wrote: >> On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote: >>> On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote: As far as I can tell at the moment, they might

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 01:45:55PM -0700, Bruce Perens wrote: > On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote: > > On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote: > > >> As far as I can tell at the moment, they might even require systemd. > > For those of

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 1:40 PM, KatolaZ wrote: > On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote: >> As far as I can tell at the moment, they might even require systemd. For those of you requiring ritual purification, I recommend this St. Ignutious video.

Re: [DNG] AMPROLLA GLITCH: ISSUE SOLVED -- PLEASE READ CAREFULLY

On Wed, Jun 28, 2017 at 04:32:26PM -0400, zap wrote: [cut] > > In other words: > > > > 1) create the file /etc/apt/preferences/ascii-pin containing the > > following three lines: > How do you make a file there especially if preferences is either missing > or named differently? > > > aka,

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 03:59:05PM -0400, Hendrik Boom wrote: > On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote: > > > > ..if apt-get upgrade fails you, aptitude upgrade might work and > > vice versa, they solve package conflicts differently. > > Safely? See above. ;o) > > That's

Re: [DNG] AMPROLLA GLITCH: ISSUE SOLVED -- PLEASE READ CAREFULLY

On 06/28/2017 12:04 PM, KatolaZ wrote: > Hi All, > > as you know, there was a glitch in amprolla this morning, and by > mistake ascii got merged on Debian Buster, the new Debian testing > branch. This means that the users who apt-get updated/upgraded (or > used aptitute update/upgrade) in the

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

I try to update a local ascii repository and it gives me the following error: 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

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 07:58:13PM +0200, Arnt Karlsen wrote: > > ..if apt-get upgrade fails you, aptitude upgrade might work and > vice versa, they solve package conflicts differently. > Safely? See above. ;o) That's not the problem. aptitude and apt-get use the same repositories. The

Re: [DNG] some ASCII issues

Le 28/06/2017 à 20:33, Rick Moen a écrit : Quoting Didier Kryn (k...@in2p3.fr): 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. /home would be

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On 28/06/17 17:06, KatolaZ wrote: On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote: [cut] just wondered, Is aptitude upgrade safe? No, it was not safe. If you have upgraded your Devuan Ascii (testing) system in the last 24 hours, using whatever mean (apt-get, apt, aptitude, synaptic,

Re: [DNG] some ASCII issues

Quoting Didier Kryn (k...@in2p3.fr): > 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. /home would be where I keep anything that's sensitive.

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, 28 Jun 2017 17:06:18 +0100, KatolaZ wrote in message <20170628160618.gu14...@katolaz.homeunix.net>: > On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote: > > [cut] > > > > > just wondered, Is aptitude upgrade safe? > > > > No, it was not safe. If you have upgraded your Devuan Ascii

Re: [DNG] some ASCII issues

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.

[DNG] Amprolla replacement in RE: WARNING! DO NOT APT-GET

In an earlier post on DNG, it was implied that Amprolla was being considering being replaced (my impression). ' here is an article in regards to Debian's server platform being considered for replacement. https://lwn.net/Articles/724986/ ' FWIW - gary ___

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

Hello all, I'd like to get a few comments in to the devuan developers before a "fix" is decided upon. I'll also share the anecdote of how a separate problem in the devuan infrastructure indirectly saved me from falling victim to this incident: 1] IMO, the issue isn't really that devuan wasn't

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 10:50:07AM -0400, zap wrote: [cut] > > just wondered, Is aptitude upgrade safe? > No, it was not safe. If you have upgraded your Devuan Ascii (testing) system in the last 24 hours, using whatever mean (apt-get, apt, aptitude, synaptic, etc.) you might have erroneously

[DNG] AMPROLLA GLITCH: ISSUE SOLVED -- PLEASE READ CAREFULLY

Hi All, as you know, there was a glitch in amprolla this morning, and by mistake ascii got merged on Debian Buster, the new Debian testing branch. This means that the users who apt-get updated/upgraded (or used aptitute update/upgrade) in the last 24 hours might have gotten some packages from

Re: [DNG] some ASCII issues

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

Re: [DNG] some ASCII issues

On Mi, Jun 28, 2017 at 06:55:37 -0700, Rick Moen wrote: Yes, and this will not work with new-school methods like disc encryption because something needs to ask you for the password. What exactly about LUKS is incompatible with use of a kernel compiled to include all key drivers including those

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On 06/28/2017 08:11 AM, KatolaZ wrote: > On Wed, Jun 28, 2017 at 02:06:43PM +0200, para...@dyne.org wrote: >> On Wed, 28 Jun 2017, Svante Signell wrote: >> >>> On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote: Hi, Too late for me. Apt logged the following information:

Re: [DNG] Remote administation

Quoting Hendrik Boom (hend...@topoi.pooq.com): > IPMI is presuably the same protocol described as "The most dangerous > protocol you've never heard of"? > > http://www.itworld.com/article/2708437/security/ipmi--the-most-dangerous-protocol-you-ve-never-heard-of.html> > For that reason, IPMI

Re: [DNG] some ASCII issues

Quoting Stephan Seitz (stse+dev...@fsing.rootsland.net): > On Di, Jun 27, 2017 at 10:57:16 -0700, Rick Moen wrote: > >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.

Re: [DNG] some ASCII issues

On Di, Jun 27, 2017 at 10:57:16 -0700, Rick Moen wrote: 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. Yes, and this will not work with new-school methods like disc

Re: [DNG] some ASCII issues

Quoting k...@aspodata.se (k...@aspodata.se): > And that works when the root filesystem is on a device with fixed major/ > minor number, e.g. /dev/sda2 /dev/hda1, and even /dev/md1 for md > devices with the old (0.90) format superblock if they are auto-assebled. > It doesn't work for devices with

Re: [DNG] some ASCII issues

k...@aspodata.se writes: > And that works when the root filesystem is on a device with fixed > major/ minor number [...] It doesn't work for devices with dynamic > device numbers. That used to be true, but it's improved quite a bit in recent years. Since 2.6.37 (2011), the kernel lets you

Re: [DNG] some ASCII issues

Rick Moen: > 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

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, Jun 28, 2017 at 02:06:43PM +0200, para...@dyne.org wrote: > On Wed, 28 Jun 2017, Svante Signell wrote: > > > On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote: > > > Hi, > > > > > > Too late for me. Apt logged the following information: > > > > > > Start-Date: 2017-06-25  18:47:08

[DNG] Remote administation

On Wed, Jun 28, 2017 at 12:32:01AM -0500, John Morris wrote: > On Sat, 2017-06-24 at 11:04 -0500, Don Wright wrote: > > > Just teleport into the datacenter on the other side of the planet, or the > > office building where your after-hours key card doesn't work because all > > cards were cancelled

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, 28 Jun 2017, Svante Signell wrote: > On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote: > > Hi, > > > > Too late for me. Apt logged the following information: > > > > Start-Date: 2017-06-25  18:47:08 > > Commandline: apt-get upgrade > > Upgrade: libpam0g:amd64 (1.1.8-3.5,

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

On Wed, 2017-06-28 at 13:28 +0200, Edward Bartolo wrote: > Hi, > > Too late for me. Apt logged the following information: > > Start-Date: 2017-06-25  18:47:08 > Commandline: apt-get upgrade > Upgrade: libpam0g:amd64 (1.1.8-3.5, 1.1.8-3.6), debconf:amd64 (1.5.60, > 1.5.61),... > [ a very long

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

The ascii repositories are now offline. We will proceed sorting the issue and keeping you informed. I hope everyone understands this is the first time we experience a switch of Debian releases and that it is well part of our 'testing' phase to adjust amprolla's behaviour to behave on these

Re: [DNG] WARNING! DO NOT APT-GET UPDATE/UPGRADE ON ASCII

Hi, Too late for me. Apt logged the following information: Start-Date: 2017-06-25 18:47:08 Commandline: apt-get upgrade Upgrade: libpam0g:amd64 (1.1.8-3.5, 1.1.8-3.6), debconf:amd64 (1.5.60, 1.5.61),... [ a very long list of packages ] End-Date: 2017-06-25 18:55:08 -- If you can't explain it

[DNG] Warning: Don't upgrade ASCII until merged is corrected

Hi, Happily upgrading ASCII with deb http://auto.mirror.devuan.org/merged ascii  main contrib non-free in /etc/apt/sources.list I suddenly realized that the (many) upgraded packages come from Debian/Testing. Please fix merged ASAP to point at Debian/Stretch. Or is the idea to base the ASCII

Re: [DNG] grsecurity ripoff by Google, with Linus' approval WAS: I have a question about libsystemd0 in devuan ascii,

On Tue, 27 Jun 2017 18:37:31 -0700, Bruce wrote in message

[DNG] About /usr merge and Initramfs [was Re: some ASCII issues]

Le 28/06/2017 à 08:11, Didier Kryn a écrit : Le 28/06/2017 à 07:47, John Morris a écrit : On Sat, 2017-06-24 at 11:08 +0200, Didier Kryn wrote: Anyway I think there's a simple method to live without the initramfs. Everything which is done from initramfs could be done the same way from a

Re: [DNG] some ASCII issues

Le 28/06/2017 à 07:47, John Morris a écrit : On Sat, 2017-06-24 at 11:08 +0200, Didier Kryn wrote: Anyway I think there's a simple method to live without the initramfs. Everything which is done from initramfs could be done the same way from a disk partition, which might make it easier to