On 12/12/2018 14:04, Long Wind wrote:
sorry! this question isn't linux specific
there are two usb sockets on front panel of pc casethey appear same, but really
are notwireless mouse can only be connected to one of them
could you tell me their difference? Thanks!
Bad connection on one port? USB
On Wed, 12 Dec 2018 at 12:04, Long Wind wrote:
>
> there are two usb sockets on front panel of pc case
> they appear same, but really are not
1) try running (as root)
lsusb
lsusb -t
lsusb -v
2) you can identify the sockets on the front by comparing those
commands when the sockets are empty, and w
Long Wind wrote:
> sorry! this question isn't linux specific
> there are two usb sockets on front panel of pc casethey appear same,
> but really are notwireless mouse can only be connected to one of them.
> could you tell me their difference? Thanks!
They're easier to reach than those on the back.
On 11.12.18 09:44, Dan Ritter wrote:
> mick crane wrote:
> > On 2018-12-10 20:02, Thomas Schmitt wrote:
> > > For the purpose of sr_drive_status(), the loop is really inappropriate.
> > > This function shall obtain the drive status and not wait until the
> > > status of the medium is decided.
> >
Marek Mosiewicz wrote:
> |Just asked if it is technically possible. Application do not call
> kernel directly and they are using glibc library for example. I'm just
> curios how many libraries are there for abstracting kernel and if it is
> possible in future release to have common libraries which
md wrote:
> Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to
> the SATA based computer I've been using. With this drive (/dev/sr1), dd
> seems to working fine without having to precede it with dvdbackup -M.
Thomas Schmitt wrote:
> But aren't those copied sectors still sc
md wrote:
> Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to
> the SATA based computer I've been using. With this drive (/dev/sr1), dd
> seems to working fine without having to precede it with dvdbackup -M.
Thomas Schmitt wrote:
> But aren't those copied sectors still sc
On Tue, 11 Dec 2018 16:51:22 + (UTC)
Curt wrote:
>
> Did I say that?
>
> What you quoted up there of mine (where I said there instead of their
> up there) was an attempt at jocularity. I know you're the moral
> arbiter around these parts, repeating yourself and pointing things
> out and a
On Tue, 11 Dec 2018 16:51:22 + (UTC)
Curt wrote:
> On 2018-12-11, Joe wrote:
> >
> >> On 2018-12-10, Cindy-Sue Causey wrote:
> >> >
> >> > Beyond that, I *thought* I remembered a few times seeing long
> >> > threads being (politely) advised to move it on over to offtopic,
> >> > meaning
On Mon, Dec 10, 2018 at 11:13:35PM +, Brian wrote:
On Mon 10 Dec 2018 at 17:47:20 -0500, Cindy-Sue Causey wrote:
I *thought* there used to be a Debian-Offtopic (or off-topic)
listserv, but I don't see it listed on the listserv homepage [0]...
which is where I THOUGHT I saw it listed.
Your
Vincent Lefevre wrote:
> I get the following error when I try to connect to wifi hotspots with
> no encryption. This is from the wicd log:
>
> [...]
> 2018/12/11 18:44:15 :: Putting interface up...
> 2018/12/11 18:44:15 :: ifconfig wlp61s0 up
> 2018/12/11 18:44:17 :: enctype is None
> 2018/12/11
Greg writes:
> Americans (at least in my part of the country) never use "shall" at
> all. To us, it simply sounds archaic. We'd expect it in the King James
> Bible, or in certain kinds of fantasy literature.
I might use it in a question but other uses are archaic except in a
legalistic context s
I get the following error when I try to connect to wifi hotspots with
no encryption. This is from the wicd log:
[...]
2018/12/11 18:44:15 :: Putting interface up...
2018/12/11 18:44:15 :: ifconfig wlp61s0 up
2018/12/11 18:44:17 :: enctype is None
2018/12/11 18:44:17 :: ['iwconfig', 'wlp61s0', 'ess
On Tuesday 11 December 2018 12:31:46 Greg Wooledge wrote:
> On Tue, Dec 11, 2018 at 06:22:56PM +0100, Thomas Schmitt wrote:
> > Dan Ritter wrote:
> > > The English use it more than Americans do.
> >
> > In school it was a big deal to distinguish "will" and "shall".
> > (I was very eager to forget
On 11/12/18 17:31, Greg Wooledge wrote:
> On Tue, Dec 11, 2018 at 06:22:56PM +0100, Thomas Schmitt wrote:
>> Dan Ritter wrote:
>>> The English use it more than Americans do.
>>
>> In school it was a big deal to distinguish "will" and "shall".
>> (I was very eager to forget the exact rules when nobo
On Tue, Dec 11, 2018 at 06:22:56PM +0100, Thomas Schmitt wrote:
> Dan Ritter wrote:
> > The English use it more than Americans do.
>
> In school it was a big deal to distinguish "will" and "shall".
> (I was very eager to forget the exact rules when nobody cared any more.)
Americans (at least in m
W dniu 11.12.2018, wto o godzinie 14∶09 +, użytkownik Joe napisał:
> On Tue, 11 Dec 2018 09:16:01 + (UTC)
> Curt wrote:
>
> > On 2018-12-10, Cindy-Sue Causey wrote:
> > >
> > > Beyond that, I *thought* I remembered a few times seeing long
> > > threads being (politely) advised to move i
Hi,
i wrote:
> > This function shall obtain the drive status and not wait until the
> > status of the medium is decided.
mick crane wrote:
> I have noticed that people whose first language might not be english use
> "shall" as apposed to "will" or "should".
The topic has its own wikipedia articl
On 2018-12-11, Joe wrote:
>
>> On 2018-12-10, Cindy-Sue Causey wrote:
>> >
>> > Beyond that, I *thought* I remembered a few times seeing long
>> > threads being (politely) advised to move it on over to offtopic,
>> > meaning the listserv I thought I remembered..
>> >
>>
>> Yeah, but apparently
On Tuesday 11 December 2018 06:25:43 Thomas Schmitt wrote:
> Hi,
>
> i wrote:
> > > I know some more such dumplings.
>
> Gene Heskett wrote:
> > So do I, Thomas, but this is supposedly a polite list. :)
>
> I actually meant the bugs, not the bug makers whose sympathy is
> probably needed to ever g
gracias!. era eso mismo. ya me estaba volviendo loco.
On 12/11/2018 11:41 AM, Greg Wooledge wrote:
On Tue, Dec 11, 2018 at 11:29:28AM -0500, Eriel Perez wrote:
(*system*) ERROR (Missing newline before EOF, this crontab file will be
ignored)
Add the missing newline. If you use vi/vim, this hap
On Tue, Dec 11, 2018 at 11:29:28AM -0500, Eriel Perez wrote:
> (*system*) ERROR (Missing newline before EOF, this crontab file will be
> ignored)
Add the missing newline. If you use vi/vim, this happens automatically
and you cannot stop it. If you use something else, maybe you just have
to press
colegas
tengo este error en el syslog
(*system*) ERROR (Missing newline before EOF, this crontab file will be
ignored)
Alguna idea? esta en el fichero de rotacion de las trazas.
40 8 * * * root /usr/local/sbin/trazas.sh
la linea arriba es la que esta en el crontab (/etc/crontab
riveravaldez wrote:
> > Anything visible in your logs?
>
> And this is what I get after just boot and log-in to desktop (just fluxbox):
>
> $ sudo dmesg | grep nouveau
> [ 10.172253] nouveau :00:0d.0: NVIDIA C61 (04c000a2)
> [ 10.420487] nouveau :00:0d.0: fb0: nouveaufb frame buffer
Hello
it sems some recent update made my usb-disks appear as
/dev/disk/by-id/usb-Seagate_M3_Portabable...
indstead of
/dev/disk/by-id/ata-ST4000LM024...
nbd BUT they no longer spindown automatically and hdparm throws some error
# hdparm -S55 /dev/disk/by-id/usb-Seagate_M3_Portable_...
/dev/disk
mick crane wrote:
> On 2018-12-10 20:02, Thomas Schmitt wrote:
> > For the purpose of sr_drive_status(), the loop is really inappropriate.
> > This function shall obtain the drive status and not wait until the
> > status of the medium is decided.
> >
> completely off the topic but I have notice
On Tue, 11 Dec 2018 09:16:01 + (UTC)
Curt wrote:
> On 2018-12-10, Cindy-Sue Causey wrote:
> >
> > Beyond that, I *thought* I remembered a few times seeing long
> > threads being (politely) advised to move it on over to offtopic,
> > meaning the listserv I thought I remembered..
> >
>
> Ye
>> asking on Nouveau's mailing-list they recommended me this:
>>
>> > Use an environment that doesn't make use of GL for basic tasks.
>
> You're already doing that. GL isn't the problem unless you're
> having non-random freezes when you fire up 3D applications.
Thanks for your answer, dsr. That's
On 27-11-2018, at 13h 52'25", Ionel Mugurel Ciobîcă wrote about "issues with
stretch, issue 2 from many"
> Dear all,
[...]
> Question 2.1: Why .xsession is not read and .xsessionrc is read?
> Question 2.2: Who starts the second call of fvwm? If I comment out the
> fvwm call in .xsession(rc) then t
On 8-12-2018, at 13h 59'28", Stefan Krusche wrote about "Re: issues with
stretch, part 1 of many"
> Good day, Ionel,
Hi Stefan,
>
> This is just a guess. Maybe you are looking for this option
> in /etc/ssh/ssh_config:
>
> # StrictHostKeyChecking ask
Mine is set to no. I did it way befor
On 2018-12-10 20:02, Thomas Schmitt wrote:
Hi,
Gene Heskett wrote:
Perhaps that patch could be reverted,
It had its legitimate intentions, 10 years ago.
See
https://github.com/torvalds/linux/commit/210ba1d1724f5c4ed87a2ab1a21ca861a915f734
and a glimpse of the following woes
http://lkml.i
Marek Mosiewicz wrote:
...
> I remember time when internet had news groups and it was different type
> of social. Maybe it is wrong word. I mean place for generic discussion.
> For sure better than TV
usenet still exists and the social groups are
still there, but they may not be very active
t
Hi,
i wrote:
> > I know some more such dumplings.
Gene Heskett wrote:
> So do I, Thomas, but this is supposedly a polite list. :)
I actually meant the bugs, not the bug makers whose sympathy is probably
needed to ever get the bugs fixed.
(When pointing with one finger at others, three fingers ar
On 2018-12-11, Curt wrote:
> On 2018-12-10, Cindy-Sue Causey wrote:
>>
>> Beyond that, I *thought* I remembered a few times seeing long threads
>> being (politely) advised to move it on over to offtopic, meaning the
>> listserv I thought I remembered..
>>
>
> Yeah, but apparently the off-topic gr
On 2018-12-10, Cindy-Sue Causey wrote:
>
> Beyond that, I *thought* I remembered a few times seeing long threads
> being (politely) advised to move it on over to offtopic, meaning the
> listserv I thought I remembered..
>
Yeah, but apparently the off-topic group was consistently drifting
on topic
35 matches
Mail list logo
