From: Pavel Machek <pavel@ucw.cz>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: Brian Schau <brian@schau.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Wireless Security Lock driver.
Date: Sun, 31 Jul 2005 16:08:40 +0200 [thread overview]
Message-ID: <20050731140840.GK9418@elf.ucw.cz> (raw)
In-Reply-To: <200507311459.00957.s0348365@sms.ed.ac.uk>
Hi!
> > > I've attached a gzipped version of my Wireless Security Lock patch
> > > for v2.6.13-rc4.
> > > A Wireless Security Lock (WSL or weasel :-) is made up of two parts.
> > > One part is a receiver which you plug into any available USB port.
> > > The other part is a transmitter which at fixed intervals sends
> > > "ping packets".
> > > A "ping packet" usually consists of an ID and a flag telling if the
> > > transmitter has just been turned on.
> >
> > Idea is good... but why don't you simply use bluetooth (built into
> > many notebooks) and bluetooth-enabled phone?
> >
> > Probably could be done in userspace, too :-).
>
> There's a script to this on the gentoo wiki via BlueZ.
>
> http://gentoo-wiki.com/TIP_Bluetooth_Proximity_Monitor
>
> I personally think the problem with this approach is that most phones have
> bluetooth enabled explicitly as an option, it doesn't run all the time, or
> default on. Primarily this is because bluetooth can drain your phone's
> battery (though, I don't know by how much, if you're not actually
> transferring data over it).
I have bluetooth turned on all the time, anyway, and it does not drain
battery that badly (standby time goes down 30%?).
> A CR2032 cell, in a specific piece of kit, is going to last for a lot longer
> than a phone battery.
Well, you know... phones have *rechargable* batteries :-).
--
if you have sharp zaurus hardware you don't need... you know my address
prev parent reply other threads:[~2005-07-31 14:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 14:51 Brian Schau
2005-07-30 15:01 ` Michael Krufky
2005-07-30 15:16 ` Brian Schau
2005-07-30 15:57 ` Zwane Mwaikambo
2005-07-30 16:02 ` Brian Schau
2005-07-30 17:11 ` Michael Krufky
2005-07-30 18:05 ` Brian Schau
2005-07-30 19:42 ` Pavel Machek
2005-07-30 20:10 ` Brian Schau
2005-07-30 20:31 ` Pavel Machek
2005-07-30 21:14 ` Brian Schau
2005-07-30 21:16 ` Pavel Machek
2005-07-30 22:06 ` Brian Schau
2005-07-31 8:42 ` James Cloos
2005-07-31 9:52 ` Pavel Machek
2005-07-31 12:43 ` Brian Schau
2005-07-31 16:14 ` James Cloos
2005-07-31 13:59 ` Alistair John Strachan
2005-07-31 14:08 ` Pavel Machek [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=20050731140840.GK9418@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=brian@schau.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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®