Re: picobsd and mdconfig
On line 336 of the script, you export dead air, resulting in
and Makefile.conf handles that in a way
similar to the one you show below.
CONFIG=${CONFIG:-config}
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Fri, Jun 22, 2001 at 12:26:39PM +0200, Luigi Rizzo wrote:
On line 336 of the script, you export dead air, resulting in
and Makefile.conf handles that in a way
similar to the one you show below.
Luigi, you cannot run dead air. Makefile.conf only handles that
if the variable does not exist, not if the variable is empty.
CONFIG=${CONFIG:-config}
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
Luigi, you cannot run dead air. Makefile.conf only handles that
if the variable does not exist, not if the variable is empty.
ok my fault :)
luigi
CONFIG=${CONFIG:-config}
cheers
luigi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-small in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled: | vnconfig has changed to mdconfig in -current, but the | picobsd build script still references vnconfig, also | CONFIG isn't defined anywhere in the script, resulting | in the process dying when it tries to configure the | kernel, a couple of punctuation mods here and there, | and dumped the vnode is... log. Hi Omachonu, Do you mind posting a URL with the above patch in unified form? (i.e. diff -u) Thanks, Michael -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote: On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled: | vnconfig has changed to mdconfig in -current, but the | picobsd build script still references vnconfig, also | CONFIG isn't defined anywhere in the script, resulting | in the process dying when it tries to configure the | kernel, a couple of punctuation mods here and there, | and dumped the vnode is... log. Hi Omachonu, Do you mind posting a URL with the above patch in unified form? (i.e. diff -u) http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch Thanks, Michael -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Omachonu Ogali [EMAIL PROTECTED] http://www.informationwave.net To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 11:02:02AM -0400, Omachonu Ogali scribbled:
| On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
| On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| | vnconfig has changed to mdconfig in -current, but the
| | picobsd build script still references vnconfig, also
| | CONFIG isn't defined anywhere in the script, resulting
| | in the process dying when it tries to configure the
| | kernel, a couple of punctuation mods here and there,
| | and dumped the vnode is... log.
|
| Hi Omachonu,
|
| Do you mind posting a URL with the above patch
| in unified form? (i.e. diff -u)
|
|
|http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch
Attached is my questions about this.
The rest of it looks great. We shouldn't have any problem
with this patch at all. I will test this tonight or at USENIX.
--
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+
| --- src/release/picobsd/build/picobsd.origThu Jun 21 04:49:46 2001
| +++ src/release/picobsd/build/picobsd Thu Jun 21 10:08:00 2001
| @@ -2,3 +2,3 @@
| -gzip -9 etc/*
| +for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
| log --- Compressed files in etc/
Good idea!
| +newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
| +mount /dev/md${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
| +log `df /dev/md${VNUM}c`
| }
| @@ -527,3 +518,3 @@
| log --- Copy generic floppy_tree into MFS...
| - cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
| + cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
| +
| +du -k kernel.gz
| +df -k ${MFS_MOUNTPOINT}
| +cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
Why do you call du and df?
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 10:17:52AM -0500, Michael C . Wu wrote:
On Thu, Jun 21, 2001 at 11:02:02AM -0400, Omachonu Ogali scribbled:
| On Thu, Jun 21, 2001 at 10:03:27AM -0500, Michael C . Wu wrote:
| On Thu, Jun 21, 2001 at 10:52:32AM -0400, Omachonu Ogali scribbled:
| | vnconfig has changed to mdconfig in -current, but the
| | picobsd build script still references vnconfig, also
| | CONFIG isn't defined anywhere in the script, resulting
| | in the process dying when it tries to configure the
| | kernel, a couple of punctuation mods here and there,
| | and dumped the vnode is... log.
|
| Hi Omachonu,
|
| Do you mind posting a URL with the above patch
| in unified form? (i.e. diff -u)
|
|
http://www.informationwave.net/~missng/freebsd/notsubmitted/picobsd-build.unified.patch
Attached is my questions about this.
The rest of it looks great. We shouldn't have any problem
with this patch at all. I will test this tonight or at USENIX.
--
+---+
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
| http://iteration.net/~keichii | Yes, BSD is a conspiracy. |
+---+
| --- src/release/picobsd/build/picobsd.orig Thu Jun 21 04:49:46 2001
| +++ src/release/picobsd/build/picobsd Thu Jun 21 10:08:00 2001
| @@ -2,3 +2,3 @@
| -gzip -9 etc/*
| +for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
| log --- Compressed files in etc/
Good idea!
| +newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
| +mount /dev/md${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
| +log `df /dev/md${VNUM}c`
| }
| @@ -527,3 +518,3 @@
| log --- Copy generic floppy_tree into MFS...
| - cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
| + cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
| +
| +du -k kernel.gz
| +df -k ${MFS_MOUNTPOINT}
| +cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
Why do you call du and df?
That can be removed, that was just for debugging sake, I wanted to see
how big the image is, and how much free space I had available on the
floppy, so I could say, 'the image overshoots the floppy by NNN kB'
and then work on the space problem from there...
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
Hi, would you mind resubmitting a patch for the version of picobsd i committed this morning, also keeping in mind the following: * it would be better to define a variable, say MD, which holds the string vn or md, and is used in accessing the memory device, so we have mostly the same script working on both current and stable with just a one-line change. * you are recursively gzipping files in /etc now, so you should also modify the mfs_tree/etc/rc script which decompresses things; This might be annoying as gzip is unable to recurse in a directory tree. * re. the CONFIG variable... it does not seem to give problem with the version i committed this morning. I think there was a bug in the previous commit, but now it should be ok. * i am not sure the way you handle arguments is correct, from your patch it appears that you ignore THETYPE (first argument) if there are not two arguments. This is wrong, the second argument is optional. thanks luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo scribbled: | would you mind resubmitting a patch for the version of | picobsd i committed this morning, also keeping in mind the | following: | | * it would be better to define a variable, say MD, which holds | the string vn or md, and is used in accessing the memory | device, so we have mostly the same script working on both current | and stable with just a one-line change. | | * you are recursively gzipping files in /etc now, so you should | also modify the mfs_tree/etc/rc script which decompresses things; | This might be annoying as gzip is unable to recurse in a | directory tree. | | * re. the CONFIG variable... it does not seem to give problem with | the version i committed this morning. I think there was a bug | in the previous commit, but now it should be ok. | | * i am not sure the way you handle arguments is correct, from your | patch it appears that you ignore THETYPE (first argument) if there | are not two arguments. This is wrong, the second argument is optional. I have more questions regarding this: * Do we want NO_SWAPPING on or off in PicoBSD? I understand that many PicoBSD devices do not have swapspace. However, my understand of -current is that we do require swapping to work well. * Do we want SOFTUPDATES? * Statically compiling device.hints seems to be awkward. Perhaps we should be using a customized /boot/device.hints. This way, many devices can be disabled or enabled easily without recompiling PicoBSD/ version -- +---+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://iteration.net/~keichii | Yes, BSD is a conspiracy. | +---+ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
* Do we want NO_SWAPPING on or off in PicoBSD? I understand that many PicoBSD devices do not have swapspace. However, my understand of -current is that we do require swapping to work well. given that in the vast majority of cases you don't have a choice... * Do we want SOFTUPDATES? same as above. who cares, the memory fs is mostly readonly, and secondary storage is generally unavailable. * Statically compiling device.hints seems to be awkward. if i am not mistaken, it is the bootloader which should read the hints, but in picobsd there is no bootloader, so we have no other choice. I doubt this is a big issue, anyways, most hardware is PnP these days. flexibility is good, but reality (with its constraints) comes first :) cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd and mdconfig
On Thu, Jun 21, 2001 at 06:18:47PM +0200, Luigi Rizzo wrote:
would you mind resubmitting a patch for the version of
picobsd i committed this morning, also keeping in mind the
following:
That patch was based off of your 8:49AM (revision 1.7) commit
this morning.
* it would be better to define a variable, say MD, which holds
the string vn or md, and is used in accessing the memory
device, so we have mostly the same script working on both current
and stable with just a one-line change.
The method of allocating and releasing a md and vn are
different, would it be too much to maintain two different
scripts (-stable and -current) until mdconfig replaces
its counterpart?
* you are recursively gzipping files in /etc now, so you should
also modify the mfs_tree/etc/rc script which decompresses things;
This might be annoying as gzip is unable to recurse in a
directory tree.
Good idea, I missed that.
* re. the CONFIG variable... it does not seem to give problem with
the version i committed this morning. I think there was a bug
in the previous commit, but now it should be ok.
On line 336 of the script, you export dead air, resulting in
no program being passed to Makefile.conf, my snippet of code
at the bottom should be removed and a more appropriate line
inserted after line 62 along the lines of:
CONFIG=${CONFIG:-config}
I missed that portion of that script when I was looking at it
this morning.
* i am not sure the way you handle arguments is correct, from your
patch it appears that you ignore THETYPE (first argument) if there
are not two arguments. This is wrong, the second argument is optional.
Yeah, that should be $1 not $2.
thanks
luigi
---+-
Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione
http://www.iet.unipi.it/~luigi/ . Universita` di Pisa
TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy)
Mobile +39-347-0373137
---+-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Omachonu Ogali
[EMAIL PROTECTED]
http://www.informationwave.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
