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 run oracle express on netbsd
    NetBSD Wiki tutorials how to run oracle express on netbsd Oracle Express on NetBSD started by Emmanuel Kasper Oracle Express is a free beer version of the Oracle Database You are free to use it in production and to redistribute it but it has harcoded limits of use one CPU 1 GB of RAM and 4 GB for a table size Download the binary at http www oracle com technology software products database xe index html Convert the rpm in cpio format pkg add v rpm2cpio rpm2cpio pl oracle xe univ 10 2 0 1 1 0 i386 rpm oracle xe univ 10 2 0 1 1 0 i386 cpio Unpack the cpio archive it installs in usr lib oracle cpio idv oracle xe univ 10 2 0 1 1 0 i386 cpio Install the Suse linux environnment I don t need what exactly needed so I prefer to install all pkg add v suse 9 1nb3 Add oracle libraries to ldconfig library cache echo usr lib oracle xe app oracle product 10 2 0 server lib emul linux etc ld so conf emul linux sbin ldconfig Test sqlplus binary sqlplus nolog Right now we have a sqlplus binary that

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


  • how to run tet framework
    for example the patch ad still can be applied for distributed TET Porting to NetBSD Current opensourced version is 3 7a To download or check new versions look to the Links section below The guide was tested at least on the NetBSD current i386 and NetBSD current ARMv6 Patchset The simply patch would be applied before compilation is started Prebuild After applying patch you ll need to copy the proper makefile cp src defines UNTESTED freebsd mk src defines netbsd mk Make the TET ROOT directory like opt tet3 Copy content of TET sources tree to TET ROOT Notice to get distributed TET Create regular user tet on the target system with home path as TET ROOT without real shell Build Change working directory to TET ROOT Build framework configure t cd src make make install where means Lite t lite or Distributed t inet version of TET framework Notice to get distributed TET Change owner of the TET ROOT to tet recursively Update user s files Put to your profile TET export TET ROOT opt tet3 export PATH PATH TET ROOT bin System files correction distributed TET Start tccd daemon from the etc rc conf export TET ROOT opt tet3 if test x TET ROOT bin tccd then TET ROOT bin tccd echo TET3 tccd started fi Other files TET ROOT systems HOME systems equiv etc services are corrected in according to TET3 install guide Sample of required files You ll need a minimal TET ROOT systems file The following content in the file is enough for this test suite 000 localhost 60103 For the inet version of TET you ll need tccd running and a HOME systems equiv file in the directory of the user running tccd The following contents will do for this file Note In our

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

  • how to secure samba with stunnel
    etc stunnel stunnel pem Run chrooted as nobody chroot var run stunnel setuid nobody setgid nobody This file is created after chrooting pid stunnel Accept connections on port 800 on any interface smb accept 0 0 0 0 800 instead of port 139 port 445 will also work unless you re using Mac OS X clients connect localhost 139 As you can see you ll need an SSL certificate key This can be generated like this openssl req new nodes x509 out stunnel stunnel pem keyout etc stunnel stunnel pem Run stunnel Just add stunnel yes to your etc rc conf echo stunnel yes etc rc conf etc rc d stunnel start Warning stunnel is very silent Even if it gets an error it will just fail silently Check with pgrep if it s running Configuring your clients Unix clients On a Unix client you simply install and run security stunnel as described above You ll need to swap the port numbers and put it in client mode ie your stunnel conf should look like this client yes smb accept localhost 139 connect servername 800 This makes your client act as a samba server to which you can connect As soon as you connect to your machine the data is encrypted and forwarded to servername You can run stunnel from rc conf just like on the server side Of course you can easily test it by connecting to localhost smbclient U yoda localhost myshare Windows clients Connecting a Windows client to samba over stunnel is a major hassle Some background on why this is a problem is in order Apparently when Windows is booted the kernel binds a socket to port 445 on every real this is important as we ll see later on network interface This means that no other process can ever bind this port try it you ll get a permission denied message This would mean we need to use another port for our fake shared folder Unfortunately the Windows filemanager has no way to specify which port to use when you click map network drive so that s not an option Luckily for us Windows has the following odd behaviour When you click map network drive in the filemanager it will first try to connect to port 445 When it finds no service listening there it will try to fall back to port 139 Only when that has no service listening either it will tell the user it couldn t connect We will abuse this behaviour by tricking it into using this port Simply binding stunnel to port 139 is impossible because of the Windows behaviour where it binds ports 139 and 445 on every interface even if no actual files are being shared It turns out that it doesn t do this on loopback network devices To install one follow this set of instructions Open the add hardware wizard from the control panel Wait for it to search in vain for new hardware Tell it

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

  • how to set up a carp enabled firewall
    firewall suffers a failure or is taken offline the IP will move to one of the backups firewalls and the service will continue unaffected CARP supports IPv4 and IPv6 http www openbsd org faq pf carp html How do I enable CARP You can now use CARP assuming you re tracking the last developments 11 by adding the following line to your kernel configuration file pseudo device carp Then proceed to build re build your kernel Make sure you also build ifconfig 8 and netstat 1 and install of course Once you have built your kernel and installed it you re now ready for use Example configuration As mentioned earlier CARP is great for usage on firewalls I will show a popular and basic example here Assume the following lightly assume Internet Outside world firewall Shared LAN The obvious problem with this is that here the firewall is a single point of failure When it goes down for reasons such as Botched upgrade The other 100 reasons here it s normally tough luck Unless you fix it you have no internet in the majority of cases However with CARP we can now have something like this Internet Outside world em1 em1 Firewall 1 Firewall 2 em0 em0 Shared LAN When data comes from the Shared LAN destined for the outside world the two machines talk to each other and decided who s the MASTER and thus will handle the data So for example with the below configuration firewall 1 is the MASTER firewall and firewall 2 is the BACKUP If firewall 1 does down all traffic is automatically handled by firewall 2 completely transparent to the user Infact you could put an axe through firewall 1 anf nothing would change If firewall 1 then managed to recover is could then

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

  • how to set up a dhcp server
    your home or company network is pretty simple with NetBSD You don t need to install any software because everything you need is part of the base system Just create the file etc dhcpd conf like this deny unknown clients ddns update style none subnet 192 168 0 0 netmask 255 255 255 0 range 192 168 0 200 192 168 0 254 default lease time 28800 max lease time 86400 option broadcast address 192 168 0 255 option domain name mycompanydomainname com option domain name servers 194 152 64 35 194 25 2 132 option routers 192 168 0 1 host ftp server hardware ethernet 00 00 0a d8 39 ee fixed address 192 168 0 199 host sparc hardware ethernet 00 50 04 01 ee 20 fixed address 192 168 0 198 Now add the service to your etc rc conf This way the DHCP will be started on every reboot dhcpd yes dhcpd flags q ex0 ex0 is the Network Interface to listen on for dhcp requests This is important if you have more than one Network Interface If you don t you can omit the second line Before starting the service you have to create a

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

  • how to set up a guest os using xen3
    get more details about your actual interfaces Rebooting into DOM0 Time to reboot shutdown r now If all has gone well you should have booted into the XEN3 DOM0 kernel Check this with uname 1 uname v NetBSD 4 0 XEN3 DOM0 0 Sun Dec 16 01 20 31 PST 2007 builds wb34 home builds ab netbsd 4 0 RELEASE i386 200712160005Z obj home builds ab netbsd 4 0 RELEASE src sys arch i386 compile XEN3 DOM0 You should have XEN3 DOM0 mentioned somewhere Configuring rc scripts Copy or symlink xend xenbackendd and xendomains from usr pkg share examples rc d to etc rc d cp usr pkg share examples rc d xend etc rc d cp usr pkg share examples rc d xenbackendd etc rc d cp usr pkg share examples rc d xendomains etc rc d Edit etc rc conf and add the following lines xend YES xenbackendd YES xendomains dom1 Later on when you have created a configuration file for dom1 the xendomains variable specified above will trigger dom1 to be started when the system is booted At this point no configuration exists for dom1 therefore it does nothing at this point If you choose to name your configuration file something else adapt the name accordingly To avoid rebooting a second start all three services etc rc d xend start etc rc d xenbackendd start etc rc d xendomains start Run ifconfig a to ensure the bridge interface is present and issue a ps ax grep xen to ensure you have a similar output 12 DK 0 00 00 xenwatch 13 DK 0 00 00 xenbus 411 I 0 00 24 xenstored pid file var run xenstore pid 594 IWa 0 00 26 xenconsoled 629 IW 0 00 00 usr pkg bin python2 3 usr pkg sbin xend start 631 IWsa 0 00 02 usr pkg sbin xenbackendd 639 IWa 0 00 52 usr pkg bin python2 3 usr pkg sbin xend start The DOM0 configuration is now done We will proceed to configuring DOMU domains Configuring DOMU Configuring and installing a NetBSD DOMU Create or modify usr pkg etc xen dom1 and include this kernel usr src obj releasedir i386 binary kernel netbsd INSTALL XEN3 DOMU gz kernel netbsd XEN3 DOMU memory 64 name dom1 vcpus 1 disk phy dev wd0g 0x03 w file usr src obj releasedir i386 installation cdrom netbsd i386 iso 0x04 r vif bridge bridge0 root dev wd0d This configuration boots into the NetBSD sysinst program and allows you to install a NetBSD DOMU using the normal sysinst method This configuration uses a DOMU INSTALL kernel and an ISO image provided by a successful build release and build iso image You may be able to locate a valid Xen3 DOMU INSTALL kernel from ftp ftp netbsd org pub NetBSD daily but if not building a release is your best bet In this configuration file dev wd0g is the reserved partition for the guest operating system This should be changed to the partition you reserved prior to following the instructions within this document If you would like to use a physical CDROM instead of an ISO image change the disk line to disk phy dev wd0g 0x03 w phy dev cd0a 0x04 r Now boot into sysinst using the command xm create dom1 c The reserved partition will appear as dev xbd0 Proceed as you would with a normal NetBSD installation using xbd0 as the target drive and xbd1 as the CDROM When you have finished run shutdown hp now to dom1 Now edit usr pkg etc xen dom1 Comment the INSTALL kernel and uncomment the DOMU kernel You should now have a working NetBSD DOMU dom1 Boot into dom1 again with the command xm create dom1 c and ensure the file etc ttys contains only this line or has all other lines commented console usr libexec getty Pc vt100 on secure and the file etc wscons conf is completely empty or has all lines commented out These last two steps ensure no errors should be present on boot Setting wscons NO in etc rc conf may effectively do the same thing From here configure etc rc conf and all runtime configuration files as you would normally The network interface name should be xennet0 Use this name when configuring an IP address More information can be obtained by referencing the Xen user guide and the official NetBSD Xen Howto Questions can be addressed to the port xen NetBSD org mailling list Configuring and installing a Windows XP DOMU This requires an HVM capable processor and xentools see sections above This assumes you have a copy of the Windows install CD in home xen winxp iso and wish to create a file home xen winxp img to hold the install First create a blank file to hold the install This assumes a size of 4GB 4096M If you want a different size adjust the numbers to match dd if dev zero of home xen winxp img bs 1m count 4096 Create usr pkg etc xen win01 kernel usr pkg lib xen boot hvmloader builder hvm memory 400 device model usr pkg libexec qemu dm disk file home xen winxp img ioemu hda w file home xen winxp iso ioemu hdb cdrom r Hostname name win01 vif type ioemu bridge bridge0 boot d vnc 1 usbdevice tablet Helps with mouse pointer positioning You may want to modify the amount of memory and pathnames Ensure you have a vncviewer installed such as net tightvncviewer or net vncviewer from pkgsrc Then start the XENU and connect to it via VNC xm create usr pkg etc xen win01 vncviewer 0 This will boot the Windows ISO image and let you install Windows as normal As Windows reboots during install you may need to restart vncviewer After install change the boot d to boot c to have the system boot directly from the disk image Configuring and installing a GNU Linux DOMU We will do this in two steps

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

  • how to set up a samba server
    box for WindowsXP clients is really simple Install samba via pkgsrc cd usr pkgsrc net samba make install clean Start the services via etc inetd conf then uncomment the next two lines netbios ssn stream tcp nowait root usr pkg sbin smbd netbios ns dgram udp wait root usr pkg sbin nmbd Change it to this netbios ssn stream tcp nowait root usr pkg sbin smbd netbios ns dgram udp wait root usr pkg sbin nmbd Save the changes and restart inetd etc rc d inetd restart Now add the following lines to etc rc conf smbd YES nmbd YES samba YES You have to create a usr pkg etc samba smb conf with the following basic configuration workgroup some group server string NetBSD Samba Server hosts allow 192 168 1 192 168 0 encrypt passwords yes shared comment Shared path home ficovh mp3 browseable yes writable no valid users samba Add a valid user to the NetBSD system useradd samba Add a windows user to samba and set the password smbpasswd a U samba Now test the server with your Windows machine You can also browse the content from a windows machine with NetBSD smbclient smbclient ip windows shared

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

  • how to set up a samba server using swat
    on my NetBSD machine so that the machine s hard drive could be used for storage by the Windows PC s on the network The guest account is used for access and I won t go into how to set up users and passwords so this solution would probably be more suitable for home networks Install Samba and enable SWAT The first step is to fetch build and install Samba cd usr pkgsrc net samba make install clean Next put scripts in etc rc d so that smbd and nmbd will be started automatically when NetBSD boots up I simply used the example scripts that came with NetBSD cp usr pkg share examples rc d smbd etc rc d cp usr pkg share examples rc d nmbd etc rc d You also need to add the following lines to etc rc conf smbd YES nmbd YES SWAT can be enabled by adding the following line to etc inetd conf swat stream tcp nowait 400 root usr pkg sbin swat swat Now restart inetd to enable SWAT etc rc d inetd restart Use SWAT to configure the Samba server You should now be able to access SWAT by surfing to http 901 where is the IP for your NetBSD machine or localhost if you are accessing SWAT locally Login as root with your system s root password You will be taken to SWAT s main menu First click on the Globals icon and use that menu to configure global options such as the workgroup your Samba server is to be part of If you don t understand what an option does click the help link next to it Use the commit changes button to save your work Next click on the Shares icon To create a share type a name into

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