Re: rcs mandoc nits
On Sun, Aug 11, 2013 at 09:41:42PM +0200, Jan Stary wrote: This is small diff to the manpages in /usr/src/usr.bin/rcs What is the advantage of using '\*(Lt' instead of '' ? Is that advantage also valid for things like \*(Ltstdio.h\*(Gt ? All the other ''s and ''s are typed literally ... Jan the Lt/Gt was used originally because there was some concern that a) groff would interpret these at html markers and b) that groff would try some mathematical shenanigans with registers. i'm pretty sure the html thing is no longer an issue, but less sure about how it interprets in macros. if we could determine that it isn;t an issue for sure, we could look at diffs for removing this stuff. jmc Index: ci.1 === RCS file: /cvs/src/usr.bin/rcs/ci.1,v retrieving revision 1.37 diff -u -p -u -p -r1.37 ci.1 --- ci.1 14 Jul 2011 16:31:34 - 1.37 +++ ci.1 11 Aug 2013 19:35:57 - @@ -133,7 +133,7 @@ Check in revision .Ar rev . However, if .Ar rev -is not specified the meaning is completely different \- override any +is not specified the meaning is completely different \(en override any .Fl l or .Fl u Index: ident.1 === RCS file: /cvs/src/usr.bin/rcs/ident.1,v retrieving revision 1.12 diff -u -p -u -p -r1.12 ident.1 --- ident.1 29 Jun 2013 09:08:41 - 1.12 +++ ident.1 11 Aug 2013 19:35:57 - @@ -27,7 +27,7 @@ .Sh DESCRIPTION The .Nm -program searches for the pattern $keyword:... $ from the +program searches for the pattern $keyword: ... $ from the .Ar files specified as argument (or standard input if none are given). See the KEYWORD SUBSTITUTION section of @@ -35,7 +35,7 @@ See the KEYWORD SUBSTITUTION section of for more information. .Pp The following options are supported: -.Bl -tag -width XXX +.Bl -tag -width Ds .It Fl q Quiet mode: suppress warnings if no pattern found. .It Fl V @@ -47,7 +47,7 @@ Display version information and exit. Given the following source code in file .Pa foo.c : .Bd -literal -offset indent -#include \*(Ltstdio.h\*(Gt +#include stdio.h static char const rcsid[] = $\Id: foo.c,v 1.2 2005/11/18 09:34:51 xsa Exp $; Index: rlog.1 === RCS file: /cvs/src/usr.bin/rcs/rlog.1,v retrieving revision 1.24 diff -u -p -u -p -r1.24 rlog.1 --- rlog.13 Sep 2010 11:09:29 - 1.24 +++ rlog.111 Aug 2013 19:35:57 - @@ -69,9 +69,9 @@ Select the latest revision before or equ .El .Pp The -.Sq \*(Gt +.Sq and -.Sq \*(Lt +.Sq characters can be followed by the .Sq = character to imply an inclusive specification.
Re: yacc(1) LALR reference
On Sun, Aug 11, 2013 at 11:01:44PM +0200, Jan Stary wrote: This diff to yacc(1) adds a reference to the original LALR(1) paper. I am not sure about the markup, as mandoc render it as F. DeRemer and T. J. Pennello, Efficient Computation of LALR(1) Look-Ahead Sets, 4, TOPLAS, 4, 615-649, 1982. Note the order: issue number, journal name, volume number. Is that expected? Should I just make it issue 4:4? This includes my previous diff to the LALR markup. Jan i would just use %A, %D, %T, and %J myself. jmc Index: yacc.1 === RCS file: /cvs/src/usr.bin/yacc/yacc.1,v retrieving revision 1.26 diff -u -p -u -p -r1.26 yacc.1 --- yacc.118 Oct 2010 14:42:16 - 1.26 +++ yacc.111 Aug 2013 20:58:21 - @@ -37,9 +37,7 @@ .Os .Sh NAME .Nm yacc -.Nd an -.Tn LALR(1) -parser generator +.Nd an LALR(1) parser generator .Sh SYNOPSIS .Nm yacc .Op Fl dlrtv @@ -51,11 +49,8 @@ parser generator .Nm reads the grammar specification in .Ar file -and generates an -.Tn LR(1) -parser for it. -The parsers consist of a set of -.Tn LALR(1) +and generates an LR(1) parser for it. +The parsers consist of a set of LALR(1) parsing tables and a driver routine written in the C programming language. .Nm @@ -176,12 +171,21 @@ is defined and non-zero. .Sh DIAGNOSTICS If there are rules that are never reduced, the number of such rules is written to the standard error. -If there are any -.Tn LALR(1) +If there are any LALR(1) conflicts, the number of conflicts is also written to the standard error. .Sh SEE ALSO .Xr yyfix 1 +.Rs +.%A F. DeRemer +.%A T. J. Pennello +.%T Efficient Computation of LALR(1) Look-Ahead Sets +.%J TOPLAS +.%V 4 +.%I 4 +.%D 1982 +.%P 615-649 +.Re .Sh STANDARDS The .Nm
Re: yacc(1) mandoc nits
On Sun, Aug 11, 2013 at 10:49:27PM +0200, Jan Stary wrote: Tha yacc(1) manpage uses .Tn LALR(1) .Tn LR(1) I don't think LALR or LR is a tradename. This seems to be what mdoc(7) describes as: Since this macro is often implemented to use a small caps font, it has historically been used for acronyms (like ASCII) as well. Such usage is not recommended because it would use the same macro sometimes for semantical annotation, sometimes for physical formatting. So would it be better to just say LALR(1) without any markup, just as we say e.g. BNF? Jan yes, Tn gets abused horribly. however it's everwhere, so i wouldn;t want to tackle it in a single page. we would have to decide where exactly it makes sense (never, as far as i'm concerned), then do it everywhere consistently. jmc Index: yacc.1 === RCS file: /cvs/src/usr.bin/yacc/yacc.1,v retrieving revision 1.26 diff -u -p -r1.26 yacc.1 --- yacc.118 Oct 2010 14:42:16 - 1.26 +++ yacc.111 Aug 2013 20:48:37 - @@ -37,9 +37,7 @@ .Os .Sh NAME .Nm yacc -.Nd an -.Tn LALR(1) -parser generator +.Nd an LALR(1) parser generator .Sh SYNOPSIS .Nm yacc .Op Fl dlrtv @@ -51,11 +49,8 @@ parser generator .Nm reads the grammar specification in .Ar file -and generates an -.Tn LR(1) -parser for it. -The parsers consist of a set of -.Tn LALR(1) +and generates an LR(1) parser for it. +The parsers consist of a set of LALR(1) parsing tables and a driver routine written in the C programming language. .Nm @@ -176,8 +171,7 @@ is defined and non-zero. .Sh DIAGNOSTICS If there are rules that are never reduced, the number of such rules is written to the standard error. -If there are any -.Tn LALR(1) +If there are any LALR(1) conflicts, the number of conflicts is also written to the standard error. .Sh SEE ALSO
Re: Network appliance recomendation.
I would recommend http://www.mini-itx.com/ and a cheap four port ethernet card. I just did a quick look around google and it looks like all of the four port 100mb cards are pci-x. You also will need a pci riser like here for example http://www.wiredzone.com/Supermicro-RSCR1UUE4R-1U,-UIO-Right-Side-Riser-Card~10022708~0.htm After all that you would have a good working system. But then again after adding up all the parts cost and your time you may still want to go with a vender who builds for you :( Unless you really don't find one. Then this is your choice. Evan Root, CCNA 505.226.1319 On Sat, Aug 10, 2013 at 10:09 PM, Francisco Valladolid H. fic...@gmail.comwrote: On Sat, Aug 10, 2013 at 5:15 PM, Paul de Weerd we...@weirdnet.nl wrote: On Sat, Aug 10, 2013 at 08:09:02PM +, Stuart Henderson wrote: | These can be hard to get via the usual axiomtek reseller channels, but these are | the same thing with a different front plate: | | https://shop.bytemine.net/startseitenprodukte/bytemine-openbsd-appliance-6a16e.html | https://shop.bytemine.net/startseitenprodukte/bytemine-appliance-6a16er.html I have the 6a16e (i.e. the non-rackmountable version) and have been very happy with it. Highly recommmend it! Thank you Paul. This model is very expensive plus the shipping and import duties to Mexico.. Regards Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ -- Francisco Valladolid H. -- http://blog.bsdguy.net - Jesus Christ follower.
Re: Don't read this - OpenBSD: Not Free Not Fuctional and Definetly Not Secure | BSD, the truth - as author rewrites your comments and can't spell
On Sat, 10 Aug 2013 17:51:43 +0100 Kaya Saman wrote: I think it's much harder to learn since the documentation is more 'sparse' and also much more limited in certain areas kernel PPP daemon for example :-) - it took me a while to figure out how to get PPPoE working. Well I agree and disagree here. It is harder to set up though quicker, possibly to keep average users and their demands from tying up the limited resources OpenBSD has to do things right but is actually easier in many respects too, especially to get secure setups. Kernel ppp may be one of the only examples on OpenBSD where the docs may not be as complete and in one location (interface setup too) as they could be partly because you normally just run it and it does the job and you have just happened to have hit this one example early on in your usage. The userland ppp requires and has a lot of documentation but lacks the performance. In fact I have only recently begun to fully understand why the pkg system supports signing packages but it is only usable by users and not used on the provided packages. I believe it is because a build system is actually very difficult to secure and a system that builds everything all day everyday is quite likely to give a false sense of security (though still be secure enough for the majority), if you require this level of security you better think twice focus in and sign yourself. On a whole good OpenBSD documentation is one of OpenBSD's aims and it shows possibly but only partly because OpenBSD is made by the users for the users. I rarely have to resort to often incorrect websites or download configs on OpenBSD (sudoers, ssh, login.conf, rc.conf, openssl) and everything such as configs are always in a sane often single and logical place. This is the opposite atleast with RedHat technologies where the man pages could be called summaries rather than manuals e.g. Polkit, udev (last_action, events), PAM leading to accusations of them ignoring users and wanting to bolster enterprise usage and support contracts and all over the place leading to uncertainty and lack of control and sometimes the usage of commandline tools other than text editors.
assorted mdoc(7) nits
Reading the shorter manpages in .../man1/ as an excercise while learning mdoc(7), I made this little diff of assorted typos, forgotten .Pas. missing .Mts and such. Index: sbin/newfs_ext2fs/newfs_ext2fs.8 === RCS file: /cvs/src/sbin/newfs_ext2fs/newfs_ext2fs.8,v retrieving revision 1.7 diff -u -p -u -p -r1.7 newfs_ext2fs.8 --- sbin/newfs_ext2fs/newfs_ext2fs.816 Jul 2013 09:45:28 - 1.7 +++ sbin/newfs_ext2fs/newfs_ext2fs.812 Aug 2013 09:50:03 - @@ -314,8 +314,7 @@ command first appeared in The .Nm command was written by -.An Izumi Tsutsui -.Aq Mt tsut...@netbsd.org . +.An Izumi Tsutsui Aq Mt tsut...@netbsd.org . .Sh BUGS The .Nm Index: sbin/scan_ffs/scan_ffs.8 === RCS file: /cvs/src/sbin/scan_ffs/scan_ffs.8,v retrieving revision 1.16 diff -u -p -u -p -r1.16 scan_ffs.8 --- sbin/scan_ffs/scan_ffs.823 Mar 2008 23:28:46 - 1.16 +++ sbin/scan_ffs/scan_ffs.812 Aug 2013 09:50:03 - @@ -23,7 +23,6 @@ .\ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\ -.\ .TH scan_ffs 8 .Dd $Mdocdate: March 23 2008 $ .Dt SCAN_FFS 8 .Os Index: share/man/man9/rssadapt.9 === RCS file: /cvs/src/share/man/man9/rssadapt.9,v retrieving revision 1.6 diff -u -p -u -p -r1.6 rssadapt.9 --- share/man/man9/rssadapt.9 17 Jul 2013 20:21:54 - 1.6 +++ share/man/man9/rssadapt.9 12 Aug 2013 09:50:05 - @@ -338,7 +338,7 @@ indications over past update intervals. This approximates the rate of packet-transmission. .Fa ra_rate_thresh contains RSS thresholds that are indexed by -.Aq packet length, data rate +.Aq packet length, data rate tuples. When this node's exponential-average RSS exceeds .Fa ra_rate_thresh[i][j] , Index: usr.bin/biff/biff.1 === RCS file: /cvs/src/usr.bin/biff/biff.1,v retrieving revision 1.17 diff -u -p -u -p -r1.17 biff.1 --- usr.bin/biff/biff.1 28 Apr 2013 08:13:09 - 1.17 +++ usr.bin/biff/biff.1 12 Aug 2013 09:50:13 - @@ -35,7 +35,7 @@ .Os .Sh NAME .Nm biff -.Nd be notified if mail arrives and who it is from +.Nd be notified if mail arrives and who it is from .Sh SYNOPSIS .Nm biff .Op Cm n | y Index: usr.bin/compress/gzexe.1 === RCS file: /cvs/src/usr.bin/compress/gzexe.1,v retrieving revision 1.5 diff -u -p -u -p -r1.5 gzexe.1 --- usr.bin/compress/gzexe.131 May 2007 19:20:08 - 1.5 +++ usr.bin/compress/gzexe.112 Aug 2013 09:50:13 - @@ -52,7 +52,10 @@ program refuses to compress non-regular files with a setuid or setgid bit set, files that are already compressed using .Nm , -files in /bin or /sbin, +files in +.Pa /bin +or +.Pa /sbin , or programs it needs to perform on-the-fly decompression: .Xr sh 1 , .Xr basename 1 , Index: usr.bin/from/from.1 === RCS file: /cvs/src/usr.bin/from/from.1,v retrieving revision 1.11 diff -u -p -u -p -r1.11 from.1 --- usr.bin/from/from.1 15 Jan 2012 20:06:40 - 1.11 +++ usr.bin/from/from.1 12 Aug 2013 09:50:14 - @@ -66,7 +66,7 @@ If .Ar user is given, the .Ar user Ns 's -mailbox, is examined instead of the invoker's own mailbox. +mailbox is examined instead of the invoker's own mailbox. (Privileges are required.) .Sh FILES .Bl -tag -width /var/mail/* -compact Index: usr.bin/pkill/pkill.1 === RCS file: /cvs/src/usr.bin/pkill/pkill.1,v retrieving revision 1.23 diff -u -p -u -p -r1.23 pkill.1 --- usr.bin/pkill/pkill.1 16 Jul 2013 00:07:52 - 1.23 +++ usr.bin/pkill/pkill.1 12 Aug 2013 09:50:15 - @@ -225,5 +225,4 @@ first appeared in They are modelled after utilities of the same name that appeared in Sun Solaris 7. .Sh AUTHORS -.An Andrew Doran -.Aq Mt a...@netbsd.org . +.An Andrew Doran Aq Mt a...@netbsd.org . Index: usr.bin/rcs/ci.1 === RCS file: /cvs/src/usr.bin/rcs/ci.1,v retrieving revision 1.37 diff -u -p -u -p -r1.37 ci.1 --- usr.bin/rcs/ci.114 Jul 2011 16:31:34 - 1.37 +++ usr.bin/rcs/ci.112 Aug 2013 09:50:15 - @@ -133,7 +133,7 @@ Check in revision .Ar rev . However, if .Ar rev -is not specified the meaning is completely different \- override any +is not specified the meaning is completely different \(en override any .Fl l or .Fl u Index: usr.bin/unvis/unvis.1 === RCS file: /cvs/src/usr.bin/unvis/unvis.1,v retrieving revision 1.7 diff -u -p -u -p -r1.7 unvis.1 --- usr.bin/unvis/unvis.1 16 Aug 2009 09:41:08 - 1.7 +++
Re: Weekly digest, Issue 1685 (81 messages)
On 2013-08-11, Damon Getsman damo.g...@gmail.com wrote: The solution was, indeed, dealing with creating a hardlink to somewhere within the chroot'ed jail; in this case under /var/www/var/run/mysql/mysql.sock after the appropriate path was created. Anyway I just thought that I'd post that here, since a lot of people in the OpenBSD community didn't seem to know how simple the solution really was or where it might be found at. It might be a good idea to toss this in the 4.x to 5.0 upgrade instructions, as well. It seems like a relatively simple oversight. I don't recall when it was added, but the package readme for mysql in recent versions of OpenBSD includes a section chrooted daemons and MySQL socket which shows you exactly how to do this. less +/chrooted /usr/local/share/doc/pkg-readmes/mysql*
.shrc vs ~/.shrc
This is what happens on 5.4-beta/i386 (and any other version I got my hands on): $ cd $ pwd /home/hans $ . .shrc /bin/ksh: .: .shrc: not found $ . ~/.shrc $ echo $SHELL /bin/ksh Why is it that ksh can find ~/.shrc and '.' it, but cannot find .shrc, which is the very same file? Jan
Re: .shrc vs ~/.shrc
$ . .shrc /bin/ksh: .: .shrc: not found $ . ~/.shrc $ echo $SHELL /bin/ksh Why is it that ksh can find ~/.shrc and '.' it, but cannot find .shrc, which is the very same file? Because '.' is not in your $PATH. Miod
Re: assorted mdoc(7) nits
On Mon, Aug 12, 2013 at 12:04:30PM +0200, Jan Stary wrote: Reading the shorter manpages in .../man1/ as an excercise while learning mdoc(7), I made this little diff of assorted typos, forgotten .Pas. missing .Mts and such. thanks for these. i've committed most, with some exceptions noted below... Index: sbin/newfs_ext2fs/newfs_ext2fs.8 === RCS file: /cvs/src/sbin/newfs_ext2fs/newfs_ext2fs.8,v retrieving revision 1.7 diff -u -p -u -p -r1.7 newfs_ext2fs.8 --- sbin/newfs_ext2fs/newfs_ext2fs.8 16 Jul 2013 09:45:28 - 1.7 +++ sbin/newfs_ext2fs/newfs_ext2fs.8 12 Aug 2013 09:50:03 - @@ -314,8 +314,7 @@ command first appeared in The .Nm command was written by -.An Izumi Tsutsui -.Aq Mt tsut...@netbsd.org . +.An Izumi Tsutsui Aq Mt tsut...@netbsd.org . .Sh BUGS The .Nm i think when the work was done to add Mt, ingo said that he didn;t consider examples like above as problematic, and wasn't going to change them. i don;t see any need either (it's not wrong, and it formats correctly). ditto the pkill diff. Index: sbin/scan_ffs/scan_ffs.8 === RCS file: /cvs/src/sbin/scan_ffs/scan_ffs.8,v retrieving revision 1.16 diff -u -p -u -p -r1.16 scan_ffs.8 --- sbin/scan_ffs/scan_ffs.8 23 Mar 2008 23:28:46 - 1.16 +++ sbin/scan_ffs/scan_ffs.8 12 Aug 2013 09:50:03 - @@ -23,7 +23,6 @@ .\ (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF .\ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. .\ -.\ .TH scan_ffs 8 .Dd $Mdocdate: March 23 2008 $ .Dt SCAN_FFS 8 .Os do you and .TH have history? ;) except for these, i committed the rest. jmc Index: share/man/man9/rssadapt.9 === RCS file: /cvs/src/share/man/man9/rssadapt.9,v retrieving revision 1.6 diff -u -p -u -p -r1.6 rssadapt.9 --- share/man/man9/rssadapt.9 17 Jul 2013 20:21:54 - 1.6 +++ share/man/man9/rssadapt.9 12 Aug 2013 09:50:05 - @@ -338,7 +338,7 @@ indications over past update intervals. This approximates the rate of packet-transmission. .Fa ra_rate_thresh contains RSS thresholds that are indexed by -.Aq packet length, data rate +.Aq packet length, data rate tuples. When this node's exponential-average RSS exceeds .Fa ra_rate_thresh[i][j] , Index: usr.bin/biff/biff.1 === RCS file: /cvs/src/usr.bin/biff/biff.1,v retrieving revision 1.17 diff -u -p -u -p -r1.17 biff.1 --- usr.bin/biff/biff.1 28 Apr 2013 08:13:09 - 1.17 +++ usr.bin/biff/biff.1 12 Aug 2013 09:50:13 - @@ -35,7 +35,7 @@ .Os .Sh NAME .Nm biff -.Nd be notified if mail arrives and who it is from +.Nd be notified if mail arrives and who it is from .Sh SYNOPSIS .Nm biff .Op Cm n | y Index: usr.bin/compress/gzexe.1 === RCS file: /cvs/src/usr.bin/compress/gzexe.1,v retrieving revision 1.5 diff -u -p -u -p -r1.5 gzexe.1 --- usr.bin/compress/gzexe.1 31 May 2007 19:20:08 - 1.5 +++ usr.bin/compress/gzexe.1 12 Aug 2013 09:50:13 - @@ -52,7 +52,10 @@ program refuses to compress non-regular files with a setuid or setgid bit set, files that are already compressed using .Nm , -files in /bin or /sbin, +files in +.Pa /bin +or +.Pa /sbin , or programs it needs to perform on-the-fly decompression: .Xr sh 1 , .Xr basename 1 , Index: usr.bin/from/from.1 === RCS file: /cvs/src/usr.bin/from/from.1,v retrieving revision 1.11 diff -u -p -u -p -r1.11 from.1 --- usr.bin/from/from.1 15 Jan 2012 20:06:40 - 1.11 +++ usr.bin/from/from.1 12 Aug 2013 09:50:14 - @@ -66,7 +66,7 @@ If .Ar user is given, the .Ar user Ns 's -mailbox, is examined instead of the invoker's own mailbox. +mailbox is examined instead of the invoker's own mailbox. (Privileges are required.) .Sh FILES .Bl -tag -width /var/mail/* -compact Index: usr.bin/pkill/pkill.1 === RCS file: /cvs/src/usr.bin/pkill/pkill.1,v retrieving revision 1.23 diff -u -p -u -p -r1.23 pkill.1 --- usr.bin/pkill/pkill.1 16 Jul 2013 00:07:52 - 1.23 +++ usr.bin/pkill/pkill.1 12 Aug 2013 09:50:15 - @@ -225,5 +225,4 @@ first appeared in They are modelled after utilities of the same name that appeared in Sun Solaris 7. .Sh AUTHORS -.An Andrew Doran -.Aq Mt a...@netbsd.org . +.An Andrew Doran Aq Mt a...@netbsd.org . Index: usr.bin/rcs/ci.1 === RCS file: /cvs/src/usr.bin/rcs/ci.1,v retrieving revision 1.37 diff -u -p -u -p -r1.37 ci.1 --- usr.bin/rcs/ci.1 14 Jul 2011 16:31:34
Re: poptop on OpenBSD 5.3
On Mon, 5 Aug 2013 14:46:20 -0600 Alvaro Mantilla Gimenez alv...@alvaromantilla.com wrote: Hi Wesley, Lo__c, Thanks for the advice. I didn't know about npppd. It seems an interesting option. I am going to try that. +1 for npppd, i wrote howto (in Serbian though) here: https://www.mimar.rs/npppd-novi-openbsd-ov-pptpl2tp-server/ Make sure to use latest snapshot, and not 5.3 release, as I experienced hangs: http://openbsd.7691.n7.nabble.com/Hang-possibly-related-to-pipex-td230816.html If you still want poptop for any reason, my working ppp.conf (with authentication from active directory implementation of radius) is as follows: loop: set timeout 0 set log phase chat connect lcp ipcp command TUN set device localhost:pptp set dial set login set mppe 128 stateful set ifaddr 192.168.131.1 192.168.131.10-192.168.131.250 255.255.255.255 set server /var/tmp/loop 0177 loop-in: set timeout 0 set log phase lcp ipcp command allow mode direct pptp: load loop disable pap disable chap enable mschapv2 set radius /etc/ppp/radius.conf disable deflate pred1 deny deflate pred1 disable ipv6cp disable ipv6 accept mppe enable proxy accept dns set dns 192.168.5.21 192.168.5.24 set device !/etc/ppp/secure You will also need file /etc/ppp/secure: #!/bin/sh exec /usr/sbin/ppp -direct loop-in Hope this helps. -- Marko Cupać
Install drivers
How can I force OBSD to install drivers, that are not needed on the running hardware? This may sound strange on a first sight, but in my situation I have OBSD on a flash drive that runs via flashrd from RAM and this RAM can be located in various (i386/ARM64) systems. I want to support as much hardware as possible 'out of the box' and since a network can't be assumed, I need to preinstall the drivers. --Josef
Re: Install drivers
On 08/11/2013 10:35 AM, josef.win...@email.de wrote: I want to support as much hardware as possible 'out of the box' and since a network can't be assumed, I need to preinstall the drivers. GENERIC supports as much hardware as possible 'out of the box.' -- Matthew Weigel hacker unique idempot . ent
Re: Install drivers
On Aug 12 10:59:39, uni...@idempot.net wrote: On 08/11/2013 10:35 AM, josef.win...@email.de wrote: I want to support as much hardware as possible 'out of the box' and since a network can't be assumed, I need to preinstall the drivers. GENERIC supports as much hardware as possible 'out of the box.' You might want the non-free firmware of certain devices installed. See http://firmware.openbsd.org/firmware/ - that's where fw_update(1) finds the non-free firmware of devices found on your system.
radeondrm on Dell T100
This is the first machine I try with the new radeomdrm code: * got the latest from cvs * installed the radeomdrm firmware * restart * This machine does not run X * besides the new kms console, nothing changed OpenBSD 5.4-current (GENERIC.MP) #6: Mon Aug 12 08:28:16 CST 2013 r...@sbr0677.sbrmarketing.dev:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8563326976 (8166MB) avail mem = 8327188480 (7941MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xcf79c000 (58 entries) bios0: vendor Dell Inc. version 1.4.1 date 08/03/2009 bios0: Dell Inc. PowerEdge T100 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP APIC SPCR HPET MCFG SLIC TCPA SSDT SSDT SSDT acpi0: wakeup devices PCI0(S5) COMP(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz, 2400.41 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu0: 1MB 64b/line 4-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 200MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Pentium(R) Dual CPU E2220 @ 2.40GHz, 2400.09 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,EST,TM2,SSSE3,CX16,xTPR,PDCM,NXE,LONG,LAHF,PERF cpu1: 1MB 64b/line 4-way L2 cache cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 2 acpihpet0 at acpi0: 14318179 Hz acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (PEX1) acpiprt2 at acpi0: bus 2 (SBE0) acpiprt3 at acpi0: bus 3 (SBE4) acpiprt4 at acpi0: bus 4 (SBE5) acpiprt5 at acpi0: bus 5 (COMP) acpicpu0 at acpi0: PSS acpicpu1 at acpi0: PSS cpu0: Enhanced SpeedStep 2400 MHz: speeds: 2400, 2200, 2000, 1800, 1600, 1400, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 Intel 3200/3210 Host rev 0x01 ppb0 at pci0 dev 1 function 0 Intel 3200/3210 PCIE rev 0x01: msi pci1 at ppb0 bus 1 uhci0 at pci0 dev 26 function 0 Intel 82801I USB rev 0x02: apic 2 int 17 uhci1 at pci0 dev 26 function 1 Intel 82801I USB rev 0x02: apic 2 int 18 ehci0 at pci0 dev 26 function 7 Intel 82801I USB rev 0x02: apic 2 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb1 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x02: msi pci2 at ppb1 bus 2 ppb2 at pci0 dev 28 function 4 Intel 82801I PCIE rev 0x02: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 5 Intel 82801I PCIE rev 0x02 pci4 at ppb3 bus 4 bge0 at pci4 dev 0 function 0 Broadcom BCM5722 rev 0x00, BCM5755 C0 (0xa200): apic 2 int 17, address 00:23:8b:64:75:70 brgphy0 at bge0 phy 1: BCM5722 10/100/1000baseT PHY, rev. 0 uhci2 at pci0 dev 29 function 0 Intel 82801I USB rev 0x02: apic 2 int 21 uhci3 at pci0 dev 29 function 1 Intel 82801I USB rev 0x02: apic 2 int 20 uhci4 at pci0 dev 29 function 2 Intel 82801I USB rev 0x02: apic 2 int 21 ehci1 at pci0 dev 29 function 7 Intel 82801I USB rev 0x02: apic 2 int 21 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 Intel EHCI root hub rev 2.00/1.00 addr 1 ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev 0x92 pci5 at ppb4 bus 5 radeondrm0 at pci5 dev 5 function 0 ATI ES1000 rev 0x02: apic 2 int 19 drm0 at radeondrm0 pcib0 at pci0 dev 31 function 0 Intel 82801IR LPC rev 0x02 pciide0 at pci0 dev 31 function 2 Intel 82801I SATA rev 0x02: DMA, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 2 int 23 for native-PCI interrupt wd0 at pciide0 channel 0 drive 0: WDC WD1601ABYS-18C0A0 wd0: 16-sector PIO, LBA48, 152587MB, 31250 sectors atapiscsi0 at pciide0 channel 0 drive 1 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: PLDS, DVD-ROM DH-16D3S, SD11 ATAPI 5/cdrom removable wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 6 cd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5 wd1 at pciide0 channel 1 drive 0: WDC WD1601ABYS-18C0A0 wd1: 16-sector PIO, LBA48, 152587MB, 31250 sectors atapiscsi1 at pciide0 channel 1 drive 1 scsibus1 at atapiscsi1: 2 targets cd1 at scsibus1 targ 0 lun 0: HL-DT-ST, DVDRAM GH22NS40, NL00 ATAPI 5/cdrom removable wd1(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 6 cd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 5 usb2 at uhci0: USB revision 1.0 uhub2 at usb2 Intel UHCI root hub rev 1.00/1.00 addr 1 usb3 at uhci1: USB revision 1.0 uhub3 at usb3 Intel UHCI root hub rev 1.00/1.00 addr 1 usb4 at uhci2: USB revision 1.0 uhub4 at usb4 Intel UHCI root hub rev 1.00/1.00 addr 1 usb5 at uhci3: USB revision 1.0 uhub5 at usb5 Intel UHCI root hub rev 1.00/1.00 addr 1 usb6 at uhci4: USB revision 1.0 uhub6 at usb6 Intel UHCI root hub rev
Re: Install drivers
On Mon, 12 Aug 2013, Matthew Weigel wrote: On 08/11/2013 10:35 AM, josef.win...@email.de wrote: I want to support as much hardware as possible 'out of the box' and since a network can't be assumed, I need to preinstall the drivers. GENERIC supports as much hardware as possible 'out of the box.' Yes, but some might need fireware to work. The firmware needs to be downloaded whike online (e.g. some wifi drivers). -moj -- Matthew Weigel hacker unique idempot . ent
Re: Install drivers
this isn't a lesser operating system. all such drivers are included out of the box. the only thing that may be missing, is the various firmware files. Check out how fw_update(8) works to fetch those. On 2013 Aug 11 (Sun) at 17:35:24 +0200 (+0200), josef.win...@email.de wrote: :How can I force OBSD to install drivers, that are not needed :on the running hardware? : :This may sound strange on a first sight, but in my situation I :have OBSD on a flash drive that runs via flashrd from RAM and :this RAM can be located in various (i386/ARM64) systems. : :I want to support as much hardware as possible 'out of the box' :and since a network can't be assumed, I need to preinstall the :drivers. : : :--Josef : -- Bank error in your favor. Collect $200.
Dell Optiplex 9010 - radeomdrm
* Dell Optiplex 9010 with two radeon cards * xenocara still building. Without the radeons, inteldrm works great. OpenBSD 5.4-current (GENERIC.MP) #6: Mon Aug 12 08:28:16 CST 2013 r...@sbr0677.sbrmarketing.dev:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8521850880 (8127MB) avail mem = 8286814208 (7902MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xebfb0 (87 entries) bios0: vendor Dell Inc. version A01 date 05/04/2012 bios0: Dell Inc. OptiPlex 9010 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG HPET SSDT SSDT SSDT DMAR ASF! SLIC acpi0: wakeup devices PS2K(S3) PS2M(S3) UAR1(S3) P0P1(S4) USB1(S3) USB2(S3) USB3(S3) USB4(S3) USB5(S3) USB6(S3) USB7(S3) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.83 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 cpu0: apic clock running at 99MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu5: 256KB 64b/line 8-way L2 cache cpu5: smt 1, core 1, package 0 cpu6 at mainbus0: apid 5 (application processor) cpu6: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu6: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu6: 256KB 64b/line 8-way L2 cache cpu6: smt 1, core 2, package 0 cpu7 at mainbus0: apid 7 (application processor) cpu7: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, 3392.31 MHz cpu7: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX ,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,A ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS cpu7: 256KB 64b/line 8-way L2 cache cpu7: smt 1, core 3, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xf800, bus 0-63 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 4 (P0P1) acpiprt2 at acpi0: bus 2 (RP01)
Upgrade to 5.0 from 4.x broke Apache+PHP's ability to talk to mysql.sock
Whoops; sent this earlier, but I hadn't changed the message subject from the Message Digest default text. I assume that's why it wasn't forwarded previously. Here's what I'd written on this subject previously: Awhile back here, I brought up an issue that occurred when I was upgrading my system from OpenBSD 4.x to 5.0. I'm not sure if it was on this mailing list or not, but this seems like the most appropriate place to bring it up. I had relied on several services via Apache that utilize PHP MySQL in a fairly standard configuration. Unfortunately, when I upgraded (all according to the standard upgrade instructions provided), all of my services broke due to PHP not being able to connect to the sock located in '/var/run/mysql/mysql.sock'. I asked for help and googled like a fiend for awhile, but even when interactively talking to folks in freenet's #openbsd, I was unable to find what might've been wrong with this. Foolishly enough, several times I considered the fact that httpd would be executing everything in the chroot jail of '/var/www', but I didn't research it that deeply or try moving the sock, because I figured that with all of the people I spoke to already, certainly one of the experts would have mentioned if this had been causing an issue or not. Last night, however, when I decided to take another stab at things, googling turned up a result that I hadn't seen previously (I am google-tarded, so I will accept the possibility that I'd not done as straightforward an attempt to look for the answer of this issue as I'd thought). The link was at http://philihp.com/blog/2008/connecting-to-mysql-with-php-in-apache-on-openbsd/ (2008? Certainly I must not have googled as well as I thought!), and referred to a permanent (although kludgy) solution found at http://www.openbsdsupport.org/e107_CMS.html . The solution was, indeed, dealing with creating a hardlink to somewhere within the chroot'ed jail; in this case under /var/www/var/run/mysql/mysql.sock after the appropriate path was created. Anyway I just thought that I'd post that here, since a lot of people in the OpenBSD community didn't seem to know how simple the solution really was or where it might be found at. It might be a good idea to toss this in the 4.x to 5.0 upgrade instructions, as well. It seems like a relatively simple oversight. Best wishes. -Damon
OpenBSD pxe automated install
Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD pxe automated install
read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD pxe automated install
Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Building bind with gssapi
I've been tearing my hair out trying to get this to work. I'm running OpenBSD 5.3 x64 and I'm trying to build isc-bind from ports using the -with-gssapi in the Makefile (I want to have the -g option in nsupdate so I can use iscp-dhcp to register dynamic DNS updates against a secure Windows nameserver). I've specified --with-gssapi=/usr in the Makefile. Now, OpenBSD seems to put the gssapi.h in /usr/include/kerberosV, and krb5.h is there too. Yet, when I make the port it gives the following errors: checking for GSSAPI library... looking in /usr/lib checking gssapi.h usability... no checking gssapi.h presence... no checking for gssapi.h... no checking gssapi/gssapi.h usability... no checking gssapi/gssapi.h presence... no checking for gssapi/gssapi.h... no configure: error: gssapi.h not found I've tried adding symlinks here and there, but nothing works. I also see that the configure script wants to tack /lib onto the end of whatever path I enter for --with-gssapi=, even though the .h files aren't located in any such folder. Am I doing something wrong? I'd appreciate any insights. Thanks, Jeff Jeff Powell Systems Administrator Valley Services Electronics (408) 284-7751
unnecessary quotes in .Nd lines
Some manpages use one-line descriptions such as .Nd VAX console interface The double quotes, if I am not mistaken, are unnecessary; the diff below removes them throughout the tree. (Were these required at some point in the past?) Jan Index: games/bcd/bcd.6 === RCS file: /cvs/src/games/bcd/bcd.6,v retrieving revision 1.16 diff -u -p -u -p -r1.16 bcd.6 --- games/bcd/bcd.6 31 May 2007 19:19:17 - 1.16 +++ games/bcd/bcd.6 12 Aug 2013 19:50:10 - @@ -36,7 +36,7 @@ .Nm bcd , .Nm ppt , .Nm morse -.Nd reformat input as punch cards, paper tape or morse code +.Nd reformat input as punch cards, paper tape or morse code .Sh SYNOPSIS .Nm bcd .Op Ar string ... Index: games/fortune/strfile/strfile.8 === RCS file: /cvs/src/games/fortune/strfile/strfile.8,v retrieving revision 1.14 diff -u -p -u -p -r1.14 strfile.8 --- games/fortune/strfile/strfile.8 17 Jan 2010 13:15:34 - 1.14 +++ games/fortune/strfile/strfile.8 12 Aug 2013 19:50:10 - @@ -40,7 +40,7 @@ .Sh NAME .Nm strfile , .Nm unstr -.Nd create a random access file for storing strings +.Nd create a random access file for storing strings .Sh SYNOPSIS .Nm strfile .Op Fl iorsx Index: lib/libarch/arm/arm_sync_icache.2 === RCS file: /cvs/src/lib/libarch/arm/arm_sync_icache.2,v retrieving revision 1.3 diff -u -p -u -p -r1.3 arm_sync_icache.2 --- lib/libarch/arm/arm_sync_icache.2 17 Nov 2007 12:02:33 - 1.3 +++ lib/libarch/arm/arm_sync_icache.2 12 Aug 2013 19:50:19 - @@ -36,7 +36,7 @@ .Os .Sh NAME .Nm arm_sync_icache -.Nd clean the CPU data cache and flush the CPU instruction cache +.Nd clean the CPU data cache and flush the CPU instruction cache .Sh SYNOPSIS .In machine/sysarch.h .Ft int Index: lib/libc/gen/isfdtype.3 === RCS file: /cvs/src/lib/libc/gen/isfdtype.3,v retrieving revision 1.7 diff -u -p -u -p -r1.7 isfdtype.3 --- lib/libc/gen/isfdtype.3 5 Jun 2013 03:39:22 - 1.7 +++ lib/libc/gen/isfdtype.3 12 Aug 2013 19:50:19 - @@ -23,7 +23,7 @@ .Os .Sh NAME .Nm isfdtype -.Nd determine whether a file descriptor is of a specific type +.Nd determine whether a file descriptor is of a specific type .Sh SYNOPSIS .In sys/stat.h .Ft int Index: lib/libc/gen/posix_spawn_file_actions_init.3 === RCS file: /cvs/src/lib/libc/gen/posix_spawn_file_actions_init.3,v retrieving revision 1.6 diff -u -p -u -p -r1.6 posix_spawn_file_actions_init.3 --- lib/libc/gen/posix_spawn_file_actions_init.316 Jul 2013 15:21:11 - 1.6 +++ lib/libc/gen/posix_spawn_file_actions_init.312 Aug 2013 19:50:19 - @@ -20,7 +20,7 @@ .Sh NAME .Nm posix_spawn_file_actions_init , .Nm posix_spawn_file_actions_destroy -.Nd create and destroy posix_spawn file actions objects +.Nd create and destroy posix_spawn file actions objects .Sh SYNOPSIS .In spawn.h .Ft int Index: lib/libc/gen/posix_spawnattr_getflags.3 === RCS file: /cvs/src/lib/libc/gen/posix_spawnattr_getflags.3,v retrieving revision 1.7 diff -u -p -u -p -r1.7 posix_spawnattr_getflags.3 --- lib/libc/gen/posix_spawnattr_getflags.3 16 Jul 2013 15:21:11 - 1.7 +++ lib/libc/gen/posix_spawnattr_getflags.3 12 Aug 2013 19:50:19 - @@ -20,7 +20,7 @@ .Sh NAME .Nm posix_spawnattr_getflags , .Nm posix_spawnattr_setflags -.Nd get and set flags of a posix_spawn attributes object +.Nd get and set flags of a posix_spawn attributes object .Sh SYNOPSIS .In spawn.h .Ft int Index: lib/libc/gen/posix_spawnattr_getpgroup.3 === RCS file: /cvs/src/lib/libc/gen/posix_spawnattr_getpgroup.3,v retrieving revision 1.6 diff -u -p -u -p -r1.6 posix_spawnattr_getpgroup.3 --- lib/libc/gen/posix_spawnattr_getpgroup.316 Jul 2013 15:21:11 - 1.6 +++ lib/libc/gen/posix_spawnattr_getpgroup.312 Aug 2013 19:50:19 - @@ -28,7 +28,7 @@ .Nm posix_spawnattr_setschedpolicy , .Nm posix_spawnattr_setsigdefault , .Nm posix_spawnattr_setsigmask -.Nd get and set misc attributes of a posix_spawn attributes object +.Nd get and set misc attributes of a posix_spawn attributes object .Sh SYNOPSIS .In spawn.h .Ft int Index: lib/libc/gen/posix_spawnattr_init.3 === RCS file: /cvs/src/lib/libc/gen/posix_spawnattr_init.3,v retrieving revision 1.6 diff -u -p -u -p -r1.6 posix_spawnattr_init.3 --- lib/libc/gen/posix_spawnattr_init.3 16 Jul 2013 15:21:11 - 1.6 +++ lib/libc/gen/posix_spawnattr_init.3 12 Aug 2013 19:50:19 - @@ -20,7 +20,7 @@ .Sh NAME .Nm posix_spawnattr_init , .Nm posix_spawnattr_destroy
Re: OpenBSD pxe automated install
Please read the FAQ entry I sent you, pay close attention to install.site and upgrade.site. Both of those are scripts that are executed by the installer. Fully automatic installs have been done, usually by modifying the installer script or root's .profile. Basically: automatic, unattended installation of openbsd is possible, but you have to build the glue for it. Sent form my iFoe. On Aug 12, 2013, at 12:52, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD pxe automated install
Build your own bsd.rd which feeds precomputed values for disk size and so on. Not super hard to do. Den 12 aug 2013 21:44 skrev Loïc BLOT loic.b...@unix-experience.fr: Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Upgrade to 5.0 from 4.x broke Apache+PHP's ability to talk to mysql.sock
On 12 August 2013, Damon Getsman damo.g...@gmail.com wrote: [...] Last night, however, when I decided to take another stab at things, googling turned up a result that I hadn't seen previously (I am google-tarded, so I will accept the possibility that I'd not done as straightforward an attempt to look for the answer of this issue as I'd thought). The link was at http://philihp.com/blog/2008/connecting-to-mysql-with-php-in-apache-on-openbsd/ (2008? Certainly I must not have googled as well as I thought!), and referred to a permanent (although kludgy) solution found at http://www.openbsdsupport.org/e107_CMS.html . The solution was, indeed, dealing with creating a hardlink to somewhere within the chroot'ed jail; in this case under /var/www/var/run/mysql/mysql.sock after the appropriate path was created. [...] Please, stop repeating this nonsense. This solution works until you restart the server manually, since mysqld removes the socket before re-creating it. The real solution is either to use TCP connections, or move the socket inside the jail and make /etc/my.cnf and /var/www/etc/my.cnf point to it accordingly. Regards, Liviu Daia
Re: OpenBSD pxe automated install
Sorry if i misunderstood the goal of install.site. I look at this, more clearly, to see if it's the solution i search. -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 13:07 -0700, Johan Beisser a écrit : Please read the FAQ entry I sent you, pay close attention to install.site and upgrade.site. Both of those are scripts that are executed by the installer. Fully automatic installs have been done, usually by modifying the installer script or root's .profile. Basically: automatic, unattended installation of openbsd is possible, but you have to build the glue for it. Sent form my iFoe. On Aug 12, 2013, at 12:52, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
remove .Tn abuse [was: yacc(1) mandoc nits]
On Aug 12 07:11:16, j...@kerhand.co.uk wrote: On Sun, Aug 11, 2013 at 10:49:27PM +0200, Jan Stary wrote: Tha yacc(1) manpage uses .Tn LALR(1) .Tn LR(1) I don't think LALR or LR is a tradename. This seems to be what mdoc(7) describes as: Since this macro is often implemented to use a small caps font, it has historically been used for acronyms (like ASCII) as well. Such usage is not recommended because it would use the same macro sometimes for semantical annotation, sometimes for physical formatting. So would it be better to just say LALR(1) without any markup, just as we say e.g. BNF? Jan yes, Tn gets abused horribly. however it's everwhere, so i wouldn;t want to tackle it in a single page. we would have to decide where exactly it makes sense (never, as far as i'm concerned), then do it everywhere consistently. The diff below removes them from bin/ games/ and sys/ (more to come) leaving only those that are actualy tradenames, as in .Tn ATT Jan Index: bin/cat/cat.1 === RCS file: /cvs/src/bin/cat/cat.1,v retrieving revision 1.33 diff -u -p -u -p -r1.33 cat.1 --- bin/cat/cat.1 16 Jul 2013 06:52:05 - 1.33 +++ bin/cat/cat.1 12 Aug 2013 19:24:20 - @@ -92,12 +92,9 @@ which are displayed normally. The tab character, control-I, can be made visible via the .Fl t option. -The -.Tn DEL -character (octal 0177) prints as +The DEL character (octal 0177) prints as .Ql ^? . -.Pf Non- Ns Tn ASCII -characters (with the high bit set) are printed as +Non-ASCII characters (with the high bit set) are printed as .Ql M- (for meta) followed by the character for the low 7 bits. .El Index: bin/chio/chio.1 === RCS file: /cvs/src/bin/chio/chio.1,v retrieving revision 1.32 diff -u -p -u -p -r1.32 chio.1 --- bin/chio/chio.1 15 Jul 2013 23:43:58 - 1.32 +++ bin/chio/chio.1 12 Aug 2013 19:24:20 - @@ -243,8 +243,7 @@ Configure the changer to use picker 2 (t .Sh AUTHORS The .Nm -program and -.Tn SCSI +program and SCSI changer driver were written by .An Jason R. Thorpe Aq Mt thor...@and.com for And Communications Index: bin/csh/csh.1 === RCS file: /cvs/src/bin/csh/csh.1,v retrieving revision 1.67 diff -u -p -u -p -r1.67 csh.1 --- bin/csh/csh.1 15 Jan 2012 20:06:40 - 1.67 +++ bin/csh/csh.1 12 Aug 2013 19:24:20 - @@ -179,8 +179,7 @@ in the home directory of the invoker, and, if this is a login shell, the file .Pa \.login in the same location. -It is typical for users on -.Tn CRT Ns s +It is typical for users on CRTs to put the command .Ic stty crt in their @@ -1686,9 +1685,7 @@ Like but no .Ql \e escapes are recognized and words are delimited -by -.Tn NUL -characters in the output. +by NUL characters in the output. Useful for programs that wish to use the shell to filename expand a list of words. .Pp @@ -1945,9 +1942,7 @@ to the given The final two forms run command at priority 4 and .Ar number respectively. -The greater the number, the less -.Tn CPU -the process will get. +The greater the number, the less CPU the process will get. The superuser may specify negative priority by using .Dq nice \-number ... . .Ar command @@ -2579,9 +2574,7 @@ Built-in commands that fail return exit all other built-in commands set status to 0. .It Ic time Controls automatic timing of commands. -If set, then any command that takes more than this many -.Tn CPU -seconds +If set, then any command that takes more than this many CPU seconds will cause a line giving user, system, and real times, and a utilization percentage which is the ratio of user plus system times to real time to be printed when it terminates. Index: bin/date/date.1 === RCS file: /cvs/src/bin/date/date.1,v retrieving revision 1.59 diff -u -p -u -p -r1.59 date.1 --- bin/date/date.1 31 Aug 2011 08:48:40 - 1.59 +++ bin/date/date.1 12 Aug 2013 19:24:20 - @@ -93,8 +93,7 @@ Print out (in specified format) the date .Ar seconds from the Epoch. .It Fl t Ar minutes_west -Set the system's value for minutes west of -.Tn GMT . +Set the system's value for minutes west of GMT. .Ar minutes_west specifies the number of minutes returned in .Fa tz_minuteswest Index: bin/dd/dd.1 === RCS file: /cvs/src/bin/dd/dd.1,v retrieving revision 1.25 diff -u -p -u -p -r1.25 dd.1 --- bin/dd/dd.1 18 Oct 2011 09:37:35 - 1.25 +++ bin/dd/dd.1 12 Aug 2013 19:24:20 - @@ -123,9 +123,7 @@ using the tape .Xr ioctl 2 function calls. If the seek operation is past the end of file, space from the current -end of file to the specified offset is filled with blocks of
Re: OpenBSD pxe automated install
like kickstart for devil redhat ? From: Loïc BLOT loic.b...@unix-experience.fr Sent: Mon Aug 12 21:52:05 CEST 2013 To: misc@openbsd.org Subject: Re: OpenBSD pxe automated install Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 Toulouse France +33 6 17 230 820 +33 5 34 365 269 fpussa...@contactoffice.fr
Re: OpenBSD pxe automated install
It's exactly that. Kickstart for Redhat and Preseed.cfg for Debian -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 22:20 +0200, Francois Pussault a écrit : like kickstart for devil redhat ? From: Loïc BLOT loic.b...@unix-experience.fr Sent: Mon Aug 12 21:52:05 CEST 2013 To: misc@openbsd.org Subject: Re: OpenBSD pxe automated install Hello, thanks for your reply Johan, but this is not why i want. site.tgz contain a set of preconfigured files to deploy with other sets to deploy similar machines. My need is to install a clean OpenBSD with an automated mean: The server boot in PXE and install OpenBSD, configure network, hostname, disk, install sets by network and reboots without any human intervention. After, the server can use siteXX.tgz, yes, but this is not the main problem here -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:09 -0700, Johan Beisser a écrit : read the FAQ, Loic. http://openbsd.org/faq/faq4.html#site Site*.tgz, install.site and upgrade.site are a good starting point. On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT loic.b...@unix-experience.fr wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] Cordialement Francois Pussault 3701 - 8 rue Marcel Pagnol 31100 Toulouse France +33 6 17 230 820 +33 5 34 365 269 fpussa...@contactoffice.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: OpenBSD pxe automated install
On Mon, Aug 12, 2013 at 08:59:27PM +0200, Lo?c BLOT wrote: Hello @misc. Today i'm working on automated deploy with PXE. I have successful found and made automated PXE install on Debian with pxelinux. I know OpenBSD have a pxe boot image to netinstall the system http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution -environment/ Is there any options to automate the installation ? I want a machine to boot on bsd.rd, read a configuration file (url passed by etc/boot.conf, for example) and install with the read parameters. Is there any issue to do this or i do it myself ? Thanks for advance -- Best regards, Lo??c BLOT, UNIX systems, security and network expert http://www.unix-experience.fr [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc] There is no 'offical' method. If you check the mailing list archives you'll find a few people have come up with something that works for them. Ken
Re: OpenBSD pxe automated install
- Original Message - | read the FAQ, Loic. | | http://openbsd.org/faq/faq4.html#site | | Site*.tgz, install.site and upgrade.site are a good starting point. | | On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT | loic.b...@unix-experience.fr wrote: | Hello @misc. | | Today i'm working on automated deploy with PXE. I have successful | found | and made automated PXE install on Debian with pxelinux. | | I know OpenBSD have a pxe boot image to netinstall the system | http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution | -environment/ | | Is there any options to automate the installation ? | I want a machine to boot on bsd.rd, read a configuration file (url | passed by etc/boot.conf, for example) and install with the read | parameters. | Is there any issue to do this or i do it myself ? | | Thanks for advance | -- | Best regards, | Loïc BLOT, | UNIX systems, security and network expert | http://www.unix-experience.fr | | [demime 1.01d removed an attachment of type | application/pgp-signature which had a name of signature.asc] If you are looking for automated partitioning and the like the site.install and site.upgrade don't apply whatsoever. In order to fully automate the installation you will need to modify the bsd.rd file contents in order to do that. site.install and site.upgrade can be used to do other things like install packages or upgrade the OS as necessary. -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices “A successful person is one who can lay a solid foundation from the bricks others have thrown at them.” -David Brinkley via Luke Shaw
Re: OpenBSD pxe automated install
Thanks for the precision James, you confirmed what i have understood. I will search tomorrow. -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:23 -0700, James A. Peltier a écrit : - Original Message - | read the FAQ, Loic. | | http://openbsd.org/faq/faq4.html#site | | Site*.tgz, install.site and upgrade.site are a good starting point. | | On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT | loic.b...@unix-experience.fr wrote: | Hello @misc. | | Today i'm working on automated deploy with PXE. I have successful | found | and made automated PXE install on Debian with pxelinux. | | I know OpenBSD have a pxe boot image to netinstall the system | http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution | -environment/ | | Is there any options to automate the installation ? | I want a machine to boot on bsd.rd, read a configuration file (url | passed by etc/boot.conf, for example) and install with the read | parameters. | Is there any issue to do this or i do it myself ? | | Thanks for advance | -- | Best regards, | Loïc BLOT, | UNIX systems, security and network expert | http://www.unix-experience.fr | | [demime 1.01d removed an attachment of type | application/pgp-signature which had a name of signature.asc] If you are looking for automated partitioning and the like the site.install and site.upgrade don't apply whatsoever. In order to fully automate the installation you will need to modify the bsd.rd file contents in order to do that. site.install and site.upgrade can be used to do other things like install packages or upgrade the OS as necessary. [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Bind with GSSAPI
I've been tearing my hair out trying to get this to work. I'm running OpenBSD 5.3 x64 and I'm trying to build isc-bind from ports using the -with-gssapi in the Makefile (I want to have the -g option in nsupdate so I can use iscp-dhcp to register dynamic DNS updates against a secure Windows nameserver). I've specified --with-gssapi=/usr in the Makefile. Now, OpenBSD seems to put the gssapi.h in /usr/include/kerberosV, and krb5.h is there too. Yet, when I make the port it gives the following errors: checking for GSSAPI library... looking in /usr/lib checking gssapi.h usability... no checking gssapi.h presence... no checking for gssapi.h... no checking gssapi/gssapi.h usability... no checking gssapi/gssapi.h presence... no checking for gssapi/gssapi.h... no configure: error: gssapi.h not found I've tried adding symlinks here and there, but nothing works. I also see that the configure script wants to tack /lib onto the end of whatever path I enter for --with-gssapi=, even though the .h files aren't located in any such folder. Am I doing something wrong? I'd appreciate any insights. Thanks, Jeff
Re: OpenBSD pxe automated install
Please read http://www.openbsd.org/faq/faq6.html#PXE and hope this helps. You'd have been told with deliberately unpleasant choice of words if next time you don't research well before asking in the list. On Tue, Aug 13, 2013 at 4:57 AM, Loïc BLOT loic.b...@unix-experience.frwrote: Thanks for the precision James, you confirmed what i have understood. I will search tomorrow. -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le lundi 12 août 2013 à 12:23 -0700, James A. Peltier a écrit : - Original Message - | read the FAQ, Loic. | | http://openbsd.org/faq/faq4.html#site | | Site*.tgz, install.site and upgrade.site are a good starting point. | | On Mon, Aug 12, 2013 at 11:59 AM, Loïc BLOT | loic.b...@unix-experience.fr wrote: | Hello @misc. | | Today i'm working on automated deploy with PXE. I have successful | found | and made automated PXE install on Debian with pxelinux. | | I know OpenBSD have a pxe boot image to netinstall the system | http://www.cyberciti.biz/faq/openbsd-boot-install-using-pxe-preboot-execution | -environment/ | | Is there any options to automate the installation ? | I want a machine to boot on bsd.rd, read a configuration file (url | passed by etc/boot.conf, for example) and install with the read | parameters. | Is there any issue to do this or i do it myself ? | | Thanks for advance | -- | Best regards, | Loïc BLOT, | UNIX systems, security and network expert | http://www.unix-experience.fr | | [demime 1.01d removed an attachment of type | application/pgp-signature which had a name of signature.asc] If you are looking for automated partitioning and the like the site.install and site.upgrade don't apply whatsoever. In order to fully automate the installation you will need to modify the bsd.rd file contents in order to do that. site.install and site.upgrade can be used to do other things like install packages or upgrade the OS as necessary. [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Install drivers
On 08/12/13 18:49, Peter Hessler wrote:
this isn't a lesser operating system. all such drivers are included out
of the box.
the only thing that may be missing, is the various firmware files.
Check out how fw_update(8) works to fetch those.
This diff lets you pinpoint specific drivers, or use '-a' to
install/update them all. I've been wanting to cook something like
this up for a long time. Man page bits still missing.
/Alexander
Index: fw_update.sh
===
RCS file: /cvs/src/usr.sbin/fw_update/fw_update.sh,v
retrieving revision 1.12
diff -u -p -r1.12 fw_update.sh
--- fw_update.sh17 Sep 2012 18:28:43 - 1.12
+++ fw_update.sh13 Aug 2013 00:14:50 -
@@ -22,7 +22,7 @@ DRIVERS=acx athn bwi ipw iwi iwn malo o
PKG_ADD=pkg_add -I -D repair
usage() {
- echo usage: ${0##*/} [-nv] 2
+ echo usage: ${0##*/} [-anv] [driver ...] 2
exit 1
}
@@ -30,23 +30,29 @@ verbose() {
[ $verbose ] echo ${0##*/}: $@
}
+setver() {
+ version=$1
+ tag=$2
+}
+
+all=false
verbose=
nop=
-while getopts 'nv' s $@ 2/dev/null; do
+while getopts 'anv' s $@ 2/dev/null; do
case $s in
+ a) all=true;;
v) verbose=${verbose:--}v ;;
n) nop=-n ;;
*) usage ;;
esac
done
-# No additional arguments allowed
-[ $# = $(($OPTIND-1)) ] || usage
+shift $((OPTIND - 1))
-set -- $(sysctl -n kern.version | sed 's/^OpenBSD \([0-9]\.[0-9]\)\([^
]*\).*/\1 \2/;q')
+$all set -- $DRIVERS
-version=$1
-tag=$2
+setver $(sysctl -n kern.version |
+sed 's/^OpenBSD \([0-9]\.[0-9]\)\([^ ]*\).*/\1 \2/;q')
[[ $tag == -!(stable) ]] version=snapshots
export PKG_PATH=http://firmware.openbsd.org/firmware/$version/
@@ -59,10 +65,12 @@ update=
extra=
for driver in $DRIVERS; do
+ [ $# = 0 ] || printf %s\n $@ | fgrep -qx $driver || continue
if print -r -- $installed | grep -q ^${driver}-firmware-; then
update=$update ${driver}-firmware
extra=$extra -Dupdate_${driver}-firmware
- elif print -r -- $dmesg | grep -q ^${driver}[0-9][0-9]* at ; then
+ elif [ $# != 0 ] ||
+ print -r -- $dmesg | grep -q ^${driver}[0-9][0-9]* at ; then
install=$install ${driver}-firmware
fi
done
Man page that explains the file format of man pages?
Hello Misc, I tried man 5 man for an explanation of the synopsis section of the man page and it says there isn't a manual for the file format conventions of manual pages. Sometimes I have difficulty with the syntax of the synopsis sections, is there a document I can refer to? I also looked up the Unix version 1 man pages just for history's sake and found that they are reaaallly simple and easy to understand. Is this just something that has gotten out of hand over time? Evan Root, CCNA
Re: Man page that explains the file format of man pages?
Evan Root writes: Hello Misc, I tried man 5 man for an explanation of the synopsis section of the man page and it says there isn't a manual for the file format conventions of manual pages. Sometimes I have difficulty with the syntax of the synopsis sections, is there a document I can refer to? OpenBSD manuals are written in the mdoc macro language. There is a page describing it, in section 7 (not 5). It is mentioned in the SEE ALSO section of man(1). man 7 mdoc There is also a man(7) page, describing the older man macros, but these are not used for new manuals in OpenBSD. mdoc has the advantage of being a semantic format, unlike the old man language where the commands mostly change only the presentation. -- Anthony J. Bentley
Re: Man page that explains the file format of man pages?
I don't think you understood. I am not looking to write a man page. I was just wondering if the system came with an explanation of the manual page synopsis section language syntax. Sometimes I get confused by the language and am not sure if I understand the synopsis sections of the man pages. Also I am concerned that people who I might recommend OpenBSD to will find that an undocumented part of the system is the man pages. Even the welcome message from Theo says This message attempts to describe the most basic initial questions that a system administrator of an OpenBSD box might have. If you are not familiar with how to read man pages, type man man at a shell prompt and read the entire thing. I think that this post on stack exchange presents my question better.. the answers are all pretty short and non-committal though. http://stackoverflow.com/questions/8716047/is-there-a-specification-for-a-man-pages-synopsis-section Evan Root, CCNA 505.226.1319 On Mon, Aug 12, 2013 at 9:21 PM, Anthony J. Bentley anth...@cathet.uswrote: Evan Root writes: Hello Misc, I tried man 5 man for an explanation of the synopsis section of the man page and it says there isn't a manual for the file format conventions of manual pages. Sometimes I have difficulty with the syntax of the synopsis sections, is there a document I can refer to? OpenBSD manuals are written in the mdoc macro language. There is a page describing it, in section 7 (not 5). It is mentioned in the SEE ALSO section of man(1). man 7 mdoc There is also a man(7) page, describing the older man macros, but these are not used for new manuals in OpenBSD. mdoc has the advantage of being a semantic format, unlike the old man language where the commands mostly change only the presentation. -- Anthony J. Bentley
Re: Man page that explains the file format of man pages?
On Mon, Aug 12, 2013 at 11:49 PM, Evan Root cellarr...@gmail.com wrote: I think that this post on stack exchange presents my question better.. the answers are all pretty short and non-committal though. http://stackoverflow.com/questions/8716047/is-there-a-specification-for-a-man-pages-synopsis-section the best answer is included in that stack exchange submission POSIX.1-2008 Chapter 12 Utility Conventions describes the syntax of the SYNOPSIS sections for utilities, which is what you're looking for
