On 2017-05-15 Mon 02:50, Theo de Raadt wrote:
> ...
> This system is intentionally simple, to create robustness via simplicity.
>
> I think you are being critical because you think it is amusing.
>
(please not that the subject is still "syspatch ideas")
Syspatch infrastructure itself is
On 2017-05-15 Mon 08:19, Michal Bozon wrote:
> > > ...
> > ...
> ...
> Reverting the last patchset would be reverting the patches from the last
> patchset file, and removing that file.
>
correction/addition: in the reverse order
On 2017-05-15 Mon 02:23, Theo de Raadt wrote:
> >On 2017-05-15 Mon 01:31, Theo de Raadt wrote:
> >> >2) Notion of transactions
> >> >
> >> >Often, more patches are installed at once, with the single `syspatch`
> >> >command. One might want to be able to revert all those patches at once
> >> >as
On 2017-05-15 Mon 01:31, Theo de Raadt wrote:
> >2) Notion of transactions
> >
> >Often, more patches are installed at once, with the single `syspatch`
> >command. One might want to be able to revert all those patches at once
> >as well. A notion of transactions could be made by adding a notion
>
port for -r optional argument, which could be comma separated
patch number list.
(And this optional argument support would be also nice for the proposed -L
option)
thanks for very handy feature,
Michal Bozon
On 2017-04-14 Fri 13:28, "misc nick" wrote:
> This e-mail is complementary to the one i sent at dm...@openbsd.org.
>
> After the completion of the installation process, everything works except:
>
> -screen brightness controlled by the keyboard
> -suspend/resume when i close the lid
>
> Both
The comment for the mentioned patch reversion was:
the map-to-lowercase scheme for msdos is not going to work, because other
filesystems can contain mixed case files (ie. sgi).
discussed with krw and halex
which makes not much sense for me, because the fix was a conditional treatment
for
is used, maybe it fixed some problem,
but it has introduced another one.
MB
On 2017-05-10 Wed 12:34, Michal Bozon wrote:
> Hi,
> there is a typo in install.sub
> causing problems e.g. when removable FAT32 formatted
> disk with installation files is attached,
> and "disk" i
_opts="-s"
-mount -o ro,$_opts /dev/$_dev$resp /mnt2
+mount -o ro $_opts /dev/$_dev$resp /mnt2
}
regards,
Michal Bozon
if someone's interested, here a list of fs differences
between 6.0 upgraded from 5.9, and 6.0 install, i found,
with some obvious differences like smtpd spool or sysmerge
backups removed (amd64/qemu):
http://pastebin.com/raw/VPkdbvxy (text/plain)
(not pasting because of long lines)
hth
> > good(?) news: sysmerge is gone in 6.0
> > but not removed by 5.9 to 6.0 uprade process.
> >
>
> I really have a hard time understanding what you're trying to point out.
>
> Yes, systrace is gone, but it's an ordinary binary that does no harm,
> feel free to remove it if it makes you feel
> good(?) news: sysmerge is gone in 6.0
> but not removed by 5.9 to 6.0 uprade process.
s/sysmerge/systrace/
> Why?
good(?) news: sysmerge is gone in 6.0
but not removed by 5.9 to 6.0 uprade process.
> -With twitchy fingers on flashing keys
> +Twitchy fingers, flashing keys
>
> -always claiming "it was just a prank!"
> +Claiming "it was just a prank!"
hi, this time (60c), i hear this:
Money, donate your pay.
Automate with a cron job and we'll be ok.
+Money, donate your pay.
Thoughtful
> Even adding "debug" keyword did not assure me
> whether the problem is with my password definition:
> wpakey s3cur3-as-#311, for illustration (was not sure
> if the '#' has to be escaped somehow); or somewhere
> else. Finally, it was the latter, but it took me a while
> to realize that.
.. or
Theo de Raadt wrote:
> > > As i said, my config with # in the password worked
> > > without any escaping or quoting needed.
> > >
> >
> > i understood from your mail that you'd had to escape it.
>
> that is correct.
...
now i'm jealous, i want to be able to read other
people's thoughts too.
> On Mon, Aug 08, 2016 at 10:23:22AM +0200, Michal Bozon wrote:
> > Hi, I've had an issue connecting to a wireless network
> > (by doas sh /etc/netstart $if). Its password contained
> > '#' character(s).
> >
> > Even adding "debug" keyword did not a
Hi, this also bugs me. But ksh is not bash. Try hitting ESC
before an arrow. (I'm not sure if it is a consistent keystroke
behavior of ksh or not)
Here's one of older threads to this:
https://marc.info/?t=12126533981=1=2
regards,
Michal Bozon
Dave Cohen wrote:
...
I'll try to describe
Hi, I've had an issue connecting to a wireless network
(by doas sh /etc/netstart $if). Its password contained
'#' character(s).
Even adding "debug" keyword did not assure me
whether the problem is with my password definition:
wpakey s3cur3-as-#311, for illustration (was not sure
if the '#' has to
this is what i hear:
-With twitchy fingers on flashing keys
+Twitchy fingers, flashing keys
-always claiming "it was just a prank!"
+Claiming "it was just a prank!"
regards,
michal bozon
On 2015-10-08 Thu 16:33, Aaron Poffenberger wrote:
> On 10/08/15 16:13, ian kremlin wrote:
> >Hello
> >
> >Syracuse, NY -- no CD, but poster has arrived. looks great!
> >
> >http://ce.gl/openbsd-5.8-poster.jpg
> >
> >ian
> >
> >On Wed, Oct 7, 2015 at 10:51 AM, M Wheeler <6f84c...@refn.co.uk>
> ...
> Michael
>
you have won!
>
> --- /usr/src/games/factor/factor.c Wed Oct 28 00:59:24 2009
> +++ factor.cTue Sep 8 20:06:44 2015
> @@ -192,6 +192,19 @@ pr_fact(u_int64_t val) /* Factor this value.
> */
> (void)putchar('\n');
> }
>
> +static u_int32_t
>
.. i was wondering before, why *bin/factor is in games, now i get it.
Very nice observation!
Another factor game fake primes:
18446744073709551503 == 2^64 - 113 == 119026343 * 154980348121
18446744073709551499 == 2^64 - 117 == 363269 * 50779846542671
18446744073709551491 == 2^64 - 125 ==
there's more..
* worst case is 18446744030759878681, which is
previous_prime(sqrt(2^64))^2, which is
4294967291^2
* _smallest_ OpenBSD composite prime seems to be 4295360521,
which is 65539^2
Michal Bozon
24 matches
Mail list logo
