On 06/18/2014 05:38 PM, jhcha54008 wrote:
> Hi,
> 
> I got the same result :
> 
> mknod: 'dev/ttyS0': Permission denied
> 
> The patch below solved the issue.
> 
> It is perhaps advisable to not chroot before making a
> new device node (as in debirf version 0.33, 
> file /usr/bin/debirf, line 135 :
>         fakeroot_if_needed sh -c "mknod $DEBIRF_ROOT/dev/console c 5 1; chmod 
> 0600 $DEBIRF_ROOT/dev/console"
> which doesn't cause any error)
> 
> Thank you for making debirf such a useful tool !
> 
> Regards,
> JH Chatenet
> 
> --- a/usr/share/debirf/modules/serial-terminal
> +++ b/usr/share/debirf/modules/serial-terminal
> @@ -32,10 +32,10 @@
>  debirf_exec chown root:root "${SCRIPTED_GETTY}"
>  
>  # make sure the basic serial devices are present
> -debirf_exec mknod dev/ttyS0 c 4 64
> -debirf_exec mknod dev/ttyS1 c 4 65
> -debirf_exec mknod dev/ttyS2 c 4 66
> -debirf_exec mknod dev/ttyS3 c 4 67
> +mknod "${DEBIRF_ROOT}/dev/ttyS0" c 4 64
> +mknod "${DEBIRF_ROOT}/dev/ttyS1" c 4 65
> +mknod "${DEBIRF_ROOT}/dev/ttyS2" c 4 66
> +mknod "${DEBIRF_ROOT}/dev/ttyS3" c 4 67
>  
>  if grep "$SCRIPTED_GETTY" "$INITTAB" | grep -q -v "^[[:space:]]*#" ; then
>      echo "inittab already has a getty on the console."

This patch seems guaranteed to fail by anyone who isn't running debirf
as the superuser, which we generally don't advise.

i still haven't been able to reproduce this problem myself, though.
what system are you running this on that you see this problem?  how are
you invoking debirf?  what target are you using?

        --dkg

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to