*From:* Sven Joachim
*Sent:* Thursday, April 10, 2014 5:08PM
*To:* debian-user@lists.debian.org
*Subject:* Re: OpenSSH Packages No Longer Suggest openssh-blacklist
On 2014-04-10 23:30 +0200, Alex Robbins wrote:
I have been using Debian Testing (Jessie) and tried to upgrade today, and
-blacklist-extra in any way
I do not quite know which programs use the blacklist, but what is the
reason for
this change? Shouldn't the client, the server, or both at least suggest
openssh-blacklist? I couldn't find anything about this in the changelogs.
Thanks,
Alex Robbins
--
To U
I was able to copy almost everything from dd images to a new set
of filesystems. The only thing that was excluded from the transfer
was /var/cache/apt, because something in there was causing the problem.
I performed the transfer by booting to a second system. Interestingly,
when this problem aro
9afa09ff38e86 ]---
If there is a better way to include the log in the future (e.g. attachment),
please let me know.
Thank you,
Alex Robbins
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
On 09/11/2012 06:02 PM, lee wrote:
Alex Robbins writes:
That said, I started with screen and then switched to tmux, which is an
actively developed rewrite of screen (and is BSD licensed). It has many
technical and objective improvements over screen, and, additionally, it
has proven a much
s of different sizes,
dynamically resizing as conditions change. (I use the version from testing,
but tmux is also available in the squeeze repo.)
There is plenty of information on the web concerning tmux and it's use.
Alex Robbins
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debi
On 09/08/2012 02:55 AM, Brian wrote:
On Fri 07 Sep 2012 at 16:04:51 -0500, Alex Robbins wrote:
I am also hoping to take it a step further and say that the restricted key
(the one that only works at certain times) also requires that a pass phrase
be provided that changes based on an arbitrary
be, and I have written C# under Windows, but
I have not written C or C++. Or, maybe I missed something, and I actually
don't have to write anything other than a configuration file?
So, my question is, does anyone have any thoughts on how I should go about
making this happen?
Thank you,
Alex
On 08/27/2012 08:45 AM, Camaleón wrote:
On Sun, 26 Aug 2012 16:51:54 -0500, Alex Robbins wrote:
I am running Debian testing, which currently has kernel 3.2.23-1, same
as unstable. experimental has 3.5.something. I am looking to run
kernel version 3.3 or higher.
As I understand it, there are
On 08/26/2012 09:48 PM, Charles Kroeger wrote:
or you could install: linux-headers-amd64 linux-image-amd64 this would
insure you always had the latest kernel and headers. Your architecture
may be different so you might want to look to that in regard to my
examples.
This does not at all answer
On 08/26/2012 06:39 PM, Gary Dale wrote:
I'm confused. You said that unstable has the same version as testing,
so installing from SID wouldn't get you anything.
You're right, it wouldn't. I misspoke. I meant to say, "or I could
install
from *experimental*"
If you are looking for stability and
I am running Debian testing, which currently has kernel 3.2.23-1, same
as unstable. experimental has 3.5.something. I am looking to run
kernel version 3.3 or higher.
As I understand it, there are 2 ways to go about this. I could build
from the kernel.org source, or I could install from unst
On 08/24/2012 10:46 AM, Camaleón wrote:
El 2012-08-22 a las 15:16 -0500, Alex Robbins escribió:
(resending to the list)
On 08/22/2012 09:41 AM, Camaleón wrote:
On Tue, 21 Aug 2012 15:12:15 -0500, Alex Robbins wrote:
A recent Debian Security Advisory [1] warned that the package icedove
had
A recent Debian Security Advisory [1] warned that the package icedove had
several security issues. These issues were resolved in version 10.0.6-1
(and a
different version for Squeeze). I notice, however, that while 10.0.6-2 is
available in Sid, Wheezy is still at 10.0.5-1. This page [2] (whic
On 08/01/2012 08:41 PM, Kumar Appaiah wrote:
On Wed, Aug 01, 2012 at 07:33:35PM -0500, Alex Robbins wrote:
.
./dir
This is the expected output. However, when I execute:
find -print0 -type d
I see (on a terminal screen that does not display null characters):
../dir./file
The same goes for
I have a directory that looks like this:
.
├── dir
└── file
"dir" is a directory and "file" is a regular file. I execute:
find -type d
and get the output:
.
./dir
This is the expected output. However, when I execute:
find -print0 -type d
I see (on a terminal screen that does not display null cha
16 matches
Mail list logo
