From: "Fajar A. Nugraha" <list@fajar.net>
To: CACook@quantum-sci.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Cannot Deinstall a Debian Package
Date: Wed, 4 May 2011 09:44:20 +0700 [thread overview]
Message-ID: <BANLkTinxyFTWAoZ+pTeQYqDjaLoFSueMnQ@mail.gmail.com> (raw)
In-Reply-To: <201105031520.49993.CACook@quantum-sci.com>
On Wed, May 4, 2011 at 5:20 AM, <CACook@quantum-sci.com> wrote:
> On Tuesday 3 May, 2011 14:26:52 Fajar A. Nugraha wrote:
>> Does Debian (or whatever distro you use) support BTRFS "/"?
>> If yes, you should ask them.
>
> What do you mean 'does Debian support BTRFS'? =A0The kernel supports =
it.
Just because you can use something doesn't mean it's supported by the d=
istro.
=46or example, RHEL6 marks btrfs as "technology preview", in other word=
s
"you can use it to try out new features but don't complain if
anything's broken". There should be a similar warning in Debian.
In your case, the "broken" part is the integration with other distro
components (e.g grub)
> And why would they know more about BTRFS than you?
A good distro would normally test all components included, and mark
them as supported or not. If it's not supported, then you should
expect lower level of funcionality or integration compared to
supported components. Some signs of unsupported components:
- it's marked as "technology preview" (like in RHEL6 case)
- kernel supports it, but the distro installer does not let you use it
by default (needs some manual setup of installer flags)
- it's on a different repository (like Ubuntu's universe/multiverse)
- it's not listed as supported component
Sometimes when a distro includes a technology preview, they'd also
include known issues, caveats, or workaround needed to make it work.
In Ubuntu maverick (I suspect it's also the same in Debian) you need
to manually update to newer version of grub-pc.
>
> My whole system is installed over BTRFS. =A0If this is non-functional=
in any OS there should be a warning indicating it is non-functional.
>
There is, though the location and form may be distributed all over the =
place.
There's a warning in the kernel (see Chris's post)
Debian install manual
(http://www.debian.org/releases/stable/amd64/ch06s03.html.en#di-partiti=
on)
also doesn't list btrfs as supported partition type, in other words
it's unsupported.
>
>> Looks like grub problem. I know that Ubuntu Natty's grub-pc (grub2)
>> work just fine, so you might be able to fix it by upgrading to newer
>> grub/grub-pc (perhaps from Debian-unstable).
>
> I would be happy to upgrade grub, but the package management system i=
s jammed because of this.
You can download grub-related packages (should be grub and grub-pc,
possibly from Debian unstable) and install it manually using dpkg.
You might also need to temporarily rename /usr/sbin/update-grub
manually elsewhere and replace it with symlink to /bin/true, or move
/etc/kernel/postinst.d/zz-update-grub out of the way (just to enable
update process run correctly).
--=20
=46ajar
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-04 2:44 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 19:27 Cannot Deinstall a Debian Package CACook
2011-05-03 21:26 ` Fajar A. Nugraha
2011-05-03 22:20 ` CACook
2011-05-03 23:02 ` Chuck Burns
2011-05-04 0:12 ` CACook
2011-05-04 0:25 ` Chuck Burns
2011-05-04 1:20 ` Chris Samuel
2011-05-04 2:44 ` Fajar A. Nugraha [this message]
2011-05-04 9:51 ` Sander
2011-05-05 14:49 ` CACook
2011-05-05 18:09 ` CACook
2011-05-05 19:09 ` cwillu
2011-05-05 19:28 ` cwillu
2011-05-05 19:50 ` CACook
2011-05-05 19:55 ` Chris Mason
2011-05-05 20:32 ` CACook
2011-05-05 20:40 ` cwillu
2011-05-05 21:40 ` CACook
2011-05-05 21:48 ` cwillu
2011-05-05 22:33 ` CACook
2011-05-05 23:06 ` Miguel Garrido
2011-05-06 3:53 ` Helmut Hullen
2011-05-06 6:49 ` Sander
2011-05-05 20:31 ` cwillu
2011-05-05 20:57 ` CACook
2011-05-05 20:59 ` Lars Wirzenius
2011-05-05 21:48 ` CACook
2011-05-05 21:50 ` cwillu
2011-05-05 21:11 ` cwillu
2011-05-06 6:43 ` Sander
2011-05-06 6:33 ` Sander
2011-05-06 12:09 ` CACook
2011-05-06 12:20 ` Sander
2011-05-06 12:57 ` CACook
2011-05-06 13:21 ` Sander
2011-05-06 13:56 ` CACook
2011-05-06 14:17 ` Sander
2011-05-06 14:53 ` CACook
2011-05-06 14:58 ` Sander
2011-05-06 15:15 ` CACook
2011-05-06 17:09 ` CACook
2011-05-06 20:04 ` CACook
2011-05-06 20:16 ` Tomasz Torcz
2011-05-06 20:56 ` CACook
2011-05-06 21:23 ` Peter Stuge
2011-05-06 20:40 ` Sander
2011-05-06 20:51 ` Peter Stuge
2011-05-06 21:20 ` CACook
2011-05-06 21:28 ` Peter Stuge
2011-05-06 21:32 ` Hugo Mills
2011-05-06 22:17 ` David G Beausang
2011-05-07 1:51 ` C Anthony Risinger
2011-05-07 2:05 ` C Anthony Risinger
[not found] ` <201105062008.26159.CACook@quantum-sci.com>
2011-05-07 6:21 ` C Anthony Risinger
2011-05-07 7:03 ` Helmut Hullen
2011-05-06 13:30 ` Helmut Hullen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinxyFTWAoZ+pTeQYqDjaLoFSueMnQ@mail.gmail.com \
--to=list@fajar.net \
--cc=CACook@quantum-sci.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).