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".
  • how to use anti-aliased fonts in linux emulation
    fonts in linux emulation Contents Introduction Fixing the problem Installing Linux fontconfig Running fc cache If it doesn t work Introduction This problem is most common when someone installs a browser in linux emulation for example www opera which is only avalible through linux compat Fixing the problem The problem is that the emulated Linux system s font cache is empty thus you can t use your fonts installed in NetBSD Its quite easy to fix actualy Installing Linux fontconfig Look for which package you will need pkgfind fontconfig grep emulators emulators suse100 32 fontconfig emulators suse100 fontconfig Linux compatibility package for fontconfig emulators suse91 32 fontconfig emulators suse91 fontconfig Linux compatibility package for fontconfig You will need emulators suse100 fontconfig on i386 and suse100 32 fontconfig on amd64 architecture FIXME Install it from packages or from pkgsrc You can find more on installing in the documention or in the wiki Running fc cache The only thing you have to do after installing it is the following usr pkg emul linux usr bin fc cache It will regenerate the font cache in the compat system To ensure fonts have been cached in the compat system you can use the following

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


  • how to use encrypted swap over nfs
    1m count 64 This will create a 64MB swapfile Make sure it has the right permissions and owner chown root wheel usr swapfile chmod 600 usr swapfile Configuring the swapspace the first time Now we just have to configure it so the system can use it Configure the paramsfile for cgd 4 cgdconfig g o etc cgd swapfile V none k randomkey blowfish cbc Now we can configure the device vnconfig vnd0 usr swapfile cgdconfig cgd0 dev vnd0c etc cgd swapfile Replace dev vnd0c with dev vnd0d if necessary Disklabel the cgd with disklabel I e cgd0 it will should look something like this dev rcgd0c type cgd disk cgd label default label flags bytes sector 512 sectors track 2048 tracks cylinder 1 sectors cylinder 2048 cylinders 64 total sectors 131072 rpm 3600 interleave 1 trackskew 0 cylinderskew 0 headswitch 0 microseconds track to track seek 0 microseconds drivedata 0 3 partitions size offset fstype fsize bsize cpg sgs c 131072 0 swap Cyl 0 63 Note Depending on which archictecture you use you may need a different layout Like this on an i386 a 131072 0 swap Cyl 0 63 d 131072 0 unused 0 0 Cyl 0 63 Depending on which partition your architecture uses as raw partition If unsure check with sysctl kern rawpartition kern rawpartion 3 Back it up so it can be used later disklabel cgd0 etc cgd swapfile disklabel Use it finally swapctl a dev cgd0c Now you have working encrypted swap over nfs To check its status swapctl l Device 512 blocks Used Avail Capacity Priority dev cgd0c 131072 9696 121376 7 0 Use the swapspace at every reboot Using this swapspace automatically at every reboot is a little tricky since it can not be put int etc fstab but it can be done in another way And I have already done the work for you Check that the variables make sense on your system E g that you used vnd0 and cgd0 and RAW PART is right for your architecture Create the file etc rc conf d swap containing the following Initialize cgd over vnd swap suitable for nfs swap Note We can NOT put this swapfile in etc fstab this is why this is relatively complicated If this is the only swapspace you have configured then you can set no swap YES in rc conf otherwise the system will complain every boot IMPORTANT swapfile has to be in critical filesystems remote usr is by default vnd device vnd0 cgd device cgd0 swapfile usr swapfile paramsfile etc cgd swapfile swap disklabel etc cgd swapfile disklabel RAW PART c change to suit your arch SWAP PART c change to same as the disklabel start postcmd cryptovnd swap stop cmd cryptovnd stop Note We have to override stop cmd cryptovnd swap Since there is only one swap variable in rc conf we have to check that we are being called from swap2 if name swap1 then return fi if f swapfile then echo Configuring

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

  • how to use fuse in netbsd
    s why we use src foo bar i e src lib libpuffs instead of full path Setup Make sure that your Kernel configuration file contains the following option under filesystem file system PUFFS And this under pseudo devices pseudo device putter Add this to your etc mk conf MKPUFFS yes Build your kernel and update your userland Make sure you run make includes in your source tree in src sys if you at some point update your NetBSD sources so that you have proper header files Most importantly the src lib libpuffs headers cd src sys make USETOOLS no includes cd src lib libpuffs make USETOOLS no includes Check if libpuffs is properly installed cd src lib libpuffs make USETOOLS no cleandir dependall make USETOOLS no install Check if librefuse is properly installed cd src lib librefuse make USETOOLS no cleandir dependall make USETOOLS no install Check if fusermount is up to date and installed cd src usr sbin fusermount make USETOOLS no cleandir dependall make USETOOLS no cleandir install Check if puffs is up to date and installed cd src usr sbin puffs make USETOOLS no cleandir dependall make USETOOLS no install This will compile and install mount 9p

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

  • how to use iscsi to support an apple time machine
    v 1 2 2012 02 05 07 14 36 schmonz Exp Structure of this file an extent is a straight offset length pair of a file or device it s the lowest common storage denominator at least one is needed a device is made up of one or more extents or other devices devices can be added in a hierachical manner to enhance resilience in this example no device definitions are necessary as the target will just use a simple extent for persistent storage a target is made up of 1 or more devices The code does not support RAID1 recovery at present Simple file showing 1 extent mapped straight into 1 target extent file or device start length extent0 tmp iscsi target0 0 100MB target flags storage netmask target0 rw extent0 0 0 0 0 0 The target should be the name of a file in the filesystem you want it to reside in When the iscsi target daemon first runs over this configuration targets are initialized as UNIX sparse files Be very careful not to touch this file with a cp or any other operation which tickles NetBSD into filling in the holes in the sparce file dump and tar should be safe as is rsync if the S flag is given to it see sparse files below The etc iscsi target file can implement simple ACL models for the IP network prefix of the client s you wish to permit The default in this file as distributed is a fully open iSCSI target There is an associated etc iscsi auth file which can be used to instantiate CHAP and other protections over the iSCSI attachment by the client Be warned that the target name has to include a digit which will be translated to the SCSI LUN number of the device for the client Unless you know what you are doing its best to leave this as 0 since the client may well demand only LUN0 is used Once you have configured a target you need to enable and start the iscsi target daemon Edit etc rc conf and enable iscsi target YES and then you can run etc rc d iscsi target start it will start automatically on reboot once enabled in etc rc conf Install iSCSI initiator fetch the DMG mount install reboot required Configure the initiator open System Preferences and select globalSAN It will throw a warning about restart Don t worry it just flicks you to the correct system Preference pane select the Targets tab and use the button to add a new target provide the name or IP address of your NetBSD iSCSI target If you didn t alter the port it serves from don t alter the port here select Header Digest by default enable the mount This will cause OSX to detect a new raw device and ask you what to do with it You should select Initialize to enter the OSX disk utilities pane OSX is then initializing this

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

  • how to use lvm on netbsd
    to build with flag MKLVM set to yes cd usr src build sh u U V MKLVM yes tools distribution sets After successful build update your system with them You can also run make install as root in src external gpl2 lvm2 to install userland part of LVM into the existing NetBSD system There is also simple driver used by LVM2 tools in our kernel in src sys modules dm you have to install and load this driver before you test lvm The NetBSD LVM uses same tools as Linux and therefore we have the same user interface as is used in many common linux distributions Howto compile new kernel Kernel compilation procedure is described here http www netbsd org docs guide en chap kernel html chap kernel build sh To get device mapper compiled in kernel you have to add this option to kernel config file pseudo device dm Using new MODULAR modules There are two versions of modules in NetBSD now old LKM and new MODULAR modules New modules are build in sys modules All GENERIC kernels are compiled with support for new modules There is reachover makefile for dm driver in sys modules dm You can use it to build dm module For loading new style modules new module utils are needed You need to add MKMODULAR YES to etc mk conf and build modload modstat and modunload Compile lvm2tool and libdevmapper To get lvm working it is needed to compile and install linux lvm tools They are located in external gpl2 libdevmapper external gpl2 lvm2tools Only make make install is needed to build install tools to machine Tools are not integrated in to lists and build system now Therefore it is possible that when you try to add them to build process it will fail with

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

  • how to use midi devices with netbsd
    cloning Supported on many ISA cards and following PCI cards C Media CMI8738 cmpci 4 support broken in NetBSD 4 0 ESS Solo 1 eso 4 ForteMedia FM801 fms 4 Yamaha DS 1 yds 4 Usually MPU interfaces are conncted to MIDI Joystick port on sound cards You won t be able to play receive anything unless you connect some external MIDI device to such port Though in some rare cases MPU interface is connected to on board daughterboard WaveTable MIDI engine See mpu 4 Simple MIDI interfaces Simple MIDI interfaces are supported on many ISA cards and following PCI cards Cirrus Logic CS4280 clcs 4 Creative Labs SoundBlaster PCI Ensoniq AudioPCI based eap 4 Trident 4DWAVE and compatibles autri 4 Usually simple MIDI interfaces are connected to MIDI Joystick port on sound cards You won t be able to play receive anything unless you connect some external MIDI device to such port Note MIDI port and synth on SoundBlaster Live and newer cards by Creative is unsupported USB MIDI devices Many USB MIDI devices are supported Synth modules keyboards and MIDI interfaces are handled well See umidi 4 Yamaha OPL2 and OPL3 Popular single chip FM synthesizer Almost all ISA cards come with such chip Some of the newer cards have compatbile FM engine too PCI cards based on following chipsets have it C Media CMI8738 cmpci 4 opl support broken in NetBSD 4 0 ESS Solo 1 eso 4 ForteMedia FM801 fms 4 S3 SonicVibes sv 4 Yamaha DS 1 yds 4 NetBSD opl driver has built in General MIDI instrument definitions so your system is ready to play without additional configuration Note New PCI cards by Creative Labs do not have this chip See opl 4 Identifying MIDI devices You can easily discover what kind of MIDI

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

  • how to use no bitmapped fonts
    Emulators Packages Browse packages Release engineering Wiki Home Edit Comment Source History New RecentChanges NetBSD Wiki tutorials how to use no bitmapped fonts Create local conf in usr pkg etc fontconfig xml version 1 0 DOCTYPE fontconfig SYSTEM fonts dtd fontconfig include conf d 70 no bitmaps conf include fontconfig There referenced file 70 no bitmaps conf doesn t exist in conf d and therefore have to be copied there

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

  • how to use nokia 6230i over bluetooth as a gprs modem
    The Access Point Name APN used by your GSM Operator may need to be different from the internet used below pty rfcomm sppd a phone d ubt0 s DUN m encrypt connect usr sbin chat V f etc ppp chat gsm U internet T 99 noccp Configuring Bluetooth First activate Bluetooth on your phone on the Nokia 6230i as follows Menu Settings Connectivity Bluetooth Bluetooth settings My phone s name Choose a name for your device for this example I will use My Nokia Menu Settings Connectivity Bluetooth Bluetooth settings My phone s visbility Choose Shown to all Menu Settings Connectivity Bluetooth Bluetooth Choose Bluetooth on Plug your Bluetooth dongle into your computer and you should see something like the following on the console ubt0 at uhub0 port 1 configuration 1 interface 0 ubt0 Broadcom BCM92035DGROM rev 1 10 0 04 addr 2 Now we need to establish a Bluetooth connection between your phone and computer Enable the Bluetooth dongle etc rc d btconfig start Configuring Bluetooth controllers ubt0 and perform an inquiry to discover the Bluetooth device address of your phone btconfig ubt0 inquiry Device Discovery from device ubt0 1 response 1 bdaddr 00 22 b3 22 3e 32 name My Nokia Add an alias of the bdaddr yours will be different to etc bluetooth hosts echo 00 22 b3 22 3e 32 phone etc bluetooth hosts Next set up a PIN in order to pair the phone with your Bluetooth dongle btpin a phone r l 6 PIN 928434 and attempt to open a manual RFCOMM connection to the Dial Up Networking DUN service on the phone press C to close the connection rfcomm sppd a phone s DUN Starting on stdio AT OK ATI Nokia ATI3 Nokia 6230i OK C Your phone should prompt you for accepting

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