> > > We've been over this already. No, the configurator user should *not*
> > > have to su at any point before actual kernel installation. Bad
> > > practice, no doughnut.
> >
> > Why bad practice? Anyway, you can:
> >
> > if [ /proc/ -nt /var/run/dmidecode ]; then
> > echo We need to run some code as root.
> > echo -n Enter root\'s> > su -c 'dmidecode > /var/run/dmidecode'
> > fi
> >
> > Which provides at least a way to have your config tool
> > work without having to bloat the initramfs.
>
> OK. One more time.
>
> The autoconfigurator is *not* mean to be run at boot time, or as root.
>
> It is intended to be run by ordinary users, after system boot time.
> This is so they can configure and experimentally build kernels without
> incurring the "oops..." risks of going root.
>
> Therefore, the above 'solution' is not acceptable.
Therefore, autoconfigurator is not acceptable. Tada.
You can't go around saying "my autoconfigurator needs this so put it into
kernel". autoconfigurator is not important enough to touch kernel/initrd.
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/