sylvain.sab...@free.fr writes:
> Ever since I've used this software, which must get
> back to 6.4 or so, the manual page has been missing.
The manpage was removed years ago by upstream. Sad but true. The current
documentation for rtorrent is only accessible as a wiki:
https://github.com/rakshasa/r
On Mon, Feb 15, 2021 at 05:03:55PM -0600, Luke Small wrote:
> I'm running fvwm window manager and I just switched to -current. Roxterm is
> totally messed up, won't do transparent background and I tried
> xfce4-terminal and it says it won't do transparent backgrounds because
> compositing is disabl
The Epson Workforce Pro WF-6090 monochrome laser printer works well.
It sells for about $300. Wifi can be disabled. It works on USB and
network. Here is my printcap:
lp|local line printer:\
:lp=/dev/lp:sh:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:
rp|remote line printer:\
:lp=
Hi,
From: Norman Golisz
Date: Fri, 12 Feb 2021 10:21:05 +0100
> Hi,
>
> after upgrading to the latest snapshot my keyboard (Happy Hacking
> Keyboard) stopped working.
I am useing Happy Hacking keyboard model:PD-KB400B and upgraded
OpenBSD current by
http://ftp.riken.jp/pub/OpenBSD/snapshots/am
Ever since I've used this software, which must get
back to 6.4 or so, the manual page has been missing.
I had found a fix for this on the FreeBSD commits back
then. In the meantime, here is the webpage I've used as
a reference : https://linux.die.net/man/1/rtorrent
Hi,
You are correct!
The contents of my .forward!!
pcengine$ cat .forward
"|/usr/local/bin/procmail -f -"
And yes, all my filtering is defined in my .procmailrc file.
Sorry for any confusion!
Cheers,
Steve W.
On 15/02/2021 11:30 a.m., Austin Hook wrote:
Hi Steve, I wonder if in your ema
I'm running fvwm window manager and I just switched to -current. Roxterm is
totally messed up, won't do transparent background and I tried
xfce4-terminal and it says it won't do transparent backgrounds because
compositing is disabled Sure first-world problems, but I REALLY want
fvwm to do trans
On 2/15/21 7:21 PM, Judah Kocher wrote:
Hello Theo,
I never for a moment intended to convey that anyone "owed" me support
of any kind for my outside-the-box use of this tool. While I don't
understand your vitriolic response to someone else's application of
your software for their own perso
On 2/15/21 6:23 PM, Luke A. Call wrote:
On 2021-02-15 09:33:03+, Ottavio Caruso
wrote:
On 14/02/2021 23:44, Theo de Raadt wrote:
When we get reports like this where people "touch the insides", both
Florian and I regret that sysupgrade ever arrived in the system.
We want to delete
> On Sun, 14 Feb 2021 16:44:37 -0700
> "Theo de Raadt" wrote:
>
>> You are outside the box, by changing tons of stuff.
>>
>> People who operate inside the box won't be able to help you.
>>
>> And it is even less likely when you are dishonest in the original
>> email. You claimed your sysupgrade us
Hello,
Does sysupgrade leave any kind of logging behind which could help me to
pinpoint why it is failing on one system while working on another
apparently identical system?
You should get emails:
Subject: hostname upgrade response file
Subject: hostname upgrade log
Subject: hostname rc.sysm
On Mon, Feb 15, 2021 at 12:21:11PM -0500, Judah Kocher wrote:
> Hello Theo,
>
> I never for a moment intended to convey that anyone "owed" me support of any
> kind for my outside-the-box use of this tool.
You couldn't be bothered to even send a dmesg or a copy of the script
with the first email.
On Sun, 14 Feb 2021 16:44:37 -0700
"Theo de Raadt" wrote:
> You are outside the box, by changing tons of stuff.
>
> People who operate inside the box won't be able to help you.
>
> And it is even less likely when you are dishonest in the original
> email. You claimed your sysupgrade use was com
Hi Steve, I wonder if in your email (below) you have your lines slightly
out of order:
> My .procmailrc:
> "|/usr/local/bin/procmail -f -"
I am thinking that is your .forward file.
and
> Not sure if this is your problem or not.? But I have quite a large .procmailrc
> file (200 lines)
Judah
> I did not and do not expect anyone else to solve my problem for me.
Your dishonesty is consistant.
We supply it all as software. You can study it and find your problem.
Blaming me solves nothing.
Hello Theo,
I never for a moment intended to convey that anyone "owed" me support of
any kind for my outside-the-box use of this tool. While I don't
understand your vitriolic response to someone else's application of your
software for their own personal use in a way you do not condone, you are
Hello,
mcmer-open...@tor.at (Marcus MERIGHI), 2021.02.07 (Sun) 18:28 (CET):
> I just saw a reason to crank relayd.conf(5)s "prefork" from its default
> of 3 to 12.
> After restarting relayd I could not connect anymore.
PEBKAC: The "prefork" directive followed the table definitions, which is
the
On 2021-02-15 09:33:03+, Ottavio Caruso
wrote:
> On 14/02/2021 23:44, Theo de Raadt wrote:
> > When we get reports like this where people "touch the insides", both
> > Florian and I regret that sysupgrade ever arrived in the system.
> > We want to delete sysupgrade.
>
> If this is not ju
On 14/02/2021 23:44, Theo de Raadt wrote:
When we get reports like this where people "touch the insides", both
Florian and I regret that sysupgrade ever arrived in the system.
We want to delete sysupgrade.
If this is not just a provocative statement, +1 from me.
I've never liked unatten
On Sun, Feb 14, 2021 at 02:23:08PM +0100, Riccardo Mottola wrote:
> Hi Stuart and others,,
>
>
> Stuart Henderson wrote:
> >
> > > I installed the firmware with fw_update. I try to bring the interface
> > > up, I can set the nwid, but it never connects.
> > What do you type to bring the interfac
Got it.
If i sort out the answer (since i noticed a spare xtra-partition i had made)
i will go ahead and followup...
thx, h.
On Mon, Feb 15, 2021 at 3:28 AM Otto Moerbeek wrote:
> On Mon, Feb 15, 2021 at 01:57:23AM -0800, harold felton wrote:
>
> > howdee,
> >
> > this is totally not critical, b
On Mon, Feb 15, 2021 at 01:57:23AM -0800, harold felton wrote:
> howdee,
>
> this is totally not critical, but i will go ahead and ask:
>
> assuming that i have added the following to /etc/mk.conf...
> DEBUG=-g
> KEEPKERNELS=yes
> SUDO=doas
> WARNINGS=-Wall
>
> how big do i need the /usr/obj pa
howdee,
this is totally not critical, but i will go ahead and ask:
assuming that i have added the following to /etc/mk.conf...
DEBUG=-g
KEEPKERNELS=yes
SUDO=doas
WARNINGS=-Wall
how big do i need the /usr/obj partition to be ?
i do not remember specifically adjusting the /usr/xxx partitions
when
23 matches
Mail list logo