Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: initramfs programs (was [RFC] klibc requirements) | Date | 9 Jan 2002 15:28:09 -0800 |
| |
Followup to: <20020109174637.A1742@thyrsus.com> By author: "Eric S. Raymond" <esr@thyrsus.com> In newsgroup: linux.dev.kernel > > Matthew Kirkwood <matthew@hairy.beasts.org>: > > > The underlying problem is that dmidecode needs access to kmem, and I > > > can't assume that the person running my configurator will be root. > > > > But you can "su -c" (also sudo, I suppose). If that person > > doesn't have root, then building a kernel isn't going to do > > them much good. > > 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. >
We have also been over the fact that dmidecode, if written appropriately, could be setuid, or call a "dmicat" setuid program. This is a dmidecode implementation detail.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - 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/
| |