Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Author Message
CaesarTjalboOffline
Post subject: kernel-remover oddity  PostPosted: 17.07.2012, 23:08



Joined: 2010-09-13
Posts: 95
Location: Enschede
Status: Offline
It's a pretty irrelevant observation but technically speaking it's still a bug: the kernel-remover script does weird things when it can't find a /boot directory.

Afaik it lists the contents of the current directory as options to delete, correct behavior would be to exit with an error message.

Feel free to ignore it though.
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: kernel-remover oddity  PostPosted: 18.07.2012, 01:02



Joined: 2010-08-25
Posts: 766

Status: Offline
What do you understand under "can't find a /boot/ directory"?

- there being no /boot/ directory under / (e.g. some partial chroot environment)
- it being not allowed to be read by root, but physically present
- implications from read-only root configurations
- a separate /boot/ partition which is just not mounted at the moment (so an empty, but present /boot/)
- some netboot or external boot (kvm with kernel/ initrd supplied via cli arguments) environment (please specify)
- something totally different

Knowing the exact error condition would help a lot for fixing it (and to confirm if it really got fixed).
 
 View user's profile Send private message  
Reply with quote Back to top
CaesarTjalboOffline
Post subject: Re: RE: kernel-remover oddity  PostPosted: 18.07.2012, 08:34



Joined: 2010-09-13
Posts: 95
Location: Enschede
Status: Offline
      slh wrote:
- there being no /boot/ directory under /
Separate boot partition mounted under otherwise empty (root)/boot/ directory. I was struggling to solve a grub issue and had the /boot/ directory removed and forgot to put it back.

System boots and works normally. Running kernel-remover gives reported strange behavior.

Reproduction: on normal running system, rename existing /boot/ directory to something else, run kernel-remover (-F text), note the entries. Change working directory, repeat. (*)

I know it's a silly situation which shouldn't occur on any normal system but perhaps you can imagine my surprise when I stared at the options presented by kernel-remover.

(*) edit: don't forget to name it back.
 
 View user's profile Send private message  
Reply with quote Back to top
slhOffline
Post subject: RE: Re: RE: kernel-remover oddity  PostPosted: 19.07.2012, 00:19



Joined: 2010-08-25
Posts: 766

Status: Offline
Thanks, we will look at this problem soon (it's not fixed in 3.1.7 yet).
 
 View user's profile Send private message  
Reply with quote Back to top
Display posts from previous:     
Jump to:  
All times are GMT - 12 Hours
Post new topic   Reply to topic
View previous topic Printable version Log in to check your private messages View next topic
Powered by Zafenio