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".

  • sysctl 8 variables to set at boot time Default core name template kern defcorename n core Number of kernel threads to use for NFS client vfs nfs iothreads 4 net

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


  • null
    Foundation Advocacy Documentation FAQ HOWTOs The Guide Manual pages Wiki Support Problem report guide Report a bug Query bug database 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 null The big void Add a comment Last edited at teatime on Sunday May 26th 2013

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

  • OpenSoundSystem
    Home Edit 1 comment Source History New RecentChanges NetBSD Wiki OpenSoundSystem Open Sound System for NetBSD This page shows the progress of the porting of OSSv4 to NetBSD Version The current version is v4 2 hg 889 Status DMA ported not complete PCI config access complete PCI mapping ported to bus space INB OUTB incomplete should use bus space 9 module support WIP Locking ported to mutex 9 MALLOC ported to kmem 9 getid ported to kauth 9 pkg incomplete compat audio not yet FAQ What works Loading osscore kmod works Loading virtal drivers work No functional testing has been done yet Who is working on it ahoka Where to get it You will need devel mercurial and lang gawk and devel gmake to build it Browse online http bitbucket org ahoka oss4 netbsd To get it hg clone http bitbucket org ahoka oss4 netbsd How to build it http www opensound com wiki index php Building OSSv4 from source I use this to build modules rm rf tmp ossbuild mkdir tmp ossbuild cd tmp ossbuild home ahoka mercurial opensound com configure gmake build cd prototype usr lib oss build sh install sh RSS Atom OSSv4 on NetBSD status update

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

  • optical media
    ways Using the package abcde abcde is an acronym for A Basic CD Encoder and is available from pkgsrc This package grabs a CD using the cdparanoia package for optimum readout quality and encodes the audio with selectable backends vorbis mp3 flac spx mpc wav and m4a Grab the disk using abcde d dev rcd0d o mp3 p P This will encode the disc track by track padding the tracknumbers

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

  • panic
    the swap partition At boot time the swap file coredump will be saved to var crash The following settings control this behaviour they are set by default in etc defaults rc conf you don t usually need to change those savecore yes savecore flags N netbsd z savecore dir var crash A gzip 1 compressed file will be available for analysis with gdb 1 Your swap partition must be at least the size of your physical RAM Your var crash partition must have sufficient space to hold the same file Example Crash Force Panic from WSCons via KVM Dell DRAC4 You can force a kernel panic from the console on amd64 i386 using the special key sequence Control Alt Esc Forcing the Kernel Panic from Console TODO You can then instruct the KDB to run a preliminary backtrace to get a general idea of what went wrong TODO You can then force a sync of the file system and and dump of the kernel memory into the swap partition TODO At reboot you will see the etc rc d savecore script archive and gzip the dump TODO You can then load the core dump into standard gdb 8 What Now You can submit the feedback as a PR to the NetBSD GNATS system If you wish to continue to debug you may find this article useful TODO NetBSD kernel developer cheat sheet Processing the CORE Dump Hubert Feyrer has a great guide to analyzing kernel panic core dumps at http www feyrer de NetBSD bx blosxom cgi index front tags gdb Additionally the following command below can be used to create a relatively useful backtrace localhost cd var crash localhost gunzip d gz localhost gdb symbols netbsd gdb quiet eval command file netbsd gdb eval command target kvm netbsd 1 core eval command bt eval command list eval command info all registers 2 1 Load new symbol table from netbsd gdb y or n y Reading symbols from netbsd gdb done 0 0xc047c9f8 in cpu reboot howto 256 bootstr 0x0 at usr src sys arch i386 i386 machdep c 927 927 dumpsys 0 0xc047c9f8 in cpu reboot howto 256 bootstr 0x0 at usr src sys arch i386 i386 machdep c 927 1 0xc01c3f2a in db sync cmd addr 1065223264 have addr false count 1071881791 modif 0xcc883c04 BINARY at usr src sys ddb db command c 1304 2 0xc01c45fa in db command last cmdp 0xc07dfe3c at usr src sys ddb db command c 926 3 0xc01c4856 in db command loop at usr src sys ddb db command c 583 4 0xc01c7320 in db trap type 1 code 0 at usr src sys ddb db trap c 101 5 0xc0478855 in kdb trap type 1 code 0 regs 0xcc883e3c at usr src sys arch i386 i386 db interface c 229 6 0xc047efe2 in trap frame 0xcc883e3c at usr src sys arch i386 i386 trap c 350 7 0xc010cb80 in calltrap 8 0xc047717c in breakpoint 9 0xc02e3676 in wskbd translate id 0xc0833ae0 type

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

  • How to use pkgsrc on Solarish (Illumos based)
    This page will cover the requirement to bootstrap pkgsrc successfully on Illumos based Solarish systems Prebuilt binaries a repository of packages is provided by Joyent so it is not necessary to go through this process unless by choice It is assumed that a copy of the pkgsrc files have been obtained and uncompressed ready to bootstrap OmniOS At the time of writing the latest build available was r151012 which had GCC 4 8 x available On a freshly installed system the only components needed to bootstrap pkgsrc successfully is GCC lint linker object files and header files pkg install gcc48 header linker lint object file header math pkgsrc can then be bootstrapped as normal Tribblix All that s required is for the develop overlay to be installed in order to successfully bootstrap pkgsrc on Tribblix zap install overlay develop OpenIndiana On the 151a8 development release of OpenIndiana the installation of GCC GNU binutils is required alongside lint object files and header files to bootstrap pkgsrc successfully pkg install illumos gcc gnu binutils system header developer library lint object file header math PATH opt gcc 4 4 4 bin usr gnu bin PATH pkgsrc bootstrap bootstrap OpenSXCE Comes with all necessary

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

  • faq
    reference Release engineering Projects list Ports History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki pkgsrc faq Frequently Asked Questions Is it normal for pkg add to complain when I use binaries built for NetBSD 5 1 on NetBSD 5 1 2 Yes pkgsrc is cross platform and there s no general way to distinguish minor revision from major one There re many systems that don t handle versions uniformly Heuristics are complex and sometimes are really tricky e g NetBSD 5 1 2 is mostly compatible with NetBSD 5 1 but NetBSD 5 99 56 may be incompatible with NetBSD 5 99 55 We cannot embed all relevant knowledge into pkg add That s why you see e g pkg add Warning package bc 1 06nb3 was built for a platform pkg add NetBSD x86 64 5 1 pkg vs NetBSD x86 64 5 1 2 this host Since you know the versioning scheme of your system NetBSD in this case better than computer you can handle it better Hiding this information instead is wrong since sometimes incompatibilities even slight ones are critical hence the warning If you know that your

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

  • frequently asked questions from pkgsrc developers
    from pkgsrc developers Contents Questions Answers How can I get a list of all make variables that are used by pkgsrc When patching a GNU style configure script where should I add changes I m going to make incompatible changes to pkgsrc Where should I document it What s the difference between TEST test and See also Questions Answers How can I get a list of all make variables that are used by pkgsrc That s difficult But you can get a very good approximation by changing to a package directory and running the following command make dv show var VARNAME VARNAME sed n s Global 1 p sed s sort u grep A Z less Another possibility is to run bmake show all This will list many but not all variables If you need more information about a specific variable run bmake help topic VARNAME or have a look at pkglint s variable definition file When patching a GNU style configure script where should I add changes If you want your changes to override everything else then look for ac config files and put it somewhere before that line I m going to make incompatible changes to pkgsrc Where

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