On Saturday 02 Jan 2016 2:32:36 PM Ed Greshko wrote:
> Well, since your cronjob is a program which performs an email function and
> since those errors being reported are referencing files in your directory I
> would say the most likely cause is the interaction between your cronjob and
> an MTA and
I'm getting an ancient horror message from my old HP w2207h flat
panel monitor. I have a KVM switch between it and three different PCs, of
which the newest (#1) is running F23, the oldest (#3) F22, and the middle
F22 or F23 (I disremember which).
About the time any of them fini
On 01/02/2016 09:58 AM, Beartooth wrote:
I'm getting an ancient horror message from my old HP w2207h flat
panel monitor. I have a KVM switch between it and three different PCs, of
which the newest (#1) is running F23, the oldest (#3) F22, and the middle
F22 or F23 (I disremember which).
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon
$ ps -ef | grep adb
jd 19967
On 01/02/2016 01:12 PM, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to d
On Sat, 2 Jan 2016 16:58:35 + (UTC)
Beartooth wrote:
>
> I'm getting an ancient horror message from my old HP w2207h
> flat panel monitor. I have a KVM switch between it and three
> different PCs, of which the newest (#1) is running F23, the oldest
> (#3) F22, and the middle F22 or F23
On 01/02/2016 01:20 PM, stan wrote:
On Sat, 2 Jan 2016 16:58:35 + (UTC)
Beartooth wrote:
I'm getting an ancient horror message from my old HP w2207h
flat panel monitor. I have a KVM switch between it and three
different PCs, of which the newest (#1) is running F23, the oldest
(#3
On 01/02/16 10:58, Beartooth wrote:
>
> I'm getting an ancient horror message from my old HP w2207h flat
> panel monitor. I have a KVM switch between it and three different PCs, of
> which the newest (#1) is running F23, the oldest (#3) F22, and the middle
> F22 or F23 (I disremember whi
On 02Jan2016 22:11, Sudhir Khanger wrote:
On Saturday 02 Jan 2016 2:32:36 PM Ed Greshko wrote:
Well, since your cronjob is a program which performs an email function and
since those errors being reported are referencing files in your directory I
would say the most likely cause is the interactio
On Fri, Jan 1, 2016 at 8:57 PM, Javier Perez wrote:
>
>
> Really?? All I had to do is select the partition and mark it for
> reformatting, and selected the desktop package and it works.
>
> That's the point. If I want to reuse the partition I HAVE to reformat it.
Yes, that's intended. There's goo
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
>
> On 12/30/2015 12:13 PM, Jon LaBadie wrote:
> >On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
> >>Android is 4.4.2 (nothing newer is available for my phone.
> >>Developer option set. usb debugging enabled.
> >>
> >>yet, when I
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
>
> On 01/02/2016 01:12 PM, jd1008 wrote:
> >On 12/30/2015 12:13 PM, Jon LaBadie wrote:
> >>On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
> >>>
> >>>Android is 4.4.2 (nothing newer is available for my phone.
> >>>Developer optio
If you haven't tried using 'strace mkfs." it's very educational.
All it does is write some stuff to the disk. It's mostly zeros, but
also the signature, UUID, stuff that makes up the superblocks. The
fact this fails, suggest the device can't even handle basic writes. So
there's no reason to believe
On 01/02/2016 03:58 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debu
On 01/02/2016 04:03 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
On 01/02/2016 01:12 PM, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
Android is 4.4.2 (nothing newer is available for m
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cable.
Other than that, I've got nothing.
Good lu
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cab
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a different computer, or
borrow a cable to see what
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cab
On 01/02/2016 07:01 PM, Joe Zeff wrote:
On 01/02/2016 05:56 PM, jd1008 wrote:
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a differen
On 01/02/2016 06:11 PM, jd1008 wrote:
>
>
> On 01/02/2016 07:01 PM, Joe Zeff wrote:
>> On 01/02/2016 05:56 PM, jd1008 wrote:
>>> Well, these are the same cables I used on my previous phones
>>> and they worked extremely well.
>>> My phone is less than 2 years old, and looks like brand new.
>
21 matches
Mail list logo
