installed the k12ltsp distro with Keith Chandler at Sandwell LEA this pm, its
based on RH7.0, and installs easily (although did have a problem taking the
default partitions) and has everything pre-installed, including support for
all LTSP kernels, although they've concentrated on PXE boots in the US.
the desktop is Gnome (well Helixcode/Ximian infact) and has been configured,
but its still fairly liberal and will need cutting down (remove the games?).
They have also got some default academic like apps (Gnumeric etc) installed.
On discussion this afternoon, would be anybody be interested in a training
day on K12LTSP? (or LTSP more generally), as Sandwell's EMU have offered to
host. No exact date, but soon, also no real cost. its not for politics, more
of a 'run wot u brung' event for schools/LEAs
Red Hat Europe
t:+44 1483 734955 m:+44 7720 079845
As previously stated, it has come to my attention that some people might
not be aware of the intentions of Fen Systems with regard to OSIE, and
might have leapt to their own conclusions. This post is intended to
clarify any potential areas of misunderstanding.
Fen Systems *does* expect that the existence of OSIE will be commercially
beneficial to Fen Systems. Given that we are in the business of providing
Linux-based solutions to UK schools, it is inevitable that an organisation
dedicated to promoting the use of Linux (and other open-source software)
in UK schools will benefit us in some way, whether we want it to or not.
Since we are likely to benefit from the existence of OSIE, it is only
proper that we should also contribute to it. It would be reprehensible if
we were to sit back, playing no active role, and simply enjoy the benefits
created by the work of others (as some people seem to be suggesting that
we should do). As good "open-source citizens" (to borrow a phrase used
recently), we should be contributing actively in whatever ways we can.
The fact that we are a business rather than a not-for-profit group is
irrelevant - free software does not mean "software with no commercial
involvement" and anyone who thinks that businesses have no place in
open-source projects simply doesn't understand what the "free" in "free
We have no desire to "control" OSIE. If the organisation is not seen to
be independent, then it is of no benefit to us or to anyone else. Those
of you who were at the meeting on March 12 will remember that the
independence of OSIE was the first point I made under the heading of
No "control" does not mean no involvement, nor does it mean that we do not
want to have a say in the direction OSIE takes. The independence of an
organisation is assured by having multiple interests represented at all
"levels". It is *not* assured by having specific interests (e.g.
commercial interests) "barred" from involvement. Again, anyone who thinks
that "free" and "open-source" means "non-commercial" has not understood
the concepts "free" and "open-source" and should have a good read through
We will ensure that content we produce for OSIE is not unfairly biased in
favour of our products and services. For example, the current Resource
Library makes no mention of any particular vendor, not even to the extent
of saying (for example) that Fen Systems are working on an improved
graphing capability for Octave. However, we will also endeavour to ensure
that OSIE content is not unfairly biased *against* our products and
services. For example, we would consider it inappropriate for what is
currently the section on "How to get open-source software" to change so
that it spends twelve pages discussing downloading, burning CDs,
installation procedures, installation troubleshooting etc. and then
mentions, as a footnote, "by the way, you can also buy ready-made
systems". If there is a question in the Knowledge Base asking "how can I
write a PHP web-page to act as a form for my complex relational database?"
then we would consider it appropriate to post an answer that, alongside
giving some pointers on how to get started with PHP, mentioned that Fen
Systems would be prepared to develop such a page under the terms of its
UNIQUES service. After all, not everyone wants to spend several days
learning a new programming language if they have the alternative of paying
£50 to get someone else to do it so that they can concentrate on the 1001
other things on their "to do" list.
We think that it is in the interests of everyone that OSIE remain
unbiased, and unbiased means that there is no bias in any direction - it
does not *just* mean "not biased in favour of commercial organisations".
I hope that this is enough explanation - if anyone wants me to clarify any
of the points then please e-mail me.
BTW, OSIE discussions are now starting in earnest on the osie-general
mailing list (Kevin has started the ball rolling). If you do want to be
involved in OSIE, please join the list by visiting
This is my final OSIE-related post to this list, as discussion has now
moved to the list on SourceForge.
> From: Giles Nunn <giles(a)satproj.org.uk>
> It depends which window manager/desktop you use. In principle if you make
> the menu configuration files root-writeable only, then they can't change
> anything. There is normally a skeleton directory which is copied when
> creating each user. Try /etc/skel.
Something along the lines of:
chown root.root directory_name -R (make the files owned by root, group
root, and apply changes recursively)
chown go-w directory_name -R (remove write permissions for group and other
users, and apply changes recursively)
Should do it, I think :)
I wonder if anyone else has had problems getting the ltsp download from either
the ktsp link or direct from sourceforge - I get unable to connect to database
Derek Harding, (BA MIAP)
ICT & Network Manager
I would like to say that we ought to give ourselves time to
hack out exactly what we want to acheive at another meeting
though ... It is really nice to meet people face to face, but now
that the thing is getting off the ground, I would say that to
make it worth the effort of travel/organising we need a really
solid agenda with specific aims this time. Last time was
great as a launch pad ... but we need to be more focused
Because of this, I think that we don't need one too soon,
I think we need time to hack out some details first.
I have several ideas for ensuring that the discussions
are as productive via email as we can make them (as I
am sure other people have too), but lets talk about
that on the osie lists ...
(probably give people until tomorrow night (Thurs) and
then start talking on osie ... ?)
Slight problem here....
Not to be awkward but the web addresses www.osie.org.uk or
www.osie.org. are not accessable to anyone using the N2H2 BESS filtering
Tel : 01554 750661
Fax : 01554 758255
1. The contents of this email may be snooped on by
interested government parties for unknown purposes!
Regulation of Investigatory Powers Act, 2000.
2. The opinions expressed in this email are personal
and may not be shared by Bryngwyn School.
> Would it not be sensible to organise another event
> pretty soon with an action plan and get some lead
> names against those actions ?
The reason I am pushing the use of sourceforge to manage
the project, is that we can get the core people (who want to
take an active role) listed.
Once we are at this stage, we can start assigning tasks
to people and then each 'job' has an owner. These tasks
would not (in the first instance) be programming/writing,
but things like 'sort out who is to host it', 'sort out
the domain name', 'formulate a list of aims for OSIE', etc.
Once a task has an owner to coordinate it, it is likely to
be discussed and resolved, without the discussions
just 'drifting off'.
The problem with free-for-all mailing lists, is (as you
say) it is too easy for the detail to be lost, and often
(in my experience on lists in the past) subjects
'drop out' of favour, without being resolved ...
So - when sourceforge is up and running, I suggest
all key people who are prepared to spend a little time
doing something, get on the mailing list, and we start
to discuss the structure of the project.
We would first (I guess) start by trying to list appropriate
sub-project areas, so that tasks can be allocated.
This would be the key functions, required - I don't
really want to start discussions here (but I will ?),
but this could include things like the server (hosting, web
technology, etc), web site itself (structure/content),
PR, policy, etc.
This way, people have something to own and work
towards, and the thing moves forward.