Ken Irving wrote:
> On Tue, Apr 07, 2009 at 01:34:57PM -0400, Barclay, Daniel wrote:
>> John Hasler wrote:
>>> Daniel writes:
Debian packages should have some standard place to go to to see those
latter kinds of information.
>>> /usr/share/doc/ contains README.debian, the upstream R
On Tue,07.Apr.09, 13:24:39, Barclay, Daniel wrote:
> >
> > Auto generated from what?
>
> From whatever contains any structured information to be read and added to
> README.Debian files if they remain partly non-structured as they currently
> are.
>
> The package contents can be obtained with
On Tue, Apr 07, 2009 at 01:34:57PM -0400, Barclay, Daniel wrote:
> John Hasler wrote:
> > Daniel writes:
> >> Debian packages should have some standard place to go to to see those
> >> latter kinds of information. If it did, that place could also hold an
> >> indication of any daemons started (or
Manoj Srivastava wrote:
> On Mon, Apr 06 2009, Barclay, Daniel wrote:
>
>> Debian packages should probably have some kind of post-installation
>> read-me file to tell you essential things about an installed package
>> (e.g, the commands now available; the manual/info/etc. pages now
>> avaible; daem
John Hasler wrote:
> Daniel writes:
>> Debian packages should have some standard place to go to to see those
>> latter kinds of information. If it did, that place could also hold an
>> indication of any daemons started (or installed but pending further
>> configuration) by installing a package.
>
Andrei Popescu wrote:
> On Mon,06.Apr.09, 13:21:49, Barclay, Daniel wrote:
>> Andrei Popescu wrote:
>>> On Mon,06.Apr.09, 12:52:02, Barclay, Daniel wrote:
>>>
Debian packages should have some standard place to go to to see those
latter kinds of information. If it did, that place could al
On Mon, Apr 06 2009, Barclay, Daniel wrote:
> Nuno Magalhães wrote:
is it possible to install a daemon from a Debian package without having
it automatically started afterwards?
>>
>> At the risk of starting a holy war, and kind of highjaking, shouldn't
>> Debian *not* start just-install
On Mon,06.Apr.09, 13:21:49, Barclay, Daniel wrote:
> Andrei Popescu wrote:
> > On Mon,06.Apr.09, 12:52:02, Barclay, Daniel wrote:
> >
> >> Debian packages should have some standard place to go to to see those
> >> latter kinds of information. If it did, that place could also hold
> >> an indicati
On Mon,06.Apr.09, 18:54:20, Nuno Magalhães wrote:
> >> ...and all those who don't even know what a daemon is (OMG: the computer
> >> is possessed by demons!), but expect Debian to Just Work?
>
> Those are probably using Ubuntu or Redmond stuff.
Not if I did the install! My mother's laptop runs s
>> On Mon,06.Apr.09, 12:00:43, Celejar wrote:
>>
>> > But what harm would there be in inserting a debconf question asking the
>> > user if the daemon should be started automatically? That should please
>> > all users, except for those who will be really annoyed by having to
>> > answer one additio
Daniel writes:
> Debian packages should have some standard place to go to to see those
> latter kinds of information. If it did, that place could also hold an
> indication of any daemons started (or installed but pending further
> configuration) by installing a package.
/usr/share/doc/ contains R
On Mon, 6 Apr 2009 20:05:01 +0300
Andrei Popescu wrote:
> On Mon,06.Apr.09, 12:00:43, Celejar wrote:
>
> > But what harm would there be in inserting a debconf question asking the
> > user if the daemon should be started automatically? That should please
> > all users, except for those who will
Andrei Popescu wrote:
> On Mon,06.Apr.09, 12:52:02, Barclay, Daniel wrote:
>
>> Debian packages should have some standard place to go to to see those
>> latter kinds of information. If it did, that place could also hold
>> an indication of any daemons started (or installed but pending further
>>
On Mon,06.Apr.09, 12:52:02, Barclay, Daniel wrote:
> Debian packages should have some standard place to go to to see those
> latter kinds of information. If it did, that place could also hold
> an indication of any daemons started (or installed but pending further
> configuration) by installing a
On Mon,06.Apr.09, 12:00:43, Celejar wrote:
> But what harm would there be in inserting a debconf question asking the
> user if the daemon should be started automatically? That should please
> all users, except for those who will be really annoyed by having to
> answer one additional question ...
Nuno Magalhães wrote:
>>> is it possible to install a daemon from a Debian package without having
>>> it automatically started afterwards?
>
> At the risk of starting a holy war, and kind of highjaking, shouldn't
> Debian *not* start just-installed daemons by default? Or at least ask
> while insta
On Mon, 06 Apr 2009 03:44:11 -0500
Manoj Srivastava wrote:
...
> See, there are two equally viable options here. Use debconf to
> configure the daemon, so most people can install, answer questions, and
> be on their merry way --- or not start and let the user configure it as
> they wi
On Thu, Apr 02 2009, Celejar wrote:
> On Thu, 02 Apr 2009 10:12:54 -0500
> Manoj Srivastava wrote:
>
> ...
>
>> There are mechanisms by which the site admin can tailor the
>> selection of daemons that start -- but the default should be I
>> installed it, and I installed it for a reason,
On Thu, Apr 02 2009, Dave Ewart wrote:
> On Thursday, 02.04.2009 at 10:12 -0500, Manoj Srivastava wrote:
>
>> > At the risk of starting a holy war, and kind of highjaking,
>> > shouldn't Debian *not* start just-installed daemons by default? Or
>> > at least ask while installing if such daemon is t
On Wed, 01 Apr 2009 17:23:09 +0200, Jukka Salmi wrote:
> Hello,
>
> is it possible to install a daemon from a Debian package without having
> it automatically started afterwards?
>
> What I want to do is to install samba, but neither smbd nor nbmd
> should be started until I had a chance to edit
> suggesting that there can be perfectly common use cases where I want
> the thing installed, and eventually even running, but not just yet, or
> right now.
Or not by root (e.g. mpd).
Stefan
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscr
On Thu, Apr 02, 2009 at 02:23:38PM -0400, Celejar wrote:
> On Thu, 02 Apr 2009 10:12:54 -0500 Manoj Srivastava wrote:
>
> > There are mechanisms by which the site admin can tailor the
> > selection of daemons that start -- but the default should be I
> > installed it, and I installed it
On Thu, 02 Apr 2009 10:12:54 -0500
Manoj Srivastava wrote:
...
> There are mechanisms by which the site admin can tailor the
> selection of daemons that start -- but the default should be I
> installed it, and I installed it for a reason, so I want the thing
> running.
But perhaps I
Sven Joachim --> debian-user (2009-04-01 18:07:34 +0200):
> On 2009-04-01 17:23 +0200, Jukka Salmi wrote:
>
> > Hello,
> >
> > is it possible to install a daemon from a Debian package without having
> > it automatically started afterwards?
>
> Temporarily create an executable /usr/sbin/policy-rc.
On Thursday, 02.04.2009 at 10:12 -0500, Manoj Srivastava wrote:
> > At the risk of starting a holy war, and kind of highjaking,
> > shouldn't Debian *not* start just-installed daemons by default? Or
> > at least ask while installing if such daemon is to be started
> > automatically (like sshd does
On Thu, Apr 02 2009, Nuno Magalhães wrote:
>>> is it possible to install a daemon from a Debian package without having
>>> it automatically started afterwards?
>
> At the risk of starting a holy war, and kind of highjaking, shouldn't
> Debian *not* start just-installed daemons by default? Or at le
On Thu,02.Apr.09, 09:26:56, Nuno Magalhães wrote:
> >> is it possible to install a daemon from a Debian package without having
> >> it automatically started afterwards?
>
> At the risk of starting a holy war, and kind of highjaking, shouldn't
> Debian *not* start just-installed daemons by default?
2009/4/2 Nuno Magalhães :
>>> is it possible to install a daemon from a Debian package without having
>>> it automatically started afterwards?
>
> At the risk of starting a holy war, and kind of highjaking, shouldn't
> Debian *not* start just-installed daemons by default? Or at least ask
> while in
>> is it possible to install a daemon from a Debian package without having
>> it automatically started afterwards?
At the risk of starting a holy war, and kind of highjaking, shouldn't
Debian *not* start just-installed daemons by default? Or at least ask
while installing if such daemon is to be st
On 2009-04-01 17:23 +0200, Jukka Salmi wrote:
> Hello,
>
> is it possible to install a daemon from a Debian package without having
> it automatically started afterwards?
Temporarily create an executable /usr/sbin/policy-rc.d that exits with a
value of 101, e.g. the following shell script:
#!/bin
30 matches
Mail list logo
