The Datafile PD-CD 4

home *** CD-ROM | disk | FTP | other *** search

/ The Datafile PD-CD 4 / DATAFILE_PDCD4.iso / unix / riscbsd / docs / config_gui < prev next >

Wrap

Text File | 1996-10-07 | 25.2 KB | 706 lines

RiscBSD Configuration Guide --------------------------- Copyright (c) 1996 Mark Brinicombe $Id: config_guide.txt,v 1.5 1996/04/03 02:29:55 mark Exp $ Pre-requisits : Beta installation of RiscBSD with the compiler installed (sets base, as252, cc263, comp and local) Note: To compile kernel source newer than 10/03/96 it is recommended that the cc272 set is installed in preference to the cc263 set. source files required: sys.tar.gz netbsd-patches.tar.gz csc-patch.tar.gz or: sys-arm32.tar.gz The patches file is available from ftp.ph.kcl.ac.uk in the directory /pub/acorn/RiscBSD/sources/patches/netbsd-patches.tar.gz The sys.tar.gz file can be obtained from any netbsd-current mirror site e.g. ftp://src.doc.ic.ac.uk/pub/packages/unix/NetBSD-current/tars/src/sys.tar.gz The csc-patch.tar.gz file can also be from on the RiscBSD ftp site. This contains the patch files and object files needed to build kernels with the Cumana SCSI II driver for which the source code to the driver is NDA. The sys-arm32.tar.gz file is also available from ftp.ph.kcl.ac.uk and has already had all the patches applied and contains the csc driver object file. Installing the files -------------------- cd /usr extract the sys.tar.gz and netbsd-patches.tar.gz files e.g. tar xfvz /usr/local/tars/sys.tar.gz tar xfvz /usr/local/tars/netbsd-patches.tar.gz If you are short of space you can prune the kernel source tree. e.g. cd /usr/src/sys/arch rm -rf alpha amiga atari da30 hp300 i386 m68k mac mac68k mvme68k pc532 pmax rm -rf sparc sun3 vax leaving just the arm32 directory. If you are really short of space you can also prune some of the compatibilty modules e.g. cd /usr/src/sys/compat rm -rf freebsd hpux ibcs2 linux osf1 svr4 ultrix The sub directory common is required. NOTE: You will need 2MB-3MB on the partition holding your kernel source tree for the object files when you build the kernel. If you have the sys-arm32.tar.gz file then this should be extracted from / i.e. cd / tar xfvz /usr/local/tars/sys-arm32.tar.gz This source tree already has already been pruned and has had all the patches applied. Geography --------- /usr/src/ is the home of all the standard NetBSD source code i.e. bin sbin usr.bin usr.sbin etc ... However to configure your own kernels you only need the sys source tree. Often there is a symbolic link /sys to /usr/src/sys The source tree in /usr/src/sys is completely self contained and does use any files outside the sys directory. Although the kernel build itself does not user /usr/include several support binaries such as makemodes do. Within the sys directory are a set of directories containing the source to the various kernel components. Some of these directories will have further sub directories e.g. arch, compat, lib and miscfs. These directories are : adosfs amigados filesystem arch architecture dependent source compat compatibility modules conf configuration files ddb kernel debugger dev generic device source code isofs iso filesystems (cd9660) kern main kernel source code lib kernel libraries miscfs miscellaneous filesystems msdosfs msdos filesystem net network source code netccitt netcitt source code netinet inet source code netiso netiso source code netns netns source code nfs nfs source code scsi scsi device source code stand miscellaneous code sys kernel header files ufs ufs filesystem source code vm virtual memory source code There are two arm32 specific directories. They are : sys/arch/arm32 sys/lib/libkern/arch/arm32 Site seeing ----------- cd /usr/src/sys/arch/arm32 This is the top level of the arm kernel code. The subdirectories are listed below. arm32 main arm32 source code. boot source code for boot loader. compile kernel compile directory. conf configuration files. dev drivers that are not hardware specific. doc Miscellaneous kernel documents. fpe-arm ARM Ltd FPE based floating point emulator. fpe-sp single precision floating point emulator. include machine specific include files. kshell kernel shell. Used for debugging but a bit redundant now. mainbus source code mainbus device and drivers attached to the mainbus e.g. combo chip driver wd, rd, com, lpt. podulebus source code for podulebus device and drivers for podule hardware. There are two experimental directories that exist within the mainbus and podulebus directories. These do not exist in the standard NetBSD source tree but may be created when applying some of the patches or NetBSD/arm32 specific upgrades. These directories contain experimental source files and development source files that are not ready for public use. They also are where NDA code is developed. Object file versions of the NDA drivers may be found in these directories. Installing the patches ---------------------- There are number of patches that can be applied to the machine independant part of the source tree. Most of these patches are not required but are recommended. Eventually they will be integrated into the standard source tree. Until then they must be manually applied. A lot of the patches are for non kernel parts of the source tree. Since this guide deals with kernel configuration only those patches related to the kernel will be considered. They are all the patches that begin sys. The filenames of the patch files describe the locations of the patches. sys.compat.common.compat_tty.c.patch - signed char patch sys.kern.exec_aout.c.patch - 4MB binaries compatibility sys.kern.subr_prf.c.patch - width specifier on kernel print %s sys.kern.tty_compat.c.patch - signed char patch sys.kern.vfs_subr.c.patch - verbose fs unmounting sys.scsi.sd.c.patch - MO disc disklabel and geom patch sys.sys.proc.h.patch - signed char patch sys.arch.arm32.conf.Makefile.arm32.patch - make to speed up makedepend To apply these patches, either apply manually i.e. cd /usr/src/sys/kern patch -p0 </usr/src/patch/sys.kern.exec_aout.c.patch patch -p0 </usr/src/patch/sys.kern.subr_prf.c.patch patch -p0 </usr/src/patch/sys.kern.tty_compat.c.patch patch -p0 </usr/src/patch/sys.kern.vfs_subr.c.patch cd /usr/src/sys/scsi patch -p0 </usr/src/patch/sys.scsi.sd.c.patch cd /usr/src/sys/compat/common patch -p0 </usr/src/patch/sys.compat.common.compat_tty.c.patch cd /usr/src/sys/sys patch -p0 </usr/src/patch/sys.sys.proc.h cd /usr/src/sys/arch/arm32/conf patch -p0 </usr/src/patch/sys.arch.arm32.conf.Makefile.arm32.patch or use the applypatches script in the /usr/src/patch directory i.e. the command /usr/src/patch/applypatches sys will apply all the patches to the sys source tree. Creating your Kernel Configuration File --------------------------------------- Before we can build a kernel we need to create a kernel configuration file. A kernel configuration file contains information on all the kernel options required e.g. filesystems and networking and specifies all the devices to build into the kernel. cd /usr/src/sys/arch/arm32/conf In this directory are a number of files. Most of these are example kernel configuration files from some of the RiscBSD development machines. All the file in capitals are kernel configuration files. In addition there is a makefile template an a list of the various source files required for different options and devices. There is also a monitors directory that contains standard monitor definition files as used by RiscOS. Monitor definition files are used to obtain mode timing information that is compiled into the kernel so that the vidc can be correctly setup at boot time. If you have a custom monitor definition file or the appropriate one is not in the monitors sub directory you should copy the one you use in RiscOS into this directory. Now copy the GENERIC kernel configuration to the configuration file for your machine. This is your machine name in capitals. e.g. cp GENERIC <name of your machine in capitals> Now you need to edit your configuration file to select the appropriate options. The GENERIC configuration file is fairly self explanatory, It basically consists of options and devices. The file is split into a number of sections with similar or related options grouped together e.g. filesystem options, network options etc. Each section has a comment which will be used when refering to the various sections. To remove options, rather than deleting them it is perhaps better to comment the lines out with a hash character in case you wish to enable the options later. Typically you will not need to change anything above the CPU options. The only line that you may possible want to change in the maxusers line. The CPU options section defines CPU specific options. These are the CPU type and the abort type. Currently the options CPU_ARM6 and CPU_ARM7 are valid. If the kernel is configured with CPU_ARM6 then the option CPU_LATE_ABORT can be used to run the processor in late abort abort. This is required if you want compatibility with the ARM7 or later processors since the ARM6 is the only processor that supports the early abort model. The only difference is that the fault code is slightly more efficient with early aborts as register fixups are not required. The next section defined FPE options. Currently there are two possible options, FPE and ARMFPE. These define which floating point emulator is built into the kernel. The option FPE builds in the original single precision FPE while the option ARMFPE builds in the newer ARM Ltd based FPE. It is valid to specify both these options in which case the ARM Ltd FPE is installed first and if the installation fails the kernel will fall back to the single precision FPE. The next section are filesystem options. These select which filesystems should be build in. The FFS option is REQUIRED as this is the standard filesystem the RiscBSD uses. The next section contains the networking options. If you intend to use NFS then you should make use of the NFSSERVER and NFSCLIENT options. If you have multiple network interfaces in your machine then you may require packet forwarding so you should select the option GATEWAY. As standard the only other network option you are likely to need is INET. The next section contains compatibility options. Compatibility with BSD 4.3 is required for X and various other binaries. In practice it is probably a good idea to keep all the compatibility options in the GENERIC config. Next are the shared memory options. Currently this has not been tested/debugged and should not be used. The next section contains device options. Currently there are two options for the ramdisk device. You only need these options if you are configuring a ramdisk. If you do configure a ramdisk you require the RAMDISK_HOOKS options if you want to be able to setup the ramdisk at boot time. The RAMDISK_SIZE option allows a fixed size ramdisk to be configured. The best thing is to configure a zero size ramdisk. Then you can override the size using the boot config option. The option PLIP should be used here if you want plip support to be added to the lpt driver. The final section of options are the development options. These are as follows : DIAGNOSTIC - compile in extra consistency checks. Adds a slight code overhead quite a few kernel functions and is many for check for possible kernel problems while developing e.g. null process pointers etc. For the moment it is recomended that you keep this option enabled. There may be some compilation problems if DIAGNOSTIC is turned off. KTRACE - compile in system call tracing. Read the man pages for ktrace and kdump for more information of system call tracing. IRQSTATS - compile in irq statistic gathering. POSTMORTEM - compile in the postmortem code. This gets call on a panic and dumps information useful to me (mark) when debugging. ROTTEN_INNARDS - shows the guts of the postmortem. This is not really any use to anybody else as nobody else knows what the information means. KSHELL - compiles in the kernel shell. This is the shell that gets enter when the kernel panics. It provides some debugging information but most of if functions are now redundant. This is likely to be replaced sometime with the standard NetBSD kernel debugger. LKM - compile in the loadable kernel module support code. The kernel support for LKM's is completed but LKM's cannot currently be build until the linker is upgraded. DEBUGTERM - adds console debugging code. Only of use to Nut, do not use. KGDB - adds remote kernel debugging code. This option is not fully supported yet. DDB - adds in kernel debugger. This option is not fully supported yet. Next comes the specification for the kernel object and the root and swap devices. This should be left as config netbsd swap generic options GENERIC The root and swap devices will then be taken from the bootloader Now we reach the device configuration section. This section lists all the devices that should be built into the kernel. On boot the kernel will probe these devices and configure any that are found. The mainbus device must always be configured. This is the device to which all the main devices are attached e.g. wd, fd, lpt and com. The cpu device is used to configure the CPU's. You must configure cpu0 at mainbus for the boot processor. Additional cpus can be configured on the multiprocessor card bus. The vidcvideo device is not a required device yet for basic operation. In the future this is likely to become a required device for vidc support. If you wish to use X then this device is required. The vt device is the virtual console device. You need to configure 1 virtual terminal device for each virtual console you want. The wdc device is the IDE controller. If you are configuring any IDE driver then you need to configure this. The wd driver needs to be configured if you want to use the internal IDE drive. If you only have a one IDE driver then you only need to configure wd0. If you have two driver then you should configure wd1 as well. The fdc device is the floppy controller device. This needs to be configured if you are going to configure any floppy devices. The fd driver should be configured for the number of floppy driver you have. Typically this will just be one. The rd device is the ramdisc device. This should be configured if you want to use a ramdisc. There are two ways of setting the ramdisc size. You can specify a size with the RAMDISC_SIZE option which will always allocate a fixed amount of memory to the ramdisc or you can configure the device with RAMDISC_SIZE=0 and specify the ramdisc size from the boot config. The kbd device is required if you want to be able to use the keyboard. You may find that you cannot build a kernel without the kbd driver. The quadmouse device is required if you want to use X. The com device is the required if you want to use the serial port. A second com device can be configure for the second serial port in the IO chip but this is not recommended as the kernel will fail a multiuser startup. If you want to use the second serial port you need to make the second serial interrupt available other wise processes that try and access the device will hang e.g. ttyflags during the multiuser startup. The lpt device drives the standard printer port. There are two modes of operation; polled and interrupt driven. If you specify an irq number for the printer device then interrupt support will be enable when the device is configured. If you have an interrupt driver lpt device you can still select polling operation when you open the lpt device by using /dev/lpa rather than /dev/lpt The beep device can be configured on machine that do not have 16 bit sound. Currently the 16 bit sound driver is under development and the beep device does not produce a proper beep on machines that do have the 16 bit sound card. Now we reach the podulebus device. This is the attach point for all the devices that are connected to the podule bus. The podulebus device will rpobe the podulebus and reports all the located podules. It then proceeds to configure any found podules. If you are likely to fit any podules to your machine then you should configure this device. Next come the devices for various SCSI cards. The asc device (Acorn SCSI I card) can be configured if you have one of these podules. The csc device (Cumana SCSI II) cannot be configured yet as the source for this is under NDA. If you wish to use this driver then you must install e csc-patch.tar.gz file and patch arm32/conf/files.arm32 This patch allows the csc driver to be build from object code rather than source code. The ptsc device (Powertec SCSI II) can be configured if you have one of these podules. The oak device (Oak SCSI I) can be configured if you have one of these podules. Next you should configure any of the SCSI devices you want i.e. sd, st, cd, ch, uk and ss. Then come the ethernet drivers. Although the network slot driver physically do not attach to the podule bus they are functionally very similar and are handled by the podulebus. The ea device supports the ether3 and ether5 podules The eb device supports the etherB network slot cards (AEH71) The eh device supports the etherH icubed network slot card (AEH72) The ie device supports the ether1 podule Lastly are the pseudo devices. These are devices that do not drive specific hardware. If you are using networking then you need the lookback device (This includes using X). The bpfilter device is a packet filter that is attached to the network devices. It allows the input and output packets to be examined with tcpdump etc. The sl device configures the slip device. This is require if you want to use SLIP via a com device. The ppp device configures the ppp device. The tun device configures the kernel to support network tunneling. The pty device configures pseudo terminals. These are required for networking and X. The vnd device configures the vnode device driver. This allows files to be attached to a device for paging etc. The ccd device configures the concatenated disc driver. If you want to know what this is check the man page on ccdconfig. If you need this option then you should know what it is. The rd device is the ramdisc device. This should be configured if you want to use a ramdisc. There are two ways of setting the ramdisc size. You can specify a size with the RAMDISC_SIZE option which will always allocate a fixed amount of memory to the ramdisc or you can configure the device with RAMDISC_SIZE=0 and specify the ramdisc size from the boot config. After the devices the only remaining configuration stuff is the monitor and modes. These are passed as make options. You should set the makeoption MONITOR to the name of you monitor definition file in the monitors subdirectory. The MODES makeoption should be a list of the resolutions you want to build in the kernel in the form x,y,f When you boot your kernel the mode closed to that specified in the boot config is used. Configuring your kernel ----------------------- Ok now save the file. While still in the arm32/conf directory at the prompt type config <name of your machine in captials> This will analyse your configuration file and will create the directory ../compile/<name of your machine in captials> It will create a makefile and all the necessary header files in that directory. On completion, config will print a reminder to do a make depend before building the kernel. Now cd to the compile directory for your configuration e.g. if you did config GENERIC cd ../compile/GENERIC type make depend This will proceed to build all the dependancies for the kernel source files. Once the make depend has completed at the prompt, type make Now twiddle your fingers an hour or two while the kernel builds. When the build completes you should then find a file called netbsd in the directory. This is your custom configured kernel. At the prompt type mv /netbsd /netbsd.old mv netbsd /netbsd Now you are ready to reboot. If you are not doing native boots then you will need to copy the kernel over the RISC OS. You should now be able to boot you new kernel. The version line when the kernel boots will report the kernel configuration and the kernel revision along with the build date and the builder. ------------------------------------------------------------------------------ Appendix A - Example GENERIC configuration file This is a copy of the GENERIC configuration file. It if provided here purely for reference in case you print this file out. # # GENERIC -- everything that's currently supported # include "std.arm32" # estimated number of users maxusers 32 # Standard system options options TIMEZONE=0 # time zone to adjust RTC time by options DST=0 # daylight savings time used by RTC options SWAPPAGER # paging; REQUIRED options VNODEPAGER # mmap() of files options DEVPAGER # mmap() of devices # CPU options options CPU_ARM6 options CPU_LATE_ABORT # ARM7XX compatibility # FPA options options FPE options ARMFPE # File system options options FFS # UFS options QUOTA # UFS quotas options LFS # log-structured file system options MFS # memory file system options CD9660 # ISO 9660 + Rock Ridge file system options MSDOSFS # MS-DOS file system options FDESC # /dev/fd options FIFO # FIFOs; RECOMMENDED options KERNFS # /kern options NULLFS # loopback file system options PORTAL # ? options PROCFS # /proc options UMAPFS # NULLFS + uid and gid remapping options UNION # union file system # Networking options options NFSCLIENT options NFSSERVER options GATEWAY # packet forwarding options INET # IP + ICMP + TCP + UDP options NS # XNS options ISO,TPIP # OSI options EON # OSI tunneling over IP options CCITT,LLC,HDLC # X.25 # Compatibility options options COMPAT_43 options COMPAT_10 options COMPAT_09 options TCP_COMPAT_42 # TCP bug compatibility with 4.2BSD # Shared memory options #options SYSVMSG # System V-like message queues #options SYSVSEM # System V-like semaphores #options SYSVSHM # System V-like memory sharing #options SHMMAXPGS=1024 # 1024 pages is the default # Device options options RAMDISK_HOOKS options RAMDISK_SIZE=0 # Size in KBytes options PLIP # Development options options DIAGNOSTIC # internally consistency checks options KTRACE # system call tracing, a la ktrace(1) options IRQSTATS # IRQ statistics options POSTMORTEM # perform postmortem on panic #options ROTTEN_INNARDS # show the gory bit of the postmortem options KSHELL # kernel developemnt shell (debug) options LKM # loadable kernel modules #options DEBUGTERM # create a debug console #options KGDB # remote kernel debugging options DDB # in-kernel debugger #makeoptions DEBUG="-g" # compile full symbol table config netbsd swap generic options GENERIC # The main bus device mainbus0 at root # The boot cpu cpu0 at mainbus? # The hydra multiprocessor device #hydra0 at mainbus? # The vidc vidcvideo0 at mainbus? # generic VT console device vt0 at mainbus? vt1 at mainbus? vt2 at mainbus? vt3 at mainbus? vt4 at mainbus? vt5 at mainbus? # IDE disk controller wdc0 at mainbus? base 0x002107c0 irq 9 wd0 at wdc? drive ? wd1 at wdc? drive ? # Floppy disk controller fdc0 at mainbus? base 0x00210fc0 irq 12 dack 0x00002000 fd0 at fdc? drive ? # kbd via IOMD kbd0 at mainbus? base 0x00000000 # quadrature mouse quadmouse0 at mainbus? base 0x00000000 # PS2 mouse pms0 at mainbus? base 0x00000000 # Serial ports com0 at mainbus? base 0x00210fe0 irq 10 #com1 at mainbus? base 0x00210be0 # Parallel ports lpt0 at mainbus? base 0x002109e0 irq 0 # Crude sound device beep0 at mainbus? base 0x00000000 # Podule bus device podulebus0 at root asc0 at podulebus? # Acorn SCSI card scsibus* at asc? #csc0 at podulebus? # Cumana SCSI II card #scsibus* at csc? ptsc0 at podulebus? # Power-Tec SCSI II card scsibus* at ptsc? oak0 at podulebus? # Oak SCSI I card scsibus* at oak? sd* at scsibus? target ? lun ? # SCSI disk drives st* at scsibus? target ? lun ? # SCSI tape drives cd* at scsibus? target ? lun ? # SCSI CD-ROM drives ch* at scsibus? target ? lun ? # SCSI auto-changers uk* at scsibus? target ? lun ? # SCSI unknown device ss* at scsibus? target ? lun ? # SCSI scanner #kie* at podulebus? slot ? offset ? ea0 at podulebus? # Ether3 podules eb0 at podulebus? # EtherB network slot cards eh0 at podulebus? # EtherH network slot cards ie0 at podulebus? # Ether1 podules pseudo-device loop 1 # network loopback pseudo-device bpfilter 8 # packet filter pseudo-device sl 2 # CSLIP pseudo-device ppp 2 # PPP pseudo-device tun 2 # network tunneling over tty pseudo-device pty 32 # pseudo-terminals pseudo-device tb 1 # tablet line discipline pseudo-device vnd 4 # paging to files pseudo-device ccd 2 # concatenated disk devices pseudo-device rd 1 # Ramdisk driver makeoptions MONITOR="Taxan875+LR" makeoptions MODES="1024,768,60 1024,768,70 800,600,60 640,480,60 1280,1024 1152,900" ------------------------------------------------------------------------------ $Log: config_guide.txt,v $ Revision 1.5 1996/04/03 02:29:55 mark Config file example updated to reflect latest changes to the GENERIC config file. The ramdisc is now a psuedo device. More interrupts are now specified in the config file. Revision 1.4 1996/03/09 08:22:32 mark Updated to reflect changes in NetBSD-current. Updated information on asc device Added recommendation of cc272 set for new kernel builds. revision 1.3 1996/02/24 02:48:06 mark Added information on the sys-arm32.tar.gz file on the ftp site. revision 1.2 1996/02/08 22:16:27 mark Miscellaneous updates and corrections. revision 1.1 1996/02/02 05:23:03 mark Initial commit of the kernel configuration guide