r whatever) and 'run',
> > then if you can trigger it do a 'bt'.
> >
> Just to be thrill, here follows my sha256sum of my /sbin/ifconfig:
>
> SHA256 (/sbin/ifconfig) =
> e1b9688f2ebf5a278408c49ac13e35479a96b883ff9891ada141470d55a1b158
>
> If anyone running stable can check it yours is the same, I appreciate.
It matches -release from the official CD.
--
Creamy! <3
KB_US, pckbd_keydesc_iopener),
+ KBD_MAP(KB_UK | KB_TERM122, KB_UK, 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
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
.
> >
>
> it's why i added the word "optional" to the description. the syntax
> [] is really ugly, and is hard to understand.
Why is it ugly and hard to understand??? I think it's rather obvious
that [] signifies optional and <> signifies the name 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
OpenBSD box at a time? Let's face it, EBCDIC didn't cause enough confusion
and headaches so let's try confusing people with IPv6, complete with
IP addresses that look like an MD5 checksum gone wrong, and impossible to
remember.
> It is time to replace the hack with a proper solution.
IPv6 exists. It's useful. OpenBSD supports it very well. Do we need it
enabled by default? No.
--
Creamy! <3
is
another matter. Autoconfiguration in general is dangerous and
unnecessary. We have 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
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
point if nodbody's interested in it apart from me:-).
Look back in the archives... This was posted around the 5.0 era:
http://marc.info/?l=openbsd-bugs&m=132851264207109&w=2
--
Creamy! <3
On Sun, May 11, 2014 at 06:52:51AM -0400, Kenneth Westerback wrote:
> On 11 May 2014 06:38, Creamy wrote:
> > On Sun, May 11, 2014 at 06:03:24AM -0400, Kenneth Westerback wrote:
> >> On 11 May 2014 05:26, "Creamy" wrote:
> >> >
> >> > Hello a
On Sun, May 11, 2014 at 06:31:23AM -0400, Kenneth Westerback wrote:
> On 11 May 2014 06:03, Kenneth Westerback wrote:
> >
> > On 11 May 2014 05:26, "Creamy" wrote:
> >>
> >> Hello again!
> >>
> >> OK, this time it's a bug, (or i
On Sun, May 11, 2014 at 06:03:24AM -0400, Kenneth Westerback wrote:
> On 11 May 2014 05:26, "Creamy" wrote:
> >
> > Hello again!
> >
> > OK, this time it's a bug, (or is it a feature?), in dhclient.
> >
> > Imagine that you have two separ
#!/bin/sh
ifconfig 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 dhc
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 n
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
t true.
For example:
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
tab
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 w
s for the nocrater.com site, even though it's
off-line at the moment and re-directing everybody to the mobile site,
which is making us look really unprofessional, I know, but I've been
spending so much time contributing to this list that I haven't had time
to fix it. I've also had private mails quizzing me as to who I am,
(who cares, if I'm writing good code?), and general written abuse, mostly
off-list.
Get a life.
--
Creamy
re you just trolling for the sake of it?
I didn't expect that from you, frankly. Other people have been
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
istically, perhaps you could just choose to maintain the
-patch branch of a particular version that was of interest to you. For
example, if we stopped supporting 486 in 6.0, by way of example, what
is to stop you taking 6.0 and maintaining a -patch branch of it for
ever more, backporting any new security and other important patches?
Frankly, that would probably benefit the community much more than trying
to keep the main distribution working on ancient kit forever more.
Please don't put too much weight on a comment which was said quite
casually as a small part of a much wider discussion.
--
Creamy
Server
line covers a lot of machines.
In fact, to everybody else who is reading this, doesn't it just point out
that 486 support 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
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 wrote:
> > > > Looking to the future, when are we goi
On Tue, Mar 26, 2013 at 09:00:39PM +0400, Franco Fichtner wrote:
> On Mar 26, 2013, at 6:26 PM, Creamy wrote:
>
> >> but I honestly question the utility of any of these ISA
> >> network and SCSI drivers.
> >
> > Perhaps somebody who is new to coding might
s
hard disk failed?
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
ia. Not. Have you ever used those machines, with their
crashing removable disk packs. and tape drives that unwound 2400 feet
of tape all over 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
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
rminfo: No such file or directory
$ ls /usr/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
s to use.
Which should change, remove -o in the rc.conf comment, or add -o in
the, (disabled), lines in inetd.conf?
--
Creamy
/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
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/0
_F1 && in <= KS_F20) {
+ if (in >= KS_F1 && in <= KS_F24) {
*out = vt100_fkeys[in - KS_F1];
return (5);
}
--
Creamy
it should be spelled in full letters
> > then ?
>
> iff is a useful technical word which avoids us typing it out in full
> every time.
iff you know what it means :-)
--
Creamy
filter_major &&
This is not exactly a typo, I believe it means, 'if and only if'.
However, iff is a bad term to use precisely for this reason, so please
spell it out in full :-).
--
Creamy
On Fri, Mar 22, 2013 at 12:29:19PM +0100, Stefan Sperling wrote:
> On Fri, Mar 22, 2013 at 09:55:01AM +0000, 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
> &g
l locales as and when a significant number
of translations exist in ports, as it gives people an incentive to translate
in to their local language.
--
Creamy
; 0) ||
- ((cmoscentury == 19) && (clockcentury == 20) &&
-(clockyear == 2000))) {
+ ((cmoscentury == 19) && (clockcentury == 20))) {
printf("WARNING: Setting NVRAM century to %d\n",
clockcentury);
s = splclock();
--
Creamy
be nice to define all this somewhere in the
keyboard map, but I don't know if other people might consider it to be
unnecessarily bloating things, because the existing system works well
enough for most users, (who don't have loads of extra keys, ha! ha! ha!).
--
Creamy
if (kp->group1[0] == KS_Repeat && type==WSCONS_EVENT_KEY_UP)
+ {
+ sc->sc_keyrepeat_data = wskbd_store_keyrepeat_data;
+ }
/* Now update modifiers */
switch (kp->group1[0]) {
--
Creamy
On Wed, Mar 20, 2013 at 09:21:10AM +0100, Otto Moerbeek wrote:
> On Wed, Mar 20, 2013 at 12:43:37AM +0000, 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
> &g
me and I'll happily go back to
working in isolation from the rest 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
nywhere near me. No closed
source system is an "enterprise (WAN) solution", by definition.
I basically have fears that this discussion is going to lead to people
trying to write something like an IMAP client using a shell script and
netcat. It would never work 100%, and us expending effort to make it
work 99% of the time just hurts the users who are stuck with the 1% of
failiures.
--
Creamy
kind of balony.
Then make 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
c, on a LAN.
Exactly - it's useful on a LAN where you're in control of both client
and server 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
user can change the
values for all of the VCs. Great.
--
Creamy
.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
st others do not,
we need some way to handle this if it's eventually going to be in the
main tree.
I am happy to produce the patch making a submap for 122 key terminal
keyboards, but how would you like it done exactly?
--
Creamy
to the NVRAM if
(cmoscentury == 19) && (clockcentury == 20) ?
--
Creamy
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 @@
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 */
#d
lementing this in X? I notice 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
49 matches
Mail list logo
