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".
  • Make /boot.cfg handling machine independent
    file Examples are i386 amd64 which share a bootloader and sparc64 However they do not share code nor even the basic command parser Obviously this is not the NetBSD way to do things and the situation needs to be improved The milestones of this project split the machine dependent parts out provide generic machine independent support for most of the boot cfg handling leave configuration like what commands are allowed

    Original URL path: http://wiki.netbsd.org/projects/project/common-boot-cfg/ (2016-02-01)
    Open archived version from archive


  • Compressed Cache System
    projects project Compressed Cache System Contact tech embed Duration estimate 2 months NetBSD version of compressed cache system for low memory devices http linuxcompressed sourceforge net RSS Atom Compressed Cache Details Hi I am interested in working on this project I would like to know if any work is being done with respect to this project Any response and pointers would be greatly appreciated Thanks Vinay Comment by Vinaykumar in

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

  • Support pkgsrc cross-bootstrapping
    Duration estimate 3 months pkgsrc duplicates NetBSD efforts in maintaining X org packages pkgsrc X11 being able to cross build could replace base X11 distribution The latter decoupling should simplify maintainance of software updating X11 and associated software becomes easier because of pkgsrc s shorter release cycle and more volatility Cross buildable and cross installable pkgsrc tools could also simplify maintainance of slower systems by utilising power of faster ones

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

  • Create a cross-compile environment package for pkgsrc on NetBSD
    NetBSD Wiki projects project Create a cross compile environment package for pkgsrc on NetBSD Contact tech pkg Duration estimate 3 months The goal of this project is to generate a package or packages that will set up a cross compiling environment for one slow NetBSD architecture on another fast NetBSD architecture starting with and using the NetBSD toolchain in src The package will require a checked out NetBSD src tree or as a refinement parts thereof and is supposed to generate the necessary cross building tools using src build sh with appropriate flags for the necessary usr include and libraries of the slow architecture build these to fit or use the slow architecture s base tgz and comp tgz or parts thereof As an end result you should e g be able to install the binary cross pkgsrc NetBSD amd64 to atari package on your fast amd64 and start building packages for your slow atari system Use available packages like eg pkgtools pkg comp to build the cross compiling environment where feasible As test target for the cross compiling environment use pkgtools pkg install which is readily cross compilable by itself If time permits test and fix cross compiling pkgsrc

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

  • CVS Migration for NetBSD repos
    git hg fossil has already been done which is why we are able to now ask how would the project continue to function Our decision matters You re reading this because you care about the future of NetBSD and you understand that good tools act as a force multiplier Our decision is not obvious If it were we d have made it already and wouldn t be disagreeing so persistently about which one it needs to be Our decision needs to be about the whole elephant We all understand the basics of using source control This level of understanding is necessary but not sufficient to make an informed decision about whether to migrate any or all of NetBSD s repositories to another VCS and if so which or how Our choice of VCS carries implications not only about how developers hack on NetBSD but also about how non developers contribute and become developers and how Project sysadmins keep our valuable code secure Therefore any choice of VCS other than the default sticking with CVS for a while longer necessarily implies that as a group we all need to learn how we re going to do what we expect to need to do Not all of this learning needs to happen before we can make a reasonably confident decision for our Project But if we want to arrive at consensus much of it does There is no available choice of VCS that entirely avoids tradeoffs for us Therefore to choose intelligently we must first consider all the tradeoffs we can think of then decide which ones we can live with and which we can not Our decision needs to be made together We re a community The only way a complicated interconnected set of changes like this can be implemented is

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

  • Defragmentation for FFS
    for FFS Contact tech kern Heavily used file systems tend to spread the blocks all over the disk especially if free space is scarce The traditional fix for this is to use dump newfs and restore to rebuild a volume however this is not acceptable for current disk sizes The resize ffs code already contains logic for relocating blocks as it needs to be able to do that to shrink

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

  • Desktop infrastructure
    adopt system level design decisions that we don t want Rather than chase after Linux compatibility we are better off designing the system layer and infrastructure components ourselves It is easier to place poorly conceived interfaces on top of a solid design than to reimplement a poorly conceived design Furthermore if we can manage to do a few things right we should be able to get at least some uptake for them The purpose of this project per se is not to implement any particular piece of infrastructure It is to identify pieces of infrastructure that the desktop software stacks need from the operating system or provide themselves but ought to get from the operating system figure out solid designs that are compatible with Unix and traditional Unix values and generate project descriptions for them in order to get them written and deployed For example GNOME and KDE rely heavily on dbus for sending notifications around While dbus itself is a more or less terrible piece of software that completely fails to match the traditional Unix model rather than doing one thing well it does several things at once pretty much all badly it is used by GNOME and KDE because there are things a desktop needs to do that require sending messages around We need a transport for such messages not a reimplementation of dbus but a solid and well conceived way of sending notices around among running processes Note that one of the other things dbus does is start services up we already have inetd for that but it s possible that inetd could use some strengthening in order to be suitable for the purpose It will probably also need to be taught about whatever message scheme we come up with And we might want to e g

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

  • Graceful USB disk detach/reattach
    History Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki projects project Graceful USB disk detach reattach Contact tech kern Mentors Matthias Drochner David Young Duration estimate 3 months Make NetBSD behave gracefully when a live USB FireWire disk drive is accidentally detached and re attached by for example creating a virtual block device that receives block read write commands on behalf of the underlying disk driver This device will delegate reads and writes to the disk driver but it will keep a list of commands that are outstanding that is reads that the disk driver has not completed and writes that have not hit the platter so to speak Milestones Provide a character device for userland to read indications that a disk in use was abruptly detached Following disk re attachment the virtual block device replays its list of outstanding commands A correct solution will not replay commands to the wrong disk if the removable was replaced instead of re attached Open questions Prior art Isn t this how the Amiga worked How will this interact with mount unmount is there a use count on devices Can you leverage wedges in your

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