Re: PicoBSD build error after r281316
2015-06-22 17:03 GMT+02:00 Luigi Rizzo ri...@iet.unipi.it: On Monday, June 22, 2015, Stefano Garzarella stefanogarzare...@gmail.com wrote: Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase (release/picobsd/build/picobsd --init): In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder.c:23: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory I found that the r281316 commit introduces these lines that maybe cause these errors: lib/liblzma/config.h:152 /* Define to 1 if you have the immintrin.h header file. */ #if defined(__FreeBSD__) defined(__amd64__) #define HAVE_IMMINTRIN_H 1 #endif Before r281316 all work fine. This seems a clang vs our-old-GCC issue. Picobsd is compiled with GCC. Wonder if we should consider the compiler in the conditions to check for immintrin.h availability. I think the same. Commenting those lines the picobsd script works fine. Thanks, Stefano Cheers Luigi Thanks, Stefano Garzarella -- *Stefano Garzarella* Software Engineer e-mail: stefano.garzare...@gmail.com github: http://github.com/stefano-garzarella linkedin: http://it.linkedin.com/pub/stefano-garzarella -- -+--- Prof. Luigi RIZZO, ri...@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/. Universita` di Pisa TEL +39-050-2217533 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -+--- -- *Stefano Garzarella* Software Engineer e-mail: stefano.garzare...@gmail.com github: http://github.com/stefano-garzarella linkedin: http://it.linkedin.com/pub/stefano-garzarella ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: PicoBSD build error after r281316
On Monday, June 22, 2015, Stefano Garzarella stefanogarzare...@gmail.com wrote: Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase (release/picobsd/build/picobsd --init): In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder.c:23: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory I found that the r281316 commit introduces these lines that maybe cause these errors: lib/liblzma/config.h:152 /* Define to 1 if you have the immintrin.h header file. */ #if defined(__FreeBSD__) defined(__amd64__) #define HAVE_IMMINTRIN_H 1 #endif Before r281316 all work fine. This seems a clang vs our-old-GCC issue. Picobsd is compiled with GCC. Wonder if we should consider the compiler in the conditions to check for immintrin.h availability. Cheers Luigi Thanks, Stefano Garzarella -- *Stefano Garzarella* Software Engineer e-mail: stefano.garzare...@gmail.com javascript:_e(%7B%7D,'cvml','stefano.garzare...@gmail.com'); github: http://github.com/stefano-garzarella linkedin: http://it.linkedin.com/pub/stefano-garzarella -- -+--- Prof. Luigi RIZZO, ri...@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/. Universita` di Pisa TEL +39-050-2217533 . via Diotisalvi 2 Mobile +39-338-6809875 . 56122 PISA (Italy) -+--- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
PicoBSD build error after r281316
Hi all, I'm using picobsd on FreeBSD-head (r284697) to build a picobsd image with gcc, but I have the following errors during the init phase (release/picobsd/build/picobsd --init): In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder.c:23: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lz/lz_encoder_mf.c:16: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lzma/lzma_encoder_optimum_fast.c:13: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory In file included from /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/lzma/lzma_encoder_optimum_normal.c:14: /usr/home/stefano/repos/freebsd/lib/liblzma/../../contrib/xz/src/liblzma/common/memcmplen.h:19:24: error: immintrin.h: No such file or directory I found that the r281316 commit introduces these lines that maybe cause these errors: lib/liblzma/config.h:152 /* Define to 1 if you have the immintrin.h header file. */ #if defined(__FreeBSD__) defined(__amd64__) #define HAVE_IMMINTRIN_H 1 #endif Before r281316 all work fine. Thanks, Stefano Garzarella -- *Stefano Garzarella* Software Engineer e-mail: stefano.garzare...@gmail.com github: http://github.com/stefano-garzarella linkedin: http://it.linkedin.com/pub/stefano-garzarella ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
I've posted a diff to -arm about 2 years ago that I used to
cross-build arm picobsd images for a gumstix platform on a i386 host.
I don't know if the diff will apply cleanly anymore but here it is in
anyway.
--- a/release/picobsd/build/Makefile.conf
+++ b/release/picobsd/build/Makefile.conf
@@ -21,7 +21,8 @@ MODULES?=-DNO_MODULES # do not build them as a default
# If config were smart enough, we could place the config
# file in some other place than ${SRC}/sys/i386/conf, but
# at the moment (Oct.2001) this is not possible yet.
-CONF=${SRC}/sys/i386/conf
+#CONF=${SRC}/sys/i386/conf
+CONF=${SRC}/sys/${TARGET_ARCH}/conf
#CONF=${BUILDDIR}/conf # XXX does not work yet
CONFFILE=PICOBSD-${name}
@@ -39,10 +40,19 @@ ${BUILDDIR}/kernel: ${KERNFILE}
${KERNFILE}: ${COMPILE} do_a_make_in_the_kernel_directory_anyways
do_a_make_in_the_kernel_directory_anyways:
+ unset TARGET_CPUTYPE
+ unset TARGET_BIG_ENDIAN
(cd ${COMPILE}; ${BINMAKE} KERNEL=kernel ${MODULES} )
+trampoline:
+ unset TARGET_CPUTYPE
+ unset TARGET_BIG_ENDIAN
+ (cd ${COMPILE}; ${BINMAKE} KERNEL=kernel ${MODULES} trampoline )
+
${COMPILE}: ${CONF}/${CONFFILE}
- (cd ${CONF}; ${CONFIG} -d ${COMPILE} ${CONFFILE}; \
+ unset TARGET_CPUTYPE
+ unset TARGET_BIG_ENDIAN
+ (cd ${CONF}; PATH=${TMPPATH} ${CONFIG} -d ${COMPILE} ${CONFFILE}; \
cd ${COMPILE}; ${BINMAKE} KERNEL=kernel ${MODULES} depend )
${CONF}/${CONFFILE}: PICOBSD
--- /dev/null
+++ b/release/picobsd/build/build.sh
@@ -0,0 +1 @@
+./picobsd --target_arch arm --target_cputype xscale --src
/home/jacques/gumstix -n -v gumstix
diff --git a/release/picobsd/build/picobsd b/release/picobsd/build/picobsd
index a3b3cf5..14235ff 100755
--- a/release/picobsd/build/picobsd
+++ b/release/picobsd/build/picobsd
@@ -21,6 +21,7 @@
# Makefile.conf Makefile used to build the kernel
# config shell variables, sourced here.
# mfs.mtree mtree config file
+#
# floppy.tree/ files which go on the floppy
# mfs_tree/ files which go onto the mfs
#
@@ -28,13 +29,10 @@
# PICOBSDkernel config file
# config shell variables, sourced here.
# crunch.confcrunchgen configuration
-# mfs.mtree overrides ${PICO_TREE}/mfs.mtree
# floppy.tree.excludefiles from floppy.tree/ which we do not need
here.
-# floppy.tree/ local additions to ${PICO_TREE}/mfs_free
+# floppy.tree/ local additions to the floppy.tree
# floppy.tree.${site}/ same as above, site specific.
# mfs_tree/ local additions to the mfs_free
-# buildtree.mk optional makefile to build an extension for floppy tree
-# (generated in buildtree/ )
#
#--- The main entry point is at the end.
@@ -100,7 +98,7 @@ set_defaults() {
EDITOR=${EDITOR:-vi}
fd_size=${fd_size:-1440}
-o_use_loader=yes # use /boot/loader
+o_target_arch=i386
o_all_in_mfs=yes # put all files in mfs so you can boot and run
# the image via diskless boot.
o_clean= # do not clean
@@ -109,7 +107,7 @@ set_defaults() {
o_tarv= # tar verbose flag, or v
o_init_src= # non if we need to init libs and includes.
o_makeopts=${MAKEOPTS:--s} # make options, be silent by default
-o_no_devfs=yes # we do not want devfs
+o_no_devfs= # we do not want devfs
o_do_modules=# do not build modules
SRC=/usr/src # default location for sources
@@ -130,7 +128,6 @@ set_defaults() {
# mountpoint used to build memory filesystems
c_fs=fs.PICOBSD# filename used for the memory filesystem
c_img=picobsd.bin # filename used for the picobsd image
-generate_iso=NO # don't generate the iso image
# select the right memory disk name
case `uname -r` in
@@ -150,7 +147,6 @@ set_defaults() {
trap fail 15
}
-# use the new build infrastructure
create_includes_and_libraries2() {
local no
log create_includes_and_libraries2() for ${SRC}
@@ -163,7 +159,7 @@ create_includes_and_libraries2() {
export MAKEOBJDIRPREFIX
( cd ${SRC};
# make -DNOCLEAN -DNOPROFILE -DNOGAMES -DNOLIBC_R -DPICOBSD buildworld
-make _+_= $no toolchain _includes _libraries
+make _+_= $no toolchain
)
}
@@ -212,7 +208,7 @@ create_includes_and_libraries() {
# set_type type looks in user or system directories for the floppy type
# specified as first argument, and sets variables according to the config.
-# file. Also sets MY_TREE and BUILDDIR and SITE
+# file. Sets THETYPE, SITE, name, MY_TREE and BUILDDIR
set_type() {
local a i
@@ -260,13 +256,6 @@ set_msgs() { # OK
\t3. Site-info: ${SITE}\n\t4. Full-path: ${MY_TREE}\n
}
-# build the iso image
-build_iso_image
Re: cross-arch building picobsd/nanobsd images ?
On 4 January 2012 20:53, Jacques Fourie jacques.fou...@gmail.com wrote:
I've posted a diff to -arm about 2 years ago that I used to
cross-build arm picobsd images for a gumstix platform on a i386 host.
I don't know if the diff will apply cleanly anymore but here it is in
anyway.
Hi,
I've figured out all the right flags to pass to a cross-build
environment. Namely:
env CROSS_BUILD_TESTING=YES
MAKEOBJDIRPREFIX=${X_MAKEOBJDIRPREFIX} \
make ${BUILD_FLAGS} TARGET=${TARGET}
TARGET_ARCH=${TARGET_ARCH} \
${X_TARGET_CPUTYPE} KERNCONF=${KERNCONF}
DESTDIR=${X_DESTDIR} \
KODIR=/boot/kernel.${KERNCONF}/
\
KMODDIR=/boot/kernel.${KERNCONF}/
\
__MAKE_CONF=/dev/null SRCCONF=/dev/null
\
LOCAL_DIRS=${LOCAL_DIRS}
\
LOCAL_TOOL_DIRS=${LOCAL_TOOL_DIRS} $1
\
.. ignore LOCAL_TOOL_DIRS, I haven't committed that yet to -HEAD.
If someone would like to update picobsd to make this work, I'll
happily test out patches and commit it to -HEAD.
Building -8 and previous needed some extra hacks (eg
TARGET_BIG_ENDIAN) which have been removed from -HEAD/-9.
Good luck!
Adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
On Wed, Jan 4, 2012 at 9:50 PM, Adrian Chadd adr...@freebsd.org wrote: On 4 January 2012 20:53, Jacques Fourie jacques.fou...@gmail.com wrote: I've posted a diff to -arm about 2 years ago that I used to cross-build arm picobsd images for a gumstix platform on a i386 host. I don't know if the diff will apply cleanly anymore but here it is in anyway. Hi, I've figured out all the right flags to pass to a cross-build environment. Namely: ... .. ignore LOCAL_TOOL_DIRS, I haven't committed that yet to -HEAD. If someone would like to update picobsd to make this work, I'll happily test out patches and commit it to -HEAD. Building -8 and previous needed some extra hacks (eg TARGET_BIG_ENDIAN) which have been removed from -HEAD/-9. Here's the FreeNAS project/iXsystems' contribution to nanobsd which was contributed back to Warner, but hasn't been reviewed / committed to CURRENT since I missed my pre-Christmas window of opportunity :(. There are some potentially helpful gems that could be added to picobsd (and vice versa I'm sure) -- look for NANO_ARCH for instance; it doesn't resolve the TARGET_BIG_ENDIAN issue noted previously, but that's probably part of the reason why NANO_PMAKE is a separate variable... Thanks! -Garrett nanobsd-omnibus-01.04.2012.patch Description: Binary data ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
On 12/20/11 18:19, Olivier Cochard-Labbé wrote: On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo ri...@iet.unipi.it wrote: On a related topic, does anyone have experience on cross-building nanobsd images ? Hi Luigi, I using little cross-building nanobsd images (i386 on amd64 and vice versa). All my patchs for nanobsd are available on BSD Router Project (http://bsdrp.net) including a patch for compiling ports from nanobsd too. Right now I'm working on adding cross-build mips (RouterStation Pro) nanobsd patch but without the compiling ports feature, because I can only cross-compile word/kernel and I didn't know how to cross-compile ports. I have done some nanobsd related changes (without ports) locally for RS PRO 6 months ago, not sure how it is useful now. But it could be easier to modify. http://people.freebsd.org/~ganbold/nanobsd_rspro.tar.gz Ganbold Regards, Olivier ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo ri...@iet.unipi.it wrote: On a related topic, does anyone have experience on cross-building nanobsd images ? Hi Luigi, I using little cross-building nanobsd images (i386 on amd64 and vice versa). All my patchs for nanobsd are available on BSD Router Project (http://bsdrp.net) including a patch for compiling ports from nanobsd too. Right now I'm working on adding cross-build mips (RouterStation Pro) nanobsd patch but without the compiling ports feature, because I can only cross-compile word/kernel and I didn't know how to cross-compile ports. Regards, Olivier ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
2011/12/20 Olivier Cochard-Labbé oliv...@cochard.me: On Mon, Dec 19, 2011 at 11:45 PM, Luigi Rizzo ri...@iet.unipi.it wrote: On a related topic, does anyone have experience on cross-building nanobsd images ? Hello Mr. Olivier! I using little cross-building nanobsd images (i386 on amd64 and vice versa). All my patchs for nanobsd are available on BSD Router Project (http://bsdrp.net) including a patch for compiling ports from nanobsd too. Yeah, FreeNAS 8.x employs a similar semi-hacky way of doing a full-blown chroot with a clean environment setup [that you might want to steal ;)..[1]] Right now I'm working on adding cross-build mips (RouterStation Pro) nanobsd patch but without the compiling ports feature, because I can only cross-compile word/kernel and I didn't know how to cross-compile ports. Let's work together on this. It's a non-trivial project that I'd like to see come true for FreeNAS to build an ARM platform on x86 hardware (someday..). Also, I'd pick up some of the recent changes we made to nanobsd [2] -- it might help your cause. Cheers, -Garrett 1. http://freenas.svn.sourceforge.net/viewvc/freenas/trunk/nanobsd/common (look for the CR function; follow the history back for credits to the original inspiration). 2. http://freenas.svn.sourceforge.net/viewvc/freenas/trunk/build/nanobsd/ ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: cross-arch building picobsd/nanobsd images ?
Hi, I used to build a few ARM images (on amd64 host) using /usr/src/tools/tools/nanobsd/gateworks/ and regularly i386 images (on amd64 host too) using /usr/src/tools/tools/nanobsd/pcengines/ Bye/2 --- Michael Reifenberger mich...@reifenberger.com http://www.Reifenberger.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
cross-arch building picobsd/nanobsd images ?
Hi, recently I have tried to build picobsd image for a different architecture than the current one, with only partial success. In particular, three weeks ago i committed some changes to the picobsd script so now i can build working amd64 images on amd64. However when i try a cross build (e.g. i386 image on an amd64 host) the kernel stops right after trying to mount the root partition. The error message is the following: ... Timecounter TSC frequency 1858691100 Hz quality 800 Trying to mount root from ufs:/dev/md0 []... panic: mutex Giant owned at .../sys/kern/kern_exit.c:128 cpuid = 0 KDB: enter: panic [ thread pid 1 tid 11 ] Stopped at kdb_enter+0x3b: movl$0,kdb_why db The backtrace indicates the following (i omit the numbers, as i am manually copying the text) kdb_enter panic _mtx_assert exit1 kern_execve sys_execve exec_shell_imgact fork_exit fork_trampoline --- trap 0, eip = 0, esp = 0xc3708d60, ebp = 0 --- any idea on what could be going wrong ? On a related topic, does anyone have experience on cross-building nanobsd images ? thanks luigi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Problem with building PicoBSD with CURRENT tree
It appears that a recent change to src/Makefile.inc1 has broken the
build of PicoBSD when I attempt to build CURRENT on FreeBSD-4.8
host:
*** PICO_OBJ is /home/possum/u0/pavlin/freebsd_src/../usr/obj-pico/picobsd/pim
make: no target to make.
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 147: warning:
make -f /dev/null -m /scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/share/mk
CPUTYPE=i386 -V CPUTYPE returned non-zero status
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 761: warning:
String comparison operator should be either == or !=
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 761: Malformed
conditional ((!defined(NO_RESCUE) || defined(RELEASEDIR)) (${TARGET_ARCH} !=
${MACHINE_ARCH} || ${BOOTSTRAPPING} 501101))
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 761: Missing
dependency operator
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 763: if-less endif
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 763: Need an
operator
make: fatal errors encountered -- cannot continue
The change that breaks the build is in revision 1.388 of Makefile.inc1; see
http://www.freebsd.org/cgi/cvsweb.cgi/src/Makefile.inc1.diff?r1=1.387r2=1.388
The particular command in the release/picobsd/build/picobsd script
that triggers the above problem is:
eval export `cd ${SRC}; make -f Makefile.inc1 -V WMAKEENV`
Reversing back the Makefile.inc1 change by applying the following
simple nit does fix the problem:
--- Makefile.inc1 Tue Sep 2 21:01:02 2003
+++ Makefile.inc1.FIX Tue Sep 2 19:21:49 2003
@@ -758,7 +758,7 @@
.if (!defined(NO_RESCUE) || \
defined(RELEASEDIR)) \
-(${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} 501101)
+(${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} 501101 )
_crunchide=usr.sbin/crunch/crunchide
.endif
I believe that the particular change to Makefile.inc1 was made with
the assumption that we are always going to use the new make version
that comes with FreeBSD-current.
However, even if I use the new make to run the above command, I
still have an error:
[EMAIL PROTECTED]
../usr/obj-pico/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/make.i386/make -f
Makefile.inc1 -V WMAKEENV
../usr/obj-pico/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/make.i386/make: not found
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 147: warning:
../usr/obj-pico/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/make.i386/make -f
/dev/null -m /scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/share/mk CPUTYPE=i386 -V
CPUTYPE returned non-zero status
/scratch/possum/u1/pavlin/FreeBSD/HEAD.cvs/src/Makefile.inc1, line 149: CPUTYPE
global should be set with ?=.
Exit 1
Thanks,
Pavlin
P.S. Running make with -DALWAYS_CHECK_MAKE does not do the trick,
because it has no effect inside Makefile.inc1 :)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
build picobsd bridge fail in locore.s
Can someone help me, I want to build a picobsd floppy. Command: release/picobsd/build/picobsd bridge Error: suffix or operands invalid for 'shr' I think the complain is about the fillkptphys(prot) macro in sys/i386/i386/locore.s I cvsuped current yesterday I havent build picobsd in 5.0 before -- Mauritz Sundell, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd redux
Is there any particular reason for using -current for that? The problem is that -current is in horrible state now (gcc 3.1, KSE-III and so on), so that I'd suggest to use -stable branch or -current sources just before gcc 3.1 import. -Maxim George V. Neville-Neil wrote: Hey Folks, So now I'm working somewhere that we're trying to use Picobsd on the Soekris boards (www.soekris.com). Right now there is a build problem I'm trying to solve. When picobsd goes to build the libraries etc. it chokes on the csu stuff: CC=cc MKDEP_CPP_OPTS=-M -DCRT_BEGIN mkdep -f .depend -a -nostdinc -I/sandb oxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/sandboxes /gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/config -I/sandboxes/gnn/FreeBS D/src/gnu/lib/csu/../../../contrib/gcc -I. -I/sandboxes/gnn/FreeBSD/src/gnu/lib / csu/../../usr.bin/cc/cc_tools /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../ c ontrib/gcc/crtstuff.c cc -nostdinc -I/sandboxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_ FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-o mit-frame-pointer -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc / config -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc -I. -I/san dboxes/gnn/FreeBSD/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN - c -o crtbegin.o /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crt s tuff.c In file included from /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/g c c/crtstuff.c:63: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37 : field `array' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:13 5 : field `augmentation' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:14 3 : field `pc_begin' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: warn ing: `used' attribute directive ignored /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In funct ion `__do_global_dtors_aux': /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: synt ax error before `completed' /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: `com pleted' undeclared (first use in this function) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: (Eac h undeclared identifier is reported only once /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for each function it appears in.) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top l evel: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: warn ing: `used' attribute directive ignored *** Error code 1 Any pointers would be great, I need to get this stuff back up to snuff fast. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current 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 redux
Hi, At 22:55 1/7/02, George V. Neville-Neil wrote: When picobsd goes to build the libraries etc. it chokes on the csu stuff: [etc] First, I'd echo what someone else said about avoiding -current right now. Second, you may have better luck if you buildworld before attempting a picobsd build. -- Bob Bishop +44 (0)118 977 4017 [EMAIL PROTECTED]fax +44 (0)118 989 4254 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: picobsd redux
Is there any particular reason for using -current for that? The problem is that -current is in horrible state now (gcc 3.1, KSE-III and so on), so that I'd suggest to use -stable branch or -current sources just before gcc 3.1 import. Well there are two things going on. My employer wants to use -CURRENT and is willing to let me hack on it, and the other is that I volunteered to do some of the multi-threading/locking work in the network stack. If I can kill these two birds with one stone I can do work for the project while also getting paid. Alas the paid part gets a higher priority :-) When, exactly, was the 3.1 import? Later, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
picobsd redux
Hey Folks, So now I'm working somewhere that we're trying to use Picobsd on the Soekris boards (www.soekris.com). Right now there is a build problem I'm trying to solve. When picobsd goes to build the libraries etc. it chokes on the csu stuff: CC=cc MKDEP_CPP_OPTS=-M -DCRT_BEGIN mkdep -f .depend -a -nostdinc -I/sandb oxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/sandboxes /gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/config -I/sandboxes/gnn/FreeBS D/src/gnu/lib/csu/../../../contrib/gcc -I. -I/sandboxes/gnn/FreeBSD/src/gnu/lib / csu/../../usr.bin/cc/cc_tools /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../ c ontrib/gcc/crtstuff.c cc -nostdinc -I/sandboxes/gnn/FreeBSD/src/../usr/include -DIN_GCC -DHAVE_LD_EH_ FRAME_HDR -finhibit-size-directive -fno-inline-functions -fno-exceptions -fno-o mit-frame-pointer -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc / config -I/sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc -I. -I/san dboxes/gnn/FreeBSD/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN - c -o crtbegin.o /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crt s tuff.c In file included from /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/g c c/crtstuff.c:63: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:37 : field `array' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:13 5 : field `augmentation' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/unwind-dw2-fde.h:14 3 : field `pc_begin' has incomplete type /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:254: warn ing: `used' attribute directive ignored /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: In funct ion `__do_global_dtors_aux': /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:256: synt ax error before `completed' /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: `com pleted' undeclared (first use in this function) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: (Eac h undeclared identifier is reported only once /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:259: for each function it appears in.) /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c: At top l evel: /sandboxes/gnn/FreeBSD/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:298: warn ing: `used' attribute directive ignored *** Error code 1 Any pointers would be great, I need to get this stuff back up to snuff fast. Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan -- George V. Neville-Neil [EMAIL PROTECTED] Neville-Neil Consulting www.neville-neil.com I learn only to be contented. inscription at Ryoan-ji in Kyoto, Japan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
On Mon, Feb 25, 2002 at 04:38:29PM -0800, George V. Neville-Neil wrote:
Hi Folks,
I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I
figure I'll throw this out to the list. On 21 Feb 2002 a change was made to
the
You'll have to pay some money if you need a 24-hour responsiveness. :-)
bsd.lib.mk and bsd.prog.mk which is commented, in part, as:
Get rid of the (now unneeded) -I${DESTDIR}/usr/include magic in bsd.prog.mk
and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we
no longer have users of it.
This change was made by ru. Alas this breaks the picobsd build since the
statically built libraries need some way to know to get their includes from the
directory you're building in. This does not affect a general 5.0 build (I checked
that this morning) but is still very problematic. I'm only just starting with the
picobsd stuff and I would love to fix this bug in the right place if only someone
could tell me what this change meant and how pervasive it was.
Putting in an extra CFLAG for -I${SRC}usr/include works for some libraries but
breaks libbind as alluded to by this comment in the same checkin:
(Attempt to move the -nostdinc -I... part of CFLAGS into the new CINCLUDES
(modeled after a similar CXXINCLUDES) eventually failed because hard-coding
${WORLDTMP}/usr/include to be the first in the include list does not always
work, e.g. lib/libbind.)
So, can someone help me out here?
What src/release PicoBSD script should I try to run to reproduce this?
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
You'll have to pay some money if you need a 24-hour responsiveness. :-) The check is in the mail ;-) What src/release PicoBSD script should I try to run to reproduce this? -CURRENT as of Monday. Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. If you can give me a bit of info (or a place to look) I can help address this problem. I'm going to try to work with Luigi on maintaining picobsd as this will be my main development system. It's a very good way for embedded systems hacks (like myself) to work. Very natural. And it's nice that I don't have to worry about having -CURRENT on my development machine. Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
On Wed, Feb 27, 2002 at 09:49:28AM -0800, George V. Neville-Neil wrote: You'll have to pay some money if you need a 24-hour responsiveness. :-) The check is in the mail ;-) What src/release PicoBSD script should I try to run to reproduce this? -CURRENT as of Monday. Things work fine in a checkout from 20 Feb 2002 and that's what I'm working with. If you can give me a bit of info (or a place to look) I can help address this problem. I'm going to try to work with Luigi on maintaining picobsd as this will be my main development system. It's a very good way for embedded systems hacks (like myself) to work. Very natural. And it's nice that I don't have to worry about having -CURRENT on my development machine. This still doesn't answer my question -- how can I reproduce the problem? cd /foo/bar make grrr Something like that... Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Latest versions of bsd.lib.mk break picobsd...
This still doesn't answer my question -- how can I reproduce the problem? cd /foo/bar make grrr Something like that... Whoops, sorry. To reproduce this do: cd /usr/src ./release/picobsd/build/picobsd --src /usr/src --init yes, I know that --src is unnecessary but I always use it since I'm often using a tree that's NOT at /usr/src so I include it here. The --init will break with: mkdep -f .depend -a -nostdinc -DSTANDARD_INCLUDE_DIR=/home/gnn/FreeBSD/src.latest../usr/include -I/home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:32: stddef.h: No such file or directory /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:33: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/crt1.c:34: /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. *** Error code 1 Stop in /home/gnn/FreeBSD/src.latest. --- fail: Error 1 error code libraries in Error: failed while making libraries --- Aborting ./release/picobsd/build/picobsd Later, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Latest versions of bsd.lib.mk break picobsd...
Hi Folks,
I've tried contacting [EMAIL PROTECTED] directly but haven't seen anything so I
figure I'll throw this out to the list. On 21 Feb 2002 a change was made to
the
bsd.lib.mk and bsd.prog.mk which is commented, in part, as:
Get rid of the (now unneeded) -I${DESTDIR}/usr/include magic in bsd.prog.mk
and bsd.lib.mk. Finish the removal of LDDESTDIR in bsd.lib.mk,v 1.55 -- we
no longer have users of it.
This change was made by ru. Alas this breaks the picobsd build since the
statically built libraries need some way to know to get their includes from the
directory you're building in. This does not affect a general 5.0 build (I checked
that this morning) but is still very problematic. I'm only just starting with the
picobsd stuff and I would love to fix this bug in the right place if only someone
could tell me what this change meant and how pervasive it was.
Putting in an extra CFLAG for -I${SRC}usr/include works for some libraries but
breaks libbind as alluded to by this comment in the same checkin:
(Attempt to move the -nostdinc -I... part of CFLAGS into the new CINCLUDES
(modeled after a similar CXXINCLUDES) eventually failed because hard-coding
${WORLDTMP}/usr/include to be the first in the include list does not always
work, e.g. lib/libbind.)
So, can someone help me out here?
Thanks,
George
--
George V. Neville-Neil [EMAIL PROTECTED]
NIC:GN82
Those who would trade liberty for temporary security deserve neither
- Benjamin Franklin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Problems with picobsd...
Hi Folks, I'm now mirroring the CVS repository locally (with cvsup) and then checking out the head of the tree with cvs co src to get at -CURRENT. I'm trying to work with picobsd but I get the following on the latest (24 Feb 2002, 22:25 Pacific Time) stuff when I just try to --init the system: cd /home/gnn/FreeBSD/src/lib/csu/i386-elf; make depend; make all; make install cc -nostdinc -elf -Wall -fkeep-inline-functions -I/home/gnn/FreeBSD/src/lib/c su/i386-elf/../common -c /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c -o crt1.o /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:32: stddef.h: No such file or directory /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:33: stdlib.h: No such file or directory In file included from /home/gnn/FreeBSD/src/lib/csu/i386-elf/crt1.c:34: /home/gnn/FreeBSD/src/lib/csu/i386-elf/../common/crtbrand.c:28: sys/param.h: No such file or directory *** Error code 1 Stop in /home/gnn/FreeBSD/src/lib/csu/i386-elf. *** Error code 1 Stop in /home/gnn/FreeBSD/src. *** Error code 1 Stop in /home/gnn/FreeBSD/src. --- fail: Error 1 error code libraries in Error: failed while making libraries --- Aborting ./release/picobsd/build/picobsd This comes from the command: ./release/picobsd/build/picobsd --src /home/gnn/FreeBSD/src --init Clues? Thanks, George -- George V. Neville-Neil [EMAIL PROTECTED] NIC:GN82 Those who would trade liberty for temporary security deserve neither - Benjamin Franklin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/release/picobsd/mfs_tree/etc termcap
On Thu, 1 Nov 2001, Luigi Rizzo wrote: luigi 2001/11/01 08:52:35 PST Modified files: release/picobsd/mfs_tree/etc termcap Log: Add entries for dumb and dialup terminals, as the shell in HEAD refuses to start if it does not find a matching entry for the terminal type. My impression is that this is a problem in the shell, because at least on PicoBSD images, the shell itself coredumps. Anyways, this is the quickest fix i can come up with. This is probably caused by the not so recent breakage of libedit. I now understand why I didn't see as many problems as des for single-user shells: I have /etc/malloc.conf - aj, and this prevents detection of the breakage. With the default malloc options, set -E in /bin/sh always dumps core if $TERM doesn't exist. $TERM never exists for single-user-shells if /usr is a separate filesystem. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
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
picobsd and mdconfig
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.
Index: picobsd
===
RCS file: /home/ncvs/src/release/picobsd/build/picobsd,v
retrieving revision 1.7
diff -r1.7 picobsd
3c3
# $FreeBSD: src/release/picobsd/build/picobsd,v 1.7 2001/06/21 08:49:46 luigi Exp $
---
# $FreeBSD$
80,85d79
NO_DEVFS=yes # DEVFS is currently broken. Always set this.
# Find a suitable vnode
VNUM=`mount | awk /vn/ { num++ } END { printf \%d\, num }`
log --- Using vn${VNUM}...
161d154
echo - vnode is $VNUM
329c322
dd if=${BUILDDIR}/picobsd.bin of=/dev/rfd0.${FLOPPY_SIZE}
---
dd if=${BUILDDIR}/picobsd.bin of=/dev/fd0
427c420
gzip -9 etc/*
---
for f in `find etc/ -type 'f'` ; do gzip -9 $f ; done
436,437d428
free_vnode
448c439
disklabel -rw vn${VNUM} fd${MFS_SIZE} || fail $? mfs_disklabel
---
disklabel -rw md${VNUM} fd${MFS_SIZE} || fail $? mfs_disklabel
450c441
disklabel -rw vn${VNUM} auto || fail $? mfs_disklabel
---
disklabel -rw md${VNUM} auto || fail $? mfs_disklabel
452,454c443,445
newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn${VNUM}c /dev/null
mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT} || fail $? no_mount
log `df /dev/vn${VNUM}c`
---
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`
528c519
cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd
---
cp -Rp ${BUILDDIR}/floppy.tree/* ${MFS_MOUNTPOINT}/fd || fail $? ftree_copy
533,534c524,525
fsck -p /dev/rvn${VNUM}c
vnconfig -u vn${VNUM}
---
fsck -p /dev/md${VNUM}c
vnconfig -u md${VNUM}
540,541c531,532
umount /dev/vn${VNUM} 2 /dev/null || true
vnconfig -u vn${VNUM} 2 /dev/null || true
---
umount /dev/md${VNUM} 2 /dev/null || true
mdconfig -d -u ${VNUM} 2 /dev/null || true
557,559c548,550
no_vnconfig)
echo Error while doing vnconfig of ${imgname} on /dev/rvn${VNUM}...
echoMost probably your running kernel doesn't have the vn(4) device.
---
no_mdconfig)
echo Error while doing mdconfig of ${imgname} on /dev/md${VNUM}...
echoMost probably your running kernel doesn't have the md(4) device.
562c553
echo Error while labeling ${MFS_NAME} size ${MFS_SIZE}
---
echo Error while labeling ${MFS_NAME} size ${MFS_SIZE}.
565c556
echo Error while mounting ${MFS_NAME} (/dev/vn${VNUM}c) on ${MFS_MOUNTPOINT}
---
echo Error while mounting ${MFS_NAME} (/dev/md${VNUM}c) on ${MFS_MOUNTPOINT}.
568c559
echo Error while making hierarchy in ${MFS_MOUNTPOINT}
---
echo Error while making hierarchy in ${MFS_MOUNTPOINT}.
574c565
echo Error while doing disklabel on of floppy.img size $FLOPPY_SIZE
---
echo Error while doing disklabel on of floppy.img size $FLOPPY_SIZE.
577c568,576
echo Error: you must build PICOBSD${suffix} kernel first
---
echo Error: you must build PICOBSD${suffix} kernel first.
;;
ftree_copy)
echo Error while copying floppy tree to ${MFS_MOUNTPOINT}.
echoPerhaps ${MFS_MOUNTPOINT} is out of space.
;;
kernel_copy)
echo Error while copying PICOBSD${suffix}/kernel to ${MFS_MOUNTPOINT}.
echoPerhaps ${MFS_MOUNTPOINT} is out of space.
594c593
# Create a zero-filled disk image with a boot sector, and vnconfig it.
---
# Create a zero-filled disk image with a boot sector, and mdconfig it.
602c601,602
vnconfig -c -s labels vn${VNUM} ${imgname} || fail $? no_vnconfig
---
VNODE=`mdconfig -a -t vnode -s ${imgsize}k -f ${imgname}` || fail $? no_mdconfig
VNUM=`echo ${VNODE} | sed 's/^md//'`
622c622
disklabel -Brw -b ${boot1} -s ${b2} vn${VNUM} fd${FLOPPY_SIZE} || \
---
disklabel -Brw -b ${boot1} -s ${b2} md${VNUM} fd${FLOPPY_SIZE} || \
625c625
newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/vn${VNUM}c /dev/null
---
newfs -i ${FLOPPY_INODES} -m 0 -p 0 -o space /dev/md${VNUM}c /dev/null
627c627
mount /dev/vn${VNUM}c ${MFS_MOUNTPOINT}
---
mount /dev/md${VNUM}c ${MFS_MOUNTPOINT}
636c636,639
cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel
---
du -k kernel.gz
df -k ${MFS_MOUNTPOINT}
cp -p kernel.gz ${MFS_MOUNTPOINT}/kernel || fail $? kernel_copy
714a718,723
# Ugh.
if [ ! $CONFIG ]; then
CONFIG=config
fi
717,719c726,730
THETYPE=$1
SITE=$2
set_type $THETYPE
---
# First, check if arguments where passed to us before parsing.
if [ $2 ]; then
THETYPE=$1
SITE=$2
set_type $THETYPE
721c732
# If $1=package, it creates a neat set of floppies
---
# If $1
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
cross-building PicoBSD - need advice...
Hi,
I suspect it is more likely that i get feedback from people on -current,
which is why this email is addressed there. I am Bcc-ing to -small in
case the people there are interested too.
Basically, i would like to come up with some easy way to cross-build
picobsd images, embedding the relevant commands into the picobsd
build script so one only has to specify the SRC tree location and the
script does all things for you.
There are a number of dependencies that need to be addressed in
this process, including at least the following.
1. the config program.
I more or less know how to handle this, basically compile
whatever config is in ${SRC}/usr.sbin/config and use that
one for the config step.
2. location of standard include files.
Here, it looks not too complex -- at the moment i
basically do the following:
cd ${SRC}
mkdir -p usr/include
DESTDIR=`pwd` make includes
CFLAGS=-nostdinc -I`pwd`/usr/includes ; export CFLAGS
and hope that the various makefiles honor CFLAGS settings.
It seems to work for most things.
3. libraries
This is the hard part for me. I guess there is some way
from the makefiles in ${SRC}/lib to build just the static
libraries and put them in some place where I can use them
without conflict with the standard ones, but how ?
So, could anyone suggest a good way to address step #3 ?
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
PICOBSD stale?
The ready-made PICOBSD-diskimages all seems to be based on FreeBSD 3.x I also doesn't seem to be able to make picobsd from current sources, althugh I didn't try that hard. Is picobsd stale? Leif To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
PicoBSD
Ok, parts of PicoBSD are finally working again. I've managed to get dial, isp, and net working again. The only ones left to check out are bridge and install, I'm not sure about router, does that still exist or was that replaced by bridge? Bridge is too big to fit on a floppy so I'm working on slimming that down a little. -- +-+ | Omachonu Ogali [EMAIL PROTECTED] | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PicoBSD
The following patch is for -CURRENT. It at least gets past that dumb
floppy loop. The problem I'm having is that after the scripts, nothing
else is done, it just sits there with "Welcome to PicoBSD". Any ideas?
To Luigi: I made the changes you asked for, disregard that patchfile as
I've incorporated those changes in here.
-- snip --
--- /usr/src/release/picobsd/build/Makefile.crunch Tue Feb 8 03:27:55 2000
+++ /usr/src/release/picobsd/build/Makefile.crunch Thu Mar 30 14:28:20 2000
@@ -4,3 +4,3 @@
SRC?=/usr/src
-CRUNCHFLAGS+= -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT
+CRUNCHFLAGS+= -DNOPAM -DRELEASE_CRUNCH -DNOSECURE -DNOCRYPT -DNONETGRAPH -DNOIPSEC
@@ -31,12 +31,12 @@
install:
- cp crunch1 /mnt/stand/crunch
- chmod 555 /mnt/stand/crunch
+ cp crunch1 ${MFS_MOUNTPOINT}/stand/crunch
+ chmod 555 ${MFS_MOUNTPOINT}/stand/crunch
for i in `crunchgen -l crunch1.conf` ; \
do \
- ln /mnt/stand/crunch /mnt/stand/$${i}; \
+ ln ${MFS_MOUNTPOINT}/stand/crunch ${MFS_MOUNTPOINT}/stand/$${i}; \
done
- rm /mnt/stand/crunch
+ rm ${MFS_MOUNTPOINT}/stand/crunch
# Install the MIB files
- #mkdir -p /mnt/usr/local/share/snmp/mibs
- #cp ../../net/crunch1/mibs/*.txt /mnt/usr/local/share/snmp/mibs/
+ #mkdir -p ${MFS_MOUNTPOINT}/usr/local/share/snmp/mibs
+ #cp ../../net/crunch1/mibs/*.txt ${MFS_MOUNTPOINT}/usr/local/share/snmp/mibs/
--- /usr/src/release/picobsd/build/buildTue Feb 8 03:24:59 2000
+++ /usr/src/release/picobsd/build/buildThu Mar 30 14:33:40 2000
@@ -75,3 +75,3 @@
-# Main build procedure. It calls another scripts (stage1)
+# Main build procedure. It calls another script (stage1)
main() {
@@ -103,4 +103,5 @@
echo -n "- Cleaning temporary files... "
- umount -f /mnt
- vnconfig -u /dev/rvn0
+ umount -f ${MFS_MOUNTPOINT}
+ rm -rf ${MFS_MOUNTPOINT}
+ vnconfig -u /dev/rvn${VNUM}
./clean ${TYPE}
--- /usr/src/release/picobsd/build/crunch.inc Tue Feb 8 03:29:18 2000
+++ /usr/src/release/picobsd/build/crunch.inc Thu Mar 30 12:04:03 2000
@@ -6 +6,2 @@
NONETGRAPH=yes
+NOIPSEC=yes
--- /usr/src/release/picobsd/build/mfs.mtreeTue Feb 8 06:39:28 2000
+++ /usr/src/release/picobsd/build/mfs.mtreeThu Mar 30 12:04:04 2000
@@ -49,2 +49,8 @@
..
+locale
+..
+syscons
+..
+nls
+..
..
--- /usr/src/release/picobsd/build/stage1 Tue Feb 8 03:25:00 2000
+++ /usr/src/release/picobsd/build/stage1 Thu Mar 30 14:03:27 2000
@@ -10,4 +10,8 @@
+# By default, /tmp should exist.
+#
MFS_NAME=fs.PICOBSD
-MFS_MOUNTPOINT=/mnt
+MFS_MOUNTPOINT=`mktemp -d "/tmp/picobsd.XX"`
+export MFS_MOUNTPOINT
+
# fail errno errcode
@@ -21,3 +25,3 @@
no_vnconfig)
- echo "Error while doing vnconfig of ${MFS_NAME} on /dev/rvn0..."
+ echo "Error while doing vnconfig of ${MFS_NAME} on /dev/rvn${VNUM}..."
echo " Most probably your running kernel doesn't have the vn(4) device."
@@ -28,3 +32,3 @@
no_mount)
- echo "Error while mounting ${MFS_NAME} (/dev/vn0c) on ${MFS_MOUNTPOINT}"
+ echo "Error while mounting ${MFS_NAME} (/dev/vn${VNUM}c) on ${MFS_MOUNTPOINT}"
;;
@@ -40,3 +44,3 @@
vnconfig2)
- echo "Error while doing vnconfig of floppy.img on /dev/rvn0..."
+ echo "Error while doing vnconfig of floppy.img on /dev/rvn${VNUM}..."
;;
@@ -56,2 +60,4 @@
echo "- Aborting $0"
+umount ${MFS_MOUNTPOINT} 2 /dev/null || true
+rm -rf ${MFS_MOUNTPOINT} 2 /dev/null || true
exit 10
@@ -63,5 +69,9 @@
echo "- Preparing MFS filesystem..."
-umount /dev/vn0 2 /dev/null || true
+VNUM=`mount | awk "/vn/ { num++ } END { printf \"%d\", num }"`
+export VNUM
+echo "- Using vn${VNUM}..."
+
+umount /dev/vn${VNUM} 2 /dev/null || true
umount ${MFS_MOUNTPOINT} 2 /dev/null || true
-vnconfig -u /dev/rvn0 2 /dev/null || true
+vnconfig -u /dev/rvn${VNUM} 2 /dev/null || true
@@ -72,3 +82,3 @@
-vnconfig -s labels -c /dev/rvn0 ${MFS_NAME} 2/dev/null || \
+vnconfig -s labels -c /dev/rvn${VNUM} ${MFS_NAME} 2/dev/null || \
fail $? no_vnconfig
@@ -80,9 +90,9 @@
if [ ${MFS_SIZE} -lt 1024 ] ; then
- disklabel -rw /dev/rvn0 fd${MFS_SIZE} || fail $? disklabel
+ disklabel -rw /dev/rvn${VNUM} fd${MFS_SIZE} || fail $? disklabel
else
- disklabel -rw vn0 auto || fail $? disklabel
+ disklabel -rw vn${VNUM} auto || fail $? disklabel
fi
-newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn0c
-mount /dev/vn0c ${MFS_MOUNTPOINT} || fail $? no_mount
+newfs -i ${MFS_INODES} -m 0 -p 0 -o space /dev/rvn${VNUM}c
+mount /
df output ? (picobsd related)
Hi,
on 3.4R, when booting, a
df /
would return the name of the boot device, something like
fd0a
wd0a...
and the like. On a recent -current snap, this returns
ufs:fd0a
I used the previous behaviour in picobsd's rc to mount
the file system from the boot device,
set `df /` ; dev="/dev/$8"
echo "Reading /etc from ${dev}..."
mount -o rdonly ${dev} /mnt
unfortunately the "ufs:" prefix breaks the above code.
Any suggestion on how to proceed ? I could of course put some extra
entries on fstab so that i can write
set `df /` ; filesystem="/$8"
mount -o rdonly ${filesystem}
but this requires having entries on the filesystem etc. etc.
Any simple shell trick to parse/remove the ufs: prefix ?
Note, i cannot use tr, basename or other progs, they are just not there!
cheers
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: df output ? (picobsd related)
ufs:fd0a set `df /` ; dev="/dev/$8" How about something like IFS=': '; set `df /`; IFS=' ' dev="/dev/$9" -- Richard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: df output ? (picobsd related)
On Mon, 7 Feb 2000, Luigi Rizzo wrote: on 3.4R, when booting, a df / would return the name of the boot device, something like fd0a wd0a... and the like. On a recent -current snap, this returns ufs:fd0a This may be caused by using a not very recent -current snap. I think I fixed this bug ion 1999/11/28. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: df output ? (picobsd related)
On Mon, Feb 07, 2000 at 01:04:27PM +0100, Luigi Rizzo wrote:
and the like. On a recent -current snap, this returns
ufs:fd0a
I used the previous behaviour in picobsd's rc to mount
the file system from the boot device,
set `df /` ; dev="/dev/$8"
echo "Reading /etc from ${dev}..."
mount -o rdonly ${dev} /mnt
unfortunately the "ufs:" prefix breaks the above code.
Any simple shell trick to parse/remove the ufs: prefix ?
Note, i cannot use tr, basename or other progs, they are just not there!
How about dev="/dev/${8#*:}" ?
--
Andrew
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Building PicoBSD
I'm trying to build a `net' PicoBSD on a -current system and am
running into problems that appear to be inside make(1) (and how it
imports/exports/treats MAKEFLAGS).
I thought I'd try to shrink things by stripping the ISDN and RADIUS
support out of ppp (amongst other things), but ppp/i4b.c kept getting
included in the crunch1.cache and crunch1.mk. I eventually wound up
with the patches below which:
1) Within crunchgen(8), explicitly pass the environment MAKEFLAGS to
the subordinate make as a commandline option.
2) Add various options to net/crunch1/Makefile's MAKEFLAGS to disable
unwanted bits and pieces.
3) Explicitly pass MAKEFLAGS to both crunchgen and the `build it all`
make.
4) Remote ipfw and -lradius from the crunch.conf file.
5) Fix the password diffs to suit a -current system. (Note that there
is a generic problem with including the $FreeBSD$ tag in the diffs).
The result of all this is that ppp/i4b.o _has_ been left out (suggesting
that the -DNOI4B in MAKEFLAGS is being seen), but ppp/nat_cmd.o and
ppp/chap_ms.o are still being included (suggesting that the -DNONAT,
-DNOALIAS, -DRELEASE_CRUNCH and -DNOCRYPT _aren't_ being seen).
Does anyone have any ideas? I _hope_ I'm doing soething silly...
Index: src/usr.sbin/crunch/crunchgen/crunchgen.c
===
RCS file: /home/CVSROOT/./src/usr.sbin/crunch/crunchgen/crunchgen.c,v
retrieving revision 1.11
diff -u -r1.11 crunchgen.c
--- crunchgen.c 1998/09/14 11:33:38 1.11
+++ crunchgen.c 1999/09/15 05:41:23
@@ -544,7 +544,7 @@
fprintf(f, "crunchgen_objs:\n\t@echo 'OBJS= '${OBJS}\n");
fclose(f);
-sprintf(line, "make -f %s crunchgen_objs 21", tempfname);
+sprintf(line, "make 'MAKEFLAGS=$MAKEFLAGS' -f %s crunchgen_objs 21", tempfname);
if((f = popen(line, "r")) == NULL) {
warn("submake pipe");
goterror = 1;
Index: src/release/picobsd/net/crunch1/Makefile
===
RCS file: /home/CVSROOT/./src/release/picobsd/net/crunch1/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- Makefile1999/08/28 01:33:39 1.5
+++ Makefile1999/09/15 05:47:50
@@ -3,6 +3,8 @@
#
SRC?=/usr/src
+MAKEFLAGS+=-DNOPAM -DNOSECURE -DNOCRYPT -DRELEASE_CRUNCH -DNOI4B -DNORADIUS -DNONAT
+
all: crunch
crunch:
@@ -11,8 +13,8 @@
touch /usr/src/usr.bin/passwd/.picobsd.patched; \
fi
@cat crunch.conf|sed -e "s@/usr/src@${SRC}@" crunch1.conf
- @crunchgen ./crunch1.conf
- @${MAKE} -f crunch1.mk -DNOPAM all \
+ @MAKEFLAGS="${MAKEFLAGS}" crunchgen ./crunch1.conf
+ @${MAKE} ${MAKEFLAGS} -f crunch1.mk -DNOPAM all \
"CFLAGS=${CFLAGS} -DRELEASE_CRUNCH -DCRUNCHED_BINARY -DNOSECURE -DNOCRYPT"
#21 /dev/null
clean:
Index: src/release/picobsd/net/crunch1/crunch.conf
=======
RCS file: /home/CVSROOT/./src/release/picobsd/net/crunch1/crunch.conf,v
retrieving revision 1.9
diff -u -r1.9 crunch.conf
--- crunch.conf 1999/08/28 01:33:39 1.9
+++ crunch.conf 1999/09/15 05:52:33
@@ -25,7 +25,8 @@
progs pwd ppp telnet more
progs passwd date
-progs mount_cd9660 mount_nfs ping traceroute routed ipfw
+progs mount_cd9660 mount_nfs ping traceroute routed
+# ipfw
ln mount_cd9660 cd9660
ln mount_nfs nfs
@@ -42,4 +43,4 @@
libs -lncurses -lmytinfo -lipx -lz -lpcap -lalias -lwrap
libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm
libs -lgnuregex -ltelnet
-libs -lradius # used by ppp
+# libs -lradius # used by ppp
Index: src/release/picobsd/net/crunch1/passwd.diff
=======
RCS file: /home/CVSROOT/./src/release/picobsd/net/crunch1/passwd.diff,v
retrieving revision 1.5
diff -u -r1.5 passwd.diff
--- passwd.diff 1999/08/28 01:33:39 1.5
+++ passwd.diff 1999/09/13 03:08:52
@@ -2,14 +2,14 @@
--- Makefile Sat Aug 1 20:40:38 1998
***
*** 2,24
- # $FreeBSD: ./src/release/picobsd/net/crunch1/passwd.diff,v 1.5 1999/08/28 01:33:39
peter Exp $
+ # $FreeBSD: ./src/usr.bin/passwd/Makefile,v 1.34 1999/09/06 17:30:02 peter Exp $
PROG=passwd
! SRCS=local_passwd.c passwd.c pw_copy.c pw_util.c pw_yp.c \
! yp_passwd.c ypxfr_misc.c ${GENSRCS}
GENSRCS=yp.h yp_clnt.c yppasswd.h yppasswd_clnt.c \
yppasswd_private.h yppasswd_private_clnt.c yppasswd_private_xdr.c
- CFLAGS+=-Wall -DPASSWD_IGNORE_COMMENTS
+ CFLAGS+=-Wall
! DPADD= ${LIBCRYPT} ${LIBRPCSVC} ${LIBUTIL}
! LDADD= -lcrypt -lrpcsvc -lutil
@@ -26,14 +26,14 @@
CLEANFILES= ${GENSRCS}
--- 2,21
- # $FreeBSD: ./src/release/picobsd/net/crunch1/passwd.diff,v 1.5 1999/08/28 01:33:39
peter Exp $
+ # $FreeBSD: ./src/usr.bin/passwd/Makefile,v 1.34 1999/09/06 17:30:02 peter Exp $
PROG=passwd
! SRCS=local
PicoBSD major update
Hello, I'm committing an update of the PicoBSD code tree that should allow it to build on -STABLE and take advantage of loader's new features. Luigi Rizzo did the majority of the work, I debugged. I have use of this code thus why I'm sponsoring this commit. Significant changes include: . Now builds on -STABLE (-CURRENT is broken due to bugs) . etc directory contents centrilized in /floppy.tree instead of each type directory (can exclude override as desired) . Removed extraneous language files (lang files for rc really necessary?) . dialog-based build tool . MFS image loads as a mfs_root module instead of compiled into kernel A MFC is pending. Please send commit-related complaints to me, and other queries either to the list or both of us. Luigi is heading for the US later this week and may be out of email range. Thanks! Doug White Internet: [EMAIL PROTECTED]| FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite| www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCCARD today works but sysinstall and PicoBSD broken. (was PCCARD driver still sucks)
Thank to all for replies. It seems that today current finaly have fixed (pccard works without patches). Hovewer, sysinstall (and PicoBSD) broken with following symptoms: cc -O2 -march=pentium -mpentium -pipe -Wall -I/usr/src/release/sysinstall/../../ gnu/lib/libdialog -I/usr/src/release/sysinstall -I/usr/src/release/sysinstall/.. /../sys -DUC_PRIVATE -DKERN_NO_SYMBOLS?? -c kget.c In file included from kget.c:31: /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: parse error befo re `ointhand2_t' /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: warning: no semi colon at end of struct or union /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:66: warning: no semi colon at end of struct or union /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:67: warning: type de faults to `int' in declaration of `id_iu' /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:67: warning: data de finition has no type or storage class /usr/src/release/sysinstall/../../sys/i386/isa/isa_device.h:80: parse error befo re `}' kget.c: In function `kget': kget.c:69: sizeof applied to an incomplete type kget.c:71: dereferencing pointer to incomplete type kget.c:72: dereferencing pointer to incomplete type kget.c:74: dereferencing pointer to incomplete type kget.c:75: dereferencing pointer to incomplete type kget.c:77: dereferencing pointer to incomplete type etc. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
