Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Doug]

On 05/30/2016 05:08 PM, Lisi Reisz wrote:

On Monday 30 May 2016 22:49:52 Lisi Reisz wrote:

(Parlez-vois français, je parle le
français?)

My spell checker can't cope with French, and I'm a lousy typist.. :-(
parlez-vo*U*s français etc.

Lisi


Many word processors have French dictionaries. You have to set the 
language that you're going to write in, and then the spell checker 
should work.
If you don't use an international keyboard, however, you may have some 
fun with all the diacritical marks in the French language. The Compose
key will solve that problem, but it's just a bit clumsy for continuous 
writing in a foreign language. Just about all characters with diacritic 
marks are
obtainable by striking and letting go of the compose key* and then 
typing two characters. For instance, compose ' a  gives you á and
compose , c gives you ç. The character can be upper case, as in compose 
È. Works for other European languages also: Löffel, Straße. Also, currency

and degree symbols, etc.
*Compose key can be set in Linux as one of the non character keys, like 
right-alt, or if you have a Windows keyboard, the right Win key. Check

the keyboard setup in your Linux distro.

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Monday 30 May 2016 22:49:52 Lisi Reisz wrote:
> (Parlez-vois français, je parle le  
> français?)

My spell checker can't cope with French, and I'm a lousy typist.. :-(  
parlez-vo*U*s français etc.

Lisi

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Monday 30 May 2016 22:49:52 Lisi Reisz wrote:
> "When I type "english" the spell-checker
> tries to correct to to "English", why?" I'd have known immediately what you
> meant.

correction:
"When I type "english" the spell-checker 
tries to correct IT to "English", why?" I'd have known immediately what you 
meant.

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Monday 30 May 2016 20:35:40 Rodary Jacques wrote:
> Thank you, I didn't know. In French (I was careful
> here) languages' names and peoples' nationalities
> don't take a capital letter. But towns' and countries'
> names do of course.
>   Jacques
> P.S.:I still don't see where was the joke in my post,
> but never mind.

I couldn't make head or tail of what you were saying about *English* so 
decided that it was meant to be a joke.  You *were* trying to make a joke of 
it, of course.  If you had just said "When I type "english" the spell-checker 
tries to correct to to "English", why?" I'd have known immediately what you 
meant.

So:  I would have got that wrong in French (note the capital) too.  I thought 
that: Je suis Anglaise et je parle anglais, vous êtes Français et vous parlez 
français.  But you say that it is: Je suis anglaise et je parle anglais, vous 
êtes français et vous parlez français?  (Parlez-vois français, je parle le  
français?)

Lisi

Re: Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Rodary Jacques]

Thank you, I didn't know. In French (I was careful 
here) languages' names and peoples' nationalities 
don't take a capital letter. But towns' and countries' 
names do of course.
Jacques
P.S.:I still don't see where was the joke in my post, 
but never mind.

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Saturday 28 May 2016 10:11:39 Lisi Reisz wrote:
> Thank you in
>
> > advance, and again, sorry for my poor english (kspell still tells me to
> > write *English* instead and nobody told me why, and this proves nobody
> > looks at the first post in a thread :-D)

I think I have just worked out what this means.  The spell checker is 
objecting to the spelling of "english".  "English" begins with a capital 
letter .  It is incorrect to spell the language with a lower case initial 
letter.  So the spell checker was correct in objecting.

I *think* that this is what you are getting at here.  You would not 
spell "Paris" "paris", surely?

Lisi

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Saturday 28 May 2016 01:28:03 Rodary Jacques wrote:
> Thanks for your comments I also use apt* commands, when necessary, but
> the point is that people don't seem to read thoroughly the threads they are
> answering to: I don't mind using wicd, I even tried it. But it also uses
> /etc/network/interfaces, and my questioning is about initramfs, ifaces
> drivers, /proc/net/dev, and $networking in insserv (not $network). And I
> would be very grateful to anyone who could answer to those questions
> (named-bind9, wifi access-point) not to the first answers. Thank you in
> advance, and again, sorry for my poor english (kspell still tells me to
> write *English* instead and nobody told me why, and this proves nobody
> looks at the first post in a thread :-D)
>   Cheers
>   Jacques


Ask your questions clearly and separately and you might get answers.  And you 
could try answering the questions people have asked you.

In addition, people can be answering each other, not just you.  You don't own 
the thread, you just started it, and you and others have broken it regularly 
so that it is actually impossible to look at the first post.  I tried 
yesterday.  I even had a look at Google's "conversations" to try and trace 
this thread back.  I failed.

So: state your questions clearly and separately (typed separately, with nice 
clear spaces between, and stated separately) - and please, no jokes.  They 
don't survive the translation.

Lisi

Re: Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Rodary Jacques]

Thanks for your comments I also use apt* commands, when necessary, but 
the point is that people don't seem to read thoroughly the threads they are 
answering to: I don't mind using wicd, I even tried it. But it also uses 
/etc/network/interfaces, and my questioning is about initramfs, ifaces 
drivers, /proc/net/dev, and $networking in insserv (not $network). And I 
would be very grateful to anyone who could answer to those questions 
(named-bind9, wifi access-point) not to the first answers. Thank you in 
advance, and again, sorry for my poor english (kspell still tells me to write 
*English* instead and nobody told me why, and this proves nobody looks at 
the first post in a thread :-D)
Cheers
Jacques 

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Michael Lange]

Hi,

On Fri, 27 May 2016 08:32:59 +0100
Lisi Reisz  wrote:

(...)
> So, correction, "said unstable by Synaptic"  (Does it???)
> 
> Here is what I get with aptitude in Jessie:
> 
(...)
> I don't see any mention of unstable.

I see the same in synaptic here, nothing about "unstable".

Regards

Michael



.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Where there's no emotion, there's no motive for violence.
-- Spock, "Dagger of the Mind", stardate 2715.1

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Lisi Reisz]

On Friday 27 May 2016 01:21:25 Rodary Jacques wrote:
> > Could we have a reference please for "said unstable by debian's package
> > installer"? (I assume you're talking about the wicd packages, because
> > someone wrote "Please note, an entry does not work with network-manager.
> > Use wicd instead" in the thread called "WiFi Access Point".)
>
> I find your post only today may 26. I read the warnings of synaptic about
> wicd.

Synaptic!=debian's package installer

It is one of Debian's package installers, and a late-comer at that, which I 
have found causes problems.  Perhaps this is one of them?  (Note the "I have 
found".  I don't want to start a flame war!!!)

So, correction, "said unstable by Synaptic"  (Does it???)

Here is what I get with aptitude in Jessie:

peter@Nyx-II:~$ aptitude show wicd
Package: wicd
State: not installed
Version: 1.7.2.4-4.1
Priority: optional
Section: net
Maintainer: David Paleino 
Architecture: all
Uncompressed Size: 16.4 k
Depends: wicd-daemon (= 1.7.2.4-4.1), wicd-gtk (= 1.7.2.4-4.1) | wicd-curses 
(=
 1.7.2.4-4.1) | wicd-cli (= 1.7.2.4-4.1) | wicd-client
Description: wired and wireless network manager - metapackage
 Wicd is a general-purpose network configuration server which aims to provide 
a simple
 but flexible interface for connecting to networks. Its features include:
 * wide variety of settings;
 * ability to connect to (and maintain profiles for) both wired and wireless 
networks;
 * support for many encryption schemes, including WEP, WPA, WPA2 and custom 
schemes;
 * wireless-tools compatibility;
 * tray icon showing network activity and signal strength;
 * lack of GNOME dependencies (although it does require GTK+), making it easy 
to use in
   Xfce, Fluxbox, Openbox, Enlightenment, etc.

 This is a metapackage, it allows installation of all the components of Wicd, 
including
 one of the clients, which must be manually chosen.
Homepage: http://wicd.sourceforge.net/

Tags: admin::configuring, admin::monitoring, implemented-in::python,
  network::configuration, role::metapackage, role::program, 
scope::utility,
  use::checking, use::configuring, use::monitor

peter@Nyx-II:~$
--

I don't see any mention of unstable.

And Brian, that description will tell you why some of us like it.  But I have 
nothing against wpagui, and am not "fixated" on wicd.  I just use it and have 
found it reliable.  Does wpagui also administer wired netrworks, as does 
wicd?

Lisi

Re: [deb...@lionunicorn.co.uk: Re: Network manager (again) Re:]

[Rodary Jacques]

Le vendredi 20 mai 2016 16:09:25, vous avez écrit :
> Hi, I thought you might only be subscribed to the French list
> and not this one, so you might have missed this.

> 
> Could we have a reference please for "said unstable by debian's package
> installer"? (I assume you're talking about the wicd packages, because
> someone wrote "Please note, an entry does not work with network-manager.
> Use wicd instead" in the thread called "WiFi Access Point".)

I find your post only today may 26. I read the warnings of synaptic about wicd. 
And now that I 
have learned things about systemd, insserv and them requiring to start 
networking (not network) 
as soon as the driver's modules are loaded, long before reading 
/etc/network/interfaces (BTW 
mine includes only lo)  I won't change anything more: It works! I start named  
in /etc/rc.local, not 
bind9 which definitely won't work, and  my wifi access point in gnome-nettool. 
And I don't halt 
my server. Not intellectually satisfying, but practical! 
Jacques
PS: my wifi problem came from firmware-iwlwifi being loaded much too late (7s 
after boot-start, 
when r8169 and e1000e for my NICs are loaded before 0.8s) probably because the 
version in 
early Jessie was broken, and replaced after installation (see 
https://wiki.debian.org/iwlwifi).