[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Invoking ‘init’ from an init.d script (Wheezy)



On Wed, Jun 10, 2015 at 2:14 PM, David Kalnischkies
<david@kalnischkies.de> wrote:
> On Mon, Jun 08, 2015 at 12:09:37PM +0200, Alexander Thomas wrote:
>> I know, but this is a closed system and nothing is pulled in from
>> external repositories during this automated update. The stuff that is
>> included in the local patch repository is thoroughly tested before
>> release. Still, enforcing proper signing and getting rid of that
>> --force-yes is on our TODO list.
>
> Use --allow-unauthenticated in this case. Or better yet, mark the local
> source as [trusted=yes] in sources.list to avoid this prompt without
> opening the floodgates entirely.
>
> --force-yes e.g. also disables the 'Do as I say' prompt before
> destroying your system^W^W^Wremoving (pseudo) essential packages.
>
>
> It is on my TODO list to drop the --force-yes flag and replace it with
> specialised --allow-* flags 'just' to force users to acknowledge what
> it is they are saying yes to. Somehow most people are way more willing
> to add --allow-everything than --allow-prostate-exam …

I think the second highest-rated answer here is one of the reasons for
the popularity of --force-yes:
http://superuser.com/questions/164553/automatically-answer-yes-when-using-apt-get-install
Anyone with sufficient reputation to make comments, may want to add a
remark about --allow-unauthenticated in an attempt to stop people from
shooting at the unsigned mosquito with a bazooka.


Regards,

Alexander


Reply to: