From 46b1f05a5ed1de5ff8d948951ba5464fafe50f92 Mon Sep 17 00:00:00 2001 From: freesource Date: Wed, 13 Feb 2002 20:25:00 +0000 Subject: [PATCH] 1.3.5 --- pkg/dpkg/changelog | 34 ++++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/pkg/dpkg/changelog b/pkg/dpkg/changelog index bf81dfd..839e0b6 100644 --- a/pkg/dpkg/changelog +++ b/pkg/dpkg/changelog @@ -1,3 +1,37 @@ +gbootroot (1.3.5-1) unstable; urgency=low + + * Now the template called Helper.yard used to create the + root_fs_helper is included with root_fs_helper. + * 1.3.4 was awarded Editor's pick by SoftLandMark, but I recommend + upgrading to 1.3.5 because of my oversight with the root_fs_helper + issue, as well as the improved initrd testing capability of the + specially patched 2.4.17-10um kernel. I also recommend running + gbootroot as a normal user, at least that's what I usually do. :) + * Root_fs_helper was working fine, but because I hadn't committed, let + alone copied the new changes to CVS I didn't notice any aberrations + until I installed the new released version of gbootroot. This is + related to the new securretty requirements of uml. Problem fixed. + * Initrd was not working with any fs other than ext2. After + contacting the trinux-uml project, Matthew Franz + confirmed that he was having problems creating a working uml for the + initrd created by Bill Burdick . I + talked Bill into sending me his uml .config, and narrowed down the + problem to cramfs. Cramfs has known bugs as documented in the + kernel sources. Because cramfs was placed before just about every + fs in the VFS check order, and trinux-uml's initrd was minix, the + kernel failed, but an ext2 initrd didn't. Changing the order in + which filesystems are checked during the VFS stage by editing + fs/Makefile solves the problem. Thanks to Henrik Nordstrom + for pointing out how to do this at user-mode- + linux-devel. I am hoping the patch found in user-mode- + linux/usr/lib/uml/cramfs-vfs-oder.patch becomes part of uml. This + should have been corrected ages ago in the standard Linux kernel. + * Removed unecessary warning which warned that left-hand side + replacements couldn't be a directory if it happened to find that + directory on the hostfs. Directories can be replacements. + + -- Jonathan Rosenbaum Wed, 13 Feb 2002 15:11:41 -0500 + gbootroot (1.3.4-1) unstable; urgency=low * Updated to 2.4.17-10um and added Jeff's initrd fix.