On Mon, Apr 22, 2013 at 07:51:42PM +0100, Jonathan Dowland wrote:
On Sun, Apr 21, 2013 at 12:31:25AM +0100, Kevin Chadwick wrote:
Jonathan Dowland wrote:
If you were a faithful follower of Kernighan UNIX philosophy, you
wouldn't touch those nasty BSDs with a bargepole.
Rubbish
On Sun, Apr 21, 2013 at 12:31:25AM +0100, Kevin Chadwick wrote:
On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote:
And that's a Linux problem where some BSDs put lots of effort into
compliance only to have the standard changed to suit linux due to
pressure.
Which
Hello
Excerpt from Roger Leigh:
-- snip --
update-rc.d foo disable|enable
is one method.
-- snip --
i did played further around with this. First have a look at this:
# find /etc/rc[S0-6].d/ -iname '*mountkernfs.sh*'
/etc/rcS.d/S01mountkernfs.sh
# update-rc.d mountkernfs.sh disable
On Wed, Apr 17, 2013 at 09:52:04PM +0100, Kevin Chadwick wrote:
And did it boot slower than with init scripts and waste valuable
memory. Lookup systemd on the buildroot list and you will see. Debian
may run on even a cheap toaster one day but systemd would causes issues
when that is possible.
On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote:
And that's a Linux problem where some BSDs put lots of effort into
compliance only to have the standard changed to suit linux due to
pressure.
Which standard, POSIX?
POSIX is a very good thing. Do you disagree? I could perhaps
Hello Roger,
Excerpt from myself:
-- snip --
insserv clearly complains instead that other services are affected by this
change. Generally to a admin insserv seems to be nicer API over update-rc.d to
me. Apart from that, by this i found a major bug in rc-update(). Will fix
that.
i have
On Wed, Apr 17, 2013 at 09:51:02PM +0100, Kevin Chadwick wrote:
And that's a Linux problem where some BSDs put lots of effort into
compliance only to have the standard changed to suit linux due to
pressure.
Which standard, POSIX?
Hello Roger
Excerpt from Roger Leigh:
-- snip --
Yes, the man page says it swaps the S for a K.
e.g. say we have the following link:
/etc/rc2.d/K10cups
Then afaik - and please correct if i am wrong - init will call the stop part
of
this initscript when ever runlevel 2 is entered. So
On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote:
I believe very strongly that it is. universality with Linux supporting
smaller and smaller Arm chips is part of what I was touching on in the
paragraph you had a hard time deciphering. This is something BSD is
having a hard time
On Tue, Apr 16, 2013 at 08:30:45PM -0400, staticsafe wrote:
On 4/16/2013 19:33, Chris Bannister wrote:
On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote:
I believe very strongly that it is. universality with Linux supporting
Roger Leigh wrote:
Getting rid of all the /etc/default disable options will be a release
goal for jessie.
Good. I'd prefer to be rid of /etc/default entirely!
For example, I just learned about /etc/default/keyboard.
Why not /etc/keyboard or /etc/keyboard.default? Having a central
location for
On 04/16/2013 11:55 AM, Thilo Six wrote:
Hello Michael,
Excerpt from Michael Biebl:
-- snip --
+ dropping human readable textfiles in favour of c binary code, which
makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like
On 04/16/2013 03:02 PM, Kevin Chadwick wrote:
Lets not pollute this useful thread with systemd
It seems a thread about init systems and administration/tweaking of them is the
most appropriate place for systemd to be mentioned. Not least that it can solve
the problem the OP had. It should not be
Joel Roth wrote:
Roger Leigh wrote:
Getting rid of all the /etc/default disable options will be a release
goal for jessie.
Good. I'd prefer to be rid of /etc/default entirely!
So you would rather that people edit the /ec/init.d/* scripts
themselves and manage them as conffiles at upgrade
Bob Proulx wrote:
Joel Roth wrote:
Roger Leigh wrote:
Getting rid of all the /etc/default disable options will be a release
goal for jessie.
Good. I'd prefer to be rid of /etc/default entirely!
So you would rather that people edit the /ec/init.d/* scripts
themselves and manage
Hello Roger
Excerpt from Roger Leigh:
update-rc.d foo disable|enable
-- snip --
It might be a nuisance but running the stop part of the initscript isn't the
same as not touching it all?
Sorry, I don't quite understand the question here. update-rc.d
never starts or stops anything--all
Joel Roth wrote:
I suppose the answer is that there is no shortcut to
administering a system than learning the details.
Nope. No such thing as a free lunch.
And in the free(dom) software community we have the additional free
market burden of many different sources. There are many different
Although, I accept there is no real excuse for my rudeness.
No worries, I have a thick actually english skin as I hope those I talk
to do too. If you think that's rude, you are probably a gent.
--
___
'Write programs that do
I believe very strongly that it is. universality with Linux supporting
smaller and smaller Arm chips is part of what I was touching on in the
paragraph you had a hard time deciphering. This is something BSD is
having a hard time competing with atleast in my experience of wanting
to be
On 04/16/2013 03:02 PM, Kevin Chadwick wrote:
Lets not pollute this useful thread with systemd
It seems a thread about init systems and administration/tweaking of them
is the
most appropriate place for systemd to be mentioned. Not least that it can
solve
the problem the OP had. It
On Wed, Apr 17, 2013 at 08:55:42PM +0200, Thilo Six wrote:
Hello Roger
Excerpt from Roger Leigh:
update-rc.d foo disable|enable
-- snip --
It might be a nuisance but running the stop part of the initscript isn't
the
same as not touching it all?
Sorry, I don't quite
+ dropping human readable textfiles in favour of c binary code, which makes
it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like format
and much more readable then shell scripts with all their boiler plate.
I think you miss
On Tue, Apr 16, 2013 at 10:33:47AM +0100, Kevin Chadwick wrote:
I think you miss the point which is those unit files depend on C code
So do classic init scripts:
$ file /sbin/init
/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs),
On Mon, Apr 15, 2013 at 09:20:03PM +0100, Kevin Chadwick wrote:
Lets not pollute this useful thread with systemd
It seems a thread about init systems and administration/tweaking of them is the
most appropriate place for systemd to be mentioned. Not least that it can solve
the problem the OP had.
On 04/16/2013 04:33 AM, Kevin Chadwick wrote:
+ dropping human readable textfiles in favour of c binary code, which makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like format
and much more readable then shell scripts with all
Hello Michael,
Excerpt from Michael Biebl:
-- snip --
+ dropping human readable textfiles in favour of c binary code, which
makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like format
and much more readable then shell
Lets not pollute this useful thread with systemd
It seems a thread about init systems and administration/tweaking of them is
the
most appropriate place for systemd to be mentioned. Not least that it can
solve
the problem the OP had. It should not be ignored or avoided from being
On Tue, Apr 16, 2013 at 10:33:47AM +0100, Kevin Chadwick wrote:
I think you miss the point which is those unit files depend on C code
So do classic init scripts:
$ file /sbin/init
/sbin/init: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared
On Tue, Apr 16, 2013 at 09:06:31PM +0100, Kevin Chadwick wrote:
Yes and do you know it was designed to do just what it does for a good
reason in 32 kb of code. Hello world is 8kb
Not relevant to choosing an init system.
I am saying it is easy for anyone to follow edit and lookup a man page
Yes and do you know it was designed to do just what it does for a good
reason in 32 kb of code. Hello world is 8kb
Not relevant to choosing an init system.
I believe very strongly that it is. universality with Linux supporting
smaller and smaller Arm chips is part of what I was touching
On Mon, Apr 15, 2013 at 11:21:00AM -0500, Yaro Kasear wrote:
[systemd] has a concurrent startup, meaning it brings a system up and down
*very* quickly by starting independent units at the same time.
Standard SysV init generally cannot do this, though it's hard to
account for how initscripts
On Mon, Apr 15, 2013 at 09:09:15PM +0200, Thilo Six wrote:
update-rc.d foo disable|enable
is one method.
Thank you for sharing this!
It might be a nuisance but running the stop part of the initscript isn't the
same as not touching it all?
Sorry, I don't quite understand the question
Rick Thomas wrote:
Bob Proulx wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
For an example of where one will want to manage the init scripts,
take a look at the thread
On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote:
Yes and do you know it was designed to do just what it does for a good
reason in 32 kb of code. Hello world is 8kb
Not relevant to choosing an init system.
I believe very strongly that it is. universality with Linux
On 4/16/2013 19:33, Chris Bannister wrote:
On Tue, Apr 16, 2013 at 10:21:02PM +0100, Kevin Chadwick wrote:
Yes and do you know it was designed to do just what it does for a good
reason in 32 kb of code. Hello world is 8kb
Not relevant to choosing an init system.
I believe very strongly
On Apr 14, 2013, at 10:10 PM, Bob Proulx wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
Hi Bob,
For an example of where one will want to manage the init scripts,
take a
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
Hi Bob,
For an example of where one will want to manage the init scripts,
take a look at the thread in debian-user with
On Mon, Apr 15, 2013 at 11:02:19AM +0100, Kevin Chadwick wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
Hi Bob,
For an example of where one will want to
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
What is more complicated than this. If you want it then install it.
If you don't want it then remove or purge it. With those two
On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
What is more complicated than this. If you want it then install
Le 15/04/2013 14:39, Stefan Monnier a écrit :
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
What is more complicated than this. If you want it then install it.
If you don't want it
Le 15/04/2013 16:55, Roger Leigh a écrit :
On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
What is more complicated
On Mon, Apr 15, 2013 at 05:28:02PM +0200, Erwan David wrote:
Le 15/04/2013 16:55, Roger Leigh a écrit :
On Mon, Apr 15, 2013 at 08:39:27AM -0400, Stefan Monnier wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always
On 04/15/2013 05:02 AM, Kevin Chadwick wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
Hi Bob,
For an example of where one will want to manage the init scripts,
take a look at
On Mon, Apr 15, 2013 at 03:55:33PM +0100, Roger Leigh wrote:
Getting rid of all the /etc/default disable options will be a release
goal for jessie.
Very glad to hear that. Services that come shipped with an /etc/default file
that disables the daemon 'by default' really irk me. Not least puppet,
Am 15.04.2013 17:26, schrieb Erwan David:
And disabling them in /etc/default prevent launching them after boot
(see my need on the other tread).
update-rc.d disable is the proper way to disable a service from
starting at boot time.
--
Why is it that all of the instruments seeking
Thilo Six wrote:
gentoo has a rather nice API for an administrator to handle
initscripts s.th. i always missed in debian.
Isn't sysv-rc-conf what you are looking for?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hello Bob,
Excerpt from Bob Proulx:
Thilo Six wrote:
Subject: administration of initscripts
...in debian has been no pleasure for some time now.
Sorry to hear that. Why not?
I was looking for the offical way of dealing with initscript for some time
now. If you look online mostly update
Hello Roger,
Excerpt from Roger Leigh:
-- snip --
update-rc.d foo disable|enable
is one method.
Thank you for sharing this!
It might be a nuisance but running the stop part of the initscript isn't the
same as not touching it all?
-- snip --
Getting rid of all the /etc/default disable
Hello Siard,
Excerpt from Siard:
Thilo Six wrote:
gentoo has a rather nice API for an administrator to handle
initscripts s.th. i always missed in debian.
Isn't sysv-rc-conf what you are looking for?
Thank you for your help. I am aware of the existents of 3rd party managing tools
of this
file-rc works, but only just. I would not be surprised if it was
removed for the next stable release--it's simply incompatible with
dependency-based booting.
That's a shame, I would take direct editing of runlevel.conf over
dependency-based booting myself.
When you are using dynamic
Hello Yaro,
Excerpt from Yaro Kasear:
-- snip --
Systemd has assimilated udev,
-- snip --
Related to the above two downsides, systemd is not really a crowning
example of a developer following the UNIX Philosophy of one simple task
and do it well.
-- snip --
Administrators might not
On Mon, 15 Apr 2013 08:39:27 -0400
Stefan Monnier monn...@iro.umontreal.ca wrote:
I have been using Debian for many years now. In all of that time I
have never wanted to manage init scripts. I always wonder. What
are people trying to do?
What is more complicated than this. If you
Am 15.04.2013 20:12, schrieb Celejar:
What's wrong with sysv-rc-conf (although it won't work for some of the
fancier stuff you have in mind, such as running daemons on demand)?
It's orphaned and hasn't seen any updates for over 6 years.
--
Why is it that all of the instruments seeking
Am 15.04.2013 21:35, schrieb Thilo Six:
+ dropping human readable textfiles in favour of c binary code, which makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like format
and much more readable then shell scripts with all their
On Tue, 16 Apr 2013 02:12:20 +0200
Michael Biebl bi...@debian.org wrote:
Am 15.04.2013 20:12, schrieb Celejar:
What's wrong with sysv-rc-conf (although it won't work for some of the
fancier stuff you have in mind, such as running daemons on demand)?
It's orphaned and hasn't seen any
On 04/15/2013 07:13 PM, Michael Biebl wrote:
Am 15.04.2013 21:35, schrieb Thilo Six:
+ dropping human readable textfiles in favour of c binary code, which makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files are text-files in ini-like format
and much
Am 16.04.2013 04:26, schrieb Yaro Kasear:
UNLESS, does anyone know if journalctl works fine inside a
LiveCD/DVD/USB/Ferret/Whatever on another systemd setup? Or, maybe as a
better way to put it, use a live media's journalctl to use a non-running
systemd's journal?
Sure, that works: journalctl
Am 16.04.2013 04:26, schrieb Yaro Kasear:
On 04/15/2013 07:13 PM, Michael Biebl wrote:
Am 15.04.2013 21:35, schrieb Thilo Six:
+ dropping human readable textfiles in favour of c binary code, which
makes it
needless more complex to debug the whole show.
That's non-sense. systemd unit files
...in debian has been no pleasure for some time now.
Hello readers.
Well the reason i write this, is i found a solution that works for me which i
would like to share with you.
Following goals had been set:
1) Do not clash with existing system tools.
It is notably that it has even been said
Thilo Six wrote:
Subject: administration of initscripts
...in debian has been no pleasure for some time now.
Sorry to hear that. Why not?
Well the reason i write this, is i found a solution that works for me which i
would like to share with you.
Thank you for sharing.
Following goals had
61 matches
Mail list logo
