Best of Technical Support
I want to configure RHL 6.1 both as a server for a small home network (eth0) and as a dial-up client to my > ISP using dhcp (ppp0). What should my network configuration (i.e., DNS, gateways, routes, etc.) look like? —Tom Dolan, firstname.lastname@example.org
You need several things. We have little space here to explain everything, so instead I will point you to the documents that should clearly explain each step: 1.- Set up your LAN: www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Networking-Overview-HOWTO.html www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Net-HOWTO.html 2.- Hook up to your ISP: www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/ISP-Hookup -HOWTO.html 3.- Set SAMBA (if you have Windows PC's on your local net): www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/SMB-HOWTO.html www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Windows-LA N-Server-HOWTO.html 4.- Some security won't hurt: www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Security-HOWTO.html—Felipe E. Barousse Boué, email@example.com
I just installed Red Hat 6.2 and it worked fine. When booted, my system prompted LILO and boot Linux in Red Hat. I changed LILO to boot DOS. Now when I boot my system I get a C prompt. How do I get my Red Hat back? —Pablo, firstname.lastname@example.org
You should use your Linux boot floppy to reboot under Linux. Then edit your lilo.conf to set up dual boot and validate by typing lilo as root. For example:
boot=/dev/hda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=linux image=/boot/vmlinuz-2.2.14-5.0 label=linux initrd=/boot/initrd-2.2.14-5.0.img read-only root=/dev/hdb1 other=/dev/hda1 label=dos
--Pierre Ficheux, email@example.com
I am having a problem with my end users trying to receive and send their mail. My mail server is working under Linux Op. All users receive the message, The server could not be found (Account "Sendmail" SMTP Server; mail, Error number 0x800ccc0d). —Walter Minja, firstname.lastname@example.org
Because of the error message you mention, it looks to me like your users are using a Windows client. You need to properly set up. For outgoing mails, set the SMTP IP address on each PC to the IP number of your Linux box in your local area network. For incoming mails, the POP IP address should be set up with the same IP address of your Linux box. Bear in mind that POP3 service must be installed and enabled (with an uncommented “pop-3” line in /etc/inetd.conf). —Felipe E. Barousse Boué, email@example.com
I cannot get the rawrite program to work on any of my systems. I tried the autoloader from the Corel distribution, but all I am able to do is get to the point where they give the option to either install from the CD or create a boot disk. When the option to create a boot disk is selected, there is an error of some sort with the system not being able to transfer the boot image to the floppy. When the option to install from the CD is chosen (I have ensured that the computer's bios has the CD boot option selected), it reverts to the other boot options (floppy or C: drive). I have tried executing the rawrite program after booting my system with a Win95 boot disk but have no luck with either distribution.
My computer systems are all intel cpu-based, and the distributions I have are the i386 distributions. —Robert Cordner, firstname.lastname@example.org
Assuming all files were downloaded (transferred) correctly, to generate a boot disk, the only file you need is the one named boot.img or bootnet.img (the latter for installs through a network). Transfer this file with ftp using BINary mode. After you get this file, which is pretty small (around 1.4 Mbytes), from DOS use the command: rawrite, which will ask you for the file name to write to the disk, prompt you to insert a disk and write the file you just downloaded to the disk generating an install disk. Of course, the rest of the distribution's files would be needed, so, download them all using BINary transfer as well, or if you use the bootnet.img image file, you may be able to install through a LAN if you are on one. —Felipe E. Barousse Boué, email@example.com
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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