Bug#47490: marked as done (ask when mke2fs'ing whether to create sparse superblocks)
Your message dated Mon, 03 Jan 2000 14:52:09 -0500
with message-id <20000103195209.402B7938CB@arroz.fake>
and subject line bugs fixed in boot-floppies 2.2.4
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 15 Oct 1999 10:49:06 +0000
Received: (qmail 32532 invoked from network); 15 Oct 1999 10:49:05 -0000
Received: from unknown (HELO www.starshine.org) (qmailr@209.157.85.7)
by master.debian.org with SMTP; 15 Oct 1999 10:49:05 -0000
Received: (qmail 14167 invoked from network); 15 Oct 1999 10:49:20 -0000
Received: from antares.in.starshine.org (HELO antares.starshine.org) (209.157.85.17)
by www.starshine.org with SMTP; 15 Oct 1999 10:49:20 -0000
Received: from canopus2.starshine.org (saturn.in.starshine.org [209.157.85.27])
by antares.starshine.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id DAA12345;
Fri, 15 Oct 1999 03:41:04 -0700
Received: (from jimd@localhost)
by canopus2.starshine.org (8.9.3/8.8.8) id DAA21194;
Fri, 15 Oct 1999 03:49:10 -0700
Date: Fri, 15 Oct 1999 03:49:10 -0700
Message-Id: <199910151049.DAA21194@canopus2.starshine.org>
From: Jim Dennis <jimd@starshine.org>
Subject: base: mke2fs makes unmountable filesystems; mount doesn't honor -o nocheck
To: submit@bugs.debian.org
X-Mailer: bug 3.2.6
Package: base
Version: 19991015
Severity: important
I was wrong. Earlier I claimed that mount was
unable to handle a filesystem with a non-default
inode/block ratio ("couldn't mount RDWR"). However,
my reasoning was wrong.
In actuality the new mke2fs is making filesystems that
the latest mount command will not tolerate.
I've heard that we need to start using the
mount -o nocheck (or check=none) option to mount the
newly created filesystems with the "sparse superblock"
features.
However, that option is not honored with my copy of
mount (2.9x). mke2fs version is 1.15.
e2fsprogs version 1.15-3
-- System Information
Debian Release: potato
Kernel Version: Linux canopus2 2.0.36 #2 Sun Feb 21 15:55:27 EST 1999 i586 unknown
---------------------------------------
Received: (at 47490-done) by bugs.debian.org; 3 Jan 2000 19:48:44 +0000
Received: (qmail 25339 invoked from network); 3 Jan 2000 19:48:40 -0000
Received: from 209-122-226-23.s277.tnt1.nyw.ny.dialup.rcn.com (HELO arroz.fake) (@209.122.226.23)
by master.debian.org with SMTP; 3 Jan 2000 19:48:40 -0000
Received: by arroz.fake (Postfix, from userid 421)
id 402B7938CB; Mon, 3 Jan 2000 14:52:09 -0500 (EST)
To: 11926-done@bugs.debian.org, 21867-done@bugs.debian.org,
23337-done@bugs.debian.org, 27650-done@bugs.debian.org,
33950-done@bugs.debian.org, 35873-done@bugs.debian.org,
36657-done@bugs.debian.org, 47490-done@bugs.debian.org,
48779-done@bugs.debian.org, 48866-done@bugs.debian.org,
52596-done@bugs.debian.org
Subject: bugs fixed in boot-floppies 2.2.4
From: Adam Di Carlo <adam@onshore.com>
Date: Mon, 03 Jan 2000 14:52:09 -0500
Sender: apharris@burrito.onshore.com
Message-Id: <20000103195209.402B7938CB@arroz.fake>
Thank you for your bug report. The bug should have been closed by
boot-floppies version 2.2.4, now in unstable (for i386, others
following shortly). Let us know if you have any more problems.
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Changes: boot-floppies (2.2.4) unstable; urgency=low
.
* fdisk: using the 2.2 features of the /proc file-system, we should be
able to detect any and all kernel-supported r/w random-access devices
* dbootstrap: installation via HTTP method (net-fetch) added; messages
not yet tuned, this method should work fine but might not look pretty
yet
* dbootstrap: look for files and stuff in
dists/potato/main/disks-%s/current where %s is the architecture name
* busybox: more updates, fixing some critical problems in tar (setuid
not respected, files with symlinks to them (i.e. libc) set to 777),
cp, and mv didn't work for directories; fix problem where symlink
targets were made world-writable (!)
* dbootstrap: when writing /etc/fstab, use tabs (closes: Bug#11926,
Bug#36657)
* dbootstrap: add commented out /dev/pts example to /etc/fstab
(closes: Bug#33950)
* dbootstrap: don't ask about GMT or not on m68k; when we *do* ask about
it, do it in one dialog box, not two; look for UTC not GMT in
/etc/default/rcS (closes: Bug#48866)
* base: remove setserial from sparc platform
* base: add xviddetect, and pciutils -- these are not yet integrated,
however; debconf-tiny integration put off due to critical
perl-5.005-base bugs
* rescue: rdev.sh handles an alternate kernel location as an optional
argument (closes: Bug#27650)
* dbootstrap: ask when mke2fs'ing whether to use 2.2 specific features
(closes: Bug#47490)
* dbootstrap: change the wording of the name server selection
(closes: Bug#23337); many other wording changes
* dbootstrap: don't put `vga=normal' in the default lilo.conf since it
apparently breaks MDA graphics cards (closes: Bug#35873)
* top-level Makefile: check for dependancies by examining
/var/lib/dpkg/status instead of running `dpkg --get-selections' since
the latter only shows whether a package is *selected* for installation
(closes: Bug#52596)
* scripts/basedisks/new_root_home/.bash_profile: trap `:' instead of `""'
so that children don't ignore the signals (closes: Bug#21867)
* dbootstrap: be more specific when prompting for floppies
(closes: Bug#48779)
* debian/rules: scrub /usr/src/boot-floppies.tar.gz more, removing wierd
ownership and permissions
Reply to: