Increase grub timeout
Hi I'm reaching my one year anniversary using fedora, so I guess it's time to stop lurking and start writing, so here goes. Back in November I added my two cents to the bugzilla report titled "Increase grub timeout". Today I got a notification the it has been set as WontFix. The reason by Chris Lumen in his last paragraph states: I'm closing as WONTFIX only on that basis. Don't take it as an offence or that we'll never change this behavior. I'm just not willing to fix it until there's distribution buy-in. Thanks. OK, no offense taken, and, I understand that for marketing, saving a few seconds off of boot-up time is an immense selling point, especially when all the distros stand up next to one another and try to write their boot up times into the snow. Reading the forums and the mailing lists, I don't think I've come across one post that is positive for keeping the timeout at zero, yet, there is a wall to be hurdled called "distribution buy-in". After close to a year using fedora, I know that the first thing I have to do is change the timeout to a 3 and comment out hiddenmenu. But as a new user, it took a while for me to figure out what was going on. I feel for the new user who has a video card that is not immediately recognized and winds up with a black screen after the boot. I have had this happen to me personally doing an install, and, there have been some installs where hitting esc would not stop the boot. I've had to ssh into one machine to change the timeout, just so I could add "vesa" to the kernel line during boot. As someone who spends his time helping Linux users on forums, it would really help a lot to remove this obstacle. It doesn't make sense to lock a new user out of the grub screen. Thanks for Listening Tom Wroblewski GoinEasy9 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Increase grub timeout
There are many instances in the forums, where, adding a cheat code to the kernel line in grub will solve a problem, but, if one doesn't have access to grub at boot-up, the solution is made more difficult. Even the act of booting to init 3 to make a diagnosis by looking at the logs requires a rescue disk when there is no access to the grub screen. Installations aren't always seamless, a timeout of 1 to 3 seconds makes the recovery easier. -Original Message- From: Chris Jones To: Development discussions related to Fedora Sent: Sat, May 15, 2010 2:05 am Subject: Re: Increase grub timeout I was under the impression that a timeout is intentional/used only if another operating system is detected upon installation. ie. Windows. If no other operating system is detected, then there's no point having a timeout. -- Chris Jones Photographic Imaging Professional and Graphic Designer ABN: 98 317 740 240 Photo Resolutions - Photo Printing, Editing and Restorations Web: http://photoresolutions.freehostia.com Email: -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Increase grub timeout
That's not entirely true. I have read many posts where hitting escape had no effect on stopping boot. I, myself have one motherboard that functions (or doesn't function) in the same way. -Original Message- From: Genes MailLists To: Development discussions related to Fedora Sent: Sat, May 15, 2010 10:06 am Subject: Re: Increase grub timeout On 05/15/2010 09:48 AM, Felix Miata wrote: rior to first boot. I always change it to 12-15, depending on how many > stanzas are proposed. 3 seconds doesn't give me time to reach for the You dont really need to 'react' and make a decision other than to touch the kbd .. once you've touched the kbd .. you can take as long as you want choosing the grub entry/editing etc ... -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [HEADS-UP] systemd is now the default init system in rawhide
Add init=/sbin/upstart to the end of the kernel line and it will boot up using upstart. Last lines in my boot read failing to load default.service and then failing to start default.service. -Original Message- From: darrell pfeifer To: Development discussions related to Fedora Sent: Wed, Jul 28, 2010 5:59 pm Subject: Re: [HEADS-UP] systemd is now the default init system in rawhide I installed the latest systemd and added the appropriate symbolic link to graphical startup. My system hangs when almost complete at the plymouth throbber. In text mode it gets to the end of starting services and hangs. gdm never starts. In /var/log/messages, these seem to be the suspicious lines Jul 28 14:21:26 darrell init[1]: Job dev-mapper-vg_darrell\x1dlv_root.device/start timed out. Jul 28 14:21:26 darrell kernel: init[1]: Job dev-mapper-vg_darrell\x1dlv_root.device/start timed out. Jul 28 14:21:35 darrell init[1]: Job dev-disk-by\x1duuid-f060d5d3\x1ddef6\x1d4247\x1d9162\x1da810e55ca01c.device/s tart timed out. Jul 28 14:21:35 darrell kernel: init[1]: Job dev-disk-by\x1duuid-f060d5d3\x1ddef6\x1d4247\x1d9162\x1da810e55ca01c. device/start timed out. df shows the volume as /dev/mapper/vg_darrell-lv_root Any suggestions? darrell -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: [HEADS-UP] systemd is now the default init system in rawhide
I found a fix on bugzilla: rpm -e --nodeps systemd-units yum install systemd-units Which created the symlinks and default.service which seemed to be missing, and allowed the boot to finish, but I may have been to quick to use it. One CPU core is at maximum and Chrome won't open, so I'm temporarily back to upstart till I get time to look at it further. https://bugzilla.redhat.com/show_bug.cgi?id=618315 -Original Message- From: darrell pfeifer To: Development discussions related to Fedora Sent: Wed, Jul 28, 2010 6:46 pm Subject: Re: [HEADS-UP] systemd is now the default init system in rawhide On Wed, Jul 28, 2010 at 19:33, wrote: Add init=/sbin/upstart to the end of the kernel line and it will boot up using upstart. Last lines in my boot read failing to load default.service and then failing to start default.service. Check one of the recent previous messages. ln -sf /lib/systemd/system/graphical.target /etc/systemd/system/default.target Will solve that problem and get you a bit further along the way. darrell -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
