Re[2]: FreeBSD 4.6-RELEASE, 4.7-RELEASE vs Asus P2B-DS motherboard
Hello KAKIUCHI, Saturday, October 26, 2002, 4:05:36 PM, you wrote: KM> I'm using P2B seriese boards. KM> When I enable USB IRQ on BIOS or remove USB device from kernel, KM> it's seems good. Thanks a lot. Now it works ! 8)) -- Best regards, Eugenemailto:emz@;norma.perm.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Unable to compile -STABLE kernel with SMBFS
hi, there! On Mon, Oct 28, 2002 at 08:28:41AM +0200, Toni Viemero wrote: > I tried compiling new kernel with the following options: > > options SMBFS #SMB/CIFS filesystem > options NETSMB #SMB/CIFS requester > options NETSMBCRYPTO#encrypted password support for SMB > > Error messages attached as smbfs_smb.txt. > > Is the problem me or in the kernel itself? you forgot 'options LIBMCHAIN' and 'options LIBICONV' /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Unable to compile -STABLE kernel with SMBFS
I tried compiling new kernel with the following options: options SMBFS #SMB/CIFS filesystem options NETSMB #SMB/CIFS requester options NETSMBCRYPTO#encrypted password support for SMB Error messages attached as smbfs_smb.txt. Is the problem me or in the kernel itself? -- Toni Viemerö | http://selfdestruct.net "When life hands you a lemon, say, 'Oh yeah, I like lemons. What else ya got?'" linking kernel smbfs_smb.o: In function `smbfs_smb_lockandx': smbfs_smb.o(.text+0x9a): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0xa8): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0xb6): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0xd0): undefined reference to `mb_put_mem' smbfs_smb.o(.text+0xe4): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0xf2): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0x103): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x11c): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x135): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x152): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x162): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x178): undefined reference to `mb_put_uint32le' smbfs_smb.o: In function `smbfs_smb_statfs2': smbfs_smb.o(.text+0x21f): undefined reference to `mb_init' smbfs_smb.o(.text+0x227): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x259): undefined reference to `md_get_uint32' smbfs_smb.o(.text+0x263): undefined reference to `md_get_uint32le' smbfs_smb.o(.text+0x26d): undefined reference to `md_get_uint32le' smbfs_smb.o(.text+0x277): undefined reference to `md_get_uint32le' smbfs_smb.o(.text+0x284): undefined reference to `md_get_uint16le' smbfs_smb.o: In function `smbfs_smb_statfs': smbfs_smb.o(.text+0x350): undefined reference to `md_get_uint16le' smbfs_smb.o(.text+0x363): undefined reference to `md_get_uint16le' smbfs_smb.o(.text+0x376): undefined reference to `md_get_uint16le' smbfs_smb.o(.text+0x38c): undefined reference to `md_get_uint16le' smbfs_smb.o: In function `smbfs_smb_setfsize': smbfs_smb.o(.text+0x44f): undefined reference to `mb_put_mem' smbfs_smb.o(.text+0x45d): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x470): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x47e): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x498): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0x4a9): undefined reference to `mb_put_uint16le' smbfs_smb.o: In function `smbfs_smb_setpattr': smbfs_smb.o(.text+0x53f): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x57d): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x58f): undefined reference to `mb_put_mem' smbfs_smb.o(.text+0x5ac): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0x5de): undefined reference to `mb_put_uint8' smbfs_smb.o(.text+0x5ec): undefined reference to `mb_put_uint8' smbfs_smb.o: In function `smbfs_smb_setptime2': smbfs_smb.o(.text+0x669): undefined reference to `mb_init' smbfs_smb.o(.text+0x671): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x679): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x6a5): undefined reference to `mb_init' smbfs_smb.o(.text+0x6ad): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x6e7): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x6f2): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x72b): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x736): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x73e): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x746): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x754): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x75c): undefined reference to `mb_put_uint32le' smbfs_smb.o: In function `smbfs_smb_setpattrNT': smbfs_smb.o(.text+0x7dc): undefined reference to `mb_init' smbfs_smb.o(.text+0x7e7): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x7ef): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x81b): undefined reference to `mb_init' smbfs_smb.o(.text+0x825): undefined reference to `mb_put_int64le' smbfs_smb.o(.text+0x860): undefined reference to `mb_put_int64le' smbfs_smb.o(.text+0x898): undefined reference to `mb_put_int64le' smbfs_smb.o(.text+0x8a6): undefined reference to `mb_put_int64le' smbfs_smb.o(.text+0x8b1): undefined reference to `mb_put_uint32le' smbfs_smb.o: In function `smbfs_smb_setftime': smbfs_smb.o(.text+0x954): undefined reference to `mb_put_mem' smbfs_smb.o(.text+0x962): undefined reference to `mb_put_uint32le' smbfs_smb.o(.text+0x9b2): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0x9c6): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0xa16): undefined reference to `mb_put_uint16le' smbfs_smb.o(.text+0xa2a): undefined reference to `mb_put_uint16le' smbfs_smb.o:
ipfw pipe show: No buffer space available
Hi! I have 210 pipes configured with ipfw1, each uses GRED. It works fine but sometimes I cannot get list of pipes: # ipfw pipe show ipfw: getsockopt(IP_DUMMYNET_GET): No buffer space available If I repeat, it can sometimes success and fail again next time. What's wrong? netstat -m shows I have about 4200 mbufs used/peak and 32768 total. Eugene Grosbein To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Mergemaster [was: Re: Ifconfig config of gif tunnels]
Phil Kernick wrote:
> I'd also like the opposite - a list of files that mergemaster will not update
> under any circumstances.
mergemaster does its comparison based on the presence or absence of
files in the live tree on the system, and the temproot tree created by
mergemaster. So, if you have files that you never want mm to compare,
you can simply use the MM_PRE_COMPARE_SCRIPT hook and delete those files
from the temproot tree. Similarly, if you always want to update certain
files, you could use the same hook and delete the files from the live
tree, and use the autoinstall option to mergemaster.
in ~/.mergemasterrc (or /etc/mergemaster.rc)
AUTO_INSTALL=yes
MM_PRE_COMPARE_SCRIPT=/usr/local/libexec/mergemaster_pre_compare
In /usr/local/libexec/mergemaster_pre_compare:
#!/bin/sh
# NOTE: No PATH needed, because mm's PATH is already draconian enough
# I want mm to always ignore the motd
rm -f ${TEMPROOT}/etc/motd
# I don't use inetd, so always just update this file
rm -f /etc/inetd.conf
# NOTE: No exit here, or else mm will exit too
Of course, the motd example could just as easily be accomplished by
putting 'IGNORE_MOTD=yes' in .mergemasterrc, but you get the idea.
Because of how mm sources the *_SCRIPT's, all the internal variables are
available for its use, which is quite handy. You could make the second
example somewhat safer by doing this for example:
if [ -n "${AUTO_INSTALL}" ]; then
rm -f /etc/inetd.conf
fi
Personally, I am philosophically opposed to having mm automatically
update files, which is why there are no options to do so in the script
itself. However, enough people have requested those features that I have
added the _SCRIPT hooks so that people can load their own guns, and
point them at their feet at will.
> At the moment I remove the CVS id from the top of
> all of the files that I modify so that I remember during mergemaster whether I
> should update them or not.
ERrr that's weird. :) If the cvs ID's are the same in the live
version and the temproot version, mm will simply ignore the file. If
they are different, mm will show you the diffs, and you can choose how
to deal with them.
I like the idea that someone else suggested of putting:
# LOCAL MODIFICATIONS #
near anything you changed, so that you can see it in the diffs easier. I
do something similar myself.
HTH,
Doug
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: mergemaster error messages
"Maxim M. Kazachek" wrote: > > After mergemaster I see following messages: > > Do you wish to delete what is left of /var/tmp/temproot? [no] yes > rm: /var/tmp/temproot/var/empty: operation not permitted > rm: /var/tmp/temproot/var: Directory not empty > rm: /var/tmp/temproot: Directory not empty > *** /var/tmp/temproot has been removed I realize that this message is old, but users of -Stable might want to know that I recently mfc'ed my fixes for this problem, and a few DESTDIR related fixes as well. > Why we need to do rm -rf twice before and after chflags -R 0? If you remove all the files that don't have flags before doing the 'chflags -R' step, it goes much faster. Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: unmounting disabled with writeprotected floppy
On Sun, 27 Oct 2002, Hanspeter Roth wrote: HR> I frequently store some files on a floppy. Thus my fstab contains HR> /dev/fd0/floppy msdos rw,noauto 0 0 HR> This usually allows me to write on the floppy. HR> Sometimes I insert a floppy that's writeprotected. HR> If I forget to mount it readonly explicitly (-r) the system thinks HR> it is writeable. If the floppy is unmounted without any attempts to HR> write to the floppy there is no problem. HR> The problem starts if I forget to mention -r. After attempting to HR> unmount the floppy the system starts to I bark at the console. HR> It prevents the floppy from being unmounted. After shutdown is HR> issued the system insists that the floppy must be unmounted _before_ HR> any other filesystem (/, /var, /usr) is unmounted. But since it also HR> prevents the floppy from being unmounted it also prevents the other HR> filesystems from being unmounted. They will be fscked on the next HR> boot. HR> I think this situation is better solved in Linux. Why not mount the HR> floppy implicitly readonly if it is writeprotected? There was a thread about it a couple of weeks ago, you can look through the archives. For the meantime, a perfectly accepted for me workaround is emulators/mtools port. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
unmounting disabled with writeprotected floppy
Hello, I frequently store some files on a floppy. Thus my fstab contains /dev/fd0/floppy msdos rw,noauto 0 0 This usually allows me to write on the floppy. Sometimes I insert a floppy that's writeprotected. If I forget to mount it readonly explicitly (-r) the system thinks it is writeable. If the floppy is unmounted without any attempts to write to the floppy there is no problem. The problem starts if I forget to mention -r. After attempting to unmount the floppy the system starts to I bark at the console. It prevents the floppy from being unmounted. After shutdown is issued the system insists that the floppy must be unmounted _before_ any other filesystem (/, /var, /usr) is unmounted. But since it also prevents the floppy from being unmounted it also prevents the other filesystems from being unmounted. They will be fscked on the next boot. I think this situation is better solved in Linux. Why not mount the floppy implicitly readonly if it is writeprotected? -Hanspeter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: GRE tunnel kernel support for SQUID and Cisco (wccp v1)
On Sun, Oct 27, 2002 at 05:45:43PM +0200, Lefteris Tsintjelis wrote: > Hi all. > > I am not sure I send this to the right list. If no, I apologize and > please tell me where to send it to. > Is there any chance of including the following patch to kernel? New code submissions must be committed to -CURRENT first. Does there exist an implementation of this for -CURRENT? Also, discussion of code submission should be done on a technical list, such as [EMAIL PROTECTED] for this case. Kris msg50854/pgp0.pgp Description: PGP signature
