[pkg-fso-maint] [Debian] Finally, linux-2.6-openmoko into the pkg-fso repository
luca at pca.it
Mon Oct 20 14:08:36 UTC 2008
Please don't top post: http://en.wikipedia.org/wiki/Top_posting
Then, thank you for your test and feeback. As a general node, you can
report any bug in the Debian packages directly to the Debian BTS, as
explained at .
On Mon, 20 Oct 2008 12:01:47 +0200, Michele Renda wrote:
> Michele Renda wrote:
>> Here are the results:
>> dpkg: error processing
>> error creating symbolic link `./boot/uImage.bin': Operation not permitted
This is quite strange, for the possible causes read below.
> Ps. If it can help, I think the solution is to modify:
> ...creating symbolic link `./boot/uImage.bin'
> ...creating symbolic link `/boot/uImage.bin' (absolute ref)
IIRC dpkg works on the / folder, which means that there's no difference
between the two references above. And in that case the error would be
root at gismo:~# ln -s /root/.bashrc ./boot/test.link
ln: creating symbolic link `./boot/test.link': No such file or directory
root at gismo:~#
FYI, the link was automatically created by dh_link from the debhelper
package : it takes care of everything and it's written for Debian
following the Debian policy, thus it'd be strange that no one has
I'm quite sure that the problem is with the filesystem used for the
/boot partition. Since I performed my test with ext2 only, I completely
forgot that the /boot partition can be a vfta, too. Indeed, with vfat I
get the same error:
root at ranma:~# ln -s /root/.bashrc /boot/test.link
ln: creating symbolic link `/boot/test.link': Operation not permitted
root at ranma:~#
I'll fix it with the next kernel image, which will be milestone3.
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 314 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20081020/57f9892f/attachment.pgp
More information about the pkg-fso-maint