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".
  • bsd make
    t get created Installing neatly to a user customisable path can be done most cleanly like this PREFIX usr local BINDIR PREFIX bin LIBDIR PREFIX lib MANDIR PREFIX man FILESDIR PREFIX share misc Added advantage is that this will work out of the box on pkgsrc and FreeBSD s ports since these define PREFIX to be their installation paths Switch manpage generation installation on and off with MKMAN by setting it to yes or no Make include files types of projects bsd prog mk programs Expects a manpage of the name PROG 1 if MAN is not defined Initialise MAN to an empty value if you do not have a manpage PROG foo SRCS foo c MAN include bsd prog mk bsd lib mk libraries Does not create shared libraries unless you define SHLIB MAJOR variable LIB this SHLIB MAJOR 1 SHLIB MINOR 0 include bsd lib mk You may define SHLIB TINY variable too Alternatively you may define variables in shlib version file major 0 minor 1 where the 0 and 1 are replaced by the appropriate version numbers of course bsd man mk manpage stuff You can automatically have BSD Make create symlinks to your base manpages by defining MLINKS as a list of manpage 1 linkname 1 tuples separated by spaces Example MLINKS real foo 3 foo 3 real foo 3 other foo 3 Here real foo 3 is a real file the rest are all links that will be created in the installation path Manpages must have an extension to identify their category or installation will fail Special constructs Special constructs if for include etc must have their dot flush left aligned The word after the dot may be indented however You can check the current target being built by make with if make targname blah

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


  • bugtracking
    not changed much since I got behind on it if anything it s dropped What this means is that the rate PRs are getting fixed has dropped and that s because it s become impossible to find anything again It seems to me that one of the chief things we want from a new bugtracker is to be able to provide something like this browseable index Therefore it must be able to support the kinds of metadata that the buglists tree was using If we move to a bugtracker without this support it may solve some of the more glaring problems with gnats but it isn t going to help us find stuff in the bug database and it isn t going to do anything to help make the large backlog of unfixed bugs go away Metadata types After working the bug database for some years and also after maintaining the buglists pages I ve come to the conclusion that we need the following types of metadata fields containing tags fields containing one of an enumerated list of choices fields containing a classification according to a hierarchical taxonomy fields containing free form text And also importantly we need arbitrarily many such fields not a fixed set concocted at the time the database is set up Tags A tag field contains zero or more entries from a list of allowable choices This is a well understood concept and most bug databases support tags in one way or another however I don t think most support arbitrarily many different tags fields with their own sets of allowable tags Two questions immediately arise from this description why do we need to restrict tags to allowable values and why do we need multiple tags fields instead of just one The first question is easy when you have a database of 50 000 things you need to place some controls on what gets entered or you eventually end up with trash This is just a fact of life with databases when they get big enough We have enough problems without having to deal with misspelled tags and typos The second follows partly from the first and partly from ensuing human interface concerns if you just have one tags field the number of possible tag values grows without bound as more and more tags get added and before too long the list becomes itself hard to work with Grouping tags into logical sets e g all releng tags for which bugs are critical for which releases in one field makes it much easier to search for them and also much easier to browse the database looking for bugs that aren t tagged but should be Also this makes it possible to have developer only tag fields private personal tags and so forth without undue complications Enumerations An enumeration field contains exactly one entry from a list of allowable choices This differs from a tag field in certain obvious ways We already have some of these in gnats but they re hardcoded fields rather than being instances of a general metadata type If we re going to have arbitrary metadata fields at all rather than a fixed set of predefined fields we more or less need enumeration fields to be able to migrate the existing database Also some things that one might abuse tags for if one only had tags are perhaps better handled as enumerations e g no bug should be both critical for a release and also would be nice for the same release That said a bugtracker that only has tags fields is probably adequate though not entirely desirable because one can abuse tags instead Hierarchical taxonomy A hierarchical taxonomy is a scheme for identifying and thus finding things based on a nested series of choices The hierarchical taxonomy most people are most familiar with is probably the scheme for species in biology That especially in its more modern forms is more complex than we need but the basic principle is the same at the top you have everything and then you pick one of several kinds of things and then you re dealing with a restricted subset and so forth until you get down to a manageable number of things to look at at once that all have similar properties The buglists pages supported tags as well but were fundamentally based on a hierarchical classification of bugs based on where in the system they occur This as noted above has been extremely useful in practice There is another hierarchical taxonomy that I d like to deploy but which I wasn t about to try to do without better tools classifying bugs based on their symptoms If we were going to pick just one of these metadata features that s the most important it would be this The problem is most bugtrackers do not support hierarchical taxonomies In fact so far no existing bugtracker has been found to do so This is an extremely important point because it means that we need to find a way to do it This is going to involve writing code either new code or an extension to some bugtracker we otherwise like Free form text Free form text fields have two uses one is for enumerations where the set of things being enumerated is too large to be manageable as an enumeration e g pkgsrc packages or NetBSD version numbers or programs in usr bin and the other is for text that we think text retrieval tools will be able to process usefully I have no examples of the latter kind on hand but I expect some will appear there are several of the former kind that we definitely want to be able to support One is the pkgsrc package by pkgpath a PR is about not all pkgsrc PRs apply to only one package but most do Another for base system PRs is the name of the man page most closely associated with what s broken This

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

  • stuff we dislike about gnats
    to clean up the consequences gnats accepts a wide range of misformatted incoming PRs then mangles them further and drops them into an internal queue needing manual attention gnats fairly frequently belches on incoming mail requiring intervention from admins By default gnats does not treat incoming confidential PRs as confidential it requires manual filtering in the surrounding email logic gnats has no support whatsoever for automatically handling bounced mail There s no way to disable sending mail to email addresses that are known to be invalid When a bug is closed there s no way to disambiguate from its closed state whether it s fixed invalid obsolete or otherwise won t fix User interface gnats has no ability to do anything by web besides display PRs and they display only as plain text Things that you should be able to do that you can t include filing comments browsing from one PR to other related ones either explicit links from one PR to another or retriving other PRs with similar properties subscribing to PRs to get updates even by email let alone by RSS The only way to do administrative operations is to run an editor on the backend text file representation of a single bug This means you can t readily massedit PRs e g put a lot of related PRs in feedback at once update someone s email address move misfiled comments from one PR to another But you can t file a comment on a PR from the command line you have to send email The nag mails that gnats sends to submitters are annoying to handle in particular just replying to them does not go anywhere useful The nag mails that gnats sends to developers list a bunch of PRs but do not list them in

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

  • comments
    but inside this dir there is not a vim package However I can see two vim packages one for each of these paths ftp ftp netbsd org pub pkgsrc packages NetBSD earmv6hf 7 0 2015Q2 All ftp ftp netbsd org pub pkgsrc packages NetBSD earmv6hf 7 0 2015Q3 All Said that my question is Did I messed up the selection of the mirror Why only the first path had all the dependecies needed by pkgin I am sorry I do not remember which package was missing Can I and should I add all the three paths to install other packages For those interested I wrote down all the steps I followed during installation https blog apsu it netbsd rpib1 install Regards agz Comment by aggaz late Sunday evening January 10th 2016 Remove comment NetBSD working on the Raspberry Pi Zero Trying to boot the latest snapshot on my Pi Zero resulted in 8 flashes of the OK ACT LED bootcode bin and or start elf problems according to the documentation This image boots fine on my Pi B and Pi 2 I over wrote bootcode bin start elf and start cd elf on the freshly imaged SD card from an Arch Linux MicroSD that works in the Pi Zero It now boots I don t know if these are exactly the correct files but I suspect they likely require updating in the base image I ve included MD5 sums of the files for your convenience From the NetBSD Image 20151231 MD5 bootcode bin 9a4ad6a12ad7dc1aae279888c25d2252 MD5 start elf a2c4b9ea3ae986f88ea01e05bef46904 MD5 start cd elf 85924312c9b51d1ef5b7ca301bb18d54 Files I copied over that make it bootable from my Arch Linux Pi Zero environment MD5 bootcode bin 6cc6560c0178c10928d14b8768969dab MD5 start elf f5b2a422d863efe5d47b1ac291ccaa3a MD5 start cd elf f0dfc1462c5d9b003b64428fd52406ed Hope this helps Comment by ax0n in the wee hours of Friday night January 2nd 2016 Remove comment Accelerated X Just wondering whether anyone is working on porting either xserver xorg video fbdev or xf86 video fbturbo to NetBSD It would be great to have an accelerated X driver I d be more than happy to test any driver that is being worked on Comment by nickdate Thursday afternoon December 24th 2015 Remove comment Philips Freevents laptop Works well up to and including NetBSD5 NetBSD6 is slow NetBSD7 is unusably slow when networking is enabled giving lots of sdmmc0 couldn t enable card 60 messages Disabling that driver in boot c causes debugger breaking points in the mmc interrupt handler Comment by Nigel Wednesday night December 16th 2015 Remove comment Does the DS3231 RTC module works Hi I am kaku How can I use the DS3231 RTC module for raspberry pi Thank you very much Comment by hchguoyq at lunch time on Wednesday December 16th 2015 Remove comment A note on ccache and pkgsrc If you update the PKGSRC COMPILER value to include ccache as the wiki states it does use it but it creates a new ccache directory under each packages work subdirectory So any use of make

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

  • pending
    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 comments pending RSS Atom QBA 1 800 860 9230 QUICKBOOKS HELP DESK PHONE NUMBER QUICKBOOKS PRO SUPPORT PHONE NUMBER this comment needs moderation Comment by Anne late Wednesday evening January 20th 2016 Remove comment bananapi console this comment needs moderation

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

  • curses in netbsd
    last operating systems or even the last one not using ncurses As curses is not as specified as you could wish there are some differences to consider Note This article covers curses as well as libform and libmenu which are bundled together with ncurses This is meant to be an naturally incomplete list of what the programmer has to care for new item 3 in NetBSD s curses copies the

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

  • dev
    NetBSD 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 dev null Add a comment Last edited at teatime on Sunday May 26th 2013 Preferences

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

  • null
    Edit Comment Source History New RecentChanges NetBSD Wiki dev null The big void See the archive of older posts RSS Atom Add a new post titled NetBSD 6 1 Released The NetBSD Project recently released version 6 1 of the NetBSD operating system In addition to many stability fixes it provides an improved NPF NetBSD s new packet filter with symmetric multiprocessing support The NetBSD 6 1 release also had various hardware driver additions including LSI Thunderbolt SAS2208 controllers Apple s Thunderbolt to Gigabit Ethernet adapter Hydra and ASDG Zorro2 bus network cards and USB and onboard Ethernet support for the Raspberry Pi Also the LSI Logic Dell MegaRAID SAS RAID controller can now be managed on NetBSD using the MegaCLI Linux binary The flock tool was added inspired by the Linux program of the same name and support for touchscreen calibration was addedto wsconsctl For more information see http www netbsd org releases formal 6 NetBSD 6 1 html Posted late Tuesday night May 29th 2013 Comment sei Numero Sei Posted late Sunday afternoon May 26th 2013 1 comment altre terre lower case Posted at teatime on Sunday May 26th 2013 Comment IMPORTANT No upper case letters in blog

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