From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: FUSE (was: Add a module post kernel config/build)
Date: Thu, 19 Apr 2007 14:15:26 +0100 [thread overview]
Message-ID: <20070419141526.387fd2fc@krikkit.digimed.co.uk> (raw)
In-Reply-To: <87lkgolk0v.fsf@newsguy.com>
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
Hello reader@newsguy.com,
> > hm. What's unclear? You have build fuse only for this kernel
> > version. When you update your kernel, you'll need to rebuild
> > all the external modules (fuse, maybe alsa, ...). module-rebuild
> > is your friend.
>
> Whats unclear is why I have to do anything extra for this kernel when
> I did not in past 2.
You probably ran module-rebuild without realising it covered fuse too.
You could avoid all this hassle by enabling fuse in your kernel. Out of
tree drivers cause extras hassle and should only be used when the
in-kernel drivers are not suitable for your needs.
--
Neil Bothwick
He's dead, Jim. Just like your career.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-19 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-18 9:15 [gentoo-user] Add a module post kernel config/build reader
2007-04-18 10:33 ` Boyd Stephen Smith Jr.
2007-04-19 0:44 ` [gentoo-user] " reader
2007-04-18 10:37 ` Alexander Skwar
2007-04-18 12:50 ` Neil Bothwick
2007-04-18 13:35 ` [gentoo-user] FUSE (was: Add a module post kernel config/build) Alexander Skwar
2007-04-18 15:00 ` Neil Bothwick
2007-04-19 0:40 ` [gentoo-user] " reader
2007-04-19 4:42 ` Nistor Andrei
2007-04-19 6:58 ` Alexander Skwar
2007-04-19 10:45 ` reader
2007-04-19 13:15 ` Neil Bothwick [this message]
2007-04-18 10:47 ` [gentoo-user] Add a module post kernel config/build Mike Williams
2007-04-18 11:10 ` Etaoin Shrdlu
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=20070419141526.387fd2fc@krikkit.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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