Dear Debian.org
Hope you are doing good.
We’d like to inform you a very important issue regarding your website”
Debian.org” which is the reason why you are losing lots of traffic and
conversion.
Your website is good in terms of design and content. However, it doesn’t
follow Search Engine Guidelin
On 2019-12-05, Brian wrote:
>
>> If you have nothing to hide, it most certainly does not mean you have
>> nothing to fear.
>
> I wondered when the "If you have nothing to hide,..." argument would
> surface. I have plenty to hide. For example, I would not like it widely
> known that I occasionally
On Fri, Dec 06, 2019 at 09:28:58AM -, Curt wrote:
[...]
> Unhappily, both you and Joe were so impatient to refute this argument
> that you could not wait for it to be actually presented [...]
A little pompous yourself, of late?
Nevermind
-- t
signature.asc
Description: Digital signature
On 2019-12-06, wrote:
>
> On Fri, Dec 06, 2019 at 09:28:58AM -, Curt wrote:
>
> [...]
>
>> Unhappily, both you and Joe were so impatient to refute this argument
>> that you could not wait for it to be actually presented [...]
>
> [...] pompous [...]?
You seem to have sadly progressed backwar
On Fri, Dec 06, 2019 at 10:21:45AM -, Curt wrote:
> On 2019-12-06, wrote:
> > [...] pompous [...]?
>
> You seem to have sadly progressed backwards [...]
Thanks for confirming.
Cheers?
-- t
signature.asc
Description: Digital signature
I could be an offset defined.
Could you post following files?
/sys/block/sdd/queue/optimal_io_size
/sys/block/sdd/queue/minimum_io_size
/sys/block/sdd/alignment_offset
/sys/block/sdd/queue/physical_block_size
/sys/block/sdd/queue/logical_block_size
Toni Mas
Missatge de Sergey Spiridonov de
The files exist. They'd been unmodified, and working, for several
months. 'ufw reset' regenerates them with the defaults. Neither of them
includes the word 'DROP', and I don't think their contents are passed
directly to nftables. I'm not familiar with their syntax, so I can't say
if there's any
On 12/5/19 5:02 AM, Bjoern Schiessle wrote:
I tried to move the file /usr/local/share/lua/5.2/DBI.lua away, then
the error message changes to:
Dec 05 11:57:35 sql error Error in SQL transaction:
/usr/share/lua/5.2/DBI.lua:53: Cannot load driver MySQL. Available
drivers are: PostgreSQL
So
Brian Vaughan writes:
>
> It looks to me like both in /sbin and in /usr/sbin, there are symlinks
> from the names of the old iptables executables to the nftables
> versions, via /etc/alternatives. So I'm not sure what was actually
> changed, but now I'm thinking that the iptables update revealed
hi,
please reply to the list only...
here is my script fragment:
=
#!/bin/bash
#this doesn't work...
echo -e "\n\nThis doesn't work.\n\n"
old_summary=`echo "Previous glitches and inconsistencies were due to a missing
/ at the end of the baseurl... ,.#*$+%*$&#+(*={_})"`
echo "Summary -
On Fri, Dec 06, 2019 at 12:06:10PM -0500, songbird wrote:
> #this doesn't work...
> old_summary=`echo "Previous glitches and inconsistencies were due to a
> missing / at the end of the baseurl... ,.#*$+%*$&#+(*={_})"`
> result=`echo "summary: \"\"" | sed -e "s/^summary: .*$/summary:
> \"${old_s
I have a buster system that is failing ever to reach a login prompt on the
console tty.
The last message on the screen is:
A start job is running for Hold until boot process finished up
followed by a timer that simply increases without end and says "no limit".
How do I find out what is causing
D. R. Evans composed on 2019-12-06 11:11 (UTC-0700):
> I have a buster system that is failing ever to reach a login prompt on the
> console tty.
> The last message on the screen is:
> A start job is running for Hold until boot process finished up
> followed by a timer that simply increases with
Greg Wooledge wrote:
...
> Ideally, you'd just stop trying to use sed with user-supplied variables
> injected into the code. Sed was never built to be safe for that kind of
> work.
sed was designed to operate on streams. a sequence of
characters is a stream. i don't see any reason why
putti
On Fri, Dec 06, 2019 at 02:40:49PM -0500, songbird wrote:
> Greg Wooledge wrote:
> ...
> > Ideally, you'd just stop trying to use sed with user-supplied variables
> > injected into the code. Sed was never built to be safe for that kind of
> > work.
>
> sed was designed to operate on streams. a
On 2019-12-06 at 14:40, songbird wrote:
> Greg Wooledge wrote: ...
>> Ideally, you'd just stop trying to use sed with user-supplied
>> variables injected into the code. Sed was never built to be safe
>> for that kind of work.
>
> sed was designed to operate on streams. a sequence of characters
Brian Vaughan wrote:
someone already filed a bug for this (by a quick look
at ufw bug reports).
note that iptables version 1.8.3-2 (current testing version)
and ufw 0.36-1 work ok (ufw is same version for both testing
and unstable at the moment)
songbird
Yes, filed since I last checked:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946289
On 12/6/2019 12:09 PM, songbird wrote:
Brian Vaughan wrote:
someone already filed a bug for this (by a quick look
at ufw bug reports).
note that iptables version 1.8.3-2 (current testing version)
a
The Wanderer wrote:
>songbird wrote:
...
>> sed was designed to operate on streams. a sequence of characters is
>> a stream. i don't see any reason why putting the variable into the
>> middle of that expression means anything different.
>
> Because sed doesn't see the variable; the variable is ha
Greg Wooledge wrote:
...
> If you insist on doing #1, so be it. It's your damned computer, and your
> damned problem. I can only warn you and be ignored so many times
> before I give up and let your fuck yourself, as you so vehemently and
> stubbornly eager to do.
i appreciate the actual expla
Felix Miata wrote on 12/6/19 11:22 AM:
> D. R. Evans composed on 2019-12-06 11:11 (UTC-0700):
>
>> I have a buster system that is failing ever to reach a login prompt on the
>> console tty.
>
>> The last message on the screen is:
>> A start job is running for Hold until boot process finished up
On 12/6/2019 10:25 PM, D. R. Evans wrote:
> Felix Miata wrote on 12/6/19 11:22 AM:
>> D. R. Evans composed on 2019-12-06 11:11 (UTC-0700):
>>
>>> I have a buster system that is failing ever to reach a login prompt on the
>>> console tty.
>>
>>> The last message on the screen is:
>>> A start job i
On 3/12/19 8:42 pm, Keith Bainbridge wrote:
Just wondering if this is ALL good advice?
Should I use it for ALL my mail, or just sensitive stuff, like lobbying
politicians.
I'm still here. Have had a couple of questions that have gotten me
thinking deeply, primarily about whose/what safe
On 06.12.19 14:40, songbird wrote:
> Greg Wooledge wrote:
> ...
> > Ideally, you'd just stop trying to use sed with user-supplied variables
> > injected into the code. Sed was never built to be safe for that kind of
> > work.
>
> sed was designed to operate on streams. a sequence of
> charact
On 7/12/19 12:55 pm, Keith Bainbridge wrote:
On 3/12/19 8:42 pm, Keith Bainbridge wrote:
Just wondering if this is ALL good advice?
Should I use it for ALL my mail, or just sensitive stuff, like
lobbying politicians.
I'm still here. Have had a couple of questions that have gotten me
thi
Erik Christiansen wrote:
...
> If the sed implementation of variable regexes proves problematic, then
> there's awk with its Dynamic Regexps. (Section 2.8 of the pdf manual
> floating about out there.)
>
> With its C-like syntax, it's less write-only than perl, perhaps because
> it is of the same v
26 matches
Mail list logo
