Slashdot Mirror
Feasibility of Linux for Public-Access Labs?
Benanov asks: "I'm doing a literature review on the Feasibility of Linux for a public-access lab (i.e. not Computer Science students at a university but instead the entire student body would have a login), and I haven't found any detailed studies about any places where this is actually done. If you know of any citeable sources about studies / reviews, I'd really appreciate it."
I have setup a general access lab using linux and LTSP, but it was only for 16 highschool students, so I am not sure how relevant to your quest. I would recommend looking for studies regarding LTSP.
Jamie Zawinski has produced a nice document describing how he did it, problems he faced, etc.
[LINK]
Carnegie Mellon has a large network for about 5,000 current undergrads, 1,000 current graduate students, and hundreds of staffers (not to mention 'miscellaneous' accounts). Most people use it to log into Windows or Macintosh systems on campus, since that's what they're used to. Furthermore, the default window manager on Linux and Solaris is mwm (Motif Window Manager), which is absolutely horrible. Among other things, it completely ceases to work if NUM LOCK is on. There's been talk about switching over to GNOME as the default, but as of now people have to ask each other how to switch to Windowmaker, FVWM, or the current GNOME environment.
One time early in the academic year, I noticed a user had forgotten to log out. In the xterm that had been opened with mwm, I saw:
% netscape
% netscape
% netscape
% netscape
% aol
bash: aol: command not found
% aol
bash: aol: command not found
% aol.com
bash: aol.com: command not found
% aol.com
bash: aol.com: command not found
% netscape.com
bash: netscape.com: command not found
Make all the jokes you want about LARTing the newbies, but there were absolutely no options on screen. Furthermore, there are no solid equivalents for popular Windows or Macintosh software packages on Linux or Solaris. IE for Solaris is lackluster compared to Windows, Mozilla is still unreliable and doesn't render some sites properly (they were designed for IE; live with it), GIMP is no substitute for Photoshop, and StarOffice is still nowhere close to Microsoft Office.
For more information, click here.
The SEUL is an organization for using Linux for education. There's even a case study section.
What you're describing has been the way
things have worked at MIT for the last
18 years (although with various Unixi,
now including Linux) starting with Project
Athena in the early 80's. Athena is where
we get X Windows and Kerberos.
The University of Texas at Dallas does it. There is a lab full of Red Hat Linux computers and Sun Ray terminals.
Though their web site is a bit sparse on details, you could probably shoot an email to a member of the staff. They're friendly people, and I'm sure they'd be willing to help you out.
She's your average windows user, don't ask her about hardware or drivers she just wants browse the web etc.
She had no trouble logging in through kdm.
she had no trouble using the default kde3 setup. All this with no help from me (i wasn't even watching)
She can check her email, browse the web, listen to music and print stuff out (thanks cups + kdeprint).
A couple of months went by, I haven't watched her use it at all...
I asked her the other day, so how do you like linux?
her answer: "It's just like using windows" and "I like the way it looks".
Seems to me unsophisticated users aren't able to set up a kde3 box but they are sure able to use one.
Liberty.
There's a small library near my office where there are four public access terminals. Historically they all ran Windows, but just for a laugh the sysadmin put Linux on one of them; and the users avoided the Linux machine like it was radioactive. They didn't seem to like the "weird" web browsers that it came with (Opera and Mozilla), and they had a hard time adapting to the application launcher, however trivially it seemed to differ from the Windows "Start" button. Non-technical people prefer familiarity and ease of use above all else when using a computer.
Toronto-area transit rider? Rate your ride.
For more than 10 years, practically all university students have gotten a UNIX login, and universities have been full of public terminals for students in labs and in hallways. In some richer universities, they have even had *oooh* X-terminals.
The machines have usually been Sun, but I don't think Linux would be overwhelmingly different from them...
So forgive me if I don't quite understand the question. UNIX has been a feasible solution for all students for years, and there's little reason to believe Linux wouldn't be.
The Carleton University EngSoc Project is a wholly student-owned and student-run UNIX network at Carleton University in Ottawa, Ontario, Canada. Once the largest Linux userbase in the world, they've provided Linux shell accounts to every undergraduate Engineering student for at least 7 years.
Since 1996, they've offered a Public Access Lab using donated hardware and space provided by the University. They started off using 486 machines that booted RedHat 3 and NFS mounted from a blazing P90. Then they moved on to using NCD X-Terms. In 1998, Corel Computer donated Netwinder systems for use as the PAL workstations. In 2000, the lab sustained water damage from construction on the roof, and the Netwinders were replaced with ThinkNIC thin clients.
But we don't have any useful literature to provide.
The University of Cambridge have a system called the public workstation facility. This is comprised of machines in many departments and colleges which can authenticate against a single database, and which provide homespace and so on. I understand that some of these machines are now dual boot between NT/win2k and a home grown linux. More infomation is here.
"The new wave is not value-added; it's garbage-subtracted" - Esther Dyson, Dec 1994
1) Use Mandrake. Its the simplest install, and in an educational setup the extra apps that it has can be beneficial, also, due to the wide range of users, having all of Mandrakes bloat can help people find programs that they will find useful.
2) Use KDE/GNOME. Ideally, set it up to boot into X, have KDE/GNOME both installed and the users can select the one they want.
3) Lock down permissions tighter than a Vatican nun.
These tips will produce a perfectly usable system, fairly sturdy against morons trying to(or accidentally) screw up the system or introduce viruses or what have you. And make sure to review the logs, paying special attention to those who use the root account, either with su or by directly logging in
Having been responsible for a school computer lab, I say screw those users. They can use what I offer them or they can go somewhere else. I lost count of the number of times I had to re-image my relatively few machines because some idiot decided they absolutely had to have AIM (which hosed one of the math programs we used, which was the actual purpose of the lab).
What are open school labs for? Internet chat? No. Games? No. The purpose of open labs is to provide computers for people who can't afford their own so they can get their work done. That means word processing, spreadsheets, maybe some web browsing. All of those things can be done using Linux and various free packages. They need to edit or print out their MS Word document that they wrote at home? OpenOffice will do that just fine. The only problem I've ever had with it handling MS documents was some wrong background colors in an Excel spreadsheet, which is easily fixed.
As for the confusion, that's what lab assistants are for. "That icon is the web browser, that one is the word processor..." Quick and easy, and exactly the sort of brain dead stuff every lab assistant has to deal with all day, every day, regardless of Operating System.
For the few people who absolutely have to have Windows or Mac programs, have a few specialized labs set up for them. That's neither new nor different in a college environment, where just about every department has at least a small lab with some computers set up for the specific needs of the students taking those classes.
If a student wants to use a program not offered in the open lab, they can go find the department that would use that software and make an arrangement, or they can get their own damn computer.
Under capitalism man exploits man. Under communism it's the other way around.
The University of Notre Dame and University of Michigan both use an AFS/Kerberos set-up for large volumes of accounts.
Notre Dame offers accounts on their Solaris/SPARC machines to every student at the university. Michigan's CAEN is also an AFS/Kerberos system for the whole College of Engineering.
MIT's Athena project is pretty interesting (and also partially uses an AFS/Kerberos scheme), but it probably won't help you set up a quick public network of Linux machines since it focuses more on the research side of things (not to mention the fact that it's been actively worked on since 1983!).
In general, you will probably want to decide between an AFS/Kerberos set-up or an NFS set-up.
With AFS/Kerberos, you as the administrator would directly control a pool of servers ("Vice") which physically contain the data in every user's account. The client machines ("Venus") would get temporary "tickets" from the central Kerberos server (which you also control) to access their accounts which are stored on Vice.
In the NFS scenario, the physical location of accounts is totally decentralized and distributed across all the machines that users actually work on. This means less work for you as an administrator, but it also means less security since random users' data is actually stored on the disks of the computers in the user pool (in AFS, Vice machines are considered to be "locked in closets" to which only the administrators have physical access). It's good to remember a golden rule, "physical access to a computer always implies root access." Using a tomsrtbt disk for example, you can change the root password on just about any Linux machine with a floppy drive.
Since Vice (in the AFS scheme) computers are presumably kept behind locked doors, you avoid this type of problem. However, AFS is harder to maintain, and you probably have to pay Transarc for a commercial version.
For more info on AFS/Kerberos and NFS, I recommend surfing the ACM Digital Library, in which you can find the seminal papers on these various technologies (if you're an ACM member and have access). You may also be able to find case studies there (which I found to be surprisingly hard to find on the web).
I know this was meant to be "funny" but the last few releases of RH ship with basically everything off by default except for an ssh-server. And if ya can't trust OpenSSH, what CAN you trust? :)
The Free desktop that Just Works
it's interesting.
We moved our 15 year old son to a SuSE distribution last year. He had issues because he wasn't sure how to get to his network drives and couldn't get Starcraft running, but after a couple months he was able to install Wine and get Warcraft going (didn't get Starcraft going, much to his dismay).
Four months ago we moved our 8 year old daughter to the same SuSE distro - took away her Windows 98 and made her quit cold turkey. We configured KMail and let her go. She's had NO help and she can create documents, print web pages, browse, and runs some of the KDE games. No complaints from her at all.
So can people get used to it? Even non-geeks? Sure. If an 8-year old child can do it, I would think a college student, regardless of their general computer competency, should be able to do it as well.
I don't have a solution, but I certainly admire the problem.
Even relatively unsophisticated users can help out with routine maintenance. Plan to be able to allow an automated method (net or CD) to restore default files and configurations or to do a fresh install. This allows people with relatively few technical skills to restore machines or put the icons back.
Don't forget to put a password on the bootloader and / or BIOS so that it's less easy to fiddle with the machine. You want it to boot up normally from the HD or net each time, but not allow custom kernel parameters or booting from the CD, floppy, or unintended places on the net. You may also want to mount some or all of the local file systems read only, to slow the rate of decay. Suse, RedHat, and Mandrake are better each time, but all still have a lot of extra (troublesome) packages mixed in with the default installation. Keep user profiles and home directories on the file server(s).
Find out what the students will be doing and pick relevant packages (Mozilla, Opera, XMMS, xpdf) and be sure to pick out relevant default settings. A lot of the principles listed on Jakob Nielsens's web site are relevant for a desktop as well.
One university I saw last fall in Norway had all of their "MS-Windows" machines running Linux with Metaframe or Wine or something, so that's a good work around for legacy apps like MS-Excel. The University of Michigan has one of the better computing environments I've seen.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.