[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#795231: marked as done (fails on cubietruck with FAT /boot)

Your message dated Thu, 20 Aug 2015 10:58:34 +0100
with message-id <1440064714.3480.96.camel@debian.org>
and subject line Re: Bug#795231: fails on cubietruck with FAT /boot
has caused the Debian Bug report #795231,
regarding fails on cubietruck with FAT /boot
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
795231: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795231
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: flash-kernel
Version: 3.36
Severity: normal

A few places in flash-kernel try to ln -s, and this fails if /boot is 
a FAT filesystem. It should be possible to fall back to cp in this case.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
On Wed, 2015-08-12 at 16:34 -0400, Joey Hess wrote:
> Ian Campbell wrote:
> > The cubietruck u-boot is more than capable of booting from an ext
> > filesystem, so you should just do that, in fact everything should work
> > in this mode out of the box, how did you end up with a FAT /boot?
> 
> Haven't upgraded from default uboot yet, which does't even support
> ext2..

I wasn't aware that the CT came with a default u-boot, let alone such a
limited one. IIRC my one shipped with some Android/fastboot thing in
the nand flash and no SD card so I had to gather my own u-boot anyway.
Anyway, that's by the by I suppose.

> > On platforms where u-boot is only capable of reading FAT the
> > recommended approach is to use a dedicated FAT partition which is not
> > normally mounted and use flash-kernel's Boot-Device option to cause the
> > boot images to be copied to it.
> 
> Ok, that's reasonable..

Thanks, I'm closing the bug on that basis then.

Ian.

--- End Message ---
Reply to: