On Fri, Sep 02, 2016 at 01:57:21PM +0300, Paul Irofti wrote:
> Hi,
>
> While reinstalling OpenBSD on the x260 I saw a weird message when
> selecting the disk (that had a valid MBR)
>
> 'No valid MBR or GPT'
>
> which lead to the following installer diff.
>
> The idea is to do two checks
On Wed, Aug 31, 2016 at 01:53:30PM +0100, Theo Buehler wrote:
> On Wed, Aug 31, 2016 at 08:39:51AM -0400, Ted Unangst wrote:
> > About ten times a day I do something like this:
> > $ cd cd tedu
> > ksh: cd: bad substitution
> >
> > What does that even mean? According to the source, but not the
On Sat, Sep 10, 2016 at 01:46:05PM -0700, Philip Guenther wrote:
> On Sat, 10 Sep 2016, Martin Natano wrote:
> > When building with noperm the symlinks end up with the build user as
> > owner instead of root. Ok?
> ...
> > --- bin/chmod/Makefile 6 Sep 2001 18:52:55 - 1.7
> > +++
On January 11, 2017 1:21:30 PM GMT+01:00, Theo Buehler
wrote:
>On Wed, Jan 11, 2017 at 01:10:12PM +0100, Theo Buehler wrote:
>> On Wed, Jan 11, 2017 at 11:52:02AM +, Pedro Caetano wrote:
>> > Hi tech@
>> >
>> > I was running an headless installation via serial using
On January 11, 2017 7:36:00 PM GMT+01:00, Theo Buehler
wrote:
>> OK halex@, who would also accept a stricter regular expression in the
>sed command.
>>
>
>Alright, here's a stricter regular expression. Should I add "
>ftp.openbsd.org$"
>to it or is this good enough?
I
What's the point of installing over https if you don't care about validating
the cert?
On January 5, 2017 12:24:11 PM GMT+01:00, RD Thrush
wrote:
>Rather than add load to the OpenBSD snapshot servers, for years I
>download a snapshot to a local netgear nas server. With
On January 5, 2017 11:10:06 PM GMT+01:00, Alexander Hall <alexan...@beard.se>
wrote:
>What's the point of installing over https if you don't care about
>validating the cert?
Oh, I read too fast. Please disregard.
/Alexander
>
>On January 5, 2017 12:24:11 PM GMT+01:00
On June 25, 2017 2:06:20 PM GMT+02:00, Job Snijders wrote:
>Dear team,
>
>This patch adds a -v option to cp(1) for more verbose output.
>
> $ touch a b; mkdir c
> $ cp -v a b c
> 'a' -> 'c/a'
> 'b' -> 'c/b'
> $ cp -rv c d
> 'c' -> 'd/'
>
Yeah, I use the nowrap or so plugin. When enabled, however, you will need to
manually line break your textual lines.
/Alexander
On May 31, 2017 11:20:52 PM GMT+02:00, Edgar Pettijohn
wrote:
>Will do. Seems like Thunderbird messes then up sometimes.
>
>Sent from
On November 9, 2017 7:02:54 PM GMT+01:00, Robert Peichaer
wrote:
>On Wed, Nov 08, 2017 at 10:47:43PM +0100, Holger Mikolon wrote:
>> The veriable $HN_DIR is set in /etc/netstart on line 166 but used
>only
>> once (line 78). The diff below makes use of $HN_DIR in the other
On 06/06/18 13:50, Todd C. Miller wrote:
> On Tue, 05 Jun 2018 16:29:33 -0600, "Theo de Raadt" wrote:
>
>>> + clearstr = "\033[H\033[J";
>>
>> I abhor increasing assumptions that the terminal honours that particular
>> ANSI standard.
>>
>> Sorry, but at that point you have
t;
>Todd C. Miller(todd.mil...@sudo.ws) on 2018.06.16 06:37:03 -0600:
>> On Tue, 12 Jun 2018 02:35:57 +0200, Alexander Hall wrote:
>>
>> > The diff below uses system(3) to call /usr/bin/clear, fiddling with
>
>> > *env() to make sure the current TERM value is propag
On June 18, 2018 11:00:00 PM GMT+02:00, Richard Procter
wrote:
>
>On 6/06/2018, at 10:20 AM, Alexander Hall wrote:
>
>> This adds a "clear-screen" editing command to the emacs editing mode.
>> This is the same name as bash and zsh uses, and then I stoppe
I'm currently on vacation with very limited ability to test, but I do approve
of this way.
/Alexander
On June 17, 2018 5:00:17 PM GMT+02:00, "Todd C. Miller"
wrote:
>On Sat, 16 Jun 2018 16:16:57 -0600, "Todd C. Miller" wrote:
>
>> On Sat, 16 Jun 2018 14:50:40 +0200, Mark Kettenis wrote:
>>
This adds a "clear-screen" editing command to the emacs editing mode.
This is the same name as bash and zsh uses, and then I stopped looking.
The default binding of 'redraw' remains for ^L, for now anyway, so
you'll need to run
$ bind ^L=clear-screen"
when testing.
$CLEARSTR can be set to an
I'm OK with this.
/Alexander
On October 23, 2017 3:29:57 PM GMT+02:00, Raf Czlonka
wrote:
>What say you?
>
>On Tue, Aug 29, 2017 at 08:44:43PM BST, Raf Czlonka wrote:
>> Ping.
>>
>> Anyone?
>>
>> On Sun, Jul 16, 2017 at 01:43:32PM BST, Raf Czlonka wrote:
>> > Hi all,
>>
On December 22, 2017 11:21:12 PM GMT+01:00, Stuart Henderson
wrote:
>On 2017/12/22 19:47, Nicholas Marriott wrote:
>> I don't think we should bring ! back.
>>
>> I wanted to remove v and | (and some other stuff) shortly afterwards,
>but
>> several people objected.
>>
>>
Didn't test, but reads ok to me, with minor nit below.
On January 11, 2018 9:25:10 PM GMT+01:00, Theo Buehler
wrote:
>This aligns all cases vertically which makes them easier to find.
>
>Normalize all cases: if the long form is illegal or unsupported,
>'goto fmt_broken;',
On January 12, 2018 7:26:58 AM GMT+01:00, Theo Buehler
wrote:
>> >+ case 'd':
>> >+ case 'i':
>> >intdata = true;
>> >break;
>> >+ case 'o':
>> >+ case 'u':
>> >+ case 'x':
>> >+
On February 18, 2018 6:37:52 PM GMT+01:00, Robert Peichaer
wrote:
>On Sun, Feb 18, 2018 at 12:36:43PM +0100, Klemens Nanni wrote:
>> On Tue, Nov 21, 2017 at 08:30:25PM +0100, Klemens Nanni wrote:
>> > On Sun, Nov 12, 2017 at 10:43:46PM +0100, Klemens Nanni wrote:
>> > > On
On August 15, 2018 4:27:24 PM GMT+02:00, Scott Cheloha
wrote:
>Use dprintf for the DEFAULT_MESG string instead of the more awkward
>write+strlen combo.
>
>ok?
>
>--
>Scott Cheloha
>
>Index: sbin/nologin/nologin.c
>===
>RCS file:
On August 30, 2018 3:27:07 PM GMT+02:00, "Jiri B." wrote:
>Hi,
>
>if somebody would put into install.conf following line:
>
> URL to autopartitioning template for disklabel = /disklabel.template
>
>ftp would end in its prompt.
>
># ftp -Vo - /disklabel.template
Uh-oh... Don't mention hackers@ on tech@... (FWIW) :-)
/Alexander
On October 1, 2018 12:55:12 PM GMT+02:00, Reyk Floeter wrote:
>Hi Ori,
>
>On Sun, Sep 30, 2018 at 12:27:00PM -0700, Ori Bernstein wrote:
>> I've added support to vmd for external snapshots. That is,
>> snapshots that are derived
On December 6, 2020 8:13:26 PM GMT+01:00, Antoine Jacoutot
wrote:
>On Sun, Dec 06, 2020 at 05:20:31PM +, Stuart Henderson wrote:
>> On 2020/12/06 16:39, Otto Moerbeek wrote:
>> > On Sun, Dec 06, 2020 at 03:31:19PM +, SW wrote:
>> >
>> > > On 06/12/2020 14:32, Otto Moerbeek wrote:
>>
On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote:
> Hi Alexander,
>
> On Sun, Nov 15, 2020 at 10:22:32PM +0100, Alexander Hall wrote:
> | I googled for "POSIX find", and hit this:
> |
> | https://pubs.opengroup.org/onlinepubs/009695399/utilities/find.h
On November 17, 2020 1:11:42 PM GMT+01:00, Paul de Weerd
wrote:
>On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote:
>| On Mon, Nov 16, 2020 at 09:04:53AM +0100, Paul de Weerd wrote:
>| > Hi Alexander,
>| >
>| > On Sun, Nov 15, 2020 at 10:22:32PM +01
On Tue, Nov 17, 2020 at 01:11:42PM +0100, Paul de Weerd wrote:
> On Tue, Nov 17, 2020 at 01:06:05AM +0100, Alexander Hall wrote:
...
> | The more I read and think about it, I feel the original error message is
> | actually correct in that there is no terminating ";&
On Sun, Nov 15, 2020 at 07:19:07PM +0100, Paul de Weerd wrote:
> Hi all,
>
> It was pointed out to me off-list that I introduced a regression for
> the case that has '+' as one of its arguments, e.g.:
>
> [weerd@pom] $ find /var/empty -exec echo + {} +
> find: -exec: "+" should
The "... do done" variant has been frequently used by me, and seems to appear
at least three times in install.sub, so if this goes in, please scan the
scripts in our tree first, at least for trivial cases.
/Alexander
On July 2, 2021 8:20:44 PM GMT+02:00, "Todd C. Miller"
wrote:
>Currently,
On July 5, 2021 12:25:39 AM GMT+02:00, "Todd C. Miller"
wrote:
>On Sun, 04 Jul 2021 23:25:25 +0200, Alexander Hall wrote:
>
>> The "... do done" variant has been frequently used by me, and seems to appear
>> at least three times in install.sub, so if thi
On July 5, 2021 8:31:49 AM GMT+02:00, "Reuben ua Bríġ"
wrote:
>> Date: Sun, 4 Jul 2021 16:25:39 -0600
>> From: Todd C. Miller
>
>> let's just require a non-empty expression but still allow an empty
>> loop body.
>
>if i might suggest a slight variation, how about only requiring that
>at
On July 5, 2021 3:12:07 PM GMT+02:00, "Reuben ua Bríġ"
wrote:
>> Date: Mon, 5 Jul 2021 14:41:46 +0200
>> From: Alexander Hall
>
>> I don't really see what you win either.
>
>the point of todds diff is to fix the issue i raised:
>
> Subject: w
On July 5, 2021 3:08:27 PM GMT+02:00, Jeremie Courreges-Anglas
wrote:
>On Sun, Jul 04 2021, Todd C. Miller wrote:
>> On Sun, 04 Jul 2021 23:25:25 +0200, Alexander Hall wrote:
>>
>>> The "... do done" variant has been frequently used by me, and seems to
&g
If two files to be compared share the same inode, it should
be reasonable to consider them identical.
This gives a substantial speedup when comparing directory
structures with many hardlinked files, e.g. when using
rsnapshot for incremental backup.
Comments? OK?
/Alexander
Index: diffreg.c
Ping. Please don't be discouraged or scared just because it's a diff to ksh(1).
It really is rather simple.
Noone else ever ran into this ksh command line history search bug?
/Alexander
On September 14, 2021 12:17:22 AM GMT+02:00, Alexander Hall
wrote:
>in emacs search-history mode, ab
in emacs search-history mode, abort if ^@ is encountered
This has been bugging me for ages, and I finally realized it was me
accidentally pressing Ctrl+, rendering ^@ (a.k.a '\0' or NUL)
Easily tested with: Ctrl+R Ctrl+ ...
Minimal investigation, for reference:
bash: misbehaves in a slightly
ge
as a commit message, and probably elaborated way too little.
I'll start over with a new thread with more elaborative wording.
/Alexander
>
> On 18/09/2021, Alexander Hall wrote:
> > Ping. Please don't be discouraged or scared just because it's a diff to
> > ksh(1). It really is ra
Hi,
In ksh(1) emacs editing mode, the search-history editing command
(normally bound to ^R), is used for interactive searching through the
history of previously given commands.
While performing such a search, emitting a NUL character (i.e. '\0',
or ^@) adds said character to the search
On Tue, Sep 21, 2021 at 10:24:47PM +0200, Alexander Hall wrote:
> OK?
Unless someone finds a clever and horrible way of abusing this, I won't
be committing it pre-release.
Comments and/or OK's still appreciated though. :-)
/Alexander
On Mon, Oct 11, 2021 at 09:13:16AM -0500, Scott Cheloha wrote:
> On Sun, Oct 10, 2021 at 08:26:04PM -0400, gwes wrote:
> > On 10/10/21 5:03 PM, Scott Cheloha wrote:
> > > [...]
> > >
> > > If we want to have the unportable legacy syntax then it should work
> > > like other option arguments.
On Mon, Jan 17, 2022 at 02:23:52PM +, Klemens Nanni wrote:
> I keep doing `btrace -l | sort' to help myself searching for traces.
>
> Would it be worh making btrace sort the list of probes
> lexicographically in the first place or is there any value in seeing
> them sorted by id?
I believe
This diff makes ssh-askpass abort on ^C, like on ESC.
At times when ssh-askpass pops up behind the active window, or for some
reason is not visible, while at the same time stealing all input, ^C is
one of the "safe" key combinations that comes to my mind trying to
unlock whatever is locking up my
On Sun, Jul 03, 2022 at 09:59:21AM +, Klemens Nanni wrote:
> ...
> _ifs seems like idiomatic way in our shell code, i.e. assign function
> arguments to local variables, but $@ is a bit special.
>
> In fact, "$@" is `set -u' clean whereas "${_ifs[@]}" is not.
> netstart does not use `set -u',
On Sat, Jul 02, 2022 at 08:12:29PM +, Klemens Nanni wrote:
> On Sat, Jul 02, 2022 at 03:00:00PM +0200, Alexander Hall wrote:
> > On Thu, Jun 30, 2022 at 03:35:05PM +, Klemens Nanni wrote:
> > > On Tue, Dec 07, 2021 at 08:15:41PM +, Klemens Nanni wrote:
> >
On Thu, Jun 30, 2022 at 03:35:05PM +, Klemens Nanni wrote:
> On Tue, Dec 07, 2021 at 08:15:41PM +, Klemens Nanni wrote:
> > On Tue, Nov 23, 2021 at 01:17:14AM +, Klemens Nanni wrote:
> > > On Tue, Nov 16, 2021 at 11:09:40PM +, Klemens Nanni wrote:
> > > > Run on boot without
We currently do not explicitly set the value for Bflag. Since it's
a static variable it is initialized to 0, which just so conveniently
happen to match the default constant.
So, this is technically a no-op since the value of the initial constant
is 0 anyway, but I do not think we should not rely
On July 27, 2022 12:48:29 AM GMT+02:00, Andrew Hewus Fresh
wrote:
>On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
>> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wrote:
>> > On Sun, Jul 24, 2022 at 10:01:26AM -0600, Theo de Raadt wrote:
>> > > Jonathan
On July 27, 2022 11:06:39 AM GMT+02:00, Alexander Hall
wrote:
>On July 27, 2022 12:48:29 AM GMT+02:00, Andrew Hewus Fresh
> wrote:
>>On Sun, Jul 24, 2022 at 10:34:04AM -0700, Andrew Hewus Fresh wrote:
>>> On Sun, Jul 24, 2022 at 09:14:30AM -0700, Andrew Hewus Fresh wro
On July 27, 2022 3:47:56 PM GMT+02:00, Andrew Hewus Fresh
wrote:
>On Wed, Jul 27, 2022 at 11:06:39AM +0200, Alexander Hall wrote:
>> I think replacing '*' with '*([![:cntrl:]])' can be the droid your looking
>> for.
>
>As I was falling asleep last night I was trying to
I think this adds nothing. It already states your system will be restored to
its previous state, and so it will, as far as possible.
Actually, specifically external (USB) disks, are probably *not* properly
restored though...
/Alexander
On October 21, 2022 9:05:25 AM GMT+02:00, "Solène
On October 10, 2022 12:45:09 AM GMT+02:00, Klemens Nanni
wrote:
>On Wed, Oct 05, 2022 at 04:56:57PM +0200, Alexander Hall wrote:
>> While I dislike the ">/dev/null 2>&1" sledgehammer, this is in the right
>> direction.
>
>Agreed.
>
>We should
On October 5, 2022 12:57:44 AM GMT+02:00, Klemens Nanni
wrote:
>There is no problem to fix, but every boot I read "/clearing /tmp" and
>know it is a useless step since my /tmp live on volatile RAM anyway.
>
>Other steps in rc(8) also check and print/log conditionally, so this
>can do as well,
On October 4, 2022 10:11:46 PM GMT+02:00, Klemens Nanni
wrote:
>This function's style is a bit off: it wraps the body in a subshell to
>discard all stdout/err at once, but a still uses return inside it.
>
>1. A command list (using {}) would be enough here as it groups like a
> subshell but
On July 7, 2023 12:50:55 PM GMT+02:00, Stefan Sperling wrote:
>On Fri, Jul 07, 2023 at 12:26:16PM +0200, Tobias Heider wrote:
>> For bigger changesets I have started experimenting with using got.
>> I don't like to have the whole tree on disk twice so I keep my got and CVS
>> checkouts in the
201 - 254 of 254 matches
Mail list logo