16:02
To: sisuite-users@lists.sourceforge.net
Subject: Re: [Sisuite-users] Grub.Pm again ;-)
Bernard, I am using this one:
http://sourceforge.net/project/showfiles.php?group_id=24006
Is that not the current version?
-Drew
- Original Message -
From: Bernard Li [EMAIL
da3 initrd
/initrd-2.6.9-22.0.2.EL.imgbut if i then IMAGE this image onto an IDE
drive, the kernel line is nolonger valid, it needs to change to
/dev/hda3.Any ideas??-Drew- Original Message
-----From: "Bernard Li" [EMAIL PROTECTED]To:
sisuite-users@lists.sourceforge.netSent: Wedne
Title: RE: [Sisuite-users] Regarding Grub.pm...
Which version of SystemImager are you using? As far as I know this functionality already exists in 3.5.3 in the sense that you can create one image and as long as the hardware are similiar enough, it doesn't matter whether the device shows up
-Drew
- Original Message -
From:
Bernard Li
To: sisuite-users@lists.sourceforge.net
; sisuite-users@lists.sourceforge.net
Sent: Monday, February 27, 2006 6:08
PM
Subject: RE: [Sisuite-users] Regarding
Grub.pm...
Which version of SystemImag
Hi Ashley:
Is it reasonable for UseYourOwnKernel.pm to use a more
standard method to
create devices?
That chunk of code has not been checked into SVN yet, so this is just
experimental code to get me going.
Another user encountered a similar problem on SuSE and used this method
instead:
Hi George:
3.6.2 is available in Debian unstable:
http://pdo.debian.net/cgi-bin/search_packages.pl?keywords=systemimagers
earchon=namessubword=1version=unstablerelease=all
However, you might want to grab source from branches/3.6.x and try
building that instead - it has numerous bugfixes since
: Friday, February 17, 2006 16:50
To: sisuite-users@lists.sourceforge.net
Subject: Re: [Sisuite-users] rpm problem building
systemimager-3.6.3 - maybe GPG key needed?
Hi Bernard!
On Feb 17, 2006, at 5:22 PM, Bernard Li wrote:
Hi Charles:
Just to clarify:
/trunk is not 3.6.3
Title: [Sisuite-users] mkbootpackage (bug 1426566)
Hi Patrick:
It sounds like you need to
use si_mkautoinstallcd with the kernel/initrd.img created using
si_prepareclient. Use the --kernel and --initrd arguments.
BTW, use si_prepareclient
with the --norsync argument. si_mkbootpackage
What version of SystemImager
are you using?
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of GustavoSent: Mon 13/02/2006 09:28To:
sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] creating
image on a mounted NFS file system
Hi,
I am having problems creating an image on
Hi Bela:
It appears that you can mount
the initrd.img and write to it:
mv initrd.img
initrd.img.gz
gunzip
initrd.img.gz
mount -o loop initrd.img
/mnt
Modify the file, then gzip
it. Hopefully it'll work.
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of B. ErdelyiSent: Fri
Hi Bela:
Don't think you need to
"recreate initrd.img with cramfs" - once you mount it and modify the functions
file, just umount initrd.img, then gzip it then rename it back to initrd.img and
put it in /tftpboot (or re-make autoboot CD).
If that doesn't work, then I
recommend you
Hi Bela:
If the tmpfs parameters were
indeed passed onto the kernel, then the tmpfs size should be what you
specified. I am really ata loss as to what has gone
wrong...
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of B. ErdelyiSent: Wed 01/02/2006 16:08To:
Hi Bela:
The RPMs have the same names,
but they are built at different times (with slightly different code). This
is my bad so from now on I will give them unique identifiers such that we can
easily identify which version you are using.
I guess the only difference
between your
Trimming
my response so it goes through...
From:
Bernard Li Sent:
Friday, January
27, 2006 11:26To:
'sisuite-users@lists.sourceforge.net'Subject: RE: [Sisuite-users] Problem
with mkautoinstallcd tmpfs
If you
want to work around
, January 27,
2006 2:28
PMTo:
sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users] Problem
with mkautoinstallcd tmpfs
Trimming my
response so it goes through...
From:
Bernard Li Sent:
Friday, January
] Problem
with mkautoinstallcd tmpfs
Trimming my
response so it goes through...
From:
Bernard Li Sent:
Friday,
January 27, 2006 11:26To:
'sisuite-users
Hi Bela:
Can you check the resulting
CD's isolinux/syslinux.cfg to make sure that the append statements are actually
there? It should look something like:LABEL systemimagerKERNEL
kernelAPPEND vga=extended initrd=initrd.img root=/dev/ram tmpfs_size=2G
tmpfs_nr_inodes=2000
I just tested
for Broadcom and SATA
This was solved
already by Bernard Li.
Alexandre TOURNIER System
Administrator
DG-JRC European
Commission
Institute for Environment and
Sustainability - Global Environment Monitoring TP 440 - Via Fermi,1 21020
ISPRA (VA) - Italy tel: +x
Hi Nick:
You should be able to find all the RPMs you need from this location:
http://svn.oscar.openclustergroup.org/oscar/branches/branch-4-2/packages
/sis/distro/
(look in common-rpms and fc4-i386)
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Looks like you're missing the perl module
XML::Simple.
What OS are you installing on?
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of chg
wangSent: Tuesday, January 03, 2006 17:20To:
sisuite-users@lists.sourceforge.netSubject:
Does RH9 actually support your SATA
drives?
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy
ToddSent: Monday, January 23, 2006 4:24To:
sisuite-users@lists.sourceforge.netSubject: RE: [Sisuite-users]
Problem with
Are you using
LVM?
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of B. ErdelyiSent: Fri 20/01/2006 11:11To:
sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] Problem
with mkautoinstallcd tmpfs
Hi,
I am attempting an image install
with si_mkautoinstallcd using SI
Title: master script missing
The master script is generated by mkautoinstallscript
(prepend si_ if newer version of SystemImager).
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris
HarrisSent: Tuesday, January 17, 2006 13:05To:
Title: [Sisuite-users] Building SystemImager RPMs
Hi Jim:
If you're looking for
SystemImager 3.5.3 RPMs, perhaps you can just use the following prebuilt ones
from the OSCAR repository:
http://svn.oscar.openclustergroup.org/oscar/branches/branch-4-2/packages/sis/distro/common-rpms/
What
Title: [Sisuite-users] kernel BUG at include/linux/i2o.h:517!
Hi Charles:
I believe si_prepareclient
uses the OS' kernel and generate a compatible initrd.img based on your
system.
Have you tried using the
stock kernel/initrd.img which came with SystemImager's boot-standard package to
Please provide:
SystemImager version
Linux distribution version
Chances are, SystemImager kernel (2.4 based I'm guessing)
recognizes your HD as /dev/hda, but your actual OS detects it as /dev/sda.
This is not uncommon with SATA devices.
Cheers,
Bernard
From:
[EMAIL PROTECTED]
-users] Problem with image on SATA drives
On Wednesday 11 January 2006 14:20, Bernard Li wrote:
Since SystemConfigurator is responsible for setting up
grub, I would say
yes, upgrade SystemConfigurator.
Other folks may have encountered the same thing, there may be some
manual steps you can
IA64 should still work, though I have not recently compiled
it.
The latest stable is 3.6.2, though the code in branch/3.6.x
has a bunch of bugfixes which you probably want, so just check out the code from
SVN.
Once the code is checked out, run:
% make source_tarball
% rpmbuild -ta
You won't be running apache during imaging, the server needs to be
rebooted (into the SystemImager kernel) before imaging can occur.
Updating is a different story though.
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Ben
Hartshorne
Sent: Monday, January 09, 2006 18:22
To: sisuite-users@lists.sourceforge.net
Subject: Re: [Sisuite-users] overrides and timing issues
On Mon, Jan 09, 2006 at 06:17:21PM -0800, Bernard Li wrote:
If you're updating, why wouldn't you just put the override
files as the
stock files
Hi Steve:
You should have the Java
webadmin setup on the blades right? In that case you should be able to see
everything on the console. The more console messages you can provide, the
easier it is for us to troubleshoot.
Other than that, the only
other thing I can suggest is run
Hi Steve:
Try this newer version of
SystemConfigurator from OSCAR trunk and see if it works for you.
Supposedly it fixes some RHEL4 grub-related issues:
http://svn.oscar.openclustergroup.org/oscar/trunk/packages/sis/distro/common-rpms/systemconfigurator-2.2.2-11ef.noarch.rpm
Cheers,
. Of course it could just be that I
haven't had any issues... yet. :-)
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of Allen BierbaumSent: Thu 05/01/2006 07:26To:
sisuite-users@lists.sourceforge.netSubject: Re: [Sisuite-users]
Interactive SystemImager installs with CD
Bernard Li wrote: Hi
nd up denying the dhcp request and
they get no ip.
or you can give out for another network, essentially running two subnets
over the same wire, and then the poor clients can't route. Trust me...I
did this. :)
On Jan 5, 2006, at 11:47 AM, Bernard Li wrote:
Correct me if I'm wrong,
b
writeable or not, though.
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of Charles GalpinSent: Thu 05/01/2006 13:44To:
sisuite-users@lists.sourceforge.netSubject: Re: [Sisuite-users] Re:
no devfs support when using 3.5.3
Hu BernardOn Jan 5, 2006, at 12:58 AM, Bernard Li
wrote: You can grab
Title: Could not stat device /dev/hda
Chances are SystemImager's
kernel could not detect your storage adapter. I wouldn't really test
SystemImager with laptop hardware if I were you - just test it on some older
hardware like PIII or something :-)
Also, what version of
SystemImager are
@lists.sourceforge.netSubject: Re: [Sisuite-users] Re:
no devfs support when using 3.5.3
On Jan 5, 2006, at 7:36 PM, Bernard Li wrote: Hi
Charles: The RPMs are built on a x86_64 system and thus
only generated the x86_64 binaries - you'll need to rebuild the SRPM on
a x86 system.Doh! I had completely
Title: [Sisuite-users] Interactive SystemImager installs with CD
Hi Allen:
You mention that you cannot
use a custom DHCP - can you use the _existing_ one then for this
purpose?
If you go with the "static
DHCP" route, you should just need a DHCP server for initial deployment, as the
IP
Title: [Sisuite-users] Re: no devfs support when using 3.5.3
If you compile using the
source from SVN (branches/3.6.x) and use si_prepareclient, it should generate a
working set of binaries. If you're on a Red Hat system, I got some RPMs
you could use.
In regards to rscync, John
may be
ubject: Re: [Sisuite-users] Re:
no devfs support when using 3.5.3
Hi BernardOn Jan 5, 2006, at 12:32 AM, Bernard Li
wrote: If you compile using the source from SVN (branches/3.6.x) and
use si_prepareclient, it should generate a working set of
binaries. If you're on a Red Hat system, I got some RPMs
Hey Andrea:
Do you think you can write up a little doc on the wiki about how to use
LVM with SystemImager 3.6.x?
I think a lot of users will find this helpful!
Thanks,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Andrea Righi
Sent:
Hi Matt:
You might want to give SystemImager 3.5.4 (unstable) a shot and see if
that solves your problem.
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Matt Larson
Sent: Monday, December 12, 2005 8:50
To:
Did you try the newer version of systemconfigurator which I
pointed you to?
Cheers,
Bernard
P.S. You might also consider using a newer version of
SystemImager (unstable)
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jide
OsatuyiSent: Friday, December 02,
Hey Ashley:
FYI, this is already fixed in trunk:
http://svn.sisuite.org/diff.php?repname=systemimagerpath=%2Ftrunk%2Flib
%2FSystemImager%2FUseYourOwnKernel.pmrev=0sc=0
Do you have any other related patches?
Thanks,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
Which version of SystemConfigurator are you
using?
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jide
OsatuyiSent: Wednesday, November 30, 2005 5:19To:
sisuite-users@lists.sourceforge.netSubject: Re: [Sisuite-users]
fstab-sync
Hi
Can you try this one and see if it
works?
http://svn.oscar.openclustergroup.org/oscar/trunk/packages/sis/distro/common-rpms/systemconfigurator-2.2.2-11ef.noarch.rpm
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jide
OsatuyiSent: Wednesday,
Hey guys:
I have been throwing around this idea of firstboot scripts for
systemimager. Basically the idea is similar to the post-install and
pre-install scripts which systemimager currently supports, but instead,
these firstboot scripts are only executed when the node is rebooted (for
the first
Hi Charles:
Have you tried the kernel from Peter Mueller to see if it works?
http://wiki.sisuite.org/SystemImager
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Charles Galpin
Sent: Tuesday, November 22, 2005 9:32
To:
Title: RE: [Sisuite-users] sata_via support
Try this from Peter Mueller, it might work:
http://world.anarchy.com/~peter/systemimager/
Alternatively, you can try the unstable version of SystemImager, 3.5.3, which has better support for SATA hardware.
Cheers,
Bernard
-Original
install_initrd and other options and the configure
tools tells me Im missing e2fsprogs-dev package which I found
nowhere..
:(
2005/11/18, John Jolet [EMAIL PROTECTED]:
that's what we've been using for like 4 months or so.
On Friday 18 November 2005 11:51, Bernard Li wrote:
Unless you have
Title: using a loop mounted .img file as the client image
Hey Dan:
Can you please file a bug at SourceForge stating the OS you
are using and any error messages. I'll try to take a look when I get a
chance:
http://sourceforge.net/tracker/?group_id=259atid=100259
Thanks,
Bernard
Hi Charlie:
You can probably extract them from here:
http://svn.oscar.openclustergroup.org/oscar/trunk/packages/sis/distro/co
mmon-rpms/systemimager-x86_64boot-standard-3.5.3-3oscar.noarch.rpm
Note that this is for version 3.5.3.
Cheers,
Bernard
-Original Message-
From: [EMAIL
@lists.sourceforge.netSubject: Re: [Sisuite-users]
SystemImager on Ubuntu
HiOn Tue, Nov 01, 2005 at 09:45:48PM -0800, Bernard Li
wrote: You guys want to add some notes in the
wiki? [1]http://wiki.sisuite.orgI claim to be an
expert in neither sisuite usage nor wiki editing.Please improve if you
can:http
Hi Dave:
You can get the ia64boot-standard if you rebuild the
SRPM.
Alternatively, if you want to use a newer development
version of SystemImager (which we have found to be pretty stable), you can grab
the pre-built RPMs here:
Title: Re: [Sisuite-users] SystemImager on Ubuntu
You guys want to add some
notes in the wiki?
http://wiki.sisuite.org
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of Jan GroenewaldSent: Tue 01/11/2005 20:55To:
sisuite-users@lists.sourceforge.netSubject: Re: [Sisuite-users]
Andres, What OS are you trying to image?
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Cañada.Andres
Sent: Friday, October 28, 2005 9:48
To: sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users] kernel panic
Title: Re: [Sisuite-users] parted - Error: Can't have the end before thestart!
Hi John:
You can try the
systemconfigurator RPM from here - not sure if it'll help with your problem
though:
I running systemimager 3.5.3 on one cluster. I've 32 bits and 64 bits
nodes. Installation on dell 1425 (x86_64) failed with this message :
Could not stat device /dev/sda
I think this is about SATA disk that are not found .
In src/linux-2.6.10/.config the SATA option is ON.
You need to
Hi John:
If you are booting SIS's kernel/initrd, then this will match up.
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of John Jolet
Sent: Wednesday, August 31, 2005 10:42
To: sisuite-users@lists.sourceforge.net
Subject:
Title: [Sisuite-users] 64-bit imaging
Hi John:
Which version of SystemImager
are you using? The development version 3.5.3 is known to work with
x86_64. This has been tested quite thoroughly under Red Hat systems (RHEL3
and RHEL4) - unfortunately I do not have much experience with Gentoo
for 3.5.3?We're using gentoo because it seems more
efficient and has the most matureand stable 64-bit environment of the major
distros.On Monday 29 August 2005 21:59, Bernard Li wrote: Hi
John: Which version of SystemImager are you using? The
development version 3.5.3 is known to work with x86_64
: Re: [Sisuite-users]
64-bit imaging
Bernard Li said on Mon, Aug 29, 2005 at 07:59:42PM
-0700: For our test cases we do use a x86_64 image server to
deploy x86_64 images, but I do think it is possible to have a x86 image server
to deploy x86_64 images.I use an x86 server to deploy x86_64 images
Title: Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Hi Jan:
You can run dd off the
filesystem of the node being imaged, i.e.
/a/bin/dd (when it is
mounted)
I believe dd was included in
busybox/BOEL in the latest development release (3.5.3).
Title: Re: [Sisuite-users] systemconfigurator --runboot fails (chroot does not see /dev/hda)
Can you post your master
script that is re-generated after you run the:
mkautoinstallscript --image
image --force --post-install reboot
command?
I think you will have better
luck with newer
Perhaps you guys can provide feedback to update the docs?
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Peter Mueller
Sent: Tuesday, August 09, 2005 15:31
To: sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users] I
Title: [Sisuite-users] CentOS 4 / RHEL 4
Isn't that the LVM
notation? Do you need to use LVM?
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of Bobby BrownSent: Tue 02/08/2005 13:38To:
sisuite-users@lists.sourceforge.netSubject: [Sisuite-users] CentOS 4
/ RHEL 4
Hi,I have CentOS
Do you have access to an older box to build SystemImager? If not then you can
try the following unofficial SystemImager RPMs and see if they work under FC4
(I see no reason why they wouldn't, but you never know...)
Please see:
http://sourceforge.net/mailarchive/forum.php?thread_id=7512457forum_id=
8921
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Leandro Tavares Carneiro
Sent: Friday, July 22, 2005 10:54
To: sisuite-users@lists.sourceforge.net
Subject:
Hi:
Thanks for writing the HOWTO.
Can you please let us know what issues you were encountering with grub?
I was able to image RHEL4 on a x86_64 computer with grub as the
bootloader. The SystemImager we used should be pretty close to what is
in trunk, but possibly with some minor modifications.
if it
dies, I verified that it did NOT install any of the boot loader. I
over wrote the MBR and re-imaged with the broken client and was unable
to boot.
When I get a few extra minutes at work I will try and replicate the
issue and send
more details.
Thx,
stoermer
On 7/19/05, Bernard Li [EMAIL
Hey Mark:
When systemconfigurator runs, it generates the error the file
/boot/grub/stage1 nor read correctly which has had me off on a wild
goose chase for 3 days trying to figure out why it's doing
that. I even
tried upgrading to SI 3.4.1 and that didn't help. I
downgraded back to
Hey Mark:
Can you change the setting such that after you use SystemImager to
deploy your node, it doesn't reboot?
In that case you can get a console on the node. Post the contents of
/boot/grub/device.map of the node. This should be somewhere in /a.
I may have a patch for SystemConfigurator
For me it re-directs fine to wiki.sisuite.org.
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Daniel Widyono
Sent: Friday, July 08, 2005 12:19
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] www.sisuite.org
Hey Dan:
You should be able to mount your initrd.img after you decompress it:
cp /tftpboot/initrd.img /tmp
cd /tmp
mv initrd.img initrd.img.z
gunzip initrd.img.z
mount -o loop initrd.img /mnt
Then you can modify the files to your hearts content. After you're
done:
umount /mnt
gzip -9
Kevin, can you let Peter know where you got the driver from? It might
help with your current issue.
Thanks,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Peter Mueller
Sent: Friday, July 08, 2005 13:52
To:
Hey Mark:
Which version of SystemImager are you using?
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Mark Seger
Sent: Friday, July 08, 2005 15:19
To: sisuite-users@lists.sourceforge.net
Cc: Stephen Grandinetti
Subject:
with
thenewer scsi drivers source code, then replace the old aic79xx.o
withthe new one, is it feasible? Anyway, I will try it.)Or, where can I
get the prototype tool?Best RegardsKevin ZengOn 7/8/05,
Bernard Li [EMAIL PROTECTED] wrote: Hi Kevin:
The compute nodes are booted by the SystemImager
These are IBM x330's, and they have PXE-booted in the past
with much older
xcat and sisuite packages (originally installed about 3
years ago), along
with redhat 7.2. I'm now using latest sisuite (xcat not
yet installed) and
RHEL4 clone (Fermi SL4).
Hmm, I didn't do any patching
Title: [Sisuite-users] Re: SATA disks with SystemImager
Actually there is a way
around this... if you mount your initrd.img, there should be a file called
/etc/init.d/rcS - just comment the line which reads "check_version" and it
should bypass the check.
Cheers,
Bernard
From: [EMAIL
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] SATA disks with SystemImager
In
http://sourceforge.net/mailarchive/forum.php?thread_id=7592971
forum_id=10334
Bernard Li wrote:
Did you have any experience with using SystemImager 3.5.2
(CVS/SVN) and SATA HDs?
I tried
systemimager-3.5.2 or
the cvs version. Using lilo with a fedora core 4, I succeed
to create an image,
even to boot but when I try to log in, it always fails, giving me :
login : permission denied.
Quoting Bernard Li [EMAIL PROTECTED]:
Hi:
I assume that besides SystemImager, you are using
Hey Ole:
Did you have any experience with using SystemImager 3.5.2 (CVS/SVN) and SATA
HDs?
Thanks,
Bernard
From: [EMAIL PROTECTED] on behalf of Ole Holm Nielsen
Sent: Thu 23/06/2005 12:25 AM
To: sisuite-users@lists.sourceforge.net
Cc: [EMAIL PROTECTED]
Hi:
I assume that besides SystemImager, you are using SystemConfigurator as
well?
I have the same problem with Red Hat Enterprise Linux 4 - the current
work around is to use lilo instead of grub. Or you can downgrade the
grub RPM which came with Fedora Core 4 with the one from Fedora Core 3
(on
Hi Marc:
Try making a CD instead of a floppy - I believe the newer kernels cannot
fit in a floppy.
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Marc Cozzi
Sent: Friday, June 17, 2005 10:56
To:
-matic boot disks. Or even older versions of SI
boot disks.. If I could find something
close to the 3c905b-txnm cards?
Thanks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Bernard
Li
Sent: Friday, June 17, 2005 1:10 PM
To: sisuite-users
-EP/STEP Suporte Tecnico de EP
Av Chile, 65 sala 1501 EDISE - Rio de Janeiro / RJ
Tel: (0xx21) 3224-1427
Bernard Li wrote:
Have looked at the code in CVS? A lot has changed since 3.5.1 was
released.
I strongly urge you to try it out and if it still has issues. If it
does, please
Hey Ole:
Thanks for writing the guide!
As I've mentioned in my previous email, I actually got it working with
an older version of SystemImager but with lilo (grub doesn't work). I
would appreciate if you can try it out - just to confirm that it does
work with older versions of SystemImager.
Hey Ole:
I appreciate your help ! After a lot of experimentation, and working
interactively on the cloned client at the end of the SI installation,
I'm now firmly convinced that Systemimager v3.4.1 as delivered by the
RPM packages on http://sourceforge.net/projects/systemimager/
*does not
Hi Greg:
Do you know which official kernel version contains that HBA
driver? Using a newer kernel in place of the one which shipped with
SystemImager and re-compiling the binaries may be one way to go about
it.
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL
email and
delete the original
message.
"Bernard Li"
[EMAIL PROTECTED] Sent
by: [EMAIL PROTECTED]
06/01/200
with grub-install?
Cheers,
Bernard
From: Ole Holm Nielsen
[mailto:[EMAIL PROTECTED]Sent: Mon 30/05/2005 12:51
AMTo: sisuite-users@lists.sourceforge.netCc: Bernard
LiSubject: Re: [Sisuite-users] Cloned clients won't boot from
harddisk (Redhat RHEL 4.0)
"Bernard Li" [EMAIL PROTECTED] wro
Okay it seems that you are using SystemConfigurator 2.2.2 already ;-)
BTW, do you have etc/systemconfig/systemconfig.conf in your image? If
so, what does it look like?
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Bernard Li
Title: [Sisuite-users] Cloned clients won't boot from harddisk (Redhat RHEL 4.0)
Hi Ole:
Do you use SystemConfigurator
along side SystemImager? One thing you can try is modify
autoinstallscript.conf and add:
boel devstyle="devfs"
/ right before the config block ends (right before
Title: SATA support in Dell Power Edge 750
You can try to re-compile the binaries but with a newer
version of parted (1.6.17 seems to work). You need to download the tarball
and put it in the src directory and also modify make.d/parted.rul to reflect the
updated version. Re-compile and it
Hi Peter and others:
Would it make sense to create a repository to store all the known
working kernels for different hardware? It would be good for users to
be able to go to a webpage and download specific kernels that are known
to work for their hardware. Not sure if it should show up in the
SI has a wiki?!
Yup - http://wiki.sisuite.org/.
Hosting in one place is a good idea; if you'd like I can host
yours on my page. Yours is for version 3.2.3 with separate
boel_binaries (bernard's own embedded linux :P) ?
I'm not sure if my version is very useful, I would imagine that yours
it into ~si/src.
- put my .config in the right place
(http://world.anarchy.com/~peter/systemimager/linux.i386.config)
- build through SI's 'make kernel'.
Regards,
P
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Bernard Li
Sent
:[EMAIL PROTECTED]]
On Behalf Of Bernard Li Sent: Tuesday, May 10, 2005
5:43 PM To: sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users] New SATA/SCSI/e1000/bcm5700 kernel out
Hi Peter: I'll try it
out tonight - thanks. BTW, did you apply the libata
patches when
Hi Peter:
I'll try it out tonight - thanks.
BTW, did you apply the libata patches when you build the kernel?
Cheers,
Bernard
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Peter Mueller
Sent: Tuesday, May 10, 2005 17:23
To:
Title: Message
Hi Peter:
Thanks for providing the config!
I am trying to re-compile the binaries with a newer version
of parted and possibly a newer version of the kernel. It would help if you
can let us know which OS you were using when you compiled the kernel (distro and
kernel version).
301 - 400 of 401 matches
Mail list logo
