jhalfs-2.0: Rebuild doesn't unmount kernel the kernel file systems in chroot

Hi,

See the subject line. Shouldn't this be checked in case a
user stops a 
build that ended somewhere in chapter 6 and had already
reached the 
point of mounted kernel file systems? Especially in
developer-use 
settings this sort of behavior might be expected, I would
think.

In such a scenario, currently we get 'Permission denied'
errors when 
trying to remove items in '/mnt/build_dir/proc/'.

--
JH
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

Jeremy Huntwork wrote:
> Hi,
> 
> See the subject line. Shouldn't this be checked in case
a user stops a 
> build that ended somewhere in chapter 6 and had already
reached the 
> point of mounted kernel file systems? Especially in
developer-use 
> settings this sort of behavior might be expected, I
would think.
> 
   This selection was meant to work against a reboot
scenario and not a 
restart of the build. At one time there was restart
mechanism included 
in makefile that tried to detect the state of the build and
decide 
whether to mount the file systems or not.  Unfortunately it
drifted to 
the bottom of the maintenance stack and eventually slipped
off the 
table. It still exists in the 1.0 code branch as
"restart_code"

> In such a scenario, currently we get 'Permission
denied' errors when 
> trying to remove items in '/mnt/build_dir/proc/'.
> 
> -- 
> JH

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

George Boudreau wrote:
>   This selection was meant to work against a reboot
scenario and not a 
> restart of the build. At one time there was restart
mechanism included 
> in makefile that tried to detect the state of the build
and decide 
> whether to mount the file systems or not. 
Unfortunately it drifted to 
> the bottom of the maintenance stack and eventually
slipped off the 
> table. It still exists in the 1.0 code branch as
"restart_code"

Thanks for the input. So... Do you think it's worth doing
something 
about, or are you inclined to leave it as is?

Also, if I had some (mostly cosmetic) adjustments to make,
should I send 
you a patch? And if so, against what code? Current SVN?

--
JH
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

Jeremy Huntwork wrote:
> George Boudreau wrote:
>>   This selection was meant to work against a reboot
scenario and not a 
>> restart of the build. At one time there was restart
mechanism included 
>> in makefile that tried to detect the state of the
build and decide 
>> whether to mount the file systems or not. 
Unfortunately it drifted to 
>> the bottom of the maintenance stack and eventually
slipped off the 
>> table. It still exists in the 1.0 code branch as
"restart_code"
> 
> Thanks for the input. So... Do you think it's worth
doing something 
> about, or are you inclined to leave it as is?
> 
> Also, if I had some (mostly cosmetic) adjustments to
make, should I send 
> you a patch? And if so, against what code? Current SVN?
> 
   The trunk is still connected to 2.0 and will remain so
for a quite a 
while. Feel free to bring the restart code up to date if you
have time. 
Drop us a line or a patch if you stumble upon any other
problems.


> -- 
> JH

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

Jeremy Huntwork wrote:
> George Boudreau wrote:
>>   This selection was meant to work against a reboot
scenario and not a 
>> restart of the build. At one time there was restart
mechanism included 
>> in makefile that tried to detect the state of the
build and decide 
>> whether to mount the file systems or not. 
Unfortunately it drifted to 
>> the bottom of the maintenance stack and eventually
slipped off the 
>> table. It still exists in the 1.0 code branch as
"restart_code"
> 
> Thanks for the input. So... Do you think it's worth
doing something 
> about, or are you inclined to leave it as is?
> 
> Also, if I had some (mostly cosmetic) adjustments to
make, should I send 
> you a patch? And if so, against what code? Current SVN?
> 
   The trunk is still connected to 2.0 and will remain so
for a quite a 
while. Feel free to bring the restart code up to date if you
have time. 
Drop us a line or a patch if you stumble upon any other
problems.


> -- 
> JH

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

George Boudreau wrote:
>   The trunk is still connected to 2.0 and will remain
so for a quite a 
> while. Feel free to bring the restart code up to date
if you have time. 
> Drop us a line or a patch if you stumble upon any other
problems.

Will do.

BTW, nice to see you again George. 

--
JH
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

El Miércoles, 1 de Noviembre de 2006 04:56, Jeremy Huntwork
escribió:

> Thanks for the input. So... Do you think it's worth
doing something
> about, or are you inclined to leave it as is?

The old restart code was removed after the last Makefile
restructuration to 
use sudo. In the TODO file there is a request to develop a
new restart code.

Thus if you have time and interest to develop it, go on.

> Also, if I had some (mostly cosmetic) adjustments to
make, should I send
> you a patch? And if so, against what code? Current SVN?

Against trunk. Trunk is now in maintenance mode for 2.x
releases. Only 
bugfixes, clean-up, and TODO items are allowed. And I think
that you have yet 
commit privilidges.

The experimental branch will be soon the place where 3.0
will be developed.


-- 
Manuel Canales Esparcia
Usuario de LFS nº2886:       http://www.linuxfroms
cratch.org
LFS en castellano: http://www.escomp
oslinux.org/lfs-es http://www.lfs-es.info
TLDP-ES:                           http://es.tldp.org
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page