it'll work.
Cheers,
Bernard
From: [EMAIL PROTECTED]
on behalf of B. Erdelyi
Sent: Fri 03/02/2006 20:22
To:
sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users]
Problem with mkautoinstallcd tmpfs
Bernard,
My thinking is that for
whatever reason
this by starting
with the initrd.img file under the standard boot i386
directory.
Sorry for the premature post, hope this
will fix the problem.
Thanks,
Bela
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi
Sent: Saturday, February 04, 2006 12:35 AM
Bernard,
I finally installed and tested the new
build. One problem has gone away
which is the setting of append options.
By specifying the tmpfs size and inodes in the append string they now get passed on
to the syslinux.cfg file without having to modify the
script.
However, the
@lists.sourceforge.net; sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users] Problem with mkautoinstallcd tmpfs
Are you using LVM?
Cheers,
Bernard
From:
[EMAIL PROTECTED] on behalf of B.
Erdelyi
Sent: Fri 20/01/2006 11:11
To: sisuite-users@lists.sourceforge.net
Subject
that it
doesn't work for you. Can you show me the output of 'rpm -qa | grep
systemimager'?
Also, are you on x86_64
or i386?
I tested it on i386,
perhaps you are on x86_64 and there is a bug in the code?
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of B
: [Sisuite-users]
Problem with mkautoinstallcd tmpfs
And you cannot PXE-boot?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi
Sent: Friday, January 27, 2006 11:41
To:
sisuite-users@lists.sourceforge.net
Subject: RE: [Sisuite-users]
Problem with mkautoinstallcd tmpfs
but not yours - as far as I know we haven't changed the code
to si_mkautoinstallcd for quite some time.
Try hardcoding for now.
Cheers,
Bernard
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of B. Erdelyi
Sent: Friday, January 27, 2006 11:55
To:
sisuite-users
Message trimmed so it will post.
Bernard,
I will download the RPMs
and reinstall again, but this is the same Oscar site I downloaded from in the
first place. I wouldnt
expect a miracle.
I will however not be
able to do it until Tuesday, which is the earliest I can return to the
Are you using LVM?
Cheers,
Bernard
From:
[EMAIL PROTECTED] on behalf of B.
Erdelyi
Sent: Fri 20/01/2006 11:11
To: sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users]
Problem with mkautoinstallcd tmpfs
Hi,
I am attempting an image install
with si_mkautoinstallcd using SI 3.6.3
?
Cheers,
Bernard
From:
[EMAIL PROTECTED] on behalf of B. Erdelyi
Sent: Fri 20/01/2006 11:11
To:
sisuite-users@lists.sourceforge.net
Subject: [Sisuite-users] Problem
with mkautoinstallcd tmpfs
Hi,
I am attempting an image install
with si_mkautoinstallcd using SI 3.6.3
Hi,
I am attempting an image install with si_mkautoinstallcd
using SI 3.6.3. The tmpfs mounted as / is not large enough to create the entire
file structure. The process ends
with tmpfs 99% full.
I have attempted to specify the append option to si_mkautoinstallcd with various values
Hi,
We are marching ahead with our experience with SI. A previous issue with device creation
was fixed following Bernard Lis direction to use mknod. Here are the commands inserted in the
master script after the disk enumeration process in case someone else needs to
do the same thing:
Hi,
I believe I sent this message to the wrong list originally,
so I am reposting it.
Thanks to Bernard Li we got over the first problem we had,
which was solved by using SI 3.6.3 instead of 3.6.2. Now we are facing a new problem.
The target client is booted from an autoinstall
to to create the
ramdisk for the node sucessfully. However, if I run systemconfigurator
manually on the node again after it failed, it works fine...
Please let me know how it
goes.
Cheers,
Bernard
From:
[EMAIL PROTECTED] on behalf of B. Erdelyi
Sent: Mon
Hi,
I am using SI 3.6.2 on a HP Proliant DL360 with two 73G SCSI
drives running RHLE 3.1. The client
preparation is started by issuing the command while logged in as root:
si_prepapre client server
servers IP addr
The process starts OK up to the following point:
tar C
15 matches
Mail list logo