On Tue, Oct 21, 2014 at 11:47:51AM +1100, Dean Hamstead wrote:
I think BSD style init is underrated. Controlling everything in rc.conf
is wonderful :)
Lets have that in Debian please?
Next you will suggest config.sys and autoexec.bat are a good design
too. :)
--
Len Sorensen
--
To
On 10/20/2014 05:28 PM, Christopher Browne wrote:
While I wasn't keen on Upstart getting chosen, I think the page they
prepared
describing the merits of moving from SysVInit presents good points well.
Sure, there is always merit to both sides of an argument. In the
process of fighting
I don't see the similarity. They are all files on a disk? :P
Dean
On 2014-10-22 00:32, Lennart Sorensen wrote:
On Tue, Oct 21, 2014 at 11:47:51AM +1100, Dean Hamstead wrote:
I think BSD style init is underrated. Controlling everything in
rc.conf
is wonderful :)
Lets have that in Debian
On 9 October 2014 19:49, Lennart Sorensen lsore...@csclub.uwaterloo.ca
wrote:
On Thu, Oct 09, 2014 at 09:25:23AM -0700, Ray Andrews wrote:
Can *anything* justify creating a problem that can't be debugged?
I noticed on a reboot yesterday that there was a 5 minute countdown
shutting down
On Thu, Oct 09, 2014 at 08:11:57AM -0700, Ray Andrews wrote:
On 10/09/2014 02:41 AM, Tomasz Kundera wrote:
identified, and some real solutions offered, but it looks to me like systemd
needs a sober re-think. Sometimes we really can be too clever for our own
good.
It is not clever to make
I'd like to say me too as the shortest opinion. Dealing with local
networks it is absolutely not important how much time the boot takes. Most
machines works all the time. During maintenance reboots I can wait a few
seconds more. But the complete lack of simplicity and transparency is
horrible.
What I find most frustrating of all is that there are LOTS of valid
concerns for the use of systemd but that it is coming out at the point of
implementation. I am sure I am a bit out of the loop with with daily tasks
etc but this kinda seems like it came out of nowhere destined for
integration
On 10/09/2014 02:41 AM, Tomasz Kundera wrote:
I'd like to say me too as the shortest opinion. Dealing with local
networks it is absolutely not important how much time the boot takes.
Most machines works all the time. During maintenance reboots I can
wait a few seconds more. But the complete
On Thu, 9 Oct 2014, Ray Andrews wrote:
From what I've read about the history and philosophy of all 'nix, I thought
it was a bedrock rule that primary inputs and outputs *must* be text.
Especially any sort of error log! To abandon that is to travel down the road
to Redmond, is it not? Mr.
On Thu, Oct 09, 2014 at 11:41:55AM +0200, Tomasz Kundera wrote:
I'd like to say me too as the shortest opinion. Dealing with local
networks it is absolutely not important how much time the boot takes. Most
machines works all the time. During maintenance reboots I can wait a few
On 10/09/2014 08:46 AM, Giacomo Mulas wrote:
On Thu, 9 Oct 2014, Ray Andrews wrote:
From what I've read about the history and philosophy of all 'nix, I
thought it was a bedrock rule that primary inputs and outputs *must*
be text. Especially any sort of error log! To abandon that is to
On Thu, Oct 09, 2014 at 09:25:23AM -0700, Ray Andrews wrote:
Can *anything* justify creating a problem that can't be debugged?
I noticed on a reboot yesterday that there was a 5 minute countdown
shutting down samba by the looks of it. Seems to be bug #762002.
Again, bedrock principles:
Do
After having read much of the stuff available online (including parts of
Lennart Poetterings blog), it appears that the essential point of it all seems
to have been to make boot up a little faster.
Bit i have a strong feeling that just a few seconds faster boot up simply do
not justify the
On Wed, Oct 08, 2014 at 03:32:58PM +0200, Michael wrote:
The new system reduces some complexity on one side while introducing much
more on the other.
The whole design so far as I can see lacks the simplicity and
transparency that the greatest minds in computer science advocate.
That seems to
On 10/08/2014 12:39 PM, ael wrote:
On Wed, Oct 08, 2014 at 03:32:58PM +0200, Michael wrote:
The new system reduces some complexity on one side while introducing much more
on the other.
The whole design so far as I can see lacks the simplicity and
transparency that the greatest minds in
I will weigh in.
In the FOSS world - I could care less what people decide to code up and
run. If you like it, go for it. Scratch that itch and share your code.
I liked the look of systemd early on, but this was in comparison to
upstart. Debian's dash based init scripts always struck me as
On Sun, Aug 10, 2014 at 03:17:44PM +0200, Michael wrote:
There were several problems, like with shut down, when sound card state
should be saved but created a guru. Sometimes it didn't even boot because
some ACPI thing stuck. Also my reboot / shutdown keys did not work anymore. I
did not
I am with you on this one. Unfortunately we can't go back now.
On Aug 10, 2014 4:33 PM, Michael codejod...@gmx.ch wrote:
Hello all,
I just want to load off my bad mood :) so let me tell you, today i
deinstalled systemd.
There were several problems, like with shut down, when sound card state
18 matches
Mail list logo
