Re: wireless mouse dies

[George N. White III]

On 7 October 2017 at 16:59, fred roller  wrote:

> You mentioned having this mouse for awhile.  Used to have similar issues
> and something to try (low tech) is to clean the connections.  An eraser or
> equivalent will do if you can get to the connectors on the dongle.
> Sometimes the connections get a micro build up on them and a mild
> non-residual abrasive does the trick.  Just a wag.  Worked with radio
> connections (which is where I was inspired) and worked on usb ports/dongles
> as well when I was support.
>

Don't ignore battery terminals, and  don't use abrasives (which many
erasers contain), as they will damage metal plating.  At one time, carbon
tetrachloride was used for cleaning contacts.   These days there are much
safer designer contact cleaners
,
After cleaning, Stabilant 22 contact enhancer
 has worked
well for me over many years.

>
> tacts-- Fred
>
> On Sat, Oct 7, 2017 at 1:03 PM, antonio montagnani <
> antonio.montagn...@alice.it> wrote:
>
>> Joe Zeff ha scritto il 07/10/2017 alle 00:05:
>>
>>> On 10/06/2017 02:54 PM, Rick Stevens wrote:
>>>
 Yeah. As a hardware engineer that has, over many years, transitioned to
 a software engineer, I always assume my software is buggy. I can't
 believe how often it turns out it's hardware like a bad cable or
 something. My rule of thumb is "If it always happens, it's probably
 software. If it's intermittent, then it's likely hardware. Or not."

>>>
>>> Pournelle's first rule of debugging is, "The first thing you check is
>>> the cables."
>>>
>>
I think it may have Pournelle who first mentioned Stabilant 22.



> ___
>>> users mailing list -- users@lists.fedoraproject.org
>>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>>
>>
>> really it is hard to check cables on a wireless mouse, isn't it?? :-)
>>
>> --
>> Antonio M
>> Skype: amontag52
>>
>> Linux Fedora F26 (Workstation Edition)
>> on Fujitsu Lifebook A512
>>
>> http://lugsaronno.altervista.org
>> http://campingmonterosa.altervista.org
>>
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
>
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
>


-- 
George N. White III 
Head of St. Margarets Bay, Nova Scotia
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: wireless mouse dies

[fred roller]

You mentioned having this mouse for awhile.  Used to have similar issues
and something to try (low tech) is to clean the connections.  An eraser or
equivalent will do if you can get to the connectors on the dongle.
Sometimes the connections get a micro build up on them and a mild
non-residual abrasive does the trick.  Just a wag.  Worked with radio
connections (which is where I was inspired) and worked on usb ports/dongles
as well when I was support.

-- Fred

On Sat, Oct 7, 2017 at 1:03 PM, antonio montagnani <
antonio.montagn...@alice.it> wrote:

> Joe Zeff ha scritto il 07/10/2017 alle 00:05:
>
>> On 10/06/2017 02:54 PM, Rick Stevens wrote:
>>
>>> Yeah. As a hardware engineer that has, over many years, transitioned to
>>> a software engineer, I always assume my software is buggy. I can't
>>> believe how often it turns out it's hardware like a bad cable or
>>> something. My rule of thumb is "If it always happens, it's probably
>>> software. If it's intermittent, then it's likely hardware. Or not."
>>>
>>
>> Pournelle's first rule of debugging is, "The first thing you check is the
>> cables."
>> ___
>> users mailing list -- users@lists.fedoraproject.org
>> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>>
>
> really it is hard to check cables on a wireless mouse, isn't it?? :-)
>
> --
> Antonio M
> Skype: amontag52
>
> Linux Fedora F26 (Workstation Edition)
> on Fujitsu Lifebook A512
>
> http://lugsaronno.altervista.org
> http://campingmonterosa.altervista.org
>
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: wireless mouse dies

[antonio montagnani]

Joe Zeff ha scritto il 07/10/2017 alle 00:05:

On 10/06/2017 02:54 PM, Rick Stevens wrote:

Yeah. As a hardware engineer that has, over many years, transitioned to
a software engineer, I always assume my software is buggy. I can't
believe how often it turns out it's hardware like a bad cable or
something. My rule of thumb is "If it always happens, it's probably
software. If it's intermittent, then it's likely hardware. Or not."


Pournelle's first rule of debugging is, "The first thing you check is 
the cables."

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


really it is hard to check cables on a wireless mouse, isn't it?? :-)

--
Antonio M
Skype: amontag52

Linux Fedora F26 (Workstation Edition)
on Fujitsu Lifebook A512

http://lugsaronno.altervista.org
http://campingmonterosa.altervista.org
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Problem: Cross compile to arm (Raspberry pi) using autotools

[Fred Smith]

On Sat, Oct 07, 2017 at 03:03:32PM +0200, Dirk Gottschalk wrote:
> Hello Ralf.
> 
> Am Samstag, den 07.10.2017, 14:43 +0200 schrieb Ralf Corsepius:
> > On 10/07/2017 01:49 PM, Dirk Gottschalk wrote:
> > Try
> > touch tmp.c
> > arm-linux-gnu-gcc -v tmp.c
> > and check the search paths being reported.
> 
> Thank you, this did the trick. The shown Path are wrong, or the rpm
> installed the files in the wrong paths, depends on how you look at it.
> 
> Now i habe to figure out if i can correct the path in config, or i do a
> somple symlink on the fs. I hope this foxes the issue.
> 
> 
> > > So, my question is: Did i miss something?
> 
> > Likely ;) Is your target running arm-linux-gnu or something else
> > (e.g. 
> > bare metal, a different OS, ...)?
> 
> My target is Linux, the Pi 3 is running Raspbian.
> 
> 
> > Normally, you need a toolchain specialized/dedicated to your target
> > and 
> > can't use an arbitrary toolchain.
> 
> Using autotools for this works for others, so the problem should be my
> configuration.
> 
> > >  How do I use the cross compiler with
> > > autotools?
> 
> > In an ideal world, exactly like you did. However, it's pretty likely
> > you 
> > are tripping over bugs in your configure.ac.
> 
> I have a very simple configure.ac, no special options, but this
> deserves a deeper look.
> 
> 
> > Also make sure NOT to have set CC, CFLAGS etc in your environment.
> 
> These variables are unset in my Environment because I use autotools for
> all my Project. These variables are set temporarily by them.
> 
> Thanks for you advice.

While I understand that your preference is to build on a linux
box other than the RPI, if you get sufficiently despearte, you
could install dev tools on the RPI and build there.

Compiling stuff on my RPI3 is reasonably fast (I haven't tried something
large like a kernel).

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
   But God demonstrates his own love for us in this: 
 While we were still sinners, 
  Christ died for us.
--- Romans 5:8 (niv) --
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: how to enable/start "git@.service" via systemd?

[Anthony Joseph Messina]

On Saturday, October 7, 2017 4:18:48 AM CDT Robert P. J. Day wrote:
>   (probably OT: more a systemd question than a fedora question, but
> i'm sure the experts will clear this up in short order.)
> 
>   wanted to experiment with the git daemon so, on my fully-updated F26
> system, installed git-daemon package, whose contents are simply:
> 
> $ rpm -ql git-daemon
> /usr/lib/systemd/system/git.socket
> /usr/lib/systemd/system/git@.service
> /usr/libexec/git-core/git-daemon
> /usr/share/doc/git/git-daemon.html
> /usr/share/doc/git/git-daemon.txt
> /usr/share/man/man1/git-daemon.1.gz
> /var/lib/git
> $
> 
>   i enabled the socket component easily enough with:
> 
> $ sudo systemctl enable git.socket
> [sudo] password for rpjday:
> Created symlink /etc/systemd/system/sockets.target.wants/git.socket →
> /usr/lib/systemd/system/git.socket.
> $
> 
> and started it as well, but i'm not sure how to start the git daemon
> itself since, as i understand it, the presence of the "@" in the
> service name typically means there can be multiple instances of them
> running (eg., getty@.service), but i have no interest in multiple
> invocations (and am not even sure why that would be a good thing).
> 
>   cut to the chase -- what's the proper way to start the git daemon on
> F26? put another way, what am i hopelessly misunderstanding here?
> 
> rday

The git-daemon service should be started "on-demand" when something connects 
to the socket.  -A

-- 
Anthony - https://messinet.com/ - https://messinet.com/~amessina/gallery
F9B6 560E 68EA 037D 8C3D  D1C9 FF31 3BDB D9D8 99B6


signature.asc
Description: This is a digitally signed message part.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Problem: Cross compile to arm (Raspberry pi) using autotools

[Dirk Gottschalk]

Hello Ralf.

Am Samstag, den 07.10.2017, 14:43 +0200 schrieb Ralf Corsepius:
> On 10/07/2017 01:49 PM, Dirk Gottschalk wrote:
> Try
> touch tmp.c
> arm-linux-gnu-gcc -v tmp.c
> and check the search paths being reported.

Thank you, this did the trick. The shown Path are wrong, or the rpm
installed the files in the wrong paths, depends on how you look at it.

Now i habe to figure out if i can correct the path in config, or i do a
somple symlink on the fs. I hope this foxes the issue.


> > So, my question is: Did i miss something?

> Likely ;) Is your target running arm-linux-gnu or something else
> (e.g. 
> bare metal, a different OS, ...)?

My target is Linux, the Pi 3 is running Raspbian.


> Normally, you need a toolchain specialized/dedicated to your target
> and 
> can't use an arbitrary toolchain.

Using autotools for this works for others, so the problem should be my
configuration.

> >  How do I use the cross compiler with
> > autotools?

> In an ideal world, exactly like you did. However, it's pretty likely
> you 
> are tripping over bugs in your configure.ac.

I have a very simple configure.ac, no special options, but this
deserves a deeper look.


> Also make sure NOT to have set CC, CFLAGS etc in your environment.

These variables are unset in my Environment because I use autotools for
all my Project. These variables are set temporarily by them.

Thanks for you advice.

Regards,
Dirk

-- 
Dirk Gottschalk
Paulusstrasse 6-8
52064 Aachen
Tel.: +49 1573 1152350

signature.asc
Description: This is a digitally signed message part
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Problem: Cross compile to arm (Raspberry pi) using autotools

[Ralf Corsepius]

On 10/07/2017 01:49 PM, Dirk Gottschalk wrote:

Hello,

I have a problem cross compiling using autotools for my Raspberry Pi 3.

I wrote a server program which runs good with Linux and under windows
(compiled with MinGW) on my X86_64 machine.

Since there is no configure wrapper for ARM like MinGW has, i use the
following configure call:

./configure --host=arm-linux-gnu

The Script is failing and the log tells me about bad options
"-qverseion" and "-V" in GCC tests. So I removed this Options from the
Script by hand.

Now it tells me about a missing file called "crt1.o". But i found this
file in "/usr/arm-linux-gnu/lib/crt1.o".
Well, in general, this indicates a broken path, either in the toolchain 
or in your compiler call.


Try
touch tmp.c
arm-linux-gnu-gcc -v tmp.c
and check the search paths being reported.


So, my question is: Did i miss something?


Likely ;) Is your target running arm-linux-gnu or something else (e.g. 
bare metal, a different OS, ...)?


Normally, you need a toolchain specialized/dedicated to your target and 
can't use an arbitrary toolchain.



 How do I use the cross compiler with
autotools?


In an ideal world, exactly like you did. However, it's pretty likely you 
are tripping over bugs in your configure.ac.


Also make sure NOT to have set CC, CFLAGS etc in your environment.

Ralf
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Problem: Cross compile to arm (Raspberry pi) using autotools

[Dirk Gottschalk]

Hello,

I have a problem cross compiling using autotools for my Raspberry Pi 3.

I wrote a server program which runs good with Linux and under windows
(compiled with MinGW) on my X86_64 machine.

Since there is no configure wrapper for ARM like MinGW has, i use the
following configure call:

./configure --host=arm-linux-gnu

The Script is failing and the log tells me about bad options 
"-qverseion" and "-V" in GCC tests. So I removed this Options from the
Script by hand.

Now it tells me about a missing file called "crt1.o". But i found this
file in "/usr/arm-linux-gnu/lib/crt1.o".

So, my question is: Did i miss something? A additional configure
parameter or anything like this? How do I use the cross compiler with
autotools?

It would be nice to habe a wrapper script line mingwXX-configure, but
it would be good to know, what to do.

Thanks,
Dirk

-- 
Dirk Gottschalk
Paulusstrasse 6-8
52064 Aachen
Tel.: +49 1573 1152350

signature.asc
Description: This is a digitally signed message part
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

how to enable/start "git@.service" via systemd?

[Robert P. J. Day]

  (probably OT: more a systemd question than a fedora question, but
i'm sure the experts will clear this up in short order.)

  wanted to experiment with the git daemon so, on my fully-updated F26
system, installed git-daemon package, whose contents are simply:

$ rpm -ql git-daemon
/usr/lib/systemd/system/git.socket
/usr/lib/systemd/system/git@.service
/usr/libexec/git-core/git-daemon
/usr/share/doc/git/git-daemon.html
/usr/share/doc/git/git-daemon.txt
/usr/share/man/man1/git-daemon.1.gz
/var/lib/git
$

  i enabled the socket component easily enough with:

$ sudo systemctl enable git.socket
[sudo] password for rpjday:
Created symlink /etc/systemd/system/sockets.target.wants/git.socket →
/usr/lib/systemd/system/git.socket.
$

and started it as well, but i'm not sure how to start the git daemon
itself since, as i understand it, the presence of the "@" in the
service name typically means there can be multiple instances of them
running (eg., getty@.service), but i have no interest in multiple
invocations (and am not even sure why that would be a good thing).

  cut to the chase -- what's the proper way to start the git daemon on
F26? put another way, what am i hopelessly misunderstanding here?

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org