public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev + incron wheel's remake : hal/dbus usefulness quest
Date: Fri, 18 Sep 2009 21:27:16 +0600	[thread overview]
Message-ID: <20090918212716.31273b43@coercion> (raw)
In-Reply-To: <20090918135914.GA14282@b1b1.lan>

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

On Fri, 18 Sep 2009 15:59:14 +0200
gibboris@gmail.com wrote:

> A small email to sumarize some thoughts about udev, removable
> storage and incron to make the job of hal and re-invent the wheel.
...
> I would be curious to read some advices about this architecture.

Nice. I have a temptation to copy-paste it right now, but there's just
no point, since I can't remember when I last plugged in an unknown
device.

> I also have 2 questions :
> - what's the way to have a incremental number for unknown devices like
>   /mnt/remusb1 then /mnt/remusb2 instead of /mnt/remusb (within udev) ?

Prehaps create a simple script that reads /etc/mtab and checks what
remusb mountpoints are used, picking a free one or creating additional
path.

> - where to put the creation of /tmp/.incron.device in the init scripts
>   to be sure it will be created BEFORE incron starts (without having to
>   create a new startup script) ?

Since it belongs to incron (and useless without one), shouldn't it be
only logical to put these lines into incron init.d script?
Sure, there'd be one more etc-update line if someone will ever change
the file, but that shouldn't happen too often, and besides, that's what
etc-update is for.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2009-09-18 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-18 13:59 [gentoo-user] udev + incron wheel's remake : hal/dbus usefulness quest gibboris
2009-09-18 15:27 ` Mike Kazantsev [this message]

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=20090918212716.31273b43@coercion \
    --to=mk.fraggod@gmail.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox