public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Con Kolivas <kernel@kolivas.org>
To: Gustavo Guillermo Perez <gustavo@compunauta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Supermount / ivman
Date: Sun, 23 Jan 2005 14:32:36 +1100	[thread overview]
Message-ID: <41F31AD4.6030707@kolivas.org> (raw)
In-Reply-To: <200501232126.08575.gustavo@compunauta.com>

[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]

Gustavo Guillermo Perez wrote:
> Cause I play with old toys, (floppys) and ivman doesn't work properly on the 
> lastest gentoo with floppys, I retouch for a while the supermount patch from 
> sourceforge for kernel 2.6.11-rc1.
> 
> I'm a n00b on kernel, I do this only for general purposes helping some 
> friends, I know supermount should not be used, and is not mantained, I've 
> tested it just only for IDE/ATAPI CD/DVD and floppys.
> 
> Cause Supermount seems to be a filesystem I replace vfs_permission by 
> generic_permission instead of permission as I read on the lkml. Other stuffs 
> too in scsi section (I don't have scsi hardware).
> 
> If Help someone else:
> 
> http://www.compunauta.com/forums/linux/instalarlinux/supermount_en.html
> 

I've been silently maintaining it offlist. No real development but 
keeping it in sync and fixing obvious bugs that show up that I can fix.

Here's a patch for 2.6.10-ck5 (should apply fairly cleanly to 2.6.10):
http://ck.kolivas.org/patches/2.6/2.6.10/2.6.10-ck5/patches/supermount-ng208-10ck5.diff

and for 2.6.11-rc1
http://ck.kolivas.org/patches/2.6/2.6.11-rc1/patches/supermount-ng208-2611rc1.diff

Cheers,
Con

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

      reply	other threads:[~2005-01-23  3:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 21:26 Supermount / ivman Gustavo Guillermo Perez
2005-01-23  3:32 ` Con Kolivas [this message]

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=41F31AD4.6030707@kolivas.org \
    --to=kernel@kolivas.org \
    --cc=gustavo@compunauta.com \
    --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