Latest 5.2.8 distro confirmation
Latest 5.2.8 distro confirmation
Could someone with Lucid 528.005 give me their: cat /etc/DISTRO_SPECS
Re: Latest 5.2.8 distro confirmation
From my original full install of 528.005....Semme wrote:Could someone with Lucid 528.005 give me their: cat /etc/DISTRO_SPECS
Code: Select all
# cat /etc/DISTRO_SPECS
#One or more words that identify this distribution:
DISTRO_NAME='Lucid '
#A three-digit numeric value, version number of this distribution:
DISTRO_VERSION=528
#A two-digit numeric value, minor-version number of this distribution:
DISTRO_MINOR_VERSION=00
#The distro whose binary packages were used to build this distribution:
DISTRO_BINARY_COMPAT='ubuntu'
#Prefix for some filenames: exs: lupusave.2fs, lupu-528.sfs
DISTRO_FILE_PREFIX='lupu'
#The version of the distro whose binary packages were used to build this distro:
DISTRO_COMPAT_VERSION='lucid'
#the kernel pet package used:
DISTRO_KERNEL_PET='linux_kernel-2.6.33.2-tickless_smp_patched-L3.pet'
#16-byte alpha-numeric ID-string appended to vmlinuz, lupu_528.sfs, zl528332.sfs and devx.sfs:
DISTRO_IDSTRING='l528120405083316'
#Puppy default filenames...
#Note, the 'SFS' files below are what the 'init' script in initrd.gz searches for,
#for the partition, path and actual files loaded, see PUPSFS and ZDRV in /etc/rc.d/PUPSTATE
DISTRO_PUPPYSFS='lupu_528.sfs'
DISTRO_ZDRVSFS='zl528332.sfs'
#
Here is the Code from Precise, that creates the IDSTRING. The Code is to find in /usr/sbin/remasterpup2 at line154:
And this is the one from the Lucid Puppy 528-004
Can't tell its position in the script, since I've modified it a lot, so its line number has changed.
Code: Select all
#100913 generate a new id-string...
IDDATE="`date +%y%m%d%H%M%S`" #12 bytes, ex: 100911153319
IDPREFIX="`echo -n "$DISTRO_FILE_PREFIX" | cut -b 1`"
#vDISTRO_VERSION="`echo -n "$DISTRO_VERSION" | cut -b 1-3`" #in case it ever gets bigger than 3 chars.
#IDSTRING="${IDPREFIX}${vDISTRO_VERSION}${IDDATE}"
#...needs to be appended to vmlinuz, puppy.sfs, zdrv.sfs and devx.sfs
#110422 increase size of idstring to 32 bytes...
IDSTRING="${IDPREFIX}${IDDATE}ZZZZ${DISTRO_VERSION}"
#...ZZZZ reserved space for future use.
LEN1=`echo -n "$IDSTRING" | wc -c`
LEN2=`expr 32 - $LEN1`
EXTX=''
while [ $LEN2 -gt 0 ];do
LEN2=`expr $LEN2 - 1`
EXTX="${EXTX}X"
done
IDSTRING="${IDSTRING}${EXTX}" #32 bytes ex: w110423092024ZZZZ5.1.2XXXXXXXXXX
Code: Select all
# 100913 generate a new id-string...
IDDATE="`date +%y%m%d%H%M%S`" #12 bytes, ex: 100911153319
IDPREFIX="`echo -n "$DISTRO_FILE_PREFIX" | cut -b 1`"
vDISTRO_VERSION="`echo -n "$DISTRO_VERSION" | cut -b 1-3`" #in case it ever gets bigger than 3 chars.
IDSTRING="${IDPREFIX}${vDISTRO_VERSION}${IDDATE}"
# ...needs to be appended to vmlinuz, puppy.sfs, zdrv.sfs and devx.sfs
[b][url=http://lazy-puppy.weebly.com]LazY Puppy[/url][/b]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
[b][url=http://rshs-dna.weebly.com]RSH's DNA[/url][/b]
[url=http://murga-linux.com/puppy/viewtopic.php?t=91422][b]SARA B.[/b][/url]
Semmel, the Searching for IDSTRING by Content...
gave the following hits >
http://bkhome.org/blog/?viewDetailed=01806
http://bkhome.org/blog/?viewDetailed=01812
http://bkhome.org/blog/?viewDetailed=01936
http://bkhome.org/blog/?viewDetailed=02228
http://bkhome.org/blog2/?viewDetailed=00042
Quintessence is that
The Woof build script 3builddistro generates a unique 16-byte id-string, "w071100912163021" in the above example. This is stored in /etc/DISTRO_SPECS and also in /DISTRO_SPECS in the initramfs -- so, the 'init' script in the initrd.gz file can read the id-string and then search for the files.
3builddistro appends the id-string onto the end of vmlinuz, puppy.sfs, zdrv.sfs and devx.sfs (or whatever they are named). It is this id-string that enables the init script to find the exact required files, regardless of their names.
Have not used Woof of Woof2 yet,
and think I remember some stray directory at Wary-0.94-0.98 times
that created some /initrdUUID directory on top level of the rootfs being run frugal PUPMODE=12 .
gave the following hits >
http://bkhome.org/blog/?viewDetailed=01806
http://bkhome.org/blog/?viewDetailed=01812
http://bkhome.org/blog/?viewDetailed=01936
http://bkhome.org/blog/?viewDetailed=02228
http://bkhome.org/blog2/?viewDetailed=00042
Quintessence is that
The Woof build script 3builddistro generates a unique 16-byte id-string, "w071100912163021" in the above example. This is stored in /etc/DISTRO_SPECS and also in /DISTRO_SPECS in the initramfs -- so, the 'init' script in the initrd.gz file can read the id-string and then search for the files.
3builddistro appends the id-string onto the end of vmlinuz, puppy.sfs, zdrv.sfs and devx.sfs (or whatever they are named). It is this id-string that enables the init script to find the exact required files, regardless of their names.
Have not used Woof of Woof2 yet,
and think I remember some stray directory at Wary-0.94-0.98 times
that created some /initrdUUID directory on top level of the rootfs being run frugal PUPMODE=12 .