From: "Pablo Barbáchano" <pablobarbachano@yahoo.es>
To: 7eggert@gmx.de, linux-kernel@vger.kernel.org
Subject: Re: loop devices removable
Date: Wed, 14 Jun 2006 17:22:32 +0200 (CEST) [thread overview]
Message-ID: <20060614152232.17933.qmail@web26012.mail.ukl.yahoo.com> (raw)
In-Reply-To: <E1FqWt5-0001Ro-8q@be1.lrz>
--- Bodo Eggert <7eggert@elstempel.de> escribió:
> Pablo Barbachano <pablobarbachano@yahoo.es> wrote:
>
> [loop devices]
>
> > The (probably broken) reason I want to do that is so I can use (my
> > modified) pmount to mount them.
>
> I'm wondering if fuse would be suited better. I did not yet experiment
> with that, but it seems it has everything you need.
There is something based on FUSE:
http://lwn.net/Articles/173617/
Which involves UML... doesn't seem a good option to me...
My approach is simpler:
1. Change pmount so it supports loopback devices
2. Change the /dev/loop* group permissions.
You can accomplish 2 by modifying udev rules, the kernel or chgrp directly.
I just wondered if the kernel how the kernel could be changed and why it wouldn't be a good idea.
Cheers,
Pablo
> --
> Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
> verbreiteten Lügen zu sabotieren.
>
> http://david.woodhou.se/why-not-spf.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
Regístrate ya - http://correo.yahoo.es
next prev parent reply other threads:[~2006-06-14 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6nDUZ-4vk-17@gated-at.bofh.it>
2006-06-14 15:02 ` Bodo Eggert
2006-06-14 15:22 ` Pablo Barbáchano [this message]
2006-06-14 20:24 ` Bodo Eggert
2006-06-14 13:45 Pablo Barbachano
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=20060614152232.17933.qmail@web26012.mail.ukl.yahoo.com \
--to=pablobarbachano@yahoo.es \
--cc=7eggert@gmx.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®