| Author |
Message |
|
|
Post subject:
Posted: Jul 25, 2007 - 08:19 PM
|
|
Joined: Jan 10, 2007
Posts: 765
Status: Offline
|
|
not really, because my question still remains. If modifying that files wouldn't be safe, modifying after kernel install is as unsafe.
So slhs and kelmos postings imply that you better should remove the menu.lst modification after kernel install part from smxi, if i understood them right. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Jul 25, 2007 - 08:48 PM
|
|
Joined: Nov 28, 2006
Posts: 4303
Status: Offline
|
|
smxi does not modify menu.lst after kernel install, that's the slh kernel installer that does that. It may run update-grub I think, but that's just to add the kernels to make sure it's updated.
Adding the new kernel on new kernel install is of course required and not an option, but tweaking grub further for optional stuff is not required and could and probably would cause annoying issues, none of which I'm interested in, especially because what the original poster was trying to achieve was being able to go to the kitchen to get a cup of coffee to avoid spending the roughly 30 seconds a shutdown takes and then typing in 3. Since that is getting into the fairly absurd in terms of time and tweaks, we'll leave this one alone until such a time comes that a real reason, something better than going to get a cup of coffee while machine reboots, comes up to even think of this question further.
Basically what you have at times is people who misunderstand the concept of useability, at least as far as I can see. If someone's life is so hectic that 30 seconds is going to really make a difference... well... I don't know, that gets kind of silly if you ask me.
<hint: if you need to get a cup of coffee during kernel install, try this: when the question comes up if you want to reboot now, don't answer it. Go to the kitchen, make your coffee, then come back, hit y, then type 3 on reboot, and you're good to go.> |
_________________ sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Jul 25, 2007 - 09:00 PM
|
|

Joined: Dec 02, 2006
Posts: 303
Location: Gold Coast, Queensland, Australia
Status: Offline
|
|
Re: h2's suggestion.
A few push-ups, a cold beer, or even a quickie work quite well, too. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Jul 25, 2007 - 09:29 PM
|
|

Joined: Dec 08, 2006
Posts: 242
Location: Deptford, NJ
Status: Offline
|
|
|
paleoflatus wrote:
Re: h2's suggestion.
A few push-ups, a cold beer, or even a quickie work quite well, too.
HAHAHAHA
Well Wife according to the SMXI script I get a cold beer and a quickie.
Guess I'll have to update the system a couple times each day
Thanks
RR |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Jul 26, 2007 - 12:19 AM
|
|
Joined: Dec 19, 2006
Posts: 1030
Status: Offline
|
|
|
BlueShadow wrote:
not really, because my question still remains. If modifying that files wouldn't be safe, modifying after kernel install is as unsafe.
So slhs and kelmos postings imply that you better should remove the menu.lst modification after kernel install part from smxi, if i understood them right.
No. My comment was towards your suggestion that h2 should do *anything* to menu.lst, you misunderstand.
The debian tools can modify grub's menu.lst as they see fit, because that code has been proven to work for many years. |
|
|
| |
|
|
|
 |
|
|
Post subject:
Posted: Jul 26, 2007 - 08:41 AM
|
|
Joined: Jan 10, 2007
Posts: 765
Status: Offline
|
|
| allright, now it's clear for me |
|
|
| |
|
|
|
 |
|
|
|