What are the basic LTSP server setup to make sure smooth implementation
of LTSP server. Things like locking normal user from doing certain
things such shutting down server .. etc. I m sure there more things need
to been done to reduce surprices which might cause security issue due to
wrong
Has anyone successfully managed to get 3D acceleration working with the i810
driver.
I'm using LTSP 4.1.1 on an Intel D845GVSR motherboard with kernel
2.6.9-ltsp-3.
I think I have done all the configuration things I've been able to find on the
subject. However, when I run 3Ddiag (from xterm
I have the same problem. There is no kernel drm module in LTSP 2.4 or
2.6 kernels for our card. Look in logs... you will see :)
Recompiling kernel may help. It is i830.ko or i915.ko, not i810.ko,
which is included. i830.o is included in 2.4 kernels, but it wants i915
module in my case.
Milan
I have been trying to do the same for the VIA CLE266 boxes we are using
in the company and here is what I have found out:
- in order to enable DRI, you have to (usually) compile load kernel
DRM driver
- use the proper X driver
- It's all useless anyway because DRI is currently NOT supported
Hi,
This is not a problem of LTSP, but problem of Win 2k3.
By default in Win2k3, you can have ony 1 session per user (unlike in
Win2k terminal server).
If there is an attempt to open new session for the same (already logged
in) user, the previous is automagically closed transferring the session
Damodaran wrote:
What are the basic LTSP server setup to make sure smooth implementation
of LTSP server. Things like locking normal user from doing certain
things such shutting down server .. etc. I m sure there more things need
to been done to reduce surprices which might cause security issue
Hi,
The server can be shutdown remremotely.otly by a normal user via kde (nor sure
about gnome or the others). To stop this simply enable the option in the kde
control centre that requires the root password for shuting down the machine.
Dave
Joe Auerbach wrote:
Damodaran wrote:
What are
Is there something about PXE that insists that the TFTP server must be on
the DHCP server's IP, even if you set the DHCP option 66 TFTP server name
to a different IP?
I have a working LTSP test server, I've put it onto my production network,
but disabled it's DHCP server. The main DHCP server
Hi there..
I wonder to know how can we detect the workstation(s)
that logon (and logoff) to the ltsp-server so we can
count how long they connect and.. maybe how much they
sould pay it (cyber cafe oriented)? can anybody tells
me how?
I would recommend using the login tracking and process accounting features of
your default system. Take for example the lastlog command. There are many ways
of automating this.
Cory
- Original Message -
From: slamet budi santoso [EMAIL PROTECTED]
Date: Wednesday, July 13, 2005 9:36
On 7/14/05, Cory Oldford [EMAIL PROTECTED] wrote:
I would recommend using the login tracking and process accounting features of
your default system. Take for example the lastlog command. There are many
ways of automating this.
man last
last will give you time of logging in and logging out
On 7/13/05, Joe Auerbach [EMAIL PROTECTED] wrote:
Damodaran wrote:
What are the basic LTSP server setup to make sure smooth implementation
of LTSP server. Things like locking normal user from doing certain
things such shutting down server .. etc. I m sure there more things need
to been done
12 matches
Mail list logo