[opensuse-buildservice] Options to use 'mknod' in OBS?
I'm working with a bit of legacy code that's apparently writing files manually for an initial ramdisk (initrd). In its makefile, it's using 'mknod -m 660 tty1 c 4 1' This causes issues with OBS, as mknod doesn't work for non-root users, IIRC. I know OBS executes builds as user 'abuild', and it makes sense to me to have a nonprivileged user doing the build. Since running builds as root is verboten, what options do I have to build this package with OBS? (Note: I am using my own OBS server/build nodes, not build.opensuse.org) -- Troy Telford -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2011-03-31 15:38:13 -0600, Troy Telford wrote:
I'm working with a bit of legacy code that's apparently writing files manually for an initial ramdisk (initrd).
In its makefile, it's using 'mknod -m 660 tty1 c 4 1'
This causes issues with OBS, as mknod doesn't work for non-root users, IIRC.
I know OBS executes builds as user 'abuild', and it makes sense to me to have a nonprivileged user doing the build.
Since running builds as root is verboten, what options do I have to build this package with OBS?
(Note: I am using my own OBS server/build nodes, not build.opensuse.org)
from the %files section in aaa_base.spec %attr(660,root,disk) %dev(b,7,0) /lib/udev/devices/loop0 so patch out the mknod from the make file and replace them with %dev lines in the %files section hth darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Marcus Rueckert
-
Troy Telford