public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Stirling <ian.stirling@mauve.plus.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APM realy sucks on 2.6.x
Date: Tue, 08 Jun 2004 21:18:31 +0100	[thread overview]
Message-ID: <40C61F17.4070601@mauve.plus.com> (raw)
In-Reply-To: <ca4tt4$p5t$2@gatekeeper.tmr.com>

Bill Davidsen wrote:
> Pavel Machek wrote:
> 
>> Hi!
>>
>>
>>> | PCMCIA... well, that's another obsolete technology. Too bad.
>>>
>>> PCMCIA is obsolete? Did I miss something, or was this a joke?
<snip>
> 
> Cardbus maybe, USB not. USB is very nice, but it's not typically SMALL. 
> A PCMCIA NIC card is a credit card size, a USB NIC is a box plus a 
> cable. Before you tell me I don't need it please name the affordable 
> laptop which has 2 NICs.

My USB nic is about 1.5*1.5*6cm, 10/100mbps ethernet, works with linux, cost
around $10 from ebay. Unfortunately, I've lost it, as it's rather small. Argh.

A problem with USB is that the connector is terribly designed for laptops.
A 5cm lever sticking out of laptops are bad. I've got several hacked plugs that
reduce this to 1cm, which is bearable.

IMO, all laptop connectors should be breakaway, when pulling the cable to detach
the connector at any angle does not destroy the connector.

It's only been a couple of years since the majority of low-end 802.11b cards being
sold were PCMCIA.




  parent reply	other threads:[~2004-06-08 20:19 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-04 21:26 APM realy sucks on 2.6.x Sebastian Kloska
2004-06-04 23:14 ` Keith Duthie
2004-06-05  8:03   ` Sebastian Kloska
2004-06-04 23:54 ` Hugh Dickins
2004-06-05 17:18   ` Sebastian Kloska
2004-06-06  3:29     ` Michael Clark
2004-06-06  4:25       ` Andrew Morton
2004-06-06 13:56         ` Sebastian Kloska
2004-06-07 12:38 ` Pavel Machek
2004-06-07 13:37   ` Sebastian Kloska
2004-06-07 14:05     ` Pavel Machek
2004-06-07 14:28       ` Sebastian Kloska
2004-06-07 14:48         ` Pavel Machek
2004-06-07 19:53           ` Felipe Alfaro Solana
2004-06-07 21:13             ` Sebastian Kloska
2004-06-08  4:16           ` Clemens Schwaighofer
2004-06-08  7:12             ` Sebastian Kloska
2004-06-08  8:58             ` Pavel Machek
2004-06-08  9:02               ` Clemens Schwaighofer
2004-06-08  9:17                 ` Pavel Machek
2004-06-08  9:50                   ` Clemens Schwaighofer
2004-06-08  9:55                     ` Pavel Machek
2004-06-08 23:59                       ` Clemens Schwaighofer
2004-06-08 17:48               ` Bill Davidsen
2004-06-08 18:59                 ` Daniel Gryniewicz
2004-06-08 20:18                 ` Ian Stirling [this message]
2004-06-07 14:42     ` Keith Duthie
2004-06-07 14:44       ` Pavel Machek
2004-06-07 14:47       ` Sebastian Kloska
2004-06-07 14:51         ` Pavel Machek
2004-06-07 15:09           ` Sebastian Kloska
2004-06-07 16:26             ` Pavel Machek
2004-06-07 15:19         ` Keith Duthie
  -- strict thread matches above, loose matches on Subject: below --
2004-06-07  8:11 Sebastian Kloska
2004-06-08  9:49 Sau Dan Lee

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=40C61F17.4070601@mauve.plus.com \
    --to=ian.stirling@mauve.plus.com \
    --cc=davidsen@tmr.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