Best of Technical Support
I have two CD-ROM drives, one recently installed. Before the installation of the second CD-ROM which is an HP 9200i CD_RW, everything mounted okay. Now, when I issue the mount command (mount /mnt/cdrom), I get the following:
CD-ROM I/O error: dev 0b:00,sector 64 isofs_read-super: bread failed,dev 0b:00 iso_blknum 16 block 32 mount: wrong fs type, bad option, bad superblock on /dev/cdrom or too many file systems
Both are SCSI drives. Please help if you can. —Tom Mcloughlin, email@example.com
There are two likely reasons for this problem. Either your “second” CD-ROM is seen as “first”, or the devices are configured to use the same SCSI ID, thus preventing any of them from functioning. Please check how SCSI identifiers have been assigned to the drivers and remember that the smaller ID is considered “first” drive (/dev/sr0) and the bigger ID is considered “second” (/dev/sr1). —Alessandro Rubini, firstname.lastname@example.org
/dev/cdrom is a symbolic link to a device like /dev/scd0 (the first SCSI CD-ROM). The second SCSI CD-ROM will be /dev/scd1. So, when wanting to mount the second CD-ROM, issue the command mount /dev/scd1 /mnt/cdrom, or create new links like /dev/cdrom0 to /dev/scd0 and /dev/cdrom1 to /dev/scd1. Don't forget to update the /etc/fstab, because mount /mnt/cdrom will read the fstab and mount the device allocated to this mounting point. —Paulo J V Wollny, email@example.com
I have the following operating systems installed on my PII Intel 440Bx system: NT4/Windows 98/Linux. While I can print absolutely fine from Windows 98 and NT4 on my HP 670C printer, I cannot do so from Linux. The error I get is “printer port is not recognised”. I have tried using the printtool to force the HP 670C on lp0, lp1 and lp2, respectively, but to no avail. What could be the problem? I have even tried changing the BIOS setting between ECP and EPP. —Sunil Dhaka, firstname.lastname@example.org
Are your printers parallel? If so, you might not have the parallel printer port driver configured correctly. Sometimes with Red Hat, the parallel port is not set up correctly after the installation. Add this line to the /etc/conf.modules file:
alias parport_lowlevel parport_pc
Reinitialize your machine, and your parallel port should now work fine. Configure everything with the printtool utility and send a test page to print. —Felipe E. Barousse, email@example.com
A local user I know, Scott Hettel, recently solved this problem on his own system. He found that Red Hat 6.1 does not support the IBM PC parallel printer port by default. The answer for this is on Red Hat's web site. See bug numbers 5698 and 5821 on their site for the resolution to this problem. You may also want to look at bug 8969, which discusses port compatibility. Please note that these issues affect only version 6.1 of Red Hat. —Chad Robinson, Chad.Robinson@brt.com
I'm trying to use mgetty with a serial port attached to a modem. The port is /dev/ttyS1. The line I put in /etc/inittab is:
S1:2345:respawn:/sbin/mgetty ttyS1Shortly after the system came up after reboot, I received this message continuously at about five-minute intervals:
INIT: Id "S1" respawning too fast: disabled for 5 minutes.Any ideas as to what I'm doing wrong? I'm running Red Hat 6.0. —Chris Yeats, CYeats@limbach.com
The message you get means that Linux starts the mgetty process and for some reason it dies, gets restarted and dies again. The most probable cause is that your modem cable does not have the correct pin wiring to work. Check www.linuxdoc.org/HOWTO/Text-Terminal-HOWTO-17.html#fast_respawn to find out a bit more about the problem. To override the cable problem (but losing modem control features), use the -r option for mgetty, which makes mgetty not monitor and detect the missing pin signals on your cable. I would still buy a good modem cable, though. —Felipe E. Barousse, firstname.lastname@example.org
Your mgetty ttyS1 command exits immediately and init disables its further invocation. You should first make the command work from the command line, where you can check what its error messages are and whether it works as expected. You should put the command in inittab only after your problems (misconfiguration, I suppose) are fixed. —Alessandro Rubini, email@example.com
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!
- Devuan Beta Release
- May 2016 Issue of Linux Journal
- EnterpriseDB's EDB Postgres Advanced Server and EDB Postgres Enterprise Manager
- The US Government and Open-Source Software
- The Humble Hacker?
- The Death of RoboVM
- BitTorrent Inc.'s Sync
- Open-Source Project Secretly Funded by CIA
- New Container Image Standard Promises More Portable Apps
- AdaCore's SPARK Pro
In modern computer systems, privacy and security are mandatory. However, connections from the outside over public networks automatically imply risks. One easily available solution to avoid eavesdroppers’ attempts is SSH. But, its wide adoption during the past 21 years has made it a target for attackers, so hardening your system properly is a must.
Additionally, in highly regulated markets, you must comply with specific operational requirements, proving that you conform to standards and even that you have included new mandatory authentication methods, such as two-factor authentication. In this ebook, I discuss SSH and how to configure and manage it to guarantee that your network is safe, your data is secure and that you comply with relevant regulations.Get the Guide