Re: {a}sync updates (was Re: make install trick)
On Thu, Oct 07, 1999 at 11:57:26AM +1000, a little birdie told me that Peter Jeremy remarked How detailed should the man page be? Exactly my query in writing this ; If it stated "all file data will be written synchronously, but inodes where the only update is atime and free block bitmaps are written asynchronously", would that be any clearer to a user who didn't have a detailed understanding of UFS? If you would like it to say something different, write some patches and send them in as a PR (keeping in mind phk's recent e-mail about green bikesheds). I'm still stewing on what should be with it; what we have works fine, if being slightly inconsistent in an obscure way. I'm trolling for ideas on whether well enough should be left alone (since there's obviously an incredibly small percentage of people USING sync as a mountop), or whether a footnote should be added somewhere (I lean toward mount(2) instead of mount(8) myself, with a possible xref in mount(8)). I'll see what I think of, and possibly have some diffs tomorrow. There should be fairly few writes to the root partition, so having these writes synchronous is not a big performance hit. On the other hand, there are probably a _lot_ of read accesses to devices in /dev and files in /bin (how many of your scripts begin #!/bin/sh?). Unless you specify NOATIME, each of these read accesses implies an atime update within the inode. Making these synchronous probably would be a big performance hit. This is why I haven't screamed for them to be sync-tified... -- Matthew Fuller (MF4839) |[EMAIL PROTECTED] Unix Systems Administrator |[EMAIL PROTECTED] Specializing in FreeBSD |http://www.over-yonder.net/ FutureSouth Communications |ISPHelp ISP Consulting "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
The Hermit Hacker wrote: Figuring one of the things a friend of mine raves about Linux for is their kld's, I'd start playing with ours... Looking in /modules, I saw 'procfs', so, cool, a place to start...remove "options PROCFS" from kernel config, rebuild, install and reboot ... crashes... so, I figure that I somehow have to tell the kernel to load that module? fs modules are automagically loaded. Alas, that's the general direction for a lot of modules. The network ones, for instance. No more need to put in the device lines in the kernel configuration file, it will be automagically loaded by ifconfig. I don't know if this is working already or not, though. Now, how to tell the kernel to load modules. Well, some stuff you can set with rc.conf(5). Other stuff you may load explicitly through kldload. And, finally, you don't need to have the _kernel_ load it. You may edit loader.conf(5) to have it loaded at the same time the kernel is loaded by, well, the loader(8). :-) (the bootstrap loader) checked the kld man page, and nothing in there appears to be appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe it was something I was supposed to configure in there, but nothing appears to be in tehre either... Help? Wild shot: are your kernel world in sync? For isntance, you made a new kernel when you edited your kernel configuration file to remove the option line, right? If you just happened to have newer sources, the new kernel might have become incompatible with the older modules, which are not made automatically (except during world). cd /sys/modules; make all install. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "I always feel generous when I'm in the inner circle of a conspiracy to subvert the world order and, with a small group of allies, just defeated an alien invasion. Maybe I should value myself a little more?" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On Thu, 07 Oct 1999 03:00:52 -0300, The Hermit Hacker wrote: checked the kld man page, and nothing in there appears to be appropriate... You should have checked the SEE ALSO secion of the manpage (I wonder whether Ruslan Ermilov is reading?) *grin* SEE ALSO kldfind(2), kldfirstmod(2), kldload(2), kldnext(2), kldstat(2), kldunload(2), kldload(8), kldstat(8), kldunload(8) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: {a}sync updates (was Re: make install trick)
Maybe the best solution is the following: - leave "sync" with its current behaviour - create a sysctl to make it truely synchronous (I was thinking of a new mount option but thats overkill) and have the documentation for that sysctl state the performance hit and recommend that the filesystem be mounted with "noatime" when this sysctl is on. The sysctl could have three levels: - off - on for atime updates - on for atime updates and free block bitmap updates On Thu, 7 Oct 1999, Peter Jeremy wrote: On 1999-Oct-07 09:15:42 +1000, Matthew D. Fuller wrote: Is this good, bad, ugly, or just inconsistent? On the one hand, you can argue that 'sync should be sync should be sync, I don't bloody care, just don't do anything async at all', since that's what it's supposed to do: mount(8): syncAll I/O to the file system should be done synchronously. How detailed should the man page be? If it stated "all file data will be written synchronously, but inodes where the only update is atime and free block bitmaps are written asynchronously", would that be any clearer to a user who didn't have a detailed understanding of UFS? If you would like it to say something different, write some patches and send them in as a PR (keeping in mind phk's recent e-mail about green bikesheds). sync atime updates will slow it down, but on the flip side, if you're mounting sync in the first place you don't care much for speed anyway. There should be fairly few writes to the root partition, so having these writes synchronous is not a big performance hit. On the other hand, there are probably a _lot_ of read accesses to devices in /dev and files in /bin (how many of your scripts begin #!/bin/sh?). Unless you specify NOATIME, each of these read accesses implies an atime update within the inode. Making these synchronous probably would be a big performance hit. Peter -- /===\ | Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] | \===/ "If it is true that our Universe has a zero net value for all conserved quantities, then it may simply be a fluctuation of the vacuum of some larger space in which our Universe is imbedded. In answer to the question of why it happened, I offer the modest proposal that our Universe is simply one of those things which happen from time to time." E. P. Tryon from "Nature" Vol.246 Dec.14, 1973 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
shell script trouble
Hi, I have for a while now (couple of weeks now I think) noticed that certain shell scripts all of a sudden don't work any longer (even though they did just fine earlier) ... the only thing that actually changed has been more recent updates of FreeBSD-current. The scripts I am having problems with are: /usr/local/etc/rc.d/rc5des.sh /usr/local/etc/postfix/postfix-script Both of these scripts still are as they were installed by their respective ports. And I know both have worked just fine for months without problems. The rc5des breakage I noticed about a weeks ago .. the postfix breakage I noticed today, while installing postfix on another system and finding out "postfix reload" no longer worked ... Is there anybody here that happens to know why these previously perfectly working shell-scripts all of a sudden are broken now ? Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell script trouble
On Thu, 07 Oct 1999 17:09:16 +0200, Pascal Hofstee wrote: Is there anybody here that happens to know why these previously perfectly working shell-scripts all of a sudden are broken now ? You'll greatly increase the chances of getting a useful answer if you show us _how_ they're breaking. :-) Cut'n'paste is your friend. Later, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CVSup work again!
Hi, Before I completely forget: CVSup should work as before. The workaround is not needed anymore. Thanks for your patience, -- Marcel Moolenaarmailto:[EMAIL PROTECTED] SCC Internetworking Databases http://www.scc.nl/ The FreeBSD projectmailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSup work again!
In article [EMAIL PROTECTED], Marcel Moolenaar [EMAIL PROTECTED] wrote: Before I completely forget: CVSup should work as before. The workaround is not needed anymore. Thanks for your patience, Thanks for healing my problem child, Marcel. It's kind of, er, sensitive ... just like me. :-) Note, you still can't _build_ a working version under -current yet. That requires a lot of patches to the port. I'm working on it, but it will be a few days still before I commit anything. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
The network ones, for instance. No more need to put in the device lines in the kernel configuration file, it will be automagically loaded by ifconfig. I don't know if this is working already or not, though. It works in -CURRENT for most PCI network devices (`de' is one notable exception). ISA ones still need to be statically compiled into your kernel. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
i386 wierd one...... kernel stack frame pointer corruption(?)
This just started happening over the last day... It's blowing up during
probing because the frame pointer is getting nuked... this is a 2xPPro
machine.
The code in question is:
static u_int64_t
isp_get_portname(isp, loopid, nodename)
struct ispsoftc *isp;
int loopid;
int nodename;
{
u_int64_t wwn = 0;
mbreg_t mbs;
mbs.param[0] = MBOX_GET_PORT_NAME;
mbs.param[1] = loopid 8;
if (nodename)
mbs.param[1] |= 1;
isp_mboxcmd(isp, mbs);
Which generates:
12f0 isp_get_portname:
12f0: 55 pushl %ebp
12f1: 89 e5 movl %esp,%ebp
12f3: 83 ec 10subl $0x10,%esp
12f6: 56 pushl %esi
12f7: 53 pushl %ebx
12f8: bb 00 00 00 00 movl $0x0,%ebx
12fd: be 00 00 00 00 movl $0x0,%esi
1302: 66 c7 45 f0 6a movw $0x6a,0xfff0(%ebp)
1307: 00
1308: 8b 4d 0cmovl 0xc(%ebp),%ecx
130b: 66 c1 e1 08 shlw $0x8,%cx
130f: 66 89 4d f2 movw %cx,0xfff2(%ebp)
1313: 83 7d 10 00 cmpl $0x0,0x10(%ebp)
1317: 74 04 je 131d isp_get_portname+0x2d
1319: 80 4d f2 01 orb$0x1,0xfff2(%ebp)
131d: 8d 45 f0leal 0xfff0(%ebp),%eax
1320: 50 pushl %eax
1321: ff 75 08pushl 0x8(%ebp)
1324: e8 b7 27 00 00 call 3ae0 isp_mboxcmd
1329: 66 81 7d f0 00 cmpw $0x4000,0xfff0(%ebp) -- EBP is 0
132e: 40
There isn't anything in isp_mboxcmd that I can see would wipe the stack
such that I can see in the C code or the generated output. This code
itself hasn't changed in months.
One thing that is possible is that it's a very deep callstack... It's
during probing and it may have called completion on a completing command
while down at the bottom of the stack starting another command. If you run
out of kernel stack, don't you get some other kind of fault?
-matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: i386 wierd one...... kernel stack frame pointer corruption(?)
One thing that is possible is that it's a very deep callstack... It's during probing and it may have called completion on a completing command while down at the bottom of the stack starting another command. If you run out of kernel stack, don't you get some other kind of fault? That kinda depends on how hard you hit the bottom of the stack. I'd typically expect a double fault though. Note that SMP systems are much better behaved in this case than the old UP kernel stack setup. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
The Hermit Hacker [EMAIL PROTECTED] wrote: Figuring one of the things a friend of mine raves about Linux for is their kld's, I'd start playing with ours... [ Going off on a slight tangent ... ] You may have gone beyond this, but a good introduction to klds is an article called, "Attacking FreeBSD with Kernel Modules", at: http://thc.pimmel.com Click on "Articles", followed by "Attacking FreeBSD with Kernel Modules (example modules)". I'm not sure how up-to-date it is, though. Strange, but true. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On Thu, 7 Oct 1999, Daniel C. Sobral wrote: The Hermit Hacker wrote: Figuring one of the things a friend of mine raves about Linux for is their kld's, I'd start playing with ours... Looking in /modules, I saw 'procfs', so, cool, a place to start...remove "options PROCFS" from kernel config, rebuild, install and reboot ... crashes... so, I figure that I somehow have to tell the kernel to load that module? fs modules are automagically loaded. Alas, that's the general direction for a lot of modules. The network ones, for instance. No more need to put in the device lines in the kernel configuration file, it will be automagically loaded by ifconfig. I don't know if this is working already or not, though. Now, how to tell the kernel to load modules. Well, some stuff you can set with rc.conf(5). Other stuff you may load explicitly through kldload. And, finally, you don't need to have the _kernel_ load it. You may edit loader.conf(5) to have it loaded at the same time the kernel is loaded by, well, the loader(8). :-) (the bootstrap loader) checked the kld man page, and nothing in there appears to be appropriate...and just looked at my /usr/src/etc/rc* files to see if maybe it was something I was supposed to configure in there, but nothing appears to be in tehre either... Help? Wild shot: are your kernel world in sync? For isntance, you made a new kernel when you edited your kernel configuration file to remove the option line, right? If you just happened to have newer sources, the new kernel might have become incompatible with the older modules, which are not made automatically (except during world). cd /sys/modules; make all install. This one is probably it *sigh* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On Thu, 7 Oct 1999, Daniel O'Connor wrote:
On 07-Oct-99 Greg Lehey wrote:
Well, the standard way to load a kld is with kldload(1) or kldload(2).
I don't know if procfs works properly like this, though.
Well I would assume (aha) that when mount cannot find procfs in the list of
FS's the kernel knows about it would try and load it just like all the others..
okay, I had started to write down the whole error message last night,
until I saw that the process that died dealt with procfs and figured it
was that I took the option out...I'll redo it tonight when I get home and
write it all down and submit it...
Just to confirm, *technically*, I should just have to comment out the
options PROCFS in my kernel config, rebuild and reboot and since procfs
isn't in the kernel, it will look for it as a module?
Will report later tonight on what happens...
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
HEADS UP!! New telnet on the block
Hello all I have just committed Nick Sayer's SRA'ed telnet; this means that if you have the secure dist, and maybe Kerberos, you will have a telnet that attempts to do some encryption apart from the Kerberos stuff. Initial reports are that this encryption is weak, but it may be better than nothing. Investigate it carefully before committing your arms-smuggling business to its security :-). M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new PnP code and pcm and kernel userconfig
The sound card is: ... unknown0: 4232 on isa0 pcm0: CS4232 at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 unknown1: GAME PORT at port 0x200-0x207 on isa0 unknown2: MPU-401 at port 0x330-0x331 irq 9 on isa0 ... Everything looks fine but in my case the CS4232 is a buggy and it can't work in duplex mode and I have to change drq0=drq1=1 Now I can't do this from the kernel userconfig (boot -c ) - pnp configuration is missing. Any ideas? Thanks, Val __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: {a}sync updates (was Re: make install trick)
There should be fairly few writes to the root partition, so having An opionion. I use the HP workstation model where my / is 1800M. I have no use for /var and /usr and find them simply stupid in today's world. (except for ISP's where there is cause for a septerate /var). Lets stick to facts. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: {a}sync updates (was Re: make install trick)
mount(8): syncAll I/O to the file system should be done synchronously. How detailed should the man page be? If it stated "all file data will be written synchronously, but inodes where the only update is atime and free block bitmaps are written asynchronously", would that be any clearer to a user who didn't have a detailed understanding of UFS? Yes. I know the difference between sync/async and data/metadata. I haven't however, done a though wall-thru of the UFS code. If the manpage says "All I/O", then the system should do *ALL* I/O sync. This isn't Linux. Guess I go off editing mount(8) again. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell script trouble
On Thu, 7 Oct 1999, Pascal Hofstee wrote: The scripts I am having problems with are: /usr/local/etc/rc.d/rc5des.sh /usr/local/etc/postfix/postfix-script Both of these scripts still are as they were installed by their respective ports. And I know both have worked just fine for months without problems. The rc5des breakage is in the fact that it seems to attempt to start the rc5des client but that never seems to get launched ... running rc5des manually does work .. so the rc5des bianry itself isn't broken. The postfix breakage is in the fact that no matter What command i try ... the postfix-script (which is called by postfix itself) always says the following: su-2.03# /usr/local/sbin/postfix reload postfix-script: fatal: the Postfix mail system is not running I Know the mail system IS running on Postfix though: su-2.03# ps -aux | egrep postfix postfix 205 0.0 0.7 928 612 ?? I 5:01PM 0:00.26 qmgr -l -t fifo postfix 1585 0.0 0.5 872 508 ?? I11:39PM 0:00.02 pickup -l -t fif postfix 1809 0.0 0.8 952 724 ?? I12:11AM 0:00.02 smtpd -n smtp -t postfix 1810 0.0 0.7 928 680 ?? I12:11AM 0:00.02 cleanup -t unix postfix 1811 0.0 0.6 900 584 ?? I12:11AM 0:00.02 trivial-rewrite postfix 1812 0.0 0.8 956 712 ?? I12:11AM 0:00.02 local -t unix Pascal Hofstee - [EMAIL PROTECTED] -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d- s+: a-- C++ UB P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP-- t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+ --END GEEK CODE BLOCK-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: {a}sync updates (was Re: make install trick)
There should be fairly few writes to the root partition, so having An opionion. I use the HP workstation model where my / is 1800M. I have no use for /var and /usr and find them simply stupid in today's world. (except for ISP's where there is cause for a septerate /var). Lets stick to facts. -- -- David([EMAIL PROTECTED]) You are not disagreeing with him, David. You are just talking about another scenario other than the one under discussion. He was talking about the case where root is small. This whole discussion was about how softupdates behaves in the subcase of small root partitions. If you have a 1.8Gb root partition that also includes /var and /usr, this whole discussion is irrelevant. DS To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: make install trick
It was my understanding that it was standard recommended practice practice pretty much across the board to create the following separate filesystems: / /tmp (perhaps an mfs, perhaps softupdates, or whatever) /usr /var /var/tmp /home (or wherever you're going to store user directories) And that most people also then created a separate filesystem for /usr/local or /opt, or wherever they're going to store the additional You are entering religion. I despise, HIGHLY DESPISE, all the partitions. I don't care for the fragmentation and PITA when upgrading it leads to. HP and SGI workstations have a single huge /. Why do you need /usr seperate from / when you aren't diskless (or /usr'less)? Look at the historic reasons for this division and see if it still makes sense to you today. (and before someone misreads this, yes, my /home is a seperate partition and my /tmp is MFS) -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: shell script trouble
On Fri, 8 Oct 1999, Pascal Hofstee wrote: su-2.03# /usr/local/sbin/postfix reload postfix-script: fatal: the Postfix mail system is not running I Know the mail system IS running on Postfix though: su-2.03# ps -aux | egrep postfix postfix 205 0.0 0.7 928 612 ?? I 5:01PM 0:00.26 qmgr -l -t fifo postfix 1585 0.0 0.5 872 508 ?? I11:39PM 0:00.02 pickup -l -t fif postfix 1809 0.0 0.8 952 724 ?? I12:11AM 0:00.02 smtpd -n smtp -t postfix 1810 0.0 0.7 928 680 ?? I12:11AM 0:00.02 cleanup -t unix postfix 1811 0.0 0.6 900 584 ?? I12:11AM 0:00.02 trivial-rewrite postfix 1812 0.0 0.8 956 712 ?? I12:11AM 0:00.02 local -t unix There are some of Postfix's daemons running above, but you seem to be missing: root 286 0.0 0.8 872 220 ?? Is 29Sep99 0:10.23 /usr/local/libexec/postfix/master Which is the actual process that listens on port 25. Since 'postfix reload' cannot communicate with master, it says that postfix is not running. Next step, find out where your master is? - Chris D. Faulhaber [EMAIL PROTECTED] | All the true gurus I've met never System/Network Administrator,| claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25.
In article [EMAIL PROTECTED] you wrote: I'm getting this with a recent current (6. october): (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. Someone is telling us to transmit data, but has not provided a buffer with any data in it. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25.
In article [EMAIL PROTECTED] you wrote: I'm getting this with a recent current (6. october): (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. Someone is telling us to transmit data, but has not provided a buffer with any data in it. This is probably the breakage that phk introduced; it's been fixed for days. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: {a}sync updates (was Re: make install trick)
On 1999-Oct-08 08:13:12 +1000, David O'Brien wrote: mount(8): syncAll I/O to the file system should be done synchronously. How detailed should the man page be? If it stated "all file data will be written synchronously, but inodes where the only update is atime and free block bitmaps are written asynchronously", would that be any clearer to a user who didn't have a detailed understanding of UFS? Yes. I know the difference between sync/async and data/metadata. My point was that the average user probably doesn't. I agree that the current description glosses over the difference (and probably shouldn't). We need to strike a balance between providing enough detail for the knowledgeable user (who wants to know exactly what a sync mount does to different types of writes within the FS) and the novice user (who doesn't understand the details of UFS and is more likely to become confused). IMHO, `sync' does behave in a reasonable manner. I'm not sure how I'd go about explaining its behaviour to someone who didn't understand the UFS though. Guess I go off editing mount(8) again. I was going to suggest that the relationship between the sync option in mount(2,8) and O_FSYNC in open(2) be noted. Only problem is that O_FSYNC isn't documented :-(. Peter -- Peter Jeremy (VK2PJ)[EMAIL PROTECTED] Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ahc panics and (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25.
On Thu, Oct 07, 1999 at 03:56:27PM -0700, Mike Smith wrote: In article [EMAIL PROTECTED] you wrote: I'm getting this with a recent current (6. october): (da2:ahc2:0:2:0): data overrun detected in Data-Out phase. Tag == 0x25. (da2:ahc2:0:2:0): Have seen Data Phase. Length = 0. NumSGs = 1. Someone is telling us to transmit data, but has not provided a buffer with any data in it. This is probably the breakage that phk introduced; it's been fixed for days. That's why I updated - but the panic happened after that. -- B.Walter COSMO-Project http://www.cosmo-project.de [EMAIL PROTECTED] Usergroup[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On 07-Oct-99 The Hermit Hacker wrote: Just to confirm, *technically*, I should just have to comment out the options PROCFS in my kernel config, rebuild and reboot and since procfs isn't in the kernel, it will look for it as a module? Yes.. That should work fine.. In fact you can have all your FS's as modules except what / is.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On 07-Oct-99 The Hermit Hacker wrote: Just to confirm, *technically*, I should just have to comment out the options PROCFS in my kernel config, rebuild and reboot and since procfs isn't in the kernel, it will look for it as a module? Yes.. That should work fine.. In fact you can have all your FS's as modules except what / is.. You can have / too, as long as you load it with the loader. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On 08-Oct-99 Mike Smith wrote: Yes.. That should work fine.. In fact you can have all your FS's as modules except what / is.. You can have / too, as long as you load it with the loader. 8) And providing / is UFS because thats all the loader understands (?) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: modules: how to use?
On 08-Oct-99 Mike Smith wrote: Yes.. That should work fine.. In fact you can have all your FS's as modules except what / is.. You can have / too, as long as you load it with the loader. 8) And providing / is UFS because thats all the loader understands (?) No, it could be a DOS filesystem too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
How do I get a PCCARD modem to work?
It looks like both nsio and sio have PCCARD support disabled at the moment. Is there any other way I can get the system to recognize my modem? -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
My status with upgrade from 3.2 to 4.0
Hi, I just wanted to let you know that I was finally able to upgrade to 4.0-current from 3.2-release. I cvsuped the 4.0 code, i compiled the 4.0 config command, i compiled the 4.0 kernel, installed the kernel, rebooted, and build and installed the world and it worked. Then i just made my custom kernel, and did some other stuff. I have a few questions though, my Voodoo Banshee makes the console display screw up wheneven i go into X (my version is 3.3.5), and then exit X. (BTW this also did this on 3.2-release) Anybody else see this? Another thing was syslogd was looking for /var/log/security and can't find it, how can i fix this? Thanks Bill [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Email Acc. Only !
What will be the best way to create an email acc. only ? without have to create a shell acc. ? Like virtual table or something like that ? Any Idea ? Thank You. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Email Acc. Only !
On 08-Oct-99 Hector Colmenares wrote: What will be the best way to create an email acc. only ? without have to create a shell acc. ? Like virtual table or something like that ? Use cyrus IMAPD (which does POP3 too). Its in the ports collection. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Are you in Debt over your Head?
Get Out Of Debt Now! ARE YOU DROWNING IN DEBT? ARE YOU RECEIVING HARASSING PHONE CALLS? Let our staff help you to eliminate your debts. WITH OUR PROGRAMS YOU WILL*: * Pay off all unsecured debt in 18-30 months * Cut your current debt payments by up to 50% * Cut Credit Card Balances 30-60% * Build savings each and every month * Stop creditor harassment if that is currently a problem. http://3626046468/nt/debtreduction/index2.html a href="http://3626046468/nt/debtreduction/index2.html"Click Here/a * To be removed from our mailing list, please click enter your email address at the webpage with remove in the name field.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
:Hi again, : : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault :error (strange, it didn't look like a normal panic screen, just the :message and the content of three registers, then the syncing disks :message). It seems that I might be wrong about hardware not being the :problem. : : I've changed the motherboard, CPU, memory and the video card and I'm :waiting to see how much it's going to stay up (I have 1day 1hour uptime so :far)... : : Thanks, : Ady (@warpnet.ro) One thing I do on all 'server' class machines that I buy (and this is also something that BEST instituted as policy in 1998) is to only buy motherboards with ECC support and only buy ECC memory to go along with that support. If you are using a non-ECC motherboard or non-ECC memory I would heartily recommend that you adopt the same policy. Not that your problem is necessarily memory related, but I've found that memory-related problems account for at least 80% of the 'difficult to locate' hardware problems that normally occur with PC technology. ECC gives you protection not only against hardware faults, but it also protects you against remarked dynamic ram chips and processors by catching the timing errors that usually occur with such chips relatively soon after purchase rather then weeks or months down the line. Being the commodity it is, memory is the most likely item on the motherboard to be out of spec. Intel's ECC implementation is not perfect (1), but it's good enough to catch these sorts of problems. note 1: Intel doesn't implement memory scrubbing properly outside of the Xeon line and FreeBSD does not scrub memory either. Scrubbing is a method of preventing bit errors from building up in memory by regenerating the ECC bits with a memory read followed by a memory write of the same data. Outside of the Xeon chipsets the OS must issue a read followed by a write. With the Xeon chipsets the OS need only issue a read and hardware will automatically rewrite a correction if it finds a bit error. This information is 6 months old so the situation may have changed. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
Hi again, On Wed, 6 Oct 1999, Adrian Penisoara wrote: hi again, On Tue, 5 Oct 1999, Matthew Dillon wrote: : The problem is that the machine is completely locked, I can't get into :the debugger with CTR-ALT-ESC; no panics so there are no coredumps :catched. Any advise ? Could you escape in the debugger when you were hit :by these bugs ? If it's completely locked up and ctl-alt-esc doesn't work (and normally does work - try it on a working system to make sure that you've compiled in the appropriate DDB options), and you aren't in an X display (ctl-alt-esc isn't useful when done from an X display)... then your lockup problem is unrelated to mmap. No X on the machine, but CTRL-ALT-ESC doesn't work. And another thing: I tried the MMAP "exploit"/test that has been floating around at that time on another 3.2-STABLE machine SMP with 2 Pentiums and it does lock the machine but you can switch consoles and escape to the debugger; on the production server (K6-2 300) everything goes dead when it happens (I haven't tried the MMAP test)... You're probably right, it's not the MMAP bug; but it's not faulty hardware -- I'll have an undeniable proof in a few days, I have downgraded to 3.1-STABLE as of 20th April... Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault error (strange, it didn't look like a normal panic screen, just the message and the content of three registers, then the syncing disks message). It seems that I might be wrong about hardware not being the problem. I've changed the motherboard, CPU, memory and the video card and I'm waiting to see how much it's going to stay up (I have 1day 1hour uptime so far)... Thanks, Ady (@warpnet.ro) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patches avail?] Re: MMAP() in STABLE/CURRENT ...
:Hi again, : : Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault :error (strange, it didn't look like a normal panic screen, just the :message and the content of three registers, then the syncing disks :message). It seems that I might be wrong about hardware not being the :problem. : : I've changed the motherboard, CPU, memory and the video card and I'm :waiting to see how much it's going to stay up (I have 1day 1hour uptime so :far)... : : Thanks, : Ady (@warpnet.ro) One thing I do on all 'server' class machines that I buy (and this is also something that BEST instituted as policy in 1998) is to only buy motherboards with ECC support and only buy ECC memory to go along with that support. If you are using a non-ECC motherboard or non-ECC memory I would heartily recommend that you adopt the same policy. Not that your problem is necessarily memory related, but I've found that memory-related problems account for at least 80% of the 'difficult to locate' hardware problems that normally occur with PC technology. And to add support to this, AAI, the oldest vendor of FreeBSD specific systems, implemented a similiar policy on all system sold sometime in 1992. But at that time ECC was not avaliable so it was ``parity memory is required, and the chipset must support it''. As soon as ECC chipsets hit the market the policy was changed to refect this. We also require all memory that we purchase be backed by a no-fuss lifetime warranty, which we pass on to the end user. I strongly recommend that any one running Unix on a PC do the same, it will save you in the long run. Since implementing the policies we have seen a near 0 memory related problem after burnin with our systems. -- Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: How do I get a PCCARD modem to work?
It seems Justin T. Gibbs wrote: It looks like both nsio and sio have PCCARD support disabled at the moment. Is there any other way I can get the system to recognize my modem? Fix the broken sio, it might be KNF and all but it doesn't work... -Soren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
