Best of Technical Support
I have two hard drives on my system. One is dedicated to Linux, the other is for Windows 98 (second edition). I can't boot to Win98 when both drives are up. They're set up fine (one master, one slave, BIOS finds them, etc.). I can boot Linux with both drives connected. If I disconnect the Linux drive, I can run Win98 fine. LILO seems to know that it has a DOS drive and a Linux drive. If I say “dos” at the boot prompt, LILO doesn't complain—things just hang. I've even tried booting with a Win98 boot floppy; the system reads from the floppy for a while and then just hangs—no message, no nothing. One drive is a WD, the other is IBM. Please help! —Mitch, firstname.lastname@example.org
I am assuming that the master disk has Linux on it, therefore you can boot fine with both disks active. It seems there is just a misconfiguration of your lilo.conf file. You have to tell LILO where (which physical disk and which partition) DOS/Windows is located. Check on the specified devices in /etc/lilo.conf. Look in the section where you have your “dos” label for /dev/hdaX and /dev/hdbY (X and Y being partition numbers) and hda, hdb representing your physical disks. You may need to find which disk holds what. Two lines like:
may be what is needed for you to be able to boot DOS (and Linux) with both disks on. Don't forget to write that LILO info to the boot sector with /sbin/lilo -v after you have made changes in /etc/lilo.conf. —Felipe E. Barousse Boué, email@example.com
You don't say whether Windows is on the slave or the master. By default, Windows won't boot from a secondary drive. However, you can try booting from the second drive by putting the following in lilo.conf to boot DOS/Windows (it swaps the drive letters):
other = /dev/hdb1 label = dosb loader = /boot/any_d.b
—Marc Merlin, firstname.lastname@example.org
I am running a console on an HpUX box. This application is run from an xterm on my Linux box. The HpUX box has no X libs and does not accept my function keys. Does anyone know how to make my function keys work while telneted into this HP system? —David, email@example.com
Since you state that the HpUX has no X libs, and it looks to me that you are just using a terminal emulation window (xterm) in your Linux box, you should be able to define which code to generate whenever you press a function key so it gets sent to the HpUx box through your xterm. You can use the xmodmap command to define such sequences on your Linux box. Put those sequences in the .xmodmaprc file of your login account or in Xmodmap's general configuration file. Try also keying ESC-1 for F1, ESC-2 for F2, etc., to test whether your application is getting Fkey sequences. Lastly, terminal emulation affects the way Fkeys work. You should have the terminal emulation correctly set up, with the termcap definitions in both the HpUX side and the Linux xterm session. --Felipe E. Barousse Bouéfbarousse@piensa.com I don't have experience with this specific case, but the normal way to get your function keys (and other nonstandard keys) recognized is to modify your TERM setting after logging in on the remote machine. You do this with something like export TERM=termtype (for bash or ksh) or setenv TERM termtype (for csh or tcsh). You may need to experiment with values for “termtype”--I would try values like “xterm”, “vt100”, “vt220”, “hpterm” and “linux” (in increasing order of desperation). If none of those works, look through /etc/termcap on the remote machine for other possible values of TERM. When you find a value that works, simply copy the TERM assignment into your shell startup file (.bash_profile, .cshrc, or whatever) on the remote system, and you'll never have to worry about it again. —Scott Maxwell, maxwell@ScottMaxwell.org
I lost the link to my C: drive (Windows). In the process of trying to connect my scanner, I changed sda1 to hda1 and now I can't gain access to my C: drive from Linux or from LILO. When it gets to the LILO prompt and I select Windows, it just locks up. How do I get the link back? —Faron Ducharme, firstname.lastname@example.org
You don't mention how you “changed sda1 to hda1”. However, LILO's configuration information is stored in /etc/lilo.conf. After editing this file, you will need to run LILO from a command prompt to tell it to reread its settings. —Chad Robinson, email@example.com Does Linux boot fine? Seems you are using SCSI disks, so if you renamed sda1 to hda1 in the /dev directory, changing it back should solve the problem, providing you haven't changed LILO's configuration at /etc/lilo.conf. Logged in as root, use mv /dev/hda1 /dev/sda1. If you cannot boot Linux, then you would have to use the emergency boot disk (you have one, don't you?) you made at installation time to be able to boot the machine and then change the device names back to normal as indicated above. —Felipe E. Barousse Boué firstname.lastname@example.org
Fast/Flexible Linux OS Recovery
On Demand Now
In this live one-hour webinar, learn how to enhance your existing backup strategies for complete disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible full-system recovery solution for UNIX and Linux systems.
Join Linux Journal's Shawn Powers and David Huffman, President/CEO, Storix, Inc.
Free to Linux Journal readers.Register Now!
|Working with Command Arguments||May 28, 2016|
|Secure Desktops with Qubes: Installation||May 28, 2016|
|CentOS 6.8 Released||May 27, 2016|
|Secure Desktops with Qubes: Introduction||May 27, 2016|
|Chris Birchall's Re-Engineering Legacy Software (Manning Publications)||May 26, 2016|
|ServersCheck's Thermal Imaging Camera Sensor||May 25, 2016|
- Secure Desktops with Qubes: Introduction
- Secure Desktops with Qubes: Installation
- Download "Linux Management with Red Hat Satellite: Measuring Business Impact and ROI"
- Working with Command Arguments
- CentOS 6.8 Released
- The Italian Army Switches to LibreOffice
- Linux Mint 18
- ServersCheck's Thermal Imaging Camera Sensor
- Chris Birchall's Re-Engineering Legacy Software (Manning Publications)
- Petros Koutoupis' RapidDisk
Until recently, IBM’s Power Platform was looked upon as being the system that hosted IBM’s flavor of UNIX and proprietary operating system called IBM i. These servers often are found in medium-size businesses running ERP, CRM and financials for on-premise customers. By enabling the Power platform to run the Linux OS, IBM now has positioned Power to be the platform of choice for those already running Linux that are facing scalability issues, especially customers looking at analytics, big data or cloud computing.
￼Running Linux on IBM’s Power hardware offers some obvious benefits, including improved processing speed and memory bandwidth, inherent security, and simpler deployment and management. But if you look beyond the impressive architecture, you’ll also find an open ecosystem that has given rise to a strong, innovative community, as well as an inventory of system and network management applications that really help leverage the benefits offered by running Linux on Power.Get the Guide