diff options
Diffstat (limited to 'source/a')
| -rw-r--r-- | source/a/aaa_base/_aaa_base/install/doinst.sh | 8 | ||||
| -rw-r--r-- | source/a/aaa_base/_aaa_base/var/spool/mail/root.new | 241 | ||||
| -rwxr-xr-x | source/a/aaa_base/aaa_base.SlackBuild | 4 | ||||
| -rwxr-xr-x | source/a/aaa_libraries/aaa_libraries.SlackBuild | 2 | ||||
| -rwxr-xr-x | source/a/eudev/eudev.SlackBuild | 13 |
5 files changed, 120 insertions, 148 deletions
diff --git a/source/a/aaa_base/_aaa_base/install/doinst.sh b/source/a/aaa_base/_aaa_base/install/doinst.sh index 16f1280d..3f26c670 100644 --- a/source/a/aaa_base/_aaa_base/install/doinst.sh +++ b/source/a/aaa_base/_aaa_base/install/doinst.sh @@ -1,10 +1,8 @@ -# Invite the new admin to register their machine with the Linux Counter: -if [ ! -f var/spool/mail/root ]; then - mv var/spool/mail/root.new var/spool/mail/root -else +# Send root a welcome email unless we detect that it's there already: +if ! grep -q "Welcome to Linux (Slackware 15.0)" var/spool/mail/root 2> /dev/null ; then cat var/spool/mail/root.new >> var/spool/mail/root - rm var/spool/mail/root.new fi +rm var/spool/mail/root.new # (Starting with Slackware 8.1) note: These links are now replaced by # copies of the header files that were used to compile glibc (in the # kernel-headers package). The version number on the kernel-headers diff --git a/source/a/aaa_base/_aaa_base/var/spool/mail/root.new b/source/a/aaa_base/_aaa_base/var/spool/mail/root.new index a8b29151..073e57a7 100644 --- a/source/a/aaa_base/_aaa_base/var/spool/mail/root.new +++ b/source/a/aaa_base/_aaa_base/var/spool/mail/root.new @@ -1,67 +1,18 @@ -From root@hive64.slackware.lan Fri May 20 15:16:45 2016 -Return-Path: <root@hive64.slackware.lan> -Received: from hive64.slackware.lan (localhost [127.0.0.1]) - by hive64.slackware.lan (8.15.2/8.15.2) with ESMTP id u4KKGjAg003580 - for <root@hive64.slackware.lan>; Fri, 20 May 2016 15:16:45 -0500 -Received: (from root@localhost) - by hive64.slackware.lan (8.15.2/8.15.2/Submit) id u4KKGj0X003579 - for root; Fri, 20 May 2016 15:16:45 -0500 -From: root@hive64.slackware.lan -Message-Id: <201605202016.u4KKGj0X003579@hive64.slackware.lan> -Date: Fri, 20 May 2016 15:16:45 -0500 -To: root@hive64.slackware.lan -Subject: Register with the Linux counter project -User-Agent: Heirloom mailx 12.5 7/5/10 -MIME-Version: 1.0 -Content-Type: text/plain; charset=us-ascii -Content-Transfer-Encoding: 7bit - - - (Adapted from a question in the Linux-FAQ) - - How Many People Use Linux? - - Linux is freely available, and no one is required to register with - any central authority, so it is difficult to know. Several businesses - survive solely on selling and supporting Linux. Linux newsgroups are - some of the most heavily read on Usenet. Accurate numbers are hard to - come by, but the number is almost certainly in the millions. - - However, people can register as Linux users at the Linux Counter - project, which has been in existence since 1993. In August of 2012 - the project counted more than 133,000 users, but that is certainly - only a small fraction of all users. The operator of the Linux Counter - estimated over 60 million users at that time. - - To get counted, visit the Web site at: - - http://linuxcounter.net - - ...and fill in the registration form. - - The current count is posted monthly to news:comp.os.linux.misc, and - is always available from the Web site. - -From root@hive64.slackware.lan Fri May 20 15:16:49 2016 -Return-Path: <root@hive64.slackware.lan> -Received: from hive64.slackware.lan (localhost [127.0.0.1]) - by hive64.slackware.lan (8.15.2/8.15.2) with ESMTP id u4KKGnSF003585 - for <root@hive64.slackware.lan>; Fri, 20 May 2016 15:16:49 -0500 -Received: (from root@localhost) - by hive64.slackware.lan (8.15.2/8.15.2/Submit) id u4KKGnJj003584 - for root; Fri, 20 May 2016 15:16:49 -0500 -From: root@hive64.slackware.lan -Message-Id: <201605202016.u4KKGnJj003584@hive64.slackware.lan> -Date: Fri, 20 May 2016 15:16:49 -0500 -To: root@hive64.slackware.lan -Subject: Welcome to Linux (Slackware 14.2)! -User-Agent: Heirloom mailx 12.5 7/5/10 -MIME-Version: 1.0 -Content-Type: text/plain; charset=us-ascii -Content-Transfer-Encoding: 7bit - - -Welcome! I'm glad to see you've made it this far! :^) +From root@z-mp.slackware.lan Tue Jan 11 14:18:55 2022 +Return-Path: <root@z-mp.slackware.lan> +X-Original-To: root +Delivered-To: root@z-mp.slackware.lan +Received: by z-mp.slackware.lan (Postfix, from userid 0) + id D7F87251F63; Tue, 11 Jan 2022 14:18:36 -0600 (CST) +Date: Tue, 11 Jan 2022 14:18:36 -0600 +To: root@z-mp.slackware.lan +Subject: Welcome to Linux (Slackware 15.0)! +User-Agent: mailx v14.9.23 +Message-Id: <20220111201855.D7F87251F63@z-mp.slackware.lan> +From: root@z-mp.slackware.lan + + +Welcome! I'm glad to see you've made it this far! :^) Here are a few hints to help you navigate through the Linux operating system a little bit better. @@ -69,18 +20,18 @@ system a little bit better. Tools to help configure your system: pkgtool: Remember those screens you saw while each package was -installing? You can see all that information (and more) again. The +installing? You can see all that information (and more) again. The simplest way is to use the 'pkgtool' utility to view the package -contents. Another way is to use 'less' or a text editor to read the +contents. Another way is to use 'less' or a text editor to read the files in /var/log/packages and /var/log/scripts (this is the method I -use). The pkgtool script serves as a frontend to the command line +use). The pkgtool script serves as a frontend to the command line package tools, so it's a menu based program that will enable you to remove, install, or view packages that are currently installed on the -system. pkgtool will also allow you to re-run some of the system admin +system. pkgtool will also allow you to re-run some of the system admin scripts that you may have seen during the installation process. - Slackware's command line package tools: I use these utilities most -of the time when I have packages to install, remove, or upgrade. These + Slackware's command line package tools: I use these utilities most +of the time when I have packages to install, remove, or upgrade. These are the tools: installpkg -- Installs packages @@ -92,28 +43,28 @@ are the tools: slackpkg: For those more used to automated package management tools you might like to try slackpkg (my favorite due to its simple, -straightforward approach to keeping a machine up to date). Slackpkg -can be found in the slackware/ap directory. A search of the web will -turn up more tools as well. You should approach these cautiously, as +straightforward approach to keeping a machine up to date). Slackpkg +can be found in the slackware/ap directory. A search of the web will +turn up more tools as well. You should approach these cautiously, as Slackware is designed around the idea that the system should be a -complete installation kept updated with any official patches. This +complete installation kept updated with any official patches. This avoids the mess of dependencies that some other Linux based GNU systems -face. However, many (if not most) of these tools won't know what to do +face. However, many (if not most) of these tools won't know what to do about .new config files, or how to handle upgrading a package that has -changed to a new name. Some also think that any package with a larger +changed to a new name. Some also think that any package with a larger build number is "better", when there have been many instances that a new upstream release wasn't working properly and we had to roll back to an earlier one, and an automated upgrade tool didn't want to -"downgrade" the package. This is something upgradepkg will gladly do, +"downgrade" the package. This is something upgradepkg will gladly do, as it doesn't (as it should not) take the package's version number to -mean much of anything. Regarding automatic upgrades, there have also +mean much of anything. Regarding automatic upgrades, there have also been cases where a library upgrade caused unwanted side effects in -programs that link with it. In theory, most libraries used on the +programs that link with it. In theory, most libraries used on the system try to retain backwards compatibility, but in practice this -isn't always the case. While any issued patches should be installed to +isn't always the case. While any issued patches should be installed to keep your system secure, always remember the old adage "don't fix it if it ain't broke" when considering other upgrades and additions, -especially if they come from unofficial sources. Again, there's a lot +especially if they come from unofficial sources. Again, there's a lot of good stuff out there, but there's also some that's not so good. It's always a good idea to look packages over before you install them. This is as simple as using 'less' to view the contents so you can see @@ -123,23 +74,23 @@ extract the archive into a temporary directory to take a closer look. netconfig: netconfig is a menu based program that will help to configure your network. You will be asked several questions and given an opportunity to review your settings before the changes are -committed. More advanced settings are available by editing the +committed. More advanced settings are available by editing the /etc/rc.d/rc.inet1.conf config file directly. pppsetup: pppsetup is a menu based program that will help you to -connect to your ISP via a PPP connection. As with netconfig you are +connect to your ISP via a PPP connection. As with netconfig you are asked a series of questions and given a chance to review your settings. KDE also includes a utility for configuring PPP dialup connections. This is found in KDE's Internet menu (kppp). xwmconfig: If you have installed the X window system, you can use -xwmconfig to choose your default window manager. Running this as root +xwmconfig to choose your default window manager. Running this as root will set the system default while running it as a normal user will only -set the window manager for that user. An /etc/X11/xorg.conf config +set the window manager for that user. An /etc/X11/xorg.conf config file is no longer required to run X, but you may still use one if you -wish. An initial xorg.conf may be generated by running: X -configure +wish. An initial xorg.conf may be generated by running: X -configure For many modern drivers (such as those using Kernel Mode Setting), -X -configure no longer generates a working xorg.conf. For those drivers +X -configure no longer generates a working xorg.conf. For those drivers you could start by copying /etc/X11/xorg.conf-vesa to /etc/X11/xorg.conf and then edit this line: Driver "vesa" @@ -147,25 +98,34 @@ Change "vesa" to the name of the X driver for your chipset. liloconfig: If you are using the LILO boot loader to start your system you can use liloconfig to setup and install Lilo to the boot -drive. There's a simple installation which tries to automatically set -up LILO to boot Linux (also Windows if found). For more advanced +drive. There's a simple installation which tries to automatically set +up LILO to boot Linux (also Windows if found). For more advanced users, the expert option offers more control over the installation -process. If you have a lot of partitions, the selection menu in -'expert' mode may overflow. You'll likely then want to go to another +process. If you have a lot of partitions, the selection menu in +'expert' mode may overflow. You'll likely then want to go to another console and find the partition you want with 'fdisk -l | less', and then go back and enter it (proving that you are, indeed, an expert). + eliloconfig: If you are using the elilo boot loader to start your +system that uses UEFI BIOS, then eliloconfig is used to copy the kernel +(and the initrd if one is found) to the EFI System Partition, as well as +to add a menu entry for Slackware to the EFI Boot Menu. After upgrading +to a new kernel, use "geninitrd" to create an updated initrd, and then +use eliloconfig to copy the kernel and initrd to the EFI System Partition. +If you've already added a menu entry for Slackware you do not need to do +it again, and indeed probably should not to avoid extra wear on the nvram +used to store EFI data. Other configuration files: The majority of system configuration files can be found in and below -the /etc directory. Most system configuration is done by editing these -files with a text editor such as 'vi', "nano", or 'joe'. If you're not +the /etc directory. Most system configuration is done by editing these +files with a text editor such as 'vi', "nano", or 'joe'. If you're not sure which files you need to edit to configure a given package, use 'less' or 'pkgtool' to see what files are installed by the package paying special attention to any files placed in /etc or that end with the suffix .new (these are usually moved into place if there's not -already a configuration file with the same name). After upgrading a +already a configuration file with the same name). After upgrading a package, if a .new config file is put in place you'll have to decide whether to delete the .new, move it over the existing config file (losing any custom configuration information in the old file), or make @@ -178,16 +138,16 @@ Hardware, network, and kernel issues: If you've got hardware such as a CD-ROM drive or Ethernet card that doesn't seem to work with Linux, it's possible that the kernel you're -using doesn't contain the needed support. In that case, you can do one +using doesn't contain the needed support. In that case, you can do one of two things: - 1. Load the support with kernel modules. This is probably the - simplest way to handle the situation. Just edit + 1. Load the support with kernel modules. This is probably the + simplest way to handle the situation. Just edit /etc/rc.d/rc.modules so that it loads the modules you need. 2. Recompile your kernel, including the needed driver(s). However, recompiling your kernel is an extreme measure that can be -both difficult and dangerous to the stability of your system. If you +both difficult and dangerous to the stability of your system. If you decide to go that route, either be sure you know the potential pitfalls or seek guidance from someone experienced with kernel configuration, compilation, and installation. @@ -196,32 +156,32 @@ compilation, and installation. with udev if the hardware is present in the system, unless the modules are not udev-capable yet, or they are blacklisted in a file in /etc/modprobe.d/ (local config files) or /lib/modprobe.d/ (config files -that ship with the system). If the module for the driver you need is +that ship with the system). If the module for the driver you need is blacklisted, copy the appropriate file from /lib/modprobe.d/ to /etc/modprobe.d/ and then comment out the line that blacklists the module -by putting # at the beginning. Files found in /etc/modprobe.d/ will +by putting # at the beginning. Files found in /etc/modprobe.d/ will override those found in /lib/modprobe.d/ and will not be overwritten by -upgrades. If that doesn't fix the issue, check with "lsmod" to make sure -that the module is loading correctly. If not, try loading it in the +upgrades. If that doesn't fix the issue, check with "lsmod" to make sure +that the module is loading correctly. If not, try loading it in the /etc/rc.d/rc.modules file. If you're on a standalone LAN without a nameserver, make sure you don't have a nameserver line in /etc/resolv.conf, or you may experience delays with many network commands as they attempt to query the bogus -nameserver. Most people these days will have a nameserver, or be able -to access one via their router/gateway. Most DHCP servers will tell +nameserver. Most people these days will have a nameserver, or be able +to access one via their router/gateway. Most DHCP servers will tell dhcpcd what it needs to know in order to set up your /etc/resolv.conf automatically. Want to run NFS? You'll need to install the rpcbind and nfs-utils -packages. Then, edit your /etc/exports to allow NFS access. (see 'man -exports' for examples). Finally, set rc.rpc and rc.nfsd executable: +packages. Then, edit your /etc/exports to allow NFS access. (see 'man +exports' for examples). Finally, set rc.rpc and rc.nfsd executable: chmod 755 /etc/rc.d/rc.rpc chmod 755 /etc/rc.d/rc.nfsd To start the NFS server, either reboot or execute the two rc files. The kernel is now set up with the CONFIG_SCSI_MULTI_LUNS option -to scan for new "SCSI" devices automatically. However, if that fails +to scan for new "SCSI" devices automatically. However, if that fails to work after inserting a digital media card, or plugging in a new USB or IEEE1394 (Firewire) device, you may need to run the following command before it becomes available as a mountable device: @@ -262,7 +222,7 @@ that CUPS will start at boot: This local "website" may also be reached using the CUPS configuration menu choice within a desktop environment such as KDE. - See the extensive docs in /usr/doc/cups for more details. If you + See the extensive docs in /usr/doc/cups for more details. If you don't see your exact printer model when adding a new printer, often one that's "close" will do the trick. @@ -272,24 +232,24 @@ Users who plan to print (or scan) need to be members of the "lp" group. Mouse support: Only very ancient mice will need any special treatment in order to -get basic support, and with GPM cut and paste on the console. Most -will work with the "ps2" or "imps2" protocols. If you should happen to +get basic support, and with GPM cut and paste on the console. Most +will work with the "ps2" or "imps2" protocols. If you should happen to have one of the ancient mice that is not a serial, PS/2, or USB mouse then you'll probably have to load a kernel module in order to get it to -work. At this point in time, a busmouse is rare. These days, most +work. At this point in time, a busmouse is rare. These days, most mice are PS/2 (with a 6 pin round plug) or USB, or occasionally serial -(with a 9 pin trapezoidal plug). These kinds of mice don't require any +(with a 9 pin trapezoidal plug). These kinds of mice don't require any special setup as the system should detect and activate them -automatically. If you think your mouse might need a special driver (if +automatically. If you think your mouse might need a special driver (if it's not working), read the comments in /etc/rc.d/rc.modules to see -which one is needed, and edit the file to load it at boot time. It's +which one is needed, and edit the file to load it at boot time. It's also possible that the /dev/mouse link may need to be changed to point -to the proper mouse device. Or, compile a new kernel with built in +to the proper mouse device. Or, compile a new kernel with built in support for your mouse and install that. Using the lsmod command, you can see if the psmouse module is loaded. If so, you're using the psmouse module for a PS/2-like mouse (including -most touchpads). If you need to adjust the mouse protocol, make a copy +most touchpads). If you need to adjust the mouse protocol, make a copy of the config file, and then edit that: cp /lib/modprobe.d/psmouse.conf /etc/modprobe.d/psmouse.conf @@ -301,38 +261,38 @@ switch, or to properly enable tap-to-click with a touchpad. Network support: - Of course, you're going to want to get your machine online. If you + Of course, you're going to want to get your machine online. If you have a router supporting DHCP you're probably already on by now. -Otherwise, 'netconfig' will give you a simple network connection. To +Otherwise, 'netconfig' will give you a simple network connection. To get your machine on the net, you'll need to install packages from the -N (network) series. If you aren't sure which ones you'll need, the -easiest thing is to just install them all. Network services will not +N (network) series. If you aren't sure which ones you'll need, the +easiest thing is to just install them all. Network services will not run unless activated by making the startup scripts in /etc/rc.d/ -executable, so it doesn't hurt to have them installed. Your machine +executable, so it doesn't hurt to have them installed. Your machine should be configured at least with loopback using the "netconfig" -utility. If you are using a modem, make sure the serial port your +utility. If you are using a modem, make sure the serial port your modem uses is correctly configured, and then use 'pppsetup' to configure -the dialup process. Additional documentation on pppsetup can be found -in /usr/doc/pppsetup-*/. DSL/Cable users who need to use PPPoE (PPP +the dialup process. Additional documentation on pppsetup can be found +in /usr/doc/pppsetup-*/. DSL/Cable users who need to use PPPoE (PPP over Ethernet) should see the docs in /usr/doc/rp-pppoe-3.12/. If you will be using wireless (or even a wired interface), you might -want to let NetworkManager handle your network connections. This is +want to let NetworkManager handle your network connections. This is a choice during the initial installation, but may also be selected later by rerunning netconfig, or by setting the startup script -to executable (chmod 755 /etc/rc.d/rc.networkmanager). When Network +to executable (chmod 755 /etc/rc.d/rc.networkmanager). When Network Manager is used to handle connections, a nice interface is provided to scan for wireless access points and make changes to the network -configuration. This interface runs automatically with KDE or Xfce. -In fluxbox, the nm-applet program will need to be launched. Other +configuration. This interface runs automatically with KDE or Xfce. +In fluxbox, the nm-applet program will need to be launched. Other window managers lack a system tray to display nm-applet, so for those you might want to look at wicd in /extra, which also provides a nice -GUI tool for connecting to wireless (or wired) networks. For window +GUI tool for connecting to wireless (or wired) networks. For window managers that do not provide a tray for running programs, start -"wicd-client" to make changes. With NetworkManager or wicd, it's +"wicd-client" to make changes. With NetworkManager or wicd, it's a good idea to remove any existing network configuration in -/etc/rc.d/rc.inet1.conf first. This can be done by running netconfig -and setting the machine to use loopback. Then, if you're using +/etc/rc.d/rc.inet1.conf first. This can be done by running netconfig +and setting the machine to use loopback. Then, if you're using NetworkManager run it a second time and select NetworkManager. If you need to set up your Linux machine as a router for other systems, @@ -340,7 +300,7 @@ you'll want to set up the interfaces in /etc/rc.d/rc.inet1.conf, and set up NAT support with something like this in /etc/rc.d/rc.firewall, and then make rc.firewall executable. -# Delete and flush. Default table is "filter". +# Delete and flush. Default table is "filter". # Others like "nat" must be explicitly stated. iptables --flush # Flush all the rules in filter and nat tables @@ -355,16 +315,23 @@ echo "Enabling ip_forwarding..." echo 1 > /proc/sys/net/ipv4/ip_forward It's possible to expand (or reduce ;-) this script for just about any -firewall needed. See "man iptables" for lots of information. +firewall needed. See "man iptables" for lots of information. F: FAQ series, and the HOWTO documentation collection: If you installed the F series, you find detailed documentation on -many common Linux tasks in /usr/doc/Linux-HOWTOs. Each of these -instructional files covers a particular Linux task. They cover most +many common Linux tasks in /usr/doc/Linux-HOWTOs. Each of these +instructional files covers a particular Linux task. They cover most system administration tasks in a lot more detail than this little email -does. +does. At this point the majority of these have been unmaintained for +years and are largely obsolete, but in spite of this there are still +good hints to be found. In general a search engine will be your best +bet for finding additional information. Or, visit the Slackware forum +on Linux Questions and you'll find a helpful community who can answer +your questions (or perhaps even I'll answer you there): + +https://www.linuxquestions.org/questions/slackware-14/ There is also a collection of Linux related FAQs (lists of Frequently Asked Questions with answers) /usr/doc/Linux-FAQs. diff --git a/source/a/aaa_base/aaa_base.SlackBuild b/source/a/aaa_base/aaa_base.SlackBuild index a0544430..2632153d 100755 --- a/source/a/aaa_base/aaa_base.SlackBuild +++ b/source/a/aaa_base/aaa_base.SlackBuild @@ -1,6 +1,6 @@ #!/bin/bash -# Copyright 2008, 2009, 2010, 2011, 2012, 2013, 2015, 2018, 2021 Patrick J. Volkerding, Sebeka, Minnesota, USA +# Copyright 2008, 2009, 2010, 2011, 2012, 2013, 2015, 2018, 2021, 2022 Patrick J. Volkerding, Sebeka, Minnesota, USA # All rights reserved. # # Redistribution and use of this script, with or without modification, is @@ -24,7 +24,7 @@ cd $(dirname $0) ; CWD=$(pwd) PKGNAM=aaa_base VERSION=15.0 -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} # Automatically determine the architecture we're building on: if [ -z "$ARCH" ]; then diff --git a/source/a/aaa_libraries/aaa_libraries.SlackBuild b/source/a/aaa_libraries/aaa_libraries.SlackBuild index b23dad63..8b421da6 100755 --- a/source/a/aaa_libraries/aaa_libraries.SlackBuild +++ b/source/a/aaa_libraries/aaa_libraries.SlackBuild @@ -23,7 +23,7 @@ cd $(dirname $0) ; CWD=$(pwd) PKGNAM=aaa_libraries VERSION=${VERSION:-15.0} -BUILD=${BUILD:-12} +BUILD=${BUILD:-13} # Automatically determine the architecture we're building on: if [ -z "$ARCH" ]; then diff --git a/source/a/eudev/eudev.SlackBuild b/source/a/eudev/eudev.SlackBuild index f663e0b1..89f1a708 100755 --- a/source/a/eudev/eudev.SlackBuild +++ b/source/a/eudev/eudev.SlackBuild @@ -1,6 +1,6 @@ #!/bin/bash -# Copyright 2006, 2008, 2009, 2010, 2011, 2012, 2013, 2015, 2017, 2018, 2020, 2021 Patrick J. Volkerding, Sebeka, MN, USA +# Copyright 2006, 2008, 2009, 2010, 2011, 2012, 2013, 2015, 2017, 2018, 2020, 2021, 2022 Patrick J. Volkerding, Sebeka, MN, USA # All rights reserved. # # Redistribution and use of this script, with or without modification, is @@ -24,7 +24,7 @@ cd $(dirname $0) ; CWD=$(pwd) PKGNAM=eudev VERSION=${VERSION:-$(echo eudev-*.tar.* | cut -d - -f 2 | rev | cut -f 3- -d . | rev)} -BUILD=${BUILD:-2} +BUILD=${BUILD:-1} NUMJOBS=${NUMJOBS:-" -j$(expr $(nproc) + 1) "} @@ -79,6 +79,13 @@ zcat $CWD/eudev.ignore_bind_unbind_events.diff.gz | patch -p1 --verbose || exit # Don't require groups that we don't need: zcat $CWD/eudev.no.renderD.no.kvm.diff.gz | patch -p1 --verbose || exit 1 +if [ ! -r configure ]; then + if [ -x ./autogen.sh ]; then + NOCONFIGURE=1 ./autogen.sh + else + autoreconf -vif + fi +fi ./configure \ --prefix=/usr \ --with-rootprefix=/ \ @@ -153,7 +160,7 @@ chmod 0755 $PKG/lib/udev/* mkdir -p $PKG/usr/doc/eudev-$VERSION cp -a \ - COPYING* README* TODO \ + BUILD* CONTRIBUTING* COPYING* LEGACY* NOTES* README* TODO* \ $PKG/usr/doc/eudev-$VERSION # Compress and fix manpage symlinks: |