Are there going to be 3.4.7 i386 RPMs as well? I am currently using
3.7.4r3734_bli-1 because that was the latest SI with i386 rpms. I have two
small problems to report w.r.t. that version:
1. The disk enumeration fails to detect a P-ATA disk (hda) and falls back to
using sda (golden client has a sata disk). I can't really decipher that chunk
of code (looking in /proc/diskstats, which does contain a bunch of lines for
hda), so I put in a work-around which is sufficient for our simple systems:
DISK0=`test -e /proc/ide/hda/geometry && echo "/dev/hda" || echo "/dev/sda"`
(ie if hda is a hard disk, that is the target, otherwise sda is the target; we
have a mix of pata, sata, and regular scsi)
As a side effect, the "disk edit" is skipped because DISKORDER is zero-length.
For the grub.conf, we always edit it in a postUpdate script since we are
upating servers and desktops (servers have serial console config in the
grub.conf). For the fstab, I fix that in a post-install script.
2. Our system config requires that the hostname is set to the short name
rather than the FQDN, but SystemConfigurator puts the FQDN
in /etc/sysconfig/network :-( I also fix that in my post-install script.
Is there a standard way to do that? Is there a reason we should use FQDN?
3. Some of the target systems have onboard 10/100 (forcedeth) and a Gbit PCI
(e1000) and others have onboard Gbit (forcedeth). We want to ue Gbit in all
cases. The UYOK initrd has e1000 and forcedeth drivers. On the systems with
the PCI card, the e1000 PCI card gets used for the autoinstall, but
SystemConfigurator configures it as eth1 (and the onboard forcedeth as eth0)
and leaves eth0 as the one to enable at boot: ooops.
As a work-around, I didabled the onboard 10/100 NIC in the BIOS and
re-installed, but some of our servers have multiple ports and it may not be
possible to force a single Gbit NIC to be visible in all cases. Is there any
way to have SystemConfigurator to configure the NIC that is actually used as
eth0? It basically means getting
alias e1000 eth0
into the modprobe.conf instead of
alias forcedeth eth0
alias e1000 eth1
On FC5 there is also the /etc/sysconfig/network-scripts/ifcfg-eth0 (and 1)
which has ONBOOT=yes (or no), but SC seems to enable eth0 and disable eth1.
Note: the golden client uses an onboard forcedeth and the e1000 drover is
included in the UYOK via the UYOK.modules_to_include file.
4. I am using UYOK and under FC5 I had to use
--append "ramdisk_size=96000"
to get the autoinstallcd to boot.
Finally: I do really like the config files for including and excluding
modules!!! I am also including 4-5 SCSI drivers for our various servers that
get the same image.
If these issues have been addressed in a more recent RC then I would be able
to test them if I can get i386 RPMs... not sure what the arch in the package
name means when the arch in the rpm name is "noarch".
On Friday 29 September 2006 08:01, Bernard Li wrote:
> That is a known issue with SystemImager 3.6.3. I will most likely upload
> the 3.7.4 x86_64 RPMs to SourceForge today. If I don't get to it, you can
> use the pre-release RPMs from
> http://www.bcgsc.ca/downloads/oscar/systemimager/dev.
--
Patrick Dowler
Tel/Tél: (250) 363-6914 | fax/télécopieur: (250) 363-0045
Canadian Astronomy Data Centre | Centre canadien de donnees astronomiques
National Research Council Canada | Conseil national de recherches Canada
Government of Canada | Gouvernement du Canada
5071 West Saanich Road | 5071, chemin West Saanich
Victoria, BC | Victoria (C.-B.)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
