On 09.01.18 15:04, Christian Groessler wrote:
> I just edited the password file directly, "vipw" and "vipw -s", and renamed
> the pi user.
When doing that, there is merit in running pwck before any powerdown/reboot,
as any illegality in a line stopped processing of all following when I
last tried
On 01/09/18 16:01, Roberto C. Sánchez wrote:
Don't forget about occurrences of 'pi' in the group files (use 'vigr'
and 'vigr -s' to catch those).
Yep. Forgot to mention that.
regards,
chris
On Tue, Jan 09, 2018 at 03:04:03PM +0100, Christian Groessler wrote:
> On 01/09/18 04:49, Jason wrote:
> > > This I'd guess is important, if you have several users. I don't, except
> > > for amanda and nut, and thats only on this machine. All the rest have
> > > one user, me, known under various al
On 01/09/18 04:49, Jason wrote:
This I'd guess is important, if you have several users. I don't, except
for amanda and nut, and thats only on this machine. All the rest have
one user, me, known under various aliases because the idiot installer is
now set to give the first user the machines name l
On Sun, Dec 10, 2017 at 10:17:12PM -0500, Gene Heskett wrote:
> On Sunday 10 December 2017 19:02:49 David Wright wrote:
>
> > On Sun 10 Dec 2017 at 16:43:02 (-0500), Gene Heskett wrote:
[...]
> >
> This I'd guess is important, if you have several users. I don't, except
> for amanda and nut, and
Gene writes:
> That is probably enough if the user is smart enough to know how to
> check, but if I pull a new iso of the install image today, will it be
> there for reading before I click install when booted to that live iso
> with no network access?
If your new ISO is the latest point release it
On Friday 15 December 2017 07:11:04 Christian Seiler wrote:
> Am 2017-12-08 21:31, schrieb Gene Heskett:
> > On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote:
> >> No objection there, and I agree that the release notes should
> >> probably have covered the policy changes. That ship has n
Am 2017-12-08 21:31, schrieb Gene Heskett:
On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote:
No objection there, and I agree that the release notes should probably
have covered the policy changes. That ship has now sailed
unfortunately.
So now, no effort will ever be made to fix the
On Mon 11 Dec 2017 at 09:16:35 (-0500), rhkra...@gmail.com wrote:
> From the Wikipedia article on "Magnetic storage":
>
> https://en.wikipedia.org/wiki/Magnetic_storage#Design
>
> "For reliable storage of data, the recording material needs to resist self-
> demagnetisation, which occurs when the
Thanks!
On Monday, December 11, 2017 10:04:09 AM Joe wrote:
> On Mon, 11 Dec 2017 09:16:35 -0500
>
> rhkra...@gmail.com wrote:
> > (Did hard disks ever use iron oxide?)
>
> The rigid platters of IBM cartridges and packs (the things you see in
> computer rooms in films) did have brown oxide coati
On Monday, December 11, 2017 09:41:45 AM Darac Marjal wrote:
> On Mon, Dec 11, 2017 at 09:16:35AM -0500, rhkra...@gmail.com wrote:
> > From the Wikipedia article on "Magnetic storage":
> > https://en.wikipedia.org/wiki/Magnetic_storage#Design
> > "For reliable storage of data, the recording
On Mon 11 Dec 2017 at 11:32:54 (+), Eduardo M KALINOWSKI wrote:
> On dom, 10 dez 2017, tomas wrote:
> >To put it differently, Debian tends to package docs separately, because
> >you might want to set up a storage-constrained system where you don't
> >want that extra stuff. To me, that makes sen
On Mon, 11 Dec 2017 09:16:35 -0500
rhkra...@gmail.com wrote:
>
> (Did hard disks ever use iron oxide?)
>
The rigid platters of IBM cartridges and packs (the things you see in
computer rooms in films) did have brown oxide coatings. The surface of
each 12 inch platter side stored a magnificent 2
On Mon, Dec 11, 2017 at 09:16:35AM -0500, rhkra...@gmail.com wrote:
On Monday, December 11, 2017 01:12:41 AM Gene Heskett wrote:
> There are instructions for making the pi's boot from rust, but its a one
> way as its said to be an otp rom in charge of that, however when I try
> to set
On Monday, December 11, 2017 01:12:41 AM Gene Heskett wrote:
> There are instructions for making the pi's boot from rust, but its a one
> way as its said to be an otp rom in charge of that, however when I try
> to set that bit, its write protected even for root. In all 3 of the pi's
> I bought. An
On Sun 10 Dec 2017 at 15:52:30 +0100, Dejan Jocic wrote:
> On 10-12-17, Joe wrote:
> >
> > I thought you might find more examples helpful. The man page says that
> > policies come from /etc/polkit-1 and /var/lib/polkit-1, but on my
> > system the /var/lib location is almost empty, and there's a l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 11, 2017 at 07:19:20AM -0500, Gene Heskett wrote:
> On Monday 11 December 2017 06:02:46 Brian wrote:
>
> > On Sun 10 Dec 2017 at 18:25:26 -0500, Gene Heskett wrote:
> > > apt can't do a show --uninstalled on the stretch machine, and the
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, Dec 11, 2017 at 11:32:54AM +, Eduardo M KALINOWSKI wrote:
[...]
> It also helps the archives, since there can be one
> architecture-independent .deb with the docs, and then smaller
> architecture-dependent .deb's with the binaries for each
On Monday 11 December 2017 06:02:46 Brian wrote:
> On Sun 10 Dec 2017 at 18:25:26 -0500, Gene Heskett wrote:
> > apt can't do a show --uninstalled on the stretch machine, and the
> > man page isn't offering much either, so to see whats available, I
> > have to go to its own keyboard and run synapt
On dom, 10 dez 2017, tomas wrote:
To put it differently, Debian tends to package docs separately, because
you might want to set up a storage-constrained system where you don't
want that extra stuff. To me, that makes sense.
It also helps the archives, since there can be one
architecture-indep
On Sun 10 Dec 2017 at 18:25:26 -0500, Gene Heskett wrote:
> apt can't do a show --uninstalled on the stretch machine, and the man
> page isn't offering much either, so to see whats available, I have to go
> to its own keyboard and run synaptic-pkexec.
The apt man page isn't unhelpful. For avail
On Sunday 10 December 2017 23:50:13 David Wright wrote:
> On Sun 10 Dec 2017 at 22:17:12 (-0500), Gene Heskett wrote:
> > On Sunday 10 December 2017 19:02:49 David Wright wrote:
> > > On Sun 10 Dec 2017 at 16:43:02 (-0500), Gene Heskett wrote:
> > > > On Sunday 10 December 2017 14:12:09 David Wrig
On Sun 10 Dec 2017 at 22:17:12 (-0500), Gene Heskett wrote:
> On Sunday 10 December 2017 19:02:49 David Wright wrote:
>
> > On Sun 10 Dec 2017 at 16:43:02 (-0500), Gene Heskett wrote:
> > > On Sunday 10 December 2017 14:12:09 David Wright wrote:
> > > > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene
On Sunday 10 December 2017 19:02:49 David Wright wrote:
> On Sun 10 Dec 2017 at 16:43:02 (-0500), Gene Heskett wrote:
> > On Sunday 10 December 2017 14:12:09 David Wright wrote:
> > > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> > > > For something that can be such a pita, not ins
On Sun 10 Dec 2017 at 16:43:02 (-0500), Gene Heskett wrote:
> On Sunday 10 December 2017 14:12:09 David Wright wrote:
>
> > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> > > For something that can be such a pita, not installing the docs
> > > doesn't seem like my error, they should
On Sunday 10 December 2017 17:45:36 Brian wrote:
> On Sun 10 Dec 2017 at 16:47:05 -0500, Gene Heskett wrote:
> > On Sunday 10 December 2017 15:05:04 Brian wrote:
> > > On Sun 10 Dec 2017 at 13:12:09 -0600, David Wright wrote:
> > > > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> >
On Sun 10 Dec 2017 at 16:47:05 -0500, Gene Heskett wrote:
> On Sunday 10 December 2017 15:05:04 Brian wrote:
>
> > On Sun 10 Dec 2017 at 13:12:09 -0600, David Wright wrote:
> > > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> > > > For something that can be such a pita, not install
On Sunday 10 December 2017 15:05:04 Brian wrote:
> On Sun 10 Dec 2017 at 13:12:09 -0600, David Wright wrote:
> > On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> > > For something that can be such a pita, not installing the docs
> > > doesn't seem like my error, they should have been
On Sunday 10 December 2017 14:12:09 David Wright wrote:
> On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> > For something that can be such a pita, not installing the docs
> > doesn't seem like my error, they should have been part of the
> > install. IMO.
>
> That's ridiculous. I don'
On Sat 09 Dec 2017 at 18:36:46 -0500, The Wanderer wrote:
> On 2017-12-09 at 09:10, Brian wrote:
>
> > The Terms and Conditions of installing a Debian package include (as
> > I'm sure you are aware) accepting the Depends: and Recomends: lines.
> > What is in these lines can be accepted or rejec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Dec 10, 2017 at 01:12:09PM -0600, David Wright wrote:
> On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
>
> > For something that can be such a pita, not installing the docs doesn't
> > seem like my error, they should have been par
On Sun 10 Dec 2017 at 13:12:09 -0600, David Wright wrote:
> On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
>
> > For something that can be such a pita, not installing the docs doesn't
> > seem like my error, they should have been part of the install. IMO.
>
> That's ridiculous. I d
On Sun 10 Dec 2017 at 00:38:12 (-0800), Jimmy Johnson wrote:
> On 12/09/2017 08:23 AM, David Wright wrote:
> >On Fri 08 Dec 2017 at 18:30:08 (-0800), Jimmy Johnson wrote:
> >>On 12/07/2017 02:31 AM, Jonathan Dowland wrote:
> >>>On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
> I'm running
On Sun 10 Dec 2017 at 10:42:53 (-0500), Gene Heskett wrote:
> For something that can be such a pita, not installing the docs doesn't
> seem like my error, they should have been part of the install. IMO.
That's ridiculous. I don't want all the docs on all the installations.
I only install docs on
On Sunday 10 December 2017 05:33:17 to...@tuxteam.de wrote:
> On Sat, Dec 09, 2017 at 11:29:58AM -0500, Gene Heskett wrote:
> > Thats another very sore point. Where are the man pages? Its
> > installed on 6, maybe 7 machines here, with zero docs.
>
> Not a user of policykit here -- I don't like it
On 10-12-17, Joe wrote:
> On Sun, 10 Dec 2017 11:02:45 +0100
> Dejan Jocic wrote:
>
> > On 10-12-17, Joe wrote:
> > > On Sun, 10 Dec 2017 00:13:59 +0100
> > > Dejan Jocic wrote:
> > >
> > >
> > > >
> > > > Man page for pklocalauthority is bit more helpful, but far from
> > > > self explanat
On Sun, 10 Dec 2017 11:02:45 +0100
Dejan Jocic wrote:
> On 10-12-17, Joe wrote:
> > On Sun, 10 Dec 2017 00:13:59 +0100
> > Dejan Jocic wrote:
> >
> >
> > >
> > > Man page for pklocalauthority is bit more helpful, but far from
> > > self explanatory.
> >
> > And not updated for Debian.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Dec 09, 2017 at 11:29:58AM -0500, Gene Heskett wrote:
> Thats another very sore point. Where are the man pages? Its installed on
> 6, maybe 7 machines here, with zero docs.
Not a user of policykit here -- I don't like it (as may be deduced
fr
On 10-12-17, Joe wrote:
> On Sun, 10 Dec 2017 00:13:59 +0100
> Dejan Jocic wrote:
>
>
> >
> > Man page for pklocalauthority is bit more helpful, but far from self
> > explanatory.
>
> And not updated for Debian.
>
> > In its examples section, it provides some insight about
> > writing .pkla
On Sun, 10 Dec 2017 00:13:59 +0100
Dejan Jocic wrote:
>
> Man page for pklocalauthority is bit more helpful, but far from self
> explanatory.
And not updated for Debian.
> In its examples section, it provides some insight about
> writing .pkla files, but it does not show all possible options
On 12/09/2017 08:23 AM, David Wright wrote:
On Fri 08 Dec 2017 at 18:30:08 (-0800), Jimmy Johnson wrote:
On 12/07/2017 02:31 AM, Jonathan Dowland wrote:
On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
I'm running Jessie (with systemd running but booting with sysvinit) and
trying to execu
On 2017-12-09 at 09:10, Brian wrote:
> The Terms and Conditions of installing a Debian package include (as
> I'm sure you are aware) accepting the Depends: and Recomends: lines.
> What is in these lines can be accepted or rejected and, in the case
> of Recommends:, adjusted to suit your needs.
On 09-12-17, Brian wrote:
> On Sat 09 Dec 2017 at 20:07:17 +0100, Dejan Jocic wrote:
>
> > On 09-12-17, Jonathan Dowland wrote:
> > > On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> > > > Consistencey can be achieved by not installing policykit. The OP
> > > > appears to have chosen the wrong ta
On 10/12/17 04:45, Tom Furie wrote:
On Sat, Dec 09, 2017 at 10:17:45AM -0500, Ric Moore wrote:
On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote:
Something I did *not* understand when I saw it in operation was why
a password was needed at the terminal but not from within the GUI's
"Applications >
On Sat 09 Dec 2017 at 20:07:17 +0100, Dejan Jocic wrote:
> On 09-12-17, Jonathan Dowland wrote:
> > On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> > > Consistencey can be achieved by not installing policykit. The OP
> > > appears to have chosen the wrong target.Consistencey can be achieved > by
On Saturday 09 December 2017 12:01:59 David Wright wrote:
> On Sat 09 Dec 2017 at 11:29:58 (-0500), Gene Heskett wrote:
> > On Saturday 09 December 2017 05:12:16 Joe wrote:
> > > On Fri, 8 Dec 2017 23:56:44 +
> > >
> > > Brian wrote:
> > > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
>
On Sat, Dec 09, 2017 at 06:20:01PM +, Jonathan Dowland wrote:
> On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> > Consistencey can be achieved by not installing policykit. The OP
> > appears to have chosen the wrong target.Consistencey can be achieved > by
> > not installing policykit.
>
>
On Sat 09 Dec 2017 at 18:20:01 +, Jonathan Dowland wrote:
> On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> > Consistencey can be achieved by not installing policykit. The OP
> > appears to have chosen the wrong target.Consistencey can be achieved > by
> > not installing policykit.
>
> As
On 09-12-17, Jonathan Dowland wrote:
> On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> > Consistencey can be achieved by not installing policykit. The OP
> > appears to have chosen the wrong target.Consistencey can be achieved > by
> > not installing policykit.
>
> As Michael pointed out in [1]
On Sat, 2017-12-09 at 10:00 +, Brian wrote:
> Consistencey can be achieved by not installing policykit. The OP
> appears to have chosen the wrong target.Consistencey can be achieved > by not
> installing policykit.
As Michael pointed out in [1], that's not the case; prior to polkit,
there was
On Sat 09 Dec 2017 at 11:29:58 (-0500), Gene Heskett wrote:
> On Saturday 09 December 2017 05:12:16 Joe wrote:
>
> > On Fri, 8 Dec 2017 23:56:44 +
> >
> > Brian wrote:
> > > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
> > > > On Fri, 8 Dec 2017 17:12:18 -0500
> > > >
> > > > Cindy-Sue Ca
On Sat 09 Dec 2017 at 10:17:45 (-0500), Ric Moore wrote:
> On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote:
> Something I did *not* understand when I saw it in
> >operation was why a password was needed at the terminal but not from
> >within the GUI's "Applications > Log Out" menu path.
>
> Thank
On Saturday 09 December 2017 05:12:16 Joe wrote:
> On Fri, 8 Dec 2017 23:56:44 +
>
> Brian wrote:
> > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
> > > On Fri, 8 Dec 2017 17:12:18 -0500
> > >
> > > Cindy-Sue Causey wrote:
> > > > I do remember having to give a password, but I don't reme
On Fri 08 Dec 2017 at 18:30:08 (-0800), Jimmy Johnson wrote:
> On 12/07/2017 02:31 AM, Jonathan Dowland wrote:
> >On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
> >>I'm running Jessie (with systemd running but booting with sysvinit) and
> >>trying to execute halt/poweroff/reboot/shutdown fro
On Sat, Dec 09, 2017 at 10:17:45AM -0500, Ric Moore wrote:
> On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote:
> > Something I did *not* understand when I saw it in operation was why
> > a password was needed at the terminal but not from within the GUI's
> > "Applications > Log Out" menu path.
>
> T
On 12/08/2017 05:12 PM, Cindy-Sue Causey wrote:
Something I did *not* understand when I saw it in
operation was why a password was needed at the terminal but not from
within the GUI's "Applications > Log Out" menu path.
Thank you Cindy, now I don't have to point out the obvious! :) Ric
--
My
On Sat 09 Dec 2017 at 10:12:16 +, Joe wrote:
> On Fri, 8 Dec 2017 23:56:44 +
> Brian wrote:
>
> > On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
> >
> > > On Fri, 8 Dec 2017 17:12:18 -0500
> > > Cindy-Sue Causey wrote:
> > >
> > > >
> > > > I do remember having to give a password
On Fri, 8 Dec 2017 23:56:44 +
Brian wrote:
> On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
>
> > On Fri, 8 Dec 2017 17:12:18 -0500
> > Cindy-Sue Causey wrote:
> >
> > >
> > > I do remember having to give a password, but I don't remember how
> > > long ago now. And I have too much ope
On Sat 09 Dec 2017 at 07:52:56 +, Jonathan Dowland wrote:
> On Fri, Dec 08, 2017 at 07:57:03PM +, Brian wrote:
> > > That's a good point.
> >
> > Not really. systemd doesn't stop providing a single place to define a
> > consistent policy because a set of users do not use it.
>
> That's n
On Sat, 09 Dec 2017 01:46:59 +
Mark Fletcher wrote:
> The OP has never been seen again since the original post. Just
> sayin’...
>
>
Because he accidentally discovered a new feature, thought it was a bug,
and was immediately corrected. End of story.
We've been discussing the 'accidentally'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 08, 2017 at 05:04:51PM -0600, John Hasler wrote:
> tomas writes:
> > Not a fan of systemd here (have outed myself this way clearly enough,
> > I think), but systemd is pretty well documented, for sure.
>
> Is the Debian default configurati
On Sat, Dec 09, 2017 at 01:30:17AM +, Glenn English wrote:
Even if there's an error in the release note? Less than optimal way to
run a train.
Errors and omissions are different things. I'm not responsible for
release notes but I suspect if there was something that was glaringly
false, it *
On Fri, Dec 08, 2017 at 03:31:54PM -0500, Gene Heskett wrote:
On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote:
No objection there, and I agree that the release notes should probably
have covered the policy changes. That ship has now sailed
unfortunately.
So now, no effort will ever
On Fri, Dec 08, 2017 at 07:57:03PM +, Brian wrote:
That's a good point.
Not really. systemd doesn't stop providing a single place to define a
consistent policy because a set of users do not use it.
That's not the point I thought was good: the point is, in Debian,
systemd is optional. As a
Glenn writes:
> Even if there's an error in the release note? Less than optimal way to
> run a train.
You can't retroactively fix the release notes: they are part of the
already released release. All you can do is publish an errata and
correct the error in the next point release.
--
John Hasler
On 12/07/2017 02:31 AM, Jonathan Dowland wrote:
On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
I'm running Jessie (with systemd running but booting with sysvinit) and
trying to execute halt/poweroff/reboot/shutdown from a terminal without
root privileges gives an error saying I must be su
The OP has never been seen again since the original post. Just sayin’...
On Sat, Dec 9, 2017 at 9:39 Menelaos Maglis wrote:
> Joe writes:
>
> > I think there's a case for asking which way to set it during an expert
> > install or during the upgrade that reversed the default setting.
>
> I think
On Fri, Dec 8, 2017 at 9:07 PM, John Hasler wrote:
> Gene Heskitt writes:
>> So now, no effort will ever be made to fix the man pages. Hell of a
>> way to run a train.
>
> That doesn't follow. The release note are specific to the release and
> thus obviously cannot be fixed.
Even if there's an
Joe writes:
> I think there's a case for asking which way to set it during an expert
> install or during the upgrade that reversed the default setting.
I think it is policy not to touch locally changed configuration during
upgrades. Usually packages ask what to do and/or provide information
when
On Fri 08 Dec 2017 at 23:06:00 +, Joe wrote:
> On Fri, 8 Dec 2017 17:12:18 -0500
> Cindy-Sue Causey wrote:
>
> >
> > I do remember having to give a password, but I don't remember how long
> > ago now. And I have too much open right now to test drive whether mine
> > does it or not these day
tomas writes:
> Not a fan of systemd here (have outed myself this way clearly enough,
> I think), but systemd is pretty well documented, for sure.
Is the Debian default configuration of Systemd also well documented?
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Fri, 8 Dec 2017 17:12:18 -0500
Cindy-Sue Causey wrote:
>
> I do remember having to give a password, but I don't remember how long
> ago now. And I have too much open right now to test drive whether mine
> does it or not these days.. :)
>
As I did the other day. I've tried it now (up-to-date
On 12/7/17, Dave Sherohman wrote:
> On Thu, Dec 07, 2017 at 11:26:45AM +1300, Ben Caradoc-Davies wrote:
>> Special privileges have been granted to console users for as long as I
>> can
>> remember, long before systemd, because they have physical access to the
>> machine. Console users typically ar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 08, 2017 at 03:29:20PM -0500, Gene Heskett wrote:
[...]
> Which until now I have never seen its supposed advantages touted. Maybe I
> don't subscribe to the right lists?
Hey, to each her/his own...
> rant mode on!
>
> Couldn't a lot o
Gene Heskitt writes:
> So now, no effort will ever be made to fix the man pages. Hell of a
> way to run a train.
That doesn't follow. The release note are specific to the release and
thus obviously cannot be fixed. The man pages can be fixed in any
future release of the subject packages. File b
On Friday 08 December 2017 14:26:41 Jonathan Dowland wrote:
> On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote:
> >>> > Basically, it was a completely inconsistent mess before systemd.
> >>> > Now you at least have a central place where you can configure
> >>> > your system behaviou
On Friday 08 December 2017 13:09:06 Menelaos Maglis wrote:
> >> > Basically, it was a completely inconsistent mess before systemd.
> >> > Now you at least have a central place where you can configure
> >> > your system behaviour.
> >
> > In the past, we had *no consistency*: inittab had one thing,
to...@tuxteam.de wrote:
> Now watch all the old skoolers dashing out of their little caves and
> waving their fists at something which could be read as a provocation
> (I'm myself one of those, just look a bit upthread :)
>
It is not about old or new, but about known and unknown. Unkown exposes
On Fri 08 Dec 2017 at 19:26:41 +, Jonathan Dowland wrote:
> On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote:
> > > > > Basically, it was a completely inconsistent mess before systemd.
> > > > > Now you at least have a central place where you can configure your
> > > > > system
On Fri, Dec 08, 2017 at 07:09:06PM +0100, Menelaos Maglis wrote:
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
In the past, we had *no consistency*: inittab had one thing, display
manage
Roberto C. Sánchez wrote:
> That is really the problem that I have with this while issue that was
> brought up. I get that it is a "sensible" default to allow users on the
> console (TTY or via DM) permission to reboot the machine. However, when
> an admin has configured the system to disallow t
>> > Basically, it was a completely inconsistent mess before systemd.
>> > Now you at least have a central place where you can configure your
>> > system behaviour.
> In the past, we had *no consistency*: inittab had one thing, display
> managers another, ACPI scripts another...if you wanted a spec
>> > Basically, it was a completely inconsistent mess before systemd.
>> > Now you at least have a central place where you can configure your
>> > system behaviour.
> In the past, we had *no consistency*: inittab had one thing, display
> managers another, ACPI scripts another...if you wanted a spec
On 2017-12-08, Jonathan Dowland wrote:
> On Fri, 2017-12-08 at 12:17 +0100, deloptes wrote:
>> Michael Biebl wrote:
>>
>> > Basically, it was a completely inconsistent mess before systemd.
>> > Now you at least have a central place where you can configure your
>> > system behaviour.
>>
>> This i
On Fri, 2017-12-08 at 12:17 +0100, deloptes wrote:
> Michael Biebl wrote:
>
> > Basically, it was a completely inconsistent mess before systemd.
> > Now you at least have a central place where you can configure your
> > system behaviour.
>
> This is your opinion - if you can not understand the "m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 08, 2017 at 12:17:16PM +0100, deloptes wrote:
> Michael Biebl wrote:
>
> > Basically, it was a completely inconsistent mess before systemd.
[...]
> This is your opinion - if you can not understand the "mess" it is a mess.
> For most o
On Fri, Dec 08, 2017 at 10:17:36AM +0100, Menelaos Maglis wrote:
>
> It is an improvement to have a consistent (central) way to configure
> this behavior.
>
> It is probably a "good thing" to allow users with physical access to
> reboot/shutdown a desktop/laptop system.
>
> It is probably not a
Michael Biebl wrote:
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
This is your opinion - if you can not understand the "mess" it is a mess.
For most of us who dislike systemd your same s
>>> I wonder how can such a severe bug make it into a Debian stable
>>> distribution? And is this just an insane default setting on Debian's
>>> side or is it yet another instance of brain-dead systemd behavior?
>>
>> Maybe I am just a brain-dead loony, but personally I prefer to be able to
>> sh
On Thu, Dec 07, 2017 at 09:37:25AM -0500, Roberto C. Sánchez wrote:
> On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
> >
> > I no longer have any non-systemd machines handy to verify this on, but
> > my memory is that I have *always* been able to use halt/poweroff/reboot
> > comma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Dec 07, 2017 at 08:03:47PM +0100, Michael Biebl wrote:
[...]
> Basically, it was a completely inconsistent mess before systemd.
> Now you at least have a central place where you can configure your
> system behaviour.
Hey, I'm "before systemd
Am 07.12.2017 um 15:37 schrieb Roberto C. Sánchez:
> On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
>>
>> I no longer have any non-systemd machines handy to verify this on, but
>> my memory is that I have *always* been able to use halt/poweroff/reboot
>> commands from the console w
On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
>
> I no longer have any non-systemd machines handy to verify this on, but
> my memory is that I have *always* been able to use halt/poweroff/reboot
> commands from the console without requiring sudo or entering a password,
> and I've
On Thu, Dec 07, 2017 at 10:02:56AM +, Tixy wrote:
I'm running Jessie (with systemd running but booting with sysvinit) and
trying to execute halt/poweroff/reboot/shutdown from a terminal without
root privileges gives an error saying I must be superuser. Which has
always been my experience in 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Dec 07, 2017 at 03:03:44AM -0600, Dave Sherohman wrote:
> On Thu, Dec 07, 2017 at 11:26:45AM +1300, Ben Caradoc-Davies wrote:
> > Special privileges have been granted to console users for as long as I can
> > remember, long before systemd, beca
On Thu, 2017-12-07 at 03:03 -0600, Dave Sherohman wrote:
>
> I no longer have any non-systemd machines handy to verify this on, but
> my memory is that I have *always* been able to use halt/poweroff/reboot
> commands from the console without requiring sudo or entering a password,
> and I've been u
On Thu, Dec 07, 2017 at 11:26:45AM +1300, Ben Caradoc-Davies wrote:
> Special privileges have been granted to console users for as long as I can
> remember, long before systemd, because they have physical access to the
> machine. Console users typically are also permitted to mount, unmount, and
> e
On Wed, 6 Dec 2017 17:35:18 -0500
Michael Stone wrote:
> On Wed, Dec 06, 2017 at 10:52:17PM +0100, Urs Thuermann wrote:
> >Yesterday, my 10 years old son logged into my laptop running Debian
> >jessie using his account, and curiously asked if he is allowed to try
> >the /sbin/reboot command. Kno
On יום רביעי, 6 בדצמבר 2017 22:52:17 IST Urs Thuermann wrote:
> Yesterday, my 10 years old son logged into my laptop running Debian
> jessie using his account, and curiously asked if he is allowed to try
> the /sbin/reboot command. Knowing I have a Linux system as opposed to
> some crappy Win mach
On Wednesday, 6 Dec 2017 at 22:52, Urs Thuermann wrote:
> Yesterday, my 10 years old son logged into my laptop running Debian
> jessie using his account, and curiously asked if he is allowed to try
> the /sbin/reboot command.
Security issues etc. aside, I love the fact that your 10 year old is
as
1 - 100 of 120 matches
Mail list logo
