All of lore.kernel.org
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] The Ubuntu Collection
Date: Wed, 07 Dec 2005 22:51:55 +0000	[thread overview]
Message-ID: <20051207225154.GA26605@wonderland.linux.it> (raw)
In-Reply-To: <1133975579.2805.21.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1231 bytes --]

On Dec 07, Kay Sievers <kay.sievers@vrfy.org> wrote:

> > 55-run-program.patch
> >     This reduces the severity of the "exec of program failed" error IF
> >     the reason the program couldn't be run was because it didn't exist
> Yeah, I'm still unsure if the used tool should be required to be in the
> rootfs or not. But it sounds like a sane default, if we don't require
> this.
I'd rather not use such a patch, because in the end it will hide real
problems.

> For the higher level things HAL is the approproate place to do device
> setup anyway. That's the reason I ignored all the map conversion things,
> cause digital cameras, scanners and such things belong to HAL these days
> and not in udev rules.
Tell this to the libsane/libgphoto maintainers... :-)

> Hmm, I'm no longer sure that the C programs for something that is
> usually 20 lines of shell long and called 3 times at bootup make sense.
> For the firmware case I always wanted to add some handling for missing
> firmware, but even for this we would not need a C program. Hmm...
Indeed. All these programs are much larger than a small shell, and I
just do not believe that shell script would not be efficient enough.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-12-07 22:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 17:12 [PATCH] The Ubuntu Collection Scott James Remnant
2005-12-07 22:37 ` Kay Sievers
2005-12-07 22:51 ` Marco d'Itri [this message]
2005-12-08  1:50 ` Scott James Remnant

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20051207225154.GA26605@wonderland.linux.it \
    --to=md@linux.it \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.