On Tue, May 29, 2007 at 11:18:39AM +0200, Jan Kunder wrote:
> X. Using Debian etch + ltsp5 (trying)
> TC=thin client
>
> On 5/28/07, Scott Balneaves <[EMAIL PROTECTED]> wrote:
> > On Mon, May 28, 2007 at 05:55:04PM +0200, Jan Kunder wrote:
> > > Hi.
> > > LTSP5 - should I use nbi, vmlinuz or initr
On 5/28/07, Scott Balneaves <[EMAIL PROTECTED]> wrote:
> On Mon, May 28, 2007 at 05:55:04PM +0200, Jan Kunder wrote:
> > Hi.
> > LTSP5 - should I use nbi, vmlinuz or initrd images?
>
> The initrd images are the initial ram disk.
>
> The dhcpd.conf file should take care of that for you: if you're bo
X. Using Debian etch + ltsp5 (trying)
TC=thin client
On 5/28/07, Scott Balneaves <[EMAIL PROTECTED]> wrote:
> On Mon, May 28, 2007 at 05:55:04PM +0200, Jan Kunder wrote:
> > Hi.
> > LTSP5 - should I use nbi, vmlinuz or initrd images?
I discover that using vmlinuz/initrd will give me - not valid i
On Mon, May 28, 2007 at 05:55:04PM +0200, Jan Kunder wrote:
> Hi.
> LTSP5 - should I use nbi, vmlinuz or initrd images?
The initrd images are the initial ram disk.
The dhcpd.conf file should take care of that for you: if you're booting
with etherboot, it will use the nbi image, if you're booting
Hi.
LTSP5 - should I use nbi, vmlinuz or initrd images?
For what reasons are there the others?
I'm booting mainly .zdsk from FDD, sometimes PXE or etherboot.
Thank you for answer
--
Jan Kunder
-
This SF.net email is sponsor
