[Rear-users] rear mkrescue hangs on SLES 9 (SP4)

Werner Flamme werner.flamme at ufz.de
Mon Jan 28 15:33:14 CET 2008

Hi Schlomo,

I do not understand anything anymore...

I put the single quotes back - and the ISO has exactly the same size as
without the quotes, 13565952 Bytes.

I swear I did no updates in between!

The only thing is my change in
/usr/share/rear/build/default/50_patch_sshd_config.sh, where I
eliminated 50% of the the [n] hack ;-) by using

if [ -d $ROOTS_DIR/etc/ssh ]; then
sed -i -e 's/PasswordAuthentication.*/PasswordAuthentication no/ig' \

and so on. The file has the correct time stamp and content, so it works.

Time sync is well documented - in "Various settings". I found it
accidentally ;-) when I came to
http://rear.sourceforge.net/documentation.php?viewall :-) Still too many
lines without content in between there ;-) Maybe I can help you, but at
first I have to understand the program for myself :-)

BTW, in the Concept paper, Chapter "FS layout", the line with /etc/rear
appears twice - before and after /usr/bin/rear (which is false, it
should be /usr/sbin/rear) :-)

Everything in your software is structured clearly, that helps to find
it. Maybe it is sometimes hard to find the name of the file where an
error occurs, since $0 is always '/usr/sbin/rear'. And in the files, the
code is well readable. The only thing that lacks readability are the
white places in the docu 8-)


Schlomo Schapiro   [28.01.2008 14:32]:
> Hi Werner,
> nice for you. But, to sum it up, are you sure that the quotes caused the 
> trouble ? Can you verify this by adding them again ? tar should not 
> break if you ask it to exclude something that doesn't exist.
> You could also try to escape the * with \ instead of the quotes.
> Regards,
> Schlomo
> PS: Congrats on finding the time sync - it is not very well documented :-(
> Werner Flamme wrote:
>> Schlomo,
>> I am sure your software reads this mailing list ;-) Or maybe it was the
>> weekend. Or whatever. A "rear -d mkrescue" today created a 13 M sized
>> ISO image to boot from. Without hassles. Without the files I do not want...
>> The only change I made was removing the single quotes from
>> /etc/rear/local.conf. These were the first changes I made - the original
>> entries were without. I added them later - and forgot them... :-(
>> So, now I have the following change to the configuration compared to the
>>  package I installed:
>> - in /etc/rear/local.conf
>>     /dev/shm/SAP*
>> )
>> COPY_AS_IS=( "${COPY_AS_IS[@]}"
>>     /etc/ssh/*
>>     /usr/share/rear/*
>> )
>> - in /etc/rear/site.conf
>> My oh my, I thought some problems were restricted to this ominous system
>> from Redmond ;-)
>> Thanks for your help!
>> Regards,
>> Werner
>> Schlomo Schapiro   [26.01.2008 21:28]:
>>> Hi Werner,
>>> this is a SLES9 ? Strange of strange, as my demo also uses SLES9 (SP3 IIRC).
>>> I have heard another issue of tar -X beeing a problem, but that was on a very
>>> specific version of Debian.
>>> To debug this kind of trouble I suggest you simply add a call to
>>> bash -i </dev/tty9 >/dev/tty9 2>&1
>>> after the problematic tar. That will spawn a shell on VT 9 where you can debug
>>> in peace and check the result of the tar.
>>> The PROGRESS output below is because you used one of the debug options.
>>> BTW, you can also use the step-by-step mode to halt the script after the
>>> problematic part (or before) to analyse.
>>> I am really sorry, but this kind of stuff is hard to debug without having your
>>> hands on the system.
>>> Try experimenting with your version of tar and the -X option to understand how
>>> to write the exclusion. Please note also that the quotes (') in the local.conf
>>> prevent the shell from expanding the pattern. You might try removing the quotes
>>> so that the shell will expand the patterns to the appropriate directories. In
>>> general though, it might be better to add --one-file-system to that specific tar
>>> because in most cases people don't want this tar to cross over mountpoints (and
>>> could still include them specifically).
>>> Regards,
>>> Schlomo
>>> Werner Flamme wrote:
>>>> I am going nuts...
>>>> Now I added some lines to local.conf and switched back to the normal tar
>>>> command. It works, except for that -X. The files in /dev/shm/* are
>>>> copied though there is still /dev/shm/SAP* in copy-as-is-exclude.
>>>> copy-as-is-filelist has now a size of 300+K bytes, not 700 as before.
>>>> The local.conf now reads:
>>>> MODULES_LOAD=( vmxnet )
>>>>     '/dev/shm/SAP*'
>>>> )
>>>> COPY_AS_IS=( "${COPY_AS_IS[@]}"
>>>>     '/etc/ssh/*'
>>>>     '/usr/share/rear/*'
>>>> )
>>>> The log says:
>>>> 2008-01-25 12:23:27 Will copy /etc/rear /usr/share/rear /dev
>>>> /etc/protocols /etc/services /etc/rpc /etc/termcap /usr/share/terminfo
>>>> /etc/ssh/* /usr/share/rear/* /etc/resolv.conf /etc/hosts /etc/host.conf
>>>> /etc/iproute2 /lib/modules/2.6.5-7.286-smp/modules.alias
>>>> /lib/modules/2.6.5-7.286-smp/modules.ccwmap
>>>> /lib/modules/2.6.5-7.286-smp/modules.dep
>>>> /lib/modules/2.6.5-7.286-smp/modules.ieee1394map
>>>> /lib/modules/2.6.5-7.286-smp/modules.inputmap
>>>> /lib/modules/2.6.5-7.286-smp/modules.isapnpmap
>>>> /lib/modules/2.6.5-7.286-smp/modules.pcimap
>>>> /lib/modules/2.6.5-7.286-smp/modules.symbols
>>>> /lib/modules/2.6.5-7.286-smp/modules.usbmap /etc/modules.conf
>>>> /etc/modprobe.conf /etc/modprobe.conf.local /etc/modprobe.conf.local~
>>>> /etc/modprobe.d /etc/ntp.conf /etc/ssh /root/.ssh and exclude /dev/shm/SAP*
>>>> PROGRESS: /etc/ssh/
>>>> PROGRESS: /etc/ssh/ssh_config
>>>> PROGRESS: /etc/ssh/moduli
>>>> PROGRESS: /etc/ssh/ssh_host_key
>>>> PROGRESS: /etc/ssh/sshd_config
>>>> PROGRESS: /etc/ssh/ssh_host_key.pub
>>>> PROGRESS: /etc/ssh/ssh_host_dsa_key
>>>> PROGRESS: /etc/ssh/ssh_host_dsa_key.pub
>>>> PROGRESS: /etc/ssh/ssh_host_rsa_key
>>>> PROGRESS: /etc/ssh/ssh_host_rsa_key.pub
>>>> PROGRESS: /etc/ssh/sshd_banner
>>>> PROGRESS: /etc/ssh/sshd_config.rpmnew
>>>> Wow. Great.
>>>> Why?
>>>> Regards,
>>>> Werner

Werner Flamme, Abt. WKDV
Helmholtz-Zentrum für Umweltforschung GmbH - UFZ
Permoserstr. 15 - 04318 Leipzig
Tel.: (0341) 235-1921 - Fax (0341) 235-451921
http://www.ufz.de - eMail: werner.flamme at ufz.de

More information about the rear-users mailing list