ping Slack dev team
in [Slackware]
|
Prev: LewPitcher.ca tops Google Search!
Next: Xorg and Intel Integrated Graphics Chipset: low resolution
From: Helmut Hullen on 26 Nov 2009 09:58 Hallo, Eef, Du meintest am 26.11.09: > But nano (and mc) _are_ in the (13.0 probably "and before") > distribution (the tagfile for the "ap" set gives: > jed:OPT > joe:OPT > jove:OPT > mc:OPT > nano:REC > in which "OPT" means optional, the question in an interactive install > will have as default NO, while REC is recommended, the question has > as default YES). And "pico" is part of "pine" (and "alpine"), CLI users may install it too. Viele Gruesse Helmut "Ubuntu" - an African word, meaning "Slackware is too hard for me".
From: Mike Jones on 26 Nov 2009 11:00 Responding to Eef Hartman: > Mike Jones <Not(a)arizona.bay> wrote: >> Something as small as Nano = no, but Vi, which is huge (and complex) by >> comparison, is the standard? From the installation disk boot? > > The "vi" in the ramdisk image is NOT a separate program, it is one of > the many commands, served by the single "busybox" executable (all > commands are just sym-links TO that executable): > > BusyBox combines tiny versions of many common UNIX utilities into a > single small executable. It provides minimalist replacements for most of > the utilities you usually find in GNU coreutils, util-linux, etc. The > utilities in BusyBox generally have fewer options than their > full-featured GNU cousins; however, the options that are included > provide the expected functionality and behave very much like their GNU > counterparts. > > The "vi" in busybox is probably less then 50 KB and has the following > command syntax: > vi > > vi [OPTIONS] [FILE]... > > Edit FILE > > Options: > > -c Initial command to run ($EXINIT also available) -R > Read-only - do not write to the file -H Short help > regarding available features > > (from the busybox website: http://www.busybox.net). > > PS: the ls, rm, cp and e.g. grep and gunzip commands are in busybox too, > Pat _is_ using a separate "tar" executable, but there is a minimal tar > in busybox too). Ah. This is a different situation to just sticking a text editor into a dir then. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 26 Nov 2009 11:01 Responding to Martin Schmitz: > Mike Jones wrote: >> Something as small as Nano = no, but Vi, which is huge (and complex) by >> comparison, is the standard? From the installation disk boot? This >> doesn't add up. > > Nano is about five times bigger than standard vi (in disksize, in > functionality vi is about 100 times "bigger"): > > [dakini]~$ ls -l /usr/bin/nano /usr/bin/nvi -rwxr-xr-x 1 root root > 145884 2008-09-16 02:07 /usr/bin/nano -rwxr-xr-x 3 root root 30354 > 2009-04-05 15:39 /usr/bin/nvi > > Martin I can see how that would sway a decision as to which editor to include. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 26 Nov 2009 11:03 Responding to Henrik Carlqvist: > Mike Jones <Not(a)Arizona.Bay> wrote: >> Reqest to Slackware installation media developers: >> >> Can we (extra pretty) PLEASE have Nano on the install disks? > > In case you wont get your request fulfilled and still feel the need for > these or other applications it might be useful to know that it is rather > easy to customize the installation disk. > > I have written a Makefile to build my own installation disks with custom > contents: > > -8<--------------------------------------------- PACKAGE_DIRS = $(shell > find ../slackware/ \( -type d -o -type l \) \ > -exec basename {} \;| \ > grep -v slackware | grep -v PACKAGES.TXT ) > KERNELS = $(shell find kernels/ \( -type d -o -type l \) \ > -exec basename {} \;| \ > grep -v kernels | sort | xargs echo ) > BZIMAGES = $(KERNELS:%=kernels/%/bzImage) > > KERNEL_VERSION = 2.6.24.5 > > LINUX_SRC = kernel_and_patches/linux-$(KERNEL_VERSION).tar.gz PATCHES = > $(wildcard kernel_and_patches/*.patch) > > PKG_BUILD_DIR = /var/tmp/henca/tmp/pkg_build KERNEL_BUILD_DIR = > /var/tmp/kernel_build/linux-$(KERNEL_VERSION) > > .INTERMEDIATE: $(KERNEL_BUILD_DIR) $(PKG_BUILD_DIR) > > KERNEL_PATCH_PKG_DIR = slackware/kernel-upgrades > > PREV_PATCH_NR = $(shell ((ls $(KERNEL_PATCH_PKG_DIR)/*.tgz 2> /dev/null > || \ > echo 1) | \ > sed -e 's/.tgz//' | \ > awk 'BEGIN {FS="-"} ; {print $$NF}' | sort | tail > -1)) > > PATCH_NR = $(strip $(shell (ls $(KERNEL_PATCH_PKG_DIR)/*.tgz 2> > /dev/null || \ > echo 0) | \ > sed -e 's/.tgz//' | \ > awk 'BEGIN {FS="-"} ; {print $$NF}' | sort | tail -1 | \ > xargs echo 1+ | bc )) > PREV_PATCH_PKG_FILE= > kernel-patches-$(KERNEL_VERSION)-i486-$(PREV_PATCH_NR).tgz > KERNEL_PATCH_PKG_FILE = > kernel-patches-$(KERNEL_VERSION)-i486-$(PATCH_NR).tgz PREV_PATCH_PKG = > $(KERNEL_PATCH_PKG_DIR)/$(PREV_PATCH_PKG_FILE) KERNEL_PATCH_PKG= $(shell > pwd)/$(KERNEL_PATCH_PKG_DIR)/$(KERNEL_PATCH_PKG_FILE) > > # Clean up kernel build directory > all: /var/tmp/dvd_install.iso > $(RM) -r $(KERNEL_BUILD_DIR) $(PKG_BUILD_DIR) > > # Only one kernel can be built at a time .NOTPARALLEL: > > /var/tmp/dvd_install.iso: nfs_install.iso isolinux/setpkg.nfs \ > $(wildcard slackware/*/*) \ > $(PREV_PATCH_PKG) > cd isolinux && ln -sf setpkg.dvd setpkg && cd .. mkisofs -o $@ \ > -R -J -V "My Slamd121 Install `date +%y%m%d`" \ -hide-rr-moved > -f\ > -v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \ > -sort isolinux/iso.sort \ > -b isolinux/isolinux.bin \ > -c isolinux/isolinux.boot \ > -x initrd_src \ > -A "My Slamd121 Install DVD" . > echo $@ created > > nfs_install.iso: isolinux/isolinux.cfg \ > isolinux/message.txt \ > isolinux/initrd.img \ > isolinux/setpkg.nfs \ > $(wildcard isolinux/*.img isolinux/*.dsk) > cd isolinux && ln -sf setpkg.nfs setpkg && cd .. mkisofs -o $@ \ > -R -J -V "My Slamd121 NFS Install `date +%y%m%d`" \ > -hide-rr-moved -f\ > -v -d -N -no-emul-boot -boot-load-size 4 -boot-info-table \ > -sort isolinux/iso.sort \ > -b isolinux/isolinux.bin \ > -c isolinux/isolinux.boot \ > -x slackware \ > -x nfs_install.iso \ > -x initrd_src \ > -A "My Slamd121 NFS Install CD" . > > isolinux/isolinux.cfg: isolinux/isolinux.cfg.start isolinux/message.txt > cp $@.start $@ > for KERNEL in $(KERNELS); do \ > echo "label $$KERNEL" >> $@; \ > echo "kernel /kernels/$$KERNEL/bzImage" >> $@; \ echo -n > "append initrd=initrd.img load_ramdisk=1 " >> $@; \ echo > "prompt_ramdisk=0 rw SLACK_KERNEL=$$KERNEL" >> $@; \ > done > > isolinux/message.txt: isolinux/message.txt.start $(BZIMAGES) > cp $@.start $@ > echo $(KERNELS) | fold -s >> $@ > > isolinux/initrd.img: initrd_src $(shell find initrd_src -type d -o -type > f ) > cd $< && find . | cpio -o -H newc | gzip > ../$@ > > initrd_src: > ifeq ($(shell whoami),root) > mkdir $@ && cd $@ && gzip -d < ../isolinux/initrd.img | cpio -i > else > @echo Run \"make initrd_src\" as root! && false > endif > slack_dirs: > find slackware -type l -exec $(RM) {} \; cd slackware && \ > ln -s $(foreach DIR, $(PACKAGE_DIRS), ../../slackware/$(DIR)) . > > kernels/%/bzImage: $(KERNEL_BUILD_DIR) kernels/%/config > echo Compiling $@ > cp $(@D)/config $</.config > cd $< && make bzImage > $(RM) $(@D)/System.map.gz > cp $</arch/x86_64/boot/bzImage $@ > cp $</System.map $(@D) > gzip -9 $(@D)/System.map > > $(KERNEL_BUILD_DIR): $(LINUX_SRC) $(wildcard kernels/*/config) > $(PATCHES) > mkdir -p $(@D) > cat $< | (cd $(@D) && tar -xzvf -) > $(foreach PATCH, $(PATCHES), \ > cat $(PATCH) | (cd $@ && patch -p1) &&) true; > > $(PREV_PATCH_PKG): $(BZIMAGES) > ( echo " Patched kernel" && echo && \ > tail -9 kernel_and_patches/patches.txt | \ awk '{$$1=""; > print $$0}' && printf "\n\n\n\n\n\n\n\n\n\n" ) | \ sed -e > 's/^/kernel-patches:/' | head -11 > \ > $(KERNEL_PATCH_PKG:%.tgz=%.txt) > mkdir -p $(PKG_BUILD_DIR)/install/new_kernels cp -rp > $(KERNELS:%=kernels/%) $(PKG_BUILD_DIR)/install/new_kernels cp > kernel_and_patches/doinst.sh $(PKG_BUILD_DIR)/install cd > $(PKG_BUILD_DIR) && /sbin/makepkg -c n $(KERNEL_PATCH_PKG) > -8<--------------------------------------------- > > The rule to look at above is the rule for isolinux/initrd.img which > takes the contents of initrd_src and creates your new initrd.img. If you > have a working nano in the directory tree of initrd_src you will get > nano on the installation disk. > > If initrd_src doesn't already exist it is created by unpacking the > contents of your current isolinux/initrd.img. This unpacking with cpio > has to be done as root to keep ownership of files in the directory tree, > all the other targets can be built as a normal user. > > The Makefile above does a lot more than just creating a custom > initrd.img, it also patches and builds kernels with different > configurations and creates a install DVD image as well as a smaller CD > image used for NFS installs. Your imagination is the only limit on how > Slackware can be customized. > > regards Henrik Co-incidentally, this lines up with another project I've been tinkering with. It wouldn't make any difference to whats available from the install disk boot up though. :( -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs.
From: Mike Jones on 26 Nov 2009 11:03
Responding to Lew Pitcher: > On November 26, 2009 07:35, in alt.os.linux.slackware, Eef Hartman > (E.J.M.Hartman(a)tudelft.nl) wrote: > >> Mike Jones <Not(a)arizona.bay> wrote: >>> If you're going to have obscure stuff like joe and jove in the default >>> install, the Nano should be in there too, to be fair about it. >> >> But nano (and mc) _are_ in the (13.0 probably "and before") >> distribution (the tagfile for the "ap" set gives: >> jed:OPT >> joe:OPT >> jove:OPT >> mc:OPT >> nano:REC > [snip] > > I took the OP's request to mean to ask for Nano on the "Live system" > part of the install DVD. Nano and Pico have been readily available as > parts of install packages for quite some time. Yup. -- *=( http://www.thedailymash.co.uk/ *=( For all your UK news needs. |