12-22-2008
Unfortunately the DOS and BART utilities won't help me as I need to run within a Linux OS in order to run the software I am looking to run. As of right now I have Fedora 9 booting from a USB key, in text only mode, with my software installed. My main problem is that the OS is not sending the text output to the serial port.
After looking at some documentation online it seemed that editing grub.conf was going to be my answer but this isn't the case in Fedora 9 apparently. All of the RHEL 4 and RHEL 5 systems I have used utilize this file, however Fedora 9 apparently doesn't. I then went to inittab where I was able to change the default run level to 3. This unfortunately only applies to the video output.
I now need to know what is the best way under Fedora 9 to redirect all screen output to the serial port. Some things I have read are indicating that I would have to use a kernel command which basically means recompiling. If this is the case I suppose I am okay with it but it will be my first time recompiling a kernel.
Thanks for the help so far!
10 More Discussions You Might Find Interesting
1. BSD
Hi to all,
Iam using FreeBSD 5.4. I want to write a kernel file with an option "CD9660_ROOT" in it. When i start to compile this kernel, it gives a message "unknown option CD9660_ROOT". Could anyone hellp with this as soon as possible.
Bye,
tadakamalla (3 Replies)
Discussion started by: tadakamalla
3 Replies
2. Linux
Hello Everybody
I am planning to install Fedora core 8 on an extra PC I have; what I wanna do is to boot from a USB stick then install Fedora from an ISO image I already have via FTP. Could any one tell me how to create bootable USB Stick for Fedora as I already found how to install from FTP... (0 Replies)
Discussion started by: ahmed_nasr2001
0 Replies
3. HP-UX
I am trying to copy a HP-UX disk. Both the OS and H/W are quite old
HP-UX hpeval3 B.09.10 A 9000/382 080009789a46
I have a 1.5Gb disk and a new 2Gb disk. I have been using the following method to create the copy, which must be a bootable disk.
#mediainit /dev/rdsk/cEd1s0
(2Gb disk) cEd0s0... (9 Replies)
Discussion started by: malcqv
9 Replies
4. Linux
Hi all,
thanks for so many helps in many problems!
Can anyone guide, how to create a bootable cd/dvd from downloaded iso images of CentOS 5? I have collected all the iso in a dvd but it is not booting the system. Any response will be appreciable... (2 Replies)
Discussion started by: naw_deepak
2 Replies
5. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
6. Red Hat
Hi I have ISO file of RHEL6.
I want to install it on my WIndows 7 machine with dual boot. But my CD/DVD drive is not working.
Please tell me how do you I make it USB bootable from my own Windows machine so that I can install it happily through flash drive. (3 Replies)
Discussion started by: nixhead
3 Replies
7. Ubuntu
I'd like to make bootable USB flash with 12.04 desktop on it with some additional packages and customizations, such as added language.
What I tried so far - I went through pendrivelinux.com ISO to USB program and have working bootable USB with 12.04 desktop on it. The problem is all my changes... (8 Replies)
Discussion started by: migurus
8 Replies
8. SuSE
Hi All,
I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server
I have already downloaded relevant OS (Trail Version) packages @
1) SLES-11-SP4-DVD-i586-GM-DVD1
2) SLES-11-SP4-DVD-i586-GM-DVD2
when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies
9. BSD
I would probably set all my rubber points here to get some real help for creating a boot device on a usb-stick. There is no CD-drive on this machine, thats why I need to use a usb-stick. And scrumming in a CD-drive to fuddle around in the fstab or something like that is out of reach.
My wisdom so... (9 Replies)
Discussion started by: 1in10
9 Replies
10. UNIX for Beginners Questions & Answers
I have a .dmg file which was created from a disk consisting of two partitions. When I mount the dmg both partitions pop up, so I know the imaging worked properly. One partition is HFS+ and the other is FAT32.
So far, I've been unable to find a way to restore the dmg to a flash drive where both... (17 Replies)
Discussion started by: paulcristo
17 Replies
HALD(8) System Manager's Manual HALD(8)
NAME
hald - HAL daemon
SYNOPSIS
hald [options]
DESCRIPTION
hald is a daemon that maintains a database of the devices connected to the system system in real-time. The daemon connects to the D-Bus
system message bus to provide an API that applications can use to discover, monitor and invoke operations on devices. For more information
about both the big picture and specific API details, refer to the HAL spec which can be found in /usr/share/doc/hal-doc/spec/hal-spec.html
depending on the distribution.
OPTIONS
The following options are supported:
--daemon=yes|no
Specify whether to run in the foreground or the background.
--verbose=yes|no
Enable verbose debug output.
--use-syslog
Enable logging of debug output to the syslog instead of stderr. Use this option only together with --verbose.
--help Print out usage.
--version
Print the version of the daemon and exit.
BUGS AND DEBUGGING
Please send bug reports to either the distribution or the HAL mailing list, see http://lists.freedesktop.org/mailman/listinfo/hal on how to
subscribe.
First, to obtain useful debug traces you will need to have debuginfo packages installed. On a Fedora system this is in the hal-debuginfo
package and can be installed via the yum update program.
Second, shut down the existing hald daemon instance; on a Fedora system this is achieved by
/etc/init.d/haldaemon stop
After having shut down the daemon, you might want to run
pkill hald
to ensure that all the helper processe of hald are killed too. To start the HAL daemon, use
/usr/sbin/hald --daemon=no --verbose=yes
If the daemon crashes, you can start it under a debugger via
gdb /usr/sbin/hald
and then typing
run --daemon=no --verbose=yes
at the (gdb) prompt. To capture a back trace, use the bt command and attach this to the bug report.
Please also attach the output of lshal(1) in the bug report if possible (it's not possible if the hald daemon crashed). If the nature of
the bug has to do with hotplugging, attach two outputs of lshal(1) - one before the device hotplug event and one after.
SEE ALSO
udev(7), dbus-daemon(1), lshal(1), hal-set-property(1), hal-get-property(1), hal-find-by-property(1), hal-find-by-capability(1), hal-is-
caller-locked-out(1)
AUTHOR
Written by David Zeuthen <david@fubar.dk> with a lot of help from many others.
HALD(8)