Why I want this?
Just trying to use the updated things. Also, I want to gain the advantage
of additional driver updates and better hardware compatibility as per
experience with Ubuntu.
Would you suggest me to do so?
Is it safe to do so?
What additional changes/risks I would have to handle?
Regards
(Resent)
Hello,
Mike Gabriel a écrit :
>
> I did not meet that issue on my test rig. I will check the recently
> upload package and report back.
FWIW, I just upgraded the isc-dhcp-server package on my i386 Squeeze
server and did not meet that issue. It only has /etc/dhcp/dhcpd.conf, no
/etc/dh
Hi.
On Sat, 16 Jan 2016 00:49:17 -0500
Steve Matzura wrote:
> Reco:
>
> All of this is an excellent learning opportunity for me. Please bear
> with me just a bit as I ask the following:
>
> On Sat, 16 Jan 2016 01:55:38 +0300, you wrote:
>
> >A simple solution:
> >
> >iptables -I INPUT
On Saturday 16 January 2016 06:06:48 Gene Heskett wrote:
> > > shows in that shells env report, but it can't find its executable
> > > with both hands, prefering to give me a
> > > gene@coyote:~/eagle-7.5.0$ bin/eagle
> > > bash: bin/eagle: No such file or directory
> > >
> > > Clues? I'm confused
Himanshu Shekhar [2016-01-16 14:02:35+05:30] wrote:
> Just trying to use the updated things. Also, I want to gain the
> advantage of additional driver updates and better hardware
> compatibility as per experience with Ubuntu. Would you suggest me to
> do so? Is it safe to do so? What additional ch
I'm interested in how laptop batteries report their charge and discharge. I'd
like to collect some data, so I'm asking for your assistance.
I've written a script that uses the "acpi" program to collect some information.
I'd like you to run my script, unplug your laptop, let it run until it nee
On Saturday 16 January 2016 05:05:22 Lisi Reisz wrote:
> On Saturday 16 January 2016 06:06:48 Gene Heskett wrote:
> > > > shows in that shells env report, but it can't find its
> > > > executable with both hands, prefering to give me a
> > > > gene@coyote:~/eagle-7.5.0$ bin/eagle
> > > > bash: bin
Reco:
On Sat, 16 Jan 2016 12:57:30 +0300, you wrote:
>>-j, --jump target
>> This specifies the target of the rule; i.e., what to do
>> if the packet matches it. The target can be a user-defined
>> chain (other than the one this rule is in), one of the special builtin
On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett wrote:
> I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> bin/eagle, which is perfectly legal syntax.
Gene,
Could you post the output of ldd /home/gene/eagle-7.5.0 for us to see?
Brandon Vincent
Hi.
On Sat, 16 Jan 2016 07:35:54 -0500
Steve Matzura wrote:
> >But with conjunction with the previous one it implements the following
> >policy:
> >
> >- anyone can connect up to 16 times via ssh.
> >- anyone exceeding the connection limit is tarpitted, and must wait
> >for an hour to try
There is laptop with "stretch/sid" on it.
I want umount all remote filesysems before suspending/hibernating it.
When google I found only solutions referring to pm-utils and
/etc/pm/sleep.d sripts. But this does not work for me. It looks like
pm-hibernate is not even calling.
So my question is: how
On Sat, 16 Jan 2016 14:31:20 +0100
kjo...@poczta.onet.pl (Kamil Jońca) wrote:
>There is laptop with "stretch/sid" on it.
>I want umount all remote filesysems before suspending/hibernating it.
>When google I found only solutions referring to pm-utils and
>/etc/pm/sleep.d sripts. But this does not w
Hi list,
xmessage does not work properly any more on my sid system. The window
is displayed as expected, it has a working okay button, but the actual
message is not readable. It could be that the message is displayed in
the background color, making it invisible.
I have a custom .Xresources file.
On 2016-01-16, Gene Heskett wrote:
>>
>> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not /bin/eagle?
>>
>> Lisi
>
> I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> bin/eagle, which is perfectly legal syntax.
Not if bin is not in your path it isn't.
Otherwise, the mes
On Sat, Jan 16, 2016 at 8:57 AM, Curt wrote:
> Not if bin is not in your path it isn't.
You should probably read [1].
It is legal syntax.
[1] http://mywiki.wooledge.org/BashFAQ/028
Brandon Vincent
On 2016-01-16, Brandon Vincent wrote:
> On Sat, Jan 16, 2016 at 8:57 AM, Curt wrote:
>> Not if bin is not in your path it isn't.
>
> You should probably read [1].
>
> It is legal syntax.
> [1] http://mywiki.wooledge.org/BashFAQ/028
I don't see what you're referring to in there.
> Brandon Vince
On Sat, 16 Jan 2016 16:55:23 +0100
Thierry Rascle wrote:
>Hi list,
>
>xmessage does not work properly any more on my sid system. The window
>is displayed as expected, it has a working okay button, but the actual
>message is not readable. It could be that the message is displayed in
>the backgroun
On Sat, Jan 16, 2016 at 9:14 AM, Curt wrote:
> I don't see what you're referring to in there.
Eagle installs itself into your home directory under a folder called
"eagle-7.5.0". Inside this folder is the "bin" folder in which the
Eagle executable is stored. If you are in the ~/eagle-7.5.0 directo
On 2016-01-16, Brandon Vincent wrote:
> On Sat, Jan 16, 2016 at 9:14 AM, Curt wrote:
>> I don't see what you're referring to in there.
>
> Eagle installs itself into your home directory under a folder called
> "eagle-7.5.0". Inside this folder is the "bin" folder in which the
> Eagle executable i
On Sat, Jan 16, 2016 at 9:42 AM, Curt wrote:
> Thank you for your time. Just another misapprehension I've been laboring
> under these many years.
I actually linked to the wrong article. I've never been able to find
actual Bash documentation that states this.
It just has always worked.
Brandon V
On Sat, 16 Jan 2016 09:21:17 -0700
Charlie Kravetz wrote:
> On Sat, 16 Jan 2016 16:55:23 +0100
> Thierry Rascle wrote:
>
> >Hi list,
> >
> >xmessage does not work properly any more on my sid system. The window
> >is displayed as expected, it has a working okay button, but the
> >actual message
Well, I thought I was doing so well. I discover now that no one,
including me, can get into my system any more via ssh. Here are the
current iptables rules:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -j DROP
On Saturday 16 January 2016 08:06:25 Brandon Vincent wrote:
> On Sat, Jan 16, 2016 at 3:49 AM, Gene Heskett
wrote:
> > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> > bin/eagle, which is perfectly legal syntax.
>
> Gene,
>
> Could you post the output of ldd /home/gene/eagle-7
Hi.
On Sat, 16 Jan 2016 12:02:57 -0500
Steve Matzura wrote:
> Well, I thought I was doing so well. I discover now that no one,
> including me, can get into my system any more via ssh. Here are the
> current iptables rules:
>
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUT
On Saturday 16 January 2016 10:57:55 Curt wrote:
> On 2016-01-16, Gene Heskett wrote:
> >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not
> >> /bin/eagle?
> >>
> >> Lisi
> >
> > I was cd'd to /home/gene/eagle-7.5.0 and the command issued was
> > bin/eagle, which is perfectly legal synt
On 15/01/16 08:47, Chris Bannister wrote:
> On Thu, Jan 14, 2016 at 04:50:04PM +, Lisi Reisz wrote:
>> ;-)
>>
>> And please, no group "hugs" among strangers. ;-)
> I remember a 'poster' I had years ago which read "There are no strangers
> here, only friends we haven't met." ;-)
What a good
On Saturday 16 January 2016 11:45:58 Brandon Vincent wrote:
> On Sat, Jan 16, 2016 at 9:42 AM, Curt wrote:
> > Thank you for your time. Just another misapprehension I've been
> > laboring under these many years.
>
> I actually linked to the wrong article. I've never been able to find
> actual Bas
Hi, Steve.
On 14/01/16 13:01, Steve Matzura wrote:
>> I do not know that client, but if your users are using Firefox, maybe
>> you could use FireFTP [1]. I never had problems with it, and we could
>> also say that while users use Firefox, you could run it on different
>> operating systems.
> It
I tried redoing the tables:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -j DROP
-A INPUT -p tcp -m tcp --dport 22 -m conntrack --ctstate NEW -m
hashlimit --hashlimit-upto 1/hour --hashlimit-burst 16
--hashlimi
On Sat, 16 Jan 2016 20:16:28 +0300, you wrote:
>> What'd I do?
>>
>
>Exactly this:
>
>iptables -F INPUT
>iptables -I INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> -m hashlimit --hashlimit 1/hour --hashlimit-burst 16 \
> --hashlimit-mode srcip --hashlimit-name ssh \
> --
Hi, Steve.
On 14/01/16 13:10, Steve Matzura wrote:
> Failing connection:
> (...)
> no matching cipher found: client
> aes192-cbc,3des-cbc,blowfish-cbc,aes128-cbc,aes256-cbc,rijndael128-cbc,rijndael192-cbc,rijndael256-cbc,rijndael-...@lysator.liu.se,des-cbc,des-...@ssh.com
> server
> aes128-ctr,ae
Daniel,
On Sat, 16 Jan 2016 14:50:20 -0300, you wrote:
>I'm sorry. I Had forgotten of the detail of the accessibility :(
No worries. Things are in a sorry state at the moment because of other
things I did without realizing I did them, but I've already told my
usership that Voyager will have to g
It helps to explain things, Daniel, but truly, the client in question
is horrendously out of date and deprecated for all secure intents and
purposes, I'm quite happy to retire it from active support on my
server.
On Sat, 16 Jan 2016 15:19:33 -0300, you wrote:
>Hi, Steve.
>
>On 14/01/16 13:10, Ste
Hi there,
since a few days my normal user, which is in group sound, cannot
play sound (aplay works but no sound) while root can.
Any ideas how to debug this?
This is a debian testing system with pulseaudio and mpd running.
/dev$ find |xargs ls -ld|grep audio
crw-rw+ 1 root audio 14,
Hi all!
Yesterday I had a power outage in my workplace and when the power was
restored, I noticed I did not have Internet access.
In reviewing the DSL router, I saw the "Ethernet" LED representing the
connection to the computer behind it, a PC firewall with Debian Jessie,
was turned off.
Apparen
Daniel Bareiro writes:
> Any idea what could be the problem?
Hardware.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
Hi, John.
Thanks for your reply.
On 16/01/16 17:13, John Hasler wrote:
>> Any idea what could be the problem?
> Hardware.
Do you mean to some problem with the motherboard?
Best regards,
Daniel
signature.asc
Description: OpenPGP digital signature
Hi.
On Sat, 16 Jan 2016 12:46:30 -0500
Steve Matzura wrote:
> On Sat, 16 Jan 2016 20:16:28 +0300, you wrote:
>
> >> What'd I do?
> >>
> >
> >Exactly this:
> >
> >iptables -F INPUT
> >iptables -I INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> > -m hashlimit --hashlimit 1/hou
Hi.
On Sat, 16 Jan 2016 13:01:29 -0500
Steve Matzura wrote:
> I tried redoing the tables:
>
> *filter
> :INPUT ACCEPT [0:0]
> :FORWARD ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> -A INPUT -p tcp -m tcp --dport 22 --tcp-flags SYN,RST,ACK SYN -j DROP
> -A INPUT -p tcp -m tcp --dport 22 -m connt
After a reboot, one of my shares will no longer mount. And of course,
it's the big one, the NAS box. Here is output from `strace mount.cifs
//DISKSTATION1/BigVol1 /mnt/bigvol1 -o
vers=2.1,username=***,password=*** (*** is real username and password
covered up):
execve("/sbin/mount.cifs", ["mount.
Reco:
On Sat, 16 Jan 2016 23:49:57 +0300, you wrote:
>Reverse the order of these two rules. As I wrote in another part of this
>thread, I mistook rules' sequence.
Like this?
iptables -I INPUT -p tcp --dport 22 --tcp-flags SYN,RST,ACK SYN \
-j DROP
iptables -I INPUT -p tcp --dport 22 -m
Reco:
On Sat, 16 Jan 2016 23:48:54 +0300, you wrote:
>Correct sequence would be:
>
>iptables -F INPUT
>iptables -A INPUT -p tcp --dport 22 -m conntrack --ctstate NEW \
> -m hashlimit --hashlimit 1/hour --hashlimit-burst 16 \
> --hashlimit-mode srcip --hashlimit-name ssh \
> --ha
On Saturday 16 January 2016 17:28:32 Gene Heskett wrote:
> somebody forgot to tell my mostly wheezy system.
[snip]
> this system with many years of cruft accumulated.
And it doesn't run like an entirely Wheezy system with no cruft. Now there's
a surprise!
Lisi
modprobe cifs maybe can help you.
2016-01-16 22:02 GMT+01:00 Steve Matzura :
> After a reboot, one of my shares will no longer mount. And of course,
> it's the big one, the NAS box. Here is output from `strace mount.cifs
> //DISKSTATION1/BigVol1 /mnt/bigvol1 -o
> vers=2.1,username=***,password=***
Emanuel,
On Sun, 17 Jan 2016 00:41:11 +0100, you wrote:
>modprobe cifs maybe can help you.
What is supposed to happen when I enter that command? All I got was
another shell prompt.
On Sat, 16 Jan 2016 12:13:14 -0500
Gene Heskett wrote:
>
> But as I said in a PM, its moot, gEDA has come to the rescue.
>
> Now, if ALL the gEDA suite was brought up to date, the repo versions
> are positively ancient, I think it would have been easier. I was able
> to build the latest pcb, V
On Saturday 16 January 2016 17:42:25 Lisi Reisz wrote:
> On Saturday 16 January 2016 17:28:32 Gene Heskett wrote:
> > somebody forgot to tell my mostly wheezy system.
>
> [snip]
>
> > this system with many years of cruft accumulated.
>
> And it doesn't run like an entirely Wheezy system with no cr
On Saturday 16 January 2016 19:41:45 Joe wrote:
> On Sat, 16 Jan 2016 12:13:14 -0500
>
> Gene Heskett wrote:
> > But as I said in a PM, its moot, gEDA has come to the rescue.
> >
> > Now, if ALL the gEDA suite was brought up to date, the repo versions
> > are positively ancient, I think it would
On Sunday 17 January 2016 01:11:04 Gene Heskett wrote:
> FWIW I just reinstalled apt and all its kinfolks, no change, so I
> installed adept, which didn't work, stuck in refresh forever, except it
> wasn't, the file menu was still active, but several attempts to manage
> the repos were ignored, and
On Sat 16 Jan 2016 at 12:28:32 (-0500), Gene Heskett wrote:
> On Saturday 16 January 2016 10:57:55 Curt wrote:
>
> > On 2016-01-16, Gene Heskett wrote:
> > >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not
> > >> /bin/eagle?
> > >>
> > >> Lisi
> > >
> > > I was cd'd to /home/gene/eagle
Hello!
I have been running Debian 8 64-bit xfce. Networking works fine.
Then I added openbox. So now at the desktop manager screen I can
choose between xfce and openbox. Networking still works fine using
xfce (network-manager).
But if I start up into openbox, or startup into xfce and then log
On Saturday 16 January 2016 22:22:34 David Wright wrote:
> On Sat 16 Jan 2016 at 12:28:32 (-0500), Gene Heskett wrote:
> > On Saturday 16 January 2016 10:57:55 Curt wrote:
> > > On 2016-01-16, Gene Heskett wrote:
> > > >> So its full path is /home/gene/eagle-7.5.0/bin/eagle, not
> > > >> /bin/eag
On Fri, Jan 15, 2016 at 12:09:47PM +0200, / vt wrote:
>
> Sorry for the rant but this is driving me crazy - I don't see the point of
> this change. It makes me a thousand times slower.
You'll have to file a bug report in the usual manner. I'm sorry, but
your rant has fallen on deaf ears, we are j
On Sat, Jan 16, 2016 at 04:49:35PM +1100, David wrote:
> On 16 January 2016 at 15:48, Steve Matzura wrote:
> > On Sat, 16 Jan 2016 01:55:38 +0300, Reco wrote:
> >
> >>A simple solution:
> >>
> >>iptables -I INPUT -p dcp -s 59.46.71.0/24 -j DROP
> >
> > iptables v1.4.21: unknown protocol "dcp" spec
54 matches
Mail list logo
