archive-org.com » ORG » N » NETBSD.ORG

Total: 1243

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • latex in netbsd
    In my case I wanted to use alphadin a package for having German styled citation references So I went to CTAN downloaded the package and unpacked it ftp http mirrors ctan org biblio bibtex contrib german din1505 zip Requesting http mirrors ctan org biblio bibtex contrib german din1505 zip Redirected to http sunsite informatik rwth aachen de ftp pub mirror ctan biblio bibtex contrib german din1505 zip Requesting http sunsite informatik rwth aachen de ftp pub mirror ctan biblio bibtex contrib german din1505 zip 100 408 KiB 244 11 KiB s 00 00 ETA 417797 bytes retrieved in 00 01 244 09 KiB s unzip din1505 zip Archive din1505 zip creating din1505 extracting din1505 abbrvdin bst extracting din1505 alphadin bst extracting din1505 plaindin bst extracting din1505 unsrtdin bst extracting din1505 natdin bst extracting din1505 natbib cfg extracting din1505 leitbild3 pdf extracting din1505 leitbild bib extracting din1505 normpatsoft pdf Running kpsepath showed that the directory to install the contained bst files was texmf bibtex bst kpsepath bst home gnrp texlive2012 texmf config bibtex bst home gnrp texlive2012 texmf var bibtex bst home gnrp texmf bibtex bst usr pkg etc texmf bibtex bst var lib texmf bibtex bst usr pkg share texmf bibtex bst usr pkg share texmf local bibtex bst usr pkg share texmf dist bibtex bst home gnrp texlive2012 texmf config bibtex csf home gnrp texlive2012 texmf var bibtex csf home gnrp texmf bibtex csf usr pkg etc texmf bibtex csf var lib texmf bibtex csf usr pkg share texmf bibtex csf usr pkg share texmf local bibtex csf usr pkg share texmf dist bibtex csf So I moved the files to texmf bibtex bst and created the directory before that cd din1505 mkdir p texmv bibtex bst mv bst texmf bibtex bst Afterwards compiling everything worked fine Useful packages For writing my Bachelor s thesis I used the following packages Some of them are very basic and are generally useful for many purposes but especially for scientific documents they are useful tex babel tex amsmath tex amscls tex stmaryrd tex microtype tex oberdiek tex bibtex BibTeX is a system to handle citations in a document Editors If you don t want to hassle learning Latex but still use its powerful typesetting or some other specifics such as the formulas you can use the software LyX editors lyx which creates Latex documents with a WYSIWYG or rather WYSIWYM interface Even if you can write Latex you should have a look at it it s a very mighty tool sometimes making your work much easier When it comes to editors there are several different ones each with its own specific strength Many people use just plain vi or vim which I did in the beginning as well But then I found geany devel geany which is an IDE originally but also serves for coding Latex It is a lightweight but also minimalistic tool for writing Latex code Another very popular tool is kile editors kile which has many features and also

    Original URL path: http://wiki.netbsd.org/tutorials/latex_in_netbsd/ (2016-02-01)
    Open archived version from archive

  • netbsd command-line cheat-sheet
    for details shutdown p now Shutdown the machine and halt afterwards but keep the power on shutdown h now File Directory Operations Find out what directory you are in pwd List contents of current working directory ls Copy a file to a new file with a different name cp foobar txt barfoo txt Remove a file delete it rm foobar txt Remove an empty directory rmdir mydir Recursively remove a directory be careful with this if you mess up you can easily wipe out your whole system This will remove the directory and all the files and subdirectories it contains provided you have permissions rm rf mydir Using Archives Create a tar archive with the contents of a directory displaying each file and directory as tar runs verbosely tar cvf my archive tar some directory The same using pax pax w v f my archive tar some directory Extract a tar archive to the current directory displaying each file and directory as tar runs verbosely tar xvf my archive tar The same using pax pax r v f my archive tar Compress a file with gzip using maximum slowest compression gzip 9 foobar txt Compress a file with bzip2 using maximum slowest compression Bzip generally compresses files better at the cost of greater time during the compression phase The archives it creates generally de compress at the same speed as gzip bzip2 9 foobar txt User Operations Add a new user and create their home directory useradd m jsmith Change a user s default shell chsh s path newshell jsmith or span class createlink a href cgi bin ikiwiki do create amp from tutorials 2Fnetbsd command line cheat sheet amp page basics 2Fchpass rel nofollow a chpass span s bin ksh jsmith Package Operations pkgsrc Add a binary package pkg

    Original URL path: http://wiki.netbsd.org/tutorials/netbsd_command-line_cheat-sheet/ (2016-02-01)
    Open archived version from archive

  • openldap authentication on netbsd
    ldap so 1 and from usr lib security pam ldap so to LOCALBASE lib security pam ldap so Before we go any further I d like to introduce some security into the mix up til now we ve talked to the ldap server without any limitations and what s called anonymous binds i e not logged in XXX can anonymous binds actually write to a db without ACLs This is an ldap user just like the test user outlined above since the ldap database can authenticate against itself You don t have to but I haven t explored the other possibilities such as SASL So we ll create a user called nss dn cn nss dc example dc org objectClass top objectClass inetOrgPerson o Example Organisation cn nss sn manager We ll attach a password so that not just anyone can connect and also change our LDAP configuration slightly so that we use encrypted passwords userPassword SSHA w5aocfmGgZqq3h8AjvaZiw8WKdrRTjTi To generate this password I use bundled with openldap server slapdpasswd slappasswd h SSHA And in slapd conf add passsword hash SSHA And of course you ll need to change the secret for the rootpw into something encrypted Note that the traffic between the ldap client and the server is still not that is if you ve been following this document encrypted so this might be best to perform locally This user will be used for ACL filtering later Next we ll need to configure the LDAP part of the plugins a convenience here is that since both the plugins are made by the same people they can share a configuration file They will look for PKG SYSCONFBASE nss ldap conf and PKG SYSCONFBASE pam ldap conf but linking them to the same file will let you have just one place to configure and protect for your ldap user password The important bits in this file is the base setting and the uri for your ldap server base dc example dc org uri ldap my server Next we need to tell it who it should contact the ldap database as binddn cn nss dc example dc org And if you want to be able to change passwords as root without knowing the user s password in advance with passwd using ldapmodify you can still just set it if you bind with the credentials to do it see ACLs I haven t mentioned this user before it s the database s root user allowed to do anything rootbinddn cn root dc example dc org The password for this will not be in this file but in a separate file called PKG SYSCONFBASE nss ldap secret or for pam PKG SYSCONFBASE pam ldap secret not sure about this but my system has both linked together Finally we will set the password exchange method to exop pam password exop This is the OpenLDAP extended method and while the passwords will still be sent in the clear they are encrypted with the database s scheme in

    Original URL path: http://wiki.netbsd.org/tutorials/openldap_authentication_on_netbsd/ (2016-02-01)
    Open archived version from archive

  • per file build options override
    options and to take advantage of special compiler options available on some target hardware platforms The build variables are usually supplied through shell variables make options or mk conf so original build infrastructure can remain clean of hacks Most build options can be applied globally to the whole NetBSD userspace or to some library program or source file for example but sometimes the special options need a few exception within the source tree This is where per source file build options override comes in handy Per source file build option override For example the CPUFLAGS build variable can be changed to depend on the source file being compiled CPUFLAGS source file name without white space and extension mnormal arch DEF CPUFLAGS mspecial arch CPUFLAGS CPUFLAGS IMPSRC T R U DEF CPUFLAGS nbmake When the BSD make builds a C file or the build command uses the CPUFLAGS variable a check is made if a variable named CPUFLAGS source file name without white space and extension exists If this variable exists its contents is used as CPUFLAGS and if it does not exist DEF CPUFLAGS is used instead See make manual for more variable name filters regexp possibilities and other predifined

    Original URL path: http://wiki.netbsd.org/tutorials/per_file_build_options_override/ (2016-02-01)
    Open archived version from archive

  • pkgsrc
    Security Community Blogs Mailing lists List archives Developers Browse source Cross reference Release engineering Projects list Ports History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki tutorials pkgsrc Upgrading packages with pkg comp and pkg chk Using pbulk to create a pkgsrc binary repository Speeding up pkgsrc builds with ccache and distcc Distributing pkgsrc builds across different OSes Using clang with pkgsrc

    Original URL path: http://wiki.netbsd.org/tutorials/pkgsrc/ (2016-02-01)
    Open archived version from archive

  • build ccache distcc
    called hostA and hostB First install the software on both machines cd usr pkgsrc devel distcc make install clean cp usr pkg share examples rc d distccd etc rc d Configure some parameters in order to allow hostA and hostB to use each other s distcc instances hostA s IP address is 192 168 1 1 hostB s IP address is 192 168 1 2 hostA grep distcc etc rc conf distccd YES distccd flags allow 192 168 1 0 24 allow 127 0 0 1 listen 192 168 1 1 log file home distcc distccd log hostB grep distcc etc rc conf distccd YES distccd flags allow 192 168 1 0 24 allow 127 0 0 1 listen 192 168 1 2 log file home distcc distccd log Instead of sending logs to syslog we will use a custom logfile located in distcc s user home directory mkdir home distcc chown distcc home distcc We can then fire up distcc on both hosts etc rc d distccd start In order to use hostnames instead of their IP addresses add them to both etc hosts tail 2 etc hosts 192 168 1 1 hostA 192 168 1 2 hostB And finally tell pkgsrc to use distcc along with ccache by adding these lines to etc mk conf on both machines PKGSRC COMPILER ccache distcc gcc DISTCC HOSTS hostA hostB MAKE JOBS 4 Here we define MAKE JOBS to 4 because we are using two single CPU hosts The recommended value for MAKE JOBS is number of CPUs 2 to avoid idle time Testing To see distcc in action simply watch the home distcc distccd log file while you are building a package tail f home distcc distccd log distccd 5218 dcc job summary client 192 168 1 1 64865 COMPILE

    Original URL path: http://wiki.netbsd.org/tutorials/pkgsrc/build_ccache_distcc/ (2016-02-01)
    Open archived version from archive

  • clang
    Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki tutorials pkgsrc clang When building NetBSD you can set MKLLVM yes to also build clang and install it and additionally HAVE LLVM yes if you want to use it to compile NetBSD itself during build sh When you have a NetBSD compiled this way you can set PKGSRC COMPILER clang CLANGBASE usr HAVE LLVM yes in your etc mk conf

    Original URL path: http://wiki.netbsd.org/tutorials/pkgsrc/clang/ (2016-02-01)
    Open archived version from archive

  • cross compile distcc
    anoncvs anoncvs fr netbsd org cvsroot co rnetbsd 5 1 2 RELEASE src We will then use the build sh script in order to build the tools needed for cross compiling cd src build sh m amd64 tools Do not use the u flag as we need to configure nbcompat for the tools to build correctly Once finished you should have a directory like tooldir Linux 2 6 32 5 xen amd64 x86 64 On the src directory This is where the cross compiling toolkit resides Installing and configuring distcc It is mandatory to configure distcc so it uses our cross comping tools to build binaries for another platform On a Debian system this is done in etc default distcc STARTDISTCC true Allowed networks ALLOWEDNETS 127 0 0 1 192 168 0 0 24 IP where distcc will listen LISTENER 192 168 0 7 Here s the real trick supersede PATH so the firsts binaries distcc will look for are NetBSD s ones PATH home netbsd src tooldir Linux 2 6 32 5 xen amd64 x86 64 x86 64 netbsd bin PATH After that simply start distcc etc init d distcc start Testing the setup On a NetBSD machine located in distcc s allowed network add the following to etc mk conf PKGSRC COMPILER ccache distcc gcc MAKE JOBS 4 DISTCC HOSTS 192 168 0 7 localhost And fire up the make command in a pkgsrc subdirectory containing a C based package You should see something like this in helper s var log distccd log file distccd 20634 dcc job summary client 192 168 0 2 64006 COMPILE OK exit 0 sig 0 core 0 ret 0 time 57ms gcc usr pkgsrc misc tmux work ccache cache tmp unvis tmp bulkor 18298 i distccd 20734 dcc job summary client 192

    Original URL path: http://wiki.netbsd.org/tutorials/pkgsrc/cross_compile_distcc/ (2016-02-01)
    Open archived version from archive