Re: What is you motivational to use OpenBSD
OpenBSD community is formed around the idea of doing things in a simple but correct manner; the community also rejects all stupid ideas that many others may accept because it is a bit more convenient. That's a good community to learn from. A community that got a good taste for sensible ideas. On Wed, 28 Aug 2019, 11:42 Mohamed salah I wanna put something in discussion, what's your motivational to use > OPENBSD what not other bsd's what not gnu/Linux, if something doesn't work > fine on openbsd and you love this os so much what will do? >
Re: SCM
fossil is interesting! what - if anything - you don't like about it Roderick? On Mon, 29 Jul 2019, 8:51 am Roderick > On Sun, 28 Jul 2019, Nathan Hartman wrote: > > > *IF* the OpenBSD devs ever wants to change SCMs--I said **IF**--then I > > root for Subversion. Subversion offers the following advantages: > > If wants to change just for changing, then there are reasons to select > something else? I realy do not understand this logic that drives this > discussion. > > What I like of CVS: rcs textfiles, transparency, no strange db. That > is a reason for which I would decide for CVS and nothing else for a > bigger project. > > I use fossil for my small programs, better said, misuse, because I > do not use it as a real SCM, but just for backuping history. And I > like it very much. > > Rodrigo > >
Re: ed(1) man page doesn't mention use of single / and ?
I wouldn't say it is particularly wonderful but it is whats out there! However, Michael W. Lucas(the author) do have awesome books. On Fri, Jul 5, 2019 at 8:26 PM Vincent Waciuk wrote: > Ed Mastery is a wonderful read. Highly recommended. >
Re: ed(1) man page doesn't mention use of single / and ?
To add to Ian's reference. "Ed Mastery" is the only book I know specific to ed(1). Mo On Thu, 4 Jul 2019, 6:54 pm ropers Do I understand correctly that this is in reference to these parts of man > 1 ed: > > > /re/ > >The next line containing the regular expression re. The search wraps > to the beginning of the buffer and continues down to the current line, if > necessary. “//” repeats the last search. > > > ?re? > >The previous line containing the regular expression re. The search > wraps to the end of the buffer and continues up to the current line, if > necessary. “??” repeats the last search. > > and: > > > (1,$)g/re/command-list > >Applies command-list to each of the addressed lines matching a > regular expression re. The current address is set to the line currently > matched before command-list is executed. At the end of the g command, the > current address is set to the last line affected by command-list. If no > lines were matched, the current line number remains unchanged. > > > >Each command in command-list must be on a separate line, and every > line except for the last must be terminated by a backslash (‘\’). Any > commands are allowed, except for g, G, v, and V. A newline alone in > command-list is equivalent to a p command. > > > If yes, then the corresponding parts of ed.1 are: > > .It / Ns Ar re Ns / > The next line containing the regular expression > .Ar re . > The search wraps to the beginning of the buffer and continues down to the > current line, if necessary. > .Qq // > repeats the last search. > .It Pf ? Ar re ? > The previous line containing the regular expression > .Ar re . > The search wraps to the end of the buffer and continues up to the > current line, if necessary. > .Qq ?? > repeats the last search. > > and: > > .It Xo > .Pf (1,$) Ic g No / > .Ar re No / Ar command-list > .Xc > .Sm on > Applies > .Ar command-list > to each of the addressed lines matching a regular expression > .Ar re . > The current address is set to the line currently matched before > command-list is executed. > At the end of the > .Ic g > command, the current address is set to the last line affected by > command-list. > If no lines were matched, > the current line number remains unchanged. > .Pp > Each command in > .Ar command-list > must be on a separate line, > and every line except for the last must be terminated by a backslash > .Pq Sq \e . > Any commands are allowed, except for > .Ic g , > .Ic G , > .Ic v , > and > .Ic V . > A newline alone in command-list is equivalent to a > .Ic p > command. > .Sm off > > I'm not actually sure how to rewrite that. Would this call for > separate /re, ?re and (1,$)g/re entries, or would it suffice to say > that the second question mark or slash can be omitted if immediately > followed by a newline? > > Does anyone else have any ideas? > > NB: In case people haven't seen it, here's an excellent ed(1) > tutorial: https://sanctum.geek.nz/arabesque/actually-using-ed/ > I just thought I'd mention that. > > Ian > > On 03/07/2019, mazoc...@disroot.org wrote: > > Hi! > > > > I am not good at explaining something shortly and clearly to fit into > > proper documentation, so I'll just describe my experience here. > > > > Terminating regular expressions with / or ? is necessary only if they > > are followed by commands, otherwise the following are legal in both > > OpenBSD ed, Plan 9 ed and GNU ed: > > /something > > / > > ? > > g/ing > > > > I hope I made life of many ed users easier :) > > > > > >
Re: When will be created a great desktop experience for OpenBSD?
if you are suggesting updating the openbsd installer to include dwm as an option. Even that it adds one more click to the installation process, it would work as a sharm for some people :P On Tue, 7 May 2019, 2:04 am Clark Block In 2019 still there is not a great desktop experience for NetBSD. However, > the new "OS108" is seeking to improve this with a NetBSD operating system > paired with the MATE desktop environment. > So, OS108, a derivative of NetBSD, has just been released: > https://os108.org/?ez_cid=CLIENT_ID(AMP_ECID_EZOIC) > > When will be created a great desktop experience for OpenBSD? >
Re: dmenu: was When will be created a great desktop experience for OpenBSD?
works like a sharm On Tue, 7 May 2019, 6:14 pm Sean Howard I compiled dwm and dmenu directly and then just wrote an xinitrc, no > adjustments necessary to be functional > > On Tue, May 7, 2019, 16:42 Steve Litt wrote: > > > On Tue, 07 May 2019 14:47:15 -0500 > > Edgar Pettijohn wrote: > > > > > > > I use dwm on everything so my desktop experience is the same > > > everywhere. > > > > Just the man I want to talk to. > > > > Do you have dmenu running on OpenBSD? Did you need to make adjustments > > for ksh instead of sh or any other property of OpenBSD? > > > > Thanks, > > > > SteveT > > > > >
Re: Need an advice: Raspberry Pi3 B+ or Pine64 ROCK64
Hi Carlos, i have a similar requirement and i am considering testing a banana pi router at this moment. On Sun, 26 Aug 2018, 11:30 am Carlos López, wrote: > Hi all, > > I am considering to buy an ARM based device to use it with OpenBSD as > a personal/portable firewall, IDS and Tor gateway. > > My only requirements are: > > a/ OpenBSD well hardware's supported > b/ Best network throughput > > It seems Raspberry 3 B+ maybe the best option, but I am not pretty sure. > > Any advice? > > -- > Greetings, > C. L. Martinez > >
Re: Daily insecurity output on valid users using key with valid shell and without password.
Set VERBOSESTATUS to 0 in /etc/daily.local Source: absolute openbsd 2nd edition, chapter 15 "System Maintenance" Havent done it myself but I hope its a good clue! On Sun, 1 Jul 2018, 8:47 pm Remco, wrote: > Op 07/01/18 om 19:22 schreef Daniel Ouellet: > > I find this annoying and sometime I over look this because I always get > > the example: > > > > == > > Running security(8): > > > > Checking the /etc/master.passwd file: > > Login share is off but still has a valid shell and alternate access > files in > >home directory are still readable. > > Login xxx is off but still has a valid shell and alternate access files > in > >home directory are still readable. > > = > > > > Is there a better or different way to do this? > > > > I always disable the login password on users with * oppose to password > > in the master.passwd file after keys are installed as I DO NOT want to > > allow login password when ssh keys are use, but still get the above > > warning daily on multiples servers & users. > > > > The Running security(8): is nice as you see possible changes done by sys > > admin and you get the feedback, but getting daily warning for the same > > things sometime will get overlook because of noise. > > > > Is there a better way to disable login and not get these warning for ssh > > key users and keep the valid idea and use of the cronjob as is? > > > > Daniel > > > > > > I think you need to use 13 asterisks for the password, passwd(5) has a > brief mentioning of this. > >
