James
[EMAIL PROTECTED] wrote:
>
> Hi
>
> You should take a breath, step back, then RFM and make a working system
> (It works if you follow instructions) then try to change it to suit
> your needs, one step at a time.
I have already done it from the beginning 3 times. Folowing all the
instruct
Hi
You should take a breath, step back, then RFM and make a working system
(It works if you follow instructions) then try to change it to suit
your needs, one step at a time.
> "
> Loadin 192.168.1.1:/HD/tftpboot/lts/vmlinuz-2.4.18-ltsp-1 .TFTP error 2
^^^
> (Access violatio
I forgot to atach my dhcpd.conf.
I'm attaching to my .config file so that you can be sure i'm doing it
right (or not).
Alex Robertson wrote:
>
> Jim
>
> Forget all previus messages on this thread. I got the same error every
> time because i was modifying a dhcpd.conf back-up file. Sorry.
>
Jim
Forget all previus messages on this thread. I got the same error every
time because i was modifying a dhcpd.conf back-up file. Sorry.
Now that i modified the right dhcpd.conf file, workstation just don't
download the kernel.
Take a look at my dhcpd.conf.
The error message shown is:
"
Loadin
So, who creates /tftpboot/lts/vmlinuz-2.4.18-ltsp-1 ??? The kernel
pakage?
[EMAIL PROTECTED] wrote:
>
> Hmm, interesting.
>
> You say that you are using the default kernel that
> comes with ltsp_core-3.0.5-i386.tgz.
>
> The interesting part is there is NO kernel included with
> the ltsp_core
Hmm, interesting.
You say that you are using the default kernel that
comes with ltsp_core-3.0.5-i386.tgz.
The interesting part is there is NO kernel included with
the ltsp_core package.
Jim.
On Wed, 28 Aug 2002, Alex Robertson wrote:
> [EMAIL PROTECTED] wrote:
> >
> > Alex,
> >
> > Which
[EMAIL PROTECTED] wrote:
>
> Alex,
>
> Which LTSP kernel are you using ?
>
> I added the sis900 driver when I build the vmlinuz-2.4.18-ltsp-1
> kernel that is in the ltsp_kernel-3.0.4 package. I'm guessing
> that you are using an older LTSP kernel.
>
> Jim McQuillan
> [EMAIL PROTECTED]
Jim
Alex,
Which LTSP kernel are you using ?
I added the sis900 driver when I build the vmlinuz-2.4.18-ltsp-1
kernel that is in the ltsp_kernel-3.0.4 package. I'm guessing
that you are using an older LTSP kernel.
Jim McQuillan
[EMAIL PROTECTED]
On Wed, 28 Aug 2002, Alex Robertson wrote:
> [EMAIL
[EMAIL PROTECTED] wrote:
>
> Alex,
>
> No need to tag the kernel again. Just use the standard
> ltsp kernel and change your root-path
> statement in the /etc/dhcpd.conf file to point to the new
> directory.
Ok. It worked! But now, while running linuxrc, I get the message:
"
modprobe: sis900
Alex,
No need to tag the kernel again. Just use the standard
ltsp kernel and change your root-path
statement in the /etc/dhcpd.conf file to point to the new
directory.
If you really want to build your own kernel, then make
sure you enable devfs in your kernel config, so that you
don't get that
Here I go again...
Let me explain all the situation.
I use slackware 8.1 - kernel 2.4.18. (server and workstation)
I changed some paths because of disk space. I installed ltsp another
directory. DHCPD, exportfs, and others know this new location. AND I
also created a sim-link in /opt/tlsp point
11 matches
Mail list logo
