Thanks for the advice. I administer, at least I try to, the boxes myself. I
use Linux it at home as a hobby and asking a question is sometimes quicker
for me than to search around for the answer.
Leland C. Scott
I can send them a note. I don't about it being "pithy" but the documentation
should be complete and correct at least.
Leland C. Scott
----- Original Message -----
From: "Rick Stevens" <ricks(a)nerd.com>
To: "KC8LDO" <kc8ldo(a)arrl.net>
Sent: Monday, November 02, 2009 2:34 PM
Subject: Re: "shutdown now" on F11 as root problems and app crashes in
> KC8LDO wrote:
>> I just checked the command line version, using "--help", as you
>> suggested, and the info is there, of course. I wasn't expecting that sort
>> of default behavior. Nothing in the man page that warns about it.
>> Somebody may want to consider adding that tid-bit to the man page. I
>> thought the man pages were the main source of info for various commands
>> etc., looks like it isn't. Guess I'll just have to be more careful.
>> Another day, learn something new.
> Yes, the man page should reflect the command better but the man pages
> are often maintained by someone other than the maintainer of the command
> itself. In this case it appears that they ARE done by the same folk
> (Canonical, Ltd.), so they should probably get a bug report. The man
> page does have a link:
> Report bugs at https://launchpad.net/products/upstart/+bugs
> If you have a chance, perhaps you should send them a pithy little note
> about it.
> - Rick Stevens, Systems Engineer ricks(a)nerd.com -
> - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 -
> - -
> - To err is human. To forgive, a large sum of money is needed. -
We are using Fedora Core 7 with 2.6.21 kernel and facing a issue in booting.
We have our PCI device on PCI slot and getting below message when system is
Uhhuh. NMI received for unknown reason a1 on CPU 0.
You have some hardware problem, likely on the PCI bus.
Dazed and confused, but trying to continue
what could be reason for above display ?
I did go back and read it, should have done that first. I did read that one
of the options the action taken is system dependent, the "-h" option. That
makes things more interesting.
I'm sitting here at work, eating lunch, reading the man page, again, for the
shutdown command using a remote VNC session to my F10 box at home. I don't
see anything that mentions any sort of default action if you fail to supply
one of the options to the shutdown command. All it says in general at the
end of the man page is :
"When invoked it generates a runlevel event, with an argument containing the
I'll have to look specifically at the one, man page, on the F11 box later
when I get home. Your comment suggests they are not the same.
One last comment. If I was not by the local attached console and saw what
happened, but was working remotely when I issued the "shutdown now" command,
having the system drop down to a CLI interface, single user mode, with the
root prompt showing isn't very comforting. Also my remote VNC session
terminated too. Not my idea of a way to lose control of the box and give
somebody else the chance to have some fun at the "free" root prompt either.
Lucky for me this box is on my home network where I'm the only one with
Leland C. Scott
I try to access the boot menu, where you can choose a kernel and,
whatever key I press, I can't stop the countdown and access the boot
I checked /boot/grub/grub.conf and I have hiddenmenu in it. But the
back-up, /boot/grub/grub.conf~ dates back to August and has hiddenmenu
in it too. Since I accessed the boot menu since August, I suppose this
is not the problem.
I have a 64 machine running XP with kvm/virt-manager. The startup and
running are fine, but shutdown or hibernate is so slow -- go have a
smoke, come back, still shutting down. I don't
smoke so it's even more annoying. Anyone have a hack for this?
I just had to replace my aging Epson C82, and bought an NX515. In
cups/gutenprint, the newest driver is for the NX400 series printers. It
works, at resolutions up to 720x720.
Whats chances we can get the newest gutenprint built for F10?
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
The NRA is offering FREE Associate memberships to anyone who wants them.
Alcohol, hashish, prussic acid, strychnine are weak dilutions. The surest
poison is time.
-- Emerson, "Society and Solitude"
it looks like F12 will need a 500M /boot partition. My current setup is
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 190M 32M 149M 18% /boot
58G 4.9G 53G 9% /
20G 9.4G 8.9G 52% /home
Or, in plain words, / and /home are LVM ext4 partitions, and /boot is a
separate 200M ext3 partition. Anyone could share some tips on what I will
need to do in order to make room for the 500M /boot partition? (as safe and
non-destructively as possible, of course). Since Fedora 10 I've been
installing instead of upgrading: I reformat everything except /home and
install from scratch (which has proven to be a nice approach, YMMV). I'd
like to stick to this approach, if possible.
I would think that I could remove current /boot, shrink / by 300M using LVM
and use the extra space to create a new /boot; is this the best way to go?
If so, has anyone done such a thing? Will it be doable from anaconda during
the F12 installation?
A jump from the less than 50M needed by F11 to 500M needed by F12 seems to
be excessive IMHO (it seems to be due changes on the installation
method). However, as long as there's an easy and painless way to make
room for the extra space needed, that's allright by me.
In trying to resolve a segfault appearing in libc-2.10.1.so with
mozilla Seamonkey, I discovered that there are really two different
versions of libc-2.10.1.so: The first one is in /lib and it is 1803428
byte, the second one is in /lib/i686/nosegneg and this one is 1816452
byte. Isn't it strange to have two files with the same name but different?
Craig White wrote:
> On Thu, 2009-10-29 at 17:08 -0400, Robert Moskowitz wrote:
>> Now I have to figure out how to deal with the small screen that the
>> Eee 701 has...
> check out what I do with my Acer Aspire One
> 1024x600 screen I run virtual at 1280x1024. It works really well.
Um I am now up to this step, but no xorg.conf file to modify.
I remember this was an issue with FC10 -- no xorg.conf and there was a
particular step you need to create one before you could modify it???