Hi Andrea,
On 3/3/08, Andrea Righi <[EMAIL PROTECTED]> wrote:
>
>
> This is a bug of si_prepareclient that doesn't resolve non-standard
> symlinks created by udev. In terms of "portability" it would be better
> to resolve this name in the standard name. If you have potentially
> heterogeneous clients, using a device naming policy based on hardware
> informations, like vendor ID, etc. could be a problem because different
> clients that have a different hardware could use the same image.
>
> For this I think the following patch could fix the problem. Could you
> test it?
>
> ---
> Index: sbin/si_prepareclient
> ===================================================================
> --- sbin/si_prepareclient (revision 4415)
> +++ sbin/si_prepareclient (working copy)
> @@ -75,6 +75,7 @@
> use lib "USR_PREFIX/lib/systemimager/perl";
> use strict;
> use Carp;
> +use Cwd 'abs_path';
> use POSIX;
> use File::Copy;
> use File::Path;
> @@ -746,6 +747,14 @@
> $boot_dev =~ s/p[0-9]+$//;
> }
>
> + # Resolve non-standard symlink names created by udev.
> + if (-l $boot_dev) {
> + $boot_dev = abs_path(readlink($boot_dev));
> + }
> + if (-l $root_dev) {
> + $root_dev = abs_path(readlink($root_dev));
> + }
> +
> # OK, we've all the info needed by systemconfigurator! Write the
> # configuration file.
> open(OUT, ">$sc_config_file") or
> ---
I have tried to apply the patch modifying the path to
/usr/sbin/si_prepareclient in the first four lines but I get this error:
golden-node:/usr/sbin # patch -p0 --dry-run <
fix-prepareclient-non-standard-symlinks-created-by-udev.path
patching file /usr/sbin/si_prepareclient
Hunk #1 succeeded at 75 with fuzz 1.
Hunk #2 FAILED at 747.
1 out of 2 hunks FAILED -- saving rejects to file
/usr/sbin/si_prepareclient.rej
I applied the patch manually and I'm going to repeat the process again. I
will tell you if it works.
> 2. The system boots using grub but the file menu.lst has not been
> > modified. At least the labels are the ones from the previous
> > installation of openSUSE 10.1 of the golden node. Obviously it works
> > because of the links of the /boot directory to the right versionof the
> > kernel and initrd.
>
>
> systemconfigurator should modify menu.lst, but since lilo has been
> detect before, grub installation is not performed (even if lilo fails).
> Are you using a post-install script to install grub?
No, I tried at the beginning but now I am not using it.
Anyway adding the PREFERED option to systemconfig.conf could be a way to
> force grub installation via systemconfigurator.
I will try this way.
> And looking at the full output of systemconfigurator would help to
> confirm if this hypothesis is correct.
>
>
> > What should I do to be able to run /sbin/lilo? Trying using UYOK to
> > reduce the size of the kernel? Modifying manually the existing
> > /etc/lilo.conf on the image?
>
>
> No. See above.
>
>
> > And regarding Grub, what is being used accidentally, does
> > systemconfigurator modify the menu.lst config file? Can I change the
> > labels of the file directly on the image?
>
>
> See above.
>
>
> -Andrea
>
I will tell you whether it works or not.
Thank you.
Jesus .-
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
