ramdisk that works with a specific kernel by using UYOK (Use Your Own Kernel). The custom
ramdisk can then be used to boot and install %{_build_arch} Linux machines during the
SystemImager autoinstall process.
From: [EMAIL PROTECTED] on behalf of Bernard Li
Sent: Thu 08/12/2005 14:37
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Sisuite-devel
Subject: RE: [Sisuite-devel] Re: boot-standard requires
Okay I'll give that a shot and let you guys know if I encounter
any
problems.
Cheers,
Bernard
> -----Original
Message-----
> From: Brian Elliott Finley [mailto:[EMAIL PROTECTED]]
>
Sent: Thursday, December 08, 2005 14:37
> To: Bernard Li; Brian Finley;
[EMAIL PROTECTED]; Sisuite-devel
> Subject: Re: [Sisuite-devel] Re:
boot-standard requires
>
> Just the spec file I
think.
>
>
> Brian Elliott Finley
> Mobile:
630.631.6621
>
> -----Original Message-----
> From: "Bernard
Li" <[EMAIL PROTECTED]>
> Date: Thu, 8 Dec 2005 14:35:08
>
To:<[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]>,
>
"Sisuite-devel" <sisuite-devel@lists.sourceforge.net>
> Subject: RE:
[Sisuite-devel] Re: boot-standard requires
>
> Hey
Brian:
>
> Do you need to modify the makefile to accomplish this, or
can
> I just go
> ahead and modify the spec file?
>
>
Thanks,
>
> Bernard
>
> > -----Original
Message-----
> > From: Brian Elliott Finley [mailto:[EMAIL PROTECTED]]
> >
Sent: Thursday, December 08, 2005 12:26
> > To: [EMAIL PROTECTED];
Sisuite-devel
> > Cc: Brian Finley; Bernard Li
> > Subject:
Re: [Sisuite-devel] Re: boot-standard requires
> >
> > Yes you
could build an initrd on a node other than the
> > golden. Even an
initrd of a different arch.
> >
> > So, I agree with your
assessment that it should be noarch.
> >
> > Cheers,
>
>
> > -Brian
> >
> >
> >
>
> Brian Elliott Finley
> > Mobile: 630.631.6621
>
>
> > -----Original Message-----
> > From: Erich Focht
<[EMAIL PROTECTED]>
> > Date: Wed, 7 Dec 2005 19:07:18
>
> To:sisuite-devel@lists.sourceforge.net
> > Cc:Brian Elliott Finley
<[EMAIL PROTECTED]>, Bernard Li
> >
<[EMAIL PROTECTED]>
> > Subject: Re: [Sisuite-devel] Re: boot-standard
requires
> >
> > On Friday 02 December 2005 17:43, Brian
Elliott Finley wrote:
> > > Benard and I are contemplating the
packaging of SI 3.5+.
> > We're trying
> > > to make
a decision about how the initrd_template files should be
> > >
packaged. Currently they're part of $boot_package.
> >
>
> > > Here are some options:
> > >
> >
> 1) Create a new package,
>
systemimager-initrd_template, and have
> >
> systemimager-client depend on
it. only the arch for
> > the client in
> >
> question would be necessary, and
this would end up
> > being an arch
> >
> dependent package:
> >
>
> > >
systemimager-initrd_template-$version.i386.rpm
> (for example)
>
> >
systemimager-initrd_template-$version.ia64.rpm
> (for example)
>
>
> > Could I build an initrd on another node than the client?
For
> > example on the
> > master? In that case I might prefer
to have the package as
> > noarch, just in
> > case the master
is of different architecture than the client.
> >
> >
systemimager-initrd_template-x86_64-$version.noarch.rpm
> > makes
sense, too, one needs to put the %Requires: lines
> inside %ifarch
>
> blocks. With multiarch setups one would have to install the
>
additional
> > packages manually.
> >
> > But if
you_allways_ want to build initrd on the client, an
> > arch dependent
rpm
> > is fine, of course.
> >
> > Regards,
>
> Erich
> >
>
>
>
-------------------------------------------------------
This
SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for
problems? Stop! Download the new AJAX search engine that
makes
searching your log files as easy as surfing the web.
DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=ick
_______________________________________________
Sisuite-devel
mailing list
Sisuite-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-devel
