All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+hb@blue-labs.org>
To: as@sci.fi
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 vs 2.6
Date: Mon, 15 Dec 2003 12:25:31 -0500	[thread overview]
Message-ID: <3FDDEE8B.3080000@blue-labs.org> (raw)
In-Reply-To: <20031215105602.8E693B802@hylsy.jippii.fi>

Partial comments below

Anssi Saari wrote:

>>  -- modules don't autoload for some reason (though I'm sure that could
>>     be solved),
>>    
>>
>
>I've had this too, with autofs4 and 3c59x. After patching lirc into the
>kernel, the only real issue is with the console. I found a patch for radeonfb,
>but didn't get anywhere with it.
>
>The rest of my problems is userland stuff:
>
>- Murasaki (a hotplug agent) doesn't react when USB things are plugged in
>  
>

You need to update your hotplug installation.  Turn on debugging in your 
hotplug scripts and copy the appropriate object ID numbers into the 
usb.usermap file.

>- swapon -a takes two minutes to complete for some reason
>  
>

Try recreating your swapon partition/file?  Turning on a gig of swap 
here happens pretty quick.

>- rpc.lockd doesn't start, it says lockdsvc: Function not implemented. I don't
>  
>

Update/rebuild your rpc/nfs tools.

>  know if I really need this anyway, nfs seems to work fine
>- zsh doesn't complete make targets like menuconfig
>- I'd also like to point out that cdrecord isn't sufficient for my 
>  CD writing needs, I need cdrdao too and it doesn't seem to support
>  direct access to ATAPI drives. 
>  
>

I haven't used zsh or cdrdao so I can't comment on them.   I don't use 
the above modules, but all the other modules on my system (numerous) do 
autoload just fine.  NFS is a big PITA for me for other reasons but the 
services do start.

My systems are of the Gentoo flavor.

David


  reply	other threads:[~2003-12-15 17:25 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.iaibikf.1l5injd@ifi.uio.no>
     [not found] ` <fa.m5245vp.h0ukb5@ifi.uio.no>
2003-12-15 10:56   ` 2.4 vs 2.6 Anssi Saari
2003-12-15 17:25     ` David Ford [this message]
2006-05-25  7:35 Vijay Chauhan
2006-05-26  7:29 ` Neil Brown
2006-05-26  7:30   ` Neil Brown
2006-05-26  8:19   ` mehta kiran
2006-05-26 19:31     ` J. Bruce Fields
2006-05-29  5:55       ` Neil Brown
2006-05-29  8:52         ` mehta kiran
2006-05-29 16:02         ` J. Bruce Fields
2006-05-30  1:12           ` Greg Banks
2006-05-30  1:59             ` J. Bruce Fields
2006-06-13  3:29               ` Neil Brown
2006-06-13 20:42                 ` J. Bruce Fields
2006-06-13 23:22                   ` Neil Brown
2006-06-14  1:29                   ` Greg Banks
2006-06-14  2:15                     ` J. Bruce Fields
2006-06-14  2:22                       ` Greg Banks
2006-06-14  4:18                         ` Neil Brown
2006-06-14  4:36                           ` Greg Banks
2006-06-14 19:40                     ` William A.(Andy) Adamson
2006-06-15  3:17                       ` Greg Banks
  -- strict thread matches above, loose matches on Subject: below --
2003-12-01  6:20 XFS for 2.4 Nathan Scott
2003-12-01 14:06 ` Marcelo Tosatti
2003-12-14  1:08   ` 2.4 vs 2.6 Jan Rychter
2003-12-14  1:01     ` Roberto Sanchez
2003-12-14 11:23       ` Måns Rullgård
2003-12-14 18:09         ` Daniel Gryniewicz
2003-12-14  1:53     ` Daniel Gryniewicz
2003-12-14  2:01     ` coderman
2003-12-14 20:23       ` tabris
2003-12-14  7:05     ` Voicu Liviu
2003-12-14 16:01       ` Roberto Sanchez
2003-12-14 17:32         ` Voicu Liviu
2003-12-15  7:23           ` Harry McGregor
2003-12-15  7:51             ` Voicu Liviu
2003-12-14 11:24     ` Frederik Deweerdt

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=3FDDEE8B.3080000@blue-labs.org \
    --to=david+hb@blue-labs.org \
    --cc=as@sci.fi \
    --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 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.