ISO-Image nitpicks

I just created an i386 -current CD and noticed the strange volume label:
NETBSD_I3868_2991. After a while I realized it was trying to say 2.99.16.

Now, since most other arch names are even longe, I'd like to suggest that
we just leave that out of the volume label, so it becomes NETBSD_29916.
That it's content is i386 is obvious, since the path on the CD starts
with i386/ anyway.

While there I added my favorite mkisofs options:

       -L     Allow ISO9660 filenames to begin  with  a  period.   Usually,  a
              leading  dot is replaced with an underscore in order to maintain
              MS-DOS compatibility.
              This violates the ISO9660 standard, but it happens  to  work  on
              many systems.  Use with caution.
       -hide-joliet-trans-tbl
              Hide the TRANS.TBL files from the Joliet tree.  These files usu-
              ally  don't make sense in the Joliet World as they list the real
              name and the ISO9660 name which may both be different  from  the
              Joliet name.
       -quiet This  makes  mkisofs even less verbose.  No progress output will
              be provided.

What do you think?

Martin

Index: Makefile
===================================================================

Re: ISO-Image nitpicks

On Tue, Mar 01, 2005 at 11:39:40AM +0100, Martin Husemann wrote:
  | I just created an i386 -current CD and noticed the strange volume label:
  | NETBSD_I3868_2991. After a while I realized it was trying to say 2.99.16.
  | 
  | Now, since most other arch names are even longe, I'd like to suggest that
  | we just leave that out of the volume label, so it becomes NETBSD_29916.
  | That it's content is i386 is obvious, since the path on the CD starts
  | with i386/ anyway.

That's fine.

  | While there I added my favorite mkisofs options:
  | 
  |        -L     Allow ISO9660 filenames to begin  with  a  period.   Usually,
  |               a leading dot is replaced with an underscore in order
  |               to maintain MS-DOS compatibility. This violates the
  |               ISO9660 standard, but it happens to work on many
  |               systems. Use with caution.

How safe is this, and what benefit does it give on our current media?

  |        -hide-joliet-trans-tbl
  |               Hide the TRANS.TBL files from the Joliet tree. These
  |               files usually don't make sense in the Joliet World as
  |               they list the real name and the ISO9660 name which may
  |               both be different from the Joliet name.

This seems fine.

  |        -quiet This  makes  mkisofs even less verbose.  No progress output

Re: ISO-Image nitpicks

On Thu, Mar 03, 2005 at 08:15:39AM +1100, Luke Mewburn wrote:
>   |        -L     Allow ISO9660 filenames to begin  with  a  period.   Usually,
>   |               a leading dot is replaced with an underscore in order
>   |               to maintain MS-DOS compatibility. This violates the
>   |               ISO9660 standard, but it happens to work on many
>   |               systems. Use with caution.
> 
> How safe is this, and what benefit does it give on our current media?

NetBSD and win* have no problems with it; but I think it actually does
not change anything for our distrib CD right now (it's just in my set
of options I always use, so I mentioned it). I've removed it.

> This didn't work as expected because of the -v later in the args.
> When I put -quiet after -v I saw the intended effect, and I like it.
> You might as well replace -v with -quiet in MKISOFS_FLAGS, and
> possibly provide a method to allow people to easily append to
> MKISOFS_FLAGS if they want to add -v to increase verbosity.

Ok, like this?

Martin

Index: Makefile
===================================================================
RCS file: /cvsroot/src/etc/Makefile,v
retrieving revision 1.304
diff -u -r1.304 Makefile
--- Makefile	23 Feb 2005 02:10:33 -0000	1.304

another thought on pkg_select

besides FTP and CVS, it would be nice to do an initial install of pkgsrc 
from a CD, e.g. when NetBSD was installed from CD and at the end of 
sysinst, pkg_install is ran.

I guess that sysinst could even provide some hints on where to get things 
from, e.g. when the NetBSD sets were installed from CD hand over a path to 
the CD mountpoint or ask the user to insert the right CD; when the NetBSD 
sets were installed via FTP, that could be indicated too to prefer 
installation over FTP.

  - Hubert

--

-- 
NetBSD - Free AND Open!      (And of course secure, portable, yadda yadda)

Re: another thought on pkg_select

> I guess that sysinst could even provide some hints on where to get things 
> from, e.g. when the NetBSD sets were installed from CD hand over a path to 
> the CD mountpoint or ask the user to insert the right CD; when the NetBSD 
> sets were installed via FTP, that could be indicated too to prefer 
> installation over FTP.

i see, maybe it can be a simple command-line switch, like

-f retreive and uncompress pkgsrc by ftp
-c cvs checkout pkgsrc
-d <path> uncrompress pkgsrc.tar.gz from <path>

additionally, i'll add a "(d)irectory" choice on 1st screen when pkgsrc is 
not found

-------------------------
iMil <imil <at> home.imil.net>                                                 _
      http://gcu-squad.org                          ASCII ribbon campaign ( )
                                                     - against HTML email  X
                                                                 & vCards / \

Re: another thought on pkg_select

On Fri, 4 Mar 2005, iMil wrote:
> i see, maybe it can be a simple command-line switch, like
>
> - -f retreive and uncompress pkgsrc by ftp
> - -c cvs checkout pkgsrc
> - -d <path> uncrompress pkgsrc.tar.gz from <path>
>
> additionally, i'll add a "(d)irectory" choice on 1st screen when pkgsrc is 
> not found

OK, make it setable via some config file (and maybe that 
setup/options/preferences dialog ;)

  - Hubert

--

-- 
NetBSD - Free AND Open!      (And of course secure, portable, yadda yadda)

Re: another thought on pkg_select

On Fri, 4 Mar 2005 13:06:51 +0100 (CET)
iMil <imil <at> home.imil.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> > I guess that sysinst could even provide some hints on where to get things 
> > from, e.g. when the NetBSD sets were installed from CD hand over a path to 
> > the CD mountpoint or ask the user to insert the right CD; when the NetBSD 
> > sets were installed via FTP, that could be indicated too to prefer 
> > installation over FTP.
> 
> i see, maybe it can be a simple command-line switch, like
> 
> - -f retreive and uncompress pkgsrc by ftp
> - -c cvs checkout pkgsrc
> - -d <path> uncrompress pkgsrc.tar.gz from <path>

You may also pass complete "loclal" URL to ftp(1) to fetch pkgsrc from
local-mounted directory, i.e.

	ftp file:///path/to/pkgsrc.tar.gz

Then, if your URL doesn't have 'ftp://' prefix, prepend it with
'file://' one. In this case '-d' switch may be avoided...

--
Mishka.

Re: ISO-Image nitpicks

On Thu, Mar 03, 2005 at 08:48:56AM +0100, Martin Husemann wrote:
  | Ok, like this?

Looks fine.

  | Index: Makefile
  | ===================================================================
  | RCS file: /cvsroot/src/etc/Makefile,v
  | retrieving revision 1.304
  | diff -u -r1.304 Makefile
  | --- Makefile	23 Feb 2005 02:10:33 -0000	1.304
  | +++ Makefile	3 Mar 2005 07:41:26 -0000
  |  <at>  <at>  -57,12 +57,15  <at>  <at> 
  |  MKISOFS?=	mkisofs
  |  DISTRIBREV!=	${HOST_SH} ${KERNSRCDIR}/conf/osrelease.sh -s
  |  # ISO 9660 volume ID.  Note that this can only contain [A-Z0-9_].
  | -ISO_VOLID!=	echo NETBSD_${MACHINE}_${DISTRIBREV} | tr a-z A-Z
  | -MKISOFS_FLAGS+= -J -l \
  | -		-r -T -v \
  | +ISO_VOLID!=	echo NETBSD_${DISTRIBREV} | tr a-z A-Z
  | +MKISOFS_FLAGS+= -J -l -hide-joliet-trans-tbl -r -T \
  |  		-V ${ISO_VOLID} \
  |  		-P "The NetBSD Project" \
  |  		-m "${RELEASEDIR}/${RELEASEMACHINEDIR}/installation/cdrom"
  | +.if ${MKISOFS_FLAGS:N-v}
  | +MKISOFS_FLAGS+=	-quiet
  | +.endif
  | + 
  |  
  |  # MD Makefile.inc may append MD targets to BIN[123].  Make sure all

NetBSD 2.0 on VIA Epia

Hi.

I have just spent an hour trying to boot the NetBSD 2.0 installer CD-ROM on my VIA Mini-ITX system with no
luck, before I got around to asking google for help.

It seems like failing Mini-ITX/VIA installations has been a problem for others before me, according to PR
#26007 (http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=26007)...

My question is: is there any work in progress for solving this problem? I am not sure I would be satisfied with
running 1.6.2 on my systems, since 2.0 would be available to me if it was not for my choice of hardware platform.

Kind regards,

Joakim Bomelin
Petabit Networks

Re: NetBSD 2.0 on VIA Epia

> My question is: is there any work in progress for solving this problem? I
> am not sure I would be satisfied with running 1.6.2 on my systems, since 2.0
> would be available to me if it was not for my choice of hardware platform.

The problem is that it needs someone with access to the failing hardware to
do some serious low-level debugging.  Until the person, hardware (and time)
get together nothing much will happen.

	David

--

-- 
David Laight: david <at> l8s.co.uk