On Sat, 27 Sep 2014 03:38:30 -0600 (MDT)
> >so is there a better way to just build a kernel? i'm not going to build a
> >whole release just for one kernel, especially when experimenting. and i mean
> >a RAMDISK kernel. i think its great the things i can do with openbsd, even
> >when it is not what is intended.
> 
> tough.

i wasn't whining, i was ASKING, and that was only an aside, not the main point
of my last message, which was an analysis of 'maketz.sh'.

this is only what got me looking at 'maketz.sh' and 'list2sh.awk'. my findings
there are relevant.

> I'm sorry, but this is the build process that makes snapshots.
> It serves that purpose and is designed for that.

did i ever say or suggest otherwise?

> It is not carveable in the way you want to use it.

obviously it is, even if 'unsupported'. i got the idea from a user on one of
the lists years ago, so it works for at least two people.

and that's still not relevant to what i said about 'maketz.sh'.

> It will not be changed.

i don't expect it to be changed for ME. my points about 'maketz.sh' are still
valid until someone show otherwise. THEY HAVE NOTHING TO DO WITH MY
'UNSUPPORTED' USE.

> You are on your own, really.

let me quote myself, the paragraph above what you quoted:
> > i know what i was doing was 'unsupported', and things could get broken, but 
> > it
> > hasn't failed me yet. i would've just ignored the maketz.sh error as i have
> > been.

which by the way is irrelevant to the point i was making about 'maketz.sh'.
this 'unsupported use' is merely why i was poking around there.

and me again:
> > and once more, i ONLY brought this up because of maketz.sh looks irrelevent.
> > i have been using openbsd for more years than i can honestly remember, i 
> > know
> > nobody here 'makes music for the fans'.

and to clarify 'nobody here makes music for the fans', means, to quote you:
> You are on your own, really.

so we are in complete agreement here.


and this is all irrelevant. someone address what i said about 'maketz.sh'.
the fix i made ONLY eliminates 'maketz.sh', not its functionality, which
is only *2 lines* and can be put in 'list2sh.awk' instead.

the fact that it allows my 'blasphemous' behaviour was also irrelevant, i
didn't care about that. i can just add 'DESTDIR=/' to my automated scripts
to make this kernel, no biggie. i don't NEED a change to the system, and
never asked for one for myself, to quote myself again:
> > and once more, i ONLY brought this up because of maketz.sh looks irrelevent.

now, did you read any of what i said about 'maketz.sh'? the proposed fix was to
eliminate it completely, placing its meager contents in 'list2sh.awk'.
i know you probably get dumb requests all the time, but maybe you shouldn't
jump to conclusions. i think i was pretty explicit, and if not, i would love
to know where i was ambiguous, to avoid it in the future.

back to 'maketz.sh':

simply, all 'maketz.sh' does is run:
    cd $destdir/usr/share/zoneinfo
    ls -1dF `tar cvf /dev/null [A-Za-y]*`

and this can be done in 'list2sh.awk' instead of said script calling 'maketz.sh'
was:
    printf("(cd ${TARGDIR}; sh $UTILS/maketz.sh $DESTDIR)\n");

i proposed:
    printf("(cd $DESTDIR/usr/share/zoneinfo && ls -1dF `tar cvf /dev/null 
[A-Za-y]*` >${TARGDIR}/var/tzlist)\n");

for a measly two lines of script. the error check is irrelevant if used
properly because $DESTDIR should always be set, thus the arg check is useless,
it should always be true (if used 'THE RIGHT WAY') and that leave 2 lines of
code. does 'maketz.sh' need to exist for two lines of code that can be put in
'list2sh.awk'?

once again, that this fixed *MY* problem is irrelevant. i don't want your help.
i don't want anyone's help. never did. to quote myself again on this point:
> > and once more, i ONLY brought this up because of maketz.sh looks irrelevent.

i left $DESTDIR in the fix, since i now know it's relevant.

now here is what i said again, if there is a logical flaw in my argument, i
would love to hear it:

> > what i am concerned with there is when distrib/miniroot/list2sh.awk is run, 
> > to
> > create the bsd.rd miniroot 'var/tzlist', the relevant line in list2sh.awk 
> > is:
> > 
> >         printf("(cd ${TARGDIR}; sh $UTILS/maketz.sh $DESTDIR)\n");
> > 
> > which calls maketz.sh:
> >         #!/bin/sh
> > 
> >         destdir=$1
> > 
> >         if [ $# -lt 1 ]; then
> >                 echo usage: maketz.sh DESTDIR
> >                 exit 0
> >         fi
> > 
> >         (
> >                 cd $destdir/usr/share/zoneinfo
> >                 ls -1dF `tar cvf /dev/null [A-Za-y]*`
> >         ) > var/tzlist
> > 
> > however my questioning of 'maketz.sh' use is sound, and it can be bypassed
> > altogether in 'list2sh.awk':
> > 
> >         printf("(cd $DESTDIR/usr/share/zoneinfo && ls -1dF `tar cvf 
> > /dev/null [A
> > 
> > as it stands, if $DESTDIR is unset it gives the error i first mentioned:
> > 
> >   usage: maketz.sh DESTDIR
> > 
> > and no 'var/tzlist' is created, which presumably will not happen if i were
> > using it 'properly'.
> > 
> > with the change to 'list2sh.awk' above, if $DESTDIR is unset, then it merely
> > does the same thing as if $DESTDIR=/
> > 
> > so if $DESTDIR is unset, it does 'cd /usr/share/zoneinfo'.
> >
> > and if $DESTDIR is set (to / as in release(8)) then it does
> > 'cd //usr/share/zoneinfo'
> > 
> > and if there is no $DESTDIR/usr/share/zoneinfo, it doesn't create a file of
> > potentially random crap (the &&).
> > 
> > so, with the below patch, if $DESTDIR is set, is should function as it does
> > now, and 'maketz.sh' can be eliminated altogether. and if DESTDIR is unset,
> > it still works (presumably there will always be a /usr/share/zoneinfo on
> > any system building release)
> > 
> > --- list2sh.awk.orig    Fri Feb 21 14:33:31 2014
> > +++ list2sh.awk Sat Sep 27 05:35:09 2014
> > @@ -60,7 +60,7 @@ $1 == "CRUNCHSPECIAL" {
> >  }
> >  $1 == "TZ" {
> >         printf("echo '%s'\n", $0);
> > -       printf("(cd ${TARGDIR}; sh $UTILS/maketz.sh $DESTDIR)\n");
> > +        printf("(cd $DESTDIR/usr/share/zoneinfo && ls -1dF `tar cvf 
> > /dev/null [A-Za-y]*` >${TARGDIR}/var/tzlist)\n");
> >         next;
> >  }
> >  $1 == "COPYDIR" {
> > 

not that i expect it to be accepted, but here is the patch again, fixing a
mistake of my own (i forgot the trailing '\n' in the printf())

--- list2sh.awk.orig    Fri Feb 21 14:33:31 2014
+++ list2sh.awk Sat Sep 27 07:48:09 2014
@@ -60,7 +60,7 @@ $1 == "CRUNCHSPECIAL" {
 }
 $1 == "TZ" {
        printf("echo '%s'\n", $0);
-       printf("(cd ${TARGDIR}; sh $UTILS/maketz.sh $DESTDIR)\n");
+        printf("(cd $DESTDIR/usr/share/zoneinfo && ls -1dF `tar cvf /dev/null 
[A-Za-y]*` >${TARGDIR}/var/tzlist)\n");
        next;
 }
 $1 == "COPYDIR" {

Reply via email to