All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: "Marco d'Itri" <md@Linux.IT>
Cc: debian-powerpc@lists.debian.org, debian-boot@lists.debian.org,
	linux-kernel@vger.kernel.org
Subject: Re: Debian Installer - boot floppies
Date: Sat, 4 Mar 2006 23:04:43 -0300	[thread overview]
Message-ID: <20060305020443.GA514@ime.usp.br> (raw)
In-Reply-To: <dudd93$frt$1@wonderland.linux.it>

On Mar 05 2006, Marco d'Itri wrote:
> sven.luther@wanadoo.fr wrote:
> >I guess we are using udev, but with a devfs-like naming scheme on
> >top, right ?  I strongly believe that swim3.ko is not hotplug
> >friendly, or that udev has some trouble with builtin modules, but i
> >would go for the first case.
>
> udev handles built-in drivers without problems, but it can create
> devices only for drivers which use the 2.6 driver core.

Nice to know that.

> If they have not been fixed yet then they are unmaintained or very
> close to this, and it's about time they are fixed or support is
> dropped.

It would be a real pitty to see swim3 dropped from the kernel. Speaking
as a mere user here, that's one of the main ways that I get information
into and from the old PowerMac 9500 that I have here.

And, I don't know if this has been reported earlier, but using mtools
(say, mcopy and friends) makes the drive become unusable (I don't
remember the messages literally here, because I'm not at the front of
the computer, but I can serve as a guinea pig if needed---despite my
lack of free time).


Thanks, Rogério Brito.

-- 
Rogério Brito : rbrito@ime.usp.br : http://www.ime.usp.br/~rbrito
Homepage of the algorithms package : http://algorithms.berlios.de
Homepage on freshmeat:  http://freshmeat.net/projects/algorithms/

           reply	other threads:[~2006-03-05  2:04 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <dudd93$frt$1@wonderland.linux.it>]

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=20060305020443.GA514@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=debian-boot@lists.debian.org \
    --cc=debian-powerpc@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@Linux.IT \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.