Hello fellow LTSP developers.
It's been a long time since I've posted anything on this mailing list, but
I want you all to know that I'm still out here involved in LTSP.
We've been working on a new wiki for LTSP as the following announcement
explains:
Release announcement:
The new LTSP wiki la
On Fri, Jul 27, 2012 at 8:39 PM, PRP Company wrote:
> For an LTSP network where all the clients show this client boot error,
> can I
> sudo gedit /opt/ltsp/i386/etc/modprobe.d/blacklist.conf
>
> then add
> blacklist i2c_piix4
> to the blacklist and save,
>
> then
> sudo ltsp-build-cl
We’ve launched a new website for LTSP.org with a brand new Wiki. We are
seeing more and more LTSP Success Stories submitted and increase in the use
of technical content and documentation on the Wiki.
For those who have successfully deployed LTSP in businesses, schools, or
elsewhere, please share y
Hello all,
We're evaluating alternatives for the mailing list server.
One thing we've been hearing is that the current list server is slow at
sending out messages.
I'm sending this message at 2:05PM EDT (18:05GMT).
If some of you would look at what time you received this message and
respond wit
Scott Balneaves has spent quite a bit of time PAM-ifing the login manager
to facilitate password expiration. it's not ready for production use yet
but he's made some great progress.
Many of the LTSP developers will be getting together at the dev conference
starting on Oct 4th. I'm sure both passw
I've always been interested in providing some kind of configuration for
LDAP in the server, but I've also looked at is as a barrier to people
getting LTSP up and running.
There's so many choices to make with LDAP and it's not exactly easy to
configure and troubleshoot.
Many people already have LD
Hey all,
I've created a "proposed" LTSP site on StackExchange. If you aren't
familiar with StackExchange, it's sort of a "forum" for asking questions
and getting answers. The answers can be voted Up or Down, so over time,
you'll get a pretty good sense of the quality of the answer to the questio
Get to the console of the thin client, or configure sshd to allow you to
ssh into the thin client from the server.
Once you have a cmd line session on the thin client, you can check to see
if your modules are loaded with lsmod, or see if dmesg shows that it
detected your drive and also you can see
Last week I sent an email announcing that We've created a StackExchange
proposal for LTSP.
Many of you have gone to the site and picked the new LTSP proposal site to
follow. I really appreciate that.
But, in order for us to get this new proposal approved, we need a total of
at least 60 users (As
:
http://area51.stackexchange.com/proposals/46547/ltsp-linux-terminal-server-project
Jim McQuillan
j...@ltsp.org
On Wed, Oct 24, 2012 at 4:43 AM, Chris Roberts wrote:
> On Tuesday 23 Oct 2012, James McQuillan wrote:
> > Each unique person can vote for up to 5 questions and they can create up
I agree with Bettina, using usermod is MUCH better than editing the
/etc/passwd file.
You'll just need to setup /etc/sudoers.conf to allow the php program to run
usermod. Actually, I'd write a script. maybe call it 'disable_user' and
'enable_user'
and setup sudo to allow THAT script to be run.
In your php code:
system( "sudo /usr/local/bin/lock_user $the_user" );
You'll need to create a script called /usr/local/bin/lock_user that
contains:
#!/bin/bash
passwd --lock $1
Make it executable and then, you'll need to add an entry to the sudoers
file to allow www-data to run the
I don't understand the desire to run "LTSP" on an android device.
We developed LTSP as a small "distribution of Linux" to run on fairly
low-end hardware because so many people weren't happy with the current
choices. At the time, the world was largely dominated by Windows 95 and 98.
LTSP was succ
I don't think anybody is running an LTSP server with a 386 CPU, and I don't
think LTSP-5 ever supported thin clients with 386 CPUs.
Linus didn't say he's dropping support for all Intel CPUs, just the i386.
I'm sure the i486's days are numbered, but even back in 1999, when we
started LTSP, we were
boa tarde Luiz,
I share your concern about performance issues on older hardware.
The fact that you are running a cpu at 500MHz indicates it's not an i386 so
you should be fine at least for a while.
Going forward, as long as the CPU is supported by the linux kernel, there
shouldn't be a problem.
'Ending support for i386' is a phrase that needs to be understood carefully.
They're not saying that Intel 32-bit support is going away. There's still
the 486, Pentium (i586) and Pentium Pro (i686).
It's just up until recently, the lowest chip the Linux kernel would support
was the 386. Now, i
Lachele,
I'll try and explain how the graphics works in a thin client environment.
A typical LTSP thin client is just a small computer with a monitor,
keyboard and mouse attached to it.
The thin client has a video card that the monitor is plugged into, and
usually USB or PS2 ports for the keyboa
is there any chance you have 2 DHCP servers on your network?
perhaps once DHCP server is providing the config that is used during the
PXE phase, and a different DHCP server is providing different values to the
kernel.
Jim McQuillan
j...@ltsp.org
On Mon, Jul 15, 2013 at 3:47 PM, James Butler wr
test 1
Some list members have alerted me that their messages aren't getting to the
list.
This is just a test to see if my messages are making it to the list.
carry on.
Jim McQuillan
j...@ltsp.org
--
Get 100% visibility
Robert,
I played with this stuff several months ago, and I found that you can put
stuff in the master_preferences file.
In my case, I created a file called: /opt/google/chrome/master_preferences
and put this:
{
"HomepageLocation" : "http://www.ltsp.org";,
"homepage_is_newtabpage" : false,
"
I like this fix.
I've been tripped up many times on the 64-bit clients looking for their
configs in the 32-bit tree.
Thanks vagrant.
Jim.
On Fri, Aug 8, 2014 at 1:38 PM, Vagrant Cascadian
wrote:
> On 2014-08-08, Michael Pope wrote:
> > Thanks to alkisg on IRC I had to copy my lts.conf file t
If you are using Gigabit ethernet, you don't need a crossover cable.
part of the gigabit spec is to automatically sense whether the devices are
plugged into a switch or directly into another machine.
Jim McQuillan
j...@ltsp.org
On Fri, Sep 5, 2014 at 10:44 AM, Great Devil Singh
wrote:
> On F
By default, all of the X traffic is tunneled through the ssh connection.
ssh will connect to the X server on a standard 600x range port, but it
should be doing it on the loopback interface (127.0.0.1).
But, the Xserver is probably still listening on the public interface
(usually something like
The X server is always listening for client apps to connect up and display
stuff.
Jim.
On Wed, Sep 10, 2014 at 4:46 PM, Vagrant Cascadian
wrote:
> On 2014-09-10 15:10:14 -0500, Vagrant Cascadian wrote:
> > I haven't yet verified for myself if 6007 is open in either the default
> > or LDM_DIRECT
This sounds like a video driver issue on the client.
It's probably using the default Vesa driver.
Unfortunately, I've been away from ltsp too long to remember what you need
to change it to, and how to change it.
Jim McQuillan
j...@ltsp.org
On Fri, Nov 7, 2014 at 4:06 PM, Mike Cammilleri wrot
My first guess would be the graphics drivers that have been automatically
chosen for those thin clients.
If it's using the generic driver instead of the specific driver that's best
for each chipset, you'll see graphic performance like you describe.
Perhaps you can get a shell running on the clien
Mark,
The old LTSP-4.2 source is available here:
http://ltsp.mirrors.tds.net/pub/ltsp/ltsp-4.2/
It's pretty old and unsupported. Also, it's nothing at all like LTSP-5 so
you may not get much out of it.
As for LTSP-5 sources, it's all in Launchpad. If you want to get it, you
will need to fa
I just noticed the http://www.ltsp.org server wasn't responding so I
restarted it.
It's back online now.
That's just a small part of the problem.
Back when I was actively running the project, I think we had a pretty good
website. It was based on twiki and was really easy for anyone to edit.
Lots
28 matches
Mail list logo
