Hi loyal Creamy fans,
Sorry if you've missed me for the last year or so, but I'm back, (from the
future), now.
So, anyway, the latest commit to msdosfs_conv.c causes a small problem in
the year 2100.
The DOS end of time is 12/31/2107. Now that we support 2038,
msdosfs_conv.c was patched
:
Your email address of choice is creamy@creamylan, and you want to relay
mail addressed to example.com via an SMTP server at smtp.creamylan.lan.
From reading the man pages, you would be forgiven for thinking that the
following will work:
table creamy db:/etc/mail/creamy.db
table secrets db:/etc/mail
On Sat, May 10, 2014 at 06:48:18PM +0200, Denis Fondras wrote:
Le 10/05/2014 17:54, Creamy a ?crit :
table creamy db:/etc/mail/creamy.db
table secrets db:/etc/mail/secrets.db
accept sender creamy for domain example.com relay via
smtps+auth://foo...@smtp.creamylan.lan auth secrets
On Sat, May 10, 2014 at 10:39:22PM +0200, Frank Brodbeck wrote:
On Sat, May 10, 2014 at 07:03:14PM +0100, Creamy wrote:
So the manual page is wrong, or at least misleading, because
the syntax of the examples differs between from, sender, and
for, so it's not clear whether the angle brackets
if0 nwid foo wpakey bar
sleep 3
dhclient -L /output
cat /output
fails with cat: /test: No such file or directory.
dhclient needs to recognise that it is not just continuing with an
active lease, even though the new lease has the same parameters it
has come from a different dhcp server.
--
Creamy
On Sun, May 11, 2014 at 06:03:24AM -0400, Kenneth Westerback wrote:
On 11 May 2014 05:26, Creamy cre...@dishplanning.com wrote:
Hello again!
OK, this time it's a bug, (or is it a feature?), in dhclient.
Imagine that you have two separate wireless networks, which operate
On Sun, May 11, 2014 at 06:31:23AM -0400, Kenneth Westerback wrote:
On 11 May 2014 06:03, Kenneth Westerback kwesterb...@gmail.com wrote:
On 11 May 2014 05:26, Creamy cre...@dishplanning.com wrote:
Hello again!
OK, this time it's a bug, (or is it a feature?), in dhclient.
Imagine
On Sun, May 11, 2014 at 06:52:51AM -0400, Kenneth Westerback wrote:
On 11 May 2014 06:38, Creamy cre...@dishplanning.com wrote:
On Sun, May 11, 2014 at 06:03:24AM -0400, Kenneth Westerback wrote:
On 11 May 2014 05:26, Creamy cre...@dishplanning.com wrote:
Hello again!
OK
the 5.0 era:
http://marc.info/?l=openbsd-bugsamp;m=132851264207109amp;w=2
--
Creamy! 3
in
software?
7E1, and 7O1 don't need explicit hardware support.
If you need 7N1, 7M1 will simulate 7N2, which the majority of hardware will work
with, (an extra stop bit).
If 8N1 works, and there is confusion over support for other modes, just bit bang
in 8N1 mode.
--
Creamy! 3
it as an option. Those who want to use it
have a choice.
Why don't the two OpenBSD users who actually use IPv6 just use
link local addresses between themselves :-)))
--
Creamy! 3
solution.
IPv6 exists. It's useful. OpenBSD supports it very well. Do we need it
enabled by default? No.
--
Creamy! 3
of a table.
we could do it, but i don;t want to. sometimes it's better to sacrifice
being a million percent correct for clarity.
Eh? How can giving incorrect information help clarity? That's a bit
strange.
--
Creamy! 3
, because how do we know that any innocent
USB device, a mouse or a keyboard for example, doesn't have firmware that
tells it to emulate a disk for 10 seconds after power is applied if it
sees that a BIOS is initialising it, and then change to an innocent device
afterwards?
--
Creamy! 3
, pckbd_keydesc_term122),
KBD_MAP(KB_UK | KB_SWAPCTRLCAPS, KB_UK, pckbd_keydesc_swapctrlcaps),
KBD_MAP(KB_JP | KB_SWAPCTRLCAPS, KB_JP, pckbd_keydesc_swapctrlcaps),
KBD_MAP(KB_FR | KB_SWAPCTRLCAPS, KB_FR, pckbd_keydesc_swapctrlcaps),
--
Creamy! 3
) =
e1b9688f2ebf5a278408c49ac13e35479a96b883ff9891ada141470d55a1b158
If anyone running stable can check it yours is the same, I appreciate.
It matches -release from the official CD.
--
Creamy! 3
that a 'repeat' keysym is defined in the
X sources, but it doesn't seem to be implemented in the code.
Any reason this console version can't be included in the tree?
--
Creamy
Diff'ed against 5.2-release
--
Creamy
--- wsksymdef.h.origTue May 24 13:23:49 2011
+++ wsksymdef.h Thu Mar 7 18:50:32 2013
@@ -507,6 +509,7 @@
#define KS_Henkan 0xf115 /* Alias for Henkan_Mode */
#define KS_Muhenkan0xf116 /* Cancel Conversion */
#define
The following patch adds the keycodes for F13-F24 on a standard PC-122
terminal keyboard.
Doesn't seem to conflict with anything else I've found.
--
Creamy
--- wskbdmap_mfii.c.origTue May 24 13:23:46 2011
+++ wskbdmap_mfii.c Thu Mar 14 13:10:56 2013
@@ -130,6 +130,18 @@
KC(83
) ?
--
Creamy
a submap for 122 key terminal
keyboards, but how would you like it done exactly?
--
Creamy
].
That's not a bug, it's a feature :-). It works as a 'reset' key, in case
you accidently run wsconsctl keyboard.repeat.del1=10 instead of =100 :-)
OK, seriously, yes it's a bug, I'll fix that and resubmit it, now that you
can see how useful the functionality is...
--
Creamy
of the VCs. Great.
--
Creamy
in a closed environment, but if people are using netcat in
a script as a quick and nasty way to write clients for internet based
services, that is not something we should advocate, because it's
wrong.
--
Creamy
the concept work. Oh, you can't, because it's broken by design.
Are you seriously suggesting that an enterprise WAN solution can be
built on netcat?
--
Creamy
to make it
work 99% of the time just hurts the users who are stuck with the 1% of
failiures.
--
Creamy
of you, as I have been for the last few
years.
If you don't like
nc, don't use it. Do you think we care?
Why should you?
You really mis-understand my whole stance on this.
--
Creamy
On Wed, Mar 20, 2013 at 09:21:10AM +0100, Otto Moerbeek wrote:
On Wed, Mar 20, 2013 at 12:43:37AM +, Creamy wrote:
On Tue, Mar 19, 2013 at 06:34:31PM -0600, Theo de Raadt wrote:
Using netcat to reliably get data is never going to be appropriate
for a production system, IMHO
*/
switch (kp-group1[0]) {
--
Creamy
) (clockcentury == 20))) {
printf(WARNING: Setting NVRAM century to %d\n,
clockcentury);
s = splclock();
--
Creamy
.
--
Creamy
On Fri, Mar 22, 2013 at 12:29:19PM +0100, Stefan Sperling wrote:
On Fri, Mar 22, 2013 at 09:55:01AM +, Creamy wrote:
Are you suggesting to add individual locales as and when a significant
number of translations exist in ports, (good idea), or to select a
few South-American dialects
, iff is a bad term to use precisely for this reason, so please
spell it out in full :-).
--
Creamy
time.
flamebait
iff you know what it means :-)
/flamebait
--
Creamy
);
}
--
Creamy
Hello Creamy fans!
Here's a patch to change the tic man page to actually state the correct
terminfo directory...
--- /usr/src/usr.bin/tic/tic.1.orig Sat Mar 23 20:01:18 2013
+++ /usr/src/usr.bin/tic/tic.1 Sat Mar 23 20:02:11 2013
@@ -31,7 +31,7 @@
.\ $Id: tic.1,v 1.15 2010/09/02 09:00:01
/identd identd
-elo
127.0.0.1:comsat dgram udp waitroot/usr/libexec/comsat comsat
[::1]:comsat dgram udp6waitroot/usr/libexec/comsat comsat
#ntalk dgram udp waitroot/usr/libexec/ntalkd ntalkd
--
Creamy
should change, remove -o in the rc.conf comment, or add -o in
the, (disabled), lines in inetd.conf?
--
Creamy
/share/terminfo
1 2 3 4 5 6 7 8 9 A E L M N P Q X a b c d e f g h i j k l m n o p q r s t u v w
x z
--
Creamy
not wait for the scripts to finish.
1171-The scripts are executed as root (with the real and effective user ID set
to 0),
No, they are not. Which is wrong, the man page, or the behavior of pppd?
--
Creamy
the place in just a few seconds? You're seeing them
through rose-tinted glasses if you did.
Not to mention that the decent Vaxen need three phase power. Great.
Looking to the future, when are we going to drop 486 support, anyway?
--
Creamy
?
Don't worry, it's been replaced with a couple of PDP11/70's,
so we can all sleep well at night.
N.B. This one *isn't* a joke.
--
Creamy
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
On Mar 26, 2013, at 6:26 PM, Creamy cre...@nocrater.com wrote:
but I honestly question the utility of any of these ISA
network and SCSI drivers.
Perhaps somebody who is new to coding might be able to learn something
On Wed, Mar 27, 2013 at 10:43:53AM +, Stuart Henderson wrote:
On 2013/03/26 18:06, Creamy wrote:
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
On Mar 26, 2013, at 6:26 PM, Creamy cre...@nocrater.com wrote:
Looking to the future, when are we going to drop 486
is, effectively, already broken, (as I suspected),
because the devices that typically go with machines of that era are
suffering bit-rot in the tree?
--
Creamy
rude to me off-list, but I thought you were above that.
Really, this community has an attitude problem - and you *need*
more developers, believe me, you shouldn't be trying to scare
them away.
--
Creamy
writing good code?), and general written abuse, mostly
off-list.
Get a life.
--
Creamy
47 matches
Mail list logo
