On May 11, 2014, at 3:24 PM, Pierre Labastie wrote:
However, they are still ran as the clfs user and will fail at the
creation of
devices when using mknod.
Did you try ?
The Makefile has:
mk_SUDO: mk_CROSS
@sudo make BREAKPOINT=$(BREAKPOINT) SUDO
@touch $@
----------------------
so all SUDO targets are run as root.
Pierre
Hi Pierre,
That is in the Makefile.
I can run make mk_SUDO and still get the same problem.
Starting at creatingdirs, all the targets are ran as the clfs user.
whoami in the 090-devices, for example, still outputs clfs and bombs
out when attempting to use mknod
and 095-changingowner doesn't use the root user so can't change
ownership of anything to 0:0
The rest work fine as the clfs user as jHALFS will set ${CLS} (/mnt/
clfs) to 777 with the sticky bit. But creating devices and changing
ownership to 0:0 in ${CLFS} (/mnt/clfs) isn't working properly like
it should.
In the Makefile:
mk_SUDO: mk_CROSS
@sudo make BREAKPOINT=$(BREAKPOINT) SUDO
@touch $@
SUDO: 090-devices 095-changingowner
090-devices: 089-createfiles
@$(call echo_message, Building)
@export BASHBIN=$(SHELL) && $(SHELL) progress_bar.sh $@ $
$PPID &
@echo "$(nl_)`date`$(nl_)" >logs/$@
@$(PRT_DU) >>logs/$@
@export CLFS=$(MOUNT_PT) && \
clfs-commands/boot/$@ >>logs/$@ 2>&1 && \
$(PRT_DU) >>logs/$@
@$(call housekeeping)
095-changingowner: 094-flags
@$(call echo_message, Building)
@export BASHBIN=$(SHELL) && $(SHELL) progress_bar.sh $@ $
$PPID &
@echo "$(nl_)`date`$(nl_)" >logs/$@
@$(PRT_DU) >>logs/$@
@export CLFS=$(MOUNT_PT) && \
clfs-commands/boot/$@ >>logs/$@ 2>&1 && \
$(PRT_DU) >>logs/$@
@$(call housekeeping)
Sincerely,
William Harrington
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
