Re: [Dng] Wheezy

Thank you, Hendrik. That is what I assumed you would find. I’m not overreacting per se. I freely admit, I’ve not looked at the code to see how well it functions independently. I also do not know for certain that it is a recent addition. I do not recall seeing it in previous Wheezy releases a

Re: [Dng] Wheezy

On Mon, Jan 05, 2015 at 09:15:11PM +, t.j.duch...@gmail.com wrote: > > >Then I have no idea about default installation (you can probably look at > >package dependencies to figure it out). But from Debian's current POV, it is > >probably considered an improvement to add systemd components and m

Re: [Dng] Wheezy

On Mon, Jan 05, 2015 at 08:52:06PM +, t.j.duch...@gmail.com wrote: > > > > > > >IIRC, Wheezy is known to have systemd packages but they aren't (or > >shouldn't be?) installed by default, probably as an early > >preparation for full systemd in Jessie. I've been running a wheezy server fo

Re: [Dng] Wheezy

>I think it is not so much a problem of the kernel, which as you > point out >can be compiled to suit and by its nature is >backwards compatible in most >things other than size, but rather >other pieces, a cascade of "what next?" >dependencies and the >horror of horrors proprietary bi

Re: [Dng] Wheezy

On 05/01/15 05:32 PM, t.j.duch...@gmail.com wrote: You can get around that. Systemd is not a kernel requirement. You can easily get around said problems by compiling your own kernel rather than using the Debian packages - which clearly have dependency issues related to systemd. Hi, I thi

Re: [Dng] Wheezy

Hi, Clarke! >It was a bit of a wake up call for me as it made me realize that for >more recent hardware continued use of Wheezy to avoid systemd may not be >as simple as it first seems. You can get around that. Systemd is not a kernel requirement. You can easily get around said problems b

Re: [Dng] vdev update and design document

Am 05.01.2015 um 07:21 schrieb Martijn Dekkers: There are several areas where there are significant legal requirements around disallowing the concept of a root / UID 0 user to have overriding access. Please be advised that SELinux was built by the NSA *specifically* to be able to meet these legal

Re: [Dng] Wheezy

I recently unintentionally installed systemd and a bunch of the related tentacles. It was a new Wheezy install w/XFCE from a DVD I figured I'd be safe from systemd with wheezy, but for some hardware (AMD A10-7850K Kaveri) I needed a newer kernel and so I enabled "backports". I obviously was

Re: [Dng] Wheezy

>Then I have no idea about default installation (you can probably look at >package dependencies to figure it out). But from Debian's current POV, it is >probably considered an improvement to add systemd components and more >recent versios of __ that use them, even if PID1 is still sysvinit. Af

Re: [Dng] Wheezy

On 2015-01-05 wrote: > > My concern is that Debian is backporting code to the Wheezy release that > > they shouldn’t be installing by default > > I should say “might be” as I am not sure and have not looked at the code > personally. I am merely concerned. > Then I have no idea about default

Re: [Dng] Wheezy

> My concern is that Debian is backporting code to the Wheezy release that > they shouldn’t be installing by default I should say “might be” as I am not sure and have not looked at the code personally. I am merely concerned. From: t.j.duch...@gmail.com Sent: ‎Monday‎, ‎January‎ ‎5‎,

Re: [Dng] Wheezy

>IIRC, Wheezy is known to have systemd packages but they aren't (or shouldn't >be?) installed by default, probably as an early preparation for full systemd in >Jessie. Yes, I know. As I’ve said before I have no problem with systemd, except on mission critical servers. My concern is tha

Re: [Dng] Wheezy

https://packages.debian.org/wheezy/systemd --- fr33domlover GPG key ID: 63E5E57D (size: 4096) GPG key fingerprint: 6FEE C222 7323 EF85 A49D 5487 5252 C5C8 63E5 E57D signature.asc Description: PGP signature _

Re: [Dng] Wheezy

On 2015-01-05 "T.J. Duchene" wrote: > I was installing wheezy this morning on a second hard drive and I noted > that systemd named packages have crept their way into the wheezy default > installs. I'm presuming that they are compatibly named or part of a > systemd/system 5 shim since systemd is

[Dng] Wheezy

I was installing wheezy this morning on a second hard drive and I noted that systemd named packages have crept their way into the wheezy default installs. I'm presuming that they are compatibly named or part of a systemd/system 5 shim since systemd is not actually running. I'm guessing they did t

Re: [Dng] vdev update and design document

On Mon, 5 Jan 2015, Hendrik Boom wrote: > Even on VMS the administrator coculd change the permissions on such > file. So it wasn't really a serious security measure. I don't know VMS, but I know how this feature is intende to be used in Windows since NT: Admin has to take ownership of the file

Re: [Dng] vdev update and design document

On Sun, Jan 04, 2015 at 06:40:10PM -0500, Jude Nelson wrote: > Hi Hendrik, > > > In VAX/VMS there was a feature that could in theory be useful, > > though I've never seen it actually used. Fila permissions could > > forbid the root user from reading the file. This might be useful > > for dire se

[Dng] devuan security wishlist item

Talking about security and ttys and login: I would like Devuan to have a clear documentation and good defaults for the Secure Attention Key (SAK). E.g. that any user at the console can expect to do Ctrl-Alt-SysRq-K to work. Too few people know that this even exists in Linux. Frits. ___