Subject: Re: How can I edit the packages install on the ISO?
To: None <poff@sixbit.org>
From: Jeremy C. Reed <reed@reedmedia.net>
List: netbsd-help
Date: 01/06/2003 09:34:17
On Fri, 3 Jan 2003 poff@sixbit.org wrote:

> > See http://www.netbsd.org/Documentation/bootcd.html for the Bootable CD
> > ROM How-To.
>
> Thanks, from what I understand I just copy the current-i386 installation
> files (118mb again I think so that's not bad) and then I can make it all
> into an ISO. I can just copy my already-burned iso onto the /cdsources as
> well. In fact, looking at the sets, would it be terrible if I just stuck
> in there compiled version of bash and pico, stuff like that and retarred
> it up as base.tgz? I know the /var/db/pkg stuff would be a bit screwy when
> I come to pkg_install (I don't really understand the db thing anyway)...

Sure.

Instead of just copying the files, chroot to the new directory hierarchy
(after you unextract the base) and use pkg_add. (This is how I do it with
my CDs.)

You can also use pkg_admin to "rebuild" it.

(This reminds me: I don't think there is any integrity checking, but I
guess that doesn't matter since the sysinst is usually downloaded from
same place.)

> Another thing I see is, couldn't I just tar up my compiled kernel which is
> (very) specific for this system and add it as KERN-LITE.tgz in the sets?
> Would I have to add it in "kernel" as well?

Just replace your main kernel since this is for your own use.

> Is there any other way to install pksrc apart from adding it as a modified
> set but untarring it into /usr then retarring so the root directory for
> the set is /usr/pkgsrc instead of /pkgsrc? Actually, it doesn't really
> matter, but would I be able to rename the pkgsrc.tar.gz pkgsrc.tgz and
> stick it in sets to be extracted automatically? Is this just *too*
> disgusting to do? I'm new to all this if you hadn't noticed already ;)

That should be fine.

(You could also unextract it, and then rebuild the tar file as
/usr/pkgsrc.)

> Another question, there is a user-ppp project from
> speedtouch.sourceforge.net, again, would I just add the compiled binary
> into base and add a ppp.conf in a ppp directory for etc?

That should be fine. (If that version of user-ppp isn't in pkgsrc, please
consider submitting a pkgsrc entry for it. Thanks.)

> Maybe a better way is to make another set called "poff" or whatever and
> include in that set pkgsrc, syssrc, compiled binaries for ppp, maybe some
> binaries for pico and bash (again I'm unclear about the best way to
> auto-add packages) and then just select it during the installation?? I
> would add a /etc/ppp directory in it too.

That should be fine too.

> One more thing. I downloaded the 1.6 iso a month or so ago - since then
> the x source has been updated with a patch for my video driver. What I
> *did* have to do was install netbsd from my iso without x, then compile x
> from the x sources which took a LONG time. How can I find out if the iso
> has been updated, and if it contains the latest x binaries? I guess the
> new x src is in netbsd-current, and that netbsd-release-1.6 doesn't get
> changed from ... release?

I think it does get changed a little. You can find out by visiting the
cvsweb.

> > Look at the code (mostly the Makefiles) under src/distrib/utils/sysinst/,
> > src/distrib/i386/floppies/ (assuming i386), and the src/etc/Makefile
> > (about building ISO).
>
> I will have a look, but I'm no genius, and will see if there's anything
> useful I can mess about with. I guess I'd have to build into my /cdsources
> from the src?

Yes.

> > Any easy way would by just to build own cdsources/ directory (like
> > described in the Bootable CD ROM HOWTO) that also includes the packages
> > you want in the packages/1.6/i386/All/ directory. Then manually install as
> > normal.
>
> As above, do you mean just add bash-xxx.tgz as a file and once installed
> run pkg_install bash like that? I'd kinda like it integrated...

That's what I meant. Integrated would be easier too. But you could
modify sysinst to handle packages too, but that is getting harder. (And
probably not a good idea to waste too much time with adding new features
to sysinst -- better to start with a new framework.)

   Jeremy C. Reed
   http://bsd.reedmedia.net/