FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 11-17-2009, 09:10 AM
maximilian attems
 
Default linux-2.6 piuparts error

0m54.3s ERROR: FAIL: Package purging left files on system:
/etc/kernel-img.conf not owned


so either it is a failure to generate such a file in postinst (as we
shouldn't really need it!?), or one would want to remove it on purge,
which opens another can of worms as this file is unowned in real boxes
and usualy created by d-i.

the best argument is that due to the convulated questions postinst
wanted to ask you in the past we had never reached that point of
generating this conffile in postinst.


diff --git a/linux-2.6/debian/templates/temp.image.plain/postinst b/linux-2.6/debian/templates/temp.image.plain/postinst
index ae8c797..43dba4d 100755
--- a/linux-2.6/debian/templates/temp.image.plain/postinst
+++ b/linux-2.6/debian/templates/temp.image.plain/postinst
@@ -478,24 +478,10 @@ sub handle_missing_link {
die("Failed to copy " . $realimageloc . "$image_name to "
. $image_dest . "$kimage .
");
}
- }
- else {
+ } else {
if (! $have_conffile) {
# current default
$do_symlink = "Yes";
-
- if (open(CONF, ">$CONF_LOC")) {
- print CONF "# Kernel Image management overrides
";
- print CONF "# See kernel-img.conf(5) for details
";
- if ($loader =~ /palo/i) {
- print CONF "link_in_boot = Yes
";
- print CONF "do_symlinks = Yes
";
- print CONF "relative_links = Yes
";
- print CONF "do_bootloader = No
";
- }
- close CONF;
- }
- $have_conffile = "Yes";
}
}



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-18-2009, 09:27 AM
Sebastian Andrzej Siewior
 
Default linux-2.6 piuparts error

* maximilian attems | 2009-11-17 11:10:46 [+0100]:

>0m54.3s ERROR: FAIL: Package purging left files on system:
> /etc/kernel-img.conf not owned

oh

>so either it is a failure to generate such a file in postinst (as we
>shouldn't really need it!?), or one would want to remove it on purge,
>which opens another can of worms as this file is unowned in real boxes
>and usualy created by d-i.
>
>the best argument is that due to the convulated questions postinst
>wanted to ask you in the past we had never reached that point of
>generating this conffile in postinst.

What is the long term goal? Do you plan do to get rid of kernel-img.conf
and let the individual boot loader handle this kind of things?
You are changing the default behavior of palo here. However the values
are written very late. link_in_boot for instance is only evalueted at
the begin of the script. So it should not really matter for postinst at
least.
The do_symlink thing is only required by people that don't have their
setup right, isn't it? So grub refers to /vmlinuz but kernel itself is
not in / but in /boot. So if those people would fix their boxes we could
get rid of do_symlink for instance right?

>
>diff --git a/linux-2.6/debian/templates/temp.image.plain/postinst b/linux-2.6/debian/templates/temp.image.plain/postinst
>index ae8c797..43dba4d 100755
>--- a/linux-2.6/debian/templates/temp.image.plain/postinst
>+++ b/linux-2.6/debian/templates/temp.image.plain/postinst
>@@ -478,24 +478,10 @@ sub handle_missing_link {
> die("Failed to copy " . $realimageloc . "$image_name to "
> . $image_dest . "$kimage .
");
> }
>- }
>- else {
>+ } else {
> if (! $have_conffile) {
> # current default
> $do_symlink = "Yes";
>-
>- if (open(CONF, ">$CONF_LOC")) {
>- print CONF "# Kernel Image management overrides
";
>- print CONF "# See kernel-img.conf(5) for details
";
>- if ($loader =~ /palo/i) {
>- print CONF "link_in_boot = Yes
";
>- print CONF "do_symlinks = Yes
";
>- print CONF "relative_links = Yes
";
>- print CONF "do_bootloader = No
";
>- }
>- close CONF;
>- }
>- $have_conffile = "Yes";
> }
> }
>

Sebastian


--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 
Old 11-18-2009, 12:05 PM
maximilian attems
 
Default linux-2.6 piuparts error

On Wed, Nov 18, 2009 at 11:27:04AM +0100, Sebastian Andrzej Siewior wrote:
> * maximilian attems | 2009-11-17 11:10:46 [+0100]:
>
> >0m54.3s ERROR: FAIL: Package purging left files on system:
> > /etc/kernel-img.conf not owned
>
> oh
>
> >so either it is a failure to generate such a file in postinst (as we
> >shouldn't really need it!?), or one would want to remove it on purge,
> >which opens another can of worms as this file is unowned in real boxes
> >and usualy created by d-i.
> >
> >the best argument is that due to the convulated questions postinst
> >wanted to ask you in the past we had never reached that point of
> >generating this conffile in postinst.
>
> What is the long term goal? Do you plan do to get rid of kernel-img.conf
> and let the individual boot loader handle this kind of things?

yes indeed the long term plan is to get rid of kernel-img.conf
any eventual hooks there should be gone with lenny+1

what they should do is leave hooks in /etc/kernel dirs,
grub has such a whishlist open, hope it gots resolved soon.


> You are changing the default behavior of palo here.
Only in the case that no /etc/kernel-img.conf existed yet.
haven't checked what the consequences of that particular change in the
other maintainer scripts.

> However the values
> are written very late. link_in_boot for instance is only evalueted at
> the begin of the script. So it should not really matter for postinst at
> least.

right

> The do_symlink thing is only required by people that don't have their
> setup right, isn't it? So grub refers to /vmlinuz but kernel itself is
> not in / but in /boot. So if those people would fix their boxes we could
> get rid of do_symlink for instance right?

any sane bootloader shouldn't need that symlink mess indeed.
afaik grub refers to the kernel directly in /boot,
but it is lilo and many other bootloaders that prefers to have that symlinking.

so it might indeed be worth also to have d-i updated on their generated
kernel-img.conf


thanks for your review!



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
 

Thread Tools




All times are GMT. The time now is 03:43 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org