Hi...
My problem got solved, here is the solution.
Solution:
While I was searching for the solution of this problem, I saw almost same problem posted on syslinux users mailing lists. Here is the link (http://syslinux.zytor.com/archives/2007-February/008075.html ) and this problem got solved by in
Problem Solved (Booting From Local Hard drive)
Hello... I have a Linux Cluster of 64-nodes withOSCAR version: 4.1 Linux Distro: Red hat 9
Pxelinux version: 2.00
There is a problem which Im trying to solve for almost a week but stillno results.When I boot a client from the network, after finis
Yes I have removed the /selinux/* from the image however I'm waiting for
some new
machines to try again.
I agree that adding the patterns would be the fast solution.Of course the
best solution
would be to have mount/mtab show all mounts ... I could open a ticket
with RH however
I'm not sure
On Feb 20, 2007, at 2:39 PM, Bas van der Vlies wrote:
> The debian packages are available at:
> ftp://ftp.sara.nl/pub/outgoing/systemimager
>
> I have only tested the release with rsync and i could reinstall a
> node.
> In the systemimager-server package are also the monitord and the
> bittor
> Kenneth Jacker
> Tue, 13 Feb 2007 10:15:22 -0800
> ar> But... why do you have /lib64 if your machine is a i686???
> That I never found out ... :-(
> After removing the the /lib64 files, I rebuilt SI and it worked!
> The last problem was finally solved.
> -Kenneth
Looks like I got bitten
[EMAIL PROTECTED] wrote:
>
> Andrea,
>
> Find below the autoinstallscript.conf.
>
> What appears to have happended is that /selinux was imaged and then
> propagated to the
> new machine. By removing /selinux files, creating /.autorelabel and
> rebooting /selinux was
> properly mounted and 'fix
