You are not logged in.
Pages: 1
I have an idea which can help out the lilo users out there. Like when arch installs(upgrades) a new kernel using pacman -Syu or pacman -S kernel[26/24], and if he is using lilo cant pacman automatically run /sbin/lilo anyway syu will be executed as root. So permissions are there.
This is just an idea that passed my mind after I read another article about a newbie ruining his system without running /sbin/lilo (Of Course this can be rectified but save us of the trouble.
Another reasonI would want this is my upgrade time. i upgrade when i sleep.
So when i waske up sleepy, i may forget /sbin/lilo
I would have put this in had I the wit or worth. I have none of these. I am just on the learning curve nad i am yet to start C pacman was written in!
P.S. Can I run this as a weekly cron job instead
add upgrade as the name an include
pacman -Syu --noconfirm --noprogressbar
/sbin/lilo
[/code]
Be yourself, because you are all that you can be
Offline
The only problem is - how can you tell that you're using lilo? Just because you have lilo installed on your system doesn't mean that's the bootloader you're using (I had lilo for ages because it was in the base packages, but I'm a grub user) so you can't just check [ -x /sbin/lilo ].
Offline
The only problem is - how can you tell that you're using lilo? Just because you have lilo installed on your system doesn't mean that's the bootloader you're using (I had lilo for ages because it was in the base packages, but I'm a grub user) so you can't just check [ -x /sbin/lilo ].
is this of use cerebral??
http://www.webhostingtalk.com/archive/t … 647-1.html
Be yourself, because you are all that you can be
Offline
if it directly doesnt work try the /sbin/grubby
If the script is no found or if reply is grub, it is grub not lilo.
Else it is lilo
Be yourself, because you are all that you can be
Offline
Must everything be a poll?
[ ] Yes
[ ] No
[ ] Tacos
I am a gated community.
Offline
this must because if it is yes, then this must be implemented democratically
Be yourself, because you are all that you can be
Offline
I think it is better to make a script in /etc/rc.d/ . It could for an example be named lilo and be executed when the system is shutdown. To make it even better it could check where the kernels are placed (from /etc/lilo.conf) and check when they last were changed and compair it to a stored time. This time is supposed to be when the script last uppdated lilo. This means that the script will only update lilo if at least one kernel is uppdated.
Offline
I don't care, as I compile kernels myself.
And pacman issues a reminder when installing a kernel, saying " don't forget to run lilo if you use it ".
Excessive showering, grooming, and toothbrushing is not only vain, it wastes valuable coding time.
Offline
this has been brought up before. I think I suggested a more generic "hooks" option, but its really not that necessary. Fact is you could write a script that greps pacman output for 'kernel26' and runs lilo if it is found.
Dusty
Offline
this must because if it is yes, then this must be implemented democratically
Says who?
Offline
you could always just write a script yourself that does this using yes | pacman -Syu; /bin/lilo. I mean... It's really not worth lines of code in my opinion.
Offline
Must everything be a poll?
[ ] Yes
[ ] No
[ X ] Tacos
Offline
tacos!
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
I've deleted the poll, but further discussion should go on topic. Those who insist on discussing tacos are directed to one of the following:
http://bbs.archlinux.org/viewtopic.php?t=21548
http://www.tacotown.org/
Dusty
Offline
Really, I thought polls were cool(I dont want people posting answers for the above line)
Still, i dont mind the poll being taken out.
In reply to raskolnikov
pacman does issue messages-> right.
But the messages get scrolled up the screen. Not many care to do a shift + PageUP.!
In reply to Dusty PJ, and especially codemac.
We can do everything by ourselves if we wanted to. Fine Arch maybe for advanced users, but isnt it a better option to include it in pacman, pacman will hardly be 1kb bigger( so it may be worth the lines of code). Startup scripts need not start network, we can do it ourselves. Even fsck(which happens one in abt 30 mounts unless u override it). Imagine the growth of pacman from about 1mb to about 2.9 mb now
Also it will be of better use to people who have come new to arch and who put their first pacman -Syu when they were sleep, woke up at 4am and in the dazed state put off their pc.
Never mind if this is going in the useless track. I thought myself that the idea maynot be welcome in the begining. thats why i put up such a title and a poll too!
I already have the rc.d script but it does the /sbin/lilo everyday. Its not going to hurt even if kernel wasnt updated!
Be yourself, because you are all that you can be
Offline
I think the need to re-run lilo after a kernel update is one of the things keeping people from using LiLo. (that and the syntax are my main reasons for NOT using LiLo).
How about we create a daemon for LiLo ?
It would work something like this :
We introduce a permanent flag , LiLo_kernel_version
Initial state : 0
Every time LiLo is run, it stores the current kernel version in this flag.
The daemon
On startup it should do nothing
On shutdown :
IF LiLo_kernel_version = 0
THEN
return # LiLo isn't used, nothing to do
ELSE
IF LiLo_Kernel_version = current_kernel_version
THEN
return # kernel hasn't changed, nothing to do
ELSE
# kernel HAS changed
run LiLo
return
--------------------
This daemon should be added to the ARCH LiLo package.
I am aware this is not a real daemon, but neither is the one ALSA uses.
For grub users this would add a small delay on startup/shutdown, for LiLo users this could be a lifesaver.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
I think the need to re-run lilo after a kernel update is one of the things keeping people from using LiLo. (that and the syntax are my main reasons for NOT using LiLo).
Funny enough, that's the syntax of Grub that keep me from using it.
Your "daemon" script is not a bad idea, though
@ScriptDevil : right, but you can use the tee(1) command to duplicate the output of pacman to a file, and read it after upgrades. Of course it would be better if pacman do this itself in a logfile (say /var/log/updates.log)...
Excessive showering, grooming, and toothbrushing is not only vain, it wastes valuable coding time.
Offline
I do not know about everyone else by I check what it's going to be upgraded before I press yes.
Having said that a simple solution for those using lilo is to concatenate commands. I mean, if you see that you have a kernel upgrade then use the command : pacman -Syu && lilo so when pacman exits the lilo command will be executed.
Hope this helps.
Offline
well, i repeat the same thing. It is like this, add it in pacman or keep telling lilo users to run lilo at the end of messages
Like why cant all error and warning messages be published at the ende than at the middle
Be yourself, because you are all that you can be
Offline
ScriptDevil, I can appreciate the 'value' of an automated process (grub like) but I see no harm in concatenating commands as a simple and fast solution.
The error message process needs no change (when you use concatenated commands) and yet you have a 'safe' way to upgrade kernel.
Offline
I've deleted the poll, but further discussion should go on topic. Those who insist on discussing tacos are directed to one of the following:
http://bbs.archlinux.org/viewtopic.php?t=21548
http://www.tacotown.org/Dusty
HA! Funniest thing I've read all day!
In this land of the pain the sane lose not knowing they were part of the game.
~LP
Offline
Pages: 1