Bug#343674: arm/netwinder: nobootloader gives wrong kernel path
- To: Jurij Smakov <jurij@wooyd.org>
- Cc: 343674@bugs.debian.org, kmuto@debian.org
- Subject: Bug#343674: arm/netwinder: nobootloader gives wrong kernel path
- From: Martin Michlmayr <tbm@cyrius.com>
- Date: Wed, 1 Feb 2006 23:09:38 +0000
- Message-id: <[🔎] 20060201230938.GC29867@deprecation.cyrius.com>
- Reply-to: Martin Michlmayr <tbm@cyrius.com>, 343674@bugs.debian.org
- In-reply-to: <Pine.LNX.4.63.0601221838560.5173@bobcat>
- References: <20051218184736.GB16162@kitenet.net> <Pine.LNX.4.63.0512181122050.3833@bobcat> <20051218201308.GG16162@kitenet.net> <Pine.LNX.4.63.0512181336050.4514@bobcat> <20051218230254.GA1715@kitenet.net> <20051224160206.GB4737@deprecation.cyrius.com> <Pine.LNX.4.63.0512241730450.3523@bobcat> <20051230144335.GE25261@deprecation.cyrius.com> <20060107194208.GA3955@deprecation.cyrius.com> <Pine.LNX.4.63.0601221838560.5173@bobcat>
* Jurij Smakov <jurij@wooyd.org> [2006-01-22 18:40]:
> Sorry for the delay, I've had some hardware failures to deal with. Here's
> the output of ls -l /boot on a freshly-installed netwinder:
>
> lrwxr-xr-x 1 root root 24 2005-07-18 10:50 vmlinuz -> > vmlinuz-2.4.27-netwinder
Right, the symlink is there, so why shouldn't it work?
In fact I just made an installation myself and it works without any
problems.
--
Martin Michlmayr
http://www.cyrius.com/
Reply to: