I've written a patch (attached) to gvfs that enables permissions to be
read - which I've been using for a week or so. I have also written code
for the set operation but it needs a little bit more work to tidy up,
which I'm prepared to do if it's going to be adopted by Ubuntu. I have
submitted the
else\
echo include/linux/version.h ; \
Signed-off by: Lawrence Rust, l...@softsystem.co.uk
** Affects: kernel-package (Ubuntu)
Importance: Undecided
Status: New
--
Failed to build linux-image-2.6.33.rc1
https://bug
Public bug reported:
Binary package hint: linux-image-2.6.31-14-powerpc
Computer is a standard Macintosh blue & white (b/w) G3, 256 MB RAM, 5.7 GB IDE
disk.
Clean install ubuntu-9.04-server-powerpc with default settings.
Run sudo do-release-upgrade
Reboot drops to busybox shell with no root file
The patch in comment 8 is incomplete. There are 2 further errors in
vfat.c that need to be fixed relating to the size of the ms_dummy2 and
vs_dummy2 fields. The attached patch is correct for the latest version
2.16.1.
** Attachment added: "Patch for 2.16.1"
http://launchpadlibrarian.net/33031
Apologies for the delay in replying but I've been away for the last
week.
I fully take on board your comments and have reviewed the code in util-
linux-ng-2.15, noting that libblkid now uses a completely rewritten
method of probing for file systems.
It's clear that this problem stems from the new
I don't agree, this is a bug either in the base version of e2fsprogs
used or in the Ubuntu patches. To prove this I built the latest
e2fsprogs-1.41.9.tar.gz from SourceForge and ran
sudo /home/lvr/e2fs/sbin/blkid -c /dev/null /dev/sdb1
/dev/sdb1: LABEL="boot" UUID="41584c58-0cef-4d78-acd1-9a01ebd
blkid -p /dev/sdb1
/dev/sdb1: ambivalent result (probably more filesystems on the device)
Looks like a bug in libblkid. I mounted an 8.04 system partition and
ran /mnt/sblin/blkid and that also failed to identify sdb1 (it works
correctly when running 8.04). Unfortunately/predictably
LD_LIBRARY_P
This is the output of blkid from karmic alpha 5:
/dev/sda1: SEC_TYPE="msdos" LABEL="WIN98ME" UUID="2B5A-1E00" TYPE="vfat"
/dev/sda2: UUID="D4ACFF30ACFF0BAC" LABEL="WIN2K" TYPE="ntfs"
/dev/sdb3: LABEL="testsys" UUID="2b61ff01-e0df-45fc-86bc-f3db250e1534"
SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb5: L
Public bug reported:
Binary package hint: mount
Yesterday (11-sep-09) I ran "upgrade-manager -d" on a Kubuntu 9.04
system to upgrade to karmic koala alpha 5 . After rebooting I had 2
problems:
1. Grub was unable to load any kernel. Fixed by removing the /boot prefix from
the kernel and initrd
I can confirm this bug on a b/w G3 which was upgraded from Gustsy 7.10
(kernel 2.6.22).
Interestingly, the 2.6.24 kernel can be booted by specifying "Linux
root=/dev/hda3" at the yaboot prompt. The system functions OK but
without a CDROM.
This lead me to consider that it was the secondary IDE c
I can confirm this bug on a b/w G3 which was upgraded from Gustsy 7.10
(kernel 2.6.22).
Interestingly, the 2.6.24 kernel can be booted by specifying "Linux
root=/dev/hda3" at the yaboot prompt. The system functions OK but
without a CDROM.
This lead me to consider that it was the secondary IDE c
I can confirm this bug on a b/w G3 which was upgraded from Gustsy 7.10
(kernel 2.6.22).
Interestingly, the 2.6.24 kernel can be booted by specifying "Linux
root=/dev/hda3" at the yaboot prompt. The system functions OK but
without a CDROM.
This lead me to consider that it was the secondary IDE c
12 matches
Mail list logo
