On Tuesday 20 June 2006 10:15, Bernard Li wrote:
> Update...
>
> It works! (well sort of...)
>
> Currently there are 2 issues with SystemInstaller and SUSE Linux:
>
> 1) directory permissions - the scripts tried to chown <user> but <user> does
> not exist, and thus using root
> 2) services not started on boot, chkconfig --list on the chroot image almost
> empty
>
> 1) is not a big issue right now, I'm sure we can somehow fix it.
>
> 2) is the bigger issue - right now I got around this by manually enabling the
> services in the chroot, here's a list I came up with:
>
> [execute in chroot, i.e. chroot /var/lib/systemimager/images/<imagename>]
> chkconfig boot.* (need to resolve dependencies)
> chkconfig network on
> chkconfig syslog on
> chkconfig cron on
> chkconfig portmap on
> chkconfig nfsboot on
> chkconfig nfs on
>
> chkconfig ntp on
> chkconfig gmond on (depending if you have Ganglia installed)
> chkconfig pbs_mom on (depending if you have TORQUE installed)
> chkconfig sshd on
Okay, I think I found a way around this mess. It looks like the postinstall
scriptlets are deliberately running differently when started from YAST, this
is not particularly nice.
The solution is:
- prepare the image directory (with /etc/{mtab,passwd,group} inside)
- install (--force --nodeps) glibc into the image with rpm
- install the rest of the stuff with yume
No more permission problems, most of the services are enabled correctly (sshd,
nfs, portmap, ...). Only "network" seems to stay disabled, I'm investigating
this one, still.
Now I need to find a place to add this suse-image-bootstrap stuff. Either
do it similar to "rapt" and add this to "yume" (with special SuSE handling) or
hide it into systeminstaller. I somehow tend towards yume, because
systeminstaller doesn't need to know about the particular distro (since it
only uses packman).
Regards,
Erich
_______________________________________________
Oscar-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
