Text 6090, 179 rader
Skriven 2006-05-17 18:03:00 av Paul Rogers (1:105/360.0)
     Kommentar till en text av Maurice Kinal
Ärende: Export
==============
 MK> Ah!  You shouldn't have to go through any of the multiple
 MK> builds if you use the built system to build packages.  Most
 MK> of stuff you can build with;

 MK>     ./configure --prefix=/usr
 MK>     make && make install DESTDIR=$PKG

Ummm, not hardly!  Just for example, here's my own build script
for cron/vixiecron:

#!/bin/bash -e
# Build cron
PREREQ1=`basename $(find /var/local/git -maxdepth 1 -name\
  '*runparts*' -print)` &&
patch -Np1 -i ../patches/vixie-cron-3.0.1-redhat_mdk-1.patch &&
patch -Np1 -i ../patches/vixie-cron-3.0.1-security-1.patch &&
patch -Np1 -i ../patches/vixie-cron-3.0.1-makefile-1.patch &&
patch -Np1 -i ../patches/vixie-cron-3.0.1-variables-1.patch &&
(make 2>&1 | tee log.make && exit $PIPESTATUS) &&
git `basename $0` &&
(make install 2>&1 | tee log.inst && exit $PIPESTATUS) &&
(cat >/etc/rc.d/init.d/cron  <<"EOF"
#!/bin/sh
# Begin $rc_base/init.d/cron - cron loader

source /etc/sysconfig/rc
source $rc_functions

case "$1" in
 start)
  echo "Starting Cron Scheduler..."
  loadproc crond
  ;;
 stop)
  echo "Stopping Cron Scheduler..."
  killproc crond
  rm -f /var/run/crond.pid
  ;;

 restart)
  $0 stop
  sleep 1
  $0 start
  ;;

 status)
  statusproc crond
  ;;

 *)
  echo "Usage: $0 {start|stop|restart|status}"
  exit 1
  ;;
esac

# End $rc_base/init.d/cron
EOF
) &&
chmod 754 /etc/rc.d/init.d/cron &&
ln -s ../init.d/cron /etc/rc.d/rc2.d/S22cron &&
ln -s ../init.d/cron /etc/rc.d/rc2.d/K78cron &&
ln -s ../init.d/cron /etc/rc.d/rc3.d/S22cron &&
ln -s ../init.d/cron /etc/rc.d/rc3.d/K78cron &&
ln -s ../init.d/cron /etc/rc.d/rc4.d/S22cron &&
ln -s ../init.d/cron /etc/rc.d/rc4.d/K78cron &&
ln -s ../init.d/cron /etc/rc.d/rc5.d/S22cron &&
ln -s ../init.d/cron /etc/rc.d/rc5.d/K78cron &&
mkdir -p /etc/cron.d &&
mkdir -p /etc/cron.hourly &&
mkdir -p /etc/cron.daily &&
mkdir -p /etc/cron.weekly &&
mkdir -p /etc/cron.monthly &&
# Now that we have cron, do some things from previous packages
(cat >/etc/cron.d/kmod  <<"EOF"
# rmmod -a is a two-hand sweep module cleaner
*/10 * * * *    root    /sbin/rmmod -as
EOF
) &&
chmod ug+x /etc/cron.d/kmod &&
(cat >/etc/cron.weekly/updatedb.cron  <<"EOF"
#!/bin/bash

LOCKFILE=/var/lock/updatedb.lock

# the lockfile is not meant to be perfect, it's just in case the
# two cron scripts get run close to each other to keep them
# from stepping on each other's toes.  The worst that will
# happen is that they will temporarily corrupt the database...
[ -f $LOCKFILE ] && exit 0
touch $LOCKFILE
updatedb --prunepaths='/proc /tmp /mnt /usr/tmp /var/tmp'
rm -f $LOCKFILE
exit 0
EOF
) &&
chmod ug+x /etc/cron.weekly/updatedb &&
(cat >/etc/cron.weekly/makewhatis.cron  <<"EOF"
#!/bin/bash

LOCKFILE=/var/lock/makewhatis.lock

# the lockfile is not meant to be perfect, it's just in case the
# two makewhatis cron scripts get run close to each other to keep
# them from stepping on each other's toes.  The worst that will
# happen is that they will temporarily corrupt the database...
[ -f $LOCKFILE ] && exit 0
touch $LOCKFILE
makewhatis -u -w
rm -f $LOCKFILE
exit 0
EOF
) &&
chmod ug+x /etc/cron.weekly/makewhatis.cron &&
echo f | git `basename $0` &&
git `basename $0` --depends-on $PREREQ1 &&
git --backup `basename $0`

 MK> And then tar/gzip $PKG.  Not all of it is that simple but

Not ANY of MY build scripts are that simple!  ;-)  Like Topsy
they just GREW!  I like the PREREQn lines--it doublechecks that
I've got what I need before getting going.  And if any step
fails, all the rest is bypassed, so I don't have to undo too
much.  The last git does the tar.  Of 130 packages or so, all
but a half-dozen or so will be tar extracts.

 MK> I use a basic fstab template for that and then just edit it

I'm not trying to build a full function, "commercial" style
install any newbie could use, but I want to make something
someone ELSE with a modicum of Linux experience could use
without having to go through the script with "gun & camera"
to figure out how to use it.  They really don't need to know
how to write a fstab.conf in order to do an install--all it
really needs is to plug in a couple device addresses and the
script can do that.  And I HATE using vi!

 MK> for  the targetted drive/partition.  If the target never
 MK> changes, such as in the case of bootable flashdisks then I
 MK> never have to edit it since it is ALWAYS the same as the
 MK> root file system is mounted into a ramdisk.  Seems to me
 MK> that it would be more difficult to write a script then
 MK> simply editing it for unique situations.  However that
 MK> depends on how often you plan to do this and it could be
 MK> scripted not unlike the setup script in Slackware which
 MK> uses a busybox enviroment.

Naw, a couple sed's can do the job with a template.  I'm not
allowing a lot of variations, but typically an install may
have different boot, root, & swap devices.  My fstab script
does that now.  I just need to use what the user told me to
build lilo.conf and/or grub/menu.lst.

 MK> what you need is in either /proc andor /sys.  Also I have the

Not during an install--I'm building a new system.  I expect
I'll be running from a floppy, Tom's RTBT or Trinux, with
the "source" files on a CD.  That part isn't entirely nailed
down quite yet.

 MK> you are using hotplug/udev then this might be a whole lot

Not yet.  This is a 2.4.31 system.  It's roughly equivalent to
a RHL8 or so.  My primary criterion in building it has been
that it should work effectively on a modest classic Pentium.
I use it daily on a 64MB Pentium-MMX 233.  (All but the HX
chipset don't cache above 64MB.  In that respect the tagline
is wrong.)  The first thing I did when I decided to build it
from LFS was write a "mission statement" to guide my decisions.

Paul Rogers, paulgrogers@yahoo.com                       -o)
http://www.angelfire.com/or/paulrogers                   /\\
Rogers' Second Law: Everything you do communicates.     _\_V

... Computer fact #2: You can never have too much RAM.
___ MultiMail/MS-DOS v0.35

---
 * Origin: The Bare Bones BBS (1:105/360)