public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joost Roeleveld <joost@antarean.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] udev and /usr
Date: Thu, 15 Sep 2011 22:03:53 +0200	[thread overview]
Message-ID: <1779916.3DFgxt01uS@eve> (raw)
In-Reply-To: <4E72275A.9000704@gentoo.org>

On Thursday, September 15, 2011 09:27:06 AM Zac Medico wrote:
> On 09/15/2011 09:04 AM, Joost Roeleveld wrote:
> > Thank you for your response, however, I do have a few questions about
> > this. Where will this default initramfs actually need to be placed?
> 
> It should be similar to how sys-apps/v86d is used for uvesafb support.
> It installs /usr/share/v86d/initramfs and when you configure your
> kernel, you set CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs" in
> order to have in included in your kernel image.

Will this be set somewhere globally to the initramfs automatically?
And doesn't this mean that a new kernel will need to be build just to satisfy 
this?

I'm trying to think of how best to avoid users who are not aware to get caught 
with non-booting systems.

Wouldn't automatic inclusion into grub.conf be a better approach? Not sure if 
grub.conf can handle a "global" setting for initramfs.

> > Also, how will
> > we be able to deal with situations where this script fails?
> 
> It should drop you to a minimal shell.

But, with udev then failing, will there be the /dev-entries to mount the 
different partitions to fix the environment?

> > If Gentoo does decide to follow the initramfs-route, why not simply
> > implement /etc/init.d/localmount in the initramfs?
> 
> I think that's pretty close to what we have planned, since the plan is
> to have the initramfs mount configuration stored on the root filesystem.

But still require a seperate configuration file for this?

> > Why require users to figure out which
> > filesystems are needed for udev?
> 
> Simply mount all filesystems containing files managed by the package
> manager with the initramfs. Anything else would expose you to the
> possibility of unsatisfied dependencies.

On my desktop, that would mean the following list:
/usr/
/var/
/opt/
/tmp/
/opt/tmp/

> > Also, I was actually hoping for a reply to the rest of my email as well,
> > especially the idea for splitting udev into 2 seperate processes.
> 
> In essence, what your doing here is playing a game of "let's see how
> long we can delay the mounting of essential filesystems". If you play
> this game, then again, you expose yourself to the possibility of
> unsatisfied dependencies. Therefore, the only foolproof approach is to
> mount all essential filesystems as soon as possible (via initramfs).

True, but I don't have any scripts configured for udev on my desktop.
My server has some scripts related to Xen, and those are all under 
/etc/xen/...

In this case, would it still be necessary to use an initramfs?

> > If someone can explain to me why my idea won't work, please let me know.
> 
> If your goal is to expose yourself to the possibility of unsatisfied
> dependencies, they your idea will achieve it.

No, my goal is to come up with a different solution to this problem which, on 
my system and possibly also on a lot of other systems, doesn't actually exist.

--
Joost



  reply	other threads:[~2011-09-15 20:05 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 14:33 [gentoo-dev] udev and /usr Joost Roeleveld
2011-09-15 15:07 ` Zac Medico
2011-09-15 16:04   ` Joost Roeleveld
2011-09-15 16:27     ` Zac Medico
2011-09-15 20:03       ` Joost Roeleveld [this message]
2011-09-15 20:14         ` Michał Górny
2011-09-15 20:37           ` Mike Frysinger
2011-09-15 20:45           ` "Paweł Hajdan, Jr."
2011-09-15 21:24             ` Brian Harring
2011-09-15 20:27         ` Rich Freeman
2011-09-15 21:56           ` Joost Roeleveld
2011-09-15 20:31         ` Robin H. Johnson
2011-09-15 22:05           ` Joost Roeleveld
2011-09-15 20:34         ` Zac Medico
2011-09-15 22:13           ` Joost Roeleveld
2011-09-15 22:27             ` Michał Górny
2011-09-16  6:02               ` Joost Roeleveld
2011-09-15 20:56       ` William Hubbs
2011-09-15 22:17         ` Joost Roeleveld
2011-09-15 18:29   ` Rich Freeman
2011-09-15 20:40     ` Joost Roeleveld
2011-09-15 20:54       ` Rich Freeman
2011-09-15 21:48         ` Joost Roeleveld
2011-09-16  0:32           ` Rich Freeman
2011-09-16  7:25             ` Joost Roeleveld
2011-09-16  7:29               ` Robin H. Johnson
2011-09-15 19:31 ` Luca Barbato
2011-09-15 20:33   ` Joost Roeleveld
2011-09-16  4:03     ` [gentoo-dev] " Duncan
2011-09-16 13:59       ` Rich Freeman
2011-09-25  6:35         ` Mike Frysinger
2011-09-25  9:53           ` Nirbheek Chauhan
2011-09-26  1:32             ` Mike Frysinger
2011-09-26  1:57               ` Nirbheek Chauhan
2011-09-26  2:27                 ` Zac Medico
2011-09-26  4:35                   ` Nirbheek Chauhan
2011-09-26  2:27                 ` Mike Frysinger
2011-09-25 12:53           ` Rich Freeman
2011-09-25 23:16             ` "Paweł Hajdan, Jr."
2011-09-26  1:37             ` Mike Frysinger
2011-09-18  5:43     ` [gentoo-dev] " Luca Barbato
2011-09-18 12:38       ` Rich Freeman
2011-09-18 12:49         ` Michał Górny
2011-09-18 12:59           ` Nirbheek Chauhan
2011-09-18 14:27             ` Jorge Manuel B. S. Vicetto
2011-09-18 14:51               ` Michał Górny
2011-09-18 17:26               ` Nirbheek Chauhan
2011-09-19  8:15                 ` Joshua Kinard
2011-09-19  8:25                   ` Alec Warner
2011-09-19  8:44                     ` Joshua Kinard
2011-09-19  8:33                   ` Michał Górny
2011-09-19  8:57                     ` Joshua Kinard
2011-09-19  9:10                       ` Michał Górny
2011-09-19 10:30                         ` Dale
2011-09-19 10:37                         ` Joshua Kinard
2011-09-19 11:17                           ` Arun Raghavan
2011-09-19 23:19                             ` Joshua Kinard
2011-09-20  0:29                               ` Rich Freeman
2011-09-20  2:08                                 ` Joshua Kinard
2011-09-20  2:50                                   ` Zac Medico
2011-09-20  6:48                               ` Fabian Groffen
2011-09-19 17:36                           ` Greg KH
2011-09-19 18:00                             ` Rich Freeman
2011-09-19 21:46                             ` Luca Barbato
2011-09-19 22:40                               ` Greg KH
2011-09-19 22:57                                 ` Nirbheek Chauhan
2011-09-20  3:53                                 ` Zac Medico
2011-09-19 23:24                             ` Joshua Kinard
2011-09-18 19:27               ` Zac Medico
2011-09-15 19:41 ` Robin H. Johnson
2011-09-15 21:00   ` Joost Roeleveld
2011-09-15 22:18     ` Robin H. Johnson
2011-09-16  8:36       ` Joost Roeleveld
2011-09-16 18:06         ` [gentoo-dev] " Duncan
2011-09-17  6:16           ` Joost Roeleveld
2011-09-17 14:10             ` Rich Freeman
2011-09-19  8:25           ` Joshua Kinard
2011-09-17 18:40         ` [gentoo-dev] " Robin H. Johnson
2011-09-18 15:22           ` Joost Roeleveld
2011-09-18 18:14             ` [gentoo-dev] " Duncan
2011-09-18 18:59               ` Rich Freeman
2011-09-19  8:03               ` Nicolas Sebrecht
2011-09-19  7:59 ` [gentoo-dev] " Joshua Kinard
2011-09-19  8:25   ` Michał Górny

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=1779916.3DFgxt01uS@eve \
    --to=joost@antarean.org \
    --cc=gentoo-dev@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