Hello,
I think it will work under FreeBSD,
CMMIW thereis no binary file (daemon) from LTSP running on server...
all binary files are execute on client side..
and the application run on the server side allready available on FreeBSD,
such as dhcp server, nfs server, xdm and so on...
so the
Hello Jim
THe Lts_xcore file which is more than 10 mb in size ,
We are unable to download the file cause the server doesnot support
resumes.
Please do the needful cause here at our end it is very difficult to
download the file which is more than 10mb at one instance.
thanks
Regards
DK
___
How i can used by own Tagged Kernel with LTSP 3.0?
Which version of MKNBI utility.?
Which MKNBI utility version will work to creat the Tagged image for LTSP
3.0
When i used version 1.2.0 it basically works with default /tftpboot
directory.
Regards
DK
_
DK,
You should find what you need in the LTSP initrd_kit.
Also, in the LTSP-3.0 documentation, there is a chapter on building
kernels. You can do it with or without the initrd.
Jim McQuillan
[EMAIL PROTECTED]
vcare wrote:
> How i can used by own Tagged Kernel with LTSP 3.0?
> Which version
DK,
hmm, "do the needful". I wish I could,
but the site is managed by SourceForge, and there
is really nothing I can do. I've posted problems
on their support page, but I get no response.
I'm working on a plan to host the site myself, which
will give me complete control over every aspect of th
DK,
I'll take a guess here and say that you are probably not mounting
the /opt/ltsp/i386 directory as the root filesystem.
Check your root-path entry in the dhcpd.conf file.
Jim.
vcare wrote:
> Hello Jim
> As per u said i upgraded the version to 3.0
> but it gives the error after mounting th
Jeff,
I'm pretty sure that it has been done.
You just don't have the install scripts. Which means you will
need to setup the services, like DHCP, TFTP, NFS and the Display
manager manually. Other than that, it should drop right in.
Jim McQuillan
[EMAIL PROTECTED]
Jeff Lacy wrote:
> Hello E
Hi, Jesper,
I had numerous problems with ltspsound as it appears on the contrib
site. Also, it wasn't meant for LTSP 3.0.
If you happen to be using RedHat I had a flawless install of the sound
package provided by the K12LTSP guys:
ltsp_sound-0.1c-8.i386.rpm
at:
ftp://k12linux.mesd.k12.or.us/
LTSP Rocks,
That being said, My application running on the server needs to
know which workstation it is being run from so that I can
configure certain features that are work station specific.
Is there a call/routine/program/scheme that I can call to determine
which station the application was st
It is said on the help of ltsp :
"With older versions of LTSP (2.08 and earlier), lots of directories were
exported on the server and mounted by the workstation. Directories such as
/bin, /usr/bin , /lib and /usr were exposed to the workstation.
The problem with that scheme is that it only works i
On Fri, 28 Dec 2001, Serge B Bromow wrote:
> LTSP Rocks,
>
> That being said, My application running on the server needs to
> know which workstation it is being run from so that I can
> configure certain features that are work station specific.
>
> Is there a call/routine/program/scheme that I
Serge,
The DISPLAY environment variable will tell you the workstation name.
If you do echo $DISPLAY
you will see something like "ws001:0.0" you can extract the
hostname from that using awk or cut or a handfull of other
utilities.
Take a look at the LTSP 3.0 documentation for starting
local app
right after abandoning using a separate DHCP from
terminal server, i'm going to combine the two on a different network, though,
what i'm wondering, can i allow my terminals to log-into a server, which they
can only physically access through the terminal server?
i.e the main part of the networ
On Fri, 28 Dec 2001, James Vasey wrote:
> right after abandoning using a separate DHCP from terminal server, i'm
> going to combine the two on a different network, though, what i'm
> wondering, can i allow my terminals to log-into a server, which they
> can only physically access through the term
I have been attempting to get sound working with ltsp 3.0 for some time. I
have ltspsound-0.1c. I am running RH7.2 on the server. The server has an
integrated i810 sound module. The workstation has an integrated cm8738
device.
I modified it to deal with the ltsp 3.0 structures. I manually crea
Plenty of references to this problem on the net, but I'm still short of
an answer to my problem. I'll appreciate any pointers from this list.
Data
RedHat 7.2
ltsp_core-3.0.0-1.i386.rpm
ltsp_kernel-3.0.1-0.i386.rpm
Client loader firmware:
Intel UNDI, PXE-2.0 (build 071) for Realtek R
Russ,
For PXE, you need the un-tagged kernel. That is in the ltsp_initrd_kit
package. You'll also need to build the initrd image.
I really should build a PXE kernel package, but I don't have any
PXE nics to test it with.
Thanks for telling me about the gdm_init_default.tmpl file, i'll have
t
I have been trying to get the NVIDIA kernel drivers (NVdriver) and
accelerated GLX working with ltsp 3.0. I followed the directions by Byron
Poland but I will first post my questions here before bothering him
directly. I had to modify the process somewhat since his instructions were
based upon
Rob,
The 2.4.9 kernel sources that I used to build the LTSP kernels includes
the NFS-Swap patch. I'm guessing that your 2.4.9 sources don't include
that. So, any module that you create may or may not work with the
standard LTSP kernel.
What I think you are going to need to do is go all the way
This error message means that you are trying transfer the lts
kernel directly. In PXE booting, this is not allowed.
You must first download the network bootstrap program (nbp) or
PXE loader BEFORE you download the actual kernel.
The PXE loader cannot be greater than 32K in size otherwise
yo
When using an etherboot or BOOTP boot ROM network booting is
quite straightforward:
The client PC contacts the DHCP or BOOTP server to get its IP
address and the name of the boot image file (ltsp kernel) to transfer down and
execute. The client PC uses TFTP to download the ltsp kernel from t
21 matches
Mail list logo
