Re: NFS client mount options in CURRENT/5.1-
Antoine Jacoutot wrote: Scott W wrote: mount -tnfs -orw,rsize=8196,wsize=8196,bg,hard,intr,async sol:/export /mnt nfs: -o rsize=: option not supported Try -r 8196 -w 8196 and have a look at man mount_nfs. Antoine Definite user error on my part, thanks. I couldn't find anything on hard vs soft mounts however- I'm assuming the default is hard, as there is only a soft (-s) option available on freeBSD? Thanks again, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS client mount options in CURRENT/5.1-
Hey all- Perusal of the man page for mount_nfs doesn't seem to shed any light here, so can someone tell me what is wrong with this mount command (namely half of the options)? mount -tnfs -orw,rsize=8196,wsize=8196,bg,hard,intr,async sol:/export /mnt nfs: -o rsize=: option not supported Likewise for wsize and hard, although documented in mount_nfs and traditionally available NFS options...any ideas? It will mount via removing the 'offending' options properly.. I don't need help on 'why are you doing this command line' etc- am just doing some throughput tests, but could use a sanity check on whats wrong with these options...? TIA, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: newfs by fstab directory name?
Wes Peters wrote:
On Tuesday 28 October 2003 12:05, David O'Brien wrote:
On Mon, Oct 27, 2003 at 01:26:23PM -0800, Wes Peters wrote:
At work we do a lot of dynamic filesystem creation, so we added the
ability to specify the 'special file' argument to newfs via the
fstab mount point directory. Please see the attached patch. If
nobody objects, I'll commit this in a couple of days.
Not objecting, but I don't follow how the change is to be used.
Can you post an example?
Sure. Example from /etc/fstab:
/dev/ad0s1d/tmpufs rw 2 2
/dev/ad0s1f/usrufs rw 2 2
/dev/ad0s1e/varufs rw 2 2
/dev/acd0 /cdrom cd9660 ro,noauto 0 0
/dev/da0s1e/spool ufs rw,noauto 0 0
The disk space on /spool is managed by the application and isn't
guaranteed to be on-line or even existent when the system portion
loads and starts the application. This space is entirely transient
data that doesn't need to be saved across reboots. When the
application starts, it checks to see if /spool is clean; if so it
just mounts it, if not it newfs's it and then mounts it. This
space isn't necessarily always da0s1e but it is always /spool
across different hardware platforms. We prefer to:
newfs /spool
rather than
. {some file full of shell variables describing the hardware}
newfs $SPOOL_PARTITION
because the former is slightly more concise. We had a local patch to do
this in our 4.x code base, but it seemed a general enough change that
others might find it useful as well. I recall ecountering this same
problem at DoBox so it appears to be a general problem for disk-based
appliances, at least if you want to support differing hardware.
This would also be useful for anyone doing any sort of benchmarking
using data sets- I did a code port of LADDIS/SFS to Linux ages ago to do
some NFS/SMB fileserver testing, and I can say, quite a LOT of entirely
temporary data is generated...
Scott
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1-CURRENT in wall- SOLVED
Dag-Erling Smørgrav wrote: M. Warner Losh [EMAIL PROTECTED] writes: find /usr/obj -name .depend or better yet rm -rf /usr/obj/* *ahem* the correct incantation is: # cd /usr/src # make cleandir # make cleandir DES Removing the /usr/obj/* tree worked, back in business. Will have to take a closer look at the 'master' Makefile, as I didn't see the cleandir target at first glance, so had been using 'make clean make buildworld' for previous builds- I take it this is NOT needed as the build process does a 'make clean' prior to building? Thanks to all... Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Question on freeBSD (5.1-CURRENT) portupgrade of Perl 5.8 andlibiconv 1.9.1_3
Hey all. In doing a portupgrade -RvN for windowmaker, Perl and libiconv were recompiled. I saved the log output and noticed several oddities I was wondering if anyone can explain? 1..several settings come up as undefined during the Perl build, namely: $i_malloc $d_setegid $d_seteuid $i_iconv These don't look troubling by themselves dur to 'autoconf magic,' but the next one for libiconv is more bothersome: From libiconv 1.9.1_3 configure: checking if libtool supports shared libraries... yes *** Warning: the command libtool uses to detect shared libraries, *** /usr/bin/file, produces output that libtool cannot recognize. *** The result is that libtool may fail to recognize shared libraries *** as such. This will affect the creation of libtool libraries that *** depend on shared libraries, but programs linked with such libtool *** libraries will work regardless of this problem. Nevertheless, you *** may want to report the problem to your system manager and/or to *** [EMAIL PROTECTED] Any ideas? Also, is there a way to pass configure options to portupgrade, or should I run make clean ./configure for each port in an 'upgrade chain' and then force portupgrade to not make clean prior to building/installing? Thanks, Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Buildworld fails in 5.1-CURRENT in wall
M. Warner Losh wrote: I'd remove all the .depend files and try again. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] I've tried that one- I'm not familiar with freeBSD's build environment, but 'find /usr/src -name .depend shows the only .depend files are in the kernel tree /usr/src/sus/i386/compile/ , so I'm assuming it's generating them as part of the build process itself, or dumping them outside of the /usr/src heirarchy. Tried again from cvsup ~11pm with same results...any other ideas? Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Help- re-install of 5.1 release leaves bootloader unworkable
Hey all- hopefully someone can point me in the right direction here. After problems with cvsuped 5.1 current, I did a re-install of 5.1 RELEASE on a system with two IDE drives. The install appears to go well, but on reboot, I'm faced with what appears to be 3(!!) options for booting BSD, none of which work. The system is a dual celeron 366MHz with 768M RAM. HPT66 IDE controller which has 2 IDE drives plugged into it. These show up as ad4 and ad5 during the install. The boot menu shows as: F1 freebsd F2 freebsd F3 Disk 1 none of which work. If I type: unload boot 3(ad1,d) I get an error 1 lba 0 Other selections result in: no /boot/loader I have been able to load the fixit disk, and mount the correct partitions, but the only references I've seen to any help with respect to re-installing the boot loader are 'installbootloader' which doesn't appear to be on this install. So...how do I recover this install and remove the 'bad' entries in the loader, and point it at the correct disk? Disk layout is as follows: ad3s1a /tmp 2G ad3s1b swap 2G ad4s1d /boot 128M ad4s1a /1G ad4s1e /var 2G ad4s2d /usr 10G ad4s1b /home 5G Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
5.1 current make buildworld fails consistently on crtstuff.c- Help?
Hey all. I've been unsuccessful at performing a 'make buildworld' for
the past week based on a cvsup of 5.1-current. This is a fresh install
as of ~10 days ago on a Dual Celeron BP-6 system, 784M RAM. To say this
is getting frustrating at this point is an understatementanyone else
seeing this problem or have a suggestion on how to resolve this?
Failed buildlog follows, have seen this consistently break in the same
place for the past week of attempting 'make buildworld'. Some debugging
seems to point it's actually in the definition of
CRT_CALL_STATIC_FUNCTION(SECTION_OP, FUNC), likely in the definition of
one of the parameters themsevles, as removing the rest of the #defined
macro 'function' still results in the same compile error.
cc -O -pipe -DSMP -DAPIC_IO -march=pentiumpro -W -Wall -ansi -pedantic
-Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts
-Winline -Wmissing-prototypes -Wnested-externs -Wpointer-arith
-Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
-march=pentiumpro -DIN_GCC -DHAVE_LD_EH_FRAME_HDR
-finhibit-size-directive -fno-inline-functions -fno-exceptions
-fno-zero-initialized-in-bss -fno-omit-frame-pointer
-I/usr/src/gnu/lib/csu/../../../contrib/gcc/config
-I/usr/src/gnu/lib/csu/../../../contrib/gcc -I.
-I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools -g0 -DCRT_BEGIN -c -o
crtbegin.o /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c
In file included from /usr/src/contrib/gcc/crtstuff.c:63:
/usr/src/contrib/gcc/unwind-dw2-fde.h:37: warning: ISO C90 does not
support flexible array members
/usr/src/contrib/gcc/unwind-dw2-fde.h:53: warning: bit-field `sorted'
type invalid in ISO C
/usr/src/contrib/gcc/unwind-dw2-fde.h:54: warning: bit-field
`from_array' type invalid in ISO C
/usr/src/contrib/gcc/unwind-dw2-fde.h:55: warning: bit-field
`mixed_encoding' type invalid in ISO C
/usr/src/contrib/gcc/unwind-dw2-fde.h:56: warning: bit-field `encoding'
type invalid in ISO C
/usr/src/contrib/gcc/unwind-dw2-fde.h:59: warning: bit-field `count'
type invalid in ISO C
/usr/src/contrib/gcc/unwind-dw2-fde.h:139: warning: ISO C90 does not
support flexible array members
/usr/src/contrib/gcc/unwind-dw2-fde.h:147: warning: ISO C90 does not
support flexible array members
/usr/src/contrib/gcc/unwind-dw2-fde.h: In function `get_cie':
/usr/src/contrib/gcc/unwind-dw2-fde.h:157: warning: pointer of type
`void *' used in arithmetic
/usr/src/contrib/gcc/crtstuff.c: At top level:
/usr/src/contrib/gcc/crtstuff.c:122: warning: redundant redeclaration of
`__register_frame_info' in same scope
/usr/src/contrib/gcc/unwind-dw2-fde.h:95: warning: previous declaration
of `__register_frame_info'
/usr/src/contrib/gcc/crtstuff.c:125: warning: redundant redeclaration of
`__register_frame_info_bases' in same scope
/usr/src/contrib/gcc/unwind-dw2-fde.h:94: warning: previous declaration
of `__register_frame_info_bases'
/usr/src/contrib/gcc/crtstuff.c:127: warning: redundant redeclaration of
`__deregister_frame_info' in same scope
/usr/src/contrib/gcc/unwind-dw2-fde.h:101: warning: previous declaration
of `__deregister_frame_info'
/usr/src/contrib/gcc/crtstuff.c:129: warning: redundant redeclaration of
`__deregister_frame_info_bases' in same scope
/usr/src/contrib/gcc/unwind-dw2-fde.h:102: warning: previous declaration
of `__deregister_frame_info_bases'
/usr/src/contrib/gcc/crtstuff.c:198: warning: ISO C forbids empty
initializer braces
/usr/src/contrib/gcc/crtstuff.c:206: warning: ISO C forbids empty
initializer braces
/usr/src/contrib/gcc/crtstuff.c: In function `__do_global_dtors_aux':
/usr/src/contrib/gcc/crtstuff.c:280: warning: passing arg 1 of
`__deregister_frame_info' discards qualifiers from pointer target type
/usr/src/contrib/gcc/crtstuff.c: At top level:
/usr/src/contrib/gcc/crtstuff.c:288: error: syntax error before string
constant
/usr/src/contrib/gcc/crtstuff.c:288: warning: ISO C does not allow extra
`;' outside of a function
/usr/src/contrib/gcc/crtstuff.c: In function `frame_dummy':
/usr/src/contrib/gcc/crtstuff.c:316: warning: passing arg 1 of
`__register_frame_info' discards qualifiers from pointer target type
/usr/src/contrib/gcc/crtstuff.c: At top level:
/usr/src/contrib/gcc/crtstuff.c:325: error: syntax error before string
constant
/usr/src/contrib/gcc/crtstuff.c:325: warning: ISO C does not allow extra
`;' outside of a function
*** Error code 1
Stop in /usr/src/gnu/lib/csu.
*** Error code 1
This particular section of code in crtstuff.c is as follows:
CRT_CALL_STATIC_FUNCTION (INIT_SECTION_ASM_OP, frame_dummy)
which is defined as:
#ifndef CRT_CALL_STATIC_FUNCTION
# define CRT_CALL_STATIC_FUNCTION(SECTION_OP, FUNC) \
static void __attribute__((__used__)) \
call_ ## FUNC (void)\
{ \
asm (SECTION_OP); \
FUNC (); \
