Installing Libranet 2.0
Libranet 2.0 now comes on two CDs, and installation time was exactly one hour on my lab rat system (Celeron 850MHz, 320MG, ATA/100 Maxtor IDE HD, ATI Xpert 98 video, AC97 on-board sound chip.)
Since lab rat and my other systems use Caldera's GRUB for booting, I preconfigured /boot/grub/menu.lst to add a chainloader entry for the new Libranet:
chainloader = (hd0,7)+1,
because my new Libranet boot partition would be hda8 when created. I did this because Libranet needs to reboot in the middle of its installation.
Partitioning is still accomplished by cfdisk, but Libranet 2.0 no longer insists on a separate /boot partition. I prefer to use /boot but decided to follow the recommended partitioning scheme. Reiser FS is the default; no other option was offered. I do not know at this time if it is even possible to use ext2. I'll do another install later and customize the partitioning a bit.
After writing the new partitions, Libranet inquired if I wanted to let Libranet take over booting. I declined, and Libranet then recommended making a boot floppy. This is an improvement over 1.9.1 and a feature well thought out. Libranet then rebooted.
At this point, I had to insert CD1, and it immediately requested that CD2 be installed. During the package installation, I had to swap CDs a couple of times, which was a bit of a nuisance. When all packages were installed, the system booted into the new kernel and began configuring the hardware.
Libranet correctly autodetected my mouse and video card. I would recommend manual configuration, though, because it set the monitor at a very conservative default, only a 640 X 480 display.
Audio was correctly configured (on-board AC97, in my case). Libranet also detected my CD-RW drive and volunteered to set up SCSI emulation. Network configuration(in my case, just dial-up) followed. Voilá.
The first KDE came up at 640 X 480, as mentioned above, and I had to fiddle with X a bit to get 800 X 600. The problem was solved by manually setting the monitor scan rates. By the way, Libranet 2.0 comes with KDE 2.2.2 with KOffice 1.1.
Libranet also now uses CUPS as its vice apsfilter as well as its printtool. Printtool did not work for me with 1.9.1 but apsfilter did.
All in all, Libranet is a very pleasant Debian installation. It still boots remarkably fast despite the 2.4.16 kernel and KDE 2.2.2. The installation is still not ideal for newbies, it remains the domain of the Linux user who understands the mechanics of partitioning. Adding Storm's partition utility would be a big enhancement. Adding LIZARD would make it a dream.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Returning Values from Bash Functions
- Parsing an RSS News Feed with a Bash Script
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide