A Temporary Internet Lounge
and saved the file. I fixed permissions with:
chmod 644 /etc/rc5.d/S99flashplugin
Once this was done, I pressed Ctrl-D to leave chroot, and then I deleted the history file:
rm /mnt/hda1/source/root/.bash_history touch /mnt/hda1/source/root/.bash_history chmod 600 /mnt/hda1/source/root/.bash_history
Next, I started Mozilla, edited the bookmarks, set the default home to the convention home page and tweaked the default settings. These changes were stored on the RAM disk; to move them onto the hard disk I used:
cp -r ~knoppix/.mozilla/knoppix/ujixazk6.slt/* ↪/mnt/hda1/source/etc/skel/.mozilla/knoppix/ ↪ujixazk6.slt chmod -R 644 /mnt/hda1/source/etc/skel/.mozilla/ ↪knoppix/ujixazk6.slt/*
Now that I had assembled the software, I created the compressed filesystem:
mkisofs -R -U -V "KNOPPIX.net filesystem" -P \ "KNOPPIX www.knoppix.net" -hide-rr-moved \ -cache-inodes -no-bak -pad /mnt/hda1/source | nice -5 \ /usr/bin/create_compressed_fs - 65536 > \ /mnt/hda1/master/KNOPPIX/KNOPPIX
During the above process, I received and ignored a warning message that the filesystem was not ISO 9660. This process was the slow step, taking about an hour to complete on a Pentium II 350. Afterward, I created the CD as a whole:
cd /mnt/hda1 mkisofs -pad -l -r -J -v -V "KNOPPIX" -b \ KNOPPIX/boot.img -c KNOPPIX/boot.cat -hide-rr-moved \ -o /mnt/hda1/knx/knoppix.iso /mnt/hda1/master
From here, I used LFTP to move the resulting file to the support box for burning onto CD-R.
Some issues came up while polishing Knoppix, including the room's layout, power supply and router situation. In terms of room layout, I went with a large rectangular arrangement that left enough space for people to be comfortable, kept most cables from being a possible tripping hazard, placed the switches away from mischief and left a fairly safe place for volunteers to store their backpacks/bags. The cables that did have to cross the floor were covered with heavy cloth tape to stay safe. The downside to this arrangement was that I was limited to having roughly 28 machines in the room.
Before posting room rules, I consulted with the convention volunteer lawyer, Ken Smookler. The result was a sheet that disclaimed responsibility if anything went wrong and reserved the right to remove any being causing trouble (the word being used more out of concern for pets than extraterrestrials, but it legally covered us for both).
There wasn't enough power in the room to support 28+ machines, so a month before the convention I arranged with an electrician at the convention site to have extra outlets installed. In calculating power needs, I assumed 5A per PC (a typical maximum for the PCs I was looking at) and 2A per monitor. I knew the PCs would not consume their rated maximum, so I would have a comfortable safety margin. So I ordered the installation of 16 × 15A circuits (two PCs and two monitors per circuit, one circuit for switches/hubs and one circuit for laptops). This is where most of the Internet Lounge's budget went, and power never was a problem.
For the router, I considered using a Coyote Linux box similar to ones I previously had built. The problem with using a homemade router, though, was the time it would take away from other preparation work. Plus, dealing with failure would require more than running to a shop with the receipt for a warranty exchange. So, I bought a basic D-Link router/DHCP server from an office supply shop that had long hours, located near the convention site.
Six days before the convention I found out what sort of machines I would be getting and was able to start testing hardware. They were Pentium II 400MHz boxes with 128MB of RAM. KDE could have run on them, but IceWM ran great. Four days before the convention, I found out a new sponsor had to be listed on the systems. Three days before the convention, the machines shipped to the convention site. Two days before the convention, I received final approval of the setup from senior convention committee member Lance Sibley, and I started burning CD-Rs, burning a few spare CD-Rs just in case.
The day the computers shipped I got a report that some of the machines had been banged around in transit, and two arrived at the convention site with problems. Although the plan was to have 28 machines, only 26 were available. The day before the convention I did setup with volunteers Robert Eveleigh and Juan Sanmiguel. A few problems turned up, including a bad switch. A call to my office got a replacement, which necessitated buying an Ethernet crossover cable at a nearby office supply store.
Once the convention started the Internet Lounge ran 24 hours a day for the duration. So, I couldn't stick around all the time to watch things, and a number of non-Linux administrators (including Robert and Juan) monitored the room. Thanks to Knoppix, In the event of problems or oddities, I could tell people simply to reset a machine. Because the hard drives weren't being used, this was a fine solution.
Wireless access for the convention had been considered briefly but the idea was rejected for several reasons, including cost. This did not stop wireless access from happening, though. One convention attendee, Keith Lofstrom, wanted wireless access, and he put his money where his mouth was by bringing in an 802.11b wireless hub, a feature that proved popular.
There were grumbles about where the Lounge was located relative to the rest of the convention. Some people wished I had installed a few more pieces of software, including AIM and Yahoo instant messenger clients and automatic updates from a timeserver (some of the PC clocks drifted). There also were requests for a printer, but setting up a payment system to cover paper/toner costs would have been another significant project.
Still, Mozilla and IceWM did not cause any trouble for this crowd. The only real lineup for computers occurred just after the Hugo Awards ceremony, during which awards for the best of the previous years' science fiction were presented. Fortunately, that line didn't last long, and for most of the time the Lounge was busy if not full. Overall, users' reactions were positive from those who had never used Linux, including one person who said this was the best Internet Lounge ever.
Lessons learned: the instant messenger demand surprised me and the overlooked timeserver would need to be looked at in the future. Still, the ability to set up machines quickly and to make tweaks to the setup would not have been possible without Knoppix.
Colin McGregor (firstname.lastname@example.org) works for a charity, does consulting work on the side and has served as President of the Toronto Free-Net. He also has made presentations at the Toronto Linux User Group New User meetings. He enjoys attending, if not always working at, Science Fiction conventions.
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
- Weechat, Irssi's Little Brother
- New Products
- Tech Tip: Really Simple HTTP Server with Python
- Didn't read
4 min 25 sec ago
- Reply to comment | Linux Journal
9 min 25 sec ago
- Poul-Henning Kamp: welcome to
2 hours 19 min ago
- This has already been done
2 hours 20 min ago
- Reply to comment | Linux Journal
3 hours 5 min ago
- Welcome to 1998
3 hours 54 min ago
- notifier shortcomings
4 hours 17 min ago
5 hours 54 min ago
- Android User
5 hours 56 min ago
- Reply to comment | Linux Journal
7 hours 49 min ago
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?