Content-Type: text/plain
debian-user-digest Digest Volume 2014 : Issue 872
Today's Topics:
Re: strangely odd [ Bzzzz <lazyvirus@gmx.com> ]
Re: Is grub =?UTF-8?Q?perfect=3F=20= [ berenger.morel@neutralite.org ]
Re: strangely odd [ Floris <jkfloris@dds.nl> ]
Re: strangely odd [ Bzzzz <lazyvirus@gmx.com> ]
Re: building .debs with "+b1" on the [ Jonathan Dowland <jmtd@debian.org> ]
Re: Learning package building - tuto [ Jonathan Dowland <jmtd@debian.org> ]
exim4 with spamassassin ... confused [ Harry Putnam <reader@newsguy.com> ]
Re: simple database solution without [ Steve Litt <slitt@troubleshooters.c ]
Re: Deluge disappears [ berenger.morel@neutralite.org ]
Re: I'm not a huge fan of systemd [ Brian <ad44@cityscape.co.uk> ]
Re: simple database solution without [ Slavko <linux@slavino.sk> ]
Re: IEEE 802.11-USB adapters with RT [ peter@easthope.ca ]
Re: I'm not a huge fan of systemd [ Brian <ad44@cityscape.co.uk> ]
Date: Mon, 7 Jul 2014 16:21:30 +0200
From: Bzzzz <lazyvirus@gmx.com>
To: debian-user@lists.debian.org
Subject: Re: strangely odd
Message-ID: <[🔎] 20140707162130.4f2917e0@anubis.defcon1>
Content-Type: multipart/signed; micalg=pgp-sha512;
boundary="Sig_/yHe1_nG_T31u3DRrLlBEDXf"; protocol="application/pgp-signature"
--Sig_/yHe1_nG_T31u3DRrLlBEDXf
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Mon, 07 Jul 2014 16:16:15 +0200
Floris <jkfloris@dds.nl> wrote:
> apt-xapian-index runs update-apt-xapian-index as a cron job
> daily. Synaptic will also runs this command in the background to
> rebuild the database. You can also run it manually as root and see
> how long it takes. Especially when you rebuild the entire database
> instead of an update.
That was my conclusion (~1H passed before re-opening), but
I didn't launched anything manually (!).
--=20
A real friend isn't someone you use once and then throw away.
A real friend is someone you can use over and over again.
--Sig_/yHe1_nG_T31u3DRrLlBEDXf
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJTuqzqAAoJEF7bOzrWeFEBbpAQAIXzGHGKsnTrbK9sFcdb/dib
PUp5LZYzfhNxDB8kPHDFgDxxYyH7L9gDa7CsQOmdlilptSf9agJNiM0I//0+JTKX
UMZmA+MSAERjceAJ8gIEKNNph2J9ma0U7uzRjB0EOWo8DWXnM7v5UhNXKHcFqvuP
LgGsYP7V0ejdXZ9fS5AvA0+cmmyD+kNrQo8o+KUcyc2l+QT4pPJV7pnvoZkz9T6m
Vi55SwYEnseNS83BPWOTsop2TpsvOVdZEhkJY1Q3bzoyCPCIdvAJsG7H5KkK5iSZ
CNvTH77IJMtmoC/ON6KeUa75H5uuCzfx7cEudCH29Siy1y/yajtS4IDJIpvpUm+M
KkMhe7JC2VwcFfgKFj/g4NPp+LHJ16KtGrnREsQ/5IdIvGasyzncVD6/uLxBzpeQ
yOqsh5xgUrDavnMigG+wwg/v8xY5hMbyiL64conLFwPV2lILJoOQRMAo+WsPC/Yj
E3O+NjBCXMKjby+wcnd/4USsrOIuEVjwpgRL1FnuoOAwgAdsqySs73lxESW36hL6
wCRgELtz4fErpfqTXZSsFjaNAvjhRovLCiCop2rIVFEDAakRRBVP7Xf1AHcp/TiX
YjKH3gi4CzzNQfKJwzT7UJG+y3JxQ0cDCUExWDyjev5V2M4vFqLyj1Y6IAk4v69E
T3OEmGllPvFD3kM56OWO
=hG+4
-----END PGP SIGNATURE-----
--Sig_/yHe1_nG_T31u3DRrLlBEDXf--
Date: Mon, 07 Jul 2014 16:21:38 +0200
From: berenger.morel@neutralite.org
To: <debian-user@lists.debian.org>
Subject: Re: Is grub =?UTF-8?Q?perfect=3F=20=28was=20Re=3A=20Does=20LXDE?=
=?UTF-8?Q?=20really=20require=20lightdm=3F=29?=
Message-ID: <[🔎] 4ebd17ad78c9be7b9fd1a5be4a4a84f2@neutralite.org">[🔎] 4ebd17ad78c9be7b9fd1a5be4a4a84f2@neutralite.org>
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: quoted-printable
Le 30.06.2014 20:33, Ric Moore a =C3=A9crit=C2=A0:
> On 06/30/2014 06:24 AM, berenger.morel@neutralite.org wrote:
>>
>>
>> Le 28.06.2014 05:14, slitt a =C3=A9crit :
>>> On Sat, 28 Jun 2014 09:33:57 +0900
>>> Joel Rees <joel.rees@gmail.com> wrote:
>>>
>>>> On Sat, Jun 28, 2014 at 7:48 AM, [...]
>>>> > Grub is a *boot loader*.
>>>>
>>>> Lately (last few years), it seems to be trying to do a lot more.
>>>>
>>>> > What do you expect it to do? Mind read?
>>>>
>>>> I'd almost say that's one of the things the devs are trying to=20
>>>> make
>>>> it do.
>>>>
>>>
>>> I have a feeling that a lot of this thread got procmailed to
>>> my /dev/null, but for the person who asked what I wanted it to do,
>>> that's simple: Boot the damn computer with a menu to choose=20
>>> predefined
>>> kernel/initrd/disk combinations, and nothing else. And for gosh=20
>>> sakes,
>>> keep it in one file. If a config option is about "pretty", leave=20
>>> that
>>> feature out.
>>>
>>> In other words, grub1.
>>>
>>> SteveT
>>
>> Otherwise, if you do not like grub, there are other boot loaders.=20
>> LILO
>> at least works fine, and seems to be ok for your requirements: a=20
>> single
>> easy text file as configuration.
>> It's what I'm doing, excepted at work for 2 reasons: it does not=20
>> seems
>> to support the new crap named... how is it named? Secure boot?=20
>> Something
>> like that. The fun thing about that is that the grub installation=20
>> did
>> not allowed me to have a dual boot with the original windows, so I=20
>> could
>> be using LILO right now it would not change anything.
>> The other reason is that I do prefer mainstream stuff on computers=20
>> that
>> I do not want to tinker. Never had any problem with LILO, but just=20
>> in
>> case...
>
> I installed grub-customizer from source and it works a charm, with=20
> grub2. Ric
Oh, and (sorry for long time reply, I did not found lot of time to read=20
my personal mails) there is another bootloader in the wild.
Extlinux. I'm tinkering with it, since I want to build an external disk=20
able to boot various live ISOs (tails and kali to name them) plus 3=20
distros (probably Debian for real uses, plus gentoo and a *BSD for=""> experimenting). For now my disk was not bootable, but that's a story for=""> another thread, in the case I won't be able to solve my issue myself.
Date: Mon, 07 Jul 2014 16:27:26 +0200
From: Floris <jkfloris@dds.nl>
To: debian-user@lists.debian.org
Subject: Re: strangely odd
Message-ID: <[🔎] op.xims30s45k9y7g@alice.jkfloris.demon.nl">[🔎] op.xims30s45k9y7g@alice.jkfloris.demon.nl>
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Op Mon, 07 Jul 2014 16:21:30 +0200 schreef Bzzzz <lazyvirus@gmx.com>:
> On Mon, 07 Jul 2014 16:16:15 +0200
> Floris <jkfloris@dds.nl> wrote:
>
>> apt-xapian-index runs update-apt-xapian-index as a cron job
>> daily. Synaptic will also runs this command in the background to
>> rebuild the database. You can also run it manually as root and see
>> how long it takes. Especially when you rebuild the entire database
>> instead of an update.
>
> That was my conclusion (~1H passed before re-opening), but
> I didn't launched anything manually (!).
>
synaptic has launched it when you open it an hour ago.
floris
Date: Mon, 7 Jul 2014 16:32:19 +0200
From: Bzzzz <lazyvirus@gmx.com>
To: debian-user@lists.debian.org
Subject: Re: strangely odd
Message-ID: <[🔎] 20140707163219.6bc41fda@anubis.defcon1>
Content-Type: multipart/signed; micalg=pgp-sha512;
boundary="Sig_/l5TWtGYMh83QhqY47pZm6Ze"; protocol="application/pgp-signature"
--Sig_/l5TWtGYMh83QhqY47pZm6Ze
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Mon, 07 Jul 2014 16:27:26 +0200
Floris <jkfloris@dds.nl> wrote:
> synaptic has launched it when you open it an hour ago.
I should sleep more, that didn't came to my mind :(
Thanks for your helpful answers.
--=20
Melethon: not a bad picture=E2=80=A6 a real mermaid
Paupau: you really think that :D you're so cute!
Melethon: for sure, half-tuna half-human, this is quite unusual
* Paupau is now offline
--Sig_/l5TWtGYMh83QhqY47pZm6Ze
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCgAGBQJTuq9zAAoJEF7bOzrWeFEBixYP/igtSWotW57rMEf6taaJI3/A
vaJ2E4bSX2Xop6ozUyDJQ5c5uOhn7s3pq9+lzeTAGU5rshBCQAcH4ZI0GYaglTlB
nTW2F6VKz9Hm6NR/jM8Lnb1BsH1K1flHazFUpakIsk2vcyydmQ8N4f8xV/7JsZr2
DF/x7v8CC39tRdWC5if4zxdZcO/wdAU5J5HdEshOhGznVZIQMvvwL/aBxi+OlW+x
gK9dVjr5MtaRk5fX+o/kdz+teAmja5RyqR9WM3IPVufUh1qu1uiCWHe810z5g7j4
La0kq0uLmBqsjcuAqiU5ZHil2ka9tUu6/CndVyxEbEISzg46C8CVKihd9isVQwL3
VDSSwNGR+njbrlno3XLPZ0nobksR+4SPwtGr24WS6DTc1c1wDGdjengE2Z/uDsmm
Q927eEsxl0dNrc9g0jAKHl5tqfKRHqPxADmakajNyspo6NXlYnDCGJy25bepiMrF
vvScZvlf3lkHd7G4grMzYodYnjka5HgzGrJJpaXfaficnclFXQINkMAR4p/kAcI3
jcyq/LrQQDYXDlOxTFjP4N0fx5i7n072zhkMkyBXELqej6BKfVn8nyx+A65uH9nL
tDPkRXFw7YMlI0YtYM4RhNiWS9MCMVv6HQWsvfaF8saZ42UNyx9vuVrqnYrMTff8
o/L74VOa9tn5TT0r09zG
=qgwE
-----END PGP SIGNATURE-----
--Sig_/l5TWtGYMh83QhqY47pZm6Ze--
Date: Mon, 7 Jul 2014 15:55:22 +0100
From: Jonathan Dowland <jmtd@debian.org>
To: debian-user@lists.debian.org
Subject: Re: building .debs with "+b1" on the end
Message-ID: <[🔎] 20140707145522.GA4959@bryant.redmars.org">[🔎] 20140707145522.GA4959@bryant.redmars.org>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Packages in the archive with a "+bN" version suffix, such as "+b1", have been
'binNMUd': essentially rebuilt without any source changes because the
environment has changed (such as a version bump of a library dependency).
In your case it would be worthwhile documenting the fact your package differs
from the archive anyway; so I'd recommend just adding a new changelog stanza
with an NMU version number. If you have devscripts installed, 'dch -n' will
insert the correct stanza for you.
--
Jonathan Dowland
Date: Mon, 7 Jul 2014 16:01:23 +0100
From: Jonathan Dowland <jmtd@debian.org>
To: debian-user@lists.debian.org
Subject: Re: Learning package building - tutorial issue
Message-ID: <[🔎] 20140707150123.GB4959@bryant.redmars.org">[🔎] 20140707150123.GB4959@bryant.redmars.org>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Jul 07, 2014 at 03:12:28PM +1200, Chris Bannister wrote:
> On Sun, Jul 06, 2014 at 09:58:14PM +0200, Linux-Fan wrote:
> > I found a much simpler solution: Your `debian/compat` file is called
> > `debian/compact` (with an additional ``c''). Just rename it to `compat`
> > (without the second ``c'') and the problem fixes itself.
>
> So the makefile was OK after all?
Yes. A long time ago, debian packages would have their file trees constructed
at debian/tmp, prior to being tarred up for inclusion in the binary .deb. This
wasn't great for source packages which built multiple binary packages, so now
the helper tools use debian/<binarypackagename>. The "compat" file determines
what behaviour level debhelper(1) uses (the most prominent debian build helper
tool). Without it being present, debhelper reverts to an old compatibility
version.
These sort of questions are best asked on the Debian Mentors mailing list
debian-mentors@lists.debian.org
Date: Mon, 07 Jul 2014 11:14:35 -0400
From: Harry Putnam <reader@newsguy.com>
To: debian-user@lists.debian.org
Subject: exim4 with spamassassin ... confused
Message-ID: <[🔎] 87y4w58alg.fsf@reader.local.lan>
Content-Type: text/plain
After digging around in several wiki pages and other google hits on
'debian exim4 spamassassin'
I'm thoroughly confused by now.
One of the sources:
https://wiki.debian.org/Exim#Spam_scanning
Under the `Spam scanning' header it tells me exim has a default
configuration for spamassassin (-ed HP included with
exim4-daemon-heavy)
I have the `heavy' version installed and working so far as sending
mail.
So, if exim4 has a default config for SA does that mean I need not
edit anything?.... well apparently not....
The cited page goes on after saying the config is default, to tell me what
edits to make.
>From there it starts getting into what seems to be some really complex
settings.
... is all that necessary... given the config is default?
------- ------- ---=--- ------- -------
Here is another example of the googled material:
http://www.maretmanu.org/homepage/inform/exim-spam.php#spam
Down at the bottom of page is has an example called:
`All in one'
Is that intended to replace my current /etc/exim4/exim4.conf.template?
It does not really say.
------- ------- ---=--- ------- -------
Any pointers to a basic SA/exim4 setup that leaves less to guess at
would be really appreciated.
I am not an exim4 or SA adept and don't have a keen desire to become
so just to get a working setup that at least puts something into
incoming messages showing a spam analysis.
Any known working examples would be greatly useful.
Date: Mon, 7 Jul 2014 11:45:32 -0400
From: Steve Litt <slitt@troubleshooters.com>
To: debian-user@lists.debian.org
Subject: Re: simple database solution without root access
Message-ID: <[🔎] 20140707114532.7d9a9e32@mydesq2.domain.cxm>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Sun, 6 Jul 2014 21:05:10 -0600
Joe Pfeiffer <joseph@pfeifferfamily.net> wrote:
> My typical experience is that when people distinguish "text" vs
> "binary" files, they mean the whole file can reasonably be made sense
> of in a text editor (that's not a precise definition, of course, but I
> think it serves the purpose). When I open an SQLite database I have
> handy with emacs, it is rife with nulls and other non-printing
> characters. Similarly, when I try to run 'less' on it, the response
> is
>=20
> babs:506$ less house.db=20
> "house.db" may be a binary file. See it anyway?=20
>=20
> Arguably, as people typically use the distinction, it's not a text
> file. Yes, I can extract the text fields, as human-readable ASCII,
> but that does not make it a text file.
I've always thought that's *exactly* what makes it a text file. If
every character's ascii value is between 32 and 126, along with
CarriageReturn and Linefeed, it's a text file, regardless of how
readable it is, because it's a whole lot more readable than stuff with
the upper 129 chars and the miscellaneous control characters (Bell,
pagefeed, etc).
Now being a text file doesn't guarantee reasonable readability or
parsability, as anyone who's looked at M$ XML or ODF can attest. But
with a text file, at least you've got a fighting chance to reverse
engineer it.
Now that we have UDF-8, my definition is no longer valid, but if you've
worked a lot with ascii, you kind of "know what I mean".
>=20
> >Okay, thinking about it a bit, the lack of delimiters, and the
> >puzzling nature of binary zero when trying to read it as text, might
> >be what Nuno was referring to. Comma delimited files provide
> >visible, understandable delimiters,=C2=A0
>=20
> And what just about anybody else would mean by a text file, as well.
>=20
> >Oh, and the INTEGER PRIMARY KEY is never readable as TEXT.
I think the requirement is that the primary key is meaningless. Whether
it's an integer or a string is an implementation detail, I believe. And
of course, people violate the requirement all the time: How many use
social security number as the primary key (what could *possibly* go
wrong?).
> >
> >For some people seeking to keep data in text format, that might
> >disqualify SQLite. Apparently not=C2=A0 the OP?
>=20
> My impression (I'd have to go back and recheck) is that it
> disqualified it for the OP, as well.
I don't remember all the OP's requirements, but there's an excellent
"database" with the unfortunate name NoSQL, available at
http://www.strozzi.it/cgi-bin/CSA/tw7/I/en_US/NoSQL/Home%20Page
This database was called NoSQL long before the word "NoSQL" was a
buzzword adjective. Basically, what it does is map storage and
retrieval commands to sets of Unix directories and commands like cut,
sort, grep, awk and the like. NoSQL "tables" are trivial to read with
the naked eye, but it gives you Unix-command based readers to put
headers and column spacers and the like. It's pretty cool, and it's
surprisingly fast. So SQL isn't a requirement, this can be an excellent
choice.
SteveT
Steve Litt * http://www.troubleshooters.com/
Troubleshooting Training * Human Performance
Date: Mon, 07 Jul 2014 18:29:48 +0200
From: berenger.morel@neutralite.org
To: <debian-user@lists.debian.org>
Subject: Re: Deluge disappears
Message-ID: <[🔎] 95886ab417ad055f3353280b87241c64@neutralite.org">[🔎] 95886ab417ad055f3353280b87241c64@neutralite.org>
Content-Type: text/plain; charset=UTF-8;
format=flowed
Content-Transfer-Encoding: quoted-printable
Le 02.07.2014 14:57, criego duncan a =C3=A9crit=C2=A0:
> I'm running debian testing and keep it pretty up-to-date. I did
> 'aptitude update' then 'aptitude dist-upgrade' both yesterday and the
> day before. Last night i noticed that deluge was completely gone=20
> from
> my system. I never intentially uninstalled it. So i looked through=20
> the
> dpkg & aptitude logs in /var/log and the string "deluge" does not=20
> appear
> in any of these files.
>
> The one unusual thing is that the day before yesterday i deleted
> everything that had to do with enlightenment (e17), which i had been
> using and installed openbox & lxpanel.
>
> This seems totally bizarre to me. All the deluge packages i had
> installed (i was running the classic interface) were gone. I
> reinstalled and so now they're back, but my configuration is not=20
> being
> picked up because it no longer recognizes any torrents as being=20
> present.
>
> How could several packages disappear from my system (a) without my
> explicitly doing it (deluge & deluge-gtk would not be automatically
> removed due to dependencies because they're not dependent on=20
> anything)
> and (b) with no trace of this happening in /var/log/aptitude* &
> /var/log/dpkg* ???
There was a thread recently about removal of packages when using=20
aptitude's update commands. Did you verify when you did that update the=20
list of packages which were planned to be added, removed and updated?=20
Aptitude may have warned you about this, since deluge may have been=20
installed as a dependency of another package (a DE meta-package for=""> example).
Date: Mon, 7 Jul 2014 17:53:24 +0100
From: Brian <ad44@cityscape.co.uk>
To: debian-user@lists.debian.org
Subject: Re: I'm not a huge fan of systemd
Message-ID: <[🔎] 20140707165324.GH27249@copernicus.demon.co.uk">[🔎] 20140707165324.GH27249@copernicus.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sun 06 Jul 2014 at 19:01:38 +0100, Brian wrote:
> You had the time on similar dubious grounds to doubt the veracity of the
> information you were given.
It is possible the last mail did not fully or clearly address your major
concern.
With systemd-journald running or not running ('systemctl mask
systemd-journald') 'ps ax' shows /usr/sbin/rsyslogd listening. Messages
are logged to the usual places in /var/log. You can be confident that
the information you already had about binary logs with journald was not
false.
Date: Mon, 7 Jul 2014 19:09:50 +0200
From: Slavko <linux@slavino.sk>
To: debian-user@lists.debian.org
Subject: Re: simple database solution without root access
Message-ID: <[🔎] 20140707190950.52680f38@bonifac.skk>
Content-Type: multipart/signed; micalg=pgp-sha1;
boundary="Sig_/bK6gnVBCQ5OYacXD1MGbpJb"; protocol="application/pgp-signature"
--Sig_/bK6gnVBCQ5OYacXD1MGbpJb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Ahoj,
D=C5=88a Mon, 7 Jul 2014 11:45:32 -0400 Steve Litt
<slitt@troubleshooters.com> nap=C3=ADsal:
> On Sun, 6 Jul 2014 21:05:10 -0600
> Joe Pfeiffer <joseph@pfeifferfamily.net> wrote:
>=20
> I've always thought that's *exactly* what makes it a text file. If
> every character's ascii value is between 32 and 126, along with
> CarriageReturn and Linefeed, it's a text file, regardless of how
> readable it is, because it's a whole lot more readable than stuff with
> the upper 129 chars and the miscellaneous control characters (Bell,
> pagefeed, etc).
>=20
> Now being a text file doesn't guarantee reasonable readability or
> parsability, as anyone who's looked at M$ XML or ODF can attest. But
> with a text file, at least you've got a fighting chance to reverse
> engineer it.
Your text file is not able to contain text in languages, which have
more than 26 letters, then it is not a text file. My language, for
example, has 43 letters... Pure ASCII is very old definition, which was
enhanced by ISO-8859-X (more than 15 years ago) to respect other
languages, and these are deprecated now by the UTF-X (Unicode).
Despite that in this ML we are writing in English, it is a
international ML, then please, do not think in English only, but
think internationally, when you are trying to generalize.
BTW, one from my first big computer things, was learn my old 8 bit
computer to write in the (something as equivalent of current) Latin2
and Cyrillic, cca 25 years ago.
regards
--=20
Slavko
http://slavino.sk
--Sig_/bK6gnVBCQ5OYacXD1MGbpJb
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJTutReAAoJEIP5qrg5GI22sxoH/1Qjwlf+RdxjwU+ZWos5zErC
Vbs6CzuYrq6Ld2db8h8n4GJxZZUx1kWUiPBTXjI/2HZ24YokpGf8zS1SFRL/r2a+
KQZ9zVzb9gFsrM4qEMZO/nXl1WVe9CrlxFQTZcqmlHd5Bprxm9hnbVTJLTJdMKXj
ieV59Lppga/6iObqYXKf4zvmrc7db4UiNHIuxLMzpT5/YV51PErlDMp48dM3jN9C
O3FhzDKx03E+bUaCGFYOSeJ+3N1a3anh6n7HxEv/TuXRuYE5/F0nfV/gHGLwfdb+
AkO2OLSHGwVwK9gPJLe6oDeSVZp/mMcFwFaZUzYVJTzka8bKoEOpZFTA4QhGpvk=
=PiXF
-----END PGP SIGNATURE-----
--Sig_/bK6gnVBCQ5OYacXD1MGbpJb--
Date: Mon, 07 Jul 2014 07:44:53 -0700
From: peter@easthope.ca
To: debian-user@lists.debian.org
Cc: peter@easthope.ca
Subject: Re: IEEE 802.11-USB adapters with RTL8187L
Message-Id: <[🔎] E1X4AA1-0002Yy-I8@dalton.invalid>
From: "Andrew M.A. Cater" <amacater@galactic.demon.co.uk>
Date: Thu, 12 Jun 2014 17:06:51 +0000
> It doesn't _have_ to be metallic - a small dish shaped "thing" in any material
> that isn't actually RF lossy may show some focussing effect. It also doesn't have
> to be solid - for some RF frequencies, chicken wire with big air holes in it will
> also work correctly. Two biscuit tin lids will make a "good enough" corner reflector.
Thanks.
From: Bzzzz <lazyvirus@gmx.com>
Date: Thu, 12 Jun 2014 19:28:37 +0200
> ... check your local regulations for EIRP max power, as 1.5W is way beyond
> most of countries legislations (ie: UE has an EIRP of 100mW).
The relevant limit in Canada and the USA appears to be 1 W.
http://www.bcwireless.net/moin.cgi/Regulatory#Using_the_Unlicensed_2.4GHz_radio_spectrum
http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf01320.html
http://www.afar.net/tutorials/fcc-rules/
(For both Debian and Windows!)
A laptop marketed in Canada or the USA might be illegal for
use in Europe, even if Debian is replaced with LiMux?
http://en.wikipedia.org/wiki/LiMux
Power density should be more pertinent to interference than
total radiated power. Location should also be pertinent.
In an urban location, the neighbour can be a few m away whereas
in a rural location the neighbour can be half a km away.
But reference to density and location might introduce unaccepable
complexity.
Thanks for the replies, ... Peter E.
--
123456789 123456789 123456789 123456789 123456789 123456789 123456789 12
Tel +1 360 639 0202 http://carnot.yi.org/ Bcc: peter at easthope. ca
Date: Mon, 7 Jul 2014 19:10:26 +0100
From: Brian <ad44@cityscape.co.uk>
To: debian-user@lists.debian.org
Subject: Re: I'm not a huge fan of systemd
Message-ID: <[🔎] 20140707181026.GI27249@copernicus.demon.co.uk">[🔎] 20140707181026.GI27249@copernicus.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon 07 Jul 2014 at 17:53:24 +0100, Brian wrote:
> With systemd-journald running or not running ('systemctl mask
> systemd-journald') 'ps ax' shows /usr/sbin/rsyslogd listening. Messages
> are logged to the usual places in /var/log. You can be confident that
> the information you already had about binary logs with journald was not
> false.
And if this reassurance is not convincing there is
https://lists.debian.org/debian-devel/2014/02/msg00772.html
With my rsyslog (and systemd maintainer) hat on, let me add a few
remarks here:
We still do install rsyslog by default and will continue to do so for
the forseeable future (for reasons like the one you mentioned).
So your text-based logs won't be gone with the switch to systemd.
Let me repeat that: Jessie will have text-based logs, nothing in that
regard changes.
Actually it does: systemd can feed additional information into syslog
(e.g. from daemons stdout/stderr), so you'll get a syslog with more
complete information when running under systemd.
As for journald, we currently don't enable persistent logging in
journald (persistent logging can be done by creating a folder
/var/log/journal with the appropriate permissions).