Re: mountpoint locking with fbsd-nfs
Matthew Dillon scribbled this message on Aug 1: :Yeah, I know about -alldirs... The problem was that we had customers who :wanted us to export their home directories, and unless I gave them their own :filesystem, I couldn't restrict it in the manner i wanted. :) : :Just checking to see that I wasn't missing a way to do this. :) I've never in my life tried this - it probably won't work, but ... use the null device maybe to create a mount point for each home dir and then export that? do you guys ever read the man page?? read the following about 10 times... it is hard to understand, but make sure you know what it says, not what you THINK is says... this is from exports(5): A host may be specified only once for each local filesystem on the server and there may be only one default en- try for each server filesystem that applies to all other hosts. The lat- ter exports the filesystem to the ``world'' and should be used only when the filesystem contains public information. so, if you want to export /var and /var/tmp both on the same file system to the same host, it would be: /var /var/tmp somehost because of this, I organize my /etc/exports file by file system and then by host... so I do stuff like: #all of my /usr exports /usr /usr/local hosta /usr /usr/X11R6 hostb /usr/local -ro #all of my /a exports /a hostc /a /a/datadir hostd -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mountpoint locking with fbsd-nfs
On Sun, 1 Aug 1999, Kevin Day wrote: :Yeah, I know about -alldirs... The problem was that we had customers who :wanted us to export their home directories, and unless I gave them their own :filesystem, I couldn't restrict it in the manner i wanted. :) : :Just checking to see that I wasn't missing a way to do this. :) : :Kevin I've never in my life tried this - it probably won't work, but ... use the null device maybe to create a mount point for each home dir and then export that? I think it sees through this. su-2.03# cat /etc/exports /varhome /mnthome su-2.03# mount /dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3970 async 1321097) procfs on /proc (local) nfs:/home on /usr/home (noatime) nfs:/var/mail on /var/mail (noatime) /var/tmp on /mnt (local) su-2.03# mountd Aug 1 23:17:48 celery mountd[89177]: can't change attributes for /mnt That was a very good idea though, i'd never have thought of it. :) I'll have to play with this more. :) It cannot ever work properly. NFS is stateless, the nfs filehandles refer to inodes, you may be able to get this to actually export files, however i'm pretty sure without other measures someone would be able to cons up a fake nfs handle for files he doesn't own. (I think) Here's two things that may work: exporting -alldirs to specific hosts using the -mapall option in /exports /home -mapall=robert roberts.machine /home -mapall=julian julains.machine using a vn device, creating a ufs on it and then mounting it, then exporting it. this gives you nice per-user quotas as well :) -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] systems administrator and programmer Wintelcom - http://www.wintelcom.net/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Assembler capable of supporting 3dnow!
On Sun, 1 Aug 1999, Brian F. Feldman wrote: On Sun, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: I'm messing around with the latest mesa and have discovered (suprise)that our assembler doesn't support 3dnow instructions. Are there any plans to update to a version of binutils that does? Linux's stuff appears to support it. According to dfr, no, since the releases are in "beta" now or something. I think it's worth updating. And no, it would be too hard to get 3DNow! wihtouut updating gas. However: you can use the linux_devutils gcc/as/ld etc. to build the parts of whatever you need with 3dnow instructions. There are no public betas that I can find. The only updates to binutils publically available seem to be the Linux patchsets :-(. -- Doug Rabson Mail: [EMAIL PROTECTED] Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: prepdisk
What fails? Can you be more specific? How recent are your boot1/boot2 blocks? I would be inclined to dd at least 8k over the front of the disk myself, but I don't think that's relevant in your case. Disk error #1 while trying to load boot/loader. I think the bios in this case trust the 5 in the length field of the mbr. Any better luck after enabling "LBA access" in boot1 as a build option (added back a few weeks ago), or does the BIOS not support this? BTW: Is this a genuine hard drive, or some form of disk-on-a-chip? I seem to recall the BIOS geometry in some cases uses a small number of sectors per track, which may push part of the 'a' partition beyond the 1023 CHS limit. Anyway, if some debugging code would help here, let me know. -- Robert Nordier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: APM related panic
# sorry to break the thread, I'm a digest reader...
Hi,
apm0: APM BIOS on motherboard
apm: APM BIOS version 0102
apm: Code16 0xc00f, Data 0xc00fdfa0
apm: Code entry 0x8010, Idling CPU enabled, Management enabled
apm: CS_limit=0x0, DS_limit=0x0
These limits look pretty suspect, although the code segment below looks
OK.
I suspect too, especially ds limit.
I've seen such bogus 1.2 APM BIOSes before. I hope attached patch
help you (for /sys/i386/apm/apm.c).
P.S.
Thank you for enhanced APM code, mike. I had enjoy last week end to
study the new code. Some of my concerns about APM gone :-)
--- apm.c- Mon Aug 2 21:31:20 1999
+++ apm.c Mon Aug 2 21:49:52 1999
@@ -773,6 +773,30 @@
sc-bios.seg.code16.limit = 0x;
sc-bios.seg.data.limit = 0x;
}
+
+ /*
+* Segment limits fixup:
+* Some bogus APM V1.1 (even if V1.2) BIOSes do not return
+* any size limits in the registers they are supposed to.
+* if we see zero limits here, we assume that means they
+* should be 64k.
+*/
+
+ /* code segment (16 bit) */
+ if (sc-bios.seg.code16.limit == 0) {
+#ifdef APM_DEBUG
+ printf("apm_probe: APM bios gave zero len code16, pegged to 64K\n");
+#endif
+ sc-bios.seg.code16.limit = 0x;
+ }
+ /* data segment */
+ if (sc-bios.seg.data.limit == 0) {
+#ifdef APM_DEBUG
+ printf("apm_probe: APM bios gave zero len data, tentative 64K\n");
+#endif
+ sc-bios.seg.data.limit = 0x;
+ }
+
return(0);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: prepdisk
On Tue, 3 Aug 1999, Bruce Evans wrote: My semantics may be wrong on these two: what I'm talking about is what is in handbook chapter 8 "Using command line utilities " gives you a disk which doesn't boot. Ok; of those two examples, the first should give you a truly dedicated disk. (You can only generate a "dangerously dedicated" disk with sysinstall.) The first gives a vanilla dangerously dedicated disk (one with a historical bogus DOSpartition table of size 5). Terminology for variants is less standard, e.g.: very dangerously dedicated:= dangerously dedicated with the DOSpartition table and/or boot signature zeroed or otherwise clobbered. undangerously dedicated:= dangerously dedicated with the DOSpartition table fixed to cover the whole disk (including the MBR). This is very easy to generate without sysinstall (just enter the start (0) and size for one partition in fdisk(8)). I've been looking for that tidbit forever! If you can build up a sample session, I'll docify it pronto. I don't have a disk to clobber or else I'd be writing docs right now :) 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
Re: APM related panic
Hi! Thanks, seems your patch did the trick (panic gone). Following is dmesd: apm_probe: APM bios gave zero len code16, pegged to 64K apm_probe: APM bios gave zero len data, tentative 64K apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdfa0 apm: Code entry 0x8010, Idling CPU enabled, Management enabled apm: CS_limit=0x, DS_limit=0x apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU enabled Add hook "default suspend" Add hook "default resume" Sincerely, Maxim # sorry to break the thread, I'm a digest reader... Hi, apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdfa0 apm: Code entry 0x8010, Idling CPU enabled, Management enabled apm: CS_limit=0x0, DS_limit=0x0 These limits look pretty suspect, although the code segment below looks OK. I suspect too, especially ds limit. I've seen such bogus 1.2 APM BIOSes before. I hope attached patch help you (for /sys/i386/apm/apm.c). P.S. Thank you for enhanced APM code, mike. I had enjoy last week end to study the new code. Some of my concerns about APM gone :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: APM related panic
Hi! Thanks, seems your patch did the trick (panic gone). Following is dmesd: Thanks for the confirmation; I've made an even more pessimistic patch that should cover your situation. Please let me know if your next CTM works correctly. Thanks for the quick bug report too! apm_probe: APM bios gave zero len code16, pegged to 64K apm_probe: APM bios gave zero len data, tentative 64K apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdfa0 apm: Code entry 0x8010, Idling CPU enabled, Management enabled apm: CS_limit=0x, DS_limit=0x apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU enabled Add hook "default suspend" Add hook "default resume" Sincerely, Maxim # sorry to break the thread, I'm a digest reader... Hi, apm0: APM BIOS on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f, Data 0xc00fdfa0 apm: Code entry 0x8010, Idling CPU enabled, Management enabled apm: CS_limit=0x0, DS_limit=0x0 These limits look pretty suspect, although the code segment below looks OK. I suspect too, especially ds limit. I've seen such bogus 1.2 APM BIOSes before. I hope attached patch help you (for /sys/i386/apm/apm.c). P.S. Thank you for enhanced APM code, mike. I had enjoy last week end to study the new code. Some of my concerns about APM gone :-) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ [EMAIL PROTECTED] \\-- Joseph Merrick \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCMCIA drivers
In message v02110102b3cae5bc55e9@DialupEudora Adam Wight writes: : First, the current zp driver cannot be configured if the pccard services : are being used, since it uses its own pccard code. Very Bad. : : Then, the PCMCIA model that we use now makes it impossible to use both : functions of a doubly useful card. This too is Very Bad. : : Is anyone addressing these problems? Yes. I'm working on porting the newconfig based pccard/cardbus code to -current. zp is evil and will die. The current pccard code is evil and must die. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: junior-hacker task: prepdisk
In message [EMAIL PROTECTED] Poul-Henning Kamp writes: : My real beef here is not with the boot failure but with the fact that our : command line tools stink when I bring in a new blank disk... Yes. Several times I've hit this problem, but have never been PO'd enough to fix it... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic plus advice needed
On Sunday, 1 August 1999 at 23:33:07 +0200, Andrzej Bialecki wrote: On Sat, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote: No, just options DDB. This bt was obtained after doing gdb -k kernel.0 vmcore.0 I still have the DDB trace on paper which I can type in if needed/wanted. What you do with the results depends a lot on what you find. On the whole, I wouldn't think it worth the pain of debugging without symbols. No it isn't... Another handful tricks of the trade: * if you still have exactly the same source tree and config file, recompile the kernel with -g to obtain the version with debugging symbols bde has reported that the code may not be identical when compiling for debugging. It should be, but for obscure reasons it doesn't quite make it. * if you can't for the life of you get the crash dump to examine what went wrong, do remember of remote GDB option under DDB - that is, if you have another machine with the same sources and kenel. But if the problem is repeatable you can prepare it beforehand... Remote GDB works miracles then. When it works. It's very temperamental. Greg -- See complete headers for address, home page and phone numbers finger [EMAIL PROTECTED] for PGP public key To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sh still is not working for MAKEDEV
On Mon, Aug 02, 1999, Maxim Sobolev wrote: Hi folks, Does anybody investigating what wrong with the sh in the -current? As I reported earlier it still fails to correctly process MAKEDEV script. Are you sure you are not running bash instead of sh? -- |Chris Costello [EMAIL PROTECTED] |Microwave: Signal from a friendly micro... `--- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sh still is not working for MAKEDEV
Well, he can run "ktrace -di ./MAKEDEV whatever" then kdump foo.dump Or compile sh with debug symbols and trace down the failure. -- Amancio Hasty [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sh still is not working for MAKEDEV
Amancio Hasty wrote: Well, he can run "ktrace -di ./MAKEDEV whatever" then kdump foo.dump Or compile sh with debug symbols and trace down the failure. Thanks to all for prompt replies. It seems like a bug in egcs which broke sh when "-march=pentium" option is used while -O? level doesn't really matter. Any ideas on how to track it down? Bests, Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
