From danny at cs.huji.ac.il Fri Aug 1 06:08:22 2008 From: danny at cs.huji.ac.il (Danny Braniss) Date: Fri Aug 1 06:08:30 2008 Subject: Laptop suggestions? In-Reply-To: <20080731100821.GA15213@eos.sc1.parodius.com> References: <1216910072.2251.8.camel@jill.exit.com> <86y73j341e.fsf@ds4.des.no> <86bq0ftjf6.fsf@ds4.des.no> <8C2BF4B9-14CD-40EA-B22E-DBB7060BFE46@bnc.net> <3A7C430E-AA1C-4CF3-88F5-F7A0EBE3273A@bnc.net> <20080731100821.GA15213@eos.sc1.parodius.com> Message-ID: > On Thu, Jul 31, 2008 at 11:17:54AM +0200, Achim Patzner wrote: > > Drivers? Who cares. Serial port? Just plug in an USB-to-serial. > > You've obviously never used a USB-to-serial adapter. Are you aware of > the fact that there is no serial device class as part of the USB > specification? (Quite a great irony, if you ask me. Universal SERIAL > Bus, yet no serial device class...) AFAIK, there isn't even a draft > proposal for such. > and even more amazing, that we still have to configure the baudrate! > You *must* have drivers for a USB-to-serial adapter. And every adapter > is different, depending upon the adapter chipset used, many of which are > not disclosed in product specifications, so there's no way to guarantee > it'll work with FreeBSD. On -stable (I believe) some people have > mentioned which USB-to-serial adapters work great under FreeBSD and > Windows, while others are horrible (dropping characters, broken flow > control, interrupt issues, and many other problems). > > > It's a perfect machine for the desktop; I've forbidden FreeBSD to come > > creeping out the server room some years ago. I need it for keeping the > > penguins away, it's really good at that (no wonder - pitchforks do > > hurt). > > But it's a pain for desktoppy things - so why shouldn't I use something > > less useful? And the other way round: Running Mac OS X Server is the > > most painful thing I've ever been paid for; I've been replacing a lot of > > them with FreeBSD-based servers. > > The amount of rhetoric in these two paragraphs is amazing; I literally > cannot tell if you're trolling with anti-FreeBSD propaganda, or if > you're trolling with pro-FreeBSD propaganda. Congratulations, you've > confused at least one reader. there is an old saying, If Moses can't get to the hill, the hill will come to Moses or is it the other way round? get a serial to ethernet gadgets, or use IPMI/ILO/or-whatever-will-be-next. I agree with Achim, I also tried to run FreeBSD on some laptops, and I lost. The Mac has some drawbacks, sure, but it has - still - a Unix flavour, and FreeBSD still rocks on the servers, slightly less on the descktop - nvidia ... danny From tevans.uk at googlemail.com Fri Aug 1 08:19:54 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Fri Aug 1 08:20:06 2008 Subject: Laptop suggestions? In-Reply-To: References: <1216910072.2251.8.camel@jill.exit.com> <86y73j341e.fsf@ds4.des.no> <86bq0ftjf6.fsf@ds4.des.no> <8C2BF4B9-14CD-40EA-B22E-DBB7060BFE46@bnc.net> <1217505964.78925.12.camel@localhost> Message-ID: <1217578788.78925.17.camel@localhost> On Thu, 2008-07-31 at 20:26 -0300, Carlos A. M. dos Santos wrote: > On Thu, Jul 31, 2008 at 9:06 AM, Tom Evans wrote: > > > > On Wed, 2008-07-30 at 21:45 -0300, Carlos A. M. dos Santos wrote: > >> Please define "comfortable". I've been running FreeBSD 7.0 pretty > >> comfortably on my HP nx6320 for several months now. I never attempted > >> to use neither Bluetooth nor the fingerprint reader, so I don't miss > >> them. The only real drawback I've found was that the memory card > >> reader does not work. I also ran 8.0-CURRENT on a HP 6910p because 7.0 > >> did not support the WI-FI card. > > > Another happy BSD user on HP - nc6320 this time though. intel(4x) > > graphics, wpi(4) wifi, bge(4) networking, fwochi(4) firewire, serial > > port, plenty of USB ports. Even the fingerprint scanner works > > (security/libfprint). > > I don't use bluetooth or the card reader, so cannot comment on them. > > > > The one down side of my HP laptop is the HP BIOS refuses to start up > > with a different wifi card installed - I'd quite like to use an ath(4) > > based card.. > > Do you have an up-to-date BIOS? I had some problems booting from USB > that I could solve using the latest BIOS version. > Yes, latest BIOS. If you search through the BIOS file, it is fairly easy to find the list of 'approved' HP vendor/device ids that it will allow to be put in the mini pci-e slot and still boot up (there are only 4 distinct device ids defined in the BIOS). I've considered just manually editing it to replace one of the device ids with my replacement card, but I fear I would probably brick the laptop! Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080801/d0602957/attachment.pgp From peterjeremy at optushome.com.au Fri Aug 1 11:11:40 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri Aug 1 11:11:47 2008 Subject: Laptop suggestions? In-Reply-To: <5f67a8c40807271423t3dc1e89bn7295b9af9fa0eda5@mail.gmail.com> References: <1216910072.2251.8.camel@jill.exit.com> <200807251802.23984.lists@jnielsen.net> <1217120187.37762.7.camel@jill.exit.com> <5f67a8c40807271423t3dc1e89bn7295b9af9fa0eda5@mail.gmail.com> Message-ID: <20080801111136.GS1359@server.vk2pj.dyndns.org> On 2008-Jul-27 17:23:46 -0400, Zaphod Beeblebrox wrote: > we'd need a method of remembering what file handles were >connected to so that they could be "reopened" (in this, I envision some type >of text string... maybe a URI/URL). As a bonus, this would give us process >migration between systems, too (assuming the URI were portable between self >same systems --- which isn't horribly hard with nfs mounts and whatnot). What you are describing here sounds more like the process checkpointing functionality that Softway (I think it was) developed sometime last century. There should be a paper on it in an AUUG Conference Proceedings somewhere. Process checkpointing is somewhat different to suspend/resume: With suspend/resume, you are saving the entire system state - which is basically a matter of dumping physical RAM to disk and being able to restore it later. You don't need to be able to isolate individual processes and there's no need to 'reopen' file handles because they will automatically re-instantiate when you restore the kernel state that included them being open. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080801/3f1f4f42/attachment.pgp From alik at klikni.cz Fri Aug 1 13:14:22 2008 From: alik at klikni.cz (Alik Dolezal) Date: Fri Aug 1 13:14:27 2008 Subject: Laptop suggestions? In-Reply-To: <20080724202140.GA2893@eos.sc1.parodius.com> References: <1216910072.2251.8.camel@jill.exit.com> <20080724202140.GA2893@eos.sc1.parodius.com> Message-ID: > And if you go with Lenovo, be aware that their T60/T60p/T61/T61p series > (and possibly the X-series) are known to sport very high temperatures. > Some people have reported temperatures of nearly 90C on their GPU (when > idling), which has a direct effect on the overall temperature of the CPU > (due to close proximity) and so on. This requires the fan to be on at > almost all times (usually low-speed mode). Others have it worse (the > laptop literally shutting off in the middle of operation): > I bought Lenovo T61 recently and dont see any hight GPU temperatures. GPU temperature is about 55C when idling. I never notice (so far) temperature above 65C. More annoying is (subjectively) hot HDD under right wrist. Cheers Ale? From samflanker at gmail.com Fri Aug 1 14:17:13 2008 From: samflanker at gmail.com (sam) Date: Fri Aug 1 14:17:20 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: References: <489036A2.5060403@gmail.com> Message-ID: <48931AD1.1090609@gmail.com> Nate Eldredge wrote: > On Wed, 30 Jul 2008, sam wrote: > >> >> 0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 >> 1682 11 1 88 >> 0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 >> 1749 6 7 87 >> |-------------------------------------------------------------------- >> >> consolekit in |waitvt state, influencing on high volumes in procs-b > > I don't understand what the problem is. It looks like consolekit is > sleeping and not using any CPU. "waitvt" just indicates where in the > kernel it's sleeping. I don't understand what you mean by "high > volumes in procs-b". > How-To-Repeat: -------------------------------------------------------------- # (|cd /usr/ports/sysutils/consolekit/ && make install clean) # /usr/local/etc/rc.d/dbus forcestart # vmstat -w 1 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr ad0 in sy cs us sy id 2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 1 98 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 3 97 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 2 98 1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 3 97 ^C # /usr/local/sbin/console-kit-daemon && vmstat -w 1 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr ad0 in sy cs us sy id 2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 1 98 0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 2 4 94 0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 0 4 96 0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 0 3 97 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 0 3 97 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 0 3 97 ^C # |-------------------------------------------------------------- please, any solution ... | |/Vladimir Ermakov From kostikbel at gmail.com Fri Aug 1 14:31:33 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Fri Aug 1 14:31:40 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <48931AD1.1090609@gmail.com> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> Message-ID: <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: > Nate Eldredge wrote: > >On Wed, 30 Jul 2008, sam wrote: > > > >> > >>0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 > >>1682 11 1 88 > >>0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 > >>1749 6 7 87 > >>|-------------------------------------------------------------------- > >> > >>consolekit in |waitvt state, influencing on high volumes in procs-b > > > >I don't understand what the problem is. It looks like consolekit is > >sleeping and not using any CPU. "waitvt" just indicates where in the > >kernel it's sleeping. I don't understand what you mean by "high > >volumes in procs-b". > > > How-To-Repeat: > -------------------------------------------------------------- > # (|cd /usr/ports/sysutils/consolekit/ && make install clean) > > # /usr/local/etc/rc.d/dbus forcestart > > # vmstat -w 1 > procs memory page disk faults cpu > r b w avm fre flt re pi po fr sr ad0 in sy cs us > sy id > 2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 > 1 98 > 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 > 3 97 > 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 > 2 98 > 1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 > 3 97 > ^C > # /usr/local/sbin/console-kit-daemon && vmstat -w 1 > procs memory page disk faults cpu > r b w avm fre flt re pi po fr sr ad0 in sy cs us > sy id > 2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 > 1 98 > 0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 > 2 4 94 > 0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 > 0 4 96 > 0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 > 0 3 97 > 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 > 0 3 97 > 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 > 0 3 97 > ^C > # > |-------------------------------------------------------------- > > please, any solution ... Solution for what ? There is nothing wrong with the system. For the purely estetisk purpose, you may look up the line tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring from it. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080801/a82854c8/attachment.pgp From samflanker at gmail.com Fri Aug 1 14:38:31 2008 From: samflanker at gmail.com (sam) Date: Fri Aug 1 14:38:38 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> Message-ID: <48931FD5.1050604@gmail.com> Kostik Belousov wrote: > On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: > >> Nate Eldredge wrote: >> >>> On Wed, 30 Jul 2008, sam wrote: >>> >>> >>>> 0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 >>>> 1682 11 1 88 >>>> 0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 >>>> 1749 6 7 87 >>>> |-------------------------------------------------------------------- >>>> >>>> consolekit in |waitvt state, influencing on high volumes in procs-b >>>> >>> I don't understand what the problem is. It looks like consolekit is >>> sleeping and not using any CPU. "waitvt" just indicates where in the >>> kernel it's sleeping. I don't understand what you mean by "high >>> volumes in procs-b". >>> >>> >> How-To-Repeat: >> -------------------------------------------------------------- >> # (|cd /usr/ports/sysutils/consolekit/ && make install clean) >> >> # /usr/local/etc/rc.d/dbus forcestart >> >> # vmstat -w 1 >> procs memory page disk faults cpu >> r b w avm fre flt re pi po fr sr ad0 in sy cs us >> sy id >> 2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 >> 1 98 >> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 >> 3 97 >> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 >> 2 98 >> 1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 >> 3 97 >> ^C >> # /usr/local/sbin/console-kit-daemon && vmstat -w 1 >> procs memory page disk faults cpu >> r b w avm fre flt re pi po fr sr ad0 in sy cs us >> sy id >> 2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 >> 1 98 >> 0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 >> 2 4 94 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 >> 0 4 96 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 >> 0 3 97 >> 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 >> 0 3 97 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 >> 0 3 97 >> ^C >> # >> |-------------------------------------------------------------- >> >> please, any solution ... >> > > Solution for what ? There is nothing wrong with the system. > > For the purely estetisk purpose, you may look up the line > tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); > or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring > from it. > high volumes in proc-b - normal ? From kostikbel at gmail.com Fri Aug 1 15:04:38 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Fri Aug 1 15:04:45 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <48931FD5.1050604@gmail.com> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> <48931FD5.1050604@gmail.com> Message-ID: <20080801150433.GK97161@deviant.kiev.zoral.com.ua> On Fri, Aug 01, 2008 at 06:38:13PM +0400, sam wrote: > Kostik Belousov wrote: > >On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: > > > >>Nate Eldredge wrote: > >> > >>>On Wed, 30 Jul 2008, sam wrote: > >>> > >>> > >>>>0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 > >>>>1682 11 1 88 > >>>>0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 > >>>>1749 6 7 87 > >>>>|-------------------------------------------------------------------- > >>>> > >>>>consolekit in |waitvt state, influencing on high volumes in procs-b > >>>> > >>>I don't understand what the problem is. It looks like consolekit is > >>>sleeping and not using any CPU. "waitvt" just indicates where in the > >>>kernel it's sleeping. I don't understand what you mean by "high > >>>volumes in procs-b". > >>> > >>> > >>How-To-Repeat: > >>-------------------------------------------------------------- > >># (|cd /usr/ports/sysutils/consolekit/ && make install clean) > >> > >># /usr/local/etc/rc.d/dbus forcestart > >> > >># vmstat -w 1 > >>procs memory page disk faults cpu > >>r b w avm fre flt re pi po fr sr ad0 in sy cs us > >>sy id > >>2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 > >>1 98 > >>0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 > >>3 97 > >>0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 > >>2 98 > >>1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 > >>3 97 > >>^C > >># /usr/local/sbin/console-kit-daemon && vmstat -w 1 > >>procs memory page disk faults cpu > >>r b w avm fre flt re pi po fr sr ad0 in sy cs us > >>sy id > >>2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 > >>1 98 > >>0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 > >>2 4 94 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 > >>0 4 96 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 > >>0 3 97 > >>0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 > >>0 3 97 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 > >>0 3 97 > >>^C > >># > >>|-------------------------------------------------------------- > >> > >>please, any solution ... > >> > > > >Solution for what ? There is nothing wrong with the system. > > > >For the purely estetisk purpose, you may look up the line > > tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); > >or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring > >from it. > > > high volumes in proc-b - normal ? This is a counter of the processes sleeping with a priority less or equal to the PZERO. Each waitvt sleep is performed with the priority PZERO, and each process sleeping on waitvt counts in the "proc-b". -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080801/15e5e7ac/attachment.pgp From lulf at freebsd.org Fri Aug 1 21:33:36 2008 From: lulf at freebsd.org (Ulf Lilleengen) Date: Fri Aug 1 21:33:49 2008 Subject: [Call for testers] New cvsmode for csup patch Message-ID: <20080801213315.GA6002@nobby.studby.ntnu.no> Hello again, Even in these new subversion days, I'm not giving up :) Thanks for the feedback I got on the previous patches. It brought some issues with the patch that should now be fixed. It took some time, but I've been priotitizing other projects. However, here are a list of the changes: - Someone experienced segfaults when doing an update. This was because using wrong format specifier to proto_printf. - Some parts of the protocol was missing, such as support for the Z command, and supporting U in cvsmode. This is now implemented. - The rcsfile implementation would use huge amounts of memory when running diffs. Lately, it was easier to pinpoint where this happened due to huge diff chains, showing clearly where the memory was lost. This is now fixed, and csup seems to have a stable memory usage. Please report if you see otherwise. - Some simplifications and removal of code that is not needed. - Added an update of the usr.bin/csup Makefile. Thanks to kris@ for pointing this out. I hope all of you that tried the previous patch will try this one. Your previous feedback was valuable in finding out where I should look to fix these problems. Patches can be found for CURRENT: http://people.freebsd.org/~lulf/patches/csup/csup_2008-08-01_CURRENT.diff and 7-STABLE: http://people.freebsd.org/~lulf/patches/csup/csup_2008-08-01_RELENG_7.diff Any feedback welcome! -- Ulf Lilleengen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080801/fa0c5f02/attachment.pgp From pjd at FreeBSD.org Sun Aug 3 08:03:49 2008 From: pjd at FreeBSD.org (Pawel Jakub Dawidek) Date: Sun Aug 3 08:04:22 2008 Subject: Linker deadlock. Message-ID: <20080803073240.GC2371@garage.freebsd.pl> Hi. Linker can easly deadlock when we try to load the same kernel module from two processes at the same time. This is because we drop kld_sx in linker_load_file() and reacquire it, which leads to LOR, because we already held vnode lock at this point. Interesing backtraces below. First process: db> tr 3066 Tracing pid 3066 tid 100090 td 0x8514b240 sched_switch(8514b240,0,104,177,bb6bbb2e,...) at sched_switch+0x40e mi_switch(104,0,80681605,1ca,0,...) at mi_switch+0x200 sleepq_switch(8514b240,0,80681605,237,80a281ec,...) at sleepq_switch+0x14d sleepq_wait(80a281ec,0,8067a18b,3,0,...) at sleepq_wait+0x63 _sx_xlock_hard(80a281ec,8514b240,0,8067a1cf,1a0,...) at _sx_xlock_hard+0x2c6 _sx_xlock(80a281ec,0,8067a1cf,1a0,0,...) at _sx_xlock+0x99 linker_load_module(853a1264,0,83ba8940,83ba893c,83ba8938,...) at linker_load_module+0xa4a linker_load_dependencies(84fb8500,bb74,8539f000,2adc,156000,...) at linker_load_dependencies+0x194 link_elf_load_file(806b74e0,8557e4c0,83ba8c24,17c,0,...) at link_elf_load_file+0x4f0 linker_load_module(0,83ba8c4c,8067a1cf,3cd,280cb730,...) at linker_load_module+0x8db kern_kldload(8514b240,8592d400,83ba8c70,0,b395eb11,...) at kern_kldload+0xc8 [...] db> show lock 0x80a281ec class: sx name: kernel linker state: XLOCK: 0x8514bd80 (tid 100117, pid 3065, "zpool") waiters: exclusive Second process: db> tr 3065 Tracing pid 3065 tid 100117 td 0x8514bd80 sched_switch(8514bd80,0,104,177,bb7e358b,...) at sched_switch+0x40e mi_switch(104,0,80681605,1ca,50,...) at mi_switch+0x200 sleepq_switch(8514bd80,0,80681605,237,8523d9c0,...) at sleepq_switch+0x14d sleepq_wait(8523d9c0,50,806906bb,4,0,...) at sleepq_wait+0x63 __lockmgr_args(8523d9c0,80100,8523da28,0,0,...) at __lockmgr_args+0x9a5 vop_stdlock(83bd2660,8508aa80,2,80100,8523d968,...) at vop_stdlock+0x65 VOP_LOCK1_APV(806c3560,83bd2660,806d2ac0,8523d968,80100,...) at VOP_LOCK1_APV+0xa5 _vn_lock(8523d968,80100,8068815b,802,804c9cb4,...) at _vn_lock+0x5e vget(8523d968,80100,8514bd80,1b7,8065d00f,...) at vget+0xc9 cache_lookup(85090158,83bd2a00,83bd2a14,0,84f3b400,...) at cache_lookup+0x4c2 nfs_lookup(83bd2838,80688e43,806d2720,80000,85090158,...) at nfs_lookup+0x101 VOP_LOOKUP_APV(806c3560,83bd2838,8068783d,1bd,83bd2a00,...) at VOP_LOOKUP_APV+0xe5 lookup(83bd29e8,8068783d,e0,c0,8506e52c,...) at lookup+0x52e namei(83bd29e8,81159a38,80a352b4,4,8067be1f,...) at namei+0x48b vn_open_cred(83bd29e8,83bd2a4c,0,84f3b400,0,...) at vn_open_cred+0x2ba vn_open(83bd29e8,83bd2a4c,0,0,806b2a00,...) at vn_open+0x33 linker_lookup_file(3,0,3,8514bd80,0,...) at linker_lookup_file+0x163 linker_load_module(0,83bd2c4c,8067a1cf,3cd,280cb730,...) at linker_load_module+0x7bd kern_kldload(8514bd80,85a7e400,83bd2c70,0,b395eb11,...) at kern_kldload+0xc8 [...] db> show vnode 0x8523d968 vnode 0x8523d968: tag nfs, type VREG usecount 1, writecount 0, refcount 189 mountedhere 0 flags () v_object 0x852489b0 ref 0 pages 372 lock type nfs: EXCL by thread 0x8514b240 (pid 3066) with exclusive waiters pending #0 0x804c2e5d at __lockmgr_args+0xa6d #1 0x80546c85 at vop_stdlock+0x65 #2 0x8065dcd5 at VOP_LOCK1_APV+0xa5 #3 0x805627ee at _vn_lock+0x5e #4 0x80557419 at vget+0xc9 #5 0x805444b2 at cache_lookup+0x4c2 #6 0x805c3b51 at nfs_lookup+0x101 #7 0x8065ee65 at VOP_LOOKUP_APV+0xe5 #8 0x8054a9be at lookup+0x52e #9 0x8054b5eb at namei+0x48b #10 0x805621da at vn_open_cred+0x2ba #11 0x80562463 at vn_open+0x33 #12 0x804f45e8 at link_elf_load_file+0x68 #13 0x804c0f9b at linker_load_module+0x8db #14 0x804c1568 at kern_kldload+0xc8 #15 0x804c1624 at kldload+0x74 #16 0x80650513 at syscall+0x283 #17 0x80634e40 at Xint0x80_syscall+0x20 [...] -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080803/e69f6de3/attachment.pgp From kostikbel at gmail.com Sun Aug 3 11:30:08 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Sun Aug 3 11:30:14 2008 Subject: Linker deadlock. In-Reply-To: <20080803073240.GC2371@garage.freebsd.pl> References: <20080803073240.GC2371@garage.freebsd.pl> Message-ID: <20080803110925.GR97161@deviant.kiev.zoral.com.ua> On Sun, Aug 03, 2008 at 09:32:40AM +0200, Pawel Jakub Dawidek wrote: > Hi. > > Linker can easly deadlock when we try to load the same kernel module > from two processes at the same time. This is because we drop kld_sx in > linker_load_file() and reacquire it, which leads to LOR, because we > already held vnode lock at this point. Interesing backtraces below. > > First process: > > db> tr 3066 > Tracing pid 3066 tid 100090 td 0x8514b240 > sched_switch(8514b240,0,104,177,bb6bbb2e,...) at sched_switch+0x40e > mi_switch(104,0,80681605,1ca,0,...) at mi_switch+0x200 > sleepq_switch(8514b240,0,80681605,237,80a281ec,...) at sleepq_switch+0x14d > sleepq_wait(80a281ec,0,8067a18b,3,0,...) at sleepq_wait+0x63 > _sx_xlock_hard(80a281ec,8514b240,0,8067a1cf,1a0,...) at _sx_xlock_hard+0x2c6 > _sx_xlock(80a281ec,0,8067a1cf,1a0,0,...) at _sx_xlock+0x99 > linker_load_module(853a1264,0,83ba8940,83ba893c,83ba8938,...) at linker_load_module+0xa4a > linker_load_dependencies(84fb8500,bb74,8539f000,2adc,156000,...) at linker_load_dependencies+0x194 > link_elf_load_file(806b74e0,8557e4c0,83ba8c24,17c,0,...) at link_elf_load_file+0x4f0 > linker_load_module(0,83ba8c4c,8067a1cf,3cd,280cb730,...) at linker_load_module+0x8db > kern_kldload(8514b240,8592d400,83ba8c70,0,b395eb11,...) at kern_kldload+0xc8 > [...] > db> show lock 0x80a281ec > class: sx > name: kernel linker > state: XLOCK: 0x8514bd80 (tid 100117, pid 3065, "zpool") > waiters: exclusive > > Second process: > > db> tr 3065 > Tracing pid 3065 tid 100117 td 0x8514bd80 > sched_switch(8514bd80,0,104,177,bb7e358b,...) at sched_switch+0x40e > mi_switch(104,0,80681605,1ca,50,...) at mi_switch+0x200 > sleepq_switch(8514bd80,0,80681605,237,8523d9c0,...) at sleepq_switch+0x14d > sleepq_wait(8523d9c0,50,806906bb,4,0,...) at sleepq_wait+0x63 > __lockmgr_args(8523d9c0,80100,8523da28,0,0,...) at __lockmgr_args+0x9a5 > vop_stdlock(83bd2660,8508aa80,2,80100,8523d968,...) at vop_stdlock+0x65 > VOP_LOCK1_APV(806c3560,83bd2660,806d2ac0,8523d968,80100,...) at VOP_LOCK1_APV+0xa5 > _vn_lock(8523d968,80100,8068815b,802,804c9cb4,...) at _vn_lock+0x5e > vget(8523d968,80100,8514bd80,1b7,8065d00f,...) at vget+0xc9 > cache_lookup(85090158,83bd2a00,83bd2a14,0,84f3b400,...) at cache_lookup+0x4c2 > nfs_lookup(83bd2838,80688e43,806d2720,80000,85090158,...) at nfs_lookup+0x101 > VOP_LOOKUP_APV(806c3560,83bd2838,8068783d,1bd,83bd2a00,...) at VOP_LOOKUP_APV+0xe5 > lookup(83bd29e8,8068783d,e0,c0,8506e52c,...) at lookup+0x52e > namei(83bd29e8,81159a38,80a352b4,4,8067be1f,...) at namei+0x48b > vn_open_cred(83bd29e8,83bd2a4c,0,84f3b400,0,...) at vn_open_cred+0x2ba > vn_open(83bd29e8,83bd2a4c,0,0,806b2a00,...) at vn_open+0x33 > linker_lookup_file(3,0,3,8514bd80,0,...) at linker_lookup_file+0x163 > linker_load_module(0,83bd2c4c,8067a1cf,3cd,280cb730,...) at linker_load_module+0x7bd > kern_kldload(8514bd80,85a7e400,83bd2c70,0,b395eb11,...) at kern_kldload+0xc8 > [...] > db> show vnode 0x8523d968 > vnode 0x8523d968: tag nfs, type VREG > usecount 1, writecount 0, refcount 189 mountedhere 0 > flags () > v_object 0x852489b0 ref 0 pages 372 > lock type nfs: EXCL by thread 0x8514b240 (pid 3066) > with exclusive waiters pending > #0 0x804c2e5d at __lockmgr_args+0xa6d > #1 0x80546c85 at vop_stdlock+0x65 > #2 0x8065dcd5 at VOP_LOCK1_APV+0xa5 > #3 0x805627ee at _vn_lock+0x5e > #4 0x80557419 at vget+0xc9 > #5 0x805444b2 at cache_lookup+0x4c2 > #6 0x805c3b51 at nfs_lookup+0x101 > #7 0x8065ee65 at VOP_LOOKUP_APV+0xe5 > #8 0x8054a9be at lookup+0x52e > #9 0x8054b5eb at namei+0x48b > #10 0x805621da at vn_open_cred+0x2ba > #11 0x80562463 at vn_open+0x33 > #12 0x804f45e8 at link_elf_load_file+0x68 > #13 0x804c0f9b at linker_load_module+0x8db > #14 0x804c1568 at kern_kldload+0xc8 > #15 0x804c1624 at kldload+0x74 > #16 0x80650513 at syscall+0x283 > #17 0x80634e40 at Xint0x80_syscall+0x20 > [...] Source line backtraces would be nicer, since gcc inliner forces me to make a guess. It seems that linker_load_module() calls linker_load_file() that drops and reaquires the linker lock. Then, it seems that dropping the module' vnode lock around the call to linker_load_dependencies() should help. diff --git a/sys/kern/link_elf.c b/sys/kern/link_elf.c index 2664ba9..52b3f8f 100644 --- a/sys/kern/link_elf.c +++ b/sys/kern/link_elf.c @@ -802,7 +802,9 @@ link_elf_load_file(linker_class_t cls, const char* filename, goto out; link_elf_reloc_local(lf); + VOP_UNLOCK(nd.ni_vp, 0); error = linker_load_dependencies(lf); + vn_lock(nd.ni_vp, LK_EXCLUSIVE | LK_RETRY); if (error) goto out; #if 0 /* this will be more trouble than it's worth for now */ diff --git a/sys/kern/link_elf_obj.c b/sys/kern/link_elf_obj.c index d8e9219..657dd0e 100644 --- a/sys/kern/link_elf_obj.c +++ b/sys/kern/link_elf_obj.c @@ -798,7 +798,9 @@ link_elf_load_file(linker_class_t cls, const char *filename, link_elf_reloc_local(lf); /* Pull in dependencies */ + VOP_UNLOCK(nd.ni_vp); error = linker_load_dependencies(lf); + vn_lock(nd.ni_vp, LK_EXCLUSIVE | LK_RETRY); if (error) goto out; -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080803/5b7e8db9/attachment.pgp From pjd at FreeBSD.org Sun Aug 3 11:35:59 2008 From: pjd at FreeBSD.org (Pawel Jakub Dawidek) Date: Sun Aug 3 11:36:06 2008 Subject: Linker deadlock. In-Reply-To: <20080803110925.GR97161@deviant.kiev.zoral.com.ua> References: <20080803073240.GC2371@garage.freebsd.pl> <20080803110925.GR97161@deviant.kiev.zoral.com.ua> Message-ID: <20080803113555.GD2371@garage.freebsd.pl> On Sun, Aug 03, 2008 at 02:09:26PM +0300, Kostik Belousov wrote: > Source line backtraces would be nicer, since gcc inliner forces me to make > a guess. It seems that linker_load_module() calls linker_load_file() > that drops and reaquires the linker lock. > > Then, it seems that dropping the module' vnode lock around the call to > linker_load_dependencies() should help. Yes, it doesn't deadlock now, thanks! > diff --git a/sys/kern/link_elf.c b/sys/kern/link_elf.c > index 2664ba9..52b3f8f 100644 > --- a/sys/kern/link_elf.c > +++ b/sys/kern/link_elf.c > @@ -802,7 +802,9 @@ link_elf_load_file(linker_class_t cls, const char* filename, > goto out; > link_elf_reloc_local(lf); > > + VOP_UNLOCK(nd.ni_vp, 0); > error = linker_load_dependencies(lf); > + vn_lock(nd.ni_vp, LK_EXCLUSIVE | LK_RETRY); > if (error) > goto out; > #if 0 /* this will be more trouble than it's worth for now */ > diff --git a/sys/kern/link_elf_obj.c b/sys/kern/link_elf_obj.c > index d8e9219..657dd0e 100644 > --- a/sys/kern/link_elf_obj.c > +++ b/sys/kern/link_elf_obj.c > @@ -798,7 +798,9 @@ link_elf_load_file(linker_class_t cls, const char *filename, > link_elf_reloc_local(lf); > > /* Pull in dependencies */ > + VOP_UNLOCK(nd.ni_vp); > error = linker_load_dependencies(lf); > + vn_lock(nd.ni_vp, LK_EXCLUSIVE | LK_RETRY); > if (error) > goto out; -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080803/def74d03/attachment.pgp From gaijin.k at gmail.com Sun Aug 3 15:10:43 2008 From: gaijin.k at gmail.com (Alexandre "Sunny" Kovalenko) Date: Sun Aug 3 16:22:31 2008 Subject: Laptop suggestions? In-Reply-To: References: <1216910072.2251.8.camel@jill.exit.com> <86y73j341e.fsf@ds4.des.no> <86bq0ftjf6.fsf@ds4.des.no> <8C2BF4B9-14CD-40EA-B22E-DBB7060BFE46@bnc.net> Message-ID: <1217776229.953.11.camel@RabbitsDen> On Wed, 2008-07-30 at 21:45 -0300, Carlos A. M. dos Santos wrote: > On Wed, Jul 30, 2008 at 5:20 PM, Achim Patzner wrote: > > Am 30.07.2008 um 18:40 schrieb Dag-Erling Sm?rgrav: > >> > >> I don't understand what Macs have to do with this - we're talking about > >> iX Systems's made-for-BSD laptop. > > > > The thread started with someone asking for a mobile computer that > > would support FreeBSD sufficiently and nobody came up with something > > fitting the bill (and being available somewhere). Considering the > > picture you're seeing at any place where more than two hardcore Unix > > users assemble you're seeing a majority of Macs. There has to be an > > obvious reason for that... I tried to break that habit more than once > > but right now the only comfortable way of running FreeBSD on a laptop > > is VMware Fusion on a Mac. Reading this entire thread convinced me > > even more. > > Please define "comfortable". I've been running FreeBSD 7.0 pretty > comfortably on my HP nx6320 for several months now. I never attempted > to use neither Bluetooth nor the fingerprint reader, so I don't miss I am sure this is not intentional, but a lot of the responses in this thread mention not using Bluetooth. If only to make sure that people are not led to believe that Bluetooth support in FreeBSD is lacking, I would like to mention that I have been using it for a long while with Apple Keyboard (something Windows incarnation of the same laptop is not capable of), Logitech V570(?) mouse, Palms E2 and TX (former NAT'd out to the network through FreeBSD host) and the string of Motorola phones for moving pictures, sounds and Java applications back and forth using OBEX. And, just to throw out some other definition of the "comfortable" -- I find my ThinkPad X61 (12" diagonally, 4.5lbs) much more comfortable to carry around than my iBook G4 or the smallest of the MacBooks being sold today. I guess, "comfortable" is on the lap of the beholder ;) -- Alexandre "Sunny" Kovalenko (????????? ?????????) From rink at FreeBSD.org Sun Aug 3 16:27:08 2008 From: rink at FreeBSD.org (Rink Springer) Date: Sun Aug 3 16:27:15 2008 Subject: Patch for working AMD Geode CS5530 audio driver on HEAD Message-ID: <20080803161057.GB35301@rink.nu> Hi, As outlined in http://lists.freebsd.org/pipermail/freebsd-hackers/2008-January/022986.html, Alec had some problems with the snd_geode driver. While I cannot test whether it works using Geode CS5536 hardware, I've managed to get the driver to work using CS5530 hardware on FreeBSD HEAD. The patch is available at http://people.freebsd.org/~rink/various/ns_geode.diff - using this, my Compaq Evo T30 flawlessly plays MP3's. The problem was that the busdma tag allocation specifies a maximum allocation size of 65536 bytes, yet it had to do so using 1 segment of at most 65535 bytes (note: 1 byte less). Since the channel code tries to allocate 65536 bytes, this didn't work [1]; yet, the return code check was messages up (sndbuf_alloc() returns 0 on success, not -1 on failure) which caused page faults later on. I am interested in integrating this work in HEAD; however, if Alec and/or Bruce could try, see and hack away to make it work on the CS5536 (or are willing to ship me a system ;-), that'd be great. [1] Thanks to Scott Long for pointing me towards the right direction. Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From brucem at mail.cruzio.com Mon Aug 4 03:46:49 2008 From: brucem at mail.cruzio.com (Bruce R. Montague) Date: Mon Aug 4 03:46:55 2008 Subject: Patch for working AMD Geode CS5530 audio driver on HEAD Message-ID: <200808040327.m743R03p000357@mail.cruzio.com> Hi, Rink. re: > The patch is available at > http://people.freebsd.org/~rink/various/ns_geode.diff Sounds great! (ok awful pun.) > I am interested in integrating this work in HEAD ... My FreeBSD development environment has been down for a few years and, despite optimistic hopes, due to day job and real life, cough, I won't be able to do anything with this driver till mid-September (if then). So as far as I am concerned, anyone who wanted to take this driver and run with it, well, that would be great. (in particular as I seem to be suffering from infinitly receeding deadline syndrome.) I know Andrew Grey (ancelgray at yahoo.com) was starting to hack on the CS5536 stuff... -bruce From guru at unixarea.de Tue Aug 5 08:05:24 2008 From: guru at unixarea.de (Matthias Apitz) Date: Tue Aug 5 08:05:31 2008 Subject: Fwd: Q: case studies about scalable, enterprise-class firewall w/ IPFilter Message-ID: <20080805080520.GB3063@rebelion.Sisis.de> Hello, I've posted the attached mail in the IP Filter mailing list; the only responses have been bad configured vacation replies :-( someone from freebsd-hackers has an idea? thanks in advance matthias ----- Forwarded message from Matthias Apitz ----- From: Matthias Apitz Date: Sun, 3 Aug 2008 08:24:15 +0200 To: IP Filter Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter Hello, We're currently protecting our network (and as well some FreeBSD laptops standalone) with IPFilter... I'm wondering if there are any case studies about scalable, enterprise-class firewall solutions, redundancy with state-full failover, and application-level inspection, and all that a like, based on IPFilter and FreeBSD; thanks in advance for any pointers matthias -- Matthias Apitz w http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. ----- End forwarded message ----- From ady at freebsd.ady.ro Tue Aug 5 09:19:10 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 5 09:19:17 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <20080805080520.GB3063@rebelion.Sisis.de> References: <20080805080520.GB3063@rebelion.Sisis.de> Message-ID: <78cb3d3f0808050219k94105adxd114012634989b31@mail.gmail.com> Hi, On Tue, Aug 5, 2008 at 10:05 AM, Matthias Apitz wrote: > > Hello, > > I've posted the attached mail in the IP Filter mailing list; the only > responses have been bad configured vacation replies :-( > > someone from freebsd-hackers has an idea? thanks in advance > > matthias > > ----- Forwarded message from Matthias Apitz ----- > > From: Matthias Apitz > Date: Sun, 3 Aug 2008 08:24:15 +0200 > To: IP Filter > Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter > > > Hello, > > We're currently protecting our network (and as well some FreeBSD laptops > standalone) with IPFilter... I'm wondering if there are any case studies > about scalable, enterprise-class firewall solutions, redundancy with > state-full failover, and application-level inspection, and all that a > like, based on IPFilter and FreeBSD; Hmm, none that I know of, but I would be interested to (get) involved in such a project (on behalf of the emerging EntepriseBSD project and/or business consulting). I have been working with IPFilter in the past, even built a pretty complex setup for the university where I've been studying (might be still running) with statefull tables (kept across reboots) and the associated scaling problems. Besides sporadic issues (with lost sessions due to overflowing the session tables until I fine-tuned the IPF state timeouts) it was quite a success. Nowadays I believe the trend is to use pf(4) instead of ipf(4) as it offers quite the same functionality under a presumably better license (although I sometimes miss the hierarchical structuring available through group/head in IPFilter). Let me know if I can be of help. Regards, Adrian Penisoara EnterpriseBSD project / ROFUG Ady (@enterprisebsd.info, @bsdconsultants.com) From tim at clewlow.org Tue Aug 5 09:26:41 2008 From: tim at clewlow.org (Tim Clewlow) Date: Tue Aug 5 09:26:48 2008 Subject: Fwd: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <20080805080520.GB3063@rebelion.Sisis.de> References: <20080805080520.GB3063@rebelion.Sisis.de> Message-ID: <53720.192.168.1.10.1217928398.squirrel@192.168.1.100> > > Hello, > > I've posted the attached mail in the IP Filter mailing list; the > only > responses have been bad configured vacation replies :-( > > someone from freebsd-hackers has an idea? thanks in advance > > matthias > > ----- Forwarded message from Matthias Apitz ----- > > From: Matthias Apitz > Date: Sun, 3 Aug 2008 08:24:15 +0200 > To: IP Filter > Subject: Q: case studies about scalable, enterprise-class firewall > w/ IPFilter > > > Hello, > > We're currently protecting our network (and as well some FreeBSD > laptops > standalone) with IPFilter... I'm wondering if there are any case > studies > about scalable, enterprise-class firewall solutions, redundancy with > state-full failover, and application-level inspection, and all that > a > like, based on IPFilter and FreeBSD; > > thanks in advance for any pointers > > matthias > -- Hi there, I have never used ipfilter, but I do use pf, and it can do state-full failover, or firewall redundancy, with CARP (the Common Address Redundancy Protocol) and pfsync. If there is an equivalent syncing program, eg ipfiltersync then you could use that with CARP to allow an ipfilter firewall to fail-over with full state tables intact. Also, you can inspect all manner of status info and tables for a running firewall with pfctl, there must be an equivalent for ipfilter. If you are looking for general info about building a firewall, eg tcp and ip headers, plus icmp and voip and other protocols, then I would recommend the following tutorial, it has a huge amount of information - it is a lot more than just a tutorial on iptables. http://iptables-tutorial.frozentux.net/iptables-tutorial.html Lastly, the "OpenBSD PF Packet Filter Book" has been very useful for me, but I use pf where possible - I think it is the easiest, and paradoxically the most powerful of all packet filters, but that is my personal opinion, YMMV. Cheers, Tim. From guru at unixarea.de Tue Aug 5 09:40:18 2008 From: guru at unixarea.de (Matthias Apitz) Date: Tue Aug 5 09:40:25 2008 Subject: restore of file system into USB key terrible slow Message-ID: <20080805094013.GA5654@rebelion.Sisis.de> Hello, I'm trying to restore a DUMP into an USB key; the DUMP was extracted from another USB key which I just want to colne this way; the USB key type is: Aug 5 10:53:34 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 5 10:53:34 rebelion kernel: da0: < Cn Memory 1100> Removable Direct Access SCSI-0 device Aug 5 10:53:34 rebelion kernel: da0: 40.000MB/s transfers Aug 5 10:53:34 rebelion kernel: da0: 3871MB (7928832 512 byte sectors: 255H 63S/T 493C) and I've created a partition (only one covering the full ~4 GByte) and a file system as: # newfs -m 0 -o space /dev/da0s1a /dev/da0s1a: 3867.2MB (7919964 sectors) block size 16384, fragment size 2048 using 22 cylinder groups of 183.77MB, 11761 blks, 23552 inodes. super-block backups (for fsck -b #) at: 160, 376512, 752864, 1129216, 1505568, 1881920, 2258272, 2634624, 3010976, 3387328, 3763680, 4140032, 4516384, 4892736, 5269088, 5645440, 6021792, 6398144, 6774496, 7150848, 7527200, 7903552 # mount /dev/da0s1a /mnt # cd /mnt # restore -rv -f /home/guru/myThings/FreeBSD/tinyUsb.dmp Verify tape and initialize maps Tape block size is 32 Header with wrong dumpdate. Dump date: Tue Aug 5 09:50:36 2008 Dumped from: the epoch Level 0 dump of /mnt on rebelion.Sisis.de:/dev/da0s1a Label: none Begin level 0 restore Initialize symbol table. Extract directories from tape Calculate extraction list. warning: ./.snap: File exists Make node ./var Make node ./var/account Make node ./var/at Make node ./var/at/jobs Make node ./var/at/spool Make node ./var/audit the restore is *terrible* slow, aound 200 blocks per second: $ df -k /mnt ; sleep 60 ; df -k /mnt Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0s1a 3829660 454 3829206 0% /mnt Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0s1a 3829660 642 3829018 0% /mnt Am I doing something wrong? What means 'Header with wrong dumpdate'? matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From ken at mthelicon.com Tue Aug 5 09:44:40 2008 From: ken at mthelicon.com (Pegasus Mc Cleaft) Date: Tue Aug 5 09:44:46 2008 Subject: IPv6 CVS Message-ID: <000301c8f6df$e1006ae0$a30140a0$@com> Hi all, Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As in receiving the STABLE and ports branches) I currently use cvs.freebsd.org but it dosent have an AAAA record. Ta Peg From tim at clewlow.org Tue Aug 5 09:52:32 2008 From: tim at clewlow.org (Tim Clewlow) Date: Tue Aug 5 09:52:39 2008 Subject: IPv6 CVS In-Reply-To: <000301c8f6df$e1006ae0$a30140a0$@com> References: <000301c8f6df$e1006ae0$a30140a0$@com> Message-ID: <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> > Hi all, > > Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As > in > receiving the STABLE and ports branches) I currently use > cvs.freebsd.org but > it dosent have an AAAA record. > > Ta > > Peg > dig aaaa cvsup4.freebsd.org ; <<>> DiG 9.4.2 <<>> aaaa cvsup4.freebsd.org ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34684 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 6, ADDITIONAL: 0 ;; QUESTION SECTION: ;cvsup4.freebsd.org. IN AAAA ;; ANSWER SECTION: cvsup4.freebsd.org. 3600 IN CNAME freebsd.isc.org. freebsd.isc.org. 3600 IN AAAA 2001:4f8:0:2::e From max at love2party.net Tue Aug 5 10:06:13 2008 From: max at love2party.net (Max Laier) Date: Tue Aug 5 10:06:20 2008 Subject: Fwd: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <20080805080520.GB3063@rebelion.Sisis.de> References: <20080805080520.GB3063@rebelion.Sisis.de> Message-ID: <200808051206.10938.max@love2party.net> Hello Matthias, On Tuesday 05 August 2008 10:05:20 Matthias Apitz wrote: > We're currently protecting our network (and as well some FreeBSD laptops > standalone) with IPFilter... I'm wondering if there are any case studies > about scalable, enterprise-class firewall solutions, redundancy with > state-full failover, and application-level inspection, and all that a > like, based on IPFilter and FreeBSD; > > thanks in advance for any pointers if IPFilter isn't the primary selection criteria, you might want to take a look at www.pfsense.org. Application-level inspection is just in the making, but all your other feature requests get a check mark. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From maxim at macomnet.ru Tue Aug 5 10:43:36 2008 From: maxim at macomnet.ru (Maxim Konovalov) Date: Tue Aug 5 10:43:43 2008 Subject: IPv6 CVS In-Reply-To: <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> Message-ID: <20080805141450.T60740@mp2.macomnet.net> On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > Hi all, > > > > Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As > > in > > receiving the STABLE and ports branches) I currently use > > cvs.freebsd.org but > > it dosent have an AAAA record. > > > > Ta > > > > Peg > > > dig aaaa cvsup4.freebsd.org > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 address as well. -- Maxim Konovalov From stsp at stsp.name Tue Aug 5 10:51:08 2008 From: stsp at stsp.name (Stefan Sperling) Date: Tue Aug 5 10:51:16 2008 Subject: IPv6 CVS In-Reply-To: <20080805141450.T60740@mp2.macomnet.net> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> Message-ID: <20080805105057.GC1450@ted.stsp.name> On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: > On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > > > > Hi all, > > > > > > Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As > > > in > > > receiving the STABLE and ports branches) I currently use > > > cvs.freebsd.org but > > > it dosent have an AAAA record. > > > > > > Ta > > > > > > Peg > > > > > dig aaaa cvsup4.freebsd.org > > > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 > address as well. AFAIK the Modula3 runtime does not support IPv6. Stefan From ken at mthelicon.com Tue Aug 5 11:04:49 2008 From: ken at mthelicon.com (Pegasus Mc Cleaft) Date: Tue Aug 5 11:04:56 2008 Subject: IPv6 CVS In-Reply-To: <20080805105057.GC1450@ted.stsp.name> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> Message-ID: <000801c8f6eb$111622f0$334268d0$@com> > -----Original Message----- > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > hackers@freebsd.org] On Behalf Of Stefan Sperling > Sent: 05 August 2008 11:51 > To: Maxim Konovalov > Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow > Subject: Re: IPv6 CVS > > On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: > > On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > > > > > > > Hi all, > > > > > > > > Does anyone know if there are any IPv6 CVS servers for FreeBSD? > (As > > > > in > > > > receiving the STABLE and ports branches) I currently use > > > > cvs.freebsd.org but > > > > it dosent have an AAAA record. > > > > > > > > Ta > > > > > > > > Peg > > > > > > > dig aaaa cvsup4.freebsd.org > > > > > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 > > address as well. > > AFAIK the Modula3 runtime does not support IPv6. > > Stefan Thanks everyone, Looks like Tim is correct where I am able to ping cvsup4, but unfortunately the csup utility reports a fail (Connection Refused) as it tries to connect to the V6 address. It will quite happily connect to the same machine V4. Stefan's explanation may be the reason for this.. Dono.. Peg From m.seaman at infracaninophile.co.uk Tue Aug 5 11:11:36 2008 From: m.seaman at infracaninophile.co.uk (Matthew Seaman) Date: Tue Aug 5 11:11:42 2008 Subject: IPv6 CVS In-Reply-To: <20080805105057.GC1450@ted.stsp.name> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> Message-ID: <48983554.7060203@infracaninophile.co.uk> Stefan Sperling wrote: > On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: >> On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: >> >>>> Hi all, >>>> >>>> Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As >>>> in >>>> receiving the STABLE and ports branches) I currently use >>>> cvs.freebsd.org but >>>> it dosent have an AAAA record. >>>> >>>> Ta >>>> >>>> Peg >>>> dig aaaa cvsup4.freebsd.org >> cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 >> address as well. > > AFAIK the Modula3 runtime does not support IPv6. Yeah, you have to use an IPv6 to IPv4 proxy like stone. (ports: net/stone, http://www.gcd.org/sengoku/stone/) Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080805/56295da0/signature.pgp From koitsu at FreeBSD.org Tue Aug 5 12:28:18 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Tue Aug 5 12:28:25 2008 Subject: IPv6 CVS In-Reply-To: <000801c8f6eb$111622f0$334268d0$@com> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> <000801c8f6eb$111622f0$334268d0$@com> Message-ID: <20080805122817.GA89022@eos.sc1.parodius.com> On Tue, Aug 05, 2008 at 12:04:33PM +0100, Pegasus Mc Cleaft wrote: > > -----Original Message----- > > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > > hackers@freebsd.org] On Behalf Of Stefan Sperling > > Sent: 05 August 2008 11:51 > > To: Maxim Konovalov > > Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow > > Subject: Re: IPv6 CVS > > > > On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: > > > On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > > > > > > > > > > Hi all, > > > > > > > > > > Does anyone know if there are any IPv6 CVS servers for FreeBSD? > > (As > > > > > in > > > > > receiving the STABLE and ports branches) I currently use > > > > > cvs.freebsd.org but > > > > > it dosent have an AAAA record. > > > > > > > > > > Ta > > > > > > > > > > Peg > > > > > > > > > dig aaaa cvsup4.freebsd.org > > > > > > > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 > > > address as well. > > > > AFAIK the Modula3 runtime does not support IPv6. > > > > Stefan > > Thanks everyone, > > Looks like Tim is correct where I am able to ping cvsup4, but > unfortunately the csup utility reports a fail (Connection Refused) as it > tries to connect to the V6 address. It will quite happily connect to the > same machine V4. csup is written in C; it does not use Modula3/ezm3. cvsup uses Modula3/ezm3. cvsup4, despite having a public IPv6 address, does not have the cvsup server bound to IPv6. Meaning: it's IPV4 only. Try a different server. Get a list (in sh/bash): for i in `jot 30 1`; do echo "==> cvsup$i" ; (host cvsup$i.freebsd.org) | grep -i ipv6; done -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From guru at unixarea.de Tue Aug 5 12:35:37 2008 From: guru at unixarea.de (Matthias Apitz) Date: Tue Aug 5 12:35:46 2008 Subject: restore of file system into USB key terrible slow In-Reply-To: <20080805094013.GA5654@rebelion.Sisis.de> References: <20080805094013.GA5654@rebelion.Sisis.de> Message-ID: <20080805123533.GA3262@rebelion.Sisis.de> El d?a Tuesday, August 05, 2008 a las 11:40:13AM +0200, Matthias Apitz escribi?: > > Hello, > > I'm trying to restore a DUMP into an USB key; the DUMP was extracted > from another USB key which I just want to colne this way; > > the USB key type is: > > Aug 5 10:53:34 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Aug 5 10:53:34 rebelion kernel: da0: < Cn Memory 1100> Removable Direct Access SCSI-0 device > Aug 5 10:53:34 rebelion kernel: da0: 40.000MB/s transfers > Aug 5 10:53:34 rebelion kernel: da0: 3871MB (7928832 512 byte sectors: 255H 63S/T 493C) > ... > > the restore is *terrible* slow, aound 200 blocks per second: This must have been an issue of the USB key; I've plug'ed in another one: Aug 5 13:53:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 5 13:53:12 rebelion kernel: da0: Removable Direct Access SCSI-2 device Aug 5 13:53:12 rebelion kernel: da0: 40.000MB/s transfers Aug 5 13:53:12 rebelion kernel: da0: 2037MB (4171776 512 byte sectors: 255H 63S/T 259C) and the restore of about 600 MByte was done in half hour; sorry for bother the list with this; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From ken at mthelicon.com Tue Aug 5 12:40:27 2008 From: ken at mthelicon.com (Pegasus Mc Cleaft) Date: Tue Aug 5 12:40:34 2008 Subject: IPv6 CVS In-Reply-To: <20080805122817.GA89022@eos.sc1.parodius.com> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> <000801c8f6eb$111622f0$334268d0$@com> <20080805122817.GA89022@eos.sc1.parodius.com> Message-ID: <002501c8f6f8$6c1e5a70$445b0f50$@com> > -----Original Message----- > From: Jeremy Chadwick [mailto:koitsu@FreeBSD.org] > Sent: 05 August 2008 13:28 > To: Pegasus Mc Cleaft > Cc: 'Stefan Sperling'; 'Maxim Konovalov'; freebsd-hackers@FreeBSD.org; > 'Tim Clewlow' > Subject: Re: IPv6 CVS > > On Tue, Aug 05, 2008 at 12:04:33PM +0100, Pegasus Mc Cleaft wrote: > > > -----Original Message----- > > > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > > > hackers@freebsd.org] On Behalf Of Stefan Sperling > > > Sent: 05 August 2008 11:51 > > > To: Maxim Konovalov > > > Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow > > > Subject: Re: IPv6 CVS > > > > > > On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: > > > > On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > Does anyone know if there are any IPv6 CVS servers for > FreeBSD? > > > (As > > > > > > in > > > > > > receiving the STABLE and ports branches) I currently use > > > > > > cvs.freebsd.org but > > > > > > it dosent have an AAAA record. > > > > > > > > > > > > Ta > > > > > > > > > > > > Peg > > > > > > > > > > > dig aaaa cvsup4.freebsd.org > > > > > > > > > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an > ipv6 > > > > address as well. > > > > > > AFAIK the Modula3 runtime does not support IPv6. > > > > > > Stefan > > > > Thanks everyone, > > > > Looks like Tim is correct where I am able to ping cvsup4, but > > unfortunately the csup utility reports a fail (Connection Refused) as > it > > tries to connect to the V6 address. It will quite happily connect to > the > > same machine V4. > > csup is written in C; it does not use Modula3/ezm3. cvsup uses > Modula3/ezm3. > > cvsup4, despite having a public IPv6 address, does not have the cvsup > server bound to IPv6. Meaning: it's IPV4 only. > > Try a different server. Get a list (in sh/bash): > > for i in `jot 30 1`; do echo "==> cvsup$i" ; (host cvsup$i.freebsd.org) > | grep -i ipv6; done > Jeremy, AH HA! Ok.. Thanks for the bash script. I tried it and ran through all the servers... The only server that seems to have cvsup bound to the V6 stack is cvsup18.freebsd.org (raines.cse.buffalo.edu) That helps a lot. Thank you very much.. Peg From aduane at juniper.net Tue Aug 5 14:03:08 2008 From: aduane at juniper.net (Andrew Duane) Date: Tue Aug 5 14:03:30 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter References: <20080805080520.GB3063@rebelion.Sisis.de> Message-ID: <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> Well, there are always Juniper Networks boxes :-) -----Original Message----- From: owner-freebsd-hackers@freebsd.org on behalf of Matthias Apitz Sent: Tue 8/5/2008 4:05 AM To: freebsd-hackers@freebsd.org Subject: Fwd: Q: case studies about scalable,enterprise-class firewall w/ IPFilter Hello, I've posted the attached mail in the IP Filter mailing list; the only responses have been bad configured vacation replies :-( someone from freebsd-hackers has an idea? thanks in advance matthias ----- Forwarded message from Matthias Apitz ----- From: Matthias Apitz Date: Sun, 3 Aug 2008 08:24:15 +0200 To: IP Filter Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter Hello, We're currently protecting our network (and as well some FreeBSD laptops standalone) with IPFilter... I'm wondering if there are any case studies about scalable, enterprise-class firewall solutions, redundancy with state-full failover, and application-level inspection, and all that a like, based on IPFilter and FreeBSD; thanks in advance for any pointers matthias -- Matthias Apitz w http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. ----- End forwarded message ----- _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From guru at unixarea.de Tue Aug 5 14:36:00 2008 From: guru at unixarea.de (Matthias Apitz) Date: Tue Aug 5 14:36:07 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> References: <20080805080520.GB3063@rebelion.Sisis.de> <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> Message-ID: <20080805143556.GB6526@rebelion.Sisis.de> El d?a Tuesday, August 05, 2008 a las 08:55:38AM -0400, Andrew Duane escribi?: > Well, there are always Juniper Networks boxes :-) Exactly this is what I'm not wanting to end up with :-) -- Matthias Apitz w http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From olli at lurza.secnetix.de Tue Aug 5 15:44:56 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Tue Aug 5 15:45:03 2008 Subject: restore of file system into USB key terrible slow In-Reply-To: <20080805123533.GA3262@rebelion.Sisis.de> Message-ID: <200808051506.m75F69d5039014@lurza.secnetix.de> Matthias Apitz wrote: > [...] > > I'm trying to restore a DUMP into an USB key; the DUMP was extracted > > from another USB key which I just want to colne this way; Note that dump/restore isn't a very fast method to clone a file system. Actually, a few years ago it was horribly slow, but it was improved somewhat. It's better now, but still not very fast. Personally I recommend to try cpdup (from ports/sysutils). You can simply type "cpdup /src /dst" and it will make an exact copy (except for sparse files). A nice feature of cpdup is that it doesn't copy files that already exist in the destination. Another way copy a directory tree is to use find+cpio: cd /src; find -d . | cpdio -dump /dst Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 From ticso at cicely7.cicely.de Tue Aug 5 19:03:22 2008 From: ticso at cicely7.cicely.de (Bernd Walter) Date: Tue Aug 5 19:03:32 2008 Subject: restore of file system into USB key terrible slow In-Reply-To: <200808051506.m75F69d5039014@lurza.secnetix.de> References: <20080805123533.GA3262@rebelion.Sisis.de> <200808051506.m75F69d5039014@lurza.secnetix.de> Message-ID: <20080805190307.GY94193@cicely7.cicely.de> On Tue, Aug 05, 2008 at 05:06:09PM +0200, Oliver Fromme wrote: > Matthias Apitz wrote: > > [...] > > > I'm trying to restore a DUMP into an USB key; the DUMP was extracted > > > from another USB key which I just want to colne this way; > > Note that dump/restore isn't a very fast method to clone > a file system. Actually, a few years ago it was horribly > slow, but it was improved somewhat. It's better now, but > still not very fast. Additonally some flash devices are horribly slow when it comes to many small random writes, which writing many small files does. Internally they do read modify writes on physically larger blocks. It is often much faster to do the FS work on an image and then dd the image to the USB stick using 64k to 256k transfers. MLC flash devices are typical candidates for being extremly slow with small random writs. If speed is an issue you should take care and invest in the higher price to buy SLC devices. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From dillon at apollo.backplane.com Tue Aug 5 20:59:25 2008 From: dillon at apollo.backplane.com (Matthew Dillon) Date: Tue Aug 5 20:59:31 2008 Subject: restore of file system into USB key terrible slow References: <20080805123533.GA3262@rebelion.Sisis.de> <200808051506.m75F69d5039014@lurza.secnetix.de> <20080805190307.GY94193@cicely7.cicely.de> Message-ID: <200808052059.m75KxJu8030759@apollo.backplane.com> I've had good luck mounting UFS -o async on USB keys for the purposes of doing bulk operations. It still isn't the fastest thing in the world but it seems fast enough. Softupdates does a *lot* of tiny I/O's, try disabling it (I think mounting async disables softupdates automatically but I'm not sure). -Matt Matthew Dillon From bruce at cran.org.uk Tue Aug 5 21:34:20 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Tue Aug 5 21:34:28 2008 Subject: IPv6 CVS In-Reply-To: <20080805122817.GA89022@eos.sc1.parodius.com> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> <000801c8f6eb$111622f0$334268d0$@com> <20080805122817.GA89022@eos.sc1.parodius.com> Message-ID: <20080805223409.620e5044@tau.draftnet> On Tue, 5 Aug 2008 05:28:17 -0700 Jeremy Chadwick wrote: > On Tue, Aug 05, 2008 at 12:04:33PM +0100, Pegasus Mc Cleaft wrote: > > > -----Original Message----- > > > From: owner-freebsd-hackers@freebsd.org [mailto:owner-freebsd- > > > hackers@freebsd.org] On Behalf Of Stefan Sperling > > > Sent: 05 August 2008 11:51 > > > To: Maxim Konovalov > > > Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow > > > Subject: Re: IPv6 CVS > > > > > > On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: > > > > On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > Does anyone know if there are any IPv6 CVS servers for > > > > > > FreeBSD? > > > (As > > > > > > in > > > > > > receiving the STABLE and ports branches) I currently use > > > > > > cvs.freebsd.org but > > > > > > it dosent have an AAAA record. > > > > > > > > > > > > Ta > > > > > > > > > > > > Peg > > > > > > > > > > > dig aaaa cvsup4.freebsd.org > > > > > > > > > cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has > > > > an ipv6 address as well. > > > > > > AFAIK the Modula3 runtime does not support IPv6. > > > > > > Stefan > > > > Thanks everyone, > > > > Looks like Tim is correct where I am able to ping cvsup4, > > but unfortunately the csup utility reports a fail (Connection > > Refused) as it tries to connect to the V6 address. It will quite > > happily connect to the same machine V4. > > csup is written in C; it does not use Modula3/ezm3. cvsup uses > Modula3/ezm3. The problem is cvsupd - since it's written in Modula3 and doesn't support IPv6 you have to use an inetd/netcat hack to accept IPv6 connections on the server. As mentioned in http://lists.freebsd.org/pipermail/freebsd-current/2008-July/086710.html cvsup18.freebsd.org and cvsup4.ru.freebsd.org both accept IPv6 connections. -- Bruce Cran From jespasac at minibofh.org Wed Aug 6 08:40:34 2008 From: jespasac at minibofh.org (Jordi Espasa Clofent) Date: Wed Aug 6 08:40:41 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> References: <20080805080520.GB3063@rebelion.Sisis.de> <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> Message-ID: <48995F1F.4010209@minibofh.org> > Well, there are always Juniper Networks boxes :-) I do the same (even more in some points) as Juniper boxes with simple standard boxes with OpenBSD and PF. At present day my central FWs are simply standard 2 boxes (each one cost 1000 euros aprox); I remember the Juniper guy offering me a 'cheap' 7000/12000 euros solution...... :P Moreover, as far I know, the core of Juniper devices is BSD (FreeBSD especially) based. -- Thanks, Jordi Espasa Clofent From koitsu at FreeBSD.org Wed Aug 6 09:44:11 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Aug 6 09:44:19 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <48995F1F.4010209@minibofh.org> References: <20080805080520.GB3063@rebelion.Sisis.de> <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> <48995F1F.4010209@minibofh.org> Message-ID: <20080806094411.GA51807@eos.sc1.parodius.com> On Wed, Aug 06, 2008 at 10:21:51AM +0200, Jordi Espasa Clofent wrote: >> Well, there are always Juniper Networks boxes :-) > > I do the same (even more in some points) as Juniper boxes with simple > standard boxes with OpenBSD and PF. > > At present day my central FWs are simply standard 2 boxes (each one cost > 1000 euros aprox); I remember the Juniper guy offering me a 'cheap' > 7000/12000 euros solution...... :P I'm amazed at the fact that people are actually comparing FreeBSD with pf to Juniper routers. I've a bit of experience with M20s and M40s, and I can assure you they're VERY different than a little x86 PC routing packets, and are significantly faster due to hardware routing. For example, you should be aware of a pf(4) bug that was only recently fixed. Our FreeBSD systems only use ACLs + state track, and have low network I/O (600kbit/sec) -- yet this sort of thing impacts production packets on a webserver: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125261 http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/pf/net/pf.c Max committed the fix to CURRENT, and it should be MFC'd on the 11th. I hope it gets backported to RELENG_6 as well, since it's pretty major (IMHO). My point isn't to insult or poke fun at pf or FreeBSD. I'm simply stating "if you really think an x86 box with pf is better than a Juniper, you're sadly mistaken". I'm not telling you to go out and buy a Juniper either, especially if it's out of your price range -- but you really need to be more aware of the differences before toting the "my FreeBSD box can do the job better!" attitude. I'm glad FreeBSD with pf works for you, though. > Moreover, as far I know, the core of Juniper devices is BSD (FreeBSD > especially) based. Correct, JunOS is FreeBSD 4.x-based. On the other hand, I find it amusing that Juniper's routers use ATA disks. A single disk failure results in the system becoming unusable administratively (requiring a reboot), while the routing engine still works fine (e.g. packets are still routed properly, ACLs applied, etc.). Config data is kept on CF, so that isn't lost. You just can't SSH into it, and all you'll see on serial console is repetitive ATA and SMART errors. I've seen this happen on three separate routers on three separate occasions at my workplace. For something that costs so much money, you'd have expected them to go with some form of disk redundancy, SCSI disks, or SSDs. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From jespasac at minibofh.org Wed Aug 6 10:49:03 2008 From: jespasac at minibofh.org (Jordi Espasa Clofent) Date: Wed Aug 6 10:49:10 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <20080806094411.GA51807@eos.sc1.parodius.com> References: <20080805080520.GB3063@rebelion.Sisis.de> <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> <48995F1F.4010209@minibofh.org> <20080806094411.GA51807@eos.sc1.parodius.com> Message-ID: <4899819C.3090502@minibofh.org> > I'm amazed at the fact that people are actually comparing FreeBSD with > pf to Juniper routers. I've a bit of experience with M20s and M40s, and > I can assure you they're VERY different than a little x86 PC routing > packets, and are significantly faster due to hardware routing. > > For example, you should be aware of a pf(4) bug that was only recently > fixed. Our FreeBSD systems only use ACLs + state track, and have low > network I/O (600kbit/sec) -- yet this sort of thing impacts production > packets on a webserver: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/125261 > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/pf/net/pf.c > > Max committed the fix to CURRENT, and it should be MFC'd on the 11th. I > hope it gets backported to RELENG_6 as well, since it's pretty major > (IMHO). Yes. That's my main personal reason to work with OpenBSD instead of FreeBSD when I need PF dedicated device. > My point isn't to insult or poke fun at pf or FreeBSD. I'm simply > stating "if you really think an x86 box with pf is better than a > Juniper, you're sadly mistaken". I'm not telling you to go out and buy > a Juniper either, especially if it's out of your price range -- but you > really need to be more aware of the differences before toting the "my > FreeBSD box can do the job better!" attitude. I'm glad FreeBSD with pf > works for you, though. Good reasoning Jeremy. I don't say that x86 pf-based box is better than Juniper. I only comment that, in my case, I do all I need with two standard boxes instead of expensive Juniper device. Anyway it's clear if one day the best solution is Juniper device, I will purchase it. But at present moment, isn't (300Mpbs/500Mpbs) > On the other hand, I find it amusing that Juniper's routers use ATA > disks. A single disk failure results in the system becoming unusable > administratively (requiring a reboot), while the routing engine still > works fine (e.g. packets are still routed properly, ACLs applied, > etc.). Config data is kept on CF, so that isn't lost. You just can't > SSH into it, and all you'll see on serial console is repetitive ATA and > SMART errors. I've seen this happen on three separate routers on three > separate occasions at my workplace. Interesting. My OpenBSD+PF FWs runs at present with ATA disks also, but I'm designing a CF-based new implementation. ;) -- Thanks, Jordi Espasa Clofent From guru at unixarea.de Wed Aug 6 12:57:22 2008 From: guru at unixarea.de (Matthias Apitz) Date: Wed Aug 6 12:57:29 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present Message-ID: <20080806125719.GA8008@rebelion.Sisis.de> Hello, I've updated usb/80361, see http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 because I have the same problem as well that an USB key attaches fine when plugged in at boot time, but not later: what makes me worry is that the problem was raised in 5.4-RC3 in 2005 and still exists in 7.0R in 2008, or have I overlooked some cool system parameter to fix this; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From cmarlatt at rxsec.com Wed Aug 6 13:46:42 2008 From: cmarlatt at rxsec.com (Chris Marlatt) Date: Wed Aug 6 14:02:46 2008 Subject: Q: case studies about scalable, enterprise-class firewall w/ IPFilter In-Reply-To: <20080806094411.GA51807@eos.sc1.parodius.com> References: <20080805080520.GB3063@rebelion.Sisis.de> <0FCFCF6165E968449991746EB91D614D142FD4@antipi.jnpr.net> <48995F1F.4010209@minibofh.org> <20080806094411.GA51807@eos.sc1.parodius.com> Message-ID: <4899A595.3040802@rxsec.com> Jeremy Chadwick wrote: > On Wed, Aug 06, 2008 at 10:21:51AM +0200, Jordi Espasa Clofent wrote: >>> Well, there are always Juniper Networks boxes :-) >> I do the same (even more in some points) as Juniper boxes with simple >> standard boxes with OpenBSD and PF. >> >> At present day my central FWs are simply standard 2 boxes (each one cost >> 1000 euros aprox); I remember the Juniper guy offering me a 'cheap' >> 7000/12000 euros solution...... :P > > I'm amazed at the fact that people are actually comparing FreeBSD with > pf to Juniper routers. I've a bit of experience with M20s and M40s, and > I can assure you they're VERY different than a little x86 PC routing > packets, and are significantly faster due to hardware routing. > The M series is hardware routed but IIRC the J series is routed in software. The performance numbers for this series are pretty close to what FreeBSD can do with the right hardware and network cards and for a lot less money. FreeBSD can also outperform many of the SSG's and NetScreen's - up to the 550/500 I think. That said, Juniper still offers numerous features that are worthwhile, even in the J, SSG and NetScreen series. You just have to need those features in order for it to make any sense. Regards, Chris From olli at lurza.secnetix.de Wed Aug 6 17:30:09 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Wed Aug 6 17:30:16 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <20080806125719.GA8008@rebelion.Sisis.de> Message-ID: <200808061729.m76HTVVh003285@lurza.secnetix.de> Matthias Apitz wrote: > I've updated usb/80361, see > http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 > because I have the same problem as well that an USB key attaches fine > when plugged in at boot time, but not later: I'm just wondering what happens if you enforce a rescan on the (virtual) SCSI bus. That is, after you have plugged in the USB stick and the problem occured, type "camcontrol rescan 0". If that doesn't help, please try this patch: =============================================================================== --- src/sys/dev/usb/umass.c.orig 2008-05-21 16:22:03.000000000 +0200 +++ src/sys/dev/usb/umass.c 2008-08-06 19:23:01.000000000 +0200 @@ -2690,7 +2690,7 @@ * completed, when interrupts have been enabled. */ - callout_reset(&sc->cam_scsi_rescan_ch, MS_TO_TICKS(200), + callout_reset(&sc->cam_scsi_rescan_ch, MS_TO_TICKS(2000), umass_cam_rescan, sc); } =============================================================================== Note that this patch is not a solution. It's purpose is to find out if the cause of your problem is the same as the one in PR usb/80361. If it is, the patch from the PR should be committed (it introduces a quirk for cases like this), and your USB stick should be added to the quirks list. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "The last good thing written in C was Franz Schubert's Symphony number 9." -- Erwin Dieterich From jrytoung at gmail.com Wed Aug 6 20:26:31 2008 From: jrytoung at gmail.com (Jerry Toung) Date: Wed Aug 6 20:26:47 2008 Subject: options MAC vs. pkg_add Message-ID: <86068e730808061300t251019b1t4b42368980f7c930@mail.gmail.com> Hi List, I am running into a weird issue. On a 6.2 stable, 32bits built with options MAC, I can run pkg_add of anything. But a 6.2 stable, 64bits built with MAC won't let me do pkg_add. If anybody has an input, please advise. Below is the output on the 64 bits machine: net3# pkg_add test.tbz +CONTENTS: Can't update time for +CONTENTS: Operation not permitted pkg_add: tar extract of /wr/home/webmgr/test.tbz failed! pkg_add: unable to extract table of contents file from '/wr/home/webmgr/test.tbz' - not a package? net3# net3# tar xvf test.tbz x +CONTENTS: Can't update time for +CONTENTS: Operation not permitted x +COMMENT: Can't update time for +COMMENT: Operation not permitted x +DESC: Can't update time for +DESC: Operation not permitted x +DISPLAY: Can't update time for +DISPLAY: Operation not permitted x usr/local/bin/sudo: Can't update time for usr/local/bin/sudo: Operation not permitted x usr/local/man/man8/sudo.8: Can't update time for usr/local/man/man8/sudo.8: Operation not permitted x usr/local/man/man8/visudo.8: Can't update time for usr/local/man/man8/visudo.8: Operation not permitted x usr/local/man/man5/sudoers.5 x usr/local/sbin/visudo: Can't update time for usr/local/sbin/visudo: Operation not permitted x usr/local/libexec/sudo_noexec.so: Can't update time for usr/local/libexec/sudo_noexec.so: Operation not permitted x usr/local/libexec/sudo_noexec.la: Can't update time for usr/local/libexec/ sudo_noexec.la: Operation not permitted x etc/sudoers: Can't update time for etc/sudoers: Operation not permitted net3# uname -a FreeBSD net3 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Aug 5 15:10:45 PDT 2008 root@test:/usr/obj/usr/src/sys/MYBD amd64 thanks, Jerry From gleb.kurtsou at gmail.com Wed Aug 6 21:19:46 2008 From: gleb.kurtsou at gmail.com (Gleb Kurtsou) Date: Wed Aug 6 21:19:53 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <200808061729.m76HTVVh003285@lurza.secnetix.de> References: <20080806125719.GA8008@rebelion.Sisis.de> <200808061729.m76HTVVh003285@lurza.secnetix.de> Message-ID: <20080806210127.GA1367@h1.d> On (06/08/2008 19:29), Oliver Fromme wrote: > Matthias Apitz wrote: > > I've updated usb/80361, see > > http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 > > because I have the same problem as well that an USB key attaches fine > > when plugged in at boot time, but not later: Situation here is somewhat opposite. Device doesn't attach at boot or attaches some times. And needs special patch to attach later. % usbdevs -v port 1 addr 2: high speed, power 300 mA, config 1, USB DRIVE(0x0111), 0(0x04e8), rev 2.00 > > I'm just wondering what happens if you enforce a rescan > on the (virtual) SCSI bus. That is, after you have > plugged in the USB stick and the problem occured, type > "camcontrol rescan 0". > > If that doesn't help, please try this patch: > > =============================================================================== > --- src/sys/dev/usb/umass.c.orig 2008-05-21 16:22:03.000000000 +0200 > +++ src/sys/dev/usb/umass.c 2008-08-06 19:23:01.000000000 +0200 > @@ -2690,7 +2690,7 @@ > * completed, when interrupts have been enabled. > */ > > - callout_reset(&sc->cam_scsi_rescan_ch, MS_TO_TICKS(200), > + callout_reset(&sc->cam_scsi_rescan_ch, MS_TO_TICKS(2000), > umass_cam_rescan, sc); > } With this patch it gives following error: Aug 6 23:33:44 h1 kernel: umass0: <0 USB DRIVE, class 0/0, rev 2.00/2.00, addr 2> on uhub2 Aug 6 23:33:46 h1 kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 23:33:46 h1 kernel: da0: < USB DRIVE 2.00> Removable Direct Access SCSI-2 device Aug 6 23:33:46 h1 kernel: da0: 40.000MB/s transfers Aug 6 23:33:46 h1 kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, I've tried to increase delay up to 4000, nothing changed. Without patch error message is different. Can reproduce it if somebody is interested in it. But what surprises is that with this patch device attaches during boot. > Note that this patch is not a solution. It's purpose is > to find out if the cause of your problem is the same as > the one in PR usb/80361. If it is, the patch from the PR > should be committed (it introduces a quirk for cases like > this), and your USB stick should be added to the quirks > list. I've been using another homemade patch for >2 years. Hope it can help to find a real solution. I have no idea what it does, I'm not sure a had one during writing it back then. Anyway key attaches and just works. diff -r 24788dc12d11 -r 519a067f2475 sys/dev/usb/umass.c --- a/sys/dev/usb/umass.c Sat Jun 03 13:05:16 2006 +0300 +++ b/sys/dev/usb/umass.c Sat Jun 03 13:08:35 2006 +0300 @@ -2514,7 +2514,7 @@ umass_cam_action(struct cam_sim *sim, un sense->extra_len = 10; ccb->csio.scsi_status = SCSI_STATUS_CHECK_COND; ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR | - CAM_AUTOSNS_VALID; + /* CAM_AUTOSNS_VALID */ 0; xpt_done(ccb); return; } @@ -2805,7 +2805,7 @@ umass_cam_sense_cb(struct umass_softc *s */ ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; csio->scsi_status = SCSI_STATUS_CHECK_COND; #if 0 @@ -2836,7 +2836,7 @@ umass_cam_sense_cb(struct umass_softc *s break; } else { ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; csio->scsi_status = SCSI_STATUS_CHECK_COND; } xpt_done(ccb); @@ -2872,7 +2872,7 @@ umass_cam_quirk_cb(struct umass_softc *s ccb->ccb_h.status = CAM_REQ_CMP; #endif ccb->ccb_h.status = CAM_SCSI_STATUS_ERROR - | CAM_AUTOSNS_VALID; + | /* CAM_AUTOSNS_VALID */ 0; ccb->csio.scsi_status = SCSI_STATUS_CHECK_COND; xpt_done(ccb); } From wbentley at futurecis.com Wed Aug 6 23:48:02 2008 From: wbentley at futurecis.com (wbentley@futurecis.com) Date: Thu Aug 7 01:56:07 2008 Subject: Idea for FreeBSD Message-ID: To who it may concern, I am A FreeBSD administrator as well as a Solaris Administrator. I use BSD at home but Solaris at work. I love both OS's but I would like to increase the administrative capability of FreeBSD. In Solaris 10 the Services Management Facility (SMF) was introduced. Basically what it does, is take all the rc.d scripts and puts them into a database to manage. Everything is converted to XML and two basic commands (svcs and svcadm) are used to manage everything. I would like to submit the idea of implementing a similar environment into FreeBSD. After looking through the developers links and googling I found no project for FreeBSD that implemented anything similar to this. I have included a link below to give a better understanding of SMF and its capabilities. Is it possible, if it does not exist already, to look at the possibility of implementing the concept of SMF into FreeBSD? I would gladly be an active supporter in this endeavor. Will Bentley Future CIS 410-782-5954 "Your resource for computer expertise!" From ioplex at gmail.com Thu Aug 7 03:01:10 2008 From: ioplex at gmail.com (Michael B Allen) Date: Thu Aug 7 03:01:20 2008 Subject: Idea for FreeBSD In-Reply-To: References: Message-ID: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> On Wed, Aug 6, 2008 at 7:14 PM, wrote: > To who it may concern, > > I am A FreeBSD administrator as well as a Solaris Administrator. I use > BSD at home but Solaris at work. I love both OS's but I would like to > increase the administrative capability of FreeBSD. > > In Solaris 10 the Services Management Facility (SMF) was introduced. > Basically what it does, is take all the rc.d scripts and puts them into > a database to manage. Everything is converted to XML XML is good at document processing and for portable self-describing databases. Otherwise, I would think significantly less of any OS (or application) that used XML for configuration data. At least nothing that anyone would *every* be forced to edit manually. But of course the format of data in a database is largely irrelevant. You could implement the same thing with dbm files or a more forgiving text format. As for getting rid of rc.d scripts, yes they're decrepit and I would love to see them go but they're simple and third party software may depend on them being the norm. Just my 2c, Mike PS: I'm not a FreeBSD "hacker" or even an admin. From tim at clewlow.org Thu Aug 7 04:24:57 2008 From: tim at clewlow.org (Tim Clewlow) Date: Thu Aug 7 04:25:03 2008 Subject: Idea for FreeBSD In-Reply-To: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> Message-ID: <52107.192.168.1.10.1218081999.squirrel@192.168.1.100> > On Wed, Aug 6, 2008 at 7:14 PM, wrote: >> To who it may concern, >> >> I am A FreeBSD administrator as well as a Solaris Administrator. >> I use >> BSD at home but Solaris at work. I love both OS's but I would like >> to >> increase the administrative capability of FreeBSD. >> >> In Solaris 10 the Services Management Facility (SMF) was >> introduced. >> Basically what it does, is take all the rc.d scripts and puts them >> into >> a database to manage. Everything is converted to XML > > XML is good at document processing and for portable self-describing > databases. Otherwise, I would think significantly less of any OS (or > application) that used XML for configuration data. At least nothing > that anyone would *every* be forced to edit manually. > > But of course the format of data in a database is largely > irrelevant. > You could implement the same thing with dbm files or a more > forgiving > text format. > > As for getting rid of rc.d scripts, yes they're decrepit and I would > love to see them go but they're simple and third party software may > depend on them being the norm. > > Just my 2c, > Mike > > PS: I'm not a FreeBSD "hacker" or even an admin. > _______________________________________________ I believe the puppet project has a lot of potential, or if not the project then at least the ideas behind it, in regard to automating administrative tasks. I particularly like the way it allows the automation of the same tasks across different operating systems. http://reductivelabs.com/trac/puppet/ Cheers, Tim. From samflanker at gmail.com Thu Aug 7 04:35:15 2008 From: samflanker at gmail.com (Vladimir Ermakov) Date: Thu Aug 7 04:35:32 2008 Subject: em0: The EEPROM Checksum Is Not Valid Message-ID: <489A7B64.4000306@gmail.com> Hello my trouble with nic part of `dmesg` output --------------------------------------------------------------------- em0: port 0xec00-0xec3f mem 0xfebc0000-0xfebdffff,0xfeb80000-0xfebbffff irq 19 at device 2.0 on pci2 em0: The EEPROM Checksum Is Not Valid device_attach: em0 attach returned 5 ---------------------------------------------------------------------- part of `pciconf -lv` output ---------------------------------------------------------------------- em0@pci0:2:2:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82545GM Gigabit Ethernet Controller' class = network subclass = ethernet ---------------------------------------------------------------------- uname output ---------------------------------------------------------------------- FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #2: Wed Jul 16 20:36:12 UTC 2008 root@:/usr/obj/usr/src/sys/STONE i386 ---------------------------------------------------------------------- please, any solution? /Vladimir Ermakov From alex.wilkinson at dsto.defence.gov.au Thu Aug 7 04:35:54 2008 From: alex.wilkinson at dsto.defence.gov.au (Wilkinson, Alex) Date: Thu Aug 7 04:36:12 2008 Subject: Idea for FreeBSD In-Reply-To: References: Message-ID: <20080807043331.GA38794@stlux503.dsto.defence.gov.au> 0n Wed, Aug 06, 2008 at 07:14:51PM -0400, wbentley@futurecis.com wrote: >I would like to submit the idea of implementing a similar environment >into FreeBSD. After looking through the developers links and googling I >found no project for FreeBSD that implemented anything similar to this. >I have included a link below to give a better understanding of SMF and >its capabilities. I believe there was a port of MacOS-X 'launchd' to FreeBSD: [http://wiki.freebsd.org/launchd] I think launchd may use XML. -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. From samflanker at gmail.com Thu Aug 7 04:35:56 2008 From: samflanker at gmail.com (Vladimir Ermakov) Date: Thu Aug 7 04:36:13 2008 Subject: em0: The EEPROM Checksum Is Not Valid Message-ID: <489A7B8F.1080407@gmail.com> Hello my trouble with nic part of `dmesg` output --------------------------------------------------------------------- em0: port 0xec00-0xec3f mem 0xfebc0000-0xfebdffff,0xfeb80000-0xfebbffff irq 19 at device 2.0 on pci2 em0: The EEPROM Checksum Is Not Valid device_attach: em0 attach returned 5 ---------------------------------------------------------------------- part of `pciconf -lv` output ---------------------------------------------------------------------- em0@pci0:2:2:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82545GM Gigabit Ethernet Controller' class = network subclass = ethernet ---------------------------------------------------------------------- uname output ---------------------------------------------------------------------- FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #2: Wed Jul 16 20:36:12 UTC 2008 root@:/usr/obj/usr/src/sys/STONE i386 ---------------------------------------------------------------------- please, any solution? /Vladimir Ermakov From koitsu at FreeBSD.org Thu Aug 7 05:07:26 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 05:07:32 2008 Subject: em0: The EEPROM Checksum Is Not Valid In-Reply-To: <489A7B64.4000306@gmail.com> References: <489A7B64.4000306@gmail.com> Message-ID: <20080807050725.GA8969@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 08:34:44AM +0400, Vladimir Ermakov wrote: > Hello > > my trouble with nic > > part of `dmesg` output > --------------------------------------------------------------------- > em0: port 0xec00-0xec3f mem > 0xfebc0000-0xfebdffff,0xfeb80000-0xfebbffff irq 19 at device 2.0 on pci2 > em0: The EEPROM Checksum Is Not Valid > device_attach: em0 attach returned 5 > ---------------------------------------------------------------------- > > part of `pciconf -lv` output > ---------------------------------------------------------------------- > em0@pci0:2:2:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x01 > hdr=0x00 > vendor = 'Intel Corporation' > device = '82545GM Gigabit Ethernet Controller' > class = network > subclass = ethernet > ---------------------------------------------------------------------- > > uname output > ---------------------------------------------------------------------- > FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #2: Wed Jul 16 20:36:12 UTC 2008 > root@:/usr/obj/usr/src/sys/STONE i386 > ---------------------------------------------------------------------- > > please, any solution? Intel probably has a utility to reset the EEPROM settings on the NIC. Jack Vogel may know where to get such a utility. I do not believe this problem is FreeBSD-related. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From mwm-keyword-freebsdhackers2.e313df at mired.org Thu Aug 7 05:34:22 2008 From: mwm-keyword-freebsdhackers2.e313df at mired.org (Mike Meyer) Date: Thu Aug 7 05:34:30 2008 Subject: Idea for FreeBSD In-Reply-To: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> Message-ID: <20080807010638.267d7790@bhuda.mired.org> On Wed, 6 Aug 2008 22:34:51 -0400 "Michael B Allen" wrote: > On Wed, Aug 6, 2008 at 7:14 PM, wrote: > > To who it may concern, > > > > I am A FreeBSD administrator as well as a Solaris Administrator. I use > > BSD at home but Solaris at work. I love both OS's but I would like to > > increase the administrative capability of FreeBSD. > > > > In Solaris 10 the Services Management Facility (SMF) was introduced. > > Basically what it does, is take all the rc.d scripts and puts them into > > a database to manage. Everything is converted to XML > > XML is good at document processing and for portable self-describing > databases. Otherwise, I would think significantly less of any OS (or > application) that used XML for configuration data. At least nothing > that anyone would *every* be forced to edit manually. Give the right tools, editing XML is actually reasonable. The right tools are a schema for the documents in question, a schema-aware editor, and applications software that bitches if the document doesn't match the schema. The problem is that you almost never get a schema, and having an application that cares is even rarer. Without those, you're best off using application tools to manipulate the documents, and never touching it except for emergencies. In which case: > But of course the format of data in a database is largely irrelevant. > You could implement the same thing with dbm files or a more forgiving > text format. Right. For that matter, you could leave the data in shell scripts, and build a layer of meta information and tools to manipulate these things - which is similar to what I see in Linux distros. The Solaris smf tools provide some nice facilities: one is single interface to start, stop, check and restart all the services on a system. We pretty much have that, as they all use the same basic arguments to their rc scripts. The only issue is figuring out which directory to find the rc script in. The other is a single interface to enable, disable and query the status of all the services. All we really have is the last one: you can run the script with the rcvar argument, and it'll list the appropriate variable if it's set, and the value it's set to. Maybe. Not all of them support this yet. > As for getting rid of rc.d scripts, yes they're decrepit and I would > love to see them go but they're simple and third party software may > depend on them being the norm. The only thing decrepit about the rc.d scripts is that they don't all support the latest facilities that you'd expect them to. But the way to fix that is to update the old ones, not to throw out all of them and start over. In particular, if you want to replace them with a better format, you need to start by showing that said format is better - and chanting buzzwords like "xml" isn't sufficient to do that. You could, for instance, get all of the facilities of svcs with a shell script that grokked the current rc.d formats. Searching wouldn't be quite as spiffy because we don't have the concept of an FMRI, and getting the output formatting facilities right would be a bit tricky, but the information is pretty much all there. svcadm is a bit harder, because you'd have to edit rc.conf in place, but again, most of the pieces are already in place. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From ioplex at gmail.com Thu Aug 7 06:31:11 2008 From: ioplex at gmail.com (Michael B Allen) Date: Thu Aug 7 06:31:19 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807010638.267d7790@bhuda.mired.org> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> Message-ID: <78c6bd860808062331h674b951ei5f7ca95a930f1af4@mail.gmail.com> On Thu, Aug 7, 2008 at 1:06 AM, Mike Meyer wrote: > On Wed, 6 Aug 2008 22:34:51 -0400 > "Michael B Allen" wrote: >> As for getting rid of rc.d scripts, yes they're decrepit and I would >> love to see them go but they're simple and third party software may >> depend on them being the norm. > > The only thing decrepit about the rc.d scripts is that they don't all > support the latest facilities that you'd expect them to. But the way > to fix that is to update the old ones, not to throw out all of them > and start over. In particular, if you want to replace them with a > better format, you need to start by showing that said format is better > - and chanting buzzwords like "xml" isn't sufficient to do that. I did not mean to say that the scripts themselves were decrepit. I mean the whole Unix runlevel rc.d apparatus in general is decrepit. There should be a library to install, start, stop, restart, uninstall, disable, enable, change order of services and also change the runlevel. And then there should be a very small utility that calls the library to invoke the desired operations from the commandline and from init. If the library and corresponding utility are implemented correctly, the format of the file containing service state should be moot since no one will ever look at it (which is to say dbm or some other binary-blob format should be used since it makes programming the said library much cleaner). And for backwards compatibility you leave the rc.d tree so that a third party can drop in a script and it will continue to work but anyone using the said utility would completely bypass all the rc.d business. But I just made that up. Of course such things are never as simple as they sound the first time around. Mike From kientzle at freebsd.org Thu Aug 7 06:32:23 2008 From: kientzle at freebsd.org (Tim Kientzle) Date: Thu Aug 7 06:32:57 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807010638.267d7790@bhuda.mired.org> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> Message-ID: <489A9344.3060306@freebsd.org> > The Solaris smf tools provide some nice facilities: one is single > interface to start, stop, check and restart all the services on a > system. We pretty much have that ... > > The other is a single interface to enable, disable and query the > status of all the services. All we really have is the last one... Sounds like the only missing pieces, then, are standard ways to enable, disable, and configure services. How about: sudo /etc/rc.d/ssh enable sudo /etc/rc.d/ssh disable sudo /etc/rc.d/ssh configure That shouldn't be much of a stretch to implement, either. The first two just append entries to /etc/rc.conf. The third opens an editor with a list of variables supported by this service and then appends the result to rc.conf. Tim From spam at rm-rf.kiev.ua Thu Aug 7 07:18:23 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Thu Aug 7 07:18:30 2008 Subject: Idea for FreeBSD Message-ID: <20080807061500.GA23109@ravenloft.kiev.ua> On Thu, Aug 07, 2008 at 01:06:38AM -0400, Mike Meyer wrote: >On Wed, 6 Aug 2008 22:34:51 "Michael B Allen" wrote: > > But of course the format of data in a database is largely irrelevant. > > You could implement the same thing with dbm files or a more forgiving > > text format. > > Right. For that matter, you could leave the data in shell scripts, and > build a layer of meta information and tools to manipulate these things > - which is similar to what I see in Linux distros. > > The Solaris smf tools provide some nice facilities: one is single > interface to start, stop, check and restart all the services on a > system. We pretty much have that, as they all use the same basic > arguments to their rc scripts. The only issue is figuring out which > directory to find the rc script in. I use for this simple script [1] plus some programmable completion. > > The other is a single interface to enable, disable and query the > status of all the services. All we really have is the last one: you > can run the script with the rcvar argument, and it'll list the > appropriate variable if it's set, and the value it's set > to. Maybe. Not all of them support this yet. > > As for getting rid of rc.d scripts, yes they're decrepit and I would > > love to see them go but they're simple and third party software may > > depend on them being the norm. Can You please be more elaborate? Yes, rc.d scripts have some problems, but I don't think We need to get rid of them. [1]: $cat /usr/local/bin/service #!/bin/sh name=$1 cmd=$2 . /etc/rc.subr if [ -z "${name}" -o -z "${cmd}" ] then echo ${0##*/} service_name command exit 3 fi if [ -r "/etc/rc.d/${name}" ] then run_rc_script "/etc/rc.d/${name}" ${cmd} exit 0 fi if [ -r "/usr/local/etc/rc.d/${name}" ] then run_rc_script "/usr/local/etc/rc.d/${name}" ${cmd} exit 0 fi if [ -r "/usr/local/etc/rc.d/${name}.sh" ] then run_rc_script "/usr/local/etc/rc.d/${name}.sh" ${cmd} exit 0 fi echo "service '${name}' not found" exit 2 -- Adios From guru at unixarea.de Thu Aug 7 07:54:57 2008 From: guru at unixarea.de (Matthias Apitz) Date: Thu Aug 7 07:55:05 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <200808061729.m76HTVVh003285@lurza.secnetix.de> References: <20080806125719.GA8008@rebelion.Sisis.de> <200808061729.m76HTVVh003285@lurza.secnetix.de> Message-ID: <20080807075453.GA3260@rebelion.Sisis.de> El d?a Wednesday, August 06, 2008 a las 07:29:31PM +0200, Oliver Fromme escribi?: > Matthias Apitz wrote: > > I've updated usb/80361, see > > http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 > > because I have the same problem as well that an USB key attaches fine > > when plugged in at boot time, but not later: > > I'm just wondering what happens if you enforce a rescan > on the (virtual) SCSI bus. That is, after you have > plugged in the USB stick and the problem occured, type > "camcontrol rescan 0". > this did not helped; I tried it a lot of times; also reading with dd(1) from /dev/da0 did not helped; > If that doesn't help, please try this patch: ... The problem is that this was a USB stick of a friend of me in which I have created a booting FreeBSD so he can make the installation of it in an eeePC; will try to get back this USB stick from him for further tests... matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From koitsu at FreeBSD.org Thu Aug 7 07:59:43 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 07:59:50 2008 Subject: Idea for FreeBSD In-Reply-To: References: Message-ID: <20080807074332.GA17830@eos.sc1.parodius.com> On Wed, Aug 06, 2008 at 07:14:51PM -0400, wbentley@futurecis.com wrote: > To who it may concern, > > I am A FreeBSD administrator as well as a Solaris Administrator. I use > BSD at home but Solaris at work. I love both OS's but I would like to > increase the administrative capability of FreeBSD. > > In Solaris 10 the Services Management Facility (SMF) was introduced. > Basically what it does, is take all the rc.d scripts and puts them into > a database to manage. Everything is converted to XML and two basic > commands (svcs and svcadm) are used to manage everything. I highly recommend you and anyone advocating the use of XML for such things read the following whitepaper/study, in full: http://www.cs.kent.ac.uk/pubs/2004/2102/content.pdf -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From samflanker at gmail.com Thu Aug 7 08:00:46 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 7 08:00:52 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> Message-ID: <489AABA5.9070602@gmail.com> Kostik Belousov wrote: > On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: > >> Nate Eldredge wrote: >> >>> On Wed, 30 Jul 2008, sam wrote: >>> >>> >>>> 0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 >>>> 1682 11 1 88 >>>> 0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 >>>> 1749 6 7 87 >>>> |-------------------------------------------------------------------- >>>> >>>> consolekit in |waitvt state, influencing on high volumes in procs-b >>>> >>> I don't understand what the problem is. It looks like consolekit is >>> sleeping and not using any CPU. "waitvt" just indicates where in the >>> kernel it's sleeping. I don't understand what you mean by "high >>> volumes in procs-b". >>> >>> >> How-To-Repeat: >> -------------------------------------------------------------- >> # (|cd /usr/ports/sysutils/consolekit/ && make install clean) >> >> # /usr/local/etc/rc.d/dbus forcestart >> >> # vmstat -w 1 >> procs memory page disk faults cpu >> r b w avm fre flt re pi po fr sr ad0 in sy cs us >> sy id >> 2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 >> 1 98 >> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 >> 3 97 >> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 >> 2 98 >> 1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 >> 3 97 >> ^C >> # /usr/local/sbin/console-kit-daemon && vmstat -w 1 >> procs memory page disk faults cpu >> r b w avm fre flt re pi po fr sr ad0 in sy cs us >> sy id >> 2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 >> 1 98 >> 0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 >> 2 4 94 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 >> 0 4 96 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 >> 0 3 97 >> 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 >> 0 3 97 >> 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 >> 0 3 97 >> ^C >> # >> |-------------------------------------------------------------- >> >> please, any solution ... >> > > Solution for what ? There is nothing wrong with the system. > > For the purely estetisk purpose, you may look up the line > tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); > or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring > from it. > ok Why proc-b on the HEAD, have low values (with working consolekit)? /Vladimir Ermakov From olli at lurza.secnetix.de Thu Aug 7 09:14:16 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Thu Aug 7 09:14:23 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <20080807075453.GA3260@rebelion.Sisis.de> Message-ID: <200808070913.m779DlBd041495@lurza.secnetix.de> Matthias Apitz wrote: > Oliver Fromme wrote: > > Matthias Apitz wrote: > > > I've updated usb/80361, see > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 > > > because I have the same problem as well that an USB key attaches fine > > > when plugged in at boot time, but not later: > > > > I'm just wondering what happens if you enforce a rescan > > on the (virtual) SCSI bus. That is, after you have > > plugged in the USB stick and the problem occured, type > > "camcontrol rescan 0". > > this did not helped; I tried it a lot of times; OK. > also reading with dd(1) from /dev/da0 did not helped; I think reading from it isn't expected to help. The device needs to be opened for _writing_ so the GEOM layer assumes that the partition or slice table was modified and re-reads it from the media. Something like this should be sufficient: dd if=/dev/null of=/dev/da0 count=0 It openes the device for writing (this is important), but doesn't actually write anything to it. > > If that doesn't help, please try this patch: > ... > > The problem is that this was a USB stick of a friend of me in which I > have created a booting FreeBSD so he can make the installation of it in > an eeePC; will try to get back this USB stick from him for further > tests... OK. A little bit of background information: If a USB memory stick is detected fine during boot, but not when plugged into the running system, it usually indicates that the USB stick needs a longer delay to be ready for the CAM SCSI layer. The default delay is 200 ms. This might be too short for some USB sticks. The patch increases it to 2000 ms. If that still doesn't help, then there must be a completely different problem with your USB stick. In that case someone with more intimate knowledge of the USB code needs to help. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd cat man du : where Unix geeks go when they die From ap00 at mail.ru Thu Aug 7 09:36:46 2008 From: ap00 at mail.ru (Anthony Pankov) Date: Thu Aug 7 09:36:54 2008 Subject: Idea for FreeBSD In-Reply-To: References: Message-ID: <14893571984.20080807131824@mail.ru> I wonder opinions on more general question: Does somebody believe in necessity of separate infrastructure for daemons(services)? As for me i very dislike unclean of "what where located". Some configuration lie in /etc, some in /usr/local/etc, some in /usr/local/program_name. In addition there is own inclusions in program conf's of some vital data/parameters located somewhere, not to mention program binary, libraries and startup scripts. What the shortest dump command that allow after fresh installation restore full functionality? So, i believe that clean rule of daemons(services) arrangement in system more important than startup design. May be rule that "all daemons should nest in /svc" can help. For example, /svc -mostly read /svc/daemon_name - daemon dir /svc/daemon_name/bin/ - program itself /svc/daemon_name/*.conf - configuration /svc/daemon_name/data/ - data itself (mostly read, rarely write) + symlinks to real data /svc/daemon_name/var2/*.conf - another configuration named var2 (for another instance) /svc/daemon_name/var2/data/ - data itself (mostly read, rarely write) + symlinks to real data another configuration named var2 /svc/daemon_name/cs/ - control scripts (startup/shutdown etc) So, by design there is ability: list all daemon (readdir /svc) start / stop daemons: svc daemon_name start = (do a "/svc/daemon_name/cs/start") use alternative configuration: svc daemon_name var2 start = (do a "/svc/daemon_name/cs/start -c var2") dump all functionallity dump /svc Thursday, August 07, 2008, 3:14:51 AM, you wrote: wfc> To who it may concern, wfc> I am A FreeBSD administrator as well as a Solaris Administrator. I use wfc> BSD at home but Solaris at work. I love both OS's but I would like to wfc> increase the administrative capability of FreeBSD. wfc> In Solaris 10 the Services Management Facility (SMF) was introduced. wfc> Basically what it does, is take all the rc.d scripts and puts them into wfc> a database to manage. Everything is converted to XML and two basic wfc> commands (svcs and svcadm) are used to manage everything. wfc> I would like to submit the idea of implementing a similar environment wfc> into FreeBSD. After looking through the developers links and googling I wfc> found no project for FreeBSD that implemented anything similar to this. wfc> I have included a link below to give a better understanding of SMF and wfc> its capabilities. wfc> Is it possible, if it does not exist already, to look at the wfc> possibility of implementing the concept of SMF into FreeBSD? I would wfc> gladly be an active supporter in this endeavor. wfc> Will Bentley wfc> Future CIS wfc> 410-782-5954 wfc> "Your resource for computer expertise!" wfc> _______________________________________________ wfc> freebsd-hackers@freebsd.org mailing list wfc> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers wfc> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Best regards, Anthony mailto:ap00@mail.ru From ap at bnc.net Thu Aug 7 09:45:15 2008 From: ap at bnc.net (Achim Patzner) Date: Thu Aug 7 09:45:23 2008 Subject: Idea for FreeBSD In-Reply-To: <78c6bd860808062331h674b951ei5f7ca95a930f1af4@mail.gmail.com> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> <78c6bd860808062331h674b951ei5f7ca95a930f1af4@mail.gmail.com> Message-ID: <12893AA5-1667-4798-9030-89DC76621292@bnc.net> Am 07.08.2008 um 08:31 schrieb Michael B Allen: > mean the whole Unix runlevel rc.d apparatus in general is decrepit. Hi, Jordan! 8-) > There should be a library to install, start, stop, restart, uninstall, > disable, enable, change order of services and also change the > runlevel. And then there should be a very small utility that calls the > library to invoke the desired operations from the commandline and from > init. As I'm having my daily struggles with launchd on Mac OS Servers (subsystems like lpd being turned of by mechanisms unknown to me, orphaned processes being unceremoniously eaten by launchd without any good reasons) the dream of having one tool instead of init, cron, inetd and the rest of that gang has turned into more work. As I'm also have an allergy against AIX since I came into contact with SMIT for the first time: Be careful what you're asking for, you might really get it. > If the library and corresponding utility are implemented > correctly, the format of the file containing service state should be > moot since no one will ever look at it Besides in emergencies. That's also the time where the tools you would urgently need to repair something aren't working because the system isn't completely up and running. Believe me: Editing XML using ed isn't that exciting. > (which is to say dbm or some > other binary-blob format should be used since it makes programming the > said library much cleaner). Who cares for the programmer? 8-) > But I just made that up. Of course such things are never as simple as > they sound the first time around. It's worse. Things that are looking great on paper often turn out to be a nightmare when you have to deal with it. And things like "I still intend on writing a plist format (the non-XML one) parser to incorporate into the code base [...]" on http://wiki.freebsd.org/launchd are scaring me even more (the only thing that makes .plists in binary format bearable is the fact that they can be transformed into XML and dealt with reasonable tools). Achim From m.seaman at infracaninophile.co.uk Thu Aug 7 10:30:05 2008 From: m.seaman at infracaninophile.co.uk (Matthew Seaman) Date: Thu Aug 7 10:30:13 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807074332.GA17830@eos.sc1.parodius.com> References: <20080807074332.GA17830@eos.sc1.parodius.com> Message-ID: <489ACE9D.4000606@infracaninophile.co.uk> Jeremy Chadwick wrote: > On Wed, Aug 06, 2008 at 07:14:51PM -0400, wbentley@futurecis.com wrote: >> To who it may concern, >> >> I am A FreeBSD administrator as well as a Solaris Administrator. I use >> BSD at home but Solaris at work. I love both OS's but I would like to >> increase the administrative capability of FreeBSD. >> >> In Solaris 10 the Services Management Facility (SMF) was introduced. >> Basically what it does, is take all the rc.d scripts and puts them into >> a database to manage. Everything is converted to XML and two basic >> commands (svcs and svcadm) are used to manage everything. > > I highly recommend you and anyone advocating the use of XML for such > things read the following whitepaper/study, in full: > > http://www.cs.kent.ac.uk/pubs/2004/2102/content.pdf > Heh. Loved all the little asides to Nancy... Amazing it hasn't been fixed in 4 years. Anyhow, yes: ASN.1 is smaller, and hence faster than XML for networked applications. Which is fine, but as far as I can see doesn't address the question at hand. There are two connected questions here: * What technology should be used to implement the FreeBSD rc.subr system? * What functionality could or should be added to the FreeBSD rc.subr system? Where the answer to the first question clearly constrains the results of the second. So what are the requirements for the rc system? Off the top of my head -- and I've probably missed some vital considerations here -- in order of priority: 1 reliability. The system has to boot up. 2 repeatability. The system has to boot up in a consistent state 3 fault tolerance. The system cannot fail to boot up unless the problems really are terminal. 4 configurability. The system has to boot up correctly for all conceivable combinations of hardware and software. 5 portability. Should run on anything from the smallest of embedded devices to the most enormous high power super computers to the most transient of virtualized hosts. 6 manageability. Must be comprehensible by ordinary mortals. 7 efficiency. Must bring the system up as fast as is practicable and without excessive use of system resources What does XML-based technology bring to this? As the OP states the primary benefit is in manageability. I would contend that the advantage claimed here is rather less significant than indicated. We already have a central database of configuration information -- /etc/rc.conf -- and while we don't have one single application to control starting and stopping services we have the next best thing: a consistent user interface for calling the individual rc-scripts. Indeed, as other posters have shown elsewhere in this thread, adding that sort of functionality is only a Small Matter of Programming using the existing tools. What's wrong wwith using XML? XML adds significantly to the complexity of an rc system -- it's suddenly necessary to have another shlib or two and several compiled applications available early in the boot process. XML itself is too general-purpose: it has too much baggage designed for its primary function of facilitating interoperation between diverse systems in different zones of control, none of which is particularly applicable to system startup. I can see the attraction of writing a nice pointy-clicky database-backed GUI management interface to encourage the uninitiated administrator, but that can only be an adjunct to the current setup, not a replacement. If you can't fix a broken system via a text only serial console accessed across whatever sort of low-bandwidth emergency connectivity you could imagine, then I suspect quite strongly it's not going to receive wholehearted community approval. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/d532fd22/signature.pgp From kostikbel at gmail.com Thu Aug 7 10:30:25 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Thu Aug 7 10:30:32 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <489AABA5.9070602@gmail.com> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> <489AABA5.9070602@gmail.com> Message-ID: <20080807103020.GS97161@deviant.kiev.zoral.com.ua> On Thu, Aug 07, 2008 at 12:00:37PM +0400, sam wrote: > Kostik Belousov wrote: > >On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: > > > >>Nate Eldredge wrote: > >> > >>>On Wed, 30 Jul 2008, sam wrote: > >>> > >>> > >>>>0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 > >>>>1682 11 1 88 > >>>>0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 > >>>>1749 6 7 87 > >>>>|-------------------------------------------------------------------- > >>>> > >>>>consolekit in |waitvt state, influencing on high volumes in procs-b > >>>> > >>>I don't understand what the problem is. It looks like consolekit is > >>>sleeping and not using any CPU. "waitvt" just indicates where in the > >>>kernel it's sleeping. I don't understand what you mean by "high > >>>volumes in procs-b". > >>> > >>> > >>How-To-Repeat: > >>-------------------------------------------------------------- > >># (|cd /usr/ports/sysutils/consolekit/ && make install clean) > >> > >># /usr/local/etc/rc.d/dbus forcestart > >> > >># vmstat -w 1 > >>procs memory page disk faults cpu > >>r b w avm fre flt re pi po fr sr ad0 in sy cs us > >>sy id > >>2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 > >>1 98 > >>0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 > >>3 97 > >>0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 > >>2 98 > >>1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 > >>3 97 > >>^C > >># /usr/local/sbin/console-kit-daemon && vmstat -w 1 > >>procs memory page disk faults cpu > >>r b w avm fre flt re pi po fr sr ad0 in sy cs us > >>sy id > >>2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 > >>1 98 > >>0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 > >>2 4 94 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 > >>0 4 96 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 > >>0 3 97 > >>0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 > >>0 3 97 > >>0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 > >>0 3 97 > >>^C > >># > >>|-------------------------------------------------------------- > >> > >>please, any solution ... > >> > > > >Solution for what ? There is nothing wrong with the system. > > > >For the purely estetisk purpose, you may look up the line > > tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); > >or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring > >from it. > > > ok > > Why proc-b on the HEAD, have low values (with working consolekit)? On what revision of HEAD ? I committed the change that causes the thread to sleep on the PZERO+1 priority instead of PZERO as r181286. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/c0fa6411/attachment.pgp From samflanker at gmail.com Thu Aug 7 10:54:38 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 7 10:55:03 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <20080807103020.GS97161@deviant.kiev.zoral.com.ua> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> <489AABA5.9070602@gmail.com> <20080807103020.GS97161@deviant.kiev.zoral.com.ua> Message-ID: <489AD467.4090300@gmail.com> Kostik Belousov wrote: > On Thu, Aug 07, 2008 at 12:00:37PM +0400, sam wrote: > >> Kostik Belousov wrote: >> >>> On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: >>> >>> >>>> Nate Eldredge wrote: >>>> >>>> >>>> 0 3 97 >>>> 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 >>>> 0 3 97 >>>> 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 >>>> 0 3 97 >>>> ^C >>>> # >>>> |-------------------------------------------------------------- >>>> >>>> please, any solution ... >>>> >>>> >>> Solution for what ? There is nothing wrong with the system. >>> >>> For the purely estetisk purpose, you may look up the line >>> tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); >>> or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring >>> >> >from it. >> >>> >>> >> ok >> >> Why proc-b on the HEAD, have low values (with working consolekit)? >> > > On what revision of HEAD ? I committed the change that causes the thread > to sleep on the PZERO+1 priority instead of PZERO as r181286. > ------------------------------------- # uname -a FreeBSD 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Fri Jul 4 20:01:51 MSD 2008 root@:/usr/obj/usr/src/sys/DAMASK i386 ------------------------------------- /Vladimir Ermakov From andenore at freebsd.org Thu Aug 7 11:17:26 2008 From: andenore at freebsd.org (Anders Nore) Date: Thu Aug 7 11:17:33 2008 Subject: Suggestion for 'pkg_add -r' Message-ID: Hi, In my pkg_improved GSoC project I've added a nice feature for 'pkg_add -r' which displays the size of the file being downloaded as well as progress status in % and bytes/kb/mb/... and download speed. If someone could test it and comment it would be perfect, below you can find the patches for RELENG_7 and -CURRENT. (As for now pkg_add does not have a -q/Q option (quiet), but this could perhaps be used to deprecate the output?). RELENG_7: http://home.no.net/andenore/patches/pkg_install_2008-08-06_RELENG_7.diff CURRENT: http://home.no.net/andenore/patches/pkg_install_2008-08-06_CURRENT.diff Thanks, Anders Nore From koitsu at FreeBSD.org Thu Aug 7 11:18:20 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 11:18:29 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <20080807075453.GA3260@rebelion.Sisis.de> References: <20080806125719.GA8008@rebelion.Sisis.de> <200808061729.m76HTVVh003285@lurza.secnetix.de> <20080807075453.GA3260@rebelion.Sisis.de> Message-ID: <20080807111819.GA23786@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 09:54:53AM +0200, Matthias Apitz wrote: > El d?a Wednesday, August 06, 2008 a las 07:29:31PM +0200, Oliver Fromme escribi?: > > > Matthias Apitz wrote: > > > I've updated usb/80361, see > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=80361 > > > because I have the same problem as well that an USB key attaches fine > > > when plugged in at boot time, but not later: > > > > I'm just wondering what happens if you enforce a rescan > > on the (virtual) SCSI bus. That is, after you have > > plugged in the USB stick and the problem occured, type > > "camcontrol rescan 0". > > > > this did not helped; I tried it a lot of times; also reading with dd(1) > from /dev/da0 did not helped; > > > If that doesn't help, please try this patch: > ... > > The problem is that this was a USB stick of a friend of me in which I > have created a booting FreeBSD so he can make the installation of it in > an eeePC; will try to get back this USB stick from him for further > tests... Can we get the brand and model of USB stick, and any specific model/version numbers that are on the device? The dmesg you provided doesn't have very good vendor strings in it (that's not your fault). I can tell you that in the case of *some* SanDisk USB sticks (and despite this, I still buy/use their products -- I like them), there are versions with buggy USB code on them. I spent quite some time with Supermicro trying to find out why a SanDisk USB stick would not boot on some of their servers -- it turned out to be broken/buggy firmware code inside of the USB stick itself. Replacing it with a different version (same size/model though) fixed the issue. Just something to be aware of... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From guru at unixarea.de Thu Aug 7 11:41:24 2008 From: guru at unixarea.de (Matthias Apitz) Date: Thu Aug 7 11:41:32 2008 Subject: USB key && kernel: da0: Attempt to query device size failed: UNIT ?ATTENTION, Medium not present In-Reply-To: <20080807111819.GA23786@eos.sc1.parodius.com> References: <20080806125719.GA8008@rebelion.Sisis.de> <200808061729.m76HTVVh003285@lurza.secnetix.de> <20080807075453.GA3260@rebelion.Sisis.de> <20080807111819.GA23786@eos.sc1.parodius.com> Message-ID: <20080807114119.GA2000@rebelion.Sisis.de> El d?a Thursday, August 07, 2008 a las 04:18:19AM -0700, Jeremy Chadwick escribi?: > Can we get the brand and model of USB stick, and any specific > model/version numbers that are on the device? The dmesg you provided > doesn't have very good vendor strings in it (that's not your fault). ... here we go: Aug 6 10:06:12 rebelion kernel: umass0: on uhub4 Aug 6 10:06:12 rebelion root: Unknown USB device: vendor 0x08ec product 0x0020 bus uhub4 Aug 6 10:06:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 10:06:12 rebelion kernel: da0: Removable Direct Access SCSI-0 device Aug 6 10:06:12 rebelion kernel: da0: 40.000MB/s transfers Aug 6 10:06:12 rebelion kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present seems to be this one: http://luhdc.berlios.de/Pages/USB//ViewSingle/ID=143/ matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From des at des.no Thu Aug 7 12:22:20 2008 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Thu Aug 7 12:22:26 2008 Subject: Idea for FreeBSD In-Reply-To: <78c6bd860808062331h674b951ei5f7ca95a930f1af4@mail.gmail.com> (Michael B. Allen's message of "Thu, 7 Aug 2008 02:31:09 -0400") References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> <78c6bd860808062331h674b951ei5f7ca95a930f1af4@mail.gmail.com> Message-ID: <86vdydf2uf.fsf@ds4.des.no> "Michael B Allen" writes: > I did not mean to say that the scripts themselves were decrepit. I > mean the whole Unix runlevel rc.d apparatus in general is decrepit. FreeBSD doesn't have runlevels. Solaris does. You don't like runlevels, but you want FreeBSD to be more like Solaris. Make up your mind... DES -- Dag-Erling Sm?rgrav - des@des.no From peterjeremy at optushome.com.au Thu Aug 7 12:35:16 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Aug 7 12:35:23 2008 Subject: Idea for FreeBSD In-Reply-To: References: Message-ID: <20080807090230.GF1359@server.vk2pj.dyndns.org> On 2008-Aug-06 19:14:51 -0400, wbentley@futurecis.com wrote: > In Solaris 10 the Services Management Facility (SMF) was introduced. The main purpose of SMF appears to be to drum up business for Sun's training courses by radically changing Sol10 Administration for little benefit. >Basically what it does, is take all the rc.d scripts and puts them into >a database to manage. Everything is converted to XML and two basic >commands (svcs and svcadm) are used to manage everything. So you take each line from inetd.conf (literally) and wrap it in several KB of XML. This definitely adds to bloat and doesn't even obey the spirit of XML (since the content of each inetd.conf entry remains opaque). I haven't looked at what happens to /etc/inittab or the rc.d scripts but I expect that it's similar. It's not clear what benefit this brings. The svcs and svcadm commands are among the most arcane I have bumped into during my >20 years of administering Unix. I agree that some of the process management facilities of SMF are better than exists for most FreeBSD daemons but don't believe that all the other baggage is worth the improvement. With FreeBSD, I can configure virtually all the system via a single text file - which is easily found and kepy under configuration control. With Sol10, there are random bits of configuration spread all over the system and there is no obvious way to control configuration. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/bc8490bb/attachment.pgp From michel at lpthe.jussieu.fr Thu Aug 7 12:01:27 2008 From: michel at lpthe.jussieu.fr (Michel Talon) Date: Thu Aug 7 12:38:29 2008 Subject: USB key && kernel: da0: ... Message-ID: <20080807120122.GA15142@lpthe.jussieu.fr> > Matthias Apitz wrote: > Aug 6 10:06:12 rebelion kernel: umass0: on uhub4 > Aug 6 10:06:12 rebelion root: Unknown USB device: vendor 0x08ec product 0x0020 bus uhub4 > Aug 6 10:06:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 10:06:12 > rebelion kernel: da0: Removable Direct Access SCSI-0 device > Aug 6 10:06:12 rebelion kernel: da0: 40.000MB/s transfers > Aug 6 10:06:12 rebelion kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > Here is another example: Aug 5 14:48:59 niobe kernel: umass0: on uhub3 Aug 5 14:48:59 niobe root: Unknown USB device: vendor 0x0951 product 0x1603 bus uhub3 Aug 5 14:48:59 niobe kernel: da1 at umass-sim0 bus 0 target 0 lun 0 Aug 5 14:48:59 niobe kernel: da1: Removable Direct Access SCSI-2 device Aug 5 14:48:59 niobe kernel: da1: 40.000MB/s transfers Aug 5 14:48:59 niobe kernel: da1: 1905MB (3902464 512 byte sectors: 255H 63S/T 242C) Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR Aug 5 14:55:57 niobe kernel: umass0: at uhub3 port 5 (addr 2) disconnected Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): lost device Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): removing device entry Aug 5 14:55:57 niobe kernel: umass0: detached Needless to say, this stick works perfectly OK under Windows and Linux. -- Michel TALON From rpaulo at freebsd.org Thu Aug 7 12:43:46 2008 From: rpaulo at freebsd.org (Rui Paulo) Date: Thu Aug 7 12:44:17 2008 Subject: Suggestion for 'pkg_add -r' In-Reply-To: References: Message-ID: <1234BBCE-6698-4EF9-8B48-4F291AD78547@freebsd.org> On 7 Aug 2008, at 11:53, Anders Nore wrote: > Hi, > > In my pkg_improved GSoC project I've added a nice feature for > 'pkg_add -r' which displays the size of the file being downloaded as > well as progress status in % and bytes/kb/mb/... and download speed. > If someone could test it and comment it would be perfect, below you > can find the patches for RELENG_7 and -CURRENT. (As for now pkg_add > does not have a -q/Q option (quiet), but this could perhaps be used > to deprecate the output?). > > RELENG_7: > http://home.no.net/andenore/patches/pkg_install_2008-08-06_RELENG_7.diff > > CURRENT: > http://home.no.net/andenore/patches/ > pkg_install_2008-08-06_CURRENT.diff Some comments: * I think you have reversed the patch. :-) * Build errors: cc1: warnings being treated as errors file.c:433: warning: no previous prototype for 'power' file.c:452: warning: no previous prototype for 'human_readable' file.c:474: warning: no previous prototype for 'printHumanReadable' file.c: In function 'printHumanReadable': file.c:482: warning: comparison between signed and unsigned parallels# ./pkg_add -r joe Fetching 321.2 kB from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/Latest/joe.tbz ... Downloading: 100% 321.2 kB at 214.8 kB/ s Done Fetching 2.4 MB from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/gettext-0.17_1.tbz ... Done Fetching 2.2 MB from ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/aspell-0.60.6_2.tbz ... Downloading: 201% 4.5 MB at 149.5 kB/s Something's wrong :-) Also, may I suggest that you make your output similar to fetch(1) ? Keep up the good work, -- Rui Paulo From des at des.no Thu Aug 7 12:49:58 2008 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Thu Aug 7 12:50:04 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807090230.GF1359@server.vk2pj.dyndns.org> (Peter Jeremy's message of "Thu, 7 Aug 2008 19:02:30 +1000") References: <20080807090230.GF1359@server.vk2pj.dyndns.org> Message-ID: <86r691f0qy.fsf@ds4.des.no> Peter Jeremy writes: > So you take each line from inetd.conf (literally) and wrap it in > several KB of XML. This definitely adds to bloat and doesn't even > obey the spirit of XML (since the content of each inetd.conf entry > remains opaque). s/inetd/rc/g I completely agree with you - but I also agree with whoever it was that suggested adding enable / disable commands to rc.subr. DES -- Dag-Erling Sm?rgrav - des@des.no From guru at unixarea.de Thu Aug 7 12:50:28 2008 From: guru at unixarea.de (Matthias Apitz) Date: Thu Aug 7 12:50:35 2008 Subject: USB key && kernel: da0: ... In-Reply-To: <20080807120122.GA15142@lpthe.jussieu.fr> References: <20080807120122.GA15142@lpthe.jussieu.fr> Message-ID: <20080807125023.GA3605@rebelion.Sisis.de> El d?a Thursday, August 07, 2008 a las 02:01:22PM +0200, Michel Talon escribi?: > > Matthias Apitz wrote: > > Aug 6 10:06:12 rebelion kernel: umass0: on uhub4 > > Aug 6 10:06:12 rebelion root: Unknown USB device: vendor 0x08ec product 0x0020 bus uhub4 > > Aug 6 10:06:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 10:06:12 > > rebelion kernel: da0: Removable Direct Access SCSI-0 device > > Aug 6 10:06:12 rebelion kernel: da0: 40.000MB/s transfers > > Aug 6 10:06:12 rebelion kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > > > > Here is another example: > > Aug 5 14:48:59 niobe kernel: umass0: on uhub3 > Aug 5 14:48:59 niobe root: Unknown USB device: vendor 0x0951 product 0x1603 bus uhub3 > Aug 5 14:48:59 niobe kernel: da1 at umass-sim0 bus 0 target 0 lun 0 > Aug 5 14:48:59 niobe kernel: da1: Removable Direct Access SCSI-2 device > Aug 5 14:48:59 niobe kernel: da1: 40.000MB/s transfers > Aug 5 14:48:59 niobe kernel: da1: 1905MB (3902464 512 byte sectors: 255H 63S/T 242C) > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR ... Have you plug'ed in or out while writing to da1 another device in the USB? I saw this as well with a USB key which worked normaly until I did a plug'in/out on the bus; matthias -- Matthias Apitz Manager Technical Support - OCLC GmbH Gruenwalder Weg 28g - 82041 Oberhaching - Germany t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.oclc.org/ http://www.UnixArea.de/ b http://gurucubano.blogspot.com/ We should all learn from the peoples of The Netherlands, France and Ireland. Aprendamos todos de los pueblos de Holanda, Francia e Irlanda. From koitsu at FreeBSD.org Thu Aug 7 12:50:46 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 12:50:53 2008 Subject: USB key && kernel: da0: ... In-Reply-To: <20080807120122.GA15142@lpthe.jussieu.fr> References: <20080807120122.GA15142@lpthe.jussieu.fr> Message-ID: <20080807125045.GA29669@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 02:01:22PM +0200, Michel Talon wrote: > > Matthias Apitz wrote: > > Aug 6 10:06:12 rebelion kernel: umass0: on uhub4 > > Aug 6 10:06:12 rebelion root: Unknown USB device: vendor 0x08ec product 0x0020 bus uhub4 > > Aug 6 10:06:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 10:06:12 > > rebelion kernel: da0: Removable Direct Access SCSI-0 device > > Aug 6 10:06:12 rebelion kernel: da0: 40.000MB/s transfers > > Aug 6 10:06:12 rebelion kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > > Here is another example: > > Aug 5 14:48:59 niobe kernel: umass0: on uhub3 > Aug 5 14:48:59 niobe root: Unknown USB device: vendor 0x0951 product 0x1603 bus uhub3 > Aug 5 14:48:59 niobe kernel: da1 at umass-sim0 bus 0 target 0 lun 0 > Aug 5 14:48:59 niobe kernel: da1: Removable Direct Access SCSI-2 device > Aug 5 14:48:59 niobe kernel: da1: 40.000MB/s transfers > Aug 5 14:48:59 niobe kernel: da1: 1905MB (3902464 512 byte sectors: 255H 63S/T 242C) > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > Aug 5 14:55:57 niobe kernel: umass0: at uhub3 port 5 (addr 2) disconnected > Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): lost device > Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): removing device entry > Aug 5 14:55:57 niobe kernel: umass0: detached > > Needless to say, this stick works perfectly OK under Windows and Linux. I have the 4GB model of this USB stick/drive. I'll give it a try on my FreeBSD RELENG_7 box when I get home in about an hour. If I can reproduce the issue, I will be more than happy to send it to someone who wants to debug it (and they can keep it as my way of saying thanks). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From talon at lpthe.jussieu.fr Thu Aug 7 13:34:58 2008 From: talon at lpthe.jussieu.fr (Michel Talon) Date: Thu Aug 7 13:44:29 2008 Subject: USB key && kernel: da0: ... Message-ID: <20080807133454.GA15519@lpthe.jussieu.fr> Matthias Apitz wrote: > Have you plug'ed in or out while writing to da1 another device in the > USB? I saw this as well with a USB key which worked normaly until I did > a plug'in/out on the bus; No, i did not touch to the usb bus. I tried to use the stick on several FreeBSD machines, without any success. One of them paniced. I had to reboot to Windows to read the stick and then download it from here for FreeBSD :-( -- Michel TALON From andenore at freebsd.org Thu Aug 7 13:50:37 2008 From: andenore at freebsd.org (Anders Nore) Date: Thu Aug 7 13:50:46 2008 Subject: Suggestion for 'pkg_add -r' In-Reply-To: <1234BBCE-6698-4EF9-8B48-4F291AD78547@freebsd.org> References: <1234BBCE-6698-4EF9-8B48-4F291AD78547@freebsd.org> Message-ID: >> >> RELENG_7: >> http://home.no.net/andenore/patches/pkg_install_2008-08-06_RELENG_7.diff >> >> CURRENT: >> http://home.no.net/andenore/patches/pkg_install_2008-08-06_CURRENT.diff > > Some comments: > * I think you have reversed the patch. :-) > * Build errors: > cc1: warnings being treated as errors > file.c:433: warning: no previous prototype for 'power' > file.c:452: warning: no previous prototype for 'human_readable' > file.c:474: warning: no previous prototype for 'printHumanReadable' > file.c: In function 'printHumanReadable': > file.c:482: warning: comparison between signed and unsigned > > parallels# ./pkg_add -r joe > Fetching 321.2 kB from > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/Latest/joe.tbz > ... > Downloading: 100% 321.2 kB at > 214.8 kB/s > Done > Fetching 2.4 MB from > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/gettext-0.17_1.tbz > ... > Done > Fetching 2.2 MB from > ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/aspell-0.60.6_2.tbz > ... > Downloading: 201% 4.5 MB at > 149.5 kB/s > > Something's wrong :-) > Heh, yes. It's my first patch(es), so it didn't go as well as I had hoped, I believe they are fixed now. The numbers for percentage should also be corrected :-) > Also, may I suggest that you make your output similar to fetch(1) ? Yes, I will work on making it similar Thanks, Anders Nore From koitsu at FreeBSD.org Thu Aug 7 14:15:18 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 14:15:24 2008 Subject: USB key && kernel: da0: ... In-Reply-To: <20080807125045.GA29669@eos.sc1.parodius.com> References: <20080807120122.GA15142@lpthe.jussieu.fr> <20080807125045.GA29669@eos.sc1.parodius.com> Message-ID: <20080807141517.GA32272@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 05:50:45AM -0700, Jeremy Chadwick wrote: > On Thu, Aug 07, 2008 at 02:01:22PM +0200, Michel Talon wrote: > > > Matthias Apitz wrote: > > > Aug 6 10:06:12 rebelion kernel: umass0: on uhub4 > > > Aug 6 10:06:12 rebelion root: Unknown USB device: vendor 0x08ec product 0x0020 bus uhub4 > > > Aug 6 10:06:12 rebelion kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 6 10:06:12 > > > rebelion kernel: da0: Removable Direct Access SCSI-0 device > > > Aug 6 10:06:12 rebelion kernel: da0: 40.000MB/s transfers > > > Aug 6 10:06:12 rebelion kernel: da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > > > > Here is another example: > > > > Aug 5 14:48:59 niobe kernel: umass0: on uhub3 > > Aug 5 14:48:59 niobe root: Unknown USB device: vendor 0x0951 product 0x1603 bus uhub3 > > Aug 5 14:48:59 niobe kernel: da1 at umass-sim0 bus 0 target 0 lun 0 > > Aug 5 14:48:59 niobe kernel: da1: Removable Direct Access SCSI-2 device > > Aug 5 14:48:59 niobe kernel: da1: 40.000MB/s transfers > > Aug 5 14:48:59 niobe kernel: da1: 1905MB (3902464 512 byte sectors: 255H 63S/T 242C) > > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB reset failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-in clear stall failed, IOERROR > > Aug 5 14:49:25 niobe kernel: umass0: BBB bulk-out clear stall failed, IOERROR > > Aug 5 14:55:57 niobe kernel: umass0: at uhub3 port 5 (addr 2) disconnected > > Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): lost device > > Aug 5 14:55:57 niobe kernel: (da1:umass-sim0:0:0:0): removing device entry > > Aug 5 14:55:57 niobe kernel: umass0: detached > > > > Needless to say, this stick works perfectly OK under Windows and Linux. > > I have the 4GB model of this USB stick/drive. I'll give it a try on my > FreeBSD RELENG_7 box when I get home in about an hour. > > If I can reproduce the issue, I will be more than happy to send it to > someone who wants to debug it (and they can keep it as my way of saying > thanks). As promised, when I got home I inserted the Kingston I have. I should note this disk was formatted as FAT32 on a Windows machine, and was also made bootable via a Windows utility made by Hewlett Packard. This is what I got upon inserting the device: umass0: on uhub4 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 3836MB (7856128 512 byte sectors: 255H 63S/T 489C) GEOM_LABEL: Label for provider da0s1 is msdosfs/KINGSTON. icarus# camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) icarus# camcontrol inquiry da0 pass0: Removable Direct Access SCSI-2 device pass0: Serial Number 40.000MB/s transfers icarus# mount_msdosfs /dev/da0s1 /mnt icarus# df -k /mnt Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/da0s1 3920364 12 3920352 0% /mnt This looks correct (there is no data on the FAT32 filesystem). icarus# umount /mnt icarus# I then removed the stick, and got this: umass0: at uhub4 port 6 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost deviceGEOM_LABEL (da0:umass-sim0:0:: 0:Label 0): msdosfs/KINGSTON removeremoving device entryd. umass0: detached Kernel messages are being printed atop one another is a known bug (it really needs to get fixed already, since increasing PRINTF_BUFR_SIZE to 256 only makes the problem slightly better), but as you can see, it worked fine. I'm thinking this may boil down to a problem with udbp(4) getting in the way, since it's responsible for the bulk (BBB) stuff. I yank udbp(4) out of my kernel because I don't see the point in including support for something I'll never use. (And are "bulk pipes" even part of the USB standard? I don't remember reading about them as part of the USB 1.0 specification, but that was a long time ago.) Here's the relevant portion of my kernel configuration: # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse I can provide full dmesg output if need be. Chipset is an Intel ICH7. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From Oleg.Ginzburg at billing.ru Thu Aug 7 14:16:29 2008 From: Oleg.Ginzburg at billing.ru (Ginzburg, Oleg) Date: Thu Aug 7 14:16:36 2008 Subject: Samba, Response too big for UDP, retry with TCP, Kerberos implementation on FreeBSD Message-ID: <04DB0C1CEA12F2449D23EDB4D0A138A8C782794195@srv-exch01.billing.ru> //sorry for spamming to another freebsd-ports maillist. This channel is more suitable// Hello, I receive a similar problem in a current configuration (FreeBSD 7.0-Release amd64, samba-3.0.31_1) like this: http://lists.samba.org/archive/samba/2007-July/133625.html and most likely I assume problems both in Samba and in realization Kerberos on FreeBSD (IMHO Samba more:) The problem consists that during the generation phase (libads/kerberos.c:create_local_private_krb5_conf_for_domain) of temporary file /var/db/samba/smb_krb5/krb5.conf. is lost the instruction for transport protocol (if they present in /etc/krb5.conf) So, temporary workaround for this problem looks like: 1) After unsuccessful execution $ net ads join ... Edit a file /var/db/samba/smb_krb5/krb5.conf., having added before server a "tcp/" (of course, only if tcp proto is necessary tcp also it should be present in/etc/krd5.conf): -- [realms] = { kdc = tcp/ ... } -- 2) Then set forbid modification on a file chflags schg /var/db/samba/smb_krb5/krb5.conf. 3) And trying "net join " again, with ignoring of rename error (create_local_private_krb5_conf_for_domain: rename of /var/db/samba/smb_tmp_krb5.IQraHE to /var/db/samba/smb_krb5/krb5.conf. failed. Errno Operation not permitted..) Operation must end with success execution. Question - Whether two (FreeBSD/Samba) problems are valid here? (Samba generate not corrected file)+(Heimdal Kerberos FreeBSD not trying force a tcp? PS: similar problem are not present in MIT Kerberos (/usr/ports/security/krb5)) -- CJSC "PETER-SERVICE" ============================ Direct: +7 812 3261290 ext. 0423 Tel: +7 812 3261299 Fax: +7 812 3261298 E-mail: Oleg.Ginzburg@billing.ru URL: http://www.billing.ru From jan.grant at bristol.ac.uk Thu Aug 7 14:17:18 2008 From: jan.grant at bristol.ac.uk (Jan Grant) Date: Thu Aug 7 14:17:25 2008 Subject: Idea for FreeBSD In-Reply-To: <86r691f0qy.fsf@ds4.des.no> References: <20080807090230.GF1359@server.vk2pj.dyndns.org> <86r691f0qy.fsf@ds4.des.no> Message-ID: <20080807145747.L3840@tribble.ilrt.bris.ac.uk> On Thu, 7 Aug 2008, Dag-Erling Sm?rgrav wrote: > Peter Jeremy writes: > > So you take each line from inetd.conf (literally) and wrap it in > > several KB of XML. This definitely adds to bloat and doesn't even > > obey the spirit of XML (since the content of each inetd.conf entry > > remains opaque). > > s/inetd/rc/g > > I completely agree with you - but I also agree with whoever it was that > suggested adding enable / disable commands to rc.subr. inetd.conf too(!); see inetconv(1M) Whilst solaris has some nice bits and pieces, the tendency to take configuration (static and dynamic) and shove it into an opaque database I personally find problematic: compare the ISC and solaris dhcp servers, for instance. enable/disable sound interesting, however. jan -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ ...You're visualising the _duck_ taped over my _mouth_..? From gabor at kovesdan.org Thu Aug 7 15:04:33 2008 From: gabor at kovesdan.org (Gabor Kovesdan) Date: Thu Aug 7 15:49:15 2008 Subject: strange issue reading /dev/null Message-ID: <489B0ACD.80008@kovesdan.org> Hello, I'm wondering why fgetc() returns 0xff if called with /dev/null: #include #include int main(void) { int c; FILE *f; f = fopen("/dev/null", "r"); if (c != EOF) printf("%c\n", fgetc(f)); } > gcc foo.c > ./a.out ? This causes a bug in BSD grep as /dev/null is not distinguished from ordinary files in the code, thus I was expecting it just returned EOF, but in reality this is not the case. How such cases should be handled? Thanks in advance, G?bor From mwm at mired.org Thu Aug 7 15:25:42 2008 From: mwm at mired.org (Mike Meyer) Date: Thu Aug 7 15:49:16 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807061500.GA23109@ravenloft.kiev.ua> References: <20080807061500.GA23109@ravenloft.kiev.ua> Message-ID: <20080807112539.65380404@mbook.local> On Thu, 7 Aug 2008 09:15:00 +0300 Alex Kozlov wrote: > [1]: > $cat /usr/local/bin/service Basically what I had in mind, but it can be made more portable across FreeBSD configurations. > #!/bin/sh > > name=$1 > cmd=$2 > > . /etc/rc.subr > if [ -z "${name}" -o -z "${cmd}" ] > then > echo ${0##*/} service_name command > exit 3 > fi > > > if [ -r "/etc/rc.d/${name}" ] > then > run_rc_script "/etc/rc.d/${name}" ${cmd} > exit 0 > fi And here's where you go wrong. What you want now is: for dir in $local_startup; do if [ -r "${dir}/${name}" ] then run_rc_script "${dir}/${name}" ${cmd} exit 0 fi if [ -r "${dir}/${name}.sh" ] then run_rc_script "${dir}/${name}.sh" ${cmd} exit 0 fi done > > echo "service '${name}' not found" > exit 2 Thanks, http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From mwm at mired.org Thu Aug 7 15:44:47 2008 From: mwm at mired.org (Mike Meyer) Date: Thu Aug 7 15:49:34 2008 Subject: Idea for FreeBSD In-Reply-To: <489A9344.3060306@freebsd.org> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> <489A9344.3060306@freebsd.org> Message-ID: <20080807114444.234d1887@mbook.local> On Wed, 06 Aug 2008 23:16:36 -0700 Tim Kientzle wrote: > > The Solaris smf tools provide some nice facilities: one is single > > interface to start, stop, check and restart all the services on a > > system. We pretty much have that ... > > > > The other is a single interface to enable, disable and query the > > status of all the services. All we really have is the last one... > > Sounds like the only missing pieces, then, are standard > ways to enable, disable, and configure services. How about: > > sudo /etc/rc.d/ssh enable > sudo /etc/rc.d/ssh disable > sudo /etc/rc.d/ssh configure > > That shouldn't be much of a stretch to implement, either. > The first two just append entries to /etc/rc.conf. The > third opens an editor with a list of variables supported > by this service and then appends the result to rc.conf. Well, that might work, but could lead to unintended consequences if you start missing settings from two different configure runs by continually appending without deleting the old settings. load_rc_config already sources /etc/rc.conf.d/"$_name". Working with that file instead of /etc/rc.conf would seem to be a cleaner solution. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From scf at FreeBSD.org Thu Aug 7 16:16:08 2008 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 7 16:16:14 2008 Subject: strange issue reading /dev/null In-Reply-To: <489B0ACD.80008@kovesdan.org> References: <489B0ACD.80008@kovesdan.org> Message-ID: On Thu, 7 Aug 2008, Gabor Kovesdan wrote: > Hello, > > I'm wondering why fgetc() returns 0xff if called with /dev/null: > > #include > #include > > int > main(void) > { > int c; > FILE *f; > > f = fopen("/dev/null", "r"); > > if (c != EOF) > printf("%c\n", fgetc(f)); > } > >> gcc foo.c >> ./a.out > ? > > This causes a bug in BSD grep as /dev/null is not distinguished from > ordinary files in the code, thus I was expecting it just returned EOF, > but in reality this is not the case. How such cases should be handled? You are testing c which has not been set. It works OK if you set c then do the test: + c = fgetc(f); if (c != EOF) - printf("%c\n", fgetc(f)); + printf("%c\n", c); Sean -- scf@FreeBSD.org From deischen at freebsd.org Thu Aug 7 16:21:11 2008 From: deischen at freebsd.org (Daniel Eischen) Date: Thu Aug 7 16:21:18 2008 Subject: strange issue reading /dev/null In-Reply-To: <489B0ACD.80008@kovesdan.org> References: <489B0ACD.80008@kovesdan.org> Message-ID: On Thu, 7 Aug 2008, Gabor Kovesdan wrote: > Hello, > > I'm wondering why fgetc() returns 0xff if called with /dev/null: > > #include > #include > > int > main(void) > { > int c; > FILE *f; > > f = fopen("/dev/null", "r"); > > if (c != EOF) > printf("%c\n", fgetc(f)); > } Hmmm, are you *sure* your code should not be written as follows: #include #include int main(int argc, char **argv) { FILE *f; int c; f = fopen("/dev/null", "r"); if (f != NULL) { c = fgetc(f); if (c != EOF) printf("%c\n", c); else printf("EOF encountered\n"); } return (0); } -- DE From koitsu at FreeBSD.org Thu Aug 7 16:25:08 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 16:25:15 2008 Subject: strange issue reading /dev/null In-Reply-To: <489B0ACD.80008@kovesdan.org> References: <489B0ACD.80008@kovesdan.org> Message-ID: <20080807162508.GA37318@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 04:46:37PM +0200, Gabor Kovesdan wrote: > Hello, > > I'm wondering why fgetc() returns 0xff if called with /dev/null: > > #include > #include > > int > main(void) > { > int c; > FILE *f; > > f = fopen("/dev/null", "r"); > > if (c != EOF) > printf("%c\n", fgetc(f)); > } > > > gcc foo.c > > ./a.out > ? > > This causes a bug in BSD grep as /dev/null is not distinguished from > ordinary files in the code, thus I was expecting it just returned EOF, > but in reality this is not the case. How such cases should be handled? Your code is wrong -- you're not calling feof(). Please read the RETURN VALUES section of fgetc(3) in full, and slowly. :-) And your if() statement serves no purpose there. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From scf at FreeBSD.org Thu Aug 7 16:54:13 2008 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 7 16:54:19 2008 Subject: strange issue reading /dev/null In-Reply-To: <489B22BD.5050109@kovesdan.org> References: <489B0ACD.80008@kovesdan.org> <489B22BD.5050109@kovesdan.org> Message-ID: On Thu, 7 Aug 2008, Gabor Kovesdan wrote: > Sean C. Farley ha scritto: >> You are testing c which has not been set. It works OK if you set c >> then do the test: >> >> + c = fgetc(f); >> if (c != EOF) >> - printf("%c\n", fgetc(f)); >> + printf("%c\n", c); > Yes, you are right, this is what I meant, I'm just a bit > disorganised.... > Thanks! You are welcome. Actually, what I found odd was that the base gcc did not warn about using an uninitialized variable using -Wall. Obviously, test fopen() and fgetc() return codes correctly as others have noted. I just assume you were not in your test program. Sean -- scf@FreeBSD.org From koitsu at FreeBSD.org Thu Aug 7 17:02:36 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 7 17:02:42 2008 Subject: strange issue reading /dev/null In-Reply-To: References: <489B0ACD.80008@kovesdan.org> <489B22BD.5050109@kovesdan.org> Message-ID: <20080807170235.GA39461@eos.sc1.parodius.com> On Thu, Aug 07, 2008 at 11:54:10AM -0500, Sean C. Farley wrote: > On Thu, 7 Aug 2008, Gabor Kovesdan wrote: > >> Sean C. Farley ha scritto: >>> You are testing c which has not been set. It works OK if you set c >>> then do the test: >>> >>> + c = fgetc(f); >>> if (c != EOF) >>> - printf("%c\n", fgetc(f)); >>> + printf("%c\n", c); >> Yes, you are right, this is what I meant, I'm just a bit >> disorganised.... >> Thanks! > > You are welcome. > > Actually, what I found odd was that the base gcc did not warn about > using an uninitialized variable using -Wall. Probably because you didn't use -O. -Wall includes -Wuninitialized, but -Wuninitialized only applies if you use optimisation. gcc won't bail if you use -Wall without -O, for obvious reasons. Case in point: $ gcc -Wall -o x x.c x.c: In function 'main': x.c:14: warning: control reaches end of non-void function $ gcc -Wuninitialized -o x x.c cc1: warning: -Wuninitialized is not supported without -O $ gcc -Wall -O -o x x.c x.c: In function 'main': x.c:14: warning: control reaches end of non-void function x.c:12: warning: 'c' is used uninitialized in this function gcc -- finding new ways every day to drive programmers crazy. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From gabor at kovesdan.org Thu Aug 7 16:28:58 2008 From: gabor at kovesdan.org (Gabor Kovesdan) Date: Thu Aug 7 17:04:05 2008 Subject: strange issue reading /dev/null In-Reply-To: References: <489B0ACD.80008@kovesdan.org> Message-ID: <489B22BD.5050109@kovesdan.org> Sean C. Farley ha scritto: > You are testing c which has not been set. It works OK if you set c then > do the test: > > + c = fgetc(f); > if (c != EOF) > - printf("%c\n", fgetc(f)); > + printf("%c\n", c); Yes, you are right, this is what I meant, I'm just a bit disorganised.... Thanks! G?bor From scf at FreeBSD.org Thu Aug 7 17:19:23 2008 From: scf at FreeBSD.org (Sean C. Farley) Date: Thu Aug 7 17:19:29 2008 Subject: strange issue reading /dev/null In-Reply-To: <20080807170235.GA39461@eos.sc1.parodius.com> References: <489B0ACD.80008@kovesdan.org> <489B22BD.5050109@kovesdan.org> <20080807170235.GA39461@eos.sc1.parodius.com> Message-ID: On Thu, 7 Aug 2008, Jeremy Chadwick wrote: > On Thu, Aug 07, 2008 at 11:54:10AM -0500, Sean C. Farley wrote: >> On Thu, 7 Aug 2008, Gabor Kovesdan wrote: >>> Sean C. Farley ha scritto: >>>> You are testing c which has not been set. It works OK if you set c >>>> then do the test: >>>> >>>> + c = fgetc(f); >>>> if (c != EOF) >>>> - printf("%c\n", fgetc(f)); >>>> + printf("%c\n", c); >>> Yes, you are right, this is what I meant, I'm just a bit >>> disorganised.... >>> Thanks! >> >> You are welcome. >> >> Actually, what I found odd was that the base gcc did not warn about >> using an uninitialized variable using -Wall. > > Probably because you didn't use -O. -Wall includes -Wuninitialized, > but -Wuninitialized only applies if you use optimisation. gcc won't > bail if you use -Wall without -O, for obvious reasons. Case in point: You are correct; I did not use -O. > $ gcc -Wall -o x x.c > x.c: In function 'main': > x.c:14: warning: control reaches end of non-void function > > $ gcc -Wuninitialized -o x x.c > cc1: warning: -Wuninitialized is not supported without -O Heh. > $ gcc -Wall -O -o x x.c > x.c: In function 'main': > x.c:14: warning: control reaches end of non-void function > x.c:12: warning: 'c' is used uninitialized in this function > > gcc -- finding new ways every day to drive programmers crazy. :-) Grr! Optimization should not be a requirement for checking for uninitialized variables. Yes, gcc adds "fun" to development. Sean -- scf@FreeBSD.org From spam at rm-rf.kiev.ua Thu Aug 7 17:26:56 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Thu Aug 7 17:27:05 2008 Subject: Idea for FreeBSD Message-ID: <20080807172650.GA56516@ravenloft.kiev.ua> On Thu, Aug 07, 2008 at 11:29:49AM +0100, Matthew Seaman wrote: > Jeremy Chadwick wrote: > > On Wed, Aug 06, 2008 at 07:14:51PM -0400, wbentley@futurecis.com wrote: > >> To who it may concern, > >> > >> I am A FreeBSD administrator as well as a Solaris Administrator. I use > >> BSD at home but Solaris at work. I love both OS's but I would like to > >> increase the administrative capability of FreeBSD. > >> > >> In Solaris 10 the Services Management Facility (SMF) was introduced. > >> Basically what it does, is take all the rc.d scripts and puts them into > >> a database to manage. Everything is converted to XML and two basic > >> commands (svcs and svcadm) are used to manage everything. > > > > I highly recommend you and anyone advocating the use of XML for such > > things read the following whitepaper/study, in full: > > > > http://www.cs.kent.ac.uk/pubs/2004/2102/content.pdf > > > > Heh. Loved all the little asides to Nancy... Amazing it hasn't been > fixed in 4 years. > > Anyhow, yes: ASN.1 is smaller, and hence faster than XML for networked > applications. Which is fine, but as far as I can see doesn't address the > question at hand. > > There are two connected questions here: > > * What technology should be used to implement the FreeBSD rc.subr > system? > > * What functionality could or should be added to the FreeBSD rc.subr > system? > > Where the answer to the first question clearly constrains the results > of the second. So what are the requirements for the rc system? Off > the top of my head -- and I've probably missed some vital considerations > here -- in order of priority: > > 1 reliability. The system has to boot up. > > 2 repeatability. The system has to boot up in a consistent state > > 3 fault tolerance. The system cannot fail to boot up unless the > problems really are terminal. > > 4 configurability. The system has to boot up correctly for all > conceivable combinations of hardware and software. > > 5 portability. Should run on anything from the smallest of > embedded devices to the most enormous high power super computers > to the most transient of virtualized hosts. > > 6 manageability. Must be comprehensible by ordinary mortals. > > 7 efficiency. Must bring the system up as fast as is practicable and > without excessive use of system resources > > What does XML-based technology bring to this? As the OP states the primary > benefit is in manageability. I would contend that the advantage claimed > here is rather less significant than indicated. We already have a central > database of configuration information -- /etc/rc.conf -- and while we don't > have one single application to control starting and stopping services we > have the next best thing: a consistent user interface for calling the > individual rc-scripts. Indeed, as other posters have shown elsewhere in > this thread, adding that sort of functionality is only a Small Matter of > Programming using the existing tools. > > What's wrong wwith using XML? XML adds significantly to the complexity of > an rc system -- it's suddenly necessary to have another shlib or two and > several compiled applications available early in the boot process. XML > itself is too general-purpose: it has too much baggage designed for its > primary function of facilitating interoperation between diverse systems in > different zones of control, none of which is particularly applicable to > system startup. While in general I agree with You, I must note that We already have xml parser (expat 1.95) for geom. See /lib/libbsdxml.so* -- Adios From gabor at kovesdan.org Thu Aug 7 16:58:30 2008 From: gabor at kovesdan.org (Gabor Kovesdan) Date: Thu Aug 7 17:39:12 2008 Subject: strange issue reading /dev/null In-Reply-To: References: <489B0ACD.80008@kovesdan.org> <489B22BD.5050109@kovesdan.org> Message-ID: <489B29A9.1090609@kovesdan.org> Sean C. Farley ha scritto: > On Thu, 7 Aug 2008, Gabor Kovesdan wrote: > >> Sean C. Farley ha scritto: >>> You are testing c which has not been set. It works OK if you set c >>> then do the test: >>> >>> + c = fgetc(f); >>> if (c != EOF) >>> - printf("%c\n", fgetc(f)); >>> + printf("%c\n", c); >> Yes, you are right, this is what I meant, I'm just a bit >> disorganised.... >> Thanks! > > You are welcome. > > Actually, what I found odd was that the base gcc did not warn about > using an uninitialized variable using -Wall. > > Obviously, test fopen() and fgetc() return codes correctly as others > have noted. I just assume you were not in your test program. Actaually, I wanted to track down why BSD grep echoed the y with the diaresis when I executed grep . References: <20080805094013.GA5654@rebelion.Sisis.de> Message-ID: <20080807184329.GA52790@walton.maths.tcd.ie> On Tue, Aug 05, 2008 at 11:40:13AM +0200, Matthias Apitz wrote: > What means 'Header with wrong dumpdate'? It's a warning message that probably shouldn't be printed, but has no impact other than the printing of the warning. We've fixed bug that causes it to be printed recently. David. From dwmalone at maths.tcd.ie Thu Aug 7 18:47:39 2008 From: dwmalone at maths.tcd.ie (David Malone) Date: Thu Aug 7 18:47:45 2008 Subject: IPv6 CVS In-Reply-To: <20080805223409.620e5044@tau.draftnet> References: <000301c8f6df$e1006ae0$a30140a0$@com> <55592.192.168.1.10.1217929950.squirrel@192.168.1.100> <20080805141450.T60740@mp2.macomnet.net> <20080805105057.GC1450@ted.stsp.name> <000801c8f6eb$111622f0$334268d0$@com> <20080805122817.GA89022@eos.sc1.parodius.com> <20080805223409.620e5044@tau.draftnet> Message-ID: <20080807184731.GB52790@walton.maths.tcd.ie> On Tue, Aug 05, 2008 at 10:34:09PM +0100, Bruce Cran wrote: > The problem is cvsupd - since it's written in Modula3 and doesn't > support IPv6 you have to use an inetd/netcat hack to accept IPv6 > connections on the server. As mentioned in > http://lists.freebsd.org/pipermail/freebsd-current/2008-July/086710.html > cvsup18.freebsd.org and cvsup4.ru.freebsd.org both accept IPv6 > connections. cvsup.ie.freebsd.org also offers cvsup over IPv6: http://lists.freebsd.org/pipermail/freebsd-stable/2003-July/001983.html Amazingly, it was announced exactly 5 years to the day before the message about cvsup18 above. David. From peterjeremy at optushome.com.au Thu Aug 7 19:07:07 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Aug 7 19:07:16 2008 Subject: strange issue reading /dev/null In-Reply-To: References: <489B0ACD.80008@kovesdan.org> <489B22BD.5050109@kovesdan.org> <20080807170235.GA39461@eos.sc1.parodius.com> Message-ID: <20080807190701.GJ64458@server.vk2pj.dyndns.org> On 2008-Aug-07 12:19:20 -0500, "Sean C. Farley" wrote: >Grr! Optimization should not be a requirement for checking for >uninitialized variables. Yes, gcc adds "fun" to development. This is documented: `-Wuninitialized' Warn if an automatic variable is used without first being initialized or if a variable may be clobbered by a `setjmp' call. These warnings are possible only in optimizing compilation, because they require data flow information that is computed only when optimizing. If you do not specify `-O', you will not get these warnings. Instead, GCC will issue a warning about `-Wuninitialized' requiring `-O'. That explanation makes sense. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/aab2e92f/attachment.pgp From ken at mthelicon.com Thu Aug 7 19:48:46 2008 From: ken at mthelicon.com (Pegasus Mc cleaft) Date: Thu Aug 7 19:48:54 2008 Subject: IPv6 CVS In-Reply-To: <20080807184731.GB52790@walton.maths.tcd.ie> References: <000301c8f6df$e1006ae0$a30140a0$@com> <20080805223409.620e5044@tau.draftnet> <20080807184731.GB52790@walton.maths.tcd.ie> Message-ID: <200808072048.39358.ken@mthelicon.com> On Thursday 07 August 2008 19:47:31 David Malone wrote: > On Tue, Aug 05, 2008 at 10:34:09PM +0100, Bruce Cran wrote: > > The problem is cvsupd - since it's written in Modula3 and doesn't > > support IPv6 you have to use an inetd/netcat hack to accept IPv6 > > connections on the server. As mentioned in > > http://lists.freebsd.org/pipermail/freebsd-current/2008-July/086710.html > > cvsup18.freebsd.org and cvsup4.ru.freebsd.org both accept IPv6 > > connections. > > cvsup.ie.freebsd.org also offers cvsup over IPv6: > > http://lists.freebsd.org/pipermail/freebsd-stable/2003-July/001983.html Thanks David, I just tried cvsup.ie.freebsd.org and it worked a treat as well.. I appreciate the information. > Amazingly, it was announced exactly 5 years to the day before the > message about cvsup18 above. Synchronisities... Dont you just love them ;> I thought about setting up a v6 cvsup server, if the community thought that another mirror would be useful. Don't know how that may be received, however.. Useful or just redundant? Peg From lars.engels at 0x20.net Thu Aug 7 20:18:20 2008 From: lars.engels at 0x20.net (Lars Engels) Date: Thu Aug 7 20:31:10 2008 Subject: Idea for FreeBSD In-Reply-To: <489A9344.3060306@freebsd.org> References: <78c6bd860808061934l133d8ca6nabbde8cd55cb1d27@mail.gmail.com> <20080807010638.267d7790@bhuda.mired.org> <489A9344.3060306@freebsd.org> Message-ID: <20080807201818.GS56464@e.0x20.net> On Wed, Aug 06, 2008 at 11:16:36PM -0700, Tim Kientzle wrote: > >The Solaris smf tools provide some nice facilities: one is single > >interface to start, stop, check and restart all the services on a > >system. We pretty much have that ... > >The other is a single interface to enable, disable and query the > >status of all the services. All we really have is the last one... > > Sounds like the only missing pieces, then, are standard > ways to enable, disable, and configure services. How about: > > sudo /etc/rc.d/ssh enable > sudo /etc/rc.d/ssh disable > sudo /etc/rc.d/ssh configure > > That shouldn't be much of a stretch to implement, either. > The first two just append entries to /etc/rc.conf. The > third opens an editor with a list of variables supported > by this service and then appends the result to rc.conf. Pretty much the same came to my mind some weeks ago. I'd propose a "rcadm" command like Solaris' svcadm, so you do not need to care about if the rc script is in /etc/rc.d or in /usr/local/etc/rc.d. And it would be safer to check if the service is already listed in rc.conf, so it doesn't get appended every time you enable a service. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080807/5fc0e377/attachment.pgp From lidl at pix.net Thu Aug 7 20:52:15 2008 From: lidl at pix.net (Kurt J. Lidl) Date: Thu Aug 7 20:52:22 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807090230.GF1359@server.vk2pj.dyndns.org> References: <20080807090230.GF1359@server.vk2pj.dyndns.org> Message-ID: <20080807202041.GB9084@pix.net> On Thu, Aug 07, 2008 at 07:02:30PM +1000, Peter Jeremy wrote: > On 2008-Aug-06 19:14:51 -0400, wbentley@futurecis.com wrote: > > In Solaris 10 the Services Management Facility (SMF) was introduced. > > The main purpose of SMF appears to be to drum up business for Sun's > training courses by radically changing Sol10 Administration for little > benefit. The main purpose of SMF was to make it possible to programmatically control the system and deal with the myriad of different types of faults from the gazillion different things that people want to run on machines. It's complex because it has to deal with the real world. > >Basically what it does, is take all the rc.d scripts and puts them into > >a database to manage. Everything is converted to XML and two basic > >commands (svcs and svcadm) are used to manage everything. Actually, the inputs to the database are in XML, and this is distilled down to a binary representation in a sqlite database that actually drives the system. While the "svccfg" and "svcadm" interfaces do give you a single manner of dealing with the database (svccfg) and then the state of a given service (svcadm). The other thing that the SMF system captures entirely is the dependencies between the different daemons and services. I'm not sure that the rcorder stuff in FreeBSD is quite as complete. It could be, I just don't know. Also, there is versioning for the changes of the sqlite database in Solaris, so you can punt back to a earlier configuration without much hassle. > With FreeBSD, I can configure virtually all the system via a single > text file - which is easily found and kepy under configuration control. > With Sol10, there are random bits of configuration spread all over the > system and there is no obvious way to control configuration. Well, realistically, the sum of the files in /etc/rc.d and /usr/local/etc/rc.d are also needed, and you need a snapshot of all of those at a given instant in time to provably know how the system is going to configure when booted. -Kurt From andenore at freebsd.org Thu Aug 7 22:33:28 2008 From: andenore at freebsd.org (Anders Nore) Date: Thu Aug 7 22:33:40 2008 Subject: Suggestion for 'pkg_add -r' In-Reply-To: <20080807204035.GT56464@e.0x20.net> References: <1234BBCE-6698-4EF9-8B48-4F291AD78547@freebsd.org> <20080807204035.GT56464@e.0x20.net> Message-ID: On Thu, 07 Aug 2008 22:40:35 +0200, Lars Engels wrote: > On Thu, Aug 07, 2008 at 03:47:24PM +0200, Anders Nore wrote: >> >> >> >>RELENG_7: >> >>http://home.no.net/andenore/patches/pkg_install_2008-08-06_RELENG_7.diff >> >> >> >>CURRENT: >> >>http://home.no.net/andenore/patches/pkg_install_2008-08-06_CURRENT.diff >> > >> >Some comments: >> > * I think you have reversed the patch. :-) >> > * Build errors: >> >cc1: warnings being treated as errors >> >file.c:433: warning: no previous prototype for 'power' >> >file.c:452: warning: no previous prototype for 'human_readable' >> >file.c:474: warning: no previous prototype for 'printHumanReadable' >> >file.c: In function 'printHumanReadable': >> >file.c:482: warning: comparison between signed and unsigned >> > >> >parallels# ./pkg_add -r joe >> >Fetching 321.2 kB from >> >ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/Latest/joe.tbz... >> > Downloading: 100% 321.2 kB at >> 214.8 kB/s >> > Done >> >Fetching 2.4 MB from >> >ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/gettext-0.17_1.tbz... >> > >> Done >> >Fetching 2.2 MB from >> >ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-current/All/aspell-0.60.6_2.tbz... >> > Downloading: 201% 4.5 MB at >> 149.5 kB/s >> > >> >Something's wrong :-) >> > >> >> Heh, yes. It's my first patch(es), so it didn't go as well as I had >> hoped, I believe they are >> fixed now. > > I just downloaded the patch and still get the warning: > /usr/src/usr.sbin/pkg_install/lib/file.c: In function > 'printHumanReadable': > /usr/src/usr.sbin/pkg_install/lib/file.c:486: warning: comparison > between signed and unsigned > *** Error code 1 > > Stop in /usr/src/usr.sbin/pkg_install/lib. > Hey, it should be fixed now. I don't know why this causes a stop in the compiling though? Thanks, Anders Nore From chuckr at telenix.org Fri Aug 8 01:11:59 2008 From: chuckr at telenix.org (Chuck Robey) Date: Fri Aug 8 01:12:07 2008 Subject: read with timeout ?? Message-ID: <489B9D4D.4010009@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have my head lost in a code problem. I just hit a point where I need to do a read from an fd, but I need to associate it with a timeout, on the order of 1 second, something like that. I had the feeling that there's a function in FreeBSD's libc that makes that simple, but I forget the function name. If anyone can remember something like what I'm talking about, I sure would appreciate a function name. I can figure out how it works, if I could only dredge up that name. I just wouldn't like to come up with 4 pounds of code where it ought to be done with a 1-liner. If you're curious, I'm still working on that tablet driver for FreeBSD. It's taken me this long to figure out that Xorg driver code. The Xorg folks have been helpful, but basically, there's almost no docs, nearly no comments, and testing a driver isn't the easiest thing in the world. Regardless, I'm getting really close on this, finally. Thanks -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkibnQoACgkQz62J6PPcoOlIaQCdG5R0p0X/hXVYh/qkX/zK63/E y+EAn3ahlXnPGPzqSdVdhbx1YsEjT4qr =bA6Z -----END PGP SIGNATURE----- From neldredge at math.ucsd.edu Fri Aug 8 01:14:34 2008 From: neldredge at math.ucsd.edu (Nate Eldredge) Date: Fri Aug 8 01:15:03 2008 Subject: read with timeout ?? In-Reply-To: <489B9D4D.4010009@telenix.org> References: <489B9D4D.4010009@telenix.org> Message-ID: On Thu, 7 Aug 2008, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have my head lost in a code problem. I just hit a point where I need to do a > read from an fd, but I need to associate it with a timeout, on the order of 1 > second, something like that. I had the feeling that there's a function in > FreeBSD's libc that makes that simple, but I forget the function name. If > anyone can remember something like what I'm talking about, I sure would > appreciate a function name. I can figure out how it works, if I could only > dredge up that name. man 2 select -- Nate Eldredge neldredge@math.ucsd.edu From wbentley at futurecis.com Thu Aug 7 23:53:40 2008 From: wbentley at futurecis.com (wbentley@futurecis.com) Date: Fri Aug 8 02:04:42 2008 Subject: Idea for FreeBSD Message-ID: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> I am surprised by the overwhelming response that this thread has acquired. I have spent the majority of the day reading all the responses that everyone has put forward. I would like to clear a few things up, comment on others, and suggest some solutions to a lot of good points that everyone has made so far. First let me reiterate a few things. I started in FreeBSD and it will always be my first love. Second, keep in mind that Solaris is a commercial product and must be viewed as such. Now that that is out of the way. I want to make it clear to everyone that I was not suggesting the idea of copying or reproducing any part of how Sun manages or implements its services; only the CONCEPT of how they do it. It does not have to be XML, or in a database or anything else. Actually I am thinking more along the lines of a wrapper that can read/modify/execute from rc.d and the rc.conf. After all, we do not want to make drastic changes. No one wants to re-write rc's or move them to another location. Even solaris still relies on rc scripts to exist. And I am sure I speak for all of us when I say that we all love the concept of how rc.conf handles everything. As some people have already pointed out multiple times so far, the idea of an enable/disable is a great idea. Maybe we can start with that and see how it goes and develop further based on need/requirements/accomplishments. I think a drop-in command like "rcadm" (someone mentioned this as an idea, but cant remember who) would be a good start for managing the states of services. Mike Meyer also brought up many good points that I agree with. Please try not to get caught up in the XML stuff, that is not a requirement or suggestion, it is just an example of how Sun did it, now how FreeBSD has to;) Someone recommended Puppet, but this is an entire framework that would have to be added/implemented and configured to work with FreeBSD as well as learning a new markup language for it. launchd has a lot of good ideas, but I am not sure how mature it is yet; maybe it is a good place to start. If we start with the basics and break it down and program this from a modular standpoint it is not so bad. Begin with the basic (high-level) approach. A shell script (service) that is aware of where rc scripts are located and that can keep track of what the current state of the services (PID's) are. An enable/disable command is nothing more that throwing a start/stop command to these rc files. The rc.conf can assist with knowing what should be enabled/disabled and what flags to throw at it. For EXAMPLE!!!!, (you got that, example only) Solaris uses one master service that is started first, and the whole point of that first service is to monitor the other services and know what state they are in and starts dependent services upon boot. Consider it the service manager almost. I could go on plenty about different ways this concept could be implemented but lets not go in the weeds to deep. A systematic approach to this would be the basics. Lets start with the idea of a enable/disable and go from there. On a side not, I am impressed with many of the points that were made and ideas already generated and all within less than 24 hours. I am glad I joined this list. Thank you all. > To who it may concern, > > I am A FreeBSD administrator as well as a Solaris Administrator. I use > BSD at home but Solaris at work. I love both OS's but I would like to > increase the administrative capability of FreeBSD. > > In Solaris 10 the Services Management Facility (SMF) was introduced. > Basically what it does, is take all the rc.d scripts and puts them into > a database to manage. Everything is converted to XML and two basic > commands (svcs and svcadm) are used to manage everything. > > I would like to submit the idea of implementing a similar environment > into FreeBSD. After looking through the developers links and googling I > found no project for FreeBSD that implemented anything similar to this. > I have included a link below to give a better understanding of SMF and > its capabilities. > > Is it possible, if it does not exist already, to look at the > possibility of implementing the concept of SMF into FreeBSD? I would > gladly be an active supporter in this endeavor. > > > Will Bentley > Future CIS > 410-782-5954 > "Your resource for computer expertise!" > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From unixmania at gmail.com Fri Aug 8 02:50:48 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Fri Aug 8 02:50:55 2008 Subject: read with timeout ?? In-Reply-To: References: <489B9D4D.4010009@telenix.org> Message-ID: On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge wrote: > On Thu, 7 Aug 2008, Chuck Robey wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I have my head lost in a code problem. I just hit a point where I need to >> do a >> read from an fd, but I need to associate it with a timeout, on the order >> of 1 >> second, something like that. I had the feeling that there's a function in >> FreeBSD's libc that makes that simple, but I forget the function name. If >> anyone can remember something like what I'm talking about, I sure would >> appreciate a function name. I can figure out how it works, if I could >> only >> dredge up that name. > > man 2 select If the fd is a socket then you can also use setsockopt(2) to set SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or recv(2) errors. The net effect is the same of using select but the syntax is simpler, IMO. -- If you think things can't get worse it's probably only because you lack sufficient imagination. From spam at rm-rf.kiev.ua Fri Aug 8 03:33:23 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Fri Aug 8 03:33:30 2008 Subject: Idea for FreeBSD Message-ID: <20080808033317.GA96397@ravenloft.kiev.ua> On Thu, Aug 07, 2008 at 11:25:39AM -0400, Mike Meyer wrote: > On Thu, 7 Aug 2008 09:15:00 +0300 Alex Kozlov wrote: > > [1]: > > $cat /usr/local/bin/service > > Basically what I had in mind, but it can be made more portable across > FreeBSD configurations. > [...] > > And here's where you go wrong. What you want now is: Yes. This is more correct: #!/bin/sh name=$1 cmd=$2 if [ -z "${name}" -o -z "${cmd}" ]; then echo ${0##*/} service_name command exit 3 fi . /etc/rc.subr load_rc_config ${name} for dir in /etc/rc.d ${local_startup}; do if [ -r "${dir}/${name}" ]; then run_rc_script "${dir}/${name}" ${cmd} exit 0 fi if [ -r "${dir}/${name}.sh" ]; then run_rc_script "${dir}/${name}.sh" ${cmd} exit 0 fi done echo "service '${name}' not found" exit 2 -- Adios From samflanker at gmail.com Fri Aug 8 08:10:05 2008 From: samflanker at gmail.com (sam) Date: Fri Aug 8 08:10:12 2008 Subject: em0: The EEPROM Checksum Is Not Valid In-Reply-To: <20080807050725.GA8969@eos.sc1.parodius.com> References: <489A7B64.4000306@gmail.com> <20080807050725.GA8969@eos.sc1.parodius.com> Message-ID: <489BFF53.7060101@gmail.com> Jeremy Chadwick wrote: > On Thu, Aug 07, 2008 at 08:34:44AM +0400, Vladimir Ermakov wrote: > >> Hello >> >> my trouble with nic >> >> part of `dmesg` output >> --------------------------------------------------------------------- >> em0: port 0xec00-0xec3f mem >> 0xfebc0000-0xfebdffff,0xfeb80000-0xfebbffff irq 19 at device 2.0 on pci2 >> em0: The EEPROM Checksum Is Not Valid >> device_attach: em0 attach returned 5 >> ---------------------------------------------------------------------- >> >> part of `pciconf -lv` output >> ---------------------------------------------------------------------- >> em0@pci0:2:2:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x01 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82545GM Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> ---------------------------------------------------------------------- >> >> uname output >> ---------------------------------------------------------------------- >> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #2: Wed Jul 16 20:36:12 UTC 2008 >> root@:/usr/obj/usr/src/sys/STONE i386 >> ---------------------------------------------------------------------- >> >> please, any solution? >> > > Intel probably has a utility to reset the EEPROM settings on the NIC. > Jack Vogel may know where to get such a utility. > > I do not believe this problem is FreeBSD-related. > > thx took IBAUTIL.EXE from Intel`s site, now my Intel_NIC works /Vladimir Ermakov From pieter at degoeje.nl Fri Aug 8 08:10:17 2008 From: pieter at degoeje.nl (Pieter de Goeje) Date: Fri Aug 8 08:10:24 2008 Subject: read with timeout ?? In-Reply-To: References: <489B9D4D.4010009@telenix.org> Message-ID: <200808081009.56521.pieter@degoeje.nl> On Friday 08 August 2008, Carlos A. M. dos Santos wrote: > On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge wrote: > > On Thu, 7 Aug 2008, Chuck Robey wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> I have my head lost in a code problem. I just hit a point where I need > >> to do a > >> read from an fd, but I need to associate it with a timeout, on the order > >> of 1 > >> second, something like that. I had the feeling that there's a function > >> in FreeBSD's libc that makes that simple, but I forget the function > >> name. If anyone can remember something like what I'm talking about, I > >> sure would appreciate a function name. I can figure out how it works, > >> if I could only > >> dredge up that name. > > > > man 2 select > > If the fd is a socket then you can also use setsockopt(2) to set > SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or > recv(2) errors. The net effect is the same of using select but the > syntax is simpler, IMO. I think poll(2) is also simpler than select for this purpose. -- Pieter de Goeje From vince at unsane.co.uk Fri Aug 8 08:57:12 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Fri Aug 8 08:57:18 2008 Subject: Idea for FreeBSD In-Reply-To: <20080808033317.GA96397@ravenloft.kiev.ua> References: <20080808033317.GA96397@ravenloft.kiev.ua> Message-ID: <489C0A63.8040600@unsane.co.uk> Alex Kozlov wrote: > On Thu, Aug 07, 2008 at 11:25:39AM -0400, Mike Meyer wrote: > >> On Thu, 7 Aug 2008 09:15:00 +0300 Alex Kozlov wrote: >> >>> [1]: >>> $cat /usr/local/bin/service >>> >> Basically what I had in mind, but it can be made more portable across >> FreeBSD configurations. >> >> > [...] > >> And here's where you go wrong. What you want now is: >> > Yes. This is more correct: > > Just to save reimplementing the wheel, have a look also at the sysutils/bsdadminscripts port. it has rcstart (and various hardlinks,) which are intended for pretty much what youre intending I think. Vince > #!/bin/sh > > name=$1 > cmd=$2 > > if [ -z "${name}" -o -z "${cmd}" ]; then > echo ${0##*/} service_name command > exit 3 > fi > > . /etc/rc.subr > > load_rc_config ${name} > > for dir in /etc/rc.d ${local_startup}; do > if [ -r "${dir}/${name}" ]; then > run_rc_script "${dir}/${name}" ${cmd} > exit 0 > fi > > if [ -r "${dir}/${name}.sh" ]; then > run_rc_script "${dir}/${name}.sh" ${cmd} > exit 0 > fi > done > > echo "service '${name}' not found" > exit 2 > > > -- > Adios > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From des at des.no Fri Aug 8 10:19:55 2008 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Fri Aug 8 10:20:01 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807172650.GA56516@ravenloft.kiev.ua> (Alex Kozlov's message of "Thu, 7 Aug 2008 20:26:50 +0300") References: <20080807172650.GA56516@ravenloft.kiev.ua> Message-ID: <86iquberlh.fsf@ds4.des.no> Alex Kozlov writes: > Matthew Seaman writes: > > [...] XML itself is too general-purpose: it has too much baggage > > designed for its primary function of facilitating interoperation > > between diverse systems in different zones of control, none of which > > is particularly applicable to system startup. > While in general I agree with You, I must note that We already have > xml parser (expat 1.95) for geom. See /lib/libbsdxml.so* Non sequitur. The fact that we have an XML parser in base does not make XML more (or less) suitable for the task. DES -- Dag-Erling Sm?rgrav - des@des.no From unixmania at gmail.com Fri Aug 8 14:33:59 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Fri Aug 8 14:34:06 2008 Subject: read with timeout ?? In-Reply-To: <200808081009.56521.pieter@degoeje.nl> References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> Message-ID: On Fri, Aug 8, 2008 at 5:09 AM, Pieter de Goeje wrote: > On Friday 08 August 2008, Carlos A. M. dos Santos wrote: >> On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge > wrote: >> > On Thu, 7 Aug 2008, Chuck Robey wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >> >> Hash: SHA1 >> >> >> >> I have my head lost in a code problem. I just hit a point where I need >> >> to do a >> >> read from an fd, but I need to associate it with a timeout, on the order >> >> of 1 >> >> second, something like that. I had the feeling that there's a function >> >> in FreeBSD's libc that makes that simple, but I forget the function >> >> name. If anyone can remember something like what I'm talking about, I >> >> sure would appreciate a function name. I can figure out how it works, >> >> if I could only >> >> dredge up that name. >> > >> > man 2 select >> >> If the fd is a socket then you can also use setsockopt(2) to set >> SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or >> recv(2) errors. The net effect is the same of using select but the >> syntax is simpler, IMO. > > I think poll(2) is also simpler than select for this purpose. BTW, the setsockopt(2) manual page stands that a send or receive timeout returns with the error EWOULDBLOCK but read(2) recv(2) send(2) and write(2) only list EAGAIN in their ERRORS section. This is harmless on BSD and Linux because EAGAIN and EWOULDBLOCK are the same, but may sound confusing for people porting from/to System V. On HP-UX, for instance, recv(2) lists both EAGAIN and EWOULDBLOCK. The setsockopt man page should be improved in order to explain standards conformance and porting issues. I volunteer to do it but the changes must be reviewed by a native English speaker. -- If you think things can't get worse it's probably only because you lack sufficient imagination. From pingmai at yahoo.com Fri Aug 8 18:43:01 2008 From: pingmai at yahoo.com (ping) Date: Fri Aug 8 18:43:13 2008 Subject: missing interrupts? Message-ID: <374442.98765.qm@web52908.mail.re2.yahoo.com> this is an interrupt handler that's attached to irq 31 on ioapic1 on a 6.1R kernel, type INTR_TYPE_NET|INTR_MPSAFE. seems that it's missing interrupts. watching the KTR trace, it was running along fine, then it just stopped. intr handler stopped getting run. but the interrupt register on chip was high. is this a case of lost interrupts? or hardware problem? TIA, ping From spam at rm-rf.kiev.ua Fri Aug 8 19:08:01 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Fri Aug 8 19:08:10 2008 Subject: Idea for FreeBSD Message-ID: <20080808190754.GA6827@ravenloft.kiev.ua> On Fri, Aug 08, 2008 at 12:19:54PM +0200, Dag-Erling Sm?rgrav wrote: > Alex Kozlov writes: > > Matthew Seaman writes: > > > [...] XML itself is too general-purpose: it has too much baggage > > > designed for its primary function of facilitating interoperation > > > between diverse systems in different zones of control, none of which > > > is particularly applicable to system startup. > > While in general I agree with You, I must note that We already have > > xml parser (expat 1.95) for geom. See /lib/libbsdxml.so* > Non sequitur. The fact that we have an XML parser in base does not make > XML more (or less) suitable for the task. I never said anything like this. Only that argument about 'to have another shlib or two... available early in the boot process' is invalid. -- Adios From nparhar at gmail.com Fri Aug 8 19:13:54 2008 From: nparhar at gmail.com (Navdeep Parhar) Date: Fri Aug 8 19:14:25 2008 Subject: mercurial working copy of FreeBSD src Message-ID: Hello everyone, I'm looking for the fastest way to get a full mercurial repository of HEAD. I tried using hgsvn and the tree at http://svn.freebsd.org/base/head but it looks like the first hgpullsvn operation will take days (literally): $ hgimportsvn http://svn.freebsd.org/base/head $ cd head $ hgpullsvn <=== This will take a long long time Does anyone know of a faster way to do this? Is there a mercurial repository out there somewhere from where I can simply "hg clone" my copy? Regards, Navdeep From spam at rm-rf.kiev.ua Fri Aug 8 19:29:44 2008 From: spam at rm-rf.kiev.ua (Alex Kozlov) Date: Fri Aug 8 19:29:51 2008 Subject: Idea for FreeBSD Message-ID: <20080808192938.GA8126@ravenloft.kiev.ua> On Fri, Aug 08, 2008 at 09:57:07AM +0100, Vincent Hoffman wrote: > > On Thu, Aug 07, 2008 at 11:25:39AM -0400, Mike Meyer wrote: > >> On Thu, 7 Aug 2008 09:15:00 +0300 Alex Kozlov wrote: > >>> [1]: > >>> $cat /usr/local/bin/service > >> Basically what I had in mind, but it can be made more portable across > >> FreeBSD configurations. > > [...] > >> And here's where you go wrong. What you want now is: > > Yes. This is more correct: > > > Just to save reimplementing the wheel, have a look also at the > sysutils/bsdadminscripts port. it has rcstart (and various hardlinks,) > which are intended for pretty much what youre intending I think. Too late, I think. This wheel was reimplemented, and quite some time ago ;-) Anyway, thanks for the pointer. I'll check on the weekends if pkg_libchk from bsdadminscripts is a suitable replacement for sysutils/libchk. -- Adios From chuckr at telenix.org Fri Aug 8 20:27:42 2008 From: chuckr at telenix.org (Chuck Robey) Date: Fri Aug 8 20:27:49 2008 Subject: read with timeout ?? In-Reply-To: <200808081009.56521.pieter@degoeje.nl> References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> Message-ID: <489CAC2F.1070907@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pieter de Goeje wrote: > On Friday 08 August 2008, Carlos A. M. dos Santos wrote: >> On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge > wrote: >>> On Thu, 7 Aug 2008, Chuck Robey wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> Hash: SHA1 >>>> >>>> I have my head lost in a code problem. I just hit a point where I need >>>> to do a >>>> read from an fd, but I need to associate it with a timeout, on the order >>>> of 1 >>>> second, something like that. I had the feeling that there's a function >>>> in FreeBSD's libc that makes that simple, but I forget the function >>>> name. If anyone can remember something like what I'm talking about, I >>>> sure would appreciate a function name. I can figure out how it works, >>>> if I could only >>>> dredge up that name. >>> man 2 select >> If the fd is a socket then you can also use setsockopt(2) to set >> SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or >> recv(2) errors. The net effect is the same of using select but the >> syntax is simpler, IMO. > > I think poll(2) is also simpler than select for this purpose. > It does look like that, I need to check the implementation a bit, because the name of this thing makes me really suspicious about how often it checks for an fd for being ready for a read. I know select comes right back, I was under the impression that poll didn't use signals to do this. Anyhow, I sure do appreciate the hint, that's just exactly what I was asking for. Spending the time figuring it all out, that'll actually be fun for me. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkicrC8ACgkQz62J6PPcoOmYjACfWP/IGjSvak1hLYSJwWBKkTjb 8qUAoJfSYOZcPJKMqqUb3Y1mltG51sgI =USHT -----END PGP SIGNATURE----- From chuckr at telenix.org Fri Aug 8 20:31:04 2008 From: chuckr at telenix.org (Chuck Robey) Date: Fri Aug 8 20:31:24 2008 Subject: read with timeout ?? In-Reply-To: References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> Message-ID: <489CACF9.3030309@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Carlos A. M. dos Santos wrote: > On Fri, Aug 8, 2008 at 5:09 AM, Pieter de Goeje wrote: >> On Friday 08 August 2008, Carlos A. M. dos Santos wrote: >>> On Thu, Aug 7, 2008 at 10:14 PM, Nate Eldredge >> wrote: >>>> On Thu, 7 Aug 2008, Chuck Robey wrote: >>>>> -----BEGIN PGP SIGNED MESSAGE----- >>>>> Hash: SHA1 >>>>> >>>>> I have my head lost in a code problem. I just hit a point where I need >>>>> to do a >>>>> read from an fd, but I need to associate it with a timeout, on the order >>>>> of 1 >>>>> second, something like that. I had the feeling that there's a function >>>>> in FreeBSD's libc that makes that simple, but I forget the function >>>>> name. If anyone can remember something like what I'm talking about, I >>>>> sure would appreciate a function name. I can figure out how it works, >>>>> if I could only >>>>> dredge up that name. >>>> man 2 select >>> If the fd is a socket then you can also use setsockopt(2) to set >>> SO_RCVTIMEO and check for EWOULDBLOCK (same as EAGAIN) upon read(2) or >>> recv(2) errors. The net effect is the same of using select but the >>> syntax is simpler, IMO. >> I think poll(2) is also simpler than select for this purpose. > > BTW, the setsockopt(2) manual page stands that a send or receive > timeout returns with the error EWOULDBLOCK but read(2) recv(2) send(2) > and write(2) only list EAGAIN in their ERRORS section. This is > harmless on BSD and Linux because EAGAIN and EWOULDBLOCK are the same, > but may sound confusing for people porting from/to System V. On HP-UX, > for instance, recv(2) lists both EAGAIN and EWOULDBLOCK. > > The setsockopt man page should be improved in order to explain > standards conformance and porting issues. I volunteer to do it but the > changes must be reviewed by a native English speaker. > Carlos, lets not go off on the socket trip for me... while I personally enjoy such a email, I have to admit my own needs fall more into a plain-jame serial line, nothing a socket-oriented thing could help me with. However, if you want to discuss this just fo the fun of it, oh please, by all means do carry on! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkicrPkACgkQz62J6PPcoOmJowCfWPt1jHY4Gx0kOAQedVATHYDd BGYAoJe6JYuskZZe85AA63sgRBG1VGF0 =dNTn -----END PGP SIGNATURE----- From jhb at freebsd.org Fri Aug 8 20:53:21 2008 From: jhb at freebsd.org (John Baldwin) Date: Fri Aug 8 20:53:32 2008 Subject: missing interrupts? In-Reply-To: <374442.98765.qm@web52908.mail.re2.yahoo.com> References: <374442.98765.qm@web52908.mail.re2.yahoo.com> Message-ID: <200808081610.03720.jhb@freebsd.org> On Friday 08 August 2008 02:16:20 pm ping wrote: > this is an interrupt handler that's attached to irq 31 on ioapic1 on a 6.1R kernel, type INTR_TYPE_NET|INTR_MPSAFE. seems that it's missing interrupts. watching the KTR trace, it was running along fine, then it just stopped. intr handler stopped getting run. but the interrupt register on chip was high. is this a case of lost interrupts? or hardware problem? There is one possible race in the I/O APIC code someone pointed me at recently. You can try expanding the scope of the icu_lock to cover all of ioapic_program_intpin() to see if it fixes your issue (sys///io_apic.c) -- John Baldwin From v.haisman at sh.cvut.cz Fri Aug 8 21:19:32 2008 From: v.haisman at sh.cvut.cz (=?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?=) Date: Fri Aug 8 21:19:38 2008 Subject: mercurial working copy of FreeBSD src In-Reply-To: References: Message-ID: <489CB856.5060506@sh.cvut.cz> Navdeep Parhar wrote, On 8.8.2008 20:47: > Hello everyone, > > I'm looking for the fastest way to get a full mercurial repository of > HEAD. > > I tried using hgsvn and the tree at http://svn.freebsd.org/base/head > but it looks like the first hgpullsvn operation will take days (literally): > > $ hgimportsvn http://svn.freebsd.org/base/head > $ cd head > $ hgpullsvn <=== This will take a long long time > > Does anyone know of a faster way to do this? Is there a mercurial > repository out there somewhere from where I can simply "hg clone" my > copy? Try this one: . > > Regards, > Navdeep -- VH -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 219 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080808/f4520e52/signature.pgp From delphij at delphij.net Fri Aug 8 21:26:16 2008 From: delphij at delphij.net (Xin LI) Date: Fri Aug 8 21:26:22 2008 Subject: mercurial working copy of FreeBSD src In-Reply-To: References: Message-ID: <489CB9E9.5010706@delphij.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Navdeep Parhar wrote: | Hello everyone, | | I'm looking for the fastest way to get a full mercurial repository of | HEAD. | | I tried using hgsvn and the tree at http://svn.freebsd.org/base/head | but it looks like the first hgpullsvn operation will take days (literally): | | $ hgimportsvn http://svn.freebsd.org/base/head | $ cd head | $ hgpullsvn <=== This will take a long long time | | Does anyone know of a faster way to do this? Is there a mercurial | repository out there somewhere from where I can simply "hg clone" my | copy? Perhaps someone should share a tarball of the hgpullsvn output, otherwise it would be a nightmare for svn.freebsd.org... Another thought would be the hg mirror provided by .fr people, which is http://hg.fr.freebsd.org/. Note that this seems to be a CVS sourced one. - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkicuekACgkQi+vbBBjt66AjNgCgqsUqGXUnIqrPgplIvt7X5Sz8 FowAoJRkW/ITN0I2UxalzK+ykYt8RLcY =fOap -----END PGP SIGNATURE----- From nparhar at gmail.com Fri Aug 8 21:31:20 2008 From: nparhar at gmail.com (Navdeep Parhar) Date: Fri Aug 8 21:31:27 2008 Subject: mercurial working copy of FreeBSD src In-Reply-To: <489CB856.5060506@sh.cvut.cz> References: <489CB856.5060506@sh.cvut.cz> Message-ID: <20080808212907.GA12267@insightsol.com> >> Hello everyone, >> >> I'm looking for the fastest way to get a full mercurial repository of >> HEAD. >> >> I tried using hgsvn and the tree at http://svn.freebsd.org/base/head >> but it looks like the first hgpullsvn operation will take days (literally): >> >> $ hgimportsvn http://svn.freebsd.org/base/head >> $ cd head >> $ hgpullsvn <=== This will take a long long time >> >> Does anyone know of a faster way to do this? Is there a mercurial >> repository out there somewhere from where I can simply "hg clone" my >> copy? > Try this one: . > Thanks, this is exactly what I was looking for. Can you also tell me how and how often it is sync'ed with the main SVN repository? Regards, Navdeep > > > -- > VH > From neldredge at math.ucsd.edu Fri Aug 8 22:51:23 2008 From: neldredge at math.ucsd.edu (Nate Eldredge) Date: Fri Aug 8 22:51:30 2008 Subject: read with timeout ?? In-Reply-To: <489CAC2F.1070907@telenix.org> References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> <489CAC2F.1070907@telenix.org> Message-ID: On Fri, 8 Aug 2008, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pieter de Goeje wrote: >> >> I think poll(2) is also simpler than select for this purpose. >> > > It does look like that, I need to check the implementation a bit, because the > name of this thing makes me really suspicious about how often it checks for an > fd for being ready for a read. I know select comes right back, I was under the > impression that poll didn't use signals to do this. AFAIK the effects are identical, just the arguments are set up in a different way. Both of them will block until the fd is ready and then return "immediately" (subject to other processes running of course). The name "poll" is a misnomer because it doesn't actually work by polling, but you can pretend that it does (and does so "infinitely often"). Neither one uses signals per se, though if the underlying hardware device is interrupt-driven, that will be what (indirectly) triggers the wake-up. poll does seem to be more convenient than messing about with fd_set's. select is older and so it comes to my mind first, that's all. -- Nate Eldredge neldredge@math.ucsd.edu From pingmai at yahoo.com Fri Aug 8 23:27:57 2008 From: pingmai at yahoo.com (Ping Mai) Date: Fri Aug 8 23:28:05 2008 Subject: missing interrupts? In-Reply-To: <200808081610.03720.jhb@freebsd.org> Message-ID: <755343.17576.qm@web52907.mail.re2.yahoo.com> Thanks John. tried it but didn't help. --- On Fri, 8/8/08, John Baldwin wrote: > From: John Baldwin > Subject: Re: missing interrupts? > To: freebsd-acpi@freebsd.org > Cc: "ping" , freebsd-drivers@freebsd.org, freebsd-hackers@freebsd.org > Date: Friday, August 8, 2008, 1:10 PM > On Friday 08 August 2008 02:16:20 pm ping wrote: > > this is an interrupt handler that's attached to > irq 31 on ioapic1 on a 6.1R > kernel, type INTR_TYPE_NET|INTR_MPSAFE. seems that > it's missing interrupts. > watching the KTR trace, it was running along fine, then it > just stopped. > intr handler stopped getting run. but the interrupt > register on chip was > high. is this a case of lost interrupts? or hardware > problem? > > There is one possible race in the I/O APIC code someone > pointed me at > recently. You can try expanding the scope of the icu_lock > to cover all of > ioapic_program_intpin() to see if it fixes your issue > (sys///io_apic.c) > > -- > John Baldwin From peterjeremy at optushome.com.au Sat Aug 9 00:45:24 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sat Aug 9 00:45:31 2008 Subject: read with timeout ?? In-Reply-To: <489CACF9.3030309@telenix.org> References: <489B9D4D.4010009@telenix.org> <200808081009.56521.pieter@degoeje.nl> <489CACF9.3030309@telenix.org> Message-ID: <20080809004518.GM64458@server.vk2pj.dyndns.org> On 2008-Aug-08 16:30:49 -0400, Chuck Robey wrote: >such a email, I have to admit my own needs fall more into a plain-jame serial >line, nothing a socket-oriented thing could help me with. If this is a normal serial port then termios(4) might help: Use non-canonical processing with VMIN = 0 and VTIME = 10 (see the section "Noncanonical Mode Input Processing"). -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080809/58b8cd63/attachment.pgp From keramida at freebsd.org Sat Aug 9 06:45:41 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Sat Aug 9 06:45:47 2008 Subject: mercurial working copy of FreeBSD src In-Reply-To: (Navdeep Parhar's message of "Fri, 8 Aug 2008 11:47:15 -0700") References: Message-ID: <87tzdu1z5f.fsf@kobe.laptop> On Fri, 8 Aug 2008 11:47:15 -0700, "Navdeep Parhar" wrote: > Hello everyone, > > I'm looking for the fastest way to get a full mercurial repository of > HEAD. Do you really want the *FULL* history of head? It's probably going to be in the order of a couple of hundred of MB, or even more. If you can live with an Hg repository that only includes the 2008 history of 'HEAD', then please keep reading, you may like the rest of this post :) > I tried using hgsvn and the tree at http://svn.freebsd.org/base/head > but it looks like the first hgpullsvn operation will take days (literally): hgpullsvn is slow. Really really *REALLY* slow... It's probably a better idea to get a recent version of the mercurial/crew branch. This includes support for the svn-1.5.X bindings, and you can convert parts of the history of the /base/head branch. I have a local hg tree with the history of the 'head' branch since 2008-01-01 on my laptop, which I periodically resync from svn with: keramida@kobe:/home/keramida$ cd /hg/bsd keramida@kobe:/hg/bsd$ ./pull-head.sh scanning source... sorting... converting... [lots of output snipped] keramida@kobe:/hg/bsd/head$ hg shortlog --limit 2 4201:99f1acdec12f | 2008-08-09 04:08 +0000 | imp: Rather than waiting a fixed amount of time, which might not be enough 4200:d5553c08bf90 | 2008-08-09 03:54 +0000 | imp: Change -1 to 0xfffffffful since the interface returns uint32_t. (1) A bit of background ======================= I didn't really want to convert the full history of the 'head' branch From Subversion, because I have a local Subversion repository for that. Being able to rebase my local in-progress patches on an Hg clone _did_ seem useful at the time, so that's why I converted only the history of 'head' from the start of 2008. The initial pull was done by pulling a clean copy of the first commit of 2008 and then importing changesets on top of that with: % cd /hg/bsd % \time hg convert --config convert.svn.startrev=175026 \ --config convert.svn.trunk='head' \ --config convert.svn.branches='' \ --config convert.svn.tags='' file:///home/svn/base/ head The initial pull took a bit of time, but far less than hgimportsvn. Subsequent pull-head.sh runs take literally seconds to pull from a local Subversion repository mirror. The speed is much much better than hgpullsvn, because the Hg convert extension doesn't parse the output of shell commands, but it links `natively' (through SWIG) with the subversion libraries. The conversion process is interruptible, and if you keep the 'SHA map' of the initial conversion you can keep pulling changesets into the conversion clone as many times as necessary with something like: % cd /hg/bsd % cat -n pull-head.sh 1 #!/bin/sh 2 3 hg convert \ 4 --config convert.svn.trunk='head' \ 5 --config convert.svn.branches='' \ 6 --config convert.svn.tags='' \ 7 file:///home/svn/base/ head % You don't need the `convert.svn.startrev=175026' option in the second and subsequent runs, because the conversion clone already has a file called `.hg/shamap' and the conversion picks up from the place it stopped the previous time. (2) Bootstrapping your own clone ================================ Everything above is of `encyclopedical' nature, because now that I've done the conversion once, you can just use a bundle file and a matching copy of my `.hg/shamap' file to bootstrap a conversion clone of your own. You can fetch an Hg bundle and a matching shamap with the history of 'head' in 2008 from: http://people.freebsd.org/~keramida/mercurial/head.hg http://people.freebsd.org/~keramida/mercurial/head.shamap The checksums of these files should be: MD5 (head.hg) = 4978723c560bc48c390be1634c7d36a4 MD5 (head.shamap) = 8e5957657fb499ed3a3575fc921e3029 SHA256 (head.hg) = ab073135925fdb54a2820077a5a4d75f4306d44a217b7c30d6b8719a9a5008d4 SHA256 (head.shamap) = 04c6648bd108d3550ffb126c321b8faf2f5dda9f891787bb57ae178efa271893 The head.hg bundle is around 92 MB and you can pull it directly into an empty Hg workspace: % hg init head % cd head ; hg pull /var/tmp/head.hg Then copy the `head.shamap' file in `.hg/shamap' and you are ready to go. You can start cloning this tree, and you can also run "hg convert" to incrementally pull the history of the svn/head branch, as many times as necessary. The `pull-head.sh' script I included above will make subsequent pulls less tedious by saving you the typing of all the --config options to get the svn->hg branch names right. (3) Important disclaimer ======================== Note that this is *NOT* an official branch of the FreeBSD source tree, so if you plan to use the head.hg bundle, this email is _not_ really a promise to keep uploading `bootstrap bundles'. You are also the sole person responsible for comparing the source tree checked out from the Hg clone with a subversion or cvs checkout and making sure that it matches. So have fun if you like it, but please don't sue me or something. HTH, Giorgos -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080809/951d3614/attachment.pgp From ivoras at freebsd.org Sat Aug 9 17:36:27 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sat Aug 9 17:36:34 2008 Subject: Patch for working AMD Geode CS5530 audio driver on HEAD In-Reply-To: <20080803161057.GB35301@rink.nu> References: <20080803161057.GB35301@rink.nu> Message-ID: Rink Springer wrote: > Hi, > > As outlined in > http://lists.freebsd.org/pipermail/freebsd-hackers/2008-January/022986.html, > Alec had some problems with the snd_geode driver. While I cannot test > whether it works using Geode CS5536 hardware, I've managed to get the > driver to work using CS5530 hardware on FreeBSD HEAD. > > The patch is available at > http://people.freebsd.org/~rink/various/ns_geode.diff - using this, my Hi, This patch looks like it needs something. Can you post or link to the entire driver please? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080809/f549d67b/signature.pgp From rink at FreeBSD.org Sat Aug 9 19:31:32 2008 From: rink at FreeBSD.org (Rink Springer) Date: Sat Aug 9 19:31:39 2008 Subject: Patch for working AMD Geode CS5530 audio driver on HEAD In-Reply-To: References: <20080803161057.GB35301@rink.nu> Message-ID: <20080809193233.GC19885@rink.nu> Hi Ivan, On Sat, Aug 09, 2008 at 07:36:07PM +0200, Ivan Voras wrote: > This patch looks like it needs something. Can you post or link to the > entire driver please? Sure - this was already outlined in the original thread, but have a look at http://63.249.85.132/gx_audio/index.html - the driver there works. You need minor tweaks to the Makefile, these can be found in http://setfilepointer.com/pub/geode/ns_geode.diff. Regards, -- Rink P.W. Springer - http://rink.nu "Anyway boys, this is America. Just because you get more votes doesn't mean you win." - Fox Mulder From ken at mthelicon.com Sun Aug 10 11:15:19 2008 From: ken at mthelicon.com (Pegasus Mc cleaft) Date: Sun Aug 10 11:15:25 2008 Subject: RFC Newer binutils Message-ID: <200808101215.15679.ken@mthelicon.com> Hello everyone, I was wondering if anyone knows if there is planned an update to the binutils for the base system planned? The reason why I'm asking is (occasionally) I use a later gcc then what comes with the system to take advantage of the newer opcodes in the Core 2. Unfortunately the base assembler dosent understand these new opcodes and things bomb out. I have installed the latest (2.18) version of buntuils and I can compile at that point. Things just get sorta ickey having two versions of binutils on the machine and thought it would be much simpler to have an update to the base. I know there are still problems with the later gcc versions (like 4.3) and can understand why FBSD hasent moved to it yet, but didnt think there was any harm in updating to the later versions of as, etc.. Ta Peg From lstewart at room52.net Sun Aug 10 14:07:37 2008 From: lstewart at room52.net (Lawrence Stewart) Date: Sun Aug 10 14:07:44 2008 Subject: RFC Newer binutils In-Reply-To: <200808101215.15679.ken@mthelicon.com> References: <200808101215.15679.ken@mthelicon.com> Message-ID: <489EEF37.4010607@room52.net> Pegasus Mc cleaft wrote: > Hello everyone, > > I was wondering if anyone knows if there is planned an update to the binutils > for the base system planned? [snip] See the July 2008 thread titled "Updating src/contrib/binutils" on freebsd-current. Cheers, Lawrence From rkramer at mweb.com Mon Aug 11 06:34:23 2008 From: rkramer at mweb.com (Rudi Kramer - MWEB) Date: Mon Aug 11 06:34:35 2008 Subject: Idea for FreeBSD References: <20080807043331.GA38794@stlux503.dsto.defence.gov.au> Message-ID: <39DC135F7F0571489196E0B6F5D58B4A03B45FFD@MWBEXCH.mweb.com> > On Behalf Of Wilkinson, Alex > Sent: Thursday, August 07, 2008 6:34 AM > To: freebsd-hackers@freebsd.org > Subject: Re: Idea for FreeBSD > > > 0n Wed, Aug 06, 2008 at 07:14:51PM -0400, wbentley@futurecis.com wrote: > > >I would like to submit the idea of implementing a similar environment > >into FreeBSD. After looking through the developers links and googling I > >found no project for FreeBSD that implemented anything similar to this. > >I have included a link below to give a better understanding of SMF and > >its capabilities. > > I believe there was a port of MacOS-X 'launchd' to FreeBSD: > > [http://wiki.freebsd.org/launchd] > > I think launchd may use XML. Tyler has made no changes to the above mentioned wiki page since 2005-11-01. We can only assume that the project is dead. Rudi From pb at ludd.ltu.se Mon Aug 11 15:49:27 2008 From: pb at ludd.ltu.se (Peter B) Date: Mon Aug 11 15:54:45 2008 Subject: Kernel compile R7.0 i386 GENERIC, fails Message-ID: <200808111537.m7BFbHf1006054@brother.ludd.ltu.se> I'm trying to compile the generic FreeBSD kernel 7.0-RELEASE i386. But it fails. Any tip on how to fix it? Extracted sources: sbase, srelease, ssys toor@m /usr/src #make buildkernel KERNCONF=GENERIC . . mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/usr/obj/usr/src/sys/GENERIC /usr/src/sys/modules/accf_http/../../netinet/accf_http.c ===> acpi (depend) ===> acpi/acpi (depend) @ -> /usr/src/sys machine -> /usr/src/sys/i386/include make: don't know how to make dsfield.c. Stop *** Error code 2 Stop in /usr/src/sys/modules/acpi. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Exit 1 From ivoras at freebsd.org Mon Aug 11 22:35:08 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Mon Aug 11 22:35:14 2008 Subject: Kernel compile R7.0 i386 GENERIC, fails In-Reply-To: <200808111537.m7BFbHf1006054@brother.ludd.ltu.se> References: <200808111537.m7BFbHf1006054@brother.ludd.ltu.se> Message-ID: Peter B wrote: > I'm trying to compile the generic FreeBSD kernel 7.0-RELEASE i386. But it > fails. Any tip on how to fix it? > > Extracted sources: sbase, srelease, ssys a) if your sources are broken, download or cvsup to a clean version b) remove /usr/obj/* -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080811/ce566d6c/signature.pgp From ady at freebsd.ady.ro Tue Aug 12 12:03:31 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 12 12:03:38 2008 Subject: Idea for FreeBSD In-Reply-To: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> Message-ID: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Hi, I'm a bit late to jump on board, but since I'm interested in the subject and previously given some thinking, here are my thoughts. And perhaps the freebsd-rc list is better suited. On Fri, Aug 8, 2008 at 1:20 AM, wrote: > I am surprised by the overwhelming response that this thread has acquired. > I have spent the majority of the day reading all the responses that > everyone has put forward. I would like to clear a few things up, comment > on others, and suggest some solutions to a lot of good points that > everyone has made so far. > > First let me reiterate a few things. I started in FreeBSD and it will > always be my first love. Second, keep in mind that Solaris is a commercial > product and must be viewed as such. Good point. Like it happened in the Linux world, we should also have some commercially backed versions of [Free]BSD in order to get better visibility and business support (which, in the end, counts a lot). That's why I've been thinking for some time about starting up the EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I believe PC-BSD is a good start for the desktop. > > Now that that is out of the way. I want to make it clear to everyone that > I was not suggesting the idea of copying or reproducing any part of how > Sun manages or implements its services; only the CONCEPT of how they do > it. It does not have to be XML, or in a database or anything else. > Actually I am thinking more along the lines of a wrapper that can > read/modify/execute from rc.d and the rc.conf. After all, we do not want > to make drastic changes. No one wants to re-write rc's or move them to > another location. Even solaris still relies on rc scripts to exist. And I > am sure I speak for all of us when I say that we all love the concept of > how rc.conf handles everything. > > As some people have already pointed out multiple times so far, the idea of > an enable/disable is a great idea. Maybe we can start with that and see > how it goes and develop further based on > need/requirements/accomplishments. I also agree that it would be good for the rc.d scripts to (re)configure themselves, since they are the ones who really know what's best for them. While we're at it, I wish we could leverage the posibility for the admin to manually start the service at the CLI, no matter whether the service has been enabled or not -- that is the "_enable" keyword should have effect only in the bootup/automatic contexts. > > I think a drop-in command like "rcadm" (someone mentioned this as an idea, > but cant remember who) would be a good start for managing the states of > services. Mike Meyer also brought up many good points that I agree with. > Please try not to get caught up in the XML stuff, that is not a > requirement or suggestion, it is just an example of how Sun did it, now > how FreeBSD has to;) > > Someone recommended Puppet, but this is an entire framework that would > have to be added/implemented and configured to work with FreeBSD as well > as learning a new markup language for it. launchd has a lot of good ideas, > but I am not sure how mature it is yet; maybe it is a good place to start. Let's put another name on the table: Upstart (upstart.ubuntu.com). It's quite fast. > > If we start with the basics and break it down and program this from a > modular standpoint it is not so bad. Begin with the basic (high-level) > approach. A shell script (service) that is aware of where rc scripts are > located and that can keep track of what the current state of the services > (PID's) are. An enable/disable command is nothing more that throwing a > start/stop command to these rc files. The rc.conf can assist with knowing > what should be enabled/disabled and what flags to throw at it. For > EXAMPLE!!!!, (you got that, example only) Solaris uses one master service > that is started first, and the whole point of that first service is to > monitor the other services and know what state they are in and starts > dependent services upon boot. Consider it the service manager almost. That would very important to for service crash recovery, to keep critical services running. Side note:what about starting up and monitoring services in jails, probably we'd need one such master service per jail ? My 5cents, Adrian. From vince at unsane.co.uk Tue Aug 12 12:29:23 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Aug 12 12:29:32 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Message-ID: <48A18213.3050307@unsane.co.uk> Adrian Penisoara wrote: > > > I also agree that it would be good for the rc.d scripts to > (re)configure themselves, since they are the ones who really know > what's best for them. > > While we're at it, I wish we could leverage the posibility for the > admin to manually start the service at the CLI, no matter whether the > service has been enabled or not -- that is the "_enable" keyword > should have effect only in the bootup/automatic contexts. > > /etc/rc.d/$service forcestart seems to be what you want. I do like the idea of being able to enable/disable services from the rc scripts as /etc/rc.d/$service rcvar | sed 's/NO/YES/' >> /etc/rc.conf and/or editing rc.conf can feel a little clunky at times. Vince >> I think a drop-in command like "rcadm" (someone mentioned this as an idea, >> but cant remember who) would be a good start for managing the states of >> services. Mike Meyer also brought up many good points that I agree with. >> Please try not to get caught up in the XML stuff, that is not a >> requirement or suggestion, it is just an example of how Sun did it, now >> how FreeBSD has to;) >> >> Someone recommended Puppet, but this is an entire framework that would >> have to be added/implemented and configured to work with FreeBSD as well >> as learning a new markup language for it. launchd has a lot of good ideas, >> but I am not sure how mature it is yet; maybe it is a good place to start. >> > > Let's put another name on the table: Upstart (upstart.ubuntu.com). > It's quite fast. > > >> If we start with the basics and break it down and program this from a >> modular standpoint it is not so bad. Begin with the basic (high-level) >> approach. A shell script (service) that is aware of where rc scripts are >> located and that can keep track of what the current state of the services >> (PID's) are. An enable/disable command is nothing more that throwing a >> start/stop command to these rc files. The rc.conf can assist with knowing >> what should be enabled/disabled and what flags to throw at it. For >> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >> that is started first, and the whole point of that first service is to >> monitor the other services and know what state they are in and starts >> dependent services upon boot. Consider it the service manager almost. >> > > That would very important to for service crash recovery, to keep > critical services running. > > Side note:what about starting up and monitoring services in jails, > probably we'd need one such master service per jail ? > > My 5cents, > Adrian. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From stefan.lambrev at moneybookers.com Tue Aug 12 12:36:40 2008 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Aug 12 12:36:47 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Message-ID: <48A183D0.6070901@moneybookers.com> Adrian Penisoara wrote: > Hi, > > I'm a bit late to jump on board, but since I'm interested in the > subject and previously given some thinking, here are my thoughts. > > And perhaps the freebsd-rc list is better suited. > > On Fri, Aug 8, 2008 at 1:20 AM, wrote: > >> I am surprised by the overwhelming response that this thread has acquired. >> I have spent the majority of the day reading all the responses that >> everyone has put forward. I would like to clear a few things up, comment >> on others, and suggest some solutions to a lot of good points that >> everyone has made so far. >> >> First let me reiterate a few things. I started in FreeBSD and it will >> always be my first love. Second, keep in mind that Solaris is a commercial >> product and must be viewed as such. >> > > Good point. Like it happened in the Linux world, we should also have > some commercially backed versions of [Free]BSD in order to get better > visibility and business support (which, in the end, counts a lot). > That's why I've been thinking for some time about starting up the > EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I > believe PC-BSD is a good start for the desktop. > There is commercial support for FreeBSD out there. Actually the problem is that misinformed people are still spreading the lie that there is not... Also the example with Linux is very bad, where you have a "stable" version only in enterprise RH or SuSe and the vanilla kernel is only for development and beta testing .. I do not want to see this happens to FreeBSD > >> Now that that is out of the way. I want to make it clear to everyone that >> I was not suggesting the idea of copying or reproducing any part of how >> Sun manages or implements its services; only the CONCEPT of how they do >> it. It does not have to be XML, or in a database or anything else. >> Actually I am thinking more along the lines of a wrapper that can >> read/modify/execute from rc.d and the rc.conf. After all, we do not want >> to make drastic changes. No one wants to re-write rc's or move them to >> another location. Even solaris still relies on rc scripts to exist. And I >> am sure I speak for all of us when I say that we all love the concept of >> how rc.conf handles everything. >> >> As some people have already pointed out multiple times so far, the idea of >> an enable/disable is a great idea. Maybe we can start with that and see >> how it goes and develop further based on >> need/requirements/accomplishments. >> > > I also agree that it would be good for the rc.d scripts to > (re)configure themselves, since they are the ones who really know > what's best for them. > > While we're at it, I wish we could leverage the posibility for the > admin to manually start the service at the CLI, no matter whether the > service has been enabled or not -- that is the "_enable" keyword > should have effect only in the bootup/automatic contexts. > Like keywords - forcestart forcerestart forcestop ?!?! > >> I think a drop-in command like "rcadm" (someone mentioned this as an idea, >> but cant remember who) would be a good start for managing the states of >> services. Mike Meyer also brought up many good points that I agree with. >> Please try not to get caught up in the XML stuff, that is not a >> requirement or suggestion, it is just an example of how Sun did it, now >> how FreeBSD has to;) >> >> Someone recommended Puppet, but this is an entire framework that would >> have to be added/implemented and configured to work with FreeBSD as well >> as learning a new markup language for it. launchd has a lot of good ideas, >> but I am not sure how mature it is yet; maybe it is a good place to start. >> > > Let's put another name on the table: Upstart (upstart.ubuntu.com). > It's quite fast. > Some of us use FreeBSD because we think this is the proper way things to be done, if we want another linux distro we may switch to *buntu .. > >> If we start with the basics and break it down and program this from a >> modular standpoint it is not so bad. Begin with the basic (high-level) >> approach. A shell script (service) that is aware of where rc scripts are >> located and that can keep track of what the current state of the services >> (PID's) are. An enable/disable command is nothing more that throwing a >> start/stop command to these rc files. The rc.conf can assist with knowing >> what should be enabled/disabled and what flags to throw at it. For >> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >> that is started first, and the whole point of that first service is to >> monitor the other services and know what state they are in and starts >> dependent services upon boot. Consider it the service manager almost. >> > > That would very important to for service crash recovery, to keep > critical services running. > Looks like we are reinventing inetd ? > Side note:what about starting up and monitoring services in jails, > probably we'd need one such master service per jail ? > Like inetd running in jail ? > My 5cents, > Overpriced ;) and good luck with enterprisebsd > Adrian. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From jonathan+freebsd-hackers at hst.org.za Tue Aug 12 12:45:46 2008 From: jonathan+freebsd-hackers at hst.org.za (Jonathan McKeown) Date: Tue Aug 12 12:45:53 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> Message-ID: <200808121414.44139.jonathan+freebsd-hackers@hst.org.za> On Tuesday 12 August 2008 14:03:30 Adrian Penisoara wrote: > ?While we're at it, I wish we could leverage the posibility for the > admin to manually start the service at the CLI, no matter whether the > service has been enabled or not -- that is the "_enable" keyword > should have effect only in the bootup/automatic contexts. Isn't this what onestart does? Jonathan From ady at freebsd.ady.ro Tue Aug 12 14:22:49 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 12 14:22:56 2008 Subject: Idea for FreeBSD In-Reply-To: <48A183D0.6070901@moneybookers.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <48A183D0.6070901@moneybookers.com> Message-ID: <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> Hi, On Tue, Aug 12, 2008 at 2:36 PM, Stefan Lambrev wrote: >>> >>> First let me reiterate a few things. I started in FreeBSD and it will >>> always be my first love. Second, keep in mind that Solaris is a >>> commercial >>> product and must be viewed as such. >>> >> >> Good point. Like it happened in the Linux world, we should also have >> some commercially backed versions of [Free]BSD in order to get better >> visibility and business support (which, in the end, counts a lot). >> That's why I've been thinking for some time about starting up the >> EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I >> believe PC-BSD is a good start for the desktop. >> > > There is commercial support for FreeBSD out there. > Actually the problem is that misinformed people are still spreading the lie > that there is not... OK, I will reword that a bit: I believe having also a "business" face for the business market will help a lot in increasing visibility. > > Also the example with Linux is very bad, where you have a "stable" version > only in enterprise RH or SuSe > and the vanilla kernel is only for development and beta testing .. I do not > want to see this happens to FreeBSD I'm not sure where is that remark headed to. And I don't think (re)packaging a business-centric version would harm -- please correct me if I'm wrong. >> While we're at it, I wish we could leverage the posibility for the >> admin to manually start the service at the CLI, no matter whether the >> service has been enabled or not -- that is the "_enable" keyword >> should have effect only in the bootup/automatic contexts. >> > > Like keywords - forcestart forcerestart forcestop ?!?! Yes, I am always reminded of that :). Well, to tell you the truth, I do not know of any other OS which requires prefixing with "force" the start/stop actions in order to act on the service at the command line, and personally I wish it weren't the case. >>> I think a drop-in command like "rcadm" (someone mentioned this as an >>> idea, >>> but cant remember who) would be a good start for managing the states of >>> services. Mike Meyer also brought up many good points that I agree with. >>> Please try not to get caught up in the XML stuff, that is not a >>> requirement or suggestion, it is just an example of how Sun did it, now >>> how FreeBSD has to;) >>> >>> Someone recommended Puppet, but this is an entire framework that would >>> have to be added/implemented and configured to work with FreeBSD as well >>> as learning a new markup language for it. launchd has a lot of good >>> ideas, >>> but I am not sure how mature it is yet; maybe it is a good place to >>> start. >>> >> >> Let's put another name on the table: Upstart (upstart.ubuntu.com). >> It's quite fast. >> > > Some of us use FreeBSD because we think this is the proper way things to be > done, if we want another linux distro we may switch to *buntu .. Oh, we are debating here, not imposing personal preferences :). Good ideas can come up from any direction, it's up to us whether we want to learn from them. >>> If we start with the basics and break it down and program this from a >>> modular standpoint it is not so bad. Begin with the basic (high-level) >>> approach. A shell script (service) that is aware of where rc scripts are >>> located and that can keep track of what the current state of the services >>> (PID's) are. An enable/disable command is nothing more that throwing a >>> start/stop command to these rc files. The rc.conf can assist with knowing >>> what should be enabled/disabled and what flags to throw at it. For >>> EXAMPLE!!!!, (you got that, example only) Solaris uses one master service >>> that is started first, and the whole point of that first service is to >>> monitor the other services and know what state they are in and starts >>> dependent services upon boot. Consider it the service manager almost. >>> >> >> That would very important to for service crash recovery, to keep >> critical services running. >> > > Looks like we are reinventing inetd ? Inetd is only for multiplexing seldomly used network services bound to specific ports -- not too many real-life services fall under this exact specification. >> >> Side note:what about starting up and monitoring services in jails, >> probably we'd need one such master service per jail ? >> > > Like inetd running in jail ? >> >> My 5cents, >> > > Overpriced ;) and good luck with enterprisebsd Well, that was usually conceived as a contribution, not a price. Ideas are free anyway ;). Thanks. Adrian. From stefan.lambrev at moneybookers.com Tue Aug 12 14:52:11 2008 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Aug 12 14:52:29 2008 Subject: Idea for FreeBSD In-Reply-To: <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <48A183D0.6070901@moneybookers.com> <78cb3d3f0808120722t461bfb56x4782899811cf63f0@mail.gmail.com> Message-ID: <48A1A391.9090808@moneybookers.com> Adrian Penisoara wrote: > Hi, > > On Tue, Aug 12, 2008 at 2:36 PM, Stefan Lambrev > wrote: > >>>> First let me reiterate a few things. I started in FreeBSD and it will >>>> always be my first love. Second, keep in mind that Solaris is a >>>> commercial >>>> product and must be viewed as such. >>>> >>>> >>> Good point. Like it happened in the Linux world, we should also have >>> some commercially backed versions of [Free]BSD in order to get better >>> visibility and business support (which, in the end, counts a lot). >>> That's why I've been thinking for some time about starting up the >>> EnterpriseBSD project (see http://launchpad.net/enterprisebsd). I >>> believe PC-BSD is a good start for the desktop. >>> >>> >> There is commercial support for FreeBSD out there. >> Actually the problem is that misinformed people are still spreading the lie >> that there is not... >> > > OK, I will reword that a bit: I believe having also a "business" face > for the business market will help a lot in increasing visibility. > > >> Also the example with Linux is very bad, where you have a "stable" version >> only in enterprise RH or SuSe >> and the vanilla kernel is only for development and beta testing .. I do not >> want to see this happens to FreeBSD >> > > I'm not sure where is that remark headed to. And I don't think > (re)packaging a business-centric version would harm -- please correct > me if I'm wrong. > The problem with "enterprise" is that they ship their own kernel which is heavily modified. If you want enterprise go for OSX :) I think it's the best enterprise BSDish system ;) Also there are more packages for FreeBSD available then for RH, and I can assure you that all programs that you actually use (like ssh, apache, perl and etc) you have to manually compile to fit your needs. > >>> While we're at it, I wish we could leverage the posibility for the >>> admin to manually start the service at the CLI, no matter whether the >>> service has been enabled or not -- that is the "_enable" keyword >>> should have effect only in the bootup/automatic contexts. >>> >>> >> Like keywords - forcestart forcerestart forcestop ?!?! >> > > Yes, I am always reminded of that :). > Well, to tell you the truth, I do not know of any other OS which > requires prefixing with "force" the start/stop actions in order to act > on the service at the command line, and personally I wish it weren't > the case. > Well I bet you can find this in most linux distros that copy FreeBSD. What about gentoo? Anyway I think that the beauty of the current rc/ng system in freebsd is that it's very easy to understand and use it. Not like those nasty XML config files that makes you blind. There are small fixes that can be applied to make the system even better, but rewriting it just for the sport looks like wasting too much power :) But after all FreeBSD innovate do not imitate ;) Anyway it's may be just me, but I do not think that the rc system in freebsd is the showstopper, that needs funding or more ppl looking at it. And btw burdening the rc subsystem to monitor your daemons is overkill too. It will never work as good as real monitoring software, and will only bloat things. There are tons of utilities that can do this. -cut- -- Best Wishes, Stefan Lambrev ICQ# 24134177 From ady at freebsd.ady.ro Tue Aug 12 15:10:23 2008 From: ady at freebsd.ady.ro (Adrian Penisoara) Date: Tue Aug 12 15:10:29 2008 Subject: FreeBSD in Business (was Re: Idea for FreeBSD) Message-ID: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> Hi, On Tue, Aug 12, 2008 at 4:52 PM, Stefan Lambrev wrote: >> I'm not sure where is that remark headed to. And I don't think >> (re)packaging a business-centric version would harm -- please correct >> me if I'm wrong. >> > > The problem with "enterprise" is that they ship their own kernel which is > heavily modified. Not one, but rather multiple kernels (which includes the generic one). Which otherwise are possible to build with the vanilla distro, but it might take a lot of tweaking time to get there and you got no QA for that either. > If you want enterprise go for OSX :) I think it's the best enterprise BSDish > system ;) Why not help the people already using FreeBSD at their workplace get better arguments to keep and grow the FreeBSD base ? ;) > Also there are more packages for FreeBSD available then for RH, and I can > assure you that > all programs that you actually use (like ssh, apache, perl and etc) you have > to manually compile to fit your needs. I tend to disagree in this particular context -- business usage relies on stability which implies a small set of very well tested packages, not necessarily the latest version. >> >> >>>> >>>> While we're at it, I wish we could leverage the posibility for the >>>> admin to manually start the service at the CLI, no matter whether the >>>> service has been enabled or not -- that is the "_enable" keyword >>>> should have effect only in the bootup/automatic contexts. >>>> >>>> >>> >>> Like keywords - forcestart forcerestart forcestop ?!?! >>> >> >> Yes, I am always reminded of that :). >> Well, to tell you the truth, I do not know of any other OS which >> requires prefixing with "force" the start/stop actions in order to act >> on the service at the command line, and personally I wish it weren't >> the case. >> > > Well I bet you can find this in most linux distros that copy FreeBSD. What > about gentoo? Umm, I have used Gentoo and I do not remember having to use "forcestart" at the command line... > Anyway I think that the beauty of the current rc/ng system in freebsd is > that it's very easy to understand and use it. > Not like those nasty XML config files that makes you blind. > There are small fixes that can be applied to make the system even better, > but rewriting it just for the sport looks like wasting too much power :) > But after all FreeBSD innovate do not imitate ;) > > Anyway it's may be just me, but I do not think that the rc system in freebsd > is the showstopper, that needs funding or more ppl looking at it. Right. And I'm going to stop here -- if you want to continue we can go off-the-list. > And btw burdening the rc subsystem to monitor your daemons is overkill too. > It will never work as good as real monitoring software, > and will only bloat things. There are tons of utilities that can do this. Umm, one should not need huge monitoring software packages to accomplish such (simple?) tasks. The inittab/ttys systems comes to my mind when I say this... ;). Over & out, Adrian. From stefan.lambrev at moneybookers.com Tue Aug 12 16:11:50 2008 From: stefan.lambrev at moneybookers.com (Stefan Lambrev) Date: Tue Aug 12 16:11:57 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <20080812115132.44b2e8f7@mbook.local> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <20080812115132.44b2e8f7@mbook.local> Message-ID: <48A1B641.6080407@moneybookers.com> Mike Meyer wrote: > On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" wrote: > >>>>>> While we're at it, I wish we could leverage the posibility for the >>>>>> admin to manually start the service at the CLI, no matter whether the >>>>>> service has been enabled or not -- that is the "_enable" keyword >>>>>> should have effect only in the bootup/automatic contexts. >>>>>> >>>>> Like keywords - forcestart forcerestart forcestop ?!?! >>>>> >>>> Yes, I am always reminded of that :). >>>> Well, to tell you the truth, I do not know of any other OS which >>>> requires prefixing with "force" the start/stop actions in order to act >>>> on the service at the command line, and personally I wish it weren't >>>> the case. >>>> >>> Well I bet you can find this in most linux distros that copy FreeBSD. What >>> about gentoo? >>> >> Umm, I have used Gentoo and I do not remember having to use >> "forcestart" at the command line... >> > > Ok, given that you 1) want to have both "XXXX this service if it's > part of our normal runtime" and "XXXX this service even if it's not > part of our normal runtime" as script commands, and that 2) XXXX > without a prefix gets the "if it's part of our normal runtime" > meaning, as we want the user to have to explicitly say "Yes, I know > this looks odd, but I know what I'm doing so do it anyway" to get the > "even if it's not part of our normal runtime" behavior, then what > would you have us use instead of "forceXXXX"? > > Personally, I think "start -f" or "start --force" might have been > better, but it's to late to fix such a minor thing. > I think the idea (behind not using force) is to implement something like in RH where there is a number of folders (for every run level) populated with links to the real rc scripts which are in /etc/init.d/ and when you type /etc/init.d/script start it will be started but the boot up rc.scripts will never do start on /etc/init.d/ itself only on the folder with links. It's not much better (or worse?) then the current system in freebsd, so I do not see why we should bother. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From mwm at mired.org Tue Aug 12 15:51:36 2008 From: mwm at mired.org (Mike Meyer) Date: Tue Aug 12 16:15:36 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> Message-ID: <20080812115132.44b2e8f7@mbook.local> On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" wrote: > >>>> While we're at it, I wish we could leverage the posibility for the > >>>> admin to manually start the service at the CLI, no matter whether the > >>>> service has been enabled or not -- that is the "_enable" keyword > >>>> should have effect only in the bootup/automatic contexts. > >>> Like keywords - forcestart forcerestart forcestop ?!?! > >> Yes, I am always reminded of that :). > >> Well, to tell you the truth, I do not know of any other OS which > >> requires prefixing with "force" the start/stop actions in order to act > >> on the service at the command line, and personally I wish it weren't > >> the case. > > Well I bet you can find this in most linux distros that copy FreeBSD. What > > about gentoo? > Umm, I have used Gentoo and I do not remember having to use > "forcestart" at the command line... Ok, given that you 1) want to have both "XXXX this service if it's part of our normal runtime" and "XXXX this service even if it's not part of our normal runtime" as script commands, and that 2) XXXX without a prefix gets the "if it's part of our normal runtime" meaning, as we want the user to have to explicitly say "Yes, I know this looks odd, but I know what I'm doing so do it anyway" to get the "even if it's not part of our normal runtime" behavior, then what would you have us use instead of "forceXXXX"? Personally, I think "start -f" or "start --force" might have been better, but it's to late to fix such a minor thing. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From vince at unsane.co.uk Tue Aug 12 16:29:25 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Tue Aug 12 16:29:33 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <48A1B641.6080407@moneybookers.com> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <20080812115132.44b2e8f7@mbook.local> <48A1B641.6080407@moneybookers.com> Message-ID: <48A1BA5E.2050000@unsane.co.uk> Stefan Lambrev wrote: > > > Mike Meyer wrote: >> On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" >> wrote: >> >>>>>>> While we're at it, I wish we could leverage the posibility for the >>>>>>> admin to manually start the service at the CLI, no matter >>>>>>> whether the >>>>>>> service has been enabled or not -- that is the "_enable" >>>>>>> keyword >>>>>>> should have effect only in the bootup/automatic contexts. >>>>>>> >>>>>> Like keywords - forcestart forcerestart forcestop ?!?! >>>>>> >>>>> Yes, I am always reminded of that :). >>>>> Well, to tell you the truth, I do not know of any other OS which >>>>> requires prefixing with "force" the start/stop actions in order to >>>>> act >>>>> on the service at the command line, and personally I wish it weren't >>>>> the case. >>>>> >>>> Well I bet you can find this in most linux distros that copy >>>> FreeBSD. What >>>> about gentoo? >>>> >>> Umm, I have used Gentoo and I do not remember having to use >>> "forcestart" at the command line... >>> >> >> Ok, given that you 1) want to have both "XXXX this service if it's >> part of our normal runtime" and "XXXX this service even if it's not >> part of our normal runtime" as script commands, and that 2) XXXX >> without a prefix gets the "if it's part of our normal runtime" >> meaning, as we want the user to have to explicitly say "Yes, I know >> this looks odd, but I know what I'm doing so do it anyway" to get the >> "even if it's not part of our normal runtime" behavior, then what >> would you have us use instead of "forceXXXX"? >> >> Personally, I think "start -f" or "start --force" might have been >> better, but it's to late to fix such a minor thing. >> > I think the idea (behind not using force) is to implement something > like in RH where there is a number of folders (for every run level) > populated with links to the real rc scripts which are in /etc/init.d/ > and when you type /etc/init.d/script start it will be started > but the boot up rc.scripts will never do start on /etc/init.d/ itself > only on the folder with links. > It's not much better (or worse?) then the current system in freebsd, > so I do not see why we should bother. > http://en.wikipedia.org/wiki/Init I hate sysV style init myself, half of why I moved to *BSD Vince From jonathan+freebsd-hackers at hst.org.za Wed Aug 13 06:11:49 2008 From: jonathan+freebsd-hackers at hst.org.za (Jonathan McKeown) Date: Wed Aug 13 06:11:56 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <20080812115132.44b2e8f7@mbook.local> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <20080812115132.44b2e8f7@mbook.local> Message-ID: <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> On Tuesday 12 August 2008 17:51:32 Mike Meyer wrote: > On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" wrote: > > > > Umm, I have used Gentoo and I do not remember having to use > > "forcestart" at the command line... > > Ok, given that you 1) want to have both "XXXX this service if it's > part of our normal runtime" and "XXXX this service even if it's not > part of our normal runtime" as script commands, and that 2) XXXX > without a prefix gets the "if it's part of our normal runtime" > meaning, as we want the user to have to explicitly say "Yes, I know > this looks odd, but I know what I'm doing so do it anyway" to get the > "even if it's not part of our normal runtime" behavior, then what > would you have us use instead of "forceXXXX"? People keep talking about forcestart. Unless I'm misunderstanding things horribly, forcestart does exactly that - forces the service to start regardless of any error that may occur. The better option for starting something as a one-off (not enabled in rc.conf) is mnemonically named onestart - which only ignores the rcvar but still fails on any other error. And yes, I like having onestart/onestop distinguished from start/stop. Jonathan From neldredge at math.ucsd.edu Wed Aug 13 06:52:36 2008 From: neldredge at math.ucsd.edu (Nate Eldredge) Date: Wed Aug 13 06:52:43 2008 Subject: Debugging reboot with Linux emulation Message-ID: Hi folks, I recently tried to run a Linux binary of Maple (commercial math software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine rebooted. I tried it again while watching the console, and no panic message appeared to be produced. Does anyone have any ideas on how to debug problems of this nature? I realize I may not be able to get Maple to work, but in any case the system should not die like this, so I can at least try to fix that bug. Incidentally, is it possible to run kdb with a USB keyboard? Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I can do nothing except hit the power button. I do have hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I don't have a PS/2 keyboard on hand, though I can try and get a hold of one if all else fails. -- Nate Eldredge neldredge@math.ucsd.edu From vince at unsane.co.uk Wed Aug 13 08:40:59 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Wed Aug 13 08:41:05 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <20080812115132.44b2e8f7@mbook.local> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> Message-ID: <48A29E15.5080303@unsane.co.uk> Jonathan McKeown wrote: > On Tuesday 12 August 2008 17:51:32 Mike Meyer wrote: > >> On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" >> > wrote: > >>> Umm, I have used Gentoo and I do not remember having to use >>> "forcestart" at the command line... >>> >> Ok, given that you 1) want to have both "XXXX this service if it's >> part of our normal runtime" and "XXXX this service even if it's not >> part of our normal runtime" as script commands, and that 2) XXXX >> without a prefix gets the "if it's part of our normal runtime" >> meaning, as we want the user to have to explicitly say "Yes, I know >> this looks odd, but I know what I'm doing so do it anyway" to get the >> "even if it's not part of our normal runtime" behavior, then what >> would you have us use instead of "forceXXXX"? >> > > People keep talking about forcestart. > > Unless I'm misunderstanding things horribly, forcestart does exactly that - > forces the service to start regardless of any error that may occur. > > The better option for starting something as a one-off (not enabled in rc.conf) > is mnemonically named onestart - which only ignores the rcvar but still fails > on any other error. > > And yes, I like having onestart/onestop distinguished from start/stop. > > I believe it "forces" a start even though its not actually enabled (in rc.conf) rather than regardless of errors. If you really want a command line of onestart/onestop install the sysutils/bsdadminscripts port which has a script called rconestart and rconestop which do exactly that ;) Vince > Jonathan > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From dchagin at freebsd.org Wed Aug 13 09:27:21 2008 From: dchagin at freebsd.org (Chagin Dmitry) Date: Wed Aug 13 09:27:28 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: References: Message-ID: <20080813090320.GA12437@dchagin.dialup.corbina.ru> On Tue, Aug 12, 2008 at 11:52:35PM -0700, Nate Eldredge wrote: > Hi folks, > > I recently tried to run a Linux binary of Maple (commercial math software) > on my FreeBSD 7.0-RELEASE/amd64 box, and the machine rebooted. I tried it > again while watching the console, and no panic message appeared to be > produced. Does anyone have any ideas on how to debug problems of this > nature? I realize I may not be able to get Maple to work, but in any case > the system should not die like this, so I can at least try to fix that > bug. > Hi ktrace/linux_kdump, or best - build linux module with -DDEBUG and see where it die. -- Have fun! chd From jonathan+freebsd-hackers at hst.org.za Wed Aug 13 10:25:21 2008 From: jonathan+freebsd-hackers at hst.org.za (Jonathan McKeown) Date: Wed Aug 13 10:25:29 2008 Subject: If not the force, what should I use? In-Reply-To: <48A29E15.5080303@unsane.co.uk> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> Message-ID: <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> On Wednesday 13 August 2008 10:40:53 Vincent Hoffman wrote: > Jonathan McKeown wrote: > > > > > People keep talking about forcestart. > > > > Unless I'm misunderstanding things horribly, forcestart does exactly that > > - forces the service to start regardless of any error that may occur. > > > > The better option for starting something as a one-off (not enabled in > > rc.conf) is mnemonically named onestart - which only ignores the rcvar > > but still fails on any other error. > > > > And yes, I like having onestart/onestop distinguished from start/stop. > > I believe it "forces" a start even though its not actually enabled (in > rc.conf) rather than regardless of errors. > If you really want a command line of onestart/onestop install the > sysutils/bsdadminscripts port which has a script called rconestart and > rconestop which do exactly that ;) No, you don't need to install anything - it's part of rc.subr. From the rc.subr(8) manpage: argument may have one of the following prefixes which alters its operation: fast Skip the check for an existing running process, and sets rc_fast=YES. force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. one Skip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. I certainly use onestart - generally when I'm configuring and testing a new service before enabling it in rc.conf. I also use it with NFS. Whenever I've changed /etc/exports, I force mountd to reread it by issuing /etc/rc.d/mountd onereload Jonathan From vince at unsane.co.uk Wed Aug 13 10:42:41 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Wed Aug 13 10:42:59 2008 Subject: If not the force, what should I use? In-Reply-To: <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> Message-ID: <48A2BA9C.6050804@unsane.co.uk> Jonathan McKeown wrote: > On Wednesday 13 August 2008 10:40:53 Vincent Hoffman wrote: > >> Jonathan McKeown wrote: >> >> >>> People keep talking about forcestart. >>> >>> Unless I'm misunderstanding things horribly, forcestart does exactly that >>> - forces the service to start regardless of any error that may occur. >>> >>> The better option for starting something as a one-off (not enabled in >>> rc.conf) is mnemonically named onestart - which only ignores the rcvar >>> but still fails on any other error. >>> >>> And yes, I like having onestart/onestop distinguished from start/stop. >>> >> I believe it "forces" a start even though its not actually enabled (in >> rc.conf) rather than regardless of errors. >> If you really want a command line of onestart/onestop install the >> sysutils/bsdadminscripts port which has a script called rconestart and >> rconestop which do exactly that ;) >> > > No, you don't need to install anything - it's part of rc.subr. > > From the rc.subr(8) manpage: > > argument may have one of the following prefixes which alters its > operation: > > fast Skip the check for an existing running process, and > sets rc_fast=YES. > > force Skip the checks for rcvar being set to ``YES'', and > sets rc_force=YES. This ignores argument_precmd > returning non-zero, and ignores any of the required_* > tests failing, and always returns a zero exit status. > > one Skip the checks for rcvar being set to ``YES'', but > performs all the other prerequisite tests. > > I certainly use onestart - generally when I'm configuring and testing a new > service before enabling it in rc.conf. > > I also use it with NFS. Whenever I've changed /etc/exports, I force mountd to > reread it by issuing > > /etc/rc.d/mountd onereload > > Doh I just skimmed though /etc/rc.subr not the manpage, thanks for the pointers. Vince > Jonathan > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From Alexander at Leidinger.net Wed Aug 13 11:28:36 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed Aug 13 11:32:27 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: References: Message-ID: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> Quoting "Nate Eldredge" (from Tue, 12 Aug 2008 23:52:35 -0700 (PDT)): > Hi folks, > > I recently tried to run a Linux binary of Maple (commercial math > software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine > rebooted. I tried it again while watching the console, and no panic > message appeared to be produced. Does anyone have any ideas on how > to debug problems of this nature? I realize I may not be able to > get Maple to work, but in any case the system should not die like > this, so I can at least try to fix that bug. > > Incidentally, is it possible to run kdb with a USB keyboard? > Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I > can do nothing except hit the power button. I do have > hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I > don't have a PS/2 keyboard on hand, though I can try and get a hold > of one if all else fails. A guess out of my cristallball: That's one of the cases which happen if you run a linux program without branding it as a linux program first. People tend to think it is not needed, but in some rare circumstances it just causes what you see, a reboot. So go and identify all binaries (IMPORTANT: but not the libraries!), e.g. with the file(1), and use "brandelf -t Linux" on those programs. Bye, Alexander. -- She said, "I know you ... you cannot sing." I said, "That's nothing, you should hear me play piano." -- Morrisey http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From kostikbel at gmail.com Wed Aug 13 11:54:18 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Wed Aug 13 11:54:24 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> Message-ID: <20080813115413.GF1803@deviant.kiev.zoral.com.ua> On Wed, Aug 13, 2008 at 01:28:22PM +0200, Alexander Leidinger wrote: > Quoting "Nate Eldredge" (from Tue, 12 Aug > 2008 23:52:35 -0700 (PDT)): > > >Hi folks, > > > >I recently tried to run a Linux binary of Maple (commercial math > >software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine > >rebooted. I tried it again while watching the console, and no panic > >message appeared to be produced. Does anyone have any ideas on how > >to debug problems of this nature? I realize I may not be able to > >get Maple to work, but in any case the system should not die like > >this, so I can at least try to fix that bug. > > > >Incidentally, is it possible to run kdb with a USB keyboard? > >Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I > >can do nothing except hit the power button. I do have > >hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I > >don't have a PS/2 keyboard on hand, though I can try and get a hold > >of one if all else fails. > > A guess out of my cristallball: > That's one of the cases which happen if you run a linux program > without branding it as a linux program first. People tend to think it > is not needed, but in some rare circumstances it just causes what you > see, a reboot. So go and identify all binaries (IMPORTANT: but not the > libraries!), e.g. with the file(1), and use "brandelf -t Linux" on > those programs. That would be an enormous local hole, assuming an native FreeBSD binary may cause system crash. I actually doubt that non-branded elf binary ever start, due to unsatisfied dynamic dependencies. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080813/6d6be562/attachment.pgp From mwm-keyword-freebsdhackers2.e313df at mired.org Wed Aug 13 12:01:58 2008 From: mwm-keyword-freebsdhackers2.e313df at mired.org (Mike Meyer) Date: Wed Aug 13 12:02:06 2008 Subject: If not the force, what should I use? In-Reply-To: <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> Message-ID: <20080813080032.2328a474@bhuda.mired.org> On Wed, 13 Aug 2008 12:27:30 +0200 Jonathan McKeown wrote: > On Wednesday 13 August 2008 10:40:53 Vincent Hoffman wrote: > > Jonathan McKeown wrote: > > > People keep talking about forcestart. > > > > > > Unless I'm misunderstanding things horribly, forcestart does exactly that > > > - forces the service to start regardless of any error that may occur. > > > > > > The better option for starting something as a one-off (not enabled in > > > rc.conf) is mnemonically named onestart - which only ignores the rcvar > > > but still fails on any other error. > > > > > > And yes, I like having onestart/onestop distinguished from start/stop. > > > > I believe it "forces" a start even though its not actually enabled (in > > rc.conf) rather than regardless of errors. > > If you really want a command line of onestart/onestop install the > > sysutils/bsdadminscripts port which has a script called rconestart and > > rconestop which do exactly that ;) > > No, you don't need to install anything - it's part of rc.subr. > > From the rc.subr(8) manpage: > > argument may have one of the following prefixes which alters its > operation: > > fast Skip the check for an existing running process, and > sets rc_fast=YES. > > force Skip the checks for rcvar being set to ``YES'', and > sets rc_force=YES. This ignores argument_precmd > returning non-zero, and ignores any of the required_* > tests failing, and always returns a zero exit status. > > one Skip the checks for rcvar being set to ``YES'', but > performs all the other prerequisite tests. In that case, someone should file a doc bug for the rc(8) manpage, which says: Each script is expected to support at least the following arguments, which are automatically supported if it uses the run_rc_command() func- tion: start Start the service. This should check that the service is to be started as specified by rc.conf(5). Also checks if the service is already running and refuses to start if it is. This latter check is not performed by standard FreeBSD scripts if the system is starting directly to multi-user mode, to speed up the boot process. If forcestart is given, ignore the rc.conf(5) check and start anyway. stop If the service is to be started as specified by rc.conf(5), stop the service. This should check that the service is running and complain if it is not. If forcestop is given, ignore the rc.conf(5) check and attempt to stop. I don't have time to do it now, but will later if no one says they have.... http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From Alexander at Leidinger.net Wed Aug 13 11:50:35 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed Aug 13 12:18:25 2008 Subject: Idea for FreeBSD In-Reply-To: <20080807202041.GB9084@pix.net> References: <20080807090230.GF1359@server.vk2pj.dyndns.org> <20080807202041.GB9084@pix.net> Message-ID: <20080813133249.18962h78i0f90g4k@webmail.leidinger.net> Quoting "Kurt J. Lidl" (from Thu, 7 Aug 2008 16:20:42 -0400): > On Thu, Aug 07, 2008 at 07:02:30PM +1000, Peter Jeremy wrote: >> On 2008-Aug-06 19:14:51 -0400, wbentley@futurecis.com wrote: >> > In Solaris 10 the Services Management Facility (SMF) was introduced. >> >> The main purpose of SMF appears to be to drum up business for Sun's >> training courses by radically changing Sol10 Administration for little >> benefit. > > The main purpose of SMF was to make it possible to programmatically > control the system and deal with the myriad of different types of > faults from the gazillion different things that people want to run > on machines. It's complex because it has to deal with the real > world. There's also some sort of functionality included, which is comparable with daemontools (depending if you enable this in the xml description or not). You could say this is included in your "deal with ... faults" above, but for people not aware of this it may be nice to know. Bye, Alexander. -- Life may have no meaning, or, even worse, it may have a meaning of which you disapprove. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From kostikbel at gmail.com Wed Aug 13 14:11:04 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Wed Aug 13 14:11:10 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> Message-ID: <20080813141059.GH1803@deviant.kiev.zoral.com.ua> On Wed, Aug 13, 2008 at 04:03:53PM +0200, Alexander Leidinger wrote: > Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 > 14:54:13 +0300): > > >On Wed, Aug 13, 2008 at 01:28:22PM +0200, Alexander Leidinger wrote: > >>Quoting "Nate Eldredge" (from Tue, 12 Aug > >>2008 23:52:35 -0700 (PDT)): > >> > >>>Hi folks, > >>> > >>>I recently tried to run a Linux binary of Maple (commercial math > >>>software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine > >>>rebooted. I tried it again while watching the console, and no panic > >>>message appeared to be produced. Does anyone have any ideas on how > >>>to debug problems of this nature? I realize I may not be able to > >>>get Maple to work, but in any case the system should not die like > >>>this, so I can at least try to fix that bug. > >>> > >>>Incidentally, is it possible to run kdb with a USB keyboard? > >>>Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I > >>>can do nothing except hit the power button. I do have > >>>hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I > >>>don't have a PS/2 keyboard on hand, though I can try and get a hold > >>>of one if all else fails. > >> > >>A guess out of my cristallball: > >>That's one of the cases which happen if you run a linux program > >>without branding it as a linux program first. People tend to think it > >>is not needed, but in some rare circumstances it just causes what you > >>see, a reboot. So go and identify all binaries (IMPORTANT: but not the > >>libraries!), e.g. with the file(1), and use "brandelf -t Linux" on > >>those programs. > > > >That would be an enormous local hole, assuming an native FreeBSD binary > >may cause system crash. I actually doubt that non-branded elf binary > >ever start, due to unsatisfied dynamic dependencies. > > You see this behavior only for static binaries. In the non-branded > case the image activator takes the FreeBSD image and unfortunately > there's a common syscall in linux which matches the syscall number in > FreeBSD which causes the reboot (IIRC reboot syscall, do we have > something like this?). It's not a system crash (kernel panic), it's a > real reboot. AFAIR this also only works if you run the program as > root. So... Then, the issue of mixing our reboot(2)/linux fcntl(2) is irrelevant. The original reporter said that system "just rebooted", and I believe that filesystems where not synced and not unmounted properly. Our reboot(2) does not have flag combination that could cause such behaviour, I think. Also, I doubt that the program being run is statically linked or run by root. Confirmation ? Overall, this looks like a nasty bug, hopefully in the linuxolator. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080813/9cc2ea75/attachment.pgp From Alexander at Leidinger.net Wed Aug 13 14:04:06 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed Aug 13 14:55:10 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813115413.GF1803@deviant.kiev.zoral.com.ua> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> Message-ID: <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 14:54:13 +0300): > On Wed, Aug 13, 2008 at 01:28:22PM +0200, Alexander Leidinger wrote: >> Quoting "Nate Eldredge" (from Tue, 12 Aug >> 2008 23:52:35 -0700 (PDT)): >> >> >Hi folks, >> > >> >I recently tried to run a Linux binary of Maple (commercial math >> >software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine >> >rebooted. I tried it again while watching the console, and no panic >> >message appeared to be produced. Does anyone have any ideas on how >> >to debug problems of this nature? I realize I may not be able to >> >get Maple to work, but in any case the system should not die like >> >this, so I can at least try to fix that bug. >> > >> >Incidentally, is it possible to run kdb with a USB keyboard? >> >Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I >> >can do nothing except hit the power button. I do have >> >hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I >> >don't have a PS/2 keyboard on hand, though I can try and get a hold >> >of one if all else fails. >> >> A guess out of my cristallball: >> That's one of the cases which happen if you run a linux program >> without branding it as a linux program first. People tend to think it >> is not needed, but in some rare circumstances it just causes what you >> see, a reboot. So go and identify all binaries (IMPORTANT: but not the >> libraries!), e.g. with the file(1), and use "brandelf -t Linux" on >> those programs. > > That would be an enormous local hole, assuming an native FreeBSD binary > may cause system crash. I actually doubt that non-branded elf binary > ever start, due to unsatisfied dynamic dependencies. You see this behavior only for static binaries. In the non-branded case the image activator takes the FreeBSD image and unfortunately there's a common syscall in linux which matches the syscall number in FreeBSD which causes the reboot (IIRC reboot syscall, do we have something like this?). It's not a system crash (kernel panic), it's a real reboot. AFAIR this also only works if you run the program as root. So... Bye, Alexander. -- Blow it out your ear. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From Alexander at Leidinger.net Wed Aug 13 15:28:23 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed Aug 13 15:35:43 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813141059.GH1803@deviant.kiev.zoral.com.ua> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> <20080813141059.GH1803@deviant.kiev.zoral.com.ua> Message-ID: <20080813172805.26324k9zft01f62o@webmail.leidinger.net> Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 17:10:59 +0300): > On Wed, Aug 13, 2008 at 04:03:53PM +0200, Alexander Leidinger wrote: >> Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 >> 14:54:13 +0300): >> >> >On Wed, Aug 13, 2008 at 01:28:22PM +0200, Alexander Leidinger wrote: >> >>Quoting "Nate Eldredge" (from Tue, 12 Aug >> >>2008 23:52:35 -0700 (PDT)): >> >> >> >>>Hi folks, >> >>> >> >>>I recently tried to run a Linux binary of Maple (commercial math >> >>>software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine >> >>>rebooted. I tried it again while watching the console, and no panic >> >>>message appeared to be produced. Does anyone have any ideas on how >> >>>to debug problems of this nature? I realize I may not be able to >> >>>get Maple to work, but in any case the system should not die like >> >>>this, so I can at least try to fix that bug. >> >>> >> >>>Incidentally, is it possible to run kdb with a USB keyboard? >> >>>Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I >> >>>can do nothing except hit the power button. I do have >> >>>hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I >> >>>don't have a PS/2 keyboard on hand, though I can try and get a hold >> >>>of one if all else fails. >> >> >> >>A guess out of my cristallball: >> >>That's one of the cases which happen if you run a linux program >> >>without branding it as a linux program first. People tend to think it >> >>is not needed, but in some rare circumstances it just causes what you >> >>see, a reboot. So go and identify all binaries (IMPORTANT: but not the >> >>libraries!), e.g. with the file(1), and use "brandelf -t Linux" on >> >>those programs. >> > >> >That would be an enormous local hole, assuming an native FreeBSD binary >> >may cause system crash. I actually doubt that non-branded elf binary >> >ever start, due to unsatisfied dynamic dependencies. >> >> You see this behavior only for static binaries. In the non-branded >> case the image activator takes the FreeBSD image and unfortunately >> there's a common syscall in linux which matches the syscall number in >> FreeBSD which causes the reboot (IIRC reboot syscall, do we have >> something like this?). It's not a system crash (kernel panic), it's a >> real reboot. AFAIR this also only works if you run the program as >> root. So... > > Then, the issue of mixing our reboot(2)/linux fcntl(2) is irrelevant. > The original reporter said that system "just rebooted", and I believe > that filesystems where not synced and not unmounted properly. Our > reboot(2) does not have flag combination that could cause such > behaviour, I think. > > Also, I doubt that the program being run is statically linked or > run by root. Confirmation ? I will not be surprised if it is statically linked and run by root. I've seen enough such cases with commercial software and users using it, that my cristalball caused me to send my first reply to the problem. > Overall, this looks like a nasty bug, hopefully in the linuxolator. The linuxulator is not involved, as there's no branding it is not invoked. The same will happen if the linxulator is not in the kernel. Bye, Alexander. -- If value corrupts then absolute value corrupts absolutely. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From koitsu at FreeBSD.org Wed Aug 13 15:47:00 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Wed Aug 13 15:47:07 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> Message-ID: <20080813154700.GA1938@eos.sc1.parodius.com> On Wed, Aug 13, 2008 at 04:03:53PM +0200, Alexander Leidinger wrote: > Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 > 14:54:13 +0300): > >> On Wed, Aug 13, 2008 at 01:28:22PM +0200, Alexander Leidinger wrote: >>> Quoting "Nate Eldredge" (from Tue, 12 Aug >>> 2008 23:52:35 -0700 (PDT)): >>> >>> >Hi folks, >>> > >>> >I recently tried to run a Linux binary of Maple (commercial math >>> >software) on my FreeBSD 7.0-RELEASE/amd64 box, and the machine >>> >rebooted. I tried it again while watching the console, and no panic >>> >message appeared to be produced. Does anyone have any ideas on how >>> >to debug problems of this nature? I realize I may not be able to >>> >get Maple to work, but in any case the system should not die like >>> >this, so I can at least try to fix that bug. >>> > >>> >Incidentally, is it possible to run kdb with a USB keyboard? >>> >Hitting Ctrl-Alt-Esc gives me the kdb prompt, but I can't type, so I >>> >can do nothing except hit the power button. I do have >>> >hint.atkbd.0.flags="0x1" in /boot/device.hints. Unfortunately I >>> >don't have a PS/2 keyboard on hand, though I can try and get a hold >>> >of one if all else fails. >>> >>> A guess out of my cristallball: >>> That's one of the cases which happen if you run a linux program >>> without branding it as a linux program first. People tend to think it >>> is not needed, but in some rare circumstances it just causes what you >>> see, a reboot. So go and identify all binaries (IMPORTANT: but not the >>> libraries!), e.g. with the file(1), and use "brandelf -t Linux" on >>> those programs. >> >> That would be an enormous local hole, assuming an native FreeBSD binary >> may cause system crash. I actually doubt that non-branded elf binary >> ever start, due to unsatisfied dynamic dependencies. > > You see this behavior only for static binaries. In the non-branded case > the image activator takes the FreeBSD image and unfortunately there's a > common syscall in linux which matches the syscall number in FreeBSD which > causes the reboot (IIRC reboot syscall, do we have something like this?). > It's not a system crash (kernel panic), it's a real reboot. AFAIR this > also only works if you run the program as root. So... There is indeed a reboot syscall, #55: /usr/include/sys/sycall.h: #define SYS_reboot 55 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From avg at icyb.net.ua Wed Aug 13 16:05:18 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Wed Aug 13 16:05:25 2008 Subject: tilt/horizontal scroll support Message-ID: <48A300B9.5090105@icyb.net.ua> I have the following mouse: http://www.logitech.com/index.cfm/partners/system_builders_integrators/products/mice/devices/3141&cl=gb,en# It has "Tilt Wheel Plus Zoom? technology", i.e. its scroll wheel can be tilted left and right. Currently it perfectly works as 3 buttons + wheel mouse, but tilting action does not cause any effect (in xev). This is some debug output from ums driver: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/27.20, addr 2, iclass 3/1 ums0: 8 buttons and Z dir. ums_attach: sc=0xffffff004d747400 ums_attach: X 8/8 ums_attach: Y 16/8 ums_attach: Z 24/8 ums_attach: B1 0/1 ums_attach: B2 1/1 ums_attach: B3 2/1 ums_attach: B4 3/1 ums_attach: B5 4/1 ums_attach: B6 5/1 ums_attach: B7 6/1 ums_attach: B8 7/1 Here's how "normal"/vertical scrolling of the wheel is reported by ums (one scroll forward and one scroll backward): ums_intr: sc=0xffffff006b502400 status=0 ums_intr: data = 00 00 00 ff 00 ums_intr: x:0 y:0 z:1 t:0 buttons:0x0 ums_intr: sc=0xffffff006b502400 status=0 ums_intr: data = 00 00 00 01 00 ums_intr: x:0 y:0 z:-1 t:0 buttons:0x0 As expected value in the 4th byte (data[3]) is interpreted as z-axis movement (and seems to always be +1/-1). Here's how tilting of the wheel is reported (tilted the wheel, held it for some time and then released): ums_intr: sc=0xffffff004d747400 status=0 ums_intr: data = 00 00 00 00 01 ums_intr: x:0 y:0 z:0 t:0 buttons:0x0 ums_intr: sc=0xffffff004d747400 status=0 ums_intr: data = 00 00 00 00 01 ums_intr: x:0 y:0 z:0 t:0 buttons:0x0 ums_intr: sc=0xffffff004d747400 status=0 ums_intr: data = 00 00 00 00 01 ums_intr: x:0 y:0 z:0 t:0 buttons:0x0 ums_intr: sc=0xffffff004d747400 status=0 ums_intr: data = 00 00 00 00 00 ums_intr: x:0 y:0 z:0 t:0 buttons:0x0 It seems that tilting is reported by value in the 5th byte (data[4]), it has hardware "auto-repeat" and end of tilting is reported by all-zeroes data. Currently, it seems, data[4] is completely ignored. I would like to get tilting to work as horizontal scrolling in X, using SysMouse protocol. As I understand currently our sysmouse(4) protocol doesn't provide for tilting data (there is no field for it in the packet structure), and Xorg sysmouse driver does not have any support for tilting either. So now I have two questions. 1. What would be the best way to each ums about the tilt capability of this mouse? Is there some generic way to detect it or maybe logitech-specific way or some model-specific quirk is required? 2. What would be the best way to pass tilting data to consumers? I see two possibilities: A) map data[4] to some extended button value (do it in ums driver), e.g. to button 6 and button 7; B) it seems that dz value is always 1 or -1, amount of scrolling affects number of mouse events, but abs(dz) is always 1; if this is really always true, then tilting could be piggy-backed onto dz as +2/-2 value (or some such) and then Xorg sysmouse driver could be taught to interpret such values as special button presses (similarly to how vertical scrolling is handled in it). Thank you in advance for advices and opinions. -- Andriy Gapon From rpaulo at FreeBSD.org Wed Aug 13 16:29:41 2008 From: rpaulo at FreeBSD.org (Rui Paulo) Date: Wed Aug 13 16:29:47 2008 Subject: tilt/horizontal scroll support In-Reply-To: <48A300B9.5090105@icyb.net.ua> References: <48A300B9.5090105@icyb.net.ua> Message-ID: <20080813162931.GC718@epsilon.local> On Wed, Aug 13, 2008 at 06:41:45PM +0300, Andriy Gapon wrote: > > I have the following mouse: > http://www.logitech.com/index.cfm/partners/system_builders_integrators/products/mice/devices/3141&cl=gb,en# ... > So now I have two questions. > 1. What would be the best way to each ums about the tilt capability of > this mouse? Is there some generic way to detect it or maybe > logitech-specific way or some model-specific quirk is required? > > 2. What would be the best way to pass tilting data to consumers? > I see two possibilities: > A) map data[4] to some extended button value (do it in ums driver), e.g. > to button 6 and button 7; > B) it seems that dz value is always 1 or -1, amount of scrolling affects > number of mouse events, but abs(dz) is always 1; if this is really > always true, then tilting could be piggy-backed onto dz as +2/-2 value > (or some such) and then Xorg sysmouse driver could be taught to > interpret such values as special button presses (similarly to how > vertical scrolling is handled in it). Well, perhaps the best way is to teach sysmouse about horizontal scrolling and then add a quirk WRT your mouse ? sysmouse(4) really needs to grow horizontal scrolling since nowadays every mouse has it. Regards, -- Rui Paulo From neldredge at math.ucsd.edu Wed Aug 13 16:47:43 2008 From: neldredge at math.ucsd.edu (Nate Eldredge) Date: Wed Aug 13 16:47:49 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813141059.GH1803@deviant.kiev.zoral.com.ua> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> <20080813141059.GH1803@deviant.kiev.zoral.com.ua> Message-ID: On Wed, 13 Aug 2008, Kostik Belousov wrote: > Then, the issue of mixing our reboot(2)/linux fcntl(2) is irrelevant. > The original reporter said that system "just rebooted", and I believe > that filesystems where not synced and not unmounted properly. Our > reboot(2) does not have flag combination that could cause such > behaviour, I think. You are right, file systems were not unmounted, and I doubt that they were synced either. They had to be fscked when the system came back up. > Also, I doubt that the program being run is statically linked or > run by root. Confirmation ? I did not run it as root. Sorry, I should have said that before. It is a little hard to trace their maze of shell scripts to figure out which binary was being run, but if I am looking at the right one, it is dynamically linked and branded SVR4. I will make sure later today. > Overall, this looks like a nasty bug, hopefully in the linuxolator. Indeed. -- Nate Eldredge neldredge@math.ucsd.edu From tevans.uk at googlemail.com Wed Aug 13 16:58:44 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Wed Aug 13 16:58:51 2008 Subject: If not the force, what should I use? In-Reply-To: <20080813080032.2328a474@bhuda.mired.org> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> <20080813080032.2328a474@bhuda.mired.org> Message-ID: <1218646719.70002.27.camel@localhost> On Wed, 2008-08-13 at 08:00 -0400, Mike Meyer wrote: > > stop If the service is to be started as specified by > rc.conf(5), stop the service. This should check that the > service is running and complain if it is not. If > forcestop is given, ignore the rc.conf(5) check and > attempt to stop. > > I don't have time to do it now, but will later if no one says they have.... > > References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> <20080813080032.2328a474@bhuda.mired.org> <1218646719.70002.27.camel@localhost> Message-ID: <20080813130612.67542bd5@mbook.local> On Wed, 13 Aug 2008 17:58:39 +0100 Tom Evans wrote: > On Wed, 2008-08-13 at 08:00 -0400, Mike Meyer wrote: > > > > stop If the service is to be started as specified by > > rc.conf(5), stop the service. This should check that the > > service is running and complain if it is not. If > > forcestop is given, ignore the rc.conf(5) check and > > attempt to stop. > > > Why should it complain? Because somebody quoted it out of context to justify a completely bogus assumption about what was and wasn't a bug. The bug in question is that the man page should note that force(start|stop|restart) should ignore any precmd problems as well as the setting in rc.conf, as that is what the tools provided by rc.subr do. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From Alexander at Leidinger.net Wed Aug 13 18:38:21 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Wed Aug 13 18:44:59 2008 Subject: Debugging reboot with Linux emulation In-Reply-To: <20080813154501.GI1803@deviant.kiev.zoral.com.ua> References: <20080813132822.18394zk66kfg0xcs@webmail.leidinger.net> <20080813115413.GF1803@deviant.kiev.zoral.com.ua> <20080813160353.55171pui9o2wvm4g@webmail.leidinger.net> <20080813141059.GH1803@deviant.kiev.zoral.com.ua> <20080813172805.26324k9zft01f62o@webmail.leidinger.net> <20080813154501.GI1803@deviant.kiev.zoral.com.ua> Message-ID: <20080813203808.16712jd03vj8pkw0@webmail.leidinger.net> Quoting "Kostik Belousov" (from Wed, 13 Aug 2008 18:45:01 +0300): > On Wed, Aug 13, 2008 at 05:28:05PM +0200, Alexander Leidinger wrote: >> The linuxulator is not involved, as there's no branding it is not >> invoked. The same will happen if the linxulator is not in the kernel. > > Ok, if the case is confirmed, I very much want to get such binary into > my hands. > > I.e., unbranded statically linked ELF binary running which causes > immediate reboot without normal kernel shutdown sequence. You could try /compat/linux/sbin/ldconfig without a brand. If it uses fcntl, it should trigger the problem. Bye, Alexander. -- Some people have no respect for age unless it's bottled. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From hraghav.devel at gmail.com Wed Aug 13 21:04:11 2008 From: hraghav.devel at gmail.com (H Raghav) Date: Wed Aug 13 21:04:18 2008 Subject: VMWare 3 port on FreeBSD 7 STABLE Message-ID: <7c299c6c0808131337t67e1b956q66a95427dfbf53de@mail.gmail.com> Hi: I am trying to run VMware 3 port from /usr/ports/emulators/vmware3 on FreeBSD 7.0 STABLE. I did a make install from the /usr/ports as root and the build and install went fine. It installed Linux Base FC4 and then installed VMWare 3. However, whenever I try to startup vmware, I get an error that /dev/vmmon cannot be found. The error is: Could not open /dev/vmmon: No such file or directory. Please make sure that the kernel module `vmmon' is loaded. Failed to initialize monitor device. Linprocfs is mounted on /compat/linux/proc. I also ran the /usr/local/rc.d/vmware.sh start and it reported that all modules are already loaded. kldstat reveals that vmmon_smp.ko is indeed loaded. Based on some research, I found this issue reported in FreeBSD 5.4; I believe the same is at work here. I am running on a DELL SMP hardware (DELL Precision 530 Workstation). http://lists.freebsd.org/pipermail/freebsd-bugs/2005-May/012725.html Any way to fix this issue in FreeBSD 7? Is it due to the SMP hardware? Can I make VMWare belive that it is running on Uniprocessor hardware? From anderson_underground at hotmail.com Wed Aug 13 23:24:19 2008 From: anderson_underground at hotmail.com (ANDERSON EDUARDO) Date: Wed Aug 13 23:24:25 2008 Subject: Ptrace in FreeBSD In-Reply-To: <20080813120012.DC6A410656F0@hub.freebsd.org> References: <20080813120012.DC6A410656F0@hub.freebsd.org> Message-ID: someone could help me use the PT_SETREGS on FreeBSD? I get the value of registers with PT_GETREGS normal, but when I make the modification and the use PT_SETREGS not working! could show me an example? _________________________________________________________________ Instale a Barra de Ferramentas com Desktop Search e ganhe EMOTICONS para o Messenger! ? GR?TIS! http://www.msn.com.br/emoticonpack From arsenault.dave at gmail.com Thu Aug 14 00:49:25 2008 From: arsenault.dave at gmail.com (Dave Arsenault) Date: Thu Aug 14 00:59:21 2008 Subject: Ptrace in FreeBSD In-Reply-To: References: <20080813120012.DC6A410656F0@hub.freebsd.org> Message-ID: <48A37B5D.6070900@gmail.com> ANDERSON EDUARDO wrote: > someone could help me use the PT_SETREGS on FreeBSD? > > I get the value of registers with PT_GETREGS normal, but when I make the modification and the use PT_SETREGS not working! > > could show me an example? > _________________________________________________________________ > Instale a Barra de Ferramentas com Desktop Search e ganhe EMOTICONS para o Messenger! ? GR?TIS! > http://www.msn.com.br/emoticonpack_______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > Would be more appropriate if you showed us the snippet of code that's causing trouble. From cynical.nihilist at gmail.com Thu Aug 14 01:20:34 2008 From: cynical.nihilist at gmail.com (Cynical Nihilist) Date: Thu Aug 14 01:20:41 2008 Subject: Ptrace in FreeBSD In-Reply-To: References: <20080813120012.DC6A410656F0@hub.freebsd.org> Message-ID: <48A38213.4010409@gmail.com> ANDERSON EDUARDO wrote: > someone could help me use the PT_SETREGS on FreeBSD? > > I get the value of registers with PT_GETREGS normal, but when I make the modification and the use PT_SETREGS not working! > > could show me an example? > _________________________________________________________________ > Instale a Barra de Ferramentas com Desktop Search e ganhe EMOTICONS para o Messenger! ? GR?TIS! > http://www.msn.com.br/emoticonpack_______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > Would be more appropriate if you showed us the snippet of code that's causing trouble. From fjwcash at gmail.com Thu Aug 14 01:22:34 2008 From: fjwcash at gmail.com (Freddie Cash) Date: Thu Aug 14 01:22:41 2008 Subject: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD)) In-Reply-To: <48A29E15.5080303@unsane.co.uk> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <20080812115132.44b2e8f7@mbook.local> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> Message-ID: On Wed, Aug 13, 2008 at 1:40 AM, Vincent Hoffman wrote: > Jonathan McKeown wrote: >> On Tuesday 12 August 2008 17:51:32 Mike Meyer wrote: >>> On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" >>> Ok, given that you 1) want to have both "XXXX this service if it's >>> part of our normal runtime" and "XXXX this service even if it's not >>> part of our normal runtime" as script commands, and that 2) XXXX >>> without a prefix gets the "if it's part of our normal runtime" >>> meaning, as we want the user to have to explicitly say "Yes, I know >>> this looks odd, but I know what I'm doing so do it anyway" to get the >>> "even if it's not part of our normal runtime" behavior, then what >>> would you have us use instead of "forceXXXX"? >>> >> People keep talking about forcestart. >> >> Unless I'm misunderstanding things horribly, forcestart does exactly that >> - forces the service to start regardless of any error that may occur. >> >> The better option for starting something as a one-off (not enabled in >> rc.conf) is mnemonically named onestart - which only ignores the rcvar but >> still fails on any other error. >> >> And yes, I like having onestart/onestop distinguished from start/stop. >> > I believe it "forces" a start even though its not actually enabled (in > rc.conf) rather than regardless of errors. > If you really want a command line of onestart/onestop install the > sysutils/bsdadminscripts port which has a script called rconestart and > rconestop which do exactly that ;) >From /etc/rc.subr: # run_rc_command argument # Search for argument in the list of supported commands, which is: # "start stop restart rcvar status poll ${extra_commands}" # If there's a match, run ${argument}_cmd or the default method # (see below). # # If argument has a given prefix, then change the operation as follows: # Prefix Operation # ------ --------- # fast Skip the pid check, and set rc_fast=yes # force Set ${rcvar} to YES, and set rc_force=yes # one Set ${rcvar} to YES Further in the file: case "$rc_arg" in fast*) # "fast" prefix; don't check pid rc_arg=${rc_arg#fast} rc_fast=yes ;; force*) # "force prefix; always run rc_force=yes _rc_prefix=force rc_arg=${rc_arg#${_rc_prefix}} if [ -n "${rcvar}" ]; then eval ${rcvar}=YES fi ;; one*) # "one" prefix; set ${rcvar}=yes _rc_prefix=one rc_arg=${rc_arg#${_rc_prefix}} if [ -n "${rcvar}" ]; then eval ${rcvar}=YES fi ;; esac Which, if I follow things, means: ** "/etc/rc.d/$script faststart" won't check for existing PID files or already running apps, and just run $script, but still checks if $script_enable=yes is in /etc/rc.conf. ** "/etc/rc.d/$script onestart" sets $script_enable=yes internally, regardless of what is in rc.conf, and runs $script. All other checks are done as per normal. ** "/etc/rc.d/$script forcestart" runs $script, regardless of what's in rc.conf, the status of the PID file, or the existence of an already running daemon. What most people in this thread are looking for is onestart. -- Freddie Cash fjwcash@gmail.com From samflanker at gmail.com Thu Aug 14 06:27:12 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 06:27:19 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA Message-ID: <48A3D034.9090809@gmail.com> elloallo@infinito.it wrote: > > > I bought an ASUS motherboard with onboard SATA II controller. I > attached 2 HDs SATA II but when I run dmesg I notice that my system > sees them as normal older SATA 150 instead of SATA 300. > > Is there any suggestion to solve this problem ? > > Have a nice day. > > ------------------dmesg output----------------------- > > Copyright (c) 1992-2006 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 6.1-RELEASE-p1 #0: Fri Jun 2 15:41:03 CEST 2006 > r...@AMOS-gw1.allo.it:/usr/obj/usr/src/sys/AMOS-SMP > WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant > WARNING: MPSAFE network stack disabled, expect reduced performance. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) D CPU 3.00GHz (3000.38-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf62 Stepping = 2 > > Features=0xbfebfbff > Features2=0xe43d,> > AMD Features=0x20000000 > AMD Features2=0x1 > Cores per package: 2 > real memory = 2138701824 (2039 MB) > avail memory = 2087825408 (1991 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > cpu1: on acpi0 > atapci0: port > 0xc800-0xc807,0xc400-0xc403,0xc000-0xc007,0xb800-0xb803,0xb400-0xb40f > irq 19 at device 4.0 on pci1 > ata2: on atapci0 > ata3: on atapci0 > atapci1: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on > pci0 > ata0: on atapci1 > ata1: on atapci1 > atapci2: port > 0xa800-0xa807,0xa400-0xa403,0xa000-0xa007,0x9800-0x9803,0x9400-0x940f > irq 17 at device 31.2 on pci0 > atapci2: failed to enable memory mapping! > ata4: on atapci2 > ata5: on atapci2 > acd0: DVDROM at ata0-master UDMA33 > ad8: 114473MB at ata4-master SATA150 > GEOM_MIRROR: Device gm0 created (id=2415013281). > GEOM_MIRROR: Device gm0: provider ad8 detected. > ad10: 114473MB at ata5-master SATA150 > GEOM_MIRROR: Device gm0: provider ad10 detected. > SMP: AP CPU #1 Launched! > GEOM_MIRROR: Device gm0: provider ad10 activated. > GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. > GEOM_MIRROR: Device gm0: rebuilding provider ad8. > Trying to mount root from ufs:/dev/mirror/gm0s1a > em0: link state changed to UP > hello my similar problem motherboard with the Intel G31 Express Chipset -------------------------------------------------------------------- |# output 'dmesg' (|partially|) atapci1: port 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ad7: 476940MB at ata3-slave SATA150 # atacontrol cap ad7 Protocol Serial ATA II device model WDC WD5000AAKS-00YGA0 serial number WD-WCAS87395070 firmware revision 12.01C02 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 976773168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes no 254/0xFE 128/0x80 # atacontrol mode ad7 current mode = SATA150 # output 'pciconf -lv' (|partially|) atapci1@pci0:0:31:2: class=0x01018f card=0x26391019 chip=0x27c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller' class = mass storage subclass = ATA # uname -a FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 |-------------------------------------------------------------------- please, any solution ? /Vladimir Ermakov From bu7cher at yandex.ru Thu Aug 14 06:56:11 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Thu Aug 14 06:56:19 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3D034.9090809@gmail.com> References: <48A3D034.9090809@gmail.com> Message-ID: <48A3D43E.2070101@yandex.ru> sam wrote: > FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD 2008 > root@:/usr/obj/usr/src/sys/GENERIC i386 > |-------------------------------------------------------------------- > > please, any solution ? Probably speed is limited via jumpers on your hard drive. -- WBR, Andrey V. Elsukov From samflanker at gmail.com Thu Aug 14 06:58:06 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 06:58:13 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3D43E.2070101@yandex.ru> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> Message-ID: <48A3D771.5010601@gmail.com> Andrey V. Elsukov wrote: > sam wrote: >> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD >> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >> |-------------------------------------------------------------------- >> >> please, any solution ? > > Probably speed is limited via jumpers on your hard drive. > http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper tried it without results /Vladimir Ermakov From kris at FreeBSD.org Thu Aug 14 07:10:16 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Thu Aug 14 07:10:24 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3D771.5010601@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> Message-ID: <48A3DA54.9070803@FreeBSD.org> sam wrote: > Andrey V. Elsukov wrote: >> sam wrote: >>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD >>> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>> |-------------------------------------------------------------------- >>> >>> please, any solution ? >> >> Probably speed is limited via jumpers on your hard drive. >> > http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper > > tried it > > without results So the jumpers were set wrong to begin with, but fixing them didnt help? Check your BIOS SATA support or look for an upgrade. Kris From koitsu at FreeBSD.org Thu Aug 14 07:16:16 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 14 07:16:24 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3D771.5010601@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> Message-ID: <20080814071616.GA758@eos.sc1.parodius.com> On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: > Andrey V. Elsukov wrote: >> sam wrote: >>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD >>> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>> |-------------------------------------------------------------------- >>> >>> please, any solution ? >> >> Probably speed is limited via jumpers on your hard drive. >> > http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper > tried it > > without results FWIW, the only time I've seen this happen is when there's a jumper limiting the capability. You should have **removed** the OPT1 jumper, and left any other jumpers alone. If you're absolutely sure the jumper is removed, I'll purchase one of these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your findings. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From samflanker at gmail.com Thu Aug 14 07:19:40 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 07:19:48 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3DA54.9070803@FreeBSD.org> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> Message-ID: <48A3DC83.1080806@gmail.com> Kris Kennaway wrote: > sam wrote: >> Andrey V. Elsukov wrote: >>> sam wrote: >>>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD >>>> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>>> |-------------------------------------------------------------------- >>>> >>>> please, any solution ? >>> >>> Probably speed is limited via jumpers on your hard drive. >>> >> http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper >> >> tried it >> >> without results > > So the jumpers were set wrong to begin with, but fixing them didnt help? i`am tried all positions from specification > Check your BIOS SATA support or look for an upgrade. BIOS is support SATA have 2 modes (Compatible, Enchanced) i`am tried both modes without results BIOS firmware is upgraded to last /Vladimir Ermakov From koitsu at FreeBSD.org Thu Aug 14 07:27:13 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 14 07:27:20 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <20080814071616.GA758@eos.sc1.parodius.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <20080814071616.GA758@eos.sc1.parodius.com> Message-ID: <20080814072713.GA1939@eos.sc1.parodius.com> On Thu, Aug 14, 2008 at 12:16:16AM -0700, Jeremy Chadwick wrote: > On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: > > Andrey V. Elsukov wrote: > >> sam wrote: > >>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD > >>> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 > >>> |-------------------------------------------------------------------- > >>> > >>> please, any solution ? > >> > >> Probably speed is limited via jumpers on your hard drive. > >> > > http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper > > tried it > > > > without results > > FWIW, the only time I've seen this happen is when there's a jumper > limiting the capability. You should have **removed** the OPT1 jumper, > and left any other jumpers alone. > > If you're absolutely sure the jumper is removed, I'll purchase one of > these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your > findings. Actually, I don't need to -- I'm using WD5000AAKS disks myself on that exact system: atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ata4: on atapci1 ata4: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ad6: 476940MB at ata3-master SATA300 ad8: 476940MB at ata4-master SATA300 icarus# atacontrol cap ad6 Protocol Serial ATA II device model WDC WD5000AAKS-00YGA0 serial number WD-WCAS83974519 firmware revision 12.01C02 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 976773168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes no 254/0xFE 128/0x80 icarus# atacontrol cap ad8 Protocol Serial ATA II device model WDC WD5000AAKS-00TMA0 serial number WD-WCAPW2137942 firmware revision 12.01C01 cylinders 16383 heads 16 sectors/track 63 lba supported 268435455 sectors lba48 supported 976773168 sectors dma supported overlap not supported Feature Support Enable Value Vendor write cache yes yes read ahead yes yes Native Command Queuing (NCQ) yes - 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management no no 0/0x00 automatic acoustic management yes no 254/0xFE 128/0x80 icarus# atacontrol mode ad6 current mode = SATA300 icarus# atacontrol mode ad8 current mode = SATA300 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From samflanker at gmail.com Thu Aug 14 07:34:22 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 07:34:28 2008 Subject: consolekit on 7.0-STABLE i386 In-Reply-To: <20080807103020.GS97161@deviant.kiev.zoral.com.ua> References: <489036A2.5060403@gmail.com> <48931AD1.1090609@gmail.com> <20080801143128.GJ97161@deviant.kiev.zoral.com.ua> <489AABA5.9070602@gmail.com> <20080807103020.GS97161@deviant.kiev.zoral.com.ua> Message-ID: <48A3DFF2.4050302@gmail.com> Kostik Belousov wrote: > On Thu, Aug 07, 2008 at 12:00:37PM +0400, sam wrote: > >> Kostik Belousov wrote: >> >>> On Fri, Aug 01, 2008 at 06:16:49PM +0400, sam wrote: >>> >>> >>>> Nate Eldredge wrote: >>>> >>>> >>>>> On Wed, 30 Jul 2008, sam wrote: >>>>> >>>>> >>>>> >>>>>> 0 19 0 1113M 29M 112 0 0 0 32 0 0 1 100 5549 >>>>>> 1682 11 1 88 >>>>>> 0 19 0 1113M 29M 297 0 0 0 136 0 0 2 122 78880 >>>>>> 1749 6 7 87 >>>>>> |-------------------------------------------------------------------- >>>>>> >>>>>> consolekit in |waitvt state, influencing on high volumes in procs-b >>>>>> >>>>>> >>>>> I don't understand what the problem is. It looks like consolekit is >>>>> sleeping and not using any CPU. "waitvt" just indicates where in the >>>>> kernel it's sleeping. I don't understand what you mean by "high >>>>> volumes in procs-b". >>>>> >>>>> >>>>> >>>> How-To-Repeat: >>>> -------------------------------------------------------------- >>>> # (|cd /usr/ports/sysutils/consolekit/ && make install clean) >>>> >>>> # /usr/local/etc/rc.d/dbus forcestart >>>> >>>> # vmstat -w 1 >>>> procs memory page disk faults cpu >>>> r b w avm fre flt re pi po fr sr ad0 in sy cs us >>>> sy id >>>> 2 1 0 62252K 644M 88 0 0 0 80 0 0 2 83 279 1 >>>> 1 98 >>>> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 134 292 0 >>>> 3 97 >>>> 0 1 0 62252K 644M 0 0 0 0 0 0 0 4 123 299 0 >>>> 2 98 >>>> 1 1 0 62252K 644M 0 0 0 0 0 0 0 3 120 305 0 >>>> 3 97 >>>> ^C >>>> # /usr/local/sbin/console-kit-daemon && vmstat -w 1 >>>> procs memory page disk faults cpu >>>> r b w avm fre flt re pi po fr sr ad0 in sy cs us >>>> sy id >>>> 2 1 0 67572K 643M 88 0 0 0 80 0 0 2 83 279 1 >>>> 1 98 >>>> 0 16 0 68660K 643M 103 0 0 0 2 0 10 13 643 381 >>>> 2 4 94 >>>> 0 16 0 68660K 643M 0 0 0 0 0 0 0 3 120 281 >>>> 0 4 96 >>>> 0 16 0 68660K 643M 0 0 0 0 0 0 0 2 120 278 >>>> 0 3 97 >>>> 0 16 0 68660K 643M 0 0 0 0 12 0 28 34 120 385 >>>> 0 3 97 >>>> 0 16 0 68660K 643M 0 0 0 0 0 0 0 4 120 292 >>>> 0 3 97 >>>> ^C >>>> # >>>> |-------------------------------------------------------------- >>>> >>>> please, any solution ... >>>> >>>> >>> Solution for what ? There is nothing wrong with the system. >>> >>> For the purely estetisk purpose, you may look up the line >>> tsleep(VTY_WCHAN(sc, i), PZERO | PCATCH, "waitvt", 0); >>> or similar in sys/dev/syscons/syscons.c, and remove the "PZERO |" substring >>> >> >from it. >> >>> >>> >> ok >> >> Why proc-b on the HEAD, have low values (with working consolekit)? >> > > On what revision of HEAD ? I committed the change that causes the thread > to sleep on the PZERO+1 priority instead of PZERO as r181286. > thx it works ------------------------------------------------------------------------ # output 'top' (part) 958 root 1 4 0 3096K 872K - 0 0:00 0.00% nfsd 960 root 1 4 0 3096K 872K - 1 0:00 0.00% nfsd 959 root 1 4 0 3096K 872K - 1 0:00 0.00% nfsd 96619 root 17 1 0 7984K 3324K waitvt 1 0:00 0.00% console-kit-daemon # /usr/local/sbin/console-kit-daemon && vmstat 1 procs memory page disk faults cpu r b w avm fre flt re pi po fr sr ad4 in sy cs us sy id 2 1 1 129M 1552M 293 0 0 0 269 0 0 40 267 826 0 0 99 0 1 0 132M 1551M 58 0 0 0 2 0 0 29 541 591 0 1 99 0 1 0 132M 1551M 0 0 0 0 0 0 0 29 155 492 0 0 100 # uname -a FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 ------------------------------------------------------------------------ /Vladimir Ermakov From bu7cher at yandex.ru Thu Aug 14 07:38:28 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Thu Aug 14 07:38:35 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3DC83.1080806@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> Message-ID: <48A3E0E4.3090909@yandex.ru> sam wrote: >> So the jumpers were set wrong to begin with, but fixing them didnt help? > i`am tried all positions from specification >> Check your BIOS SATA support or look for an upgrade. > BIOS is support SATA > have 2 modes (Compatible, Enchanced) > i`am tried both modes > > without results Can you show `ident /boot/kernel/kernel | grep ata-chipset` output? -- WBR, Andrey V. Elsukov From samflanker at gmail.com Thu Aug 14 07:44:58 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 07:45:05 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3E0E4.3090909@yandex.ru> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> Message-ID: <48A3E25E.6050105@gmail.com> Andrey V. Elsukov wrote: > sam wrote: >>> So the jumpers were set wrong to begin with, but fixing them didnt >>> help? >> i`am tried all positions from specification >>> Check your BIOS SATA support or look for an upgrade. >> BIOS is support SATA >> have 2 modes (Compatible, Enchanced) >> i`am tried both modes >> >> without results > > Can you show `ident /boot/kernel/kernel | grep ata-chipset` output? > -------------------------------------------------------- # ident /boot/kernel/kernel | grep ata-chipset $FreeBSD: src/sys/dev/ata/ata-chipset.c,v 1.202.2.11 2008/08/02 12:34:49 remko Exp $ -------------------------------------------------------- /Vladimir Ermakov From samflanker at gmail.com Thu Aug 14 08:02:35 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 08:02:42 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <20080814072713.GA1939@eos.sc1.parodius.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <20080814071616.GA758@eos.sc1.parodius.com> <20080814072713.GA1939@eos.sc1.parodius.com> Message-ID: <48A3E6AA.9000205@gmail.com> Jeremy Chadwick wrote: > On Thu, Aug 14, 2008 at 12:16:16AM -0700, Jeremy Chadwick wrote: > >> On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: >> >>> Andrey V. Elsukov wrote: >>> >>>> sam wrote: >>>> >>>>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 MSD >>>>> 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>>>> |-------------------------------------------------------------------- >>>>> >>>>> please, any solution ? >>>>> >>>> Probably speed is limited via jumpers on your hard drive. >>>> >>>> >>> http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper >>> tried it >>> >>> without results >>> >> FWIW, the only time I've seen this happen is when there's a jumper >> limiting the capability. You should have **removed** the OPT1 jumper, >> and left any other jumpers alone. >> >> If you're absolutely sure the jumper is removed, I'll purchase one of >> these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your >> findings. >> > > Actually, I don't need to -- I'm using WD5000AAKS disks myself on > that exact system: > > atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ata4: on atapci1 > ata4: [ITHREAD] > ata5: on atapci1 > ata5: [ITHREAD] > > ad6: 476940MB at ata3-master SATA300 > ad8: 476940MB at ata4-master SATA300 > may issue in driver ? ---------------------------------------------------- atapci1: port 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f irq 19 at device 31.2 on pci0 ---------------------------------------------------- /Vladimir Ermakov From koitsu at FreeBSD.org Thu Aug 14 08:11:03 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 14 08:11:29 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3E6AA.9000205@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <20080814071616.GA758@eos.sc1.parodius.com> <20080814072713.GA1939@eos.sc1.parodius.com> <48A3E6AA.9000205@gmail.com> Message-ID: <20080814081102.GA7612@eos.sc1.parodius.com> On Thu, Aug 14, 2008 at 12:02:50PM +0400, sam wrote: > Jeremy Chadwick wrote: >> On Thu, Aug 14, 2008 at 12:16:16AM -0700, Jeremy Chadwick wrote: >> >>> On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: >>> >>>> Andrey V. Elsukov wrote: >>>> >>>>> sam wrote: >>>>> >>>>>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 >>>>>> MSD 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>>>>> |-------------------------------------------------------------------- >>>>>> >>>>>> please, any solution ? >>>>>> >>>>> Probably speed is limited via jumpers on your hard drive. >>>>> >>>>> >>>> http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper >>>> tried it >>>> >>>> without results >>>> >>> FWIW, the only time I've seen this happen is when there's a jumper >>> limiting the capability. You should have **removed** the OPT1 jumper, >>> and left any other jumpers alone. >>> >>> If you're absolutely sure the jumper is removed, I'll purchase one of >>> these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your >>> findings. >>> >> >> Actually, I don't need to -- I'm using WD5000AAKS disks myself on >> that exact system: >> >> atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 >> atapci1: [ITHREAD] >> atapci1: AHCI Version 01.10 controller with 4 ports detected >> ata2: on atapci1 >> ata2: [ITHREAD] >> ata3: on atapci1 >> ata3: [ITHREAD] >> ata4: on atapci1 >> ata4: [ITHREAD] >> ata5: on atapci1 >> ata5: [ITHREAD] >> >> ad6: 476940MB at ata3-master SATA300 >> ad8: 476940MB at ata4-master SATA300 >> > may issue in driver ? > > ---------------------------------------------------- > atapci1: port > 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f > irq 19 at device 31.2 on pci0 > ---------------------------------------------------- Possibly. All my Intel ICH7 boards have AHCI capability, and I use it. See Chapter 4 here: http://www.supermicro.com/manuals/motherboard/3000/MNL-0889.pdf If your motherboard does, I'd recommend enabling it as well and see if things change. Regarding the "Enhanced" vs. "Compatible" mode: use Enhanced. On my boards, choosing Enhanced makes the AHCI and Intel MatrixRAID options appear. I'm fairly certain you don't need AHCI to get SATA300, though. I would recommend you re-check the jumpers on your disks to make sure you didn't make a mistake when adjusting things. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From tevans.uk at googlemail.com Thu Aug 14 08:19:11 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Thu Aug 14 08:19:18 2008 Subject: If not the force, what should I use? In-Reply-To: <20080813130612.67542bd5@mbook.local> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> <20080813080032.2328a474@bhuda.mired.org> <1218646719.70002.27.camel@localhost> <20080813130612.67542bd5@mbook.local> Message-ID: <1218701945.70002.31.camel@localhost> On Wed, 2008-08-13 at 13:06 -0400, Mike Meyer wrote: > On Wed, 13 Aug 2008 17:58:39 +0100 Tom Evans wrote: > > > On Wed, 2008-08-13 at 08:00 -0400, Mike Meyer wrote: > > > > > > stop If the service is to be started as specified by > > > rc.conf(5), stop the service. This should check that the > > > service is running and complain if it is not. If > > > forcestop is given, ignore the rc.conf(5) check and > > > attempt to stop. > > > > > Why should it complain? > > Because somebody quoted it out of context to justify a completely > bogus assumption about what was and wasn't a bug. > > The bug in question is that the man page should note that > force(start|stop|restart) should ignore any precmd problems as well as > the setting in rc.conf, as that is what the tools provided by rc.subr > do. > > References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <20080814071616.GA758@eos.sc1.parodius.com> <20080814072713.GA1939@eos.sc1.parodius.com> <48A3E6AA.9000205@gmail.com> <20080814081102.GA7612@eos.sc1.parodius.com> Message-ID: <48A3F478.8040901@gmail.com> Jeremy Chadwick wrote: > On Thu, Aug 14, 2008 at 12:02:50PM +0400, sam wrote: > >> Jeremy Chadwick wrote: >> >>> On Thu, Aug 14, 2008 at 12:16:16AM -0700, Jeremy Chadwick wrote: >>> >>> >>>> On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: >>>> >>>> >>>>> Andrey V. Elsukov wrote: >>>>> >>>>> >>>>>> sam wrote: >>>>>> >>>>>> >>>>>>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 13:54:27 >>>>>>> MSD 2008 root@:/usr/obj/usr/src/sys/GENERIC i386 >>>>>>> |-------------------------------------------------------------------- >>>>>>> >>>>>>> please, any solution ? >>>>>>> >>>>>>> >>>>>> Probably speed is limited via jumpers on your hard drive. >>>>>> >>>>>> >>>>>> >>>>> http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper >>>>> tried it >>>>> >>>>> without results >>>>> >>>>> >>>> FWIW, the only time I've seen this happen is when there's a jumper >>>> limiting the capability. You should have **removed** the OPT1 jumper, >>>> and left any other jumpers alone. >>>> >>>> If you're absolutely sure the jumper is removed, I'll purchase one of >>>> these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your >>>> findings. >>>> >>>> >>> Actually, I don't need to -- I'm using WD5000AAKS disks myself on >>> that exact system: >>> >>> atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 >>> atapci1: [ITHREAD] >>> atapci1: AHCI Version 01.10 controller with 4 ports detected >>> ata2: on atapci1 >>> ata2: [ITHREAD] >>> ata3: on atapci1 >>> ata3: [ITHREAD] >>> ata4: on atapci1 >>> ata4: [ITHREAD] >>> ata5: on atapci1 >>> ata5: [ITHREAD] >>> >>> ad6: 476940MB at ata3-master SATA300 >>> ad8: 476940MB at ata4-master SATA300 >>> >>> >> may issue in driver ? >> >> ---------------------------------------------------- >> atapci1: port >> 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f >> irq 19 at device 31.2 on pci0 >> ---------------------------------------------------- >> > > Possibly. All my Intel ICH7 boards have AHCI capability, and I use it. > See Chapter 4 here: > > http://www.supermicro.com/manuals/motherboard/3000/MNL-0889.pdf > > If your motherboard does, I'd recommend enabling it as well and see if > things change. > > Regarding the "Enhanced" vs. "Compatible" mode: use Enhanced. On > my boards, choosing Enhanced makes the AHCI and Intel MatrixRAID > options appear. > > I'm fairly certain you don't need AHCI to get SATA300, though. > > I would recommend you re-check the jumpers on your disks to make sure > you didn't make a mistake when adjusting things. > > - HDD on position: all jumpers removed; - SATA controller in Enchanced mode; - no option AHCI in BIOS without results /Vladimir Ermakov From koitsu at FreeBSD.org Thu Aug 14 09:08:06 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 14 09:08:21 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3F478.8040901@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <20080814071616.GA758@eos.sc1.parodius.com> <20080814072713.GA1939@eos.sc1.parodius.com> <48A3E6AA.9000205@gmail.com> <20080814081102.GA7612@eos.sc1.parodius.com> <48A3F478.8040901@gmail.com> Message-ID: <20080814090806.GA14589@eos.sc1.parodius.com> On Thu, Aug 14, 2008 at 01:01:44PM +0400, sam wrote: > Jeremy Chadwick wrote: >> On Thu, Aug 14, 2008 at 12:02:50PM +0400, sam wrote: >> >>> Jeremy Chadwick wrote: >>> >>>> On Thu, Aug 14, 2008 at 12:16:16AM -0700, Jeremy Chadwick wrote: >>>> >>>>> On Thu, Aug 14, 2008 at 10:57:53AM +0400, sam wrote: >>>>> >>>>>> Andrey V. Elsukov wrote: >>>>>> >>>>>>> sam wrote: >>>>>>> >>>>>>>> FreeBSD 7.0-STABLE FreeBSD 7.0-STABLE #5: Tue Aug 12 >>>>>>>> 13:54:27 MSD 2008 root@:/usr/obj/usr/src/sys/GENERIC >>>>>>>> i386 >>>>>>>> |-------------------------------------------------------------------- >>>>>>>> >>>>>>>> please, any solution ? >>>>>>>> >>>>>>> Probably speed is limited via jumpers on your hard drive. >>>>>>> >>>>>>> >>>>>> http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1409&p_created=#jumper >>>>>> tried it >>>>>> >>>>>> without results >>>>>> >>>>> FWIW, the only time I've seen this happen is when there's a jumper >>>>> limiting the capability. You should have **removed** the OPT1 jumper, >>>>> and left any other jumpers alone. >>>>> >>>>> If you're absolutely sure the jumper is removed, I'll purchase one of >>>>> these drives and test it on an ICH7 (Supermicro PDSMi+) to confirm your >>>>> findings. >>>>> >>>> Actually, I don't need to -- I'm using WD5000AAKS disks myself on >>>> that exact system: >>>> >>>> atapci1: port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xe8600400-0xe86007ff irq 19 at device 31.2 on pci0 >>>> atapci1: [ITHREAD] >>>> atapci1: AHCI Version 01.10 controller with 4 ports detected >>>> ata2: on atapci1 >>>> ata2: [ITHREAD] >>>> ata3: on atapci1 >>>> ata3: [ITHREAD] >>>> ata4: on atapci1 >>>> ata4: [ITHREAD] >>>> ata5: on atapci1 >>>> ata5: [ITHREAD] >>>> >>>> ad6: 476940MB at ata3-master SATA300 >>>> ad8: 476940MB at ata4-master SATA300 >>>> >>> may issue in driver ? >>> >>> ---------------------------------------------------- >>> atapci1: port >>> 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f >>> irq 19 at device 31.2 on pci0 >>> ---------------------------------------------------- >>> >> >> Possibly. All my Intel ICH7 boards have AHCI capability, and I use it. >> See Chapter 4 here: >> >> http://www.supermicro.com/manuals/motherboard/3000/MNL-0889.pdf >> >> If your motherboard does, I'd recommend enabling it as well and see if >> things change. >> >> Regarding the "Enhanced" vs. "Compatible" mode: use Enhanced. On >> my boards, choosing Enhanced makes the AHCI and Intel MatrixRAID >> options appear. >> >> I'm fairly certain you don't need AHCI to get SATA300, though. >> >> I would recommend you re-check the jumpers on your disks to make sure >> you didn't make a mistake when adjusting things. >> >> > - HDD on position: all jumpers removed; > - SATA controller in Enchanced mode; > - no option AHCI in BIOS > > without results I'm out of ideas. Others will have to continue helping... -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From bu7cher at yandex.ru Thu Aug 14 09:33:48 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Thu Aug 14 09:33:58 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3E25E.6050105@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> <48A3E25E.6050105@gmail.com> Message-ID: <48A3FBEE.5060302@yandex.ru> sam wrote: > -------------------------------------------------------- > # ident /boot/kernel/kernel | grep ata-chipset > $FreeBSD: src/sys/dev/ata/ata-chipset.c,v 1.202.2.11 2008/08/02 > 12:34:49 remko Exp $ > -------------------------------------------------------- Can you apply attached patch, rebuild your kernel, reboot in verbose mode and show /var/run/dmesg.boot ? -- WBR, Andrey V. Elsukov -------------- next part -------------- --- ata-chipset.c.orig 2008-08-12 08:31:14.000000000 +0400 +++ ata-chipset.c 2008-08-14 13:31:40.000000000 +0400 @@ -2193,6 +2193,11 @@ ctlr->allocate = ata_intel_allocate; ctlr->reset = ata_intel_reset; + if (bootverbose) { + device_printf(dev, "SCRD = 0x%08x, SATACR1 = 0x%08x\n", + pci_read_config(dev, 0x94, 4), + pci_read_config(dev, 0xac, 4)); + } /* * if we have AHCI capability and AHCI or RAID mode enabled * in BIOS we try for AHCI mode From samflanker at gmail.com Thu Aug 14 10:57:19 2008 From: samflanker at gmail.com (sam) Date: Thu Aug 14 10:57:26 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A3FBEE.5060302@yandex.ru> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> <48A3E25E.6050105@gmail.com> <48A3FBEE.5060302@yandex.ru> Message-ID: <48A40F85.3050509@gmail.com> Andrey V. Elsukov wrote: > sam wrote: >> -------------------------------------------------------- >> # ident /boot/kernel/kernel | grep ata-chipset >> $FreeBSD: src/sys/dev/ata/ata-chipset.c,v 1.202.2.11 2008/08/02 >> 12:34:49 remko Exp $ >> -------------------------------------------------------- > > Can you apply attached patch, rebuild your kernel, reboot in verbose > mode and show /var/run/dmesg.boot ? > http://cs.udmvt.ru/files/temp/dmesg.boot_0814 /Vladimir Ermakov From bu7cher at yandex.ru Thu Aug 14 11:56:39 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Thu Aug 14 11:56:47 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A40F85.3050509@gmail.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> <48A3E25E.6050105@gmail.com> <48A3FBEE.5060302@yandex.ru> <48A40F85.3050509@gmail.com> Message-ID: <48A41D70.3000507@yandex.ru> sam wrote: >> Can you apply attached patch, rebuild your kernel, reboot in verbose >> mode and show /var/run/dmesg.boot ? >> > http://cs.udmvt.ru/files/temp/dmesg.boot_0814 It seems that driver couldn't allocate IO resource at BAR5 and without this resource it can't read SATA Status register and determine negotiated speed. I think the problem is in your BIOS. If your BIOS doesn't have any AHCI or RAID specific options I don't know how correctly fix this problem. -- WBR, Andrey V. Elsukov From anderson_underground at hotmail.com Thu Aug 14 12:20:45 2008 From: anderson_underground at hotmail.com (ANDERSON EDUARDO) Date: Thu Aug 14 12:20:53 2008 Subject: Ptrace in FreeBSD In-Reply-To: <20080814073840.280C81065778@hub.freebsd.org> References: <20080814073840.280C81065778@hub.freebsd.org> Message-ID: Sorry friends! Was lack of attention, to use normal :D Thank you! _________________________________________________________________ Receba GR?TIS as mensagens do Messenger no seu celular quando voc? estiver offline. Conhe?a o MSN Mobile! http://mobile.live.com/signup/signup2.aspx?lc=pt-br From koitsu at FreeBSD.org Thu Aug 14 12:47:55 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 14 12:48:03 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <48A41D70.3000507@yandex.ru> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> <48A3E25E.6050105@gmail.com> <48A3FBEE.5060302@yandex.ru> <48A40F85.3050509@gmail.com> <48A41D70.3000507@yandex.ru> Message-ID: <20080814124754.GA20195@eos.sc1.parodius.com> On Thu, Aug 14, 2008 at 03:56:32PM +0400, Andrey V. Elsukov wrote: > sam wrote: >>> Can you apply attached patch, rebuild your kernel, reboot in verbose >>> mode and show /var/run/dmesg.boot ? >>> >> http://cs.udmvt.ru/files/temp/dmesg.boot_0814 > > It seems that driver couldn't allocate IO resource at BAR5 and > without this resource it can't read SATA Status register and > determine negotiated speed. I think the problem is in your BIOS. > If your BIOS doesn't have any AHCI or RAID specific options > I don't know how correctly fix this problem. Andrey, please correct me if I'm wrong here. I'm not familiar these kernel functions, but assuming pci_read_config() handles proper byte order, and device_printf() prints it in correct order, then I believe you may be missing something important. I haven't looked for any product Errata, but see Section 12.1 below (specific to ICH7): http://www.intel.com/assets/pdf/datasheet/307013.pdf Index 0x94 = SIR (SATA Index Register) Index 0xAC = SCAP1 (SATA Capability Register 1) I'm not sure why you called SIR "SCRD" in your device_printf(). For SIR's description, see Section 12.1.35. For SCAP1, see Section 12.1.39. The SIR value is 0x40000180, broken down into binary nibbles: %0100 0000 0000 0000 0000 0001 1000 0000 ^ ^ This indicates bit 30 is set. According to Intel's docs, bit 30 disables SCAP0 and SCAP1, thus will cause them to always return 0: Bit 30 SATA Capability Registers Disable (SCRD) When this bit is set, the SATA Capability Registers are disabled. That is, SATA Capability Registers 0 and 1 are both changed to Read Only with the value of 00000000h. Also, the Next Capability bits in the PCI Power Management Capability Information Register (D31:F2;Offset 70h bits 15:8) are changed to 00h, to indicate that the PCI Power Management Capability structure is the last PCI capability structure in the SATA controller. When this bit is cleared, the SATA Capability Registers are enabled. A quick glance seems to indicate we're not initialising some of the SATA registers at all, case in point. Someone should make a patch for the user that zeros out bit 30 of SIR, then check the xBAR and LBAR values; zeroing bit 30 might get him SATA300 support (I haven't looked at the rest of the FreeBSD ATA code yet). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From bu7cher at yandex.ru Thu Aug 14 14:56:59 2008 From: bu7cher at yandex.ru (Andrey V. Elsukov) Date: Thu Aug 14 14:57:06 2008 Subject: kern/98388: [ata] FreeBSD 6.1 - WDC WD1200JS SATA II disks are seen as older SATA In-Reply-To: <20080814124754.GA20195@eos.sc1.parodius.com> References: <48A3D034.9090809@gmail.com> <48A3D43E.2070101@yandex.ru> <48A3D771.5010601@gmail.com> <48A3DA54.9070803@FreeBSD.org> <48A3DC83.1080806@gmail.com> <48A3E0E4.3090909@yandex.ru> <48A3E25E.6050105@gmail.com> <48A3FBEE.5060302@yandex.ru> <48A40F85.3050509@gmail.com> <48A41D70.3000507@yandex.ru> <20080814124754.GA20195@eos.sc1.parodius.com> Message-ID: <527191218725809@webmail5.yandex.ru> 14.08.08, 16:47, "Jeremy Chadwick" : > On Thu, Aug 14, 2008 at 03:56:32PM +0400, Andrey V. Elsukov wrote: > > sam wrote: > >>> Can you apply attached patch, rebuild your kernel, reboot in verbose > >>> mode and show /var/run/dmesg.boot ? > >>> > >> http://cs.udmvt.ru/files/temp/dmesg.boot_0814 > > > > It seems that driver couldn't allocate IO resource at BAR5 and > > without this resource it can't read SATA Status register and > > determine negotiated speed. I think the problem is in your BIOS. > > If your BIOS doesn't have any AHCI or RAID specific options > > I don't know how correctly fix this problem. > Andrey, please correct me if I'm wrong here. I'm not familiar these > kernel functions, but assuming pci_read_config() handles proper byte > order, and device_printf() prints it in correct order, then I believe > you may be missing something important. My decision is not from output of my changes. Here is in log: found-> vendor=0x8086, dev=0x27c0, revid=0x01 domain=0, bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xc880, size 3, enabled map[14]: type I/O Port, range 32, base 0xc800, size 2, enabled map[18]: type I/O Port, range 32, base 0xc480, size 3, enabled map[1c]: type I/O Port, range 32, base 0xc400, size 2, enabled map[20]: type I/O Port, range 32, base 0xc080, size 4, enabled BAR5 is not present here. Also atapci1: port 0xc880-0xc887,0xc800-0xc803,0xc480-0xc487,0xc400-0xc403,0xc080-0xc08f irq 19 at device 31.2 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xc080 atapci1: [MPSAFE] atapci1: [ITHREAD] atapci1: SCRD = 0x40000180, SATACR1 = 0x00000000 There should be resource allocation: "rid 0x24 type 3" for AHCI or "rid 0x24 type 4" for non-AHCI. But here are nothing of these. ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xc880 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xc800 > Someone should make a patch for the user that zeros out bit 30 of SIR, > then check the xBAR and LBAR values; zeroing bit 30 might get him > SATA300 support (I haven't looked at the rest of the FreeBSD ATA code > yet). I think you can try to do it. But i don't have this hardware and trying to change some bits, making patches, waiting for results, again and again - it's not very interesting for me (i already have similar experience).. In any case ICHx which is working in non-AHCI mode is not the best choice. Many SATA features don't work in this mode and difference between SATA150 and SATA300 is small. -- WBR, Andrey V. Elsukov From mwm at mired.org Thu Aug 14 15:10:03 2008 From: mwm at mired.org (Mike Meyer) Date: Thu Aug 14 15:32:49 2008 Subject: If not the force, what should I use? In-Reply-To: <1218701945.70002.31.camel@localhost> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> <20080813080032.2328a474@bhuda.mired.org> <1218646719.70002.27.camel@localhost> <20080813130612.67542bd5@mbook.local> <1218701945.70002.31.camel@localhost> Message-ID: <20080814110959.64102a91@mbook.local> On Thu, 14 Aug 2008 09:19:05 +0100 Tom Evans wrote: > > On Wed, 2008-08-13 at 13:06 -0400, Mike Meyer wrote: > > On Wed, 13 Aug 2008 17:58:39 +0100 Tom Evans wrote: > > > > > On Wed, 2008-08-13 at 08:00 -0400, Mike Meyer wrote: > > > > > > > > stop If the service is to be started as specified by > > > > rc.conf(5), stop the service. This should check that the > > > > service is running and complain if it is not. If > > > > forcestop is given, ignore the rc.conf(5) check and > > > > attempt to stop. > > > > > > > Why should it complain? > > > > Because somebody quoted it out of context to justify a completely > > bogus assumption about what was and wasn't a bug. > > > > The bug in question is that the man page should note that > > force(start|stop|restart) should ignore any precmd problems as well as > > the setting in rc.conf, as that is what the tools provided by rc.subr > > do. > > > > > So the reason is 'Because'? > > Currently if you attempt to stop a service that is not started, there is > no error and no warning. I would like to know why you propose to change > that. Please don't jump down my throat. I don't - and didn't - propose changing it. I proposed correcting the wording on the man page so it reflects the reality of the 'force' prefix. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. O< ascii ribbon campaign - stop html mail - www.asciiribbon.org From tevans.uk at googlemail.com Thu Aug 14 15:52:05 2008 From: tevans.uk at googlemail.com (Tom Evans) Date: Thu Aug 14 15:52:11 2008 Subject: If not the force, what should I use? In-Reply-To: <20080814110959.64102a91@mbook.local> References: <78cb3d3f0808120810o54f49373n69ac5076c9a9c9b7@mail.gmail.com> <200808130813.56656.jonathan+freebsd-hackers@hst.org.za> <48A29E15.5080303@unsane.co.uk> <200808131227.30125.jonathan+freebsd-hackers@hst.org.za> <20080813080032.2328a474@bhuda.mired.org> <1218646719.70002.27.camel@localhost> <20080813130612.67542bd5@mbook.local> <1218701945.70002.31.camel@localhost> <20080814110959.64102a91@mbook.local> Message-ID: <1218729118.70002.38.camel@localhost> On Thu, 2008-08-14 at 11:09 -0400, Mike Meyer wrote: > > I don't - and didn't - propose changing it. I proposed correcting the > wording on the man page so it reflects the reality of the 'force' > prefix. > > Hello folks, I'm using "textvp_fullpath" function to get full path from vnode up to root dir. The problem is that, sometimes it works, sometimes no. I know that "textvp_fullpath" goes through the cache of the vnode and try to build full path. Are there any other ways to get full path? I haven't had any ideas yet, that is why I am asking you. Thanks. -- Uladzislau Rezki From rdivacky at freebsd.org Thu Aug 14 19:00:02 2008 From: rdivacky at freebsd.org (Roman Divacky) Date: Thu Aug 14 19:01:22 2008 Subject: textvp_fullpath In-Reply-To: <200808142120.13609.v.rezkii@sam-solutions.net> References: <200808142120.13609.v.rezkii@sam-solutions.net> Message-ID: <20080814184329.GA60497@freebsd.org> On Thu, Aug 14, 2008 at 09:20:12PM +0300, Uladzislau Rezki wrote: > Hello folks, > > I'm using "textvp_fullpath" function to get full path from vnode up to root dir. > The problem is that, sometimes it works, sometimes no. > > I know that "textvp_fullpath" goes through the cache of the vnode and > try to build full path. > > Are there any other ways to get full path? > I haven't had any ideas yet, that is why I am asking you. no... the vnode->full_path lookup is unreliable by definition in FreeBSD... what exactly are you trying to acomplish? I believe there might be other way to do whatever you want to do.. roman From v.rezkii at sam-solutions.net Fri Aug 15 09:17:02 2008 From: v.rezkii at sam-solutions.net (Uladzislau Rezki) Date: Fri Aug 15 09:17:10 2008 Subject: textvp_fullpath In-Reply-To: <20080814184329.GA60497@freebsd.org> References: <200808142120.13609.v.rezkii@sam-solutions.net> <20080814184329.GA60497@freebsd.org> Message-ID: <200808151217.04626.v.rezkii@sam-solutions.net> On 14 August 2008 21:43:29 Roman Divacky wrote: > On Thu, Aug 14, 2008 at 09:20:12PM +0300, Uladzislau Rezki wrote: > > Hello folks, > > > > I'm using "textvp_fullpath" function to get full path from vnode up to > > root dir. The problem is that, sometimes it works, sometimes no. > > > > I know that "textvp_fullpath" goes through the cache of the vnode and > > try to build full path. > > > > Are there any other ways to get full path? > > I haven't had any ideas yet, that is why I am asking you. > > no... the vnode->full_path lookup is unreliable by definition Yes , I've already got it. > in FreeBSD... what exactly are you trying to acomplish? I believe > there might be other way to do whatever you want to do.. > Well, I will try to describe it in more detail what i want to do, see below: The main task is, to pass information from the kernel space to user land about modification of file system via character device. For instance, we do something like that: echo 123 >> /etc/passwd we intercept the "write" system call and from this point we are within our own call: static int our_own_write_syscall (struct proc *p, struct write_args *uap) { struct vnode *vn = NULL; struct file *file; int sys_error; /* do system call */ sys_error = write(p, uap); if (sys_error != 0) goto leave_call; /* get the file */ file = p->p_fd->fd_ofiles[uap->fd]; /* get the vnode */ vn = (struct vnode *) file->f_data; ... } We have to to do a few thinks: 1) do original "write" sys call; 2) get full path (/etc/passwd); 3) put all this information to user land through the character device. I get stuck in point 2. I need to get full path, but how ... Thanks in advance. -- Uladzislau Rezki From avg at icyb.net.ua Fri Aug 15 12:48:32 2008 From: avg at icyb.net.ua (Andriy Gapon) Date: Fri Aug 15 12:48:39 2008 Subject: tilt/horizontal scroll support In-Reply-To: <20080813162931.GC718@epsilon.local> References: <48A300B9.5090105@icyb.net.ua> <20080813162931.GC718@epsilon.local> Message-ID: <48A57B1B.4000903@icyb.net.ua> on 13/08/2008 19:29 Rui Paulo said the following: > > Well, perhaps the best way is to teach sysmouse about horizontal scrolling > and then add a quirk WRT your mouse ? > > sysmouse(4) really needs to grow horizontal scrolling since nowadays every > mouse has it. Rui, I agree, this would be a perfect solution. What scares me is backward compatibility. I think that I do not understand how to do it right. So that older userland software works with newer kernels and newer userland works with older kernels. As I understand there are interfaces of hardware mouse drivers, then there is moused, then there is sysmouse interface and then there are user applications like X server. Knowledge of horizontal scrolling needs to be added to all components in the chain and it is better be done in backward-compatible fashion. And I really do not know to do this properly. Would it be just adding some new bytes to the protocol or growing a new protocol (level) or something else... P.S. I replaced usb ml with arch@ in cc. -- Andriy Gapon From chuckr at telenix.org Fri Aug 15 20:49:38 2008 From: chuckr at telenix.org (Chuck Robey) Date: Fri Aug 15 20:49:44 2008 Subject: startup options Message-ID: <48A5EBF6.5060908@telenix.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was wondering if it was possible, with a machine that has about 2 year old dual AMD64 processors and an up-to-date AMI BIOS, to get the machine to be able to start up from a power shutdown, after some sort of a network signal? If it might be possible, could you maybe put me onto the path of whatever info there might be on that subject? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkil6/YACgkQz62J6PPcoOk0wQCfTxUcKLOdhsOUvpwVNYOw74Ly V04AoISC3BGQsnlJeCUsdSc/VxK+K0D6 =FsXX -----END PGP SIGNATURE----- From vince at unsane.co.uk Fri Aug 15 21:00:28 2008 From: vince at unsane.co.uk (Vincent Hoffman) Date: Fri Aug 15 21:00:37 2008 Subject: startup options In-Reply-To: <48A5EBF6.5060908@telenix.org> References: <48A5EBF6.5060908@telenix.org> Message-ID: <48A5EE69.7030504@unsane.co.uk> Chuck Robey wrote: > I was wondering if it was possible, with a machine that has about 2 > year old > dual AMD64 processors and an up-to-date AMI BIOS, to get the machine > to be able > to start up from a power shutdown, after some sort of a network signal? > > If it might be possible, could you maybe put me onto the path of > whatever info > there might be on that subject? Wake on LAN is I believe a work in progress. http://wiki.freebsd.org/WakeOnLan its not an area I have much knowledge of though so other might be able to help more. Vince _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From stsp at stsp.name Fri Aug 15 21:39:33 2008 From: stsp at stsp.name (Stefan Sperling) Date: Fri Aug 15 21:39:41 2008 Subject: startup options In-Reply-To: <48A5EE69.7030504@unsane.co.uk> References: <48A5EBF6.5060908@telenix.org> <48A5EE69.7030504@unsane.co.uk> Message-ID: <20080815214021.GA1620@ted.stsp.name> On Fri, Aug 15, 2008 at 10:00:25PM +0100, Vincent Hoffman wrote: > Chuck Robey wrote: > > I was wondering if it was possible, with a machine that has about 2 > > year old > > dual AMD64 processors and an up-to-date AMI BIOS, to get the machine > > to be able > > to start up from a power shutdown, after some sort of a network signal? > > > > If it might be possible, could you maybe put me onto the path of > > whatever info > > there might be on that subject? > Wake on LAN is I believe a work in progress. > http://wiki.freebsd.org/WakeOnLan > its not an area I have much knowledge of though so other might be able > to help more. That page pretty much summarises the state of affairs, yes. Basically, you need a VIA-based ethernet card card (vr driver) and -CURRENT, or a vr card with 7.0 and patches from here: http://www.stsp.name/wol/FreeBSD-8-CURRENT-wol-backported-to-7.0/ All of those. Except the patch for pxe.c, that's there by accident. If you don't have a vr card, you will likely need to do some hacking. Follow the links from the wiki page for more information. Stefan From sam at freebsd.org Fri Aug 15 21:52:23 2008 From: sam at freebsd.org (Sam Leffler) Date: Fri Aug 15 21:52:29 2008 Subject: startup options In-Reply-To: <20080815214021.GA1620@ted.stsp.name> References: <48A5EBF6.5060908@telenix.org> <48A5EE69.7030504@unsane.co.uk> <20080815214021.GA1620@ted.stsp.name> Message-ID: <48A5FA95.2000902@freebsd.org> Stefan Sperling wrote: > On Fri, Aug 15, 2008 at 10:00:25PM +0100, Vincent Hoffman wrote: > >> Chuck Robey wrote: >> >>> I was wondering if it was possible, with a machine that has about 2 >>> year old >>> dual AMD64 processors and an up-to-date AMI BIOS, to get the machine >>> to be able >>> to start up from a power shutdown, after some sort of a network signal? >>> >>> If it might be possible, could you maybe put me onto the path of >>> whatever info >>> there might be on that subject? >>> >> Wake on LAN is I believe a work in progress. >> http://wiki.freebsd.org/WakeOnLan >> its not an area I have much knowledge of though so other might be able >> to help more. >> > > That page pretty much summarises the state of affairs, yes. > > Basically, you need a VIA-based ethernet card card (vr driver) > and -CURRENT, or a vr card with 7.0 and patches from here: > http://www.stsp.name/wol/FreeBSD-8-CURRENT-wol-backported-to-7.0/ > All of those. Except the patch for pxe.c, that's there by accident. > > If you don't have a vr card, you will likely need to do some > hacking. Follow the links from the wiki page for more information. > > trouble% cd sys/dev/ trouble% grep -l IFCAP_WOL */*.c age/if_age.c jme/if_jme.c re/if_re.c stge/if_stge.c vr/if_vr.c So 5 drivers right now support WOL. Jack said em had support a while back but he seems to have not hooked it up. Sam From rwatson at FreeBSD.org Fri Aug 15 22:09:41 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Fri Aug 15 22:09:48 2008 Subject: textvp_fullpath In-Reply-To: <200808151217.04626.v.rezkii@sam-solutions.net> References: <200808142120.13609.v.rezkii@sam-solutions.net> <20080814184329.GA60497@freebsd.org> <200808151217.04626.v.rezkii@sam-solutions.net> Message-ID: On Fri, 15 Aug 2008, Uladzislau Rezki wrote: > We have to to do a few thinks: > > 1) do original "write" sys call; > 2) get full path (/etc/passwd); > 3) put all this information to user land through the character device. > > I get stuck in point 2. I need to get full path, but how ... In FreeBSD 6.2 and higher, the kernel event auditing facility provides exactly this service already. Take a look at the auditpipe(4) facility for details of the run-time monitoring aspect of that. Robert N M Watson Computer Laboratory University of Cambridge From gballet at gmail.com Sat Aug 16 09:30:33 2008 From: gballet at gmail.com (Guillaume Ballet) Date: Sat Aug 16 09:30:40 2008 Subject: Extending the ddb command set Message-ID: Hello hackers, I am currently working on a small project and would like to add a few commands to the set that is available in ddb. I found that very interesting albeit succinct presentation: http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp where the author hints that I should use DB_COMMAND, which I did. Yet when invoking ddb, the command does not appear in the help list. I have taken a look at the source code and was expecting set_db_cmd_set to appear in my module's section list when calling objdump -h Is DB_COMMAND only working within the kernel itself, and not modules? Guillaume From rfrench at freebsd.org Sat Aug 16 10:29:56 2008 From: rfrench at freebsd.org (Ryan French) Date: Sat Aug 16 10:30:02 2008 Subject: Building custom kernel with new files Message-ID: <200808162210.02467.rfrench@freebsd.org> Hi All, I am currently trying to build a custom kernel for my Google Summer of Code, and am running into a bit of a problem. I have all of my code compiling, but when I get to the linking stage as soon as it comes to the new files I have installed it says the *.o does not exist. I have added the files to /conf/files, and well as added the files to /conf/options and /conf/NOTES, and the option is set in my Makefile for the kernel. Is there another step I need to do before I can build the kernel? Thanks for any help. Ryan French. From rdivacky at freebsd.org Sat Aug 16 10:34:48 2008 From: rdivacky at freebsd.org (Roman Divacky) Date: Sat Aug 16 10:34:55 2008 Subject: Building custom kernel with new files In-Reply-To: <200808162210.02467.rfrench@freebsd.org> References: <200808162210.02467.rfrench@freebsd.org> Message-ID: <20080816103309.GA22394@freebsd.org> On Sat, Aug 16, 2008 at 10:10:02PM +1200, Ryan French wrote: > Hi All, > > I am currently trying to build a custom kernel for my Google Summer of Code, > and am running into a bit of a problem. I have all of my code compiling, but > when I get to the linking stage as soon as it comes to the new files I have > installed it says the *.o does not exist. I have added the files > to /conf/files, and well as added the files to /conf/options and /conf/NOTES, > and the option is set in my Makefile for the kernel. Is there another step I > need to do before I can build the kernel? how do you build the kernel? adding to conf/files and conf/options should be sufficient... From attilio at freebsd.org Sat Aug 16 11:07:39 2008 From: attilio at freebsd.org (Attilio Rao) Date: Sat Aug 16 11:07:46 2008 Subject: Building custom kernel with new files In-Reply-To: <200808162210.02467.rfrench@freebsd.org> References: <200808162210.02467.rfrench@freebsd.org> Message-ID: <3bbf2fe10808160338s19d25242id2f008744ab24ede@mail.gmail.com> 2008/8/16, Ryan French : > Hi All, > > I am currently trying to build a custom kernel for my Google Summer of Code, > and am running into a bit of a problem. I have all of my code compiling, but > when I get to the linking stage as soon as it comes to the new files I have > installed it says the *.o does not exist. I have added the files > to /conf/files, and well as added the files to /conf/options and /conf/NOTES, > and the option is set in my Makefile for the kernel. Is there another step I > need to do before I can build the kernel? Ryan, can you please past the error message? More specifically, missing .o are about your newly included files or other? This can happen, for example, if the consumer of a subsystem wants to use it and the subsystem is not compiled (the stack(9) without STACK option, for example). Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From stsp at stsp.name Sat Aug 16 14:34:13 2008 From: stsp at stsp.name (Stefan Sperling) Date: Sat Aug 16 14:34:20 2008 Subject: startup options In-Reply-To: <48A5FA95.2000902@freebsd.org> References: <48A5EBF6.5060908@telenix.org> <48A5EE69.7030504@unsane.co.uk> <20080815214021.GA1620@ted.stsp.name> <48A5FA95.2000902@freebsd.org> Message-ID: <20080816143518.GE3057@ted.stsp.name> On Fri, Aug 15, 2008 at 02:52:21PM -0700, Sam Leffler wrote: > Stefan Sperling wrote: > > That page pretty much summarises the state of affairs, yes. > > > > Basically, you need a VIA-based ethernet card card (vr driver) > > and -CURRENT, or a vr card with 7.0 and patches from here: > > http://www.stsp.name/wol/FreeBSD-8-CURRENT-wol-backported-to-7.0/ > > All of those. Except the patch for pxe.c, that's there by accident. > > > > If you don't have a vr card, you will likely need to do some > > hacking. Follow the links from the wiki page for more information. > > > > > trouble% cd sys/dev/ > trouble% grep -l IFCAP_WOL */*.c > age/if_age.c > jme/if_jme.c > re/if_re.c > stge/if_stge.c > vr/if_vr.c > > So 5 drivers right now support WOL. Jack said em had support a while > back but he seems to have not hooked it up. Nice! I'll update the wiki page accordingly. What's with if_sis? Isn't it in yet because my patch only supports the NatSemi variant? (I have no idea whether the other variants work alike or not.) Stefan From sam at freebsd.org Sat Aug 16 17:15:36 2008 From: sam at freebsd.org (Sam Leffler) Date: Sat Aug 16 17:15:43 2008 Subject: Extending the ddb command set In-Reply-To: References: Message-ID: <48A70B37.60401@freebsd.org> Guillaume Ballet wrote: > Hello hackers, > > I am currently working on a small project and would like to add a few > commands to the set that is available in ddb. > > I found that very interesting albeit succinct presentation: > http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp > > where the author hints that I should use DB_COMMAND, which I did. Yet when > invoking ddb, the command does not appear in the help list. I have taken a > look at the source code and was expecting set_db_cmd_set to appear in my > module's section list when calling objdump -h > > Is DB_COMMAND only working within the kernel itself, and not modules? > > That is correct; you can't add ddb cmds from modules. It should be doable; just hasn't been done yet. Sam From rick-freebsd2008 at kiwi-computer.com Sat Aug 16 19:43:13 2008 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Sat Aug 16 19:43:21 2008 Subject: local network throughput issues Message-ID: <20080816194311.GA67723@keira.kiwi-computer.com> Hello. I've been having some serious network throughput issues recently. Prior to these issues, I was running 7.0-STABLE from a few months back. I recently build a world/kernel from csup(1) on 2008-Jul-25 and started noticing the issues. I'm currently on a RELENG_7 from 2008-Aug-02 and am building another one today. The server is running samba, dnsmasq, an NFS server, and is the gateway for a couple of freebsd machines. I first noticed the issue when I was unable to play mp3s served over samba. I was getting a throughput of about 3 KBytes/sec over my gigabit switched network. After a few weeks of trying different versions of samba and watching tcpdump/trafshow, I decided to try another test: % ssh gateway cat /dev/zero | dd of=/dev/null load: 0.00 cmd: dd 68286 [runnable] 0.00u 0.00s 0% 844k 3680+0 records in 3680+0 records out 1884160 bytes transferred in 512.856684 secs (3674 bytes/sec) ^C3680+0 records in 3680+0 records out 1884160 bytes transferred in 513.392858 secs (3670 bytes/sec) Killed by signal 2. Again, not even 4 KB/s throughput over ssh. What's weird is that not all network traffic is slow. I'm able to download at almost my full DSL speed (7168 Kbps) and here's the strange bit: NFS is fast! From the same machine as above, I have an NFS mountpoint: % dd if=/nfs/some_large_file of=/dev/null 55980+0 records in 55980+0 records out 28661760 bytes transferred in 0.147159 secs (194767476 bytes/sec) Which is what I would expect for a gigabit network. Even if I perform the same test over ssh: % ssh workstation cat /nfs/some_large_file | dd of=/dev/null 55980+0 records in 55980+0 records out 28661760 bytes transferred in 2.791392 secs (10267909 bytes/sec) This is reasonable considering ssh overhead. The kernel config for the server contains: include GENERIC ident DDB options KDB options KDB_TRACE options DDB options DDB_NUMSYM My internal network is on 172.23.20.x and the DSL modem is connected to the same NIC on 192.168.0.1: # ifconfig nfe0 nfe0: flags=8843 metric 0 mtu 1500 options=10b ether 00:15:f2:17:0c:20 inet 172.23.20.1 netmask 0xffffff00 broadcast 172.23.20.255 inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (1000baseTX ) status: active # ipfw show 00100 62968 8170100 allow ip from any to any via lo0 00110 0 0 deny ip from any to 127.0.0.0/8 00120 0 0 deny ip from 127.0.0.0/8 to any 00130 25444031 23419621364 divert 8668 ip from any to any via 192.168.0.3 00140 0 0 deny ip from not 172.23.20.0/24 to 172.23.20.0/24 dst-port 137-149,445 00150 20639141 15067620538 allow tcp from any to any established 00160 21 10683 allow ip from any to any frag 00170 79791 4696696 allow tcp from any to any setup 65530 5713367 8864760207 allow ip from any to any 65535 0 0 deny ip from any to any Other than that, I'm not doing anything out of the ordinary. Why is NFS behaving correctly and why are ssh/smbd connections so slow? I've pasted my dmesg output below. I've used this configuration for years and it wasn't until a recent RELENG_7 upgrade that I've had any problems. The box was 99-100% idle during those tests and I don't see an interrupt storm or anything funny like that. Any ideas? -- Rick C. Petty >From /var/run/dmesg.boot: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #5: Sat Aug 2 19:43:25 CDT 2008 rick@gateway:/usr/obj/usr/src/sys/DDB module_register: module sk/miibus already exists! Module sk/miibus failed to register: 17 module_register: module skc/sk already exists! Module skc/sk failed to register: 17 module_register: module pci/skc already exists! Module pci/skc failed to register: 17 module_register: module rl/miibus already exists! Module rl/miibus failed to register: 17 module_register: module cardbus/rl already exists! Module cardbus/rl failed to register: 17 module_register: module pci/rl already exists! Module pci/rl failed to register: 17 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2211.34-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x3 Cores per package: 2 real memory = 1073676288 (1023 MB) avail memory = 1037037568 (988 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 3fef0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd0002000-0xd0002fff irq 20 at device 7.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd0001000-0xd0001fff irq 21 at device 8.0 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] pcib1: at device 9.0 on pci0 pci5: on pcib1 vgapci0: mem 0xc0000000-0xc7ffffff irq 16 at device 6.0 on pci5 atapci3: port 0xa000-0xa07f,0xa400-0xa4ff mem 0xc9041000-0xc9041fff,0xc9000000-0xc901ffff irq 17 at device 7.0 on pci5 atapci3: [ITHREAD] atapci3: [ITHREAD] ata6: on atapci3 ata6: [ITHREAD] ata7: on atapci3 ata7: [ITHREAD] ata8: on atapci3 ata8: [ITHREAD] ata9: on atapci3 ata9: [ITHREAD] atapci4: port 0xa800-0xa87f,0xac00-0xacff mem 0xc9040000-0xc9040fff,0xc9020000-0xc903ffff irq 18 at device 8.0 on pci5 atapci4: [ITHREAD] atapci4: [ITHREAD] ata10: on atapci4 ata10: [ITHREAD] ata11: on atapci4 ata11: [ITHREAD] ata12: on atapci4 ata12: [ITHREAD] ata13: on atapci4 ata13: [ITHREAD] nfe0: port 0xb000-0xb007 mem 0xd0000000-0xd0000fff irq 22 at device 10.0 on pci0 miibus0: on nfe0 e1000phy0: PHY 9 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: Ethernet address: 00:15:f2:17:0c:20 nfe0: [FILTER] pcib2: at device 11.0 on pci0 pci4: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci2: on pcib4 pcib5: at device 14.0 on pci0 pci1: on pcib5 cpu0: on acpi0 powernow0: on cpu0 device_attach: powernow0 attach returned 6 cpu1: on acpi0 powernow1: on cpu1 device_attach: powernow1 attach returned 6 acpi_button0: on acpi0 acpi_tz0: on acpi0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xccfff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled ad0: 157066MB at ata0-master UDMA100 ad12: 715404MB at ata6-master SATA150 ad14: 715404MB at ata7-master SATA150 ad16: 715404MB at ata8-master SATA150 ad18: 715404MB at ata9-master SATA150 ad20: 476940MB at ata10-master SATA300 ad22: 476940MB at ata11-master SATA300 ad24: 476940MB at ata12-master SATA300 ad26: 476940MB at ata13-master SATA300 SMP: AP CPU #1 Launched! GEOM_LABEL: Label for provider ad0s1g is ufs/cache. Trying to mount root from ufs:/dev/ad0s1a GEOM_LABEL: Label ufs/cache removed. GEOM_LABEL: Label for provider ad0s1g is ufs/cache. GEOM_LABEL: Label ufs/cache removed. nfe0: link state changed to UP Additional messages from dmesg -a: Aug 16 14:02:20 gateway login: ROOT LOGIN (root) ON ttyv3 nfe0: promiscuous mode enabled nfe0: promiscuous mode disabled From rick-freebsd2008 at kiwi-computer.com Sat Aug 16 20:42:21 2008 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Sat Aug 16 20:42:27 2008 Subject: local network throughput issues In-Reply-To: References: <20080816194311.GA67723@keira.kiwi-computer.com> Message-ID: <20080816204219.GB67723@keira.kiwi-computer.com> On Sat, Aug 16, 2008 at 10:31:31PM +0200, usleepless@gmail.com wrote: > > i immediatly think dns issues if samba and ssh are slow. are your > hosts reverse lookup-able? Yes. DNS problems usually affect the time to connect, and those are fast. It's just the throughput I'm seeing a problem with. In fact in each sshd_config, I have: UseDNS no In dnsmasq, I have each host listed in /etc/hosts which is used by dnsmasq for forward and reverse DNS. No this problem started when I updated the OS on my gateway. -- Rick C. Petty From rfrench at freebsd.org Sat Aug 16 20:46:04 2008 From: rfrench at freebsd.org (Ryan French) Date: Sat Aug 16 20:46:11 2008 Subject: Building custom kernel with new files In-Reply-To: <20080816103309.GA22394@freebsd.org> References: <200808162210.02467.rfrench@freebsd.org> <20080816103309.GA22394@freebsd.org> Message-ID: <200808170846.01379.rfrench@freebsd.org> On Sat, 16 Aug 2008 10:33:09 pm you wrote: > On Sat, Aug 16, 2008 at 10:10:02PM +1200, Ryan French wrote: > > Hi All, > > > > I am currently trying to build a custom kernel for my Google Summer of > > Code, and am running into a bit of a problem. I have all of my code > > compiling, but when I get to the linking stage as soon as it comes to the > > new files I have installed it says the *.o does not exist. I have added > > the files to /conf/files, and well as added the files to /conf/options > > and /conf/NOTES, and the option is set in my Makefile for the kernel. Is > > there another step I need to do before I can build the kernel? > > how do you build the kernel? adding to conf/files and conf/options should > be sufficient... I build the file using make buildkernel KERNCONF=MPLSKERNEL while in the /usr/src/ directory. From usleepless at gmail.com Sat Aug 16 20:57:14 2008 From: usleepless at gmail.com (usleepless@gmail.com) Date: Sat Aug 16 20:57:21 2008 Subject: local network throughput issues In-Reply-To: <20080816194311.GA67723@keira.kiwi-computer.com> References: <20080816194311.GA67723@keira.kiwi-computer.com> Message-ID: On 8/16/08, Rick C. Petty wrote: > Hello. I've been having some serious network throughput issues recently. > Prior to these issues, I was running 7.0-STABLE from a few months back. I > recently build a world/kernel from csup(1) on 2008-Jul-25 and started > noticing the issues. I'm currently on a RELENG_7 from 2008-Aug-02 and am > building another one today. > > The server is running samba, dnsmasq, an NFS server, and is the gateway for > a couple of freebsd machines. I first noticed the issue when I was unable > to play mp3s served over samba. I was getting a throughput of about 3 > KBytes/sec over my gigabit switched network. After a few weeks of trying > different versions of samba and watching tcpdump/trafshow, I decided to try > another test: > > % ssh gateway cat /dev/zero | dd of=/dev/null > load: 0.00 cmd: dd 68286 [runnable] 0.00u 0.00s 0% 844k > 3680+0 records in > 3680+0 records out > 1884160 bytes transferred in 512.856684 secs (3674 bytes/sec) > ^C3680+0 records in > 3680+0 records out > 1884160 bytes transferred in 513.392858 secs (3670 bytes/sec) > Killed by signal 2. > > Again, not even 4 KB/s throughput over ssh. What's weird is that not all > network traffic is slow. I'm able to download at almost my full DSL speed > (7168 Kbps) and here's the strange bit: NFS is fast! From the same > machine as above, I have an NFS mountpoint: > > % dd if=/nfs/some_large_file of=/dev/null > 55980+0 records in > 55980+0 records out > 28661760 bytes transferred in 0.147159 secs (194767476 bytes/sec) > > Which is what I would expect for a gigabit network. Even if I perform the > same test over ssh: > > % ssh workstation cat /nfs/some_large_file | dd of=/dev/null > 55980+0 records in > 55980+0 records out > 28661760 bytes transferred in 2.791392 secs (10267909 bytes/sec) > > This is reasonable considering ssh overhead. The kernel config for the > server contains: > > include GENERIC > ident DDB > options KDB > options KDB_TRACE > options DDB > options DDB_NUMSYM > > My internal network is on 172.23.20.x and the DSL modem is connected to the > same NIC on 192.168.0.1: > > # ifconfig nfe0 > nfe0: flags=8843 metric 0 mtu 1500 > options=10b > ether 00:15:f2:17:0c:20 > inet 172.23.20.1 netmask 0xffffff00 broadcast 172.23.20.255 > inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (1000baseTX ) > status: active > > # ipfw show > 00100 62968 8170100 allow ip from any to any via lo0 > 00110 0 0 deny ip from any to 127.0.0.0/8 > 00120 0 0 deny ip from 127.0.0.0/8 to any > 00130 25444031 23419621364 divert 8668 ip from any to any via 192.168.0.3 > 00140 0 0 deny ip from not 172.23.20.0/24 to 172.23.20.0/24 dst-port 137-149,445 > 00150 20639141 15067620538 allow tcp from any to any established > 00160 21 10683 allow ip from any to any frag > 00170 79791 4696696 allow tcp from any to any setup > 65530 5713367 8864760207 allow ip from any to any > 65535 0 0 deny ip from any to any > > Other than that, I'm not doing anything out of the ordinary. Why is NFS > behaving correctly and why are ssh/smbd connections so slow? I've pasted > my dmesg output below. I've used this configuration for years and it > wasn't until a recent RELENG_7 upgrade that I've had any problems. The box > was 99-100% idle during those tests and I don't see an interrupt storm or > anything funny like that. Any ideas? > > -- Rick C. Petty > > > >From /var/run/dmesg.boot: > > > Copyright (c) 1992-2008 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 7.0-STABLE #5: Sat Aug 2 19:43:25 CDT 2008 > rick@gateway:/usr/obj/usr/src/sys/DDB > module_register: module sk/miibus already exists! > Module sk/miibus failed to register: 17 > module_register: module skc/sk already exists! > Module skc/sk failed to register: 17 > module_register: module pci/skc already exists! > Module pci/skc failed to register: 17 > module_register: module rl/miibus already exists! > Module rl/miibus failed to register: 17 > module_register: module cardbus/rl already exists! > Module cardbus/rl failed to register: 17 > module_register: module pci/rl already exists! > Module pci/rl failed to register: 17 > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ (2211.34-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 > Features=0x178bfbff > Features2=0x1 > AMD Features=0xe2500800 > AMD Features2=0x3 > Cores per package: 2 > real memory = 1073676288 (1023 MB) > avail memory = 1037037568 (988 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 2 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, 3fef0000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: at device 0.0 (no driver attached) > isab0: at device 1.0 on pci0 > isa0: on isab0 > pci0: at device 1.1 (no driver attached) > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd0002000-0xd0002fff irq 20 at device 7.0 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd0001000-0xd0001fff irq 21 at device 8.0 on pci0 > atapci2: [ITHREAD] > ata4: on atapci2 > ata4: [ITHREAD] > ata5: on atapci2 > ata5: [ITHREAD] > pcib1: at device 9.0 on pci0 > pci5: on pcib1 > vgapci0: mem 0xc0000000-0xc7ffffff irq 16 at device 6.0 on pci5 > atapci3: port 0xa000-0xa07f,0xa400-0xa4ff mem 0xc9041000-0xc9041fff,0xc9000000-0xc901ffff irq 17 at device 7.0 on pci5 > atapci3: [ITHREAD] > atapci3: [ITHREAD] > ata6: on atapci3 > ata6: [ITHREAD] > ata7: on atapci3 > ata7: [ITHREAD] > ata8: on atapci3 > ata8: [ITHREAD] > ata9: on atapci3 > ata9: [ITHREAD] > atapci4: port 0xa800-0xa87f,0xac00-0xacff mem 0xc9040000-0xc9040fff,0xc9020000-0xc903ffff irq 18 at device 8.0 on pci5 > atapci4: [ITHREAD] > atapci4: [ITHREAD] > ata10: on atapci4 > ata10: [ITHREAD] > ata11: on atapci4 > ata11: [ITHREAD] > ata12: on atapci4 > ata12: [ITHREAD] > ata13: on atapci4 > ata13: [ITHREAD] > nfe0: port 0xb000-0xb007 mem 0xd0000000-0xd0000fff irq 22 at device 10.0 on pci0 > miibus0: on nfe0 > e1000phy0: PHY 9 on miibus0 > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto > nfe0: Ethernet address: 00:15:f2:17:0c:20 > nfe0: [FILTER] > pcib2: at device 11.0 on pci0 > pci4: on pcib2 > pcib3: at device 12.0 on pci0 > pci3: on pcib3 > pcib4: at device 13.0 on pci0 > pci2: on pcib4 > pcib5: at device 14.0 on pci0 > pci1: on pcib5 > cpu0: on acpi0 > powernow0: on cpu0 > device_attach: powernow0 attach returned 6 > cpu1: on acpi0 > powernow1: on cpu1 > device_attach: powernow1 attach returned 6 > acpi_button0: on acpi0 > acpi_tz0: on acpi0 > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xccfff pnpid ORM0000 on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > atkbd0: [ITHREAD] > ppc0: parallel port not found. > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio0: [FILTER] > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwarding disabled, default to deny, logging disabled > ad0: 157066MB at ata0-master UDMA100 > ad12: 715404MB at ata6-master SATA150 > ad14: 715404MB at ata7-master SATA150 > ad16: 715404MB at ata8-master SATA150 > ad18: 715404MB at ata9-master SATA150 > ad20: 476940MB at ata10-master SATA300 > ad22: 476940MB at ata11-master SATA300 > ad24: 476940MB at ata12-master SATA300 > ad26: 476940MB at ata13-master SATA300 > SMP: AP CPU #1 Launched! > GEOM_LABEL: Label for provider ad0s1g is ufs/cache. > Trying to mount root from ufs:/dev/ad0s1a > GEOM_LABEL: Label ufs/cache removed. > GEOM_LABEL: Label for provider ad0s1g is ufs/cache. > GEOM_LABEL: Label ufs/cache removed. > nfe0: link state changed to UP > > Additional messages from dmesg -a: > > Aug 16 14:02:20 gateway login: ROOT LOGIN (root) ON ttyv3 > nfe0: promiscuous mode enabled > nfe0: promiscuous mode disabled i immediatly think dns issues if samba and ssh are slow. are your hosts reverse lookup-able? regards, usleep From rfrench at freebsd.org Sat Aug 16 21:05:24 2008 From: rfrench at freebsd.org (Ryan French) Date: Sat Aug 16 21:05:31 2008 Subject: Building custom kernel with new files In-Reply-To: <3bbf2fe10808160338s19d25242id2f008744ab24ede@mail.gmail.com> References: <200808162210.02467.rfrench@freebsd.org> <3bbf2fe10808160338s19d25242id2f008744ab24ede@mail.gmail.com> Message-ID: <200808170905.22691.rfrench@freebsd.org> On Sat, 16 Aug 2008 10:38:24 pm you wrote: > 2008/8/16, Ryan French : > > Hi All, > > > > I am currently trying to build a custom kernel for my Google Summer of > > Code, and am running into a bit of a problem. I have all of my code > > compiling, but when I get to the linking stage as soon as it comes to the > > new files I have installed it says the *.o does not exist. I have added > > the files to /conf/files, and well as added the files to /conf/options > > and /conf/NOTES, and the option is set in my Makefile for the kernel. Is > > there another step I need to do before I can build the kernel? > > Ryan, > can you please past the error message? > More specifically, missing .o are about your newly included files or other? > This can happen, for example, if the consumer of a subsystem wants to > use it and the subsystem is not compiled (the stack(9) without STACK > option, for example). > > Thanks, > Attilio The missing .o is about my own files that I have included in the kernel. More specifically I have a file 'mpls.h' and as it is the first one in the directory as soon as it gets to linking the file I get the error ld: mpls.o: No such file: No such file or directory *** Error code 1 This occurs right after the command MAKE=make sh /usr/src/sys/conf/newvers.sh MPLSKERNEL Sorry I cant copy the whole error but I am running the development in a VM and I cant copy and paste between the VM and my host machine. From attilio at freebsd.org Sat Aug 16 21:08:50 2008 From: attilio at freebsd.org (Attilio Rao) Date: Sat Aug 16 21:08:57 2008 Subject: Building custom kernel with new files In-Reply-To: <200808170905.22691.rfrench@freebsd.org> References: <200808162210.02467.rfrench@freebsd.org> <3bbf2fe10808160338s19d25242id2f008744ab24ede@mail.gmail.com> <200808170905.22691.rfrench@freebsd.org> Message-ID: <3bbf2fe10808161408y337a94d0pef6e63c5901969e5@mail.gmail.com> 2008/8/16, Ryan French : > On Sat, 16 Aug 2008 10:38:24 pm you wrote: > > 2008/8/16, Ryan French : > > > Hi All, > > > > > > I am currently trying to build a custom kernel for my Google Summer of > > > Code, and am running into a bit of a problem. I have all of my code > > > compiling, but when I get to the linking stage as soon as it comes to the > > > new files I have installed it says the *.o does not exist. I have added > > > the files to /conf/files, and well as added the files to /conf/options > > > and /conf/NOTES, and the option is set in my Makefile for the kernel. Is > > > there another step I need to do before I can build the kernel? > > > > Ryan, > > can you please past the error message? > > More specifically, missing .o are about your newly included files or other? > > This can happen, for example, if the consumer of a subsystem wants to > > use it and the subsystem is not compiled (the stack(9) without STACK > > option, for example). > > > > Thanks, > > Attilio > > The missing .o is about my own files that I have included in the kernel. More > specifically I have a file 'mpls.h' and as it is the first one in the > directory as soon as it gets to linking the file I get the error > > ld: mpls.o: No such file: No such file or directory > *** Error code 1 > > This occurs right after the command > > MAKE=make sh /usr/src/sys/conf/newvers.sh MPLSKERNEL > > Sorry I cant copy the whole error but I am running the development in a VM and > I cant copy and paste between the VM and my host machine. Can you please paste your diff against src/sys/conf/files* ? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From koitsu at FreeBSD.org Sat Aug 16 22:15:36 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Aug 16 22:15:42 2008 Subject: local network throughput issues In-Reply-To: <20080816194311.GA67723@keira.kiwi-computer.com> References: <20080816194311.GA67723@keira.kiwi-computer.com> Message-ID: <20080816221535.GA82290@eos.sc1.parodius.com> On Sat, Aug 16, 2008 at 02:43:11PM -0500, Rick C. Petty wrote: > Hello. I've been having some serious network throughput issues recently. > Prior to these issues, I was running 7.0-STABLE from a few months back. I > recently build a world/kernel from csup(1) on 2008-Jul-25 and started > noticing the issues. I'm currently on a RELENG_7 from 2008-Aug-02 and am > building another one today. > > The server is running samba, dnsmasq, an NFS server, and is the gateway for > a couple of freebsd machines. I first noticed the issue when I was unable > to play mp3s served over samba. I was getting a throughput of about 3 > KBytes/sec over my gigabit switched network. After a few weeks of trying > different versions of samba and watching tcpdump/trafshow, I decided to try > another test: > > % ssh gateway cat /dev/zero | dd of=/dev/null > load: 0.00 cmd: dd 68286 [runnable] 0.00u 0.00s 0% 844k > 3680+0 records in > 3680+0 records out > 1884160 bytes transferred in 512.856684 secs (3674 bytes/sec) > ^C3680+0 records in > 3680+0 records out > 1884160 bytes transferred in 513.392858 secs (3670 bytes/sec) > Killed by signal 2. > > Again, not even 4 KB/s throughput over ssh. What's weird is that not all > network traffic is slow. I'm able to download at almost my full DSL speed > (7168 Kbps) and here's the strange bit: NFS is fast! From the same > machine as above, I have an NFS mountpoint: > > % dd if=/nfs/some_large_file of=/dev/null > 55980+0 records in > 55980+0 records out > 28661760 bytes transferred in 0.147159 secs (194767476 bytes/sec) > > Which is what I would expect for a gigabit network. Even if I perform the > same test over ssh: > > % ssh workstation cat /nfs/some_large_file | dd of=/dev/null > 55980+0 records in > 55980+0 records out > 28661760 bytes transferred in 2.791392 secs (10267909 bytes/sec) > > This is reasonable considering ssh overhead. The kernel config for the > server contains: > > include GENERIC > ident DDB > options KDB > options KDB_TRACE > options DDB > options DDB_NUMSYM > > My internal network is on 172.23.20.x and the DSL modem is connected to the > same NIC on 192.168.0.1: > > # ifconfig nfe0 > nfe0: flags=8843 metric 0 mtu 1500 > options=10b > ether 00:15:f2:17:0c:20 > inet 172.23.20.1 netmask 0xffffff00 broadcast 172.23.20.255 > inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255 > media: Ethernet autoselect (1000baseTX ) > status: active > > # ipfw show > 00100 62968 8170100 allow ip from any to any via lo0 > 00110 0 0 deny ip from any to 127.0.0.0/8 > 00120 0 0 deny ip from 127.0.0.0/8 to any > 00130 25444031 23419621364 divert 8668 ip from any to any via 192.168.0.3 > 00140 0 0 deny ip from not 172.23.20.0/24 to 172.23.20.0/24 dst-port 137-149,445 > 00150 20639141 15067620538 allow tcp from any to any established > 00160 21 10683 allow ip from any to any frag > 00170 79791 4696696 allow tcp from any to any setup > 65530 5713367 8864760207 allow ip from any to any > 65535 0 0 deny ip from any to any > > Other than that, I'm not doing anything out of the ordinary. Why is NFS > behaving correctly and why are ssh/smbd connections so slow? I've pasted > my dmesg output below. I've used this configuration for years and it > wasn't until a recent RELENG_7 upgrade that I've had any problems. The box > was 99-100% idle during those tests and I don't see an interrupt storm or > anything funny like that. Any ideas? 1) Please provide netstat -in output. 2) NFS (unless you're explicitly disabling it) is UDP-based, while SSH and Samba are TCP-based. Your nfe0 device has TSO4 enabled on it, so I'm left wondering if the TCP offloading support for your nfe(4) device is broken. Can you try disabling it by adding -tso to your ifconfig_nfe0 line in /etc/rc.conf? If you're using DHCP on that interface, that may pose somewhat of a problem. 3) Can you disable the firewall (disable ipfw entirely) and see if the problem continues? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From rick-freebsd2008 at kiwi-computer.com Sat Aug 16 22:28:33 2008 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Sat Aug 16 22:28:39 2008 Subject: local network throughput issues In-Reply-To: <20080816221535.GA82290@eos.sc1.parodius.com> References: <20080816194311.GA67723@keira.kiwi-computer.com> <20080816221535.GA82290@eos.sc1.parodius.com> Message-ID: <20080816222831.GC67723@keira.kiwi-computer.com> On Sat, Aug 16, 2008 at 03:15:35PM -0700, Jeremy Chadwick wrote: > > 1) Please provide netstat -in output. Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll nfe0 1500 00:15:f2:17:0c:20 14714298 0 14821857 0 0 nfe0 1500 172.23.20.0/2 172.23.20.1 2144815 - 12438012 - - nfe0 1500 192.168.0.0/2 192.168.0.3 9502416 - 2357751 - - lo0 16384 31707 0 31707 0 0 lo0 16384 fe80:2::1/64 fe80:2::1 0 - 0 - - lo0 16384 ::1/128 ::1 6 - 6 - - lo0 16384 127.0.0.0/8 127.0.0.1 31588 - 31588 - - tun11 1500 985877 0 890589 0 0 tun11 1500 172.23.23.20/ 172.23.23.20 714240 - 713237 - - tun0 1500 22456 0 21872 0 0 tun0 1500 172.16.1.0/32 172.16.1.0 0 - 0 - - > 2) NFS (unless you're explicitly disabling it) is UDP-based, while SSH > and Samba are TCP-based. Your nfe0 device has TSO4 enabled on it, so > I'm left wondering if the TCP offloading support for your nfe(4) device > is broken. > > Can you try disabling it by adding -tso to your ifconfig_nfe0 line in > /etc/rc.conf? If you're using DHCP on that interface, that may pose > somewhat of a problem. Yes, that seems to have made all the difference in the world: % ssh gateway cat /dev/zero | dd of=/dev/null load: 0.08 cmd: ssh 68698 [runnable] 1.20u 0.25s 11% 3020k 94384+0 records in 94384+0 records out 48324608 bytes transferred in 5.314707 secs (9092619 bytes/sec) load: 0.08 cmd: ssh 68698 [runnable] 1.81u 0.33s 15% 3020k 147664+0 records in 147664+0 records out 75603968 bytes transferred in 7.652768 secs (9879297 bytes/sec) So I'm thinking TSO wasn't an option in the older 7-stable I was running and now it is, but the support for it is broken. Your comment about DHCP, would that affect dhcpd or dhclient? This is my "server" machine so I don't run dhclient on it. I hardcode the IP connecting to the DSL modem. I'm currently hardcoding all the other machines also so I should be okay. > 3) Can you disable the firewall (disable ipfw entirely) and see if the > problem continues? Well the firewall is primarily for NAT and port forwarding. There's nothing special about it. It looks like the TSO disabling fixed my problems. Thank you for the suggestion! -- Rick C. Petty From koitsu at FreeBSD.org Sat Aug 16 23:14:30 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Sat Aug 16 23:14:37 2008 Subject: local network throughput issues In-Reply-To: <20080816222831.GC67723@keira.kiwi-computer.com> References: <20080816194311.GA67723@keira.kiwi-computer.com> <20080816221535.GA82290@eos.sc1.parodius.com> <20080816222831.GC67723@keira.kiwi-computer.com> Message-ID: <20080816231429.GA86316@eos.sc1.parodius.com> On Sat, Aug 16, 2008 at 05:28:31PM -0500, Rick C. Petty wrote: > > 2) NFS (unless you're explicitly disabling it) is UDP-based, while SSH > > and Samba are TCP-based. Your nfe0 device has TSO4 enabled on it, so > > I'm left wondering if the TCP offloading support for your nfe(4) device > > is broken. > > > > Can you try disabling it by adding -tso to your ifconfig_nfe0 line in > > /etc/rc.conf? If you're using DHCP on that interface, that may pose > > somewhat of a problem. > > Yes, that seems to have made all the difference in the world: > > % ssh gateway cat /dev/zero | dd of=/dev/null > load: 0.08 cmd: ssh 68698 [runnable] 1.20u 0.25s 11% 3020k > 94384+0 records in > 94384+0 records out > 48324608 bytes transferred in 5.314707 secs (9092619 bytes/sec) > load: 0.08 cmd: ssh 68698 [runnable] 1.81u 0.33s 15% 3020k > 147664+0 records in > 147664+0 records out > 75603968 bytes transferred in 7.652768 secs (9879297 bytes/sec) > > So I'm thinking TSO wasn't an option in the older 7-stable I was running > and now it is, but the support for it is broken. TSO support is something that's implemented in each network driver. TSO in nfe(4) was commited to HEAD (CURRENT) on June 12th 2007. See revision 1.17 below: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/nfe/if_nfe.c That would have been what is now considered RELENG_7 (since FreeBSD 7.0-RELEASE was announced and made available on February 27th, 2008). I'm under the impression that TSO was available/enabled for you before, but I'm not sure because there's not a lot of historic data available here. I don't know why/how it broke, or what has changed. I've CC'd one of the nfe(4) maintainers, PYUN Yong-Hyeon, who should be able to help determine what's going on. Yong-Hyeon, his dmesg output is available here, but you'll probably need more than that: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-August/025706.html > Your comment about DHCP, would that affect dhcpd or dhclient? This is my > "server" machine so I don't run dhclient on it. I hardcode the IP > connecting to the DSL modem. I'm currently hardcoding all the other > machines also so I should be okay. My comment about DHCP is WRT to the FreeBSD box acting as a DHCP client (e.g. fetching an IP from your ISP). I believe dhclient (when getting a new IP) might override any interface options you set in rc.conf; purely speculative on my part, but I wanted to mention it in the case you didn't have a static IP configured in rc.conf. > > 3) Can you disable the firewall (disable ipfw entirely) and see if the > > problem continues? > > Well the firewall is primarily for NAT and port forwarding. There's > nothing special about it. It looks like the TSO disabling fixed my > problems. Thank you for the suggestion! No problem. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From ivoras at freebsd.org Sun Aug 17 12:37:57 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sun Aug 17 12:38:11 2008 Subject: Xen in HEAD Message-ID: Hi, I see commits to Xen framework in SVN so I'd like to ask what is its current status? Is it still as described in http://wiki.freebsd.org/FreeBSD/Xen ? Will it be MFC-ed before 7.1-RELEASE? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080817/8e3a9831/signature.pgp From ivoras at freebsd.org Sun Aug 17 12:50:09 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sun Aug 17 12:50:16 2008 Subject: Xen in HEAD In-Reply-To: References: Message-ID: Ivan Voras wrote: > Hi, > > I see commits to Xen framework in SVN so I'd like to ask what is its > current status? Is it still as described in > http://wiki.freebsd.org/FreeBSD/Xen ? Will it be MFC-ed before 7.1-RELEASE? One more question: Which version of Xen will be supported? The wiki mentions 3.0 but the most recent Xen release is 3.2. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080817/076d2597/signature.pgp From gballet at gmail.com Sun Aug 17 17:17:55 2008 From: gballet at gmail.com (Guillaume Ballet) Date: Sun Aug 17 17:18:01 2008 Subject: Extending the ddb command set In-Reply-To: <48A70B37.60401@freebsd.org> References: <48A70B37.60401@freebsd.org> Message-ID: On Sat, Aug 16, 2008 at 5:15 PM, Sam Leffler wrote: > > Guillaume Ballet wrote: >> >> Hello hackers, >> >> I am currently working on a small project and would like to add a few >> commands to the set that is available in ddb. >> >> I found that very interesting albeit succinct presentation: >> http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp >> >> where the author hints that I should use DB_COMMAND, which I did. Yet when >> invoking ddb, the command does not appear in the help list. I have taken a >> look at the source code and was expecting set_db_cmd_set to appear in my >> module's section list when calling objdump -h >> >> Is DB_COMMAND only working within the kernel itself, and not modules? >> >> > > That is correct; you can't add ddb cmds from modules. It should be doable; just hasn't been done yet. > > Sam > It is indeed doable: Here are the diffs for a first attempt at doing this. I am not entirely satisfied with it, though, as it does not work with DB_SHOW_COMMAND and the likes... Also, I have to declare a lot of ddb-related stuff into kern_linker.c and I don't like it. I am currently working at improving the whole thing, but in the mean time if someone wants to give it a try, comments/rants would be greatly appreciated. Guillaume --- sys/linker.h.orig 2008-08-17 18:45:56.000000000 +0200 +++ sys/linker.h 2008-08-17 18:50:57.000000000 +0200 @@ -155,6 +155,9 @@ int linker_ddb_search_symbol(caddr_t _value, c_linker_sym_t *_sym, long *_diffp); int linker_ddb_symbol_values(c_linker_sym_t _sym, linker_symval_t *_symval); +struct command; +int linker_ddb_cmd_search(char *, struct command **); +int linker_ddb_cmd_list(void); /* HWPMC helper */ --- kern/kern_linker.c.orig 2008-08-17 08:38:51.000000000 +0200 +++ kern/kern_linker.c 2008-08-17 18:47:45.000000000 +0200 @@ -777,6 +777,9 @@ * that the files list is inconsistant instead. */ +#include +#include + int linker_ddb_lookup(const char *symstr, c_linker_sym_t *sym) { @@ -831,6 +834,52 @@ } return (ENOENT); } + +int linker_ddb_cmd_list() +{ + linker_file_t lf; + struct command **start, **stop, **search; + + TAILQ_FOREACH(lf, &linker_files, link) { + if (!linker_file_lookup_set(lf,"db_cmd_set",&start,&stop,NULL)) { + for (search=start; search < stop; search++) { + db_printf("%-12s", (*search)->name); + db_end_line(12); + } + } + } + + return 0; +} + +int linker_ddb_cmd_search(char *name, struct command **cmdp) +{ + linker_file_t lf; + char *lp, *rp; + struct command **cmd, **start, **stop; + int c; + + TAILQ_FOREACH(lf, &linker_files, link) { + if (!linker_file_lookup_set(lf, "db_cmd_set", &start, &stop, NULL)) { + for (cmd=start; cmd < stop; cmd++) { + lp = name; + rp = (*cmd)->name; + + while((c = *lp) == *rp) { + if (c == 0) { + *cmdp = *cmd; + return 0; + } + + lp++; + rp++; + } + } + } + } + + return -1; +} #endif /* --- ddb/db_command.c.orig 2008-08-17 10:26:26.000000000 +0200 +++ ddb/db_command.c 2008-08-17 18:42:22.000000000 +0200 @@ -253,6 +253,9 @@ if (result == CMD_UNIQUE) return (CMD_UNIQUE); } + if (result == CMD_NONE && linker_ddb_cmd_search(name,cmdp) == 0) { + result = CMD_UNIQUE; + } if (result == CMD_NONE) { /* check for 'help' */ if (name[0] == 'h' && name[1] == 'e' @@ -280,6 +283,7 @@ db_printf("%-12s", (*aux_cmdp)->name); db_end_line(12); } + linker_ddb_cmd_list(); } static void --- ddb/db_command.h.orig 2008-08-17 18:37:34.000000000 +0200 +++ ddb/db_command.h 2008-08-17 18:49:29.000000000 +0200 @@ -46,4 +46,7 @@ extern db_addr_t db_next; /* next address to be examined or written */ +extern int linker_ddb_cmd_search(char*,struct command **); +extern int linker_ddb_cmd_list(void); + #endif /* !_DDB_DB_COMMAND_H_ */ From gballet at gmail.com Sun Aug 17 17:44:57 2008 From: gballet at gmail.com (Guillaume Ballet) Date: Sun Aug 17 17:45:03 2008 Subject: Extending the ddb command set In-Reply-To: <20080817172051.GX1803@deviant.kiev.zoral.com.ua> References: <48A70B37.60401@freebsd.org> <20080817172051.GX1803@deviant.kiev.zoral.com.ua> Message-ID: >> >> It is indeed doable: Here are the diffs for a first attempt at doing >> this. I am not entirely satisfied with it, though, as it does not work >> with DB_SHOW_COMMAND and the likes... Also, I have to declare a lot of >> ddb-related stuff into kern_linker.c and I don't like it. I am >> currently working at improving the whole thing, but in the mean time >> if someone wants to give it a try, comments/rants would be greatly >> appreciated. > > What about module unloading ? > Thanks for replying so quickly :) When a module is unloaded from the system, it is removed from the linker_files list and will therefore not be available anymore when walking through the module list. I have checked on my side and this is indeed what happens. If you saw some problem I didn't, would you please mind to elaborate? Guillaume From kostikbel at gmail.com Sun Aug 17 18:05:33 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Sun Aug 17 18:05:41 2008 Subject: Extending the ddb command set In-Reply-To: References: <48A70B37.60401@freebsd.org> Message-ID: <20080817172051.GX1803@deviant.kiev.zoral.com.ua> On Sun, Aug 17, 2008 at 05:17:54PM +0000, Guillaume Ballet wrote: > On Sat, Aug 16, 2008 at 5:15 PM, Sam Leffler wrote: > > > > Guillaume Ballet wrote: > >> > >> Hello hackers, > >> > >> I am currently working on a small project and would like to add a few > >> commands to the set that is available in ddb. > >> > >> I found that very interesting albeit succinct presentation: > >> http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp > >> > >> where the author hints that I should use DB_COMMAND, which I did. Yet when > >> invoking ddb, the command does not appear in the help list. I have taken a > >> look at the source code and was expecting set_db_cmd_set to appear in my > >> module's section list when calling objdump -h > >> > >> Is DB_COMMAND only working within the kernel itself, and not modules? > >> > >> > > > > That is correct; you can't add ddb cmds from modules. It should be doable; just hasn't been done yet. > > > > Sam > > > > It is indeed doable: Here are the diffs for a first attempt at doing > this. I am not entirely satisfied with it, though, as it does not work > with DB_SHOW_COMMAND and the likes... Also, I have to declare a lot of > ddb-related stuff into kern_linker.c and I don't like it. I am > currently working at improving the whole thing, but in the mean time > if someone wants to give it a try, comments/rants would be greatly > appreciated. What about module unloading ? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080817/558f2663/attachment.pgp From sam at freebsd.org Sun Aug 17 18:23:33 2008 From: sam at freebsd.org (Sam Leffler) Date: Sun Aug 17 18:23:45 2008 Subject: Extending the ddb command set In-Reply-To: References: <48A70B37.60401@freebsd.org> Message-ID: <48A86CA3.3040007@freebsd.org> Guillaume Ballet wrote: > On Sat, Aug 16, 2008 at 5:15 PM, Sam Leffler wrote: > >> Guillaume Ballet wrote: >> >>> Hello hackers, >>> >>> I am currently working on a small project and would like to add a few >>> commands to the set that is available in ddb. >>> >>> I found that very interesting albeit succinct presentation: >>> http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp >>> >>> where the author hints that I should use DB_COMMAND, which I did. Yet when >>> invoking ddb, the command does not appear in the help list. I have taken a >>> look at the source code and was expecting set_db_cmd_set to appear in my >>> module's section list when calling objdump -h >>> >>> Is DB_COMMAND only working within the kernel itself, and not modules? >>> >>> >>> >> That is correct; you can't add ddb cmds from modules. It should be doable; just hasn't been done yet. >> >> Sam >> >> > > It is indeed doable: Here are the diffs for a first attempt at doing > this. I am not entirely satisfied with it, though, as it does not work > with DB_SHOW_COMMAND and the likes... Also, I have to declare a lot of > ddb-related stuff into kern_linker.c and I don't like it. I am > currently working at improving the whole thing, but in the mean time > if someone wants to give it a try, comments/rants would be greatly > appreciated. > > Last I looked at this I was convinced it could be done using SYSINIT's and the existing mechanisms for adding ddb cmds. I don't think you need to modify the linker or ddb. Not sure if you looked sys/module.h and/or sys/kernel.h? Sam From tut at nhamon.com.ua Sun Aug 17 18:59:51 2008 From: tut at nhamon.com.ua (Artem Naluzhnyy) Date: Sun Aug 17 19:00:24 2008 Subject: High syscall rate Message-ID: <65dfa4fc0808171132g4a827a82y590e9d5ae849bd23@mail.gmail.com> Hi, I have 6.1-RELEASE system with lots of processes in production. Is there any way to determine which process causes high syscall rate? No kernel upgrade or sizeable downtime allowed. -- Artem Naluzhnyy From max at love2party.net Sun Aug 17 19:17:27 2008 From: max at love2party.net (Max Laier) Date: Sun Aug 17 19:17:35 2008 Subject: High syscall rate In-Reply-To: <65dfa4fc0808171132g4a827a82y590e9d5ae849bd23@mail.gmail.com> References: <65dfa4fc0808171132g4a827a82y590e9d5ae849bd23@mail.gmail.com> Message-ID: <200808172117.24894.max@love2party.net> On Sunday 17 August 2008 20:32:03 Artem Naluzhnyy wrote: > I have 6.1-RELEASE system with lots of processes in production. Is > there any way to determine which process causes high syscall rate? No > kernel upgrade or sizeable downtime allowed. see ktrace(1) -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From mat.macy at gmail.com Sun Aug 17 21:13:27 2008 From: mat.macy at gmail.com (Matthew Macy) Date: Sun Aug 17 21:37:50 2008 Subject: Xen in HEAD In-Reply-To: References: Message-ID: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> On Sun, Aug 17, 2008 at 5:49 AM, Ivan Voras wrote: > Ivan Voras wrote: >> >> Hi, >> >> I see commits to Xen framework in SVN so I'd like to ask what is its >> current status? Is it still as described in >> http://wiki.freebsd.org/FreeBSD/Xen ? Will it be MFC-ed before 7.1-RELEASE? > > One more question: Which version of Xen will be supported? The wiki mentions > 3.0 but the most recent Xen release is 3.2. Xen support will be MFC'd when it proves to be sufficiently stable for some uses. It probably won't make the freeze for 7.1. Xen 3.2 is the initial target. I've deliberately avoided any fanfare about the commits. When it is ready for "beta-use" I will update the wiki. Thanks, Kip From ivoras at freebsd.org Sun Aug 17 21:56:48 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sun Aug 17 21:56:55 2008 Subject: Xen in HEAD In-Reply-To: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> References: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> Message-ID: <9bbcef730808171427y7be526a8i6c526dabd83f7bc3@mail.gmail.com> 2008/8/17 Matthew Macy : > On Sun, Aug 17, 2008 at 5:49 AM, Ivan Voras wrote: >> Ivan Voras wrote: >>> >>> Hi, >>> >>> I see commits to Xen framework in SVN so I'd like to ask what is its >>> current status? Is it still as described in >>> http://wiki.freebsd.org/FreeBSD/Xen ? Will it be MFC-ed before 7.1-RELEASE? >> >> One more question: Which version of Xen will be supported? The wiki mentions >> 3.0 but the most recent Xen release is 3.2. > > Xen support will be MFC'd when it proves to be sufficiently stable for > some uses. It probably won't make the freeze for 7.1. Xen 3.2 is the > initial target. > > I've deliberately avoided any fanfare about the commits. When it is > ready for "beta-use" I will update the wiki. Ok, thanks! From kmacy at freebsd.org Sun Aug 17 22:03:56 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sun Aug 17 22:04:03 2008 Subject: Xen in HEAD In-Reply-To: <86hc9j2u01.fsf@srvbsdnanssv.interne.kisoft-services.com> References: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> <86hc9j2u01.fsf@srvbsdnanssv.interne.kisoft-services.com> Message-ID: <3c1674c90808171503wd51432fh96c80971e85b9f5a@mail.gmail.com> On Sun, Aug 17, 2008 at 2:48 PM, Eric Masson wrote: > "Matthew Macy" writes: > > Hi Kip, > >> Xen support will be MFC'd when it proves to be sufficiently stable for >> some uses. It probably won't make the freeze for 7.1. Xen 3.2 is the >> initial target. > > Dom0/DomU or DomU only please ? DomU only to start off with. The currently planned progression is: stabilize in HEAD -> SMP -> x86_64 -> dom0 -Kip From emss at free.fr Sun Aug 17 22:26:36 2008 From: emss at free.fr (Eric Masson) Date: Sun Aug 17 22:26:44 2008 Subject: Xen in HEAD In-Reply-To: <3c1674c90808171503wd51432fh96c80971e85b9f5a@mail.gmail.com> (Kip Macy's message of "Sun, 17 Aug 2008 15:03:55 -0700") References: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> <86hc9j2u01.fsf@srvbsdnanssv.interne.kisoft-services.com> <3c1674c90808171503wd51432fh96c80971e85b9f5a@mail.gmail.com> Message-ID: <86d4k72s88.fsf@srvbsdnanssv.interne.kisoft-services.com> "Kip Macy" writes: > DomU only to start off with. The currently planned progression is: > stabilize in HEAD -> SMP -> x86_64 -> dom0 Great, Thanks a lot for your work :) ?ric Masson -- Vous faites chier avec vos annonces ? la con ! Ou sont les mod?rateurs ????? Ca se d?grade cheza Ol?ane, ca se d?grade ...Ah ouais j'avais oubli? , y'a du Farce T?l?com derri?re, ca doit ?tre ?a ... -+- PP in: - Tout, faut tout mod?rer -+- From emss at free.fr Sun Aug 17 22:50:17 2008 From: emss at free.fr (Eric Masson) Date: Sun Aug 17 22:50:24 2008 Subject: Xen in HEAD In-Reply-To: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> (Matthew Macy's message of "Sun, 17 Aug 2008 13:44:16 -0700") References: <3c1674c90808171344g3c8658f3j87a6cdc301d71a79@mail.gmail.com> Message-ID: <86hc9j2u01.fsf@srvbsdnanssv.interne.kisoft-services.com> "Matthew Macy" writes: Hi Kip, > Xen support will be MFC'd when it proves to be sufficiently stable for > some uses. It probably won't make the freeze for 7.1. Xen 3.2 is the > initial target. Dom0/DomU or DomU only please ? Regards ?ric Masson -- t?tu comme un mule :) Enfin, l'avenir nous le dira sans doute et si j'ai raison, je ne me g?nerai pas pour le hurler de partout, par contre, si c'est toi qui a raison, merci de ne pas trop en faire :))) -+- GU21 in - Pile je gagne, face tu perds -+- From yanefbsd at gmail.com Mon Aug 18 08:04:37 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Mon Aug 18 08:04:44 2008 Subject: Idea for FreeBSD In-Reply-To: <200808121414.44139.jonathan+freebsd-hackers@hst.org.za> References: <78086795e6ab9676870368dcebb57b37.squirrel@secure.futurecis.com> <78cb3d3f0808120503t3e2c7d68n1d4383c98aa41e10@mail.gmail.com> <200808121414.44139.jonathan+freebsd-hackers@hst.org.za> Message-ID: <61273574-0EE4-4D24-A543-C9AC38ED66B0@gmail.com> On Aug 12, 2008, at 5:14 AM, Jonathan McKeown wrote: > On Tuesday 12 August 2008 14:03:30 Adrian Penisoara wrote: >> While we're at it, I wish we could leverage the posibility for the >> admin to manually start the service at the CLI, no matter whether the >> service has been enabled or not -- that is the "_enable" keyword >> should have effect only in the bootup/automatic contexts. > > Isn't this what onestart does? > > Jonathan I may be a bit late into the conversation, but for what it's worth upstart does have some positive features in the 0.5.0 version (the one that just rolled off the SVN train recently). Their use of simple and complex job start criteria and the ability to link in process monitoring functionality via DBUS clients is interesting... albeit not necessary except in high availability environments. -Garrett From gballet at gmail.com Mon Aug 18 09:14:46 2008 From: gballet at gmail.com (Guillaume Ballet) Date: Mon Aug 18 09:14:53 2008 Subject: Extending the ddb command set In-Reply-To: <48A86CA3.3040007@freebsd.org> References: <48A70B37.60401@freebsd.org> <48A86CA3.3040007@freebsd.org> Message-ID: On Sun, Aug 17, 2008 at 6:23 PM, Sam Leffler wrote: (snip) > Last I looked at this I was convinced it could be done using SYSINIT's and > the existing mechanisms for adding ddb cmds. I don't think you need to > modify the linker or ddb. Not sure if you looked sys/module.h and/or > sys/kernel.h? I have indeed looked at these files. That's actually what brought me to work on the linker when I realize now that was no necessary. Looking at them twice didn't hurt, though :) SYSINIT is a good idea to get some "struct command"s into kernel space and register them through come command. One can imagine creating a DB_COMMAND_MODULE macro or something that would do exactly that. I have however doubts on the registration part: In ddb/db_command.c, the following table is declared: static struct command_table db_command_table = { db_commands, SET_BEGIN(db_cmd_set), SET_LIMIT(db_cmd_set) }; which is the table that is used in db_command_loop. I am not aware of any other mechanism to add commands to that list. That table is made up of two parts: The first entry is a list of all the default commands. The two next entries define the boundaries of a list of pointers to optional commands. That list could be extended by a module SYSCTL but: - The table is declared as static, so at least that part must be modified, or an accessor must be written. No big deal. - Memory must be allocated and relevant information must be logged so as to know what to remove when unloading a module. That is possible, but I feel it is more risky because memory needs to be allocated and a set of locks would not hurt in that case. Parsing the list of modules each time has the advantage that no memory has to be allocated and there is no concurrency problems when the debugger is invoked (I think, please let me know if that assumption is wrong). Also, module unloading is not a problem because once the module goes, it is not in the list anymore and therefore commands can not be seen nor accessed anymore. Of course I could be wrong (or just biased?) so once again let me know if you think otherwise. Note that I have a simpler patch in progress that should not alter the linker since it will use linker_file_foreach. Either way, thanks for your comments. And sorry about the long message. Guillaume. From samflanker at gmail.com Mon Aug 18 10:17:03 2008 From: samflanker at gmail.com (sam) Date: Mon Aug 18 10:17:14 2008 Subject: sysinstall -> upgrade Message-ID: <48A94C10.5050802@gmail.com> Hello. Faced with a strange situation. output of downgrade HEAD -> 7.0-RELEASE ----------------------------------------------------------- # uname -a FreeBSD damask 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Jun 16 17:44:59 SAMST 2008 root@damask:/usr/obj/usr/src/sys/DAMASK i386 ----------------------------------------------------------- after sysinstall (upgrade to 7.0-RELEASE) ----------------------------------------------------------- # ls -l /boot/kernel total 0 # ls -l /boot/ total 980 drwxr-xr-x 2 root wheel 25600 Aug 18 11:58 GENERIC -r--r--r-- 1 root wheel 7636 Feb 24 20:52 beastie.4th -r--r--r-- 1 root wheel 8192 Feb 24 20:52 boot -r--r--r-- 1 root wheel 512 Feb 24 20:52 boot0 -r--r--r-- 1 root wheel 512 Feb 24 20:52 boot0sio -r--r--r-- 1 root wheel 512 Feb 24 20:52 boot1 -r--r--r-- 1 root wheel 7680 Feb 24 20:52 boot2 -r--r--r-- 1 root wheel 1201 Feb 24 20:52 cdboot drwxr-xr-x 2 root wheel 512 Aug 18 11:58 defaults -r--r--r-- 1 root wheel 1739 Feb 24 20:53 device.hints drwxr-xr-x 2 root wheel 512 Feb 24 20:49 firmware -r--r--r-- 1 root wheel 2249 Feb 24 20:52 frames.4th -r--r--r-- 1 root wheel 7551 Aug 14 09:27 gptboot drwxr-xr-x 2 root wheel 512 Feb 24 20:49 kernel drwxr-xr-x 2 root wheel 512 Aug 13 15:30 kernel.old drwxr-xr-x 2 root wheel 25600 Aug 18 11:47 kernel.prev -r-xr-xr-x 1 root wheel 253952 Feb 24 20:52 loader -r--r--r-- 1 root wheel 7545 Feb 24 20:52 loader.4th -rw-r--r-- 1 root wheel 105 May 12 14:32 loader.conf -r--r--r-- 1 root wheel 15219 Feb 24 20:52 loader.help -r-xr-xr-x 1 root wheel 245760 Aug 13 15:05 loader.old -r--r--r-- 1 root wheel 385 Feb 24 20:52 loader.rc -r--r--r-- 1 root wheel 512 Feb 24 20:52 mbr drwxr-xr-x 2 root wheel 512 Feb 24 20:49 modules -r--r--r-- 1 root wheel 512 Aug 14 09:27 pmbr -r--r--r-- 1 root wheel 256000 Feb 24 20:52 pxeboot -r--r--r-- 1 root wheel 692 Feb 24 20:52 screen.4th -r--r--r-- 1 root wheel 36435 Feb 24 20:52 support.4th drwxr-xr-x 2 root wheel 512 Feb 24 20:49 zfs # # ls -l /boot/GENERIC total 114862 -r-xr-xr-x 1 root wheel 14215 Feb 24 23:16 3dfx.ko -r-xr-xr-x 1 root wheel 49242 Feb 24 23:16 3dfx.ko.symbols -r-xr-xr-x 1 root wheel 5120 Feb 24 23:16 3dfx_linux.ko -r-xr-xr-x 1 root wheel 26277 Feb 24 23:16 3dfx_linux.ko.symbols -r-xr-xr-x 1 root wheel 64716 Feb 24 23:16 aac.ko -r-xr-xr-x 1 root wheel 179069 Feb 24 23:16 aac.ko.symbols -r-xr-xr-x 1 root wheel 4611 Feb 24 23:16 aac_linux.ko -r-xr-xr-x 1 root wheel 25619 Feb 24 23:16 aac_linux.ko.symbols -r-xr-xr-x 1 root wheel 3520 Feb 24 23:16 accf_data.ko -r-xr-xr-x 1 root wheel 11200 Feb 24 23:16 accf_data.ko.symbols ***************detruncated output********************** ----------------------------------------------------------- kernel directory is empty - this is normal? /Vladimir Ermakov From v.rezkii at sam-solutions.net Mon Aug 18 13:21:09 2008 From: v.rezkii at sam-solutions.net (Uladzislau Rezki) Date: Mon Aug 18 13:21:28 2008 Subject: textvp_fullpath In-Reply-To: References: <200808142120.13609.v.rezkii@sam-solutions.net> <200808151217.04626.v.rezkii@sam-solutions.net> Message-ID: <200808181621.32105.v.rezkii@sam-solutions.net> On 16 August 2008 01:09:39 Robert Watson wrote: > On Fri, 15 Aug 2008, Uladzislau Rezki wrote: > > We have to to do a few thinks: > > > > 1) do original "write" sys call; > > 2) get full path (/etc/passwd); > > 3) put all this information to user land through the character device. > > > > I get stuck in point 2. I need to get full path, but how ... > > In FreeBSD 6.2 and higher, the kernel event auditing facility provides > exactly this service already. Take a look at the auditpipe(4) facility for > details of the run-time monitoring aspect of that. > Thank you, I haven't known about it before. I looked through the source code of the "auditpipe", and found a function called "canon_path" that obtains a full path using "vn_fullpath". This function retrieve the full filesystem path that correspond to a "vnode" from cache, BUT just in case it is available within "namecache". "textvp_fullpath" and "vn_fullpath" are not reliable. Maybe I've skipped something while investigating auditpipe, but I found only one place where they get full path (audit_bsm_klib.c +483) and they use "vn_fullpath". Please correct me if am not right. Thank you in advance. -- Uladzislau Rezki From jhb at freebsd.org Mon Aug 18 14:46:53 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Aug 18 14:47:05 2008 Subject: Extending the ddb command set In-Reply-To: References: <48A70B37.60401@freebsd.org> Message-ID: <200808181002.14885.jhb@freebsd.org> On Sunday 17 August 2008 01:17:54 pm Guillaume Ballet wrote: > On Sat, Aug 16, 2008 at 5:15 PM, Sam Leffler wrote: > > Guillaume Ballet wrote: > >> Hello hackers, > >> > >> I am currently working on a small project and would like to add a few > >> commands to the set that is available in ddb. > >> > >> I found that very interesting albeit succinct presentation: > >> http://people.freebsd.org/~jhb/papers/bsdcan/2008/slides.odp >>le.freebsd.org/%7Ejhb/papers/bsdcan/2008/slides.odp> > >> > >> where the author hints that I should use DB_COMMAND, which I did. Yet > >> when invoking ddb, the command does not appear in the help list. I have > >> taken a look at the source code and was expecting set_db_cmd_set to > >> appear in my module's section list when calling objdump -h > >> > >> Is DB_COMMAND only working within the kernel itself, and not modules? > > > > That is correct; you can't add ddb cmds from modules. It should be > > doable; just hasn't been done yet. > > > > Sam > > It is indeed doable: Here are the diffs for a first attempt at doing > this. I am not entirely satisfied with it, though, as it does not work > with DB_SHOW_COMMAND and the likes... Also, I have to declare a lot of > ddb-related stuff into kern_linker.c and I don't like it. I am > currently working at improving the whole thing, but in the mean time > if someone wants to give it a try, comments/rants would be greatly > appreciated. A simpler approach is probably to make DB_COMMAND() use a SYSINIT to register new functions instead of teaching DDB about that linker set. You just need to write a shared "register_command()" function (and a deregister for SYSUNINIT for module unload) that the SYSINIT uses. This also probably requires changing the structure of the DDB tables, though you might be able to make it simpler now. You could probably just make the tables be sorted linked lists now instead of arrays. This would also remove the whole "aux table" hack. > Guillaume > > --- sys/linker.h.orig 2008-08-17 18:45:56.000000000 +0200 > +++ sys/linker.h 2008-08-17 18:50:57.000000000 +0200 > @@ -155,6 +155,9 @@ > int linker_ddb_search_symbol(caddr_t _value, c_linker_sym_t *_sym, > long *_diffp); > int linker_ddb_symbol_values(c_linker_sym_t _sym, linker_symval_t > *_symval); +struct command; > +int linker_ddb_cmd_search(char *, struct command **); > +int linker_ddb_cmd_list(void); > > > /* HWPMC helper */ > --- kern/kern_linker.c.orig 2008-08-17 08:38:51.000000000 +0200 > +++ kern/kern_linker.c 2008-08-17 18:47:45.000000000 +0200 > @@ -777,6 +777,9 @@ > * that the files list is inconsistant instead. > */ > > +#include > +#include > + > int > linker_ddb_lookup(const char *symstr, c_linker_sym_t *sym) > { > @@ -831,6 +834,52 @@ > } > return (ENOENT); > } > + > +int linker_ddb_cmd_list() > +{ > + linker_file_t lf; > + struct command **start, **stop, **search; > + > + TAILQ_FOREACH(lf, &linker_files, link) { > + if (!linker_file_lookup_set(lf,"db_cmd_set",&start,&stop,NULL)) { > + for (search=start; search < stop; search++) { > + db_printf("%-12s", (*search)->name); > + db_end_line(12); > + } > + } > + } > + > + return 0; > +} > + > +int linker_ddb_cmd_search(char *name, struct command **cmdp) > +{ > + linker_file_t lf; > + char *lp, *rp; > + struct command **cmd, **start, **stop; > + int c; > + > + TAILQ_FOREACH(lf, &linker_files, link) { > + if (!linker_file_lookup_set(lf, "db_cmd_set", &start, &stop, > NULL)) { + for (cmd=start; cmd < stop; cmd++) { > + lp = name; > + rp = (*cmd)->name; > + > + while((c = *lp) == *rp) { > + if (c == 0) { > + *cmdp = *cmd; > + return 0; > + } > + > + lp++; > + rp++; > + } > + } > + } > + } > + > + return -1; > +} > #endif > > /* > --- ddb/db_command.c.orig 2008-08-17 10:26:26.000000000 +0200 > +++ ddb/db_command.c 2008-08-17 18:42:22.000000000 +0200 > @@ -253,6 +253,9 @@ > if (result == CMD_UNIQUE) > return (CMD_UNIQUE); > } > + if (result == CMD_NONE && linker_ddb_cmd_search(name,cmdp) == 0) { > + result = CMD_UNIQUE; > + } > if (result == CMD_NONE) { > /* check for 'help' */ > if (name[0] == 'h' && name[1] == 'e' > @@ -280,6 +283,7 @@ > db_printf("%-12s", (*aux_cmdp)->name); > db_end_line(12); > } > + linker_ddb_cmd_list(); > } > > static void > --- ddb/db_command.h.orig 2008-08-17 18:37:34.000000000 +0200 > +++ ddb/db_command.h 2008-08-17 18:49:29.000000000 +0200 > @@ -46,4 +46,7 @@ > extern db_addr_t db_next; /* next address to be examined > or written */ > > +extern int linker_ddb_cmd_search(char*,struct command **); > +extern int linker_ddb_cmd_list(void); > + > #endif /* !_DDB_DB_COMMAND_H_ */ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- John Baldwin From pb at ludd.ltu.se Mon Aug 18 13:51:34 2008 From: pb at ludd.ltu.se (Peter B) Date: Mon Aug 18 15:25:18 2008 Subject: Keyboard map for asus-eee900-linux Message-ID: <200808181351.m7IDpSZr020630@brother.ludd.ltu.se> Here's a new console + X11 keymap for FreeBSD on Asus Eee 900 linux netbook: It should work for all asus eee models with Swedish, Danish, Norwegian, Finnish or Icelandic keyboard. In particular this fixes the '|' character. (Asus Eee Nordic SE-DK-NW-FI-IS 80-keys) kbdcontrol -l asus_eee_nordic.kbd Console keyboard map diff: diff -ru /usr/share/syscons/keymaps/swedish.iso.kbd asus_eee_nordic.kbd --- /usr/share/syscons/keymaps/swedish.iso.kbd 2008-02-24 18:52:28.000000000 +0100 +++ asus_eee_nordic.kbd 2008-08-18 13:27:32.000000000 +0200 @@ -1,4 +1,4 @@ -# $FreeBSD: src/share/syscons/keymaps/swedish.iso.kbd,v 1.17 2001/03/11 23:41:19 ache Exp $ +# $FreeBSD: src/share/syscons/keymaps/nordic_eee900.kbd,v 1.0 2008/08/16 16:49:24 pb Exp $ # alt # scan cntrl alt alt cntrl lock # code base shift cntrl shift alt shift cntrl shift state @@ -11,24 +11,24 @@ 005 '4' 164 nop nop '$' nop nop nop O 006 '5' '%' nop nop nop nop nop nop O 007 '6' '&' nop nop nop nop nop nop O - 008 '7' '/' nop nop '{' nop nop nop O + 008 '7' '/' nop nop '{' '?' nop nop O 009 '8' '(' nop nop '[' nop nop nop O 010 '9' ')' nop nop ']' nop gs nop O 011 '0' '=' nop nop '}' nop nop nop O 012 '+' '?' nop nop '\' nop fs nop O - 013 128 '`' nop nop nop nop nop nop O + 013 128 '`' nop nop 39 '|' nop nop O 014 bs bs del del bs bs del del O 015 ht btab nop nop ht btab nop nop O 016 'q' 'Q' dc1 dc1 'q' 'Q' dc1 dc1 C 017 'w' 'W' etb etb 'w' 'W' etb etb C 018 'e' 'E' enq enq 164 'E' enq enq C - 019 'r' 'R' dc2 dc2 'r' 'R' dc2 dc2 C + 019 'r' 'R' dc2 dc2 '?' 'R' dc2 dc2 C 020 't' 'T' dc4 dc4 't' 'T' dc4 dc4 C 021 'y' 'Y' em em 'y' 'Y' em em C - 022 'u' 'U' nak nak 'u' 'U' nak nak C + 022 'u' 'U' nak nak '?' '?' nak nak C 023 'i' 'I' ht ht 'i' 'I' ht ht C 024 'o' 'O' si si 'o' 'O' si si C - 025 'p' 'P' dle dle 'p' 'P' dle dle C + 025 'p' 'P' dle dle '?' 'P' dle dle C 026 229 197 nop nop '}' ']' nop nop C 027 168 '^' nop nop '~' nop nop nop O 028 cr cr nl nl cr cr nl nl O @@ -47,15 +47,15 @@ 041 167 189 nop nop '\' '|' nop nop O 042 lshift lshift lshift lshift lshift lshift lshift lshift O 043 ''' '*' nop nop nop nop nop nop O - 044 'z' 'Z' sub sub 'z' 'Z' sub sub C + 044 'z' 'Z' sub sub '|' 'Z' sub sub C 045 'x' 'X' can can 'x' 'X' can can C 046 'c' 'C' etx etx 'c' 'C' etx etx C 047 'v' 'V' syn syn 'v' 'V' syn syn C - 048 'b' 'B' stx stx 'b' 'B' stx stx C + 048 'b' 'B' stx '?' 'b' 'B' stx stx C 049 'n' 'N' so so 'n' 'N' so so C - 050 'm' 'M' cr cr 'm' 'M' cr cr C - 051 ',' ';' nop nop nop '<' nop nop O - 052 '.' ':' nop nop nop '>' nop nop O + 050 'm' 'M' cr cr 181 'M' cr cr C + 051 ',' ';' nop nop '<' '<' nop nop O + 052 '.' ':' nop nop '>' '>' nop nop O 053 '-' '_' us nop '/' '?' nop nop O 054 rshift rshift rshift rshift rshift rshift rshift rshift O 055 '*' '*' '*' '*' '*' '*' '*' '*' O Console keyboard map as bzip -9z uuencode: begin 644 asus_eee_nordic.kbd.bz2 M0EIH.3%!62936="%76T`!_'_FO$P"`!_______________\``0,```"`A&`' M'W@GO,NK3PCO"&]D:T`!*BD:`'J:-``&0>FIZ$`!H````'IM3"GB8H--(&U( M35/0@:F(P$8"8F`1@`!&1II@$P`&D>4J>0FT(-```````````````DU2A/4W MHF%$-$9&"&FF`$8!!@!&30P1B9&"#@`&@T-!H`-,@T,@::```R`#(#(`"))! M&FE'@*:AH``&@&@````&@R-`&33$0!#M_!Z8!XZD8I&+`3IHQ9`#%[WZ^?20 M@2$_;:)Y$"42%$`!10HD."R3@,"9U%>$OBIZ=-=.OE7R>%N*)5GUZ<+M!H\U M.+CQN-K92M@TRS"BWHIDC?0BE`!&M)BF M+F=A#1!!A"^E!C%&)%%5B21O29T&^$AJSHDPW42/6QT3J=7\NKMZW-KYD4M%K5DJ*!6=D\ZQ&WT:]L%?!88X8W%[ MX:N$.8TY1*[J<9997)M2U;6G*TC8((((81$/)FE:AUXO;*[88Z\EUZ=/1E;1 M4\1%&`8$`-=VS1SMG/PPPUXZLL]1N66('5A(`%T%WK"]8-T1LL$@DEHU83[2?<'.)D[)+R7DO)LDP)@(N!"PA81=[F]>)9OUJS1D&F5RAHE$8% MQLTBB,+E(7LTS4BIC`Y4'35'A^"!,-6-^;'5]#U&?8=/P:*XV*%#PT-#QW#@ MH=E=,6%7BVY8X^5R+WCL.O?'[99DJ3\*;+:GE.GM0>:BP0D1(6\A+**4KBX' M'%/OOO4J$Z%*4)2(@F3!*0$L%1@L%6`L%1(B1$BP5$B)$2(D1@*2`*JJBK[E M5515*(JBJM&D*)#,$/6@9\)0-@G##2/$/=[JZ-38:L]58#6V,4JQ?M25YLU` MU]``O8RY[`2G%=(XT&"2"08%()!@4@D&"2"08)()!@BG,D&"*]X MG&I:D:!0=R>7*4B2;WE M)W:NJ"N&.62I5Q( MO"HS.L@!7$DDDDF;N222P&:E%+)8XVGBGD'+PILRQ`&M=`6`JP%6`JP%@+`P MSVYZYM>M9GCGHSOHJJF&.C,"_,"19`,*H"BJ`A1)!O=3B*J=L(PFBQ-K29DL M`!4,+U#SM65J5O>]:EB8M)FA7`%6J0`355E6DI3M"BZI9B[Z;[+%%V:42D-J5DUC#Z@#_ M;`O_K,((Y`=J!=JPL45$L(/#*+%U&W``"AR#`-2!I@!92O70)L7XDL6+$WN" M0!_X*9D`VJ`G8#487$O00.U`&V\$XN!;<%&U$T8WM6"XSY`E',:#;>2QR6'XPR4!-"4@?^+ *N2*<*$AH0JZV@``` ` end This is loaded with sh ~/.xmodmaprc in ~/.xinitrc (Should be done in another way. I just didn't get it to load the intended way) X11 keyboard xmodmap (~/.xmodmaprc): # Z | xmodmap -e "keycode 0x34 = z Z guillemotleft less 0x7C less" # `|` xmodmap -e "keycode 0x15 = dead_acute dead_grave plusminus notsign bar notsign" # ? 1/2 xmodmap -e "keycode 0x31 = section onehalf paragraph threequarters paragraph threequarters" # B ? xmodmap -e "keycode 0x38 = b B rightdoublequotemark rightsinglequotemark 223 rightsinglequotemark" # I ? xmodmap -e "keycode 0x1F = i I rightarrow idotless 182 idotless" So far I got ethernet(ae), wlan(ath), graphics (Xorg), sound (hda), raw cardreader (da), keyboard, and acpi battery status to work. Todo: camera, 3G-internet. From rysto32 at gmail.com Mon Aug 18 15:38:35 2008 From: rysto32 at gmail.com (Ryan Stone) Date: Mon Aug 18 15:50:01 2008 Subject: Acquiring a mtx after an sx lock Message-ID: Are there any problems acquiring a sleep mutex after acquiring an sx lock? man 9 locking says that you can't, but doesn't provide any reasons. Obviously while you're holding the mutex you have to abide by the rules applying to mutexes, but as long as you do that, I can't see why acquiring a mutex after an sx lock would cause an issue. Is the locking man page wrong about this? Ryan Stone From max at love2party.net Mon Aug 18 15:54:22 2008 From: max at love2party.net (Max Laier) Date: Mon Aug 18 15:54:28 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: References: Message-ID: <200808181754.18812.max@love2party.net> On Monday 18 August 2008 17:14:01 Ryan Stone wrote: > Are there any problems acquiring a sleep mutex after acquiring an sx lock? > man 9 locking says that you can't, but doesn't provide any reasons. > Obviously while you're holding the mutex you have to abide by the rules > applying to mutexes, but as long as you do that, I can't see why acquiring > a mutex after an sx lock would cause an issue. Is the locking man page > wrong about this? Where does it say so? The interaction table clearly shows: You have: You want: Spin_mtx Slp_mtx sx_lock rw_lock rm_locksleep SPIN mutex ok-1 no no no no no-3 Sleep mutex ok ok-1 no ok ok no-3 | V sx_lock ok -->ok<-- ok-2 ok ok ok-4 ^ | rw_lock ok ok no ok-2 ok no-3 rm_lock ok ok no ok ok-2 no -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From rysto32 at gmail.com Mon Aug 18 16:02:57 2008 From: rysto32 at gmail.com (Ryan Stone) Date: Mon Aug 18 16:10:51 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: <200808181754.18812.max@love2party.net> References: <200808181754.18812.max@love2party.net> Message-ID: I guess the FreeBSD 8 man pages have been fixed but the FreeBSD 7 ones haven't. This is what I was looking at: http://www.freebsd.org/cgi/man.cgi?query=locking&apropos=0&sektion=0&manpath=FreeBSD+7.0-RELEASE&format=html Thanks for the response, Ryan Stone On Mon, Aug 18, 2008 at 11:54 AM, Max Laier wrote: > On Monday 18 August 2008 17:14:01 Ryan Stone wrote: > > Are there any problems acquiring a sleep mutex after acquiring an sx > lock? > > man 9 locking says that you can't, but doesn't provide any reasons. > > Obviously while you're holding the mutex you have to abide by the rules > > applying to mutexes, but as long as you do that, I can't see why > acquiring > > a mutex after an sx lock would cause an issue. Is the locking man page > > wrong about this? > > Where does it say so? The interaction table clearly shows: > > You have: You want: Spin_mtx Slp_mtx sx_lock rw_lock rm_locksleep > SPIN mutex ok-1 no no no no no-3 > Sleep mutex ok ok-1 no ok ok no-3 > | > V > sx_lock ok -->ok<-- ok-2 ok ok ok-4 > ^ > | > rw_lock ok ok no ok-2 ok no-3 > rm_lock ok ok no ok ok-2 no > > > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News > From emaste at freebsd.org Mon Aug 18 16:46:13 2008 From: emaste at freebsd.org (Ed Maste) Date: Mon Aug 18 16:46:20 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: References: <200808181754.18812.max@love2party.net> Message-ID: <20080818162411.GA77460@sandvine.com> On Mon, Aug 18, 2008 at 12:02:56PM -0400, Ryan Stone wrote: > On Mon, Aug 18, 2008 at 11:54 AM, Max Laier wrote: > > > On Monday 18 August 2008 17:14:01 Ryan Stone wrote: > > > Are there any problems acquiring a sleep mutex after acquiring an sx > > lock? > > > man 9 locking says that you can't, but doesn't provide any reasons. > > [...] > > > > Where does it say so? The interaction table clearly shows: [...] Ahh, it seems ups' commit of rmlocks changed the "You have: sx_lock, You want: Slp_mtx" case from no to ok (in r173444). -Ed From julian at elischer.org Mon Aug 18 18:31:04 2008 From: julian at elischer.org (Julian Elischer) Date: Mon Aug 18 18:31:19 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: <20080818162411.GA77460@sandvine.com> References: <200808181754.18812.max@love2party.net> <20080818162411.GA77460@sandvine.com> Message-ID: <48A9BFED.604@elischer.org> Ed Maste wrote: > On Mon, Aug 18, 2008 at 12:02:56PM -0400, Ryan Stone wrote: > >> On Mon, Aug 18, 2008 at 11:54 AM, Max Laier wrote: >> >>> On Monday 18 August 2008 17:14:01 Ryan Stone wrote: >>>> Are there any problems acquiring a sleep mutex after acquiring an sx >>> lock? >>>> man 9 locking says that you can't, but doesn't provide any reasons. >>> [...] >>> >>> Where does it say so? The interaction table clearly shows: [...] > > Ahh, it seems ups' commit of rmlocks changed the "You have: sx_lock, > You want: Slp_mtx" case from no to ok (in r173444). hmmm you know, I'm not sure what the correct answer is.. I thought rw locks were mutex compatible but sx locks were NOT.. > > -Ed > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From julian at elischer.org Mon Aug 18 18:38:36 2008 From: julian at elischer.org (Julian Elischer) Date: Mon Aug 18 18:38:45 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: <48A9BFED.604@elischer.org> References: <200808181754.18812.max@love2party.net> <20080818162411.GA77460@sandvine.com> <48A9BFED.604@elischer.org> Message-ID: <48A9C1B0.5010805@elischer.org> Julian Elischer wrote: > Ed Maste wrote: >> On Mon, Aug 18, 2008 at 12:02:56PM -0400, Ryan Stone wrote: >> >>> On Mon, Aug 18, 2008 at 11:54 AM, Max Laier wrote: >>> >>>> On Monday 18 August 2008 17:14:01 Ryan Stone wrote: >>>>> Are there any problems acquiring a sleep mutex after acquiring an sx >>>> lock? >>>>> man 9 locking says that you can't, but doesn't provide any reasons. >>>> [...] >>>> >>>> Where does it say so? The interaction table clearly shows: [...] >> >> Ahh, it seems ups' commit of rmlocks changed the "You have: sx_lock, >> You want: Slp_mtx" case from no to ok (in r173444). > > > hmmm > you know, I'm not sure what the correct answer is.. I thought rw locks > were mutex compatible but sx locks were NOT.. Ignore me.. I was reading the table backwards.. of course if you have an sx you can still take out a mutex, but not visa versa. An sx lock is considered related to a sleep. (i.e. may be long term) and as such must not be taken out when holding a mutex, which must not sleep. > >> >> -Ed >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From nikhil.rao at intel.com Mon Aug 18 21:11:59 2008 From: nikhil.rao at intel.com (Rao, Nikhil) Date: Mon Aug 18 21:12:12 2008 Subject: Multiple page support In-Reply-To: <20080818120021.751FB106568E@hub.freebsd.org> References: <20080818120021.751FB106568E@hub.freebsd.org> Message-ID: <12A5C15467D5B94F8E0FF265D9498ADD0383F1CA@orsmsx419.amr.corp.intel.com> What is the current status of multiple page sizes for applications (4K and 2MB) in FreeBSD 8-CURRENT ? It is enabled by default for the amd64 arch and only available in the amd64 and i386 architectures. >From reading the source code, there is support for "reservations" as described in the original paper (http://www.cs.rice.edu/~jnavarro/papers/phdthesis.pdf) Is the feature implementation complete apart from bug fixes etc ? Couple of features that I am referring to 1) I haven't seen any code for the "population map" radix tree that is supposed to help with reservation preemption (It enables you to lazily update the reservation pointer in struct vm_page, but this pointer itself doesn't exist anyways) 2) The original paper describes modification to the paging daemon to handle fragmentation, are these modifications implemented ? 3) Say the hardware were able to support an additional page size, How easy would it be to add an additional page size ? Nikhil From rfrench at freebsd.org Mon Aug 18 21:13:43 2008 From: rfrench at freebsd.org (Ryan French) Date: Mon Aug 18 21:13:50 2008 Subject: Summer of Code is over!! Message-ID: <200808190913.40316.rfrench@freebsd.org> Hi all, As those of you involved in the Google Summer of Code know, today is the last day of coding for the project. However, I still have a lot to do on my implementation of MPLS, and will continue to work on this until it is working. I would like to say thank you to all of those who have helped me over the course of the program in trying to get this project up and running. With that in mind I have submitted the semi-finished code for trying to get sending and receiving of packets working. Unfortunately I have come up against a bit of a brick wall in terms of trying to figure out the exact inner workings of FreeBSD. At the moment, in theory at least, the sending and receiving of packets should work, however I am stuck as to how to integrate my code properly with the kernel. So far I have created a mpls_init which contains a netisr_register function, as well as inserted the appropriate code into the ether_demux function, but it still does not appear to be running the code when an MPLS packet is received. If anyone would like to look at the code and give me any feedback on how to improve it, or any ideas on how to get it working, it would be greatly appreciated, and I understand it is a very big ask of anyone to look through it, so I will thank you in advance for your time. Thank you for being such a great community and helping me get through this summer of code. No doubt you will be hearing from me on the mailing lists as I continue to try and get this project working, and possibly even move onto other projects. -Ryan French From simon at optinet.com Mon Aug 18 23:43:50 2008 From: simon at optinet.com (Simon) Date: Mon Aug 18 23:43:57 2008 Subject: Disk quotas out of sync Message-ID: <20080818234349.D342C8FC1E@mx1.freebsd.org> Hello All, I sent this to freebsd-questions but it went unanswered, hoping for better luck here. The issue I'm trying to resolve is this: Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas getting out of sync with the actual amount used. For example, a user with 100GB used disk space suddenly shows usage of only 80GB as if the data is gone, but it isn't. This forces me to run quotacheck -av often. Was something changed regarding quotas in 7.0-R? Nobody else noticed this issue? I have this issue across multiple, different hardware, servers running 7.0-R Thank you for any insight and help in advance! -Simon From unixmania at gmail.com Tue Aug 19 01:10:44 2008 From: unixmania at gmail.com (Carlos A. M. dos Santos) Date: Tue Aug 19 01:10:51 2008 Subject: Multiple page support In-Reply-To: <12A5C15467D5B94F8E0FF265D9498ADD0383F1CA@orsmsx419.amr.corp.intel.com> References: <20080818120021.751FB106568E@hub.freebsd.org> <12A5C15467D5B94F8E0FF265D9498ADD0383F1CA@orsmsx419.amr.corp.intel.com> Message-ID: On Mon, Aug 18, 2008 at 5:42 PM, Rao, Nikhil wrote: > > What is the current status of multiple page sizes for applications (4K > and 2MB) in FreeBSD 8-CURRENT ? It is enabled by default for the amd64 > arch and only available in the amd64 and i386 architectures. I just saw this message in -current that may interest you: http://lists.freebsd.org/pipermail/freebsd-current/2008-August/087605.html -- If you think things can't get worse it's probably only because you lack sufficient imagination. From grafan at gmail.com Tue Aug 19 02:05:51 2008 From: grafan at gmail.com (Rong-en Fan) Date: Tue Aug 19 02:06:02 2008 Subject: Disk quotas out of sync In-Reply-To: <20080818234349.D342C8FC1E@mx1.freebsd.org> References: <20080818234349.D342C8FC1E@mx1.freebsd.org> Message-ID: <6eb82e0808181836p2f5bc5cfoa0072e8f00e34a5b@mail.gmail.com> On Tue, Aug 19, 2008 at 7:16 AM, Simon wrote: > Hello All, > > I sent this to freebsd-questions but it went unanswered, hoping for better > luck here. The issue I'm trying to resolve is this: > > Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas > getting out of sync with the actual amount used. For example, a user with > 100GB used disk space suddenly shows usage of only 80GB as if the data > is gone, but it isn't. This forces me to run quotacheck -av often. Was > something changed regarding quotas in 7.0-R? Nobody else noticed this issue? > I have this issue across multiple, different hardware, servers running 7.0-R > > Thank you for any insight and help in advance! Are you running SMP? Quotas in 7.x and 6.x (since this May) become MPSAFE. I'm CC'ing kib@ who wrote the patch, maybe he has some insights. Regards, Rong-En Fan From simon at optinet.com Tue Aug 19 03:54:33 2008 From: simon at optinet.com (Simon) Date: Tue Aug 19 03:54:39 2008 Subject: Disk quotas out of sync In-Reply-To: <6eb82e0808181836p2f5bc5cfoa0072e8f00e34a5b@mail.gmail.com> Message-ID: <20080819035432.975AF8FC1D@mx1.freebsd.org> Yes, I'm running SMP on all machines, version 7.0-R-p2 (amd64 on some). No group quotas, just user. Thanks, Simon On Tue, 19 Aug 2008 09:36:43 +0800, Rong-en Fan wrote: >On Tue, Aug 19, 2008 at 7:16 AM, Simon wrote: >> Hello All, >> >> I sent this to freebsd-questions but it went unanswered, hoping for better >> luck here. The issue I'm trying to resolve is this: >> >> Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas >> getting out of sync with the actual amount used. For example, a user with >> 100GB used disk space suddenly shows usage of only 80GB as if the data >> is gone, but it isn't. This forces me to run quotacheck -av often. Was >> something changed regarding quotas in 7.0-R? Nobody else noticed this issue? >> I have this issue across multiple, different hardware, servers running 7.0-R >> >> Thank you for any insight and help in advance! >Are you running SMP? Quotas in 7.x and 6.x (since this May) become MPSAFE. >I'm CC'ing kib@ who wrote the patch, maybe he has some insights. >Regards, >Rong-En Fan From rkramer at mweb.com Tue Aug 19 06:36:36 2008 From: rkramer at mweb.com (Rudi Kramer - MWEB) Date: Tue Aug 19 06:36:44 2008 Subject: Recommend literature for beginner programer Message-ID: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> Hello, I've been using FreeBSD for the last couple of years as an admin and I would like to take the next step and learn how to write code, specifically with FreeBSD in mind. Can anyone recommend some good literature to get me started? Thanks Rudi From asmodai at in-nomine.org Tue Aug 19 07:02:56 2008 From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven) Date: Tue Aug 19 07:03:04 2008 Subject: Recommend literature for beginner programer In-Reply-To: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> References: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> Message-ID: <20080819070253.GH87062@nexus.in-nomine.org> -On [20080819 08:36], Rudi Kramer - MWEB (rkramer@mweb.com) wrote: >I've been using FreeBSD for the last couple of years as an admin and I >would like to take the next step and learn how to write code, >specifically with FreeBSD in mind. What is your goal? I am of the opinion that, unless you want to dig into the kernel and such things, your time might be better spent learning a language like Python. Otherwise, if you want to dig into FreeBSD source code then you automatically come to C. So depending on your goal the books differ. -- Jeroen Ruigrok van der Werven / asmodai ????? ?????? ??? ?? ?????? http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B The quieter you become, the more you are able to hear... From mpp at mppsystems.com Tue Aug 19 07:30:36 2008 From: mpp at mppsystems.com (Mike Pritchard) Date: Tue Aug 19 07:30:43 2008 Subject: Disk quotas out of sync In-Reply-To: <20080818234349.D342C8FC1E@mx1.freebsd.org> References: <20080818234349.D342C8FC1E@mx1.freebsd.org> Message-ID: <20080819064646.GA7787@mppsystems.com> On Mon, Aug 18, 2008 at 07:16:53PM -0400, Simon wrote: > Hello All, > > I sent this to freebsd-questions but it went unanswered, hoping for better > luck here. The issue I'm trying to resolve is this: > > Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas > getting out of sync with the actual amount used. For example, a user with > 100GB used disk space suddenly shows usage of only 80GB as if the data > is gone, but it isn't. This forces me to run quotacheck -av often. Was > something changed regarding quotas in 7.0-R? Nobody else noticed this issue? > I have this issue across multiple, different hardware, servers running 7.0-R > > Thank you for any insight and help in advance! > > -Simon What do your quota options look like in rc.conf? And what does the fstab look like for the file system in question? -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787) From rkramer at mweb.com Tue Aug 19 07:36:19 2008 From: rkramer at mweb.com (Rudi Kramer - MWEB) Date: Tue Aug 19 07:36:27 2008 Subject: Recommend literature for beginner programer References: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> <20080819070253.GH87062@nexus.in-nomine.org> Message-ID: <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> > Ruigrok van der Werven > > What is your goal? I learn how FreeBSD is put together and eventually contribute code to the base. Rudi From asmodai at in-nomine.org Tue Aug 19 08:00:51 2008 From: asmodai at in-nomine.org (Jeroen Ruigrok van der Werven) Date: Tue Aug 19 08:00:58 2008 Subject: Recommend literature for beginner programer In-Reply-To: <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> References: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> <20080819070253.GH87062@nexus.in-nomine.org> <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> Message-ID: <20080819080049.GI87062@nexus.in-nomine.org> -On [20080819 09:37], Rudi Kramer - MWEB (rkramer@mweb.com) wrote: >I learn how FreeBSD is put together and eventually contribute code to >the base. So C it is. http://home.netcom.com/~tjensen/ptr/pointers.htm is a good reference for arrays and pointers. C: A Reference Manual is a good reference: http://www.amazon.com/dp/013089592X/ Programming in C (3rd edition) gets good reviews: http://www.amazon.com/dp/0672326663/ C Primer PLus (5th Edition) also looks like a good book: http://www.amazon.com/dp/0672326965/ People might say "get the K&R book", but I think that's outdated and the text itself is not the easiest, in my opinion. -- Jeroen Ruigrok van der Werven / asmodai ????? ?????? ??? ?? ?????? http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B These days get so long and I got nothing to do... From simon at optinet.com Tue Aug 19 12:38:00 2008 From: simon at optinet.com (Simon) Date: Tue Aug 19 12:38:07 2008 Subject: Disk quotas out of sync In-Reply-To: <20080819064646.GA7787@mppsystems.com> Message-ID: <20080819123800.1A4EC8FC26@mx1.freebsd.org> fstab: /dev/mfid0s2d /web1 ufs rw,userquota 2 2 rc.conf: enable_quotas="YES" check_quotas="NO" I always had it this way and it always worked until 7.x -Simon On Tue, 19 Aug 2008 01:46:46 -0500, Mike Pritchard wrote: >On Mon, Aug 18, 2008 at 07:16:53PM -0400, Simon wrote: >> Hello All, >> >> I sent this to freebsd-questions but it went unanswered, hoping for better >> luck here. The issue I'm trying to resolve is this: >> >> Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas >> getting out of sync with the actual amount used. For example, a user with >> 100GB used disk space suddenly shows usage of only 80GB as if the data >> is gone, but it isn't. This forces me to run quotacheck -av often. Was >> something changed regarding quotas in 7.0-R? Nobody else noticed this issue? >> I have this issue across multiple, different hardware, servers running 7.0-R >> >> Thank you for any insight and help in advance! >> >> -Simon >What do your quota options look like in rc.conf? And what does the >fstab look like for the file system in question? >-- >Mike Pritchard >mpp @ FreeBSD.org >"If tyranny and oppression come to this land, it will be in the guise >of fighting a foreign enemy." - James Madison (1787) From kostikbel at gmail.com Tue Aug 19 13:03:48 2008 From: kostikbel at gmail.com (Kostik Belousov) Date: Tue Aug 19 13:03:54 2008 Subject: Disk quotas out of sync In-Reply-To: <20080819035432.975AF8FC1D@mx1.freebsd.org> References: <6eb82e0808181836p2f5bc5cfoa0072e8f00e34a5b@mail.gmail.com> <20080819035432.975AF8FC1D@mx1.freebsd.org> Message-ID: <20080819130341.GY1803@deviant.kiev.zoral.com.ua> On Mon, Aug 18, 2008 at 11:54:15PM -0400, Simon wrote: > > Yes, I'm running SMP on all machines, version 7.0-R-p2 (amd64 on some). > No group quotas, just user. The questions to you: 1. Are inode counts for users coincide with quota report ? 2. How did you compared "actual usage" with the usage reported by quota subsystem ? > > Thanks, > Simon > > On Tue, 19 Aug 2008 09:36:43 +0800, Rong-en Fan wrote: > > >On Tue, Aug 19, 2008 at 7:16 AM, Simon wrote: > >> Hello All, > >> > >> I sent this to freebsd-questions but it went unanswered, hoping for better > >> luck here. The issue I'm trying to resolve is this: > >> > >> Ever since I went from 6.x to 7.0-R I have started experiencing disk quotas > >> getting out of sync with the actual amount used. For example, a user with > >> 100GB used disk space suddenly shows usage of only 80GB as if the data > >> is gone, but it isn't. This forces me to run quotacheck -av often. Was > >> something changed regarding quotas in 7.0-R? Nobody else noticed this issue? > >> I have this issue across multiple, different hardware, servers running 7.0-R > >> > >> Thank you for any insight and help in advance! > > >Are you running SMP? Quotas in 7.x and 6.x (since this May) become MPSAFE. > >I'm CC'ing kib@ who wrote the patch, maybe he has some insights. > > >Regards, > >Rong-En Fan > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080819/d3902e54/attachment.pgp From simon at optinet.com Tue Aug 19 13:24:22 2008 From: simon at optinet.com (Simon) Date: Tue Aug 19 13:24:28 2008 Subject: Disk quotas out of sync In-Reply-To: <20080819130341.GY1803@deviant.kiev.zoral.com.ua> Message-ID: <20080819132421.D05328FC24@mx1.freebsd.org> Yes, the inodes seem to be in sync. When I run quotacheck -av only blocks get fixed or at least that is what I see. Here is an example repquota -a output before 'quotacheck -av': Block limits File limits User used soft hard grace used soft hard grace john -- 135426892 175000000 175000000 - 183785 500000 500000 - after quotacheck: /web1: john fixed (user): blocks 270853784 -> 326298284 Block limits File limits User used soft hard grace used soft hard grace john -- 163149142 175000000 175000000 - 183785 500000 500000 - -Simon On Tue, 19 Aug 2008 16:03:41 +0300, Kostik Belousov wrote: >On Mon, Aug 18, 2008 at 11:54:15PM -0400, Simon wrote: >>=20 >> Yes, I'm running SMP on all machines, version 7.0-R-p2 (amd64 on some). >> No group quotas, just user. >The questions to you: >1. Are inode counts for users coincide with quota report ? >2. How did you compared "actual usage" with the usage reported by > quota subsystem ? >>=20 >> Thanks, >> Simon >>=20 >> On Tue, 19 Aug 2008 09:36:43 +0800, Rong-en Fan wrote: >>=20 >> >On Tue, Aug 19, 2008 at 7:16 AM, Simon wrote: >> >> Hello All, >> >> >> >> I sent this to freebsd-questions but it went unanswered, hoping for be= >tter >> >> luck here. The issue I'm trying to resolve is this: >> >> >> >> Ever since I went from 6.x to 7.0-R I have started experiencing disk q= >uotas >> >> getting out of sync with the actual amount used. For example, a user w= >ith >> >> 100GB used disk space suddenly shows usage of only 80GB as if the data >> >> is gone, but it isn't. This forces me to run quotacheck -av often. Was >> >> something changed regarding quotas in 7.0-R? Nobody else noticed this = >issue? >> >> I have this issue across multiple, different hardware, servers running= > 7.0-R >> >> >> >> Thank you for any insight and help in advance! >>=20 >> >Are you running SMP? Quotas in 7.x and 6.x (since this May) become MPSAF= >E. >> >I'm CC'ing kib@ who wrote the patch, maybe he has some insights. >>=20 >> >Regards, >> >Rong-En Fan >>=20 >>=20 >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From pb at ludd.ltu.se Tue Aug 19 13:05:32 2008 From: pb at ludd.ltu.se (Peter B) Date: Tue Aug 19 14:16:06 2008 Subject: USB Video class Message-ID: <200808191305.m7JD5Tbl007123@brother.ludd.ltu.se> Is there any ongoing project towards USB Video class support in FreeBSD ..? (Looking at the Asus eee builtin webcam 0x04F2 (CHICONY) 0xB071) Some links: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/ uvideo.c http://developer.berlios.de/projects/linux-uvc http://www.usb.org/developers/devclass_docs/USB_Video_Class_1_1.zip From emaste at freebsd.org Tue Aug 19 15:27:10 2008 From: emaste at freebsd.org (Ed Maste) Date: Tue Aug 19 15:27:17 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: <48A9C1B0.5010805@elischer.org> References: <200808181754.18812.max@love2party.net> <20080818162411.GA77460@sandvine.com> <48A9BFED.604@elischer.org> <48A9C1B0.5010805@elischer.org> Message-ID: <20080819152607.GA44331@sandvine.com> On Mon, Aug 18, 2008 at 11:38:40AM -0700, Julian Elischer wrote: > >Ed Maste wrote: > >>Ahh, it seems ups' commit of rmlocks changed the "You have: sx_lock, > >>You want: Slp_mtx" case from no to ok (in r173444). > > Ignore me.. I was reading the table backwards.. of course if you have > an sx you can still take out a mutex, but not visa versa. Yep, and ups' r173444 change didn't affect this at all, it just corrected the table. If I don't hear otherwise I'll merge the changes to the table to 7 sometime soon: You have: You want: Spin_mtx Slp_mtx sx_lock rw_lock sleep - SPIN mutex ok no no no no-3 + SPIN mutex ok-1 no no no no-3 Sleep mutex ok ok-1 no ok no-3 - sx_lock ok no ok-2 no ok-4 + sx_lock ok ok ok-2 ok ok-4 rw_lock ok ok no ok-2 no-3 Have SPIN / want SPIN adds the "Recursion is defined per lock" footnote. Have sx / want Slp & have sx / want rw change from no to ok. - Ed From Alexander at Leidinger.net Tue Aug 19 15:53:48 2008 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue Aug 19 17:07:10 2008 Subject: USB Video class In-Reply-To: <200808191305.m7JD5Tbl007123@brother.ludd.ltu.se> References: <200808191305.m7JD5Tbl007123@brother.ludd.ltu.se> Message-ID: <20080819175332.482767np3ciixag4@webmail.leidinger.net> Quoting "Peter B" (from Tue, 19 Aug 2008 15:05:29 +0200 (MEST)): > > Is there any ongoing project towards USB Video class support in FreeBSD ..? This is better asked on usb@ (CCed). I'm not aware of such an effort, feel free to start it (you better wait some days until the new USB stack hits CVS). Bye, Alexander. > (Looking at the Asus eee builtin webcam 0x04F2 (CHICONY) 0xB071) > > Some links: > http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/usb/ uvideo.c > http://developer.berlios.de/projects/linux-uvc > http://www.usb.org/developers/devclass_docs/USB_Video_Class_1_1.zip > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > -- While you don't greatly need the outside world, it's still very reassuring to know that it's still there. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From julian at elischer.org Tue Aug 19 18:16:43 2008 From: julian at elischer.org (Julian Elischer) Date: Tue Aug 19 18:16:50 2008 Subject: Acquiring a mtx after an sx lock In-Reply-To: <20080819152607.GA44331@sandvine.com> References: <200808181754.18812.max@love2party.net> <20080818162411.GA77460@sandvine.com> <48A9BFED.604@elischer.org> <48A9C1B0.5010805@elischer.org> <20080819152607.GA44331@sandvine.com> Message-ID: <48AB0E12.8030607@elischer.org> Ed Maste wrote: > On Mon, Aug 18, 2008 at 11:38:40AM -0700, Julian Elischer wrote: > >>> Ed Maste wrote: >>>> Ahh, it seems ups' commit of rmlocks changed the "You have: sx_lock, >>>> You want: Slp_mtx" case from no to ok (in r173444). >> Ignore me.. I was reading the table backwards.. of course if you have >> an sx you can still take out a mutex, but not visa versa. > > Yep, and ups' r173444 change didn't affect this at all, it just > corrected the table. > > If I don't hear otherwise I'll merge the changes to the table to 7 > sometime soon: > > You have: You want: Spin_mtx Slp_mtx sx_lock rw_lock sleep > - SPIN mutex ok no no no no-3 > + SPIN mutex ok-1 no no no no-3 > Sleep mutex ok ok-1 no ok no-3 > - sx_lock ok no ok-2 no ok-4 > + sx_lock ok ok ok-2 ok ok-4 > rw_lock ok ok no ok-2 no-3 > > Have SPIN / want SPIN adds the "Recursion is defined per lock" footnote. > > Have sx / want Slp & have sx / want rw change from no to ok. I agree > > - Ed > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From jrytoung at gmail.com Tue Aug 19 20:15:20 2008 From: jrytoung at gmail.com (Jerry Toung) Date: Tue Aug 19 20:15:26 2008 Subject: pkg_add on 64bits kernel w/ options MAC Message-ID: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> Hi List, I am running into a weird issue. On a 6.2 stable, 32bits built with options MAC, I can run pkg_add of anything. But a 6.2 stable, 64bits built with MAC won't let me do pkg_add. If anybody has an input, please advise. Below is the output on the 64 bits machine: net3# pkg_add test.tbz +CONTENTS: Can't update time for +CONTENTS: Operation not permitted pkg_add: tar extract of /wr/home/webmgr/test.tbz failed! pkg_add: unable to extract table of contents file from '/wr/home/webmgr/test.tbz' - not a package? net3# net3# tar xvf test.tbz x +CONTENTS: Can't update time for +CONTENTS: Operation not permitted x +COMMENT: Can't update time for +COMMENT: Operation not permitted x +DESC: Can't update time for +DESC: Operation not permitted x +DISPLAY: Can't update time for +DISPLAY: Operation not permitted x usr/local/bin/sudo: Can't update time for usr/local/bin/sudo: Operation not permitted x usr/local/man/man8/sudo.8: Can't update time for usr/local/man/man8/sudo.8: Operation not permitted x usr/local/man/man8/visudo.8: Can't update time for usr/local/man/man8/visudo.8: Operation not permitted x usr/local/man/man5/sudoers.5 x usr/local/sbin/visudo: Can't update time for usr/local/sbin/visudo: Operation not permitted x usr/local/libexec/sudo_noexec.so: Can't update time for usr/local/libexec/sudo_noexec.so: Operation not permitted x usr/local/libexec/sudo_noexec.la: Can't update time for usr/local/libexec/ sudo_noexec.la: Operation not permitted x etc/sudoers: Can't update time for etc/sudoers: Operation not permitted net3# uname -a FreeBSD net3 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Aug 5 15:10:45 PDT 2008 root@test:/usr/obj/usr/src/sys/MYBD amd64 thanks, Jerry From rwatson at FreeBSD.org Tue Aug 19 20:26:36 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Tue Aug 19 20:26:44 2008 Subject: pkg_add on 64bits kernel w/ options MAC In-Reply-To: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> References: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> Message-ID: On Tue, 19 Aug 2008, Jerry Toung wrote: > I am running into a weird issue. On a 6.2 stable, 32bits built with options > MAC, I can run pkg_add of anything. But a 6.2 stable, 64bits built with MAC > won't let me do pkg_add. If anybody has an input, please advise. Below is > the output on the 64 bits machine: Sounds like a bug of some sort. Could you send the output of "sysctl security.mac"? Also, if you could use ktrace to confirm which system calls are returning EACCES/EPERM leading to the warnings, that would also be helpful. Robert N M Watson Computer Laboratory University of Cambridge > > net3# pkg_add test.tbz > +CONTENTS: Can't update time for +CONTENTS: Operation not permitted > pkg_add: tar extract of /wr/home/webmgr/test.tbz failed! > pkg_add: unable to extract table of contents file from > '/wr/home/webmgr/test.tbz' - not a package? > net3# > > net3# tar xvf test.tbz > x +CONTENTS: Can't update time for +CONTENTS: Operation not permitted > x +COMMENT: Can't update time for +COMMENT: Operation not permitted > x +DESC: Can't update time for +DESC: Operation not permitted > x +DISPLAY: Can't update time for +DISPLAY: Operation not permitted > x usr/local/bin/sudo: Can't update time for usr/local/bin/sudo: Operation > not permitted > x usr/local/man/man8/sudo.8: Can't update time for > usr/local/man/man8/sudo.8: Operation not permitted > x usr/local/man/man8/visudo.8: Can't update time for > usr/local/man/man8/visudo.8: Operation not permitted > x usr/local/man/man5/sudoers.5 > x usr/local/sbin/visudo: Can't update time for usr/local/sbin/visudo: > Operation not permitted > x usr/local/libexec/sudo_noexec.so: Can't update time for > usr/local/libexec/sudo_noexec.so: Operation not permitted > x usr/local/libexec/sudo_noexec.la: Can't update time for > usr/local/libexec/sudo_noexec.la: Operation not permitted > x etc/sudoers: Can't update time for etc/sudoers: Operation not permitted > > net3# uname -a > FreeBSD net3 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Aug? 5 15:10:45 PDT > 2008???? root@test:/usr/obj/usr/src/sys/MYBD? amd64 > > thanks, > Jerry > > From rwatson at FreeBSD.org Tue Aug 19 20:27:15 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Tue Aug 19 20:27:21 2008 Subject: pkg_add on 64bits kernel w/ options MAC In-Reply-To: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> References: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> Message-ID: On Tue, 19 Aug 2008, Jerry Toung wrote: > I am running into a weird issue. On a 6.2 stable, 32bits built with options > MAC, I can run pkg_add of anything. But a 6.2 stable, 64bits built with MAC > won't let me do pkg_add. If anybody has an input, please advise. Below is > the output on the 64 bits machine: Also -- if you don't yet have an open PR, could you create one and forward me the PR receipt so I can take ownership of it? Robert N M Watson Computer Laboratory University of Cambridge > > net3# pkg_add test.tbz > +CONTENTS: Can't update time for +CONTENTS: Operation not permitted > pkg_add: tar extract of /wr/home/webmgr/test.tbz failed! > pkg_add: unable to extract table of contents file from > '/wr/home/webmgr/test.tbz' - not a package? > net3# > > net3# tar xvf test.tbz > x +CONTENTS: Can't update time for +CONTENTS: Operation not permitted > x +COMMENT: Can't update time for +COMMENT: Operation not permitted > x +DESC: Can't update time for +DESC: Operation not permitted > x +DISPLAY: Can't update time for +DISPLAY: Operation not permitted > x usr/local/bin/sudo: Can't update time for usr/local/bin/sudo: Operation > not permitted > x usr/local/man/man8/sudo.8: Can't update time for > usr/local/man/man8/sudo.8: Operation not permitted > x usr/local/man/man8/visudo.8: Can't update time for > usr/local/man/man8/visudo.8: Operation not permitted > x usr/local/man/man5/sudoers.5 > x usr/local/sbin/visudo: Can't update time for usr/local/sbin/visudo: > Operation not permitted > x usr/local/libexec/sudo_noexec.so: Can't update time for > usr/local/libexec/sudo_noexec.so: Operation not permitted > x usr/local/libexec/sudo_noexec.la: Can't update time for > usr/local/libexec/sudo_noexec.la: Operation not permitted > x etc/sudoers: Can't update time for etc/sudoers: Operation not permitted > > net3# uname -a > FreeBSD net3 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Aug? 5 15:10:45 PDT > 2008???? root@test:/usr/obj/usr/src/sys/MYBD? amd64 > > thanks, > Jerry > > From jrytoung at gmail.com Tue Aug 19 23:14:42 2008 From: jrytoung at gmail.com (Jerry Toung) Date: Tue Aug 19 23:14:49 2008 Subject: pkg_add on 64bits kernel w/ options MAC In-Reply-To: References: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> Message-ID: <86068e730808191614m66b72cb1y8786b8a7b6510df2@mail.gmail.com> On Tue, Aug 19, 2008 at 1:26 PM, Robert Watson wrote: > > > Sounds like a bug of some sort. Could you send the output of "sysctl > security.mac"? Also, if you could use ktrace to confirm which system calls > are returning EACCES/EPERM leading to the warnings, that would also be > helpful. > > I will file a PR later on. In the mean time here are the outputs you were looking for: security.mac.max_slots: 4 security.mac.enforce_network: 1 security.mac.enforce_pipe: 1 security.mac.enforce_posix_sem: 1 security.mac.enforce_suid: 1 security.mac.mmap_revocation_via_cow: 0 security.mac.mmap_revocation: 1 security.mac.enforce_vm: 1 security.mac.enforce_process: 1 security.mac.enforce_socket: 1 security.mac.enforce_system: 1 security.mac.enforce_kld: 1 security.mac.enforce_sysv_msg: 1 security.mac.enforce_sysv_sem: 1 security.mac.enforce_sysv_shm: 1 security.mac.enforce_fs: 1 bsd64-21# kdump -f ktrace.out 1045 ktrace RET ktrace 0 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) 1045 ktrace RET execve -1 errno 2 No such file or directory 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) 1045 ktrace RET execve -1 errno 2 No such file or directory 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) 1045 pkg_add RET execve 0 1045 pkg_add CALL mmap(0,0x1e40,0x3,0x1000,0xffffffff,0,0) 1045 pkg_add RET mmap 5443584/0x800531000 1045 pkg_add CALL munmap(0x800531000,0x1e40) 1045 pkg_add RET munmap 0 1045 pkg_add CALL __sysctl(0x7fffffffe930,0x2,0x800639180,0x7fffffffe928,0,0) 1045 pkg_add RET __sysctl 0 1045 pkg_add CALL mmap(0,0x8000,0x3,0x1002,0xffffffff,0,0) 1045 pkg_add RET mmap 5443584/0x800531000 1045 pkg_add CALL issetugid 1045 pkg_add RET issetugid 0 1045 pkg_add CALL open(0x80052eff0,0,0x1b6) 1045 pkg_add RET open -1 errno 2 No such file or directory 1045 pkg_add CALL open(0x80052e1a8,0,0) 1045 pkg_add RET open 3 1045 pkg_add CALL read(0x3,0x7fffffffe8d0,0x80) 1045 pkg_add RET read 128/0x80 1045 pkg_add CALL lseek(0x3,0,0x80,0) 1045 pkg_add RET lseek 128/0x80 1045 pkg_add CALL read(0x3,0x800535000,0x3c) 1045 pkg_add RET read 60/0x3c 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access -1 errno 2 No such file or directory 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL open(0x8005320c0,0,0x800639060) 1045 pkg_add RET open 3 1045 pkg_add CALL fstat(0x3,0x7fffffffe8e0) 1045 pkg_add RET fstat 0 1045 pkg_add CALL read(0x3,0x800638040,0x1000) 1045 pkg_add RET read 4096/0x1000 1045 pkg_add CALL mmap(0,0x10e000,0x5,0x20002,0x3,0,0) 1045 pkg_add RET mmap 6541312/0x80063d000 1045 pkg_add CALL mprotect(0x800648000,0x1000,0x7) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mprotect(0x800648000,0x1000,0x5) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mmap(0x800749000,0x2000,0x3,0x12,0x3,0,0xc000) 1045 pkg_add RET mmap 7639040/0x800749000 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL open(0x800532120,0,0x6c) 1045 pkg_add RET open 3 1045 pkg_add CALL fstat(0x3,0x7fffffffe8e0) 1045 pkg_add RET fstat 0 1045 pkg_add CALL read(0x3,0x800638040,0x1000) 1045 pkg_add RET read 4096/0x1000 1045 pkg_add CALL mmap(0,0x10c000,0x5,0x20002,0x3,0,0) 1045 pkg_add RET mmap 7647232/0x80074b000 1045 pkg_add CALL mprotect(0x800755000,0x1000,0x7) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mprotect(0x800755000,0x1000,0x5) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mmap(0x800856000,0x1000,0x3,0x12,0x3,0,0xb000) 1045 pkg_add RET mmap 8740864/0x800856000 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access -1 errno 2 No such file or directory 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL open(0x800532140,0,0x75) 1045 pkg_add RET open 3 1045 pkg_add CALL fstat(0x3,0x7fffffffe8e0) 1045 pkg_add RET fstat 0 1045 pkg_add CALL read(0x3,0x800638040,0x1000) 1045 pkg_add RET read 4096/0x1000 1045 pkg_add CALL mmap(0,0x138000,0x5,0x20002,0x3,0,0) 1045 pkg_add RET mmap 8744960/0x800857000 1045 pkg_add CALL mprotect(0x800886000,0x1000,0x7) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mprotect(0x800886000,0x1000,0x5) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mmap(0x800987000,0x8000,0x3,0x12,0x3,0,0x30000) 1045 pkg_add RET mmap 9990144/0x800987000 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL open(0x800532180,0,0x6c) 1045 pkg_add RET open 3 1045 pkg_add CALL fstat(0x3,0x7fffffffe8e0) 1045 pkg_add RET fstat 0 1045 pkg_add CALL read(0x3,0x800638040,0x1000) 1045 pkg_add RET read 4096/0x1000 1045 pkg_add CALL mmap(0,0x247000,0x5,0x20002,0x3,0,0) 1045 pkg_add RET mmap 10022912/0x80098f000 1045 pkg_add CALL mprotect(0x800a9b000,0x1000,0x7) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mprotect(0x800a9b000,0x1000,0x5) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mmap(0x800b9c000,0x37000,0x3,0x12,0x3,0,0x10d000) 1045 pkg_add RET mmap 12173312/0x800b9c000 1045 pkg_add CALL mmap(0x800bd3000,0x3000,0x3,0x1012,0xffffffff,0,0) 1045 pkg_add RET mmap 12398592/0x800bd3000 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL open(0x8005321a0,0,0x2e) 1045 pkg_add RET open 3 1045 pkg_add CALL fstat(0x3,0x7fffffffe8e0) 1045 pkg_add RET fstat 0 1045 pkg_add CALL read(0x3,0x800638040,0x1000) 1045 pkg_add RET read 4096/0x1000 1045 pkg_add CALL mmap(0,0x20f000,0x5,0x20002,0x3,0,0) 1045 pkg_add RET mmap 12410880/0x800bd6000 1045 pkg_add CALL mprotect(0x800cb1000,0x1000,0x7) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mprotect(0x800cb1000,0x1000,0x5) 1045 pkg_add RET mprotect 0 1045 pkg_add CALL mmap(0x800db1000,0x1b000,0x3,0x12,0x3,0,0xdb000) 1045 pkg_add RET mmap 14356480/0x800db1000 1045 pkg_add CALL mmap(0x800dcc000,0x19000,0x3,0x1012,0xffffffff,0,0) 1045 pkg_add RET mmap 14467072/0x800dcc000 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access -1 errno 2 No such file or directory 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL access(0x800536000,0) 1045 pkg_add RET access 0 1045 pkg_add CALL sysarch(0x81,0x7fffffffe9a0) 1045 pkg_add RET sysarch 0 1045 pkg_add CALL mmap(0,0x890,0x3,0x1000,0xffffffff,0,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0x890) 1045 pkg_add RET munmap 0 1045 pkg_add CALL mmap(0,0xae0,0x3,0x1000,0xffffffff,0,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0xae0) 1045 pkg_add RET munmap 0 1045 pkg_add CALL mmap(0,0x650,0x3,0x1000,0xffffffff,0x800000000,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0x650) 1045 pkg_add RET munmap 0 1045 pkg_add CALL mmap(0,0x22e0,0x3,0x1000,0xffffffff,0x800000000,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0x22e0) 1045 pkg_add RET munmap 0 1045 pkg_add CALL mmap(0,0xad70,0x3,0x1000,0xffffffff,0x800000000,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0xad70) 1045 pkg_add RET munmap 0 1045 pkg_add CALL mmap(0,0xb180,0x3,0x1000,0xffffffff,0x800000000,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL munmap(0x800539000,0xb180) 1045 pkg_add RET munmap 0 1045 pkg_add CALL sigprocmask(0x1,0x800637f40,0x7fffffffe960) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL sigprocmask(0x3,0x800637f50,0) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL open(0x40b965,0,0x1b6) 1045 pkg_add RET open -1 errno 2 No such file or directory 1045 pkg_add CALL lstat(0x7fffffffee40,0x7fffffffe250) 1045 pkg_add RET lstat 0 1045 pkg_add CALL __getcwd(0x510f00,0x400) 1045 pkg_add RET __getcwd 0 1045 pkg_add CALL lstat(0x510f00,0x7fffffffe220) 1045 pkg_add RET lstat 0 1045 pkg_add CALL umask(0x12) 1045 pkg_add RET umask 18/0x12 1045 pkg_add CALL sigaction(0x2,0x7fffffffe280,0x7fffffffe260) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigaction(0x1,0x7fffffffe280,0x7fffffffe260) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL stat(0x7fffffffde80,0x7fffffffd600) 1045 pkg_add RET stat 0 1045 pkg_add CALL stat(0x40bb0c,0x7fffffffbd10) 1045 pkg_add RET stat 0 1045 pkg_add CALL statfs(0x40bb0c,0x7fffffffbb20) 1045 pkg_add RET statfs 0 1045 pkg_add CALL gettimeofday(0x7fffffffbb70,0) 1045 pkg_add RET gettimeofday 0 1045 pkg_add CALL getpid 1045 pkg_add RET getpid 1045/0x415 1045 pkg_add CALL open(0x800cb135f,0,0) 1045 pkg_add RET open 3 1045 pkg_add CALL read(0x3,0x7fffffffbb84,0x6c) 1045 pkg_add RET read 108/0x6c 1045 pkg_add CALL close(0x3) 1045 pkg_add RET close 0 1045 pkg_add CALL stat(0x7fffffffda80,0x7fffffffbc40) 1045 pkg_add RET stat 0 1045 pkg_add CALL mkdir(0x7fffffffda80,0x1c0) 1045 pkg_add RET mkdir 0 1045 pkg_add CALL chmod(0x7fffffffda80,0x1c0) 1045 pkg_add RET chmod 0 1045 pkg_add CALL statfs(0x7fffffffda80,0x7fffffffbb20) 1045 pkg_add RET statfs 0 1045 pkg_add CALL __getcwd(0x510220,0x400) 1045 pkg_add RET __getcwd 0 1045 pkg_add CALL chdir(0x7fffffffda80) 1045 pkg_add RET chdir 0 1045 pkg_add CALL readlink(0x800caa841,0x7fffffffbcf0,0x3f) 1045 pkg_add RET readlink -1 errno 2 No such file or directory 1045 pkg_add CALL issetugid 1045 pkg_add RET issetugid 0 1045 pkg_add CALL mmap(0,0x1000,0x3,0x1002,0xffffffff,0x800000000,0) 1045 pkg_add RET mmap 5476352/0x800539000 1045 pkg_add CALL break(0x545000) 1045 pkg_add RET break 0 1045 pkg_add CALL break(0x546000) 1045 pkg_add RET break 0 1045 pkg_add CALL break(0x547000) 1045 pkg_add RET break 0 1045 pkg_add CALL break(0x548000) 1045 pkg_add RET break 0 1045 pkg_add CALL __sysctl(0x7fffffffbc08,0x2,0x7fffffffbbfc,0x7fffffffbc00,0,0) 1045 pkg_add RET __sysctl 0 1045 pkg_add CALL break(0x588000) 1045 pkg_add RET break 0 1045 pkg_add CALL sigaction(0x2,0x7fffffffbbe0,0x7fffffffbbc0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigaction(0x3,0x7fffffffbbe0,0x7fffffffbba0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigprocmask(0x1,0x7fffffffbb90,0x7fffffffbb80) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL fork 1045 pkg_add RET fork 1046/0x416 1045 pkg_add CALL wait4(0x416,0x7fffffffbb7c,0,0) 1045 pkg_add RET wait4 1046/0x416 1045 pkg_add CALL sigaction(0x2,0x7fffffffbbc0,0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigaction(0x3,0x7fffffffbba0,0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigprocmask(0x3,0x7fffffffbb80,0) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL break(0x558000) 1045 pkg_add RET break 0 1045 pkg_add CALL write(0x2,0x7fffffffb4a0,0x9) 1045 pkg_add RET write 9 1045 pkg_add CALL write(0x2,0x7fffffffb580,0x25) 1045 pkg_add RET write 37/0x25 1045 pkg_add CALL write(0x2,0x800db7e87,0x1) 1045 pkg_add RET write 1 1045 pkg_add CALL write(0x2,0x7fffffffb520,0x9) 1045 pkg_add RET write 9 1045 pkg_add CALL write(0x2,0x7fffffffb600,0x4f) 1045 pkg_add RET write 79/0x4f 1045 pkg_add CALL write(0x2,0x800db7e87,0x1) 1045 pkg_add RET write 1 1045 pkg_add CALL sigaction(0x2,0x7fffffffbd70,0x7fffffffbd50) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL chdir(0x510220) 1045 pkg_add RET chdir 0 1045 pkg_add CALL __sysctl(0x7fffffffbc78,0x2,0x7fffffffbc6c,0x7fffffffbc70,0,0) 1045 pkg_add RET __sysctl 0 1045 pkg_add CALL break(0x598000) 1045 pkg_add RET break 0 1045 pkg_add CALL sigaction(0x2,0x7fffffffbc50,0x7fffffffbc30) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigaction(0x3,0x7fffffffbc50,0x7fffffffbc10) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigprocmask(0x1,0x7fffffffbc00,0x7fffffffbbf0) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL fork 1045 pkg_add RET fork 1048/0x418 1045 pkg_add CALL wait4(0x418,0x7fffffffbbec,0,0) 1045 pkg_add RET wait4 1048/0x418 1045 pkg_add CALL sigaction(0x2,0x7fffffffbc30,0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigaction(0x3,0x7fffffffbc10,0) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL sigprocmask(0x3,0x7fffffffbbf0,0) 1045 pkg_add RET sigprocmask 0 1045 pkg_add CALL break(0x558000) 1045 pkg_add RET break 0 1045 pkg_add CALL sigaction(0x2,0x7fffffffbd80,0x7fffffffbd60) 1045 pkg_add RET sigaction 0 1045 pkg_add CALL exit(0x1) bsd64-21# From kientzle at freebsd.org Tue Aug 19 23:32:58 2008 From: kientzle at freebsd.org (Tim Kientzle) Date: Tue Aug 19 23:33:06 2008 Subject: pkg_add on 64bits kernel w/ options MAC In-Reply-To: <86068e730808191614m66b72cb1y8786b8a7b6510df2@mail.gmail.com> References: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> <86068e730808191614m66b72cb1y8786b8a7b6510df2@mail.gmail.com> Message-ID: <48AB5598.90404@freebsd.org> Jerry Toung wrote: > On Tue, Aug 19, 2008 at 1:26 PM, Robert Watson wrote: > >>Sounds like a bug of some sort. Could you send the output of "sysctl >>security.mac"? Also, if you could use ktrace to confirm which system calls >>are returning EACCES/EPERM leading to the warnings, that would also be >>helpful. > > bsd64-21# kdump -f ktrace.out > 1045 ktrace RET ktrace 0 > 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > 1045 ktrace RET execve -1 errno 2 No such file or directory > 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > 1045 ktrace RET execve -1 errno 2 No such file or directory > 1045 ktrace CALL execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > 1045 pkg_add RET execve 0 > 1045 pkg_add CALL mmap(0,0x1e40,0x3,0x1000,0xffffffff,0,0) > 1045 pkg_add RET mmap 5443584/0x800531000 > 1045 pkg_add CALL munmap(0x800531000,0x1e40) > 1045 pkg_add RET munmap 0 Robert forgot to specify "ktrace -i" for this. Without the "-i" option, ktrace won't follow the tar command that gets run by pkg_add. It's actually the tar command that's running into problems. Tim From rwatson at FreeBSD.org Wed Aug 20 08:25:23 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Wed Aug 20 08:25:31 2008 Subject: pkg_add on 64bits kernel w/ options MAC In-Reply-To: <86068e730808191614m66b72cb1y8786b8a7b6510df2@mail.gmail.com> References: <86068e730808191315k2997c99bvbbc586e1173858f6@mail.gmail.com> <86068e730808191614m66b72cb1y8786b8a7b6510df2@mail.gmail.com> Message-ID: On Tue, 19 Aug 2008, Jerry Toung wrote: >> Sounds like a bug of some sort. ?Could you send the output of "sysctl >> security.mac"? ?Also, if you could use ktrace to confirm which system calls >> are returning EACCES/EPERM leading to the warnings, that would also be >> helpful. > > I will file a PR later on. In the mean time here are the outputs you were > looking for: ... > bsd64-21# kdump -f ktrace.out Was this ktrace with -di? If not, could you re-run with that? The results may be Really Big so feel free to put it up at a URL somewhere. Robert N M Watson Computer Laboratory University of Cambridge > ? 1045 ktrace?? RET?? ktrace 0 > ? 1045 ktrace?? CALL? > execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > ? 1045 ktrace?? RET?? execve -1 errno 2 No such file or directory > ? 1045 ktrace?? CALL? > execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > ? 1045 ktrace?? RET?? execve -1 errno 2 No such file or directory > ? 1045 ktrace?? CALL? > execve(0x7fffffffe720,0x7fffffffec80,0x7fffffffec98) > ? 1045 pkg_add? RET?? execve 0 > ? 1045 pkg_add? CALL? mmap(0,0x1e40,0x3,0x1000,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 5443584/0x800531000 > ? 1045 pkg_add? CALL? munmap(0x800531000,0x1e40) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? > __sysctl(0x7fffffffe930,0x2,0x800639180,0x7fffffffe928,0,0) > ? 1045 pkg_add? RET?? __sysctl 0 > ? 1045 pkg_add? CALL? mmap(0,0x8000,0x3,0x1002,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 5443584/0x800531000 > ? 1045 pkg_add? CALL? issetugid > ? 1045 pkg_add? RET?? issetugid 0 > ? 1045 pkg_add? CALL? open(0x80052eff0,0,0x1b6) > ? 1045 pkg_add? RET?? open -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? open(0x80052e1a8,0,0) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? read(0x3,0x7fffffffe8d0,0x80) > ? 1045 pkg_add? RET?? read 128/0x80 > ? 1045 pkg_add? CALL? lseek(0x3,0,0x80,0) > ? 1045 pkg_add? RET?? lseek 128/0x80 > ? 1045 pkg_add? CALL? read(0x3,0x800535000,0x3c) > ? 1045 pkg_add? RET?? read 60/0x3c > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? open(0x8005320c0,0,0x800639060) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? fstat(0x3,0x7fffffffe8e0) > ? 1045 pkg_add? RET?? fstat 0 > ? 1045 pkg_add? CALL? read(0x3,0x800638040,0x1000) > ? 1045 pkg_add? RET?? read 4096/0x1000 > ? 1045 pkg_add? CALL? mmap(0,0x10e000,0x5,0x20002,0x3,0,0) > ? 1045 pkg_add? RET?? mmap 6541312/0x80063d000 > ? 1045 pkg_add? CALL? mprotect(0x800648000,0x1000,0x7) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mprotect(0x800648000,0x1000,0x5) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mmap(0x800749000,0x2000,0x3,0x12,0x3,0,0xc000) > ? 1045 pkg_add? RET?? mmap 7639040/0x800749000 > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? open(0x800532120,0,0x6c) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? fstat(0x3,0x7fffffffe8e0) > ? 1045 pkg_add? RET?? fstat 0 > ? 1045 pkg_add? CALL? read(0x3,0x800638040,0x1000) > ? 1045 pkg_add? RET?? read 4096/0x1000 > ? 1045 pkg_add? CALL? mmap(0,0x10c000,0x5,0x20002,0x3,0,0) > ? 1045 pkg_add? RET?? mmap 7647232/0x80074b000 > ? 1045 pkg_add? CALL? mprotect(0x800755000,0x1000,0x7) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mprotect(0x800755000,0x1000,0x5) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mmap(0x800856000,0x1000,0x3,0x12,0x3,0,0xb000) > ? 1045 pkg_add? RET?? mmap 8740864/0x800856000 > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? open(0x800532140,0,0x75) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? fstat(0x3,0x7fffffffe8e0) > ? 1045 pkg_add? RET?? fstat 0 > ? 1045 pkg_add? CALL? read(0x3,0x800638040,0x1000) > ? 1045 pkg_add? RET?? read 4096/0x1000 > ? 1045 pkg_add? CALL? mmap(0,0x138000,0x5,0x20002,0x3,0,0) > ? 1045 pkg_add? RET?? mmap 8744960/0x800857000 > ? 1045 pkg_add? CALL? mprotect(0x800886000,0x1000,0x7) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mprotect(0x800886000,0x1000,0x5) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mmap(0x800987000,0x8000,0x3,0x12,0x3,0,0x30000) > ? 1045 pkg_add? RET?? mmap 9990144/0x800987000 > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? open(0x800532180,0,0x6c) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? fstat(0x3,0x7fffffffe8e0) > ? 1045 pkg_add? RET?? fstat 0 > ? 1045 pkg_add? CALL? read(0x3,0x800638040,0x1000) > ? 1045 pkg_add? RET?? read 4096/0x1000 > ? 1045 pkg_add? CALL? mmap(0,0x247000,0x5,0x20002,0x3,0,0) > ? 1045 pkg_add? RET?? mmap 10022912/0x80098f000 > ? 1045 pkg_add? CALL? mprotect(0x800a9b000,0x1000,0x7) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mprotect(0x800a9b000,0x1000,0x5) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mmap(0x800b9c000,0x37000,0x3,0x12,0x3,0,0x10d000) > ? 1045 pkg_add? RET?? mmap 12173312/0x800b9c000 > ? 1045 pkg_add? CALL? mmap(0x800bd3000,0x3000,0x3,0x1012,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 12398592/0x800bd3000 > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? open(0x8005321a0,0,0x2e) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? fstat(0x3,0x7fffffffe8e0) > ? 1045 pkg_add? RET?? fstat 0 > ? 1045 pkg_add? CALL? read(0x3,0x800638040,0x1000) > ? 1045 pkg_add? RET?? read 4096/0x1000 > ? 1045 pkg_add? CALL? mmap(0,0x20f000,0x5,0x20002,0x3,0,0) > ? 1045 pkg_add? RET?? mmap 12410880/0x800bd6000 > ? 1045 pkg_add? CALL? mprotect(0x800cb1000,0x1000,0x7) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mprotect(0x800cb1000,0x1000,0x5) > ? 1045 pkg_add? RET?? mprotect 0 > ? 1045 pkg_add? CALL? mmap(0x800db1000,0x1b000,0x3,0x12,0x3,0,0xdb000) > ? 1045 pkg_add? RET?? mmap 14356480/0x800db1000 > ? 1045 pkg_add? CALL? mmap(0x800dcc000,0x19000,0x3,0x1012,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 14467072/0x800dcc000 > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? access(0x800536000,0) > ? 1045 pkg_add? RET?? access 0 > ? 1045 pkg_add? CALL? sysarch(0x81,0x7fffffffe9a0) > ? 1045 pkg_add? RET?? sysarch 0 > ? 1045 pkg_add? CALL? mmap(0,0x890,0x3,0x1000,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0x890) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? mmap(0,0xae0,0x3,0x1000,0xffffffff,0,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0xae0) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? mmap(0,0x650,0x3,0x1000,0xffffffff,0x800000000,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0x650) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? mmap(0,0x22e0,0x3,0x1000,0xffffffff,0x800000000,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0x22e0) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? mmap(0,0xad70,0x3,0x1000,0xffffffff,0x800000000,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0xad70) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? mmap(0,0xb180,0x3,0x1000,0xffffffff,0x800000000,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? munmap(0x800539000,0xb180) > ? 1045 pkg_add? RET?? munmap 0 > ? 1045 pkg_add? CALL? sigprocmask(0x1,0x800637f40,0x7fffffffe960) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? sigprocmask(0x3,0x800637f50,0) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? open(0x40b965,0,0x1b6) > ? 1045 pkg_add? RET?? open -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? lstat(0x7fffffffee40,0x7fffffffe250) > ? 1045 pkg_add? RET?? lstat 0 > ? 1045 pkg_add? CALL? __getcwd(0x510f00,0x400) > ? 1045 pkg_add? RET?? __getcwd 0 > ? 1045 pkg_add? CALL? lstat(0x510f00,0x7fffffffe220) > ? 1045 pkg_add? RET?? lstat 0 > ? 1045 pkg_add? CALL? umask(0x12) > ? 1045 pkg_add? RET?? umask 18/0x12 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffe280,0x7fffffffe260) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigaction(0x1,0x7fffffffe280,0x7fffffffe260) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? stat(0x7fffffffde80,0x7fffffffd600) > ? 1045 pkg_add? RET?? stat 0 > ? 1045 pkg_add? CALL? stat(0x40bb0c,0x7fffffffbd10) > ? 1045 pkg_add? RET?? stat 0 > ? 1045 pkg_add? CALL? statfs(0x40bb0c,0x7fffffffbb20) > ? 1045 pkg_add? RET?? statfs 0 > ? 1045 pkg_add? CALL? gettimeofday(0x7fffffffbb70,0) > ? 1045 pkg_add? RET?? gettimeofday 0 > ? 1045 pkg_add? CALL? getpid > ? 1045 pkg_add? RET?? getpid 1045/0x415 > ? 1045 pkg_add? CALL? open(0x800cb135f,0,0) > ? 1045 pkg_add? RET?? open 3 > ? 1045 pkg_add? CALL? read(0x3,0x7fffffffbb84,0x6c) > ? 1045 pkg_add? RET?? read 108/0x6c > ? 1045 pkg_add? CALL? close(0x3) > ? 1045 pkg_add? RET?? close 0 > ? 1045 pkg_add? CALL? stat(0x7fffffffda80,0x7fffffffbc40) > ? 1045 pkg_add? RET?? stat 0 > ? 1045 pkg_add? CALL? mkdir(0x7fffffffda80,0x1c0) > ? 1045 pkg_add? RET?? mkdir 0 > ? 1045 pkg_add? CALL? chmod(0x7fffffffda80,0x1c0) > ? 1045 pkg_add? RET?? chmod 0 > ? 1045 pkg_add? CALL? statfs(0x7fffffffda80,0x7fffffffbb20) > ? 1045 pkg_add? RET?? statfs 0 > ? 1045 pkg_add? CALL? __getcwd(0x510220,0x400) > ? 1045 pkg_add? RET?? __getcwd 0 > ? 1045 pkg_add? CALL? chdir(0x7fffffffda80) > ? 1045 pkg_add? RET?? chdir 0 > ? 1045 pkg_add? CALL? readlink(0x800caa841,0x7fffffffbcf0,0x3f) > ? 1045 pkg_add? RET?? readlink -1 errno 2 No such file or directory > ? 1045 pkg_add? CALL? issetugid > ? 1045 pkg_add? RET?? issetugid 0 > ? 1045 pkg_add? CALL? mmap(0,0x1000,0x3,0x1002,0xffffffff,0x800000000,0) > ? 1045 pkg_add? RET?? mmap 5476352/0x800539000 > ? 1045 pkg_add? CALL? break(0x545000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? break(0x546000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? break(0x547000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? break(0x548000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? > __sysctl(0x7fffffffbc08,0x2,0x7fffffffbbfc,0x7fffffffbc00,0,0) > ? 1045 pkg_add? RET?? __sysctl 0 > ? 1045 pkg_add? CALL? break(0x588000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbbe0,0x7fffffffbbc0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigaction(0x3,0x7fffffffbbe0,0x7fffffffbba0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigprocmask(0x1,0x7fffffffbb90,0x7fffffffbb80) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? fork > ? 1045 pkg_add? RET?? fork 1046/0x416 > ? 1045 pkg_add? CALL? wait4(0x416,0x7fffffffbb7c,0,0) > ? 1045 pkg_add? RET?? wait4 1046/0x416 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbbc0,0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigaction(0x3,0x7fffffffbba0,0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigprocmask(0x3,0x7fffffffbb80,0) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? break(0x558000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? write(0x2,0x7fffffffb4a0,0x9) > ? 1045 pkg_add? RET?? write 9 > ? 1045 pkg_add? CALL? write(0x2,0x7fffffffb580,0x25) > ? 1045 pkg_add? RET?? write 37/0x25 > ? 1045 pkg_add? CALL? write(0x2,0x800db7e87,0x1) > ? 1045 pkg_add? RET?? write 1 > ? 1045 pkg_add? CALL? write(0x2,0x7fffffffb520,0x9) > ? 1045 pkg_add? RET?? write 9 > ? 1045 pkg_add? CALL? write(0x2,0x7fffffffb600,0x4f) > ? 1045 pkg_add? RET?? write 79/0x4f > ? 1045 pkg_add? CALL? write(0x2,0x800db7e87,0x1) > ? 1045 pkg_add? RET?? write 1 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbd70,0x7fffffffbd50) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? chdir(0x510220) > ? 1045 pkg_add? RET?? chdir 0 > ? 1045 pkg_add? CALL? > __sysctl(0x7fffffffbc78,0x2,0x7fffffffbc6c,0x7fffffffbc70,0,0) > ? 1045 pkg_add? RET?? __sysctl 0 > ? 1045 pkg_add? CALL? break(0x598000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbc50,0x7fffffffbc30) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigaction(0x3,0x7fffffffbc50,0x7fffffffbc10) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigprocmask(0x1,0x7fffffffbc00,0x7fffffffbbf0) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? fork > ? 1045 pkg_add? RET?? fork 1048/0x418 > ? 1045 pkg_add? CALL? wait4(0x418,0x7fffffffbbec,0,0) > ? 1045 pkg_add? RET?? wait4 1048/0x418 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbc30,0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigaction(0x3,0x7fffffffbc10,0) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? sigprocmask(0x3,0x7fffffffbbf0,0) > ? 1045 pkg_add? RET?? sigprocmask 0 > ? 1045 pkg_add? CALL? break(0x558000) > ? 1045 pkg_add? RET?? break 0 > ? 1045 pkg_add? CALL? sigaction(0x2,0x7fffffffbd80,0x7fffffffbd60) > ? 1045 pkg_add? RET?? sigaction 0 > ? 1045 pkg_add? CALL? exit(0x1) > bsd64-21#??? > > From brd at FreeBSD.org Wed Aug 20 15:48:38 2008 From: brd at FreeBSD.org (Brad Davis) Date: Wed Aug 20 15:48:45 2008 Subject: The FreeBSD Status Reports for the Second Quarter of 2008 Message-ID: <20080820154823.GC61166@valentine.liquidneon.com> The FreeBSD Status Reports for the Second Quarter of 2008 are now available at: http://www.freebsd.org/news/status/report-2008-04-2008-06.html For convenience I have included them below as well. Regards, Brad Davis ------------------------------- FreeBSD Quarterly Status Report Introduction This Status Report covers FreeBSD related projects between April and June 2008. During this period The FreeBSD Foundation has released their July Newsletter. Thanks to all the reporters for the excellent work! We hope you enjoy reading. __________________________________________________________________ Google Summer of Code * Layer2 filtering * Porting BSD-licensed text-processing tools from OpenBSD Projects * Build cluster * finstall * FreeBSD Bugbusting Team * Graphics support for the boot loader * USB FreeBSD Architecture * ARM/Marvell port The Ports Collection * Ports Collection * Qt/KDE4 Status Report Documentation * FreeBSD FAQ Renovation * The FreeBSD Dutch Documentation Project * The FreeBSD Hungarian Documentation Project * The FreeBSD Spanish Documentation Project __________________________________________________________________ ARM/Marvell port URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/arm/src/sys/arm/orio n/&c=0h4@//depot/projects/arm/src/sys/arm/orion/?ac=83 Contact: Rafal Jaworowski Contact: Bartlomiej Sieka After the last couple of months of intensive development going on towards FreeBSD support for Marvell System-on-Chip devices, we have FreeBSD 8.0-CURRENT running on the following systems: * Orion (already available in Perforce): * 88F5281 * 88F5181 * 88F5182 Kirkwood - 88F6281 Discovery - MV78100 The above families of SOCs are built around CPU cores compliant with ARMv5TE instruction set architecture definition. They share a number of integrated peripherals, for most of which we already have operational and stable drivers: * UART * EHCI USB 2.0 * Ethernet * IDMA (general purpose DMA engine) * XOR * TWSI (I2C) * Timers, watchdog, RTC * GPIO * Interrupt controller * L1, L2 cache High level functional summary: * Production Quality * Error-free Operation * Multiuser * Self-hosted kernel/world builds * NFS- or USB-mounted root filesystem The code is partially available (Orion in Perforce), other variants will also be integrated with Perforce/SVN soon. Open tasks: 1. Drivers that are In-progress: PCI and PCIE. __________________________________________________________________ Build cluster Contact: Kris Kennaway For the past couple of months I have been working on generalizing the package build cluster to allow it to host other batch and interactive jobs. Currently we make an inefficient use of build machines because various projects have dedicated machines that are either underloaded or overloaded for their particular tasks. The goal is to provide a framework for combining all of these machine resources into a single cluster that can be shared by many users, reducing dead time and allowing distributed build tasks to take advantage of extra build resources when available. Developers will be able to obtain on-demand interactive access to a jail running on any of the available architectures, with root access. Similarly, batch jobs will specify their resource requirements and be dispatched to run on a suitable machine in the cluster. Current status: The job queue manager is working and is now being used to map package builds to machines. Various package build scripts have been rewritten to use it instead of the previous build scheduler. The generic job dispatcher is being prototyped and will be validated with several existing services such as INDEX builds. Various support services like ZFS snapshot replication have been written. __________________________________________________________________ finstall URL: http://wiki.freebsd.org/finstall URL: http://www.sf.net/projects/finstall Contact: Ivan Voras Between the last report and this one, the project has yielded a LiveCD installer for i386 containing FreeBSD 7.0-RELEASE. The project was presented at BSDCan 2008. The development is progressing slowly due to the lack of free time. I'm looking for funding that will allow me more involvement in the project. The big item currently in development is documentation and description of the protocol used between the front-end and the back-end, which will result in more robustness in the implementation and could support third-party clients. This sub-project is near completion. The project is currently hosted at SourceForge to allow contribution from non-FreeBSD developers. Open tasks: 1. Partition editor. 2. Package selection. __________________________________________________________________ FreeBSD Bugbusting Team URL: http://www.freebsd.org/support.html#gnats URL: http://wiki.freebsd.org/BugBusting URL: http://people.freebsd.org/~linimon/studies/prs/pr_manpage_index.html URL: http://people.freebsd.org/~linimon/studies/prs/pr_tag_index.html URL: http://people.freebsd.org/~linimon/studies/prs/prs_possibly_committed.h tml URL: http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html URL: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Contact: Ceri Davies Contact: Remko Lodder Contact: Mark Linimon We have granted Bruce Cran (bruce@) direct access to GNATS and Volker Werth (vwe@) has been released from mentorship. We appreciate their help! We had a third bugathon in June, which resulted in the closing of a number of bugs and the investigation/classification of several others. We are still trying to find ways to get more committers helping us with closing PRs that the team has already analyzed. We continue to make good progress in categorizing PRs as they arrive with 'tags' that correspond to manpages. (Special thanks go to Dylan Cochran for the help.) As a result, we now have created some prototype reports that allow browsing the database by manpage. In addition, another new report, oriented towards PR submitters, summarizes the most commonly reported issues. Many of these issues persist because they are difficult to fix. Before filing a PR, you may want to check through this list. Mark Linimon summarized the good technical suggestions from the bugathons so far this year to the wiki. As a part of this, he rearranged the wiki pages, so if you have not seen them for a while, please see BugBusting. In particular, the Resources page is much more complete. Jeremy Chadwick (koitsu@) is now maintaining a page that summarizes some of the commonly reported issues. This complements some of the reports, above, but includes a great deal more information, including how-tos. The overall PR count has been holding at around 5300 since the last release. Open tasks: 1. Think of some way for committers to only view PRs that have been in some way 'vetted' or 'confirmed'. 2. Generate more publicity for what we've already got in place, and for what we intend to do next. 3. Define new categories, classifications, and states for PRs, that will better match our workflow. __________________________________________________________________ FreeBSD FAQ Renovation URL: http://www.FreeBSD.org/doc/en/books/faq/ URL: http://wiki.freebsd.org/faq-renewal Contact: G?bor P?li Contact: Manolis Kiagias An extensive work on renovating the FreeBSD FAQ has been started to support its Greek and Hungarian translations. Further improvements and content changes are still possible, we hope other committers will help us to keep the FAQ updated and tuned further. We have launched a renewal proposal to collect and organize the ideas around a more interactive, accurate, open for comments, consistent across several views etc. FAQ document. We would like to experiment with methods to implement the goals mentioned before, and help is more than welcome. Open tasks: 1. Review the renovated FAQ. 2. Add more question and answers to the FAQ. 3. Refine the FAQ renewal proposal. __________________________________________________________________ Graphics support for the boot loader URL: http://wiki.freebsd.org/OliverFromme/BootLoader Contact: Oliver Fromme This project aims to implement graphics support for FreeBSD's boot loader. It will replace the existing ASCII menu. (Note that the ASCII menu will still be available when graphics mode cannot be used, such as on serial console or on unsupported hardware.) For a more detailed description and screen shots please refer to the project's Wiki URL above. Progress is slow (due to lack of time) but steady. The code currently lives in the Perforce repository. I'll try to prepare a first public CFT as soon as possible. Open tasks: 1. Implement a platform switch. 2. Implement "themes" support (in FORTH). 3. Documentation. __________________________________________________________________ Layer2 filtering URL: http://wiki.freebsd.org/GlebKurtsov/Improving_layer2_filtering URL: http://blogs.freebsdish.org/gleb/ Contact: Gleb Kurtsou Contact: Andrew Thompson Project aims to improve layer2 filtering in ipfw and pf. So far following project goals are achieved: pfil framework is extended to handle ethernet packets, ipfw layer2 filtering is greatly simplified, added l2filter and l2tag per interface flags. Both ipfw and pf firewalls support filtering by ethernet addresses, support stateful filtering with ethernet addresses and firewall's lookup tables are extended to contain ethernet addresses. Open tasks: 1. Implement ARP filtering options in IPFW. __________________________________________________________________ Porting BSD-licensed text-processing tools from OpenBSD URL: http://wiki.freebsd.org/G%C3%A1borSoC2008 URL: http://p4web.freebsd.org/@md=d&cd=//&c=Kqj@//depot/projects/soc2008/gab or_textproc/?ac=83 Contact: G?bor K?vesd?n The grep utility is ready for a thorough test on the portbuild cluster. It is almost compatible with GNU grep, but there are differences in the regex handling at the level of the regex libraries of GNU and the base system one, thus a better compatibility is very hard to implement. Some progress has been made on diff, but some important options are still missing. The sort utility seems to be very problematic in the aspect of the wide character support by design, thus it was given a lower priority. Open tasks: 1. Finish the incomplete options of diff and optimize it. 2. Investigate about the opportunities to fix sort. __________________________________________________________________ Ports Collection URL: http://www.freebsd.org/ports/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://people.freebsd.org/~fenner/portsurvey/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.freebsd.org/portmgr/index.html URL: http://tinderbox.marcuscom.com Contact: Mark Linimon The ports count has jumped to over 19,000. The PR count has been holding steady at around 900. KDE has been updated to 4.1. Special thanks go to Martin Wilke for a great deal of pre-testing. GNOME has been updated three times, first to 2.22.1 and then to 2.22.2 and 2.22.3. Other notable updates are automake, gettext, libtool, and m4. Florent Thoumie has been working on some updates to the pkg_* tools. Ion-Mihai Tetcu has set up a tinderbox with several purposes: first, to quickly try to build packages as changes are committed; secondly, to build them with a non-standard set of environment variables; and thirdly, to build older packages with the non- standard set of environment variables. As a result of all this work, and work by various committers, we are much closer to building packages corrected in the NOPORTDOCS case. Kris Kennaway has done a substantial rewrite of the package building tools, including moving as a default to ZFS, which allows quick cloning of src and ports directories. It is now much easier to manage and monitor the builds. Work on this is continuing. See the commits to Tools/portbuild/scripts for more information. (Work is ongoing to update the Package Building article.) Related work has involved cleaning up some of the ports infrastructure; in particular, the INDEX builds are now much faster. We have been able to do many -exp runs since the last report, including those for bsd.cmake.mk, autotools update, CC environment passing, the KDE 4.1 pre-integration and post-integration checks, lockmgr changes, tty changes, and others. Although a number of PRs have been closed, we are still at 57 portmgr PRs, the same as the last report. The following large changes are in the pipeline: * Introduction of Perl 5.10 We are currently building packages for amd64-6, amd64-7, amd64-8, i386-6, i386-7, i386-8, sparc64-6, and sparc64-7. RELENG_5 has reached the end of its supported life. We have added 4 new committers since the last report. Open tasks: 1. Most of the remaining ports PRs are "existing port/PR assigned to committer". Although the maintainer-timeout policy is helping to keep the backlog down, we are going to need to do more to get the ports in the shape they really need to be in. 2. Although we have added many maintainers, we still have over 4,000 unmaintained ports (see, for instance, the list on portsmon). We are always looking for dedicated volunteers to adopt at least a few unmaintained ports. As well, the packages on amd64 and sparc64 lag behind i386, and we need more testers for those. __________________________________________________________________ Qt/KDE4 Status Report URL: http://freebsd.kde.org Contact: Martin Wilke Contact: FreeBSD KDE Team Qt4 has been updated to 4.4.1 in our test repository. We ran into some runtime problems with Qt 4.4.0, so it was never committed it to the ports tree. Most of the problems have been fixed in 4.4.1 and we plan to commit it in a few days. At the moment, the KDE 4.1 ports are ready for testing before they are committed to the FreeBSD ports tree. We have already had the first Call for Public Testing on July 17th, 2008 with KDE 4.1 beta2. The feedback has been positive so far. If you want to help to test them to speed up the process, please visit the Wiki page and provide feedback. We plan to have it all committed by the middle of August. __________________________________________________________________ The FreeBSD Dutch Documentation Project URL: http://www.freebsd-nl.org URL: http://www.evilcoder.org/freebsd_nl/ Contact: Remko Lodder Contact: Rene Ladan The FreeBSD Dutch Documentation Project is an ongoing project to translate the FreeBSD Documentation resources to the Dutch language. The project is currently progressing very well in translating the FreeBSD Handbook to the Dutch language, the last chapter is being translated by the project members. Recent achievements include the translation of the Jails chapter, and the Virtualization chapter, as well as progression on the Advanced Networking chapter. Rene Ladan is a keyplayer in that region. We also started with the FAQ translation, which is another major target which we should be reaching at some point. If you care to helpout with the translation(s) and/or want to know something about it, please do not hesitate to contact us, we are glad to help where possible. Open tasks: 1. Finish the Handbook translation. 2. Finish the FAQ translation. 3. Finish the Website translation. 4. Keep the projects in sync with the English version(s). __________________________________________________________________ The FreeBSD Hungarian Documentation Project URL: http://FreeBSD.org/hu URL: http://www.FreeBSD.org/doc/hu_HU.ISO8859-2/ URL: http://wiki.FreeBSD.org/HungarianDocumentationProject URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@// depot/projects/docproj_hu/?ac=83 Contact: G?bor K?vesd?n Contact: G?bor P?li Hungarian translation of the FreeBSD Handbook has been finally committed to the doc repository. The translation of the FreeBSD FAQ has also been started, however, the original document needed to be brought up to date first. Two other article translations has been added, compiz-fusion and linux-users. Our Perforce depot was reorganized for the better layout, giving newcomers more space to play. The checkupdate script written by Giorgos Keramidas, a new tool for checking translations has been adopted to help the project's work. Open tasks: 1. Translate release notes for -CURRENT and 7.X. 2. Translate more articles. 3. Translate books/fdp-primer. __________________________________________________________________ The FreeBSD Spanish Documentation Project URL: http://FreeBSD.org/es URL: http://www.FreeBSD.org/doc/es_ES.ISO8859-1/ URL: http://wiki.FreeBSD.org/SpanishDocumentationProject URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_es/&c=S1s@// depot/projects/docproj_es/?ac=83 Contact: Jos? Vicente Carrasco Vay? Contact: G?bor K?vesd?n We have not made any significant progress in this period. We definitely need more active translators to progress with the translation project. Open tasks: 1. Complete renovation of the Spanish web site. 2. Update Handbook translation. 3. Translate release notes for -CURRENT and 7.X. __________________________________________________________________ USB URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/usb/src/sys/dev/usb2 /&c=oDu@//depot/projects/usb/src/sys/dev/usb2/?ac=83 URL: http://p4web.freebsd.org/@md=d&cd=//&cdf=//depot/projects/usb/src/sys/d ev/usb2/core/README.TXT&c=Vfw@//depot/projects/usb/src/sys/dev/usb2/cor e/README.TXT?ac=64&rev1=2 Contact: Hans Petter Sirevaag Selasky During the last three months there has been a number of changes. Most notably all global USB symbols have been renamed to "usb2_" to allow for co-existence with the old USB stack. Also there is now a completely new and reworked UGEN driver which allows multiple drivers to hook onto the same USB device. No more need to unload any kernel drivers. For example it is now possible to have a userland Mouse driver stealing half of the mouse events at the same time "ums" is loaded. The only disadvantage is that your mouse cursor will move slower on the screen. This is maybe not the most common use-case, but it illustrates that kernel USB drivers are no longer locking out other USB userland drivers. A new userland libusb is in the works for FreeBSD. The USB stack now also has support for independent USB BUS, USB Device, and USB Interface permissions. That means you can more easily give USB permissions to USB device drivers at either USB BUS, USB Device or USB Interface level. All USB modules have now been grouped into functional categories: usb2_bluetooth, usb2_ndis, usb2_controller, usb2_quirk, usb2_core, usb2_serial, usb2_ethernet, usb2_sound, usb2_image, usb2_storage, usb2_input, usb2_template, usb2_misc, and usb2_wlan. Ideas and comments with regard to the new USB API are welcome on the FreeBSD-USB Mailing List. __________________________________________________________________ From jav at sics.se Wed Aug 20 18:00:28 2008 From: jav at sics.se (Javier Ubillos) Date: Wed Aug 20 18:00:37 2008 Subject: Override default ICMP (and other protocols) default replies. Message-ID: <1219253269.9118.17.camel@dib> Hi freebsd-hackers. (Sorry for cross posting, but I got no reply when posting to freebsd-questions) I'm implementing a NAT (1 ip - 1 ip) like router. I have chosen to use pcaplib to pick up the packets. I have an implementation which picks up the packets, inspects them, rewrites the destination/source ip-addresses and sends them out on the repective interface. The problem I'm facing however is that my interfaces are answering to e.g. icmp-echo (ping) automatically, and I don't know how to turn this behaviour off. What I want to happen is that if A pings C, my router B in between should simply forward the packets w/o any automatic reactions. A --> B --> C So that if e.g. C is down, no echo-reply is sent back (or if C is up, that C is actually sending the echo-reply. Does any one know how to turn off the automatic replies (ICMP and whatever else I haven't forseen yet) or does any one know where I can find out more about the issue? Thank you // Javier -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080820/07a397c6/attachment.pgp From stb at lassitu.de Thu Aug 21 08:47:26 2008 From: stb at lassitu.de (Stefan Bethke) Date: Thu Aug 21 08:47:33 2008 Subject: Override default ICMP (and other protocols) default replies. In-Reply-To: <1219253269.9118.17.camel@dib> References: <1219253269.9118.17.camel@dib> Message-ID: <56884315-CCF6-4795-9644-BE904DB32597@lassitu.de> Am 20.08.2008 um 19:27 schrieb Javier Ubillos: > Hi freebsd-hackers. > (Sorry for cross posting, but I got no reply when posting to > freebsd-questions) > > I'm implementing a NAT (1 ip - 1 ip) like router. > > I have chosen to use pcaplib to pick up the packets. I have an > implementation which picks up the packets, inspects them, rewrites the > destination/source ip-addresses and sends them out on the repective > interface. > > The problem I'm facing however is that my interfaces are answering to > e.g. icmp-echo (ping) automatically, and I don't know how to turn this > behaviour off. > > What I want to happen is that if A pings C, my router B in between > should simply forward the packets w/o any automatic reactions. > > A --> B --> C > > So that if e.g. C is down, no echo-reply is sent back (or if C is up, > that C is actually sending the echo-reply. > > Does any one know how to turn off the automatic replies (ICMP and > whatever else I haven't forseen yet) or does any one know where I can > find out more about the issue? bpf, which libpcap uses, gives you a copy of the received packet, so the kernel will process it. Typically, if you want to process packets before the host sees them, you'd use ipfw(4) and a divert(4) socket, like natd(8) does. This allows you to modify any packet entering the system, modify it, and (if appropriate) reinject it into the stack. You can also configure your own tun(4) interface to get packets out of the kernel and process them, which might be ideal if you want to process all traffic for an IP. And finally, unless you have really weird requirements, ipfw or pf rules will likely work without any special programming. HTH, Stefan -- Stefan Bethke Fon +49 170 346 0140 From andenore at freebsd.org Thu Aug 21 14:15:08 2008 From: andenore at freebsd.org (Anders Nore) Date: Thu Aug 21 14:15:37 2008 Subject: pkg_improved GSoC 2008 finished Message-ID: Hello hackers, it's been a great summer for me working with the FreeBSD-project. It has truly been an educational experience for me and I would like to continue working on my project as well as other aspects of FreeBSD in the future. You can read about my project on the wiki-page[1] where you can read about the new features and some technical detail, there you will also find testing instructions for those of you who want to try it out. You can also download the source[2]. It will be greatly appreciated if you test it and report any bugs you discover. Thanks for a great summer! - Anders Nore [1] http://wiki.freebsd.org/AndersNore/pkg_improved [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz From olli at lurza.secnetix.de Thu Aug 21 16:37:31 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Thu Aug 21 16:37:38 2008 Subject: Boot loader + malloc Message-ID: <200808211637.m7LGbRhJ008358@lurza.secnetix.de> Hello, I've got a small question regarding $subject. I'm looking at this code snippet from src/sys/boot/i386/loader/main.c: #if defined(LOADER_BZIP2_SUPPORT) || defined(LOADER_FIREWIRE_SUPPORT) heap_top = PTOV(memtop_copyin); memtop_copyin -= 0x300000; heap_bottom = PTOV(memtop_copyin); #else heap_top = (void *)bios_basemem; heap_bottom = (void *)end; #endif setheap(heap_bottom, heap_top); If I understand correctly, the boot loader will use only low memory (i.e. below 0x100000) for malloc by default. Extended memory is only used if bzip2 or firewire support are enabled (not default). Is this intentional? Would it make sense to toggle the default and always use extended memory, unless disabled? I'm asking because the upcoming graphics support requires a little bit of memory for fonts and images, but there's only less than about 80 KB left in low memory, which is insufficient except for very trivial things. The loader kept crashing on me in nasty ways because of that. In my p4 branch I modified the above #if to also use extended memory if LOADER_GRAPHICS_SUPPORT is defined, giving me 3 MB of memory to play with, which is plenty. Is that OK, or should I expect trouble? Any comments are appreciated. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "One of the main causes of the fall of the Roman Empire was that, lacking zero, they had no way to indicate successful termination of their C programs." -- Robert Firth From jgordeev at dir.bg Thu Aug 21 17:50:26 2008 From: jgordeev at dir.bg (Jordan Gordeev) Date: Thu Aug 21 17:50:57 2008 Subject: Boot loader + malloc In-Reply-To: <200808211637.m7LGbRhJ008358@lurza.secnetix.de> References: <200808211637.m7LGbRhJ008358@lurza.secnetix.de> Message-ID: <48ADA3D1.30802@dir.bg> Oliver Fromme wrote: > Hello, > > I've got a small question regarding $subject. I'm looking > at this code snippet from src/sys/boot/i386/loader/main.c: > > #if defined(LOADER_BZIP2_SUPPORT) || defined(LOADER_FIREWIRE_SUPPORT) > heap_top = PTOV(memtop_copyin); > memtop_copyin -= 0x300000; > heap_bottom = PTOV(memtop_copyin); > #else > heap_top = (void *)bios_basemem; > heap_bottom = (void *)end; > #endif > setheap(heap_bottom, heap_top); > > If I understand correctly, the boot loader will use only > low memory (i.e. below 0x100000) for malloc by default. > Extended memory is only used if bzip2 or firewire support > are enabled (not default). Is this intentional? Would it > make sense to toggle the default and always use extended > memory, unless disabled? > > I'm asking because the upcoming graphics support requires > a little bit of memory for fonts and images, but there's > only less than about 80 KB left in low memory, which is > insufficient except for very trivial things. The loader > kept crashing on me in nasty ways because of that. > > In my p4 branch I modified the above #if to also use > extended memory if LOADER_GRAPHICS_SUPPORT is defined, > giving me 3 MB of memory to play with, which is plenty. > Is that OK, or should I expect trouble? > > Any comments are appreciated. > > Best regards > Oliver > > At present the amd64 kernel is loaded just above the first megabyte of physical memory. I have no idea if the loader uses malloc()/free() after the kernel is loaded though. From olli at lurza.secnetix.de Thu Aug 21 19:39:35 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Thu Aug 21 19:39:41 2008 Subject: Boot loader + malloc In-Reply-To: <48ADA3D1.30802@dir.bg> Message-ID: <200808211939.m7LJdJhp017576@lurza.secnetix.de> Jordan Gordeev wrote: > At present the amd64 kernel is loaded just above the first megabyte > of physical memory. Yes, I know, and the standard i386 kernel is loaded at 4 MB, and the PAE kernel is loaded at 2 MB. It doesn't matter much, though. > I have no idea if the loader uses malloc()/free() after the kernel > is loaded though. Yes, it does. By default the loader loads the kernel first, then fires up the "beastie" menu which causes quite some malloc() activity. FICL uses malloc() internally for various things. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "When your hammer is C++, everything begins to look like a thumb." -- Steve Haflich, in comp.lang.c++ From kmacy at freebsd.org Thu Aug 21 21:42:56 2008 From: kmacy at freebsd.org (Kip Macy) Date: Thu Aug 21 21:43:04 2008 Subject: the future of sun4v Message-ID: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> I apologise for cross-posting. I believe that there is a general expectation by freebsd users and developers that unsupported code should not be in CVS. Although sun4v is a very interesting platform for developers doing SMP work, I simply do not have the time or energy to maintain it. If someone else would like to step up and try his hand I would be supportive of his efforts. In the likely event that no one steps forward by the time that 7.1 is released I will ask that it be moved to the Attic. Thanks, Kip From max at love2party.net Thu Aug 21 21:51:15 2008 From: max at love2party.net (Max Laier) Date: Thu Aug 21 21:51:24 2008 Subject: MFC of r180753: ABI problems? Message-ID: <200808212351.13464.max@love2party.net> Hi, I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated that he doesn't have time to take care of it right now. It seems that changing the size of pcicfgregs (aka struct pcicfg) which is part of struct pci_devinfo is out of the question, right? Ideas where to store the HT related state or how to avoid storing the state are welcome. The merge result is attached for reference. This fix is essential for many nforce based boards from ASUS which are rather common, I'm afraid. So it would be good to have this in 7.1/6.4, I think. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News -------------- next part -------------- A non-text attachment was scrubbed... Name: htfix.diff Type: text/x-patch Size: 3881 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080821/ac610d94/htfix.bin From redchin at gmail.com Thu Aug 21 22:21:19 2008 From: redchin at gmail.com (Kevin Downey) Date: Thu Aug 21 22:58:09 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: References: Message-ID: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore wrote: > Hello hackers, > it's been a great summer for me working with the FreeBSD-project. It has > truly been an educational experience for me and I would like to continue > working on my project as well as other aspects of FreeBSD in the future. > > You can read about my project on the wiki-page[1] where you can read about > the new features and some technical detail, there you will also find testing > instructions for those of you who want to try it out. You can also download > the source[2]. It will be greatly appreciated if you test it and report any > bugs you discover. > > > Thanks for a great summer! > - Anders Nore > > > [1] http://wiki.freebsd.org/AndersNore/pkg_improved > [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz Is there a patch against 7-STABLE? Neither of the two patches on the website (-CURRENT and 7.0-RELEASE) or the tarball build on 7-STABLE. The patches are also kind of a pain because they contain diffs against files like "/usr/src/usr.sbin/pkg_install/CVS/Entries" which you don't seem to have if you just use csup. -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye From redchin at gmail.com Thu Aug 21 22:23:47 2008 From: redchin at gmail.com (Kevin Downey) Date: Thu Aug 21 22:58:20 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> Message-ID: <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> On Thu, Aug 21, 2008 at 2:56 PM, Kevin Downey wrote: > On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore wrote: >> Hello hackers, >> it's been a great summer for me working with the FreeBSD-project. It has >> truly been an educational experience for me and I would like to continue >> working on my project as well as other aspects of FreeBSD in the future. >> >> You can read about my project on the wiki-page[1] where you can read about >> the new features and some technical detail, there you will also find testing >> instructions for those of you who want to try it out. You can also download >> the source[2]. It will be greatly appreciated if you test it and report any >> bugs you discover. >> >> >> Thanks for a great summer! >> - Anders Nore >> >> >> [1] http://wiki.freebsd.org/AndersNore/pkg_improved >> [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz > > Is there a patch against 7-STABLE? Neither of the two patches on the > website (-CURRENT and 7.0-RELEASE) or the tarball build on 7-STABLE. > The patches are also kind of a pain because they contain diffs against > files like "/usr/src/usr.sbin/pkg_install/CVS/Entries" which you don't > seem to have if you just use csup. > > > -- > The Mafia way is that we pursue larger goals under the guise of > personal relationships. > Fisheye > sorry, I tried the tarball again, and it built. I must have missed something. -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye From ahornung at gmail.com Fri Aug 22 07:59:23 2008 From: ahornung at gmail.com (Alex Hornung) Date: Fri Aug 22 07:59:30 2008 Subject: Driver accessing other drivers/devices ? Message-ID: <10fba67b0808220034t2b9598cekbad7c976eed6975f@mail.gmail.com> Hello, I need to access the hard disk from within a driver that is not a FS. I would also need to get a list of PCI devices connected. Is there a way I can access these devices directly, at least in the first case, issuing directly ATA/IDE commands to the hard disk? In the case of PCI it would be even nicer to be able to communicate with the pci driver... but if that's not possible, it's also ok if I can access the PCI bus controller directly. The driver I'm writing is not a PCI or PCI device driver either. Hope someone can help me out on this one, it's important that there's no user-space code... Thanks in advance, Alex From andenore at freebsd.org Fri Aug 22 10:12:08 2008 From: andenore at freebsd.org (Anders Nore) Date: Fri Aug 22 10:12:15 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> Message-ID: On Fri, 22 Aug 2008 00:00:01 +0200, Kevin Downey wrote: > On Thu, Aug 21, 2008 at 2:56 PM, Kevin Downey wrote: >> On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore >> wrote: >>> Hello hackers, >>> it's been a great summer for me working with the FreeBSD-project. It >>> has >>> truly been an educational experience for me and I would like to >>> continue >>> working on my project as well as other aspects of FreeBSD in the >>> future. >>> >>> You can read about my project on the wiki-page[1] where you can read >>> about >>> the new features and some technical detail, there you will also find >>> testing >>> instructions for those of you who want to try it out. You can also >>> download >>> the source[2]. It will be greatly appreciated if you test it and >>> report any >>> bugs you discover. >>> >>> >>> Thanks for a great summer! >>> - Anders Nore >>> >>> >>> [1] http://wiki.freebsd.org/AndersNore/pkg_improved >>> [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz >> >> Is there a patch against 7-STABLE? Neither of the two patches on the >> website (-CURRENT and 7.0-RELEASE) or the tarball build on 7-STABLE. >> The patches are also kind of a pain because they contain diffs against >> files like "/usr/src/usr.sbin/pkg_install/CVS/Entries" which you don't >> seem to have if you just use csup. >> The CVS entries should be removed from the latest patches and a patch for RELENG_7_0 has been added. You can get the new patches from http://home.no.net/andenore/patches/ >> >> -- >> The Mafia way is that we pursue larger goals under the guise of >> personal relationships. >> Fisheye >> > > sorry, I tried the tarball again, and it built. I must have missed > something. > Maybe you tried to compile from a different directory than /usr/src/usr.sbin/pkg_install ? Makefile.inc will try to `.include "../Makefile.inc"' to get BINDIR, so if you comment this out and specify your own BINDIR variable `BINDIR?= /usr/sbin' it should be ok. Thanks for your input! - Anders Nore From peterjeremy at optushome.com.au Fri Aug 22 11:33:21 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri Aug 22 11:33:40 2008 Subject: the future of sun4v In-Reply-To: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> Message-ID: <20080822113317.GD32539@server.vk2pj.dyndns.org> [Replies re-directed to freebsd-sun4v] On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >I believe that there is a general expectation by freebsd users and >developers that unsupported code should not be in CVS. Although sun4v >is a very interesting platform for developers doing SMP work, I simply >do not have the time or energy to maintain it. If someone else would >like to step up and try his hand I would be supportive of his efforts. >In the likely event that no one steps forward by the time that 7.1 is >released I will ask that it be moved to the Attic. Since there are no other current SPARC CPUs that FreeBSD can run on (the US-II has been obsolete for about 6 years and FreeBSD won't run on any more recent sun4u chips), that will also remove the justification for maintaining a SPARC64 port. I don't have the knowledge or available time to maintain the sun4v port by myself but would be happy to be part of a team doing so. One impediment I have is that I don't have a T-1 or T-2 system that I can dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but since FreeBSD doesn't support either the virtual disk or virtual network, actually getting FreeBSD running there presents somewhat of a challenge. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080822/dfebed42/attachment.pgp From kris at FreeBSD.org Fri Aug 22 11:44:30 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 11:44:36 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <48AEA699.10903@FreeBSD.org> Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. > > I don't have the knowledge or available time to maintain the sun4v > port by myself but would be happy to be part of a team doing so. One > impediment I have is that I don't have a T-1 or T-2 system that I can > dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > since FreeBSD doesn't support either the virtual disk or virtual > network, actually getting FreeBSD running there presents somewhat of a > challenge. > There are two t1000 systems in the freebsd.org cluster that are available for people to work on. Rink Springer has also expressed interest in this. Perhaps Kip can explain some more about what things he looked at, but the most serious bugs might be in pmap or perhaps trap handling. Operationally, things like buildworld -jN die quickly with random signals, kernel traps, etc. Kris P.S. It looks like marius has made progress on US III but sun4u is still an architectural dead end. From kris at FreeBSD.org Fri Aug 22 15:04:07 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Fri Aug 22 15:04:25 2008 Subject: sun4v arch In-Reply-To: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> Message-ID: <48AED560.8010001@FreeBSD.org> Nikolay Kalev wrote: > I would also like to help as well. > As KMacy knows before i asked a lot of questions for T2 types of > servers but unfortunately i have no more access to those kind of > hardware as well. > I;m willing to participate if a team will be formated. Just so everyone is on the same page, what is needed to keep sun4v viable are people with experience with (or intention to learn about) low level architectural and implementation details of the FreeBSD kernel and the sun4v hardware platform, who know their way around things like pmap.c and other MD places where the kernel interfaces with the "bare metal", and who are willing to make a long term (multi-year) commitment to supporting the platform. Kris From nkalev at gmail.com Fri Aug 22 14:45:46 2008 From: nkalev at gmail.com (Nikolay Kalev) Date: Fri Aug 22 15:05:04 2008 Subject: sun4v arch Message-ID: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated. From gahr at FreeBSD.org Fri Aug 22 16:50:44 2008 From: gahr at FreeBSD.org (Pietro Cerutti) Date: Fri Aug 22 16:50:51 2008 Subject: sun4v arch In-Reply-To: <48AED560.8010001@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> Message-ID: <48AEEE3C.7030006@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Kris Kennaway wrote: | Just so everyone is on the same page, what is needed to keep sun4v | viable are people with experience with (or intention to learn about) low | level architectural and implementation details of the FreeBSD kernel and | the sun4v hardware platform, who know their way around things like | pmap.c and other MD places where the kernel interfaces with the "bare | metal", and who are willing to make a long term (multi-year) commitment | to supporting the platform. If we had docs... | Kris - -- Pietro Cerutti gahr@FreeBSD.org PGP Public Key: http://gahr.ch/pgp -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkiu7jsACgkQwMJqmJVx946SjgCeMIDO6Q6hZSVlsfPQTJhkM3Vk BIUAmwWDU4IAqv+nyFvGRhSxblsrVh4Q =y3qu -----END PGP SIGNATURE----- From redchin at gmail.com Fri Aug 22 17:08:52 2008 From: redchin at gmail.com (Kevin Downey) Date: Fri Aug 22 17:54:22 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> Message-ID: <1d3ed48c0808221008x28dc28a0xe01c39ecfcdc895c@mail.gmail.com> On Fri, Aug 22, 2008 at 2:56 AM, Anders Nore wrote: > On Fri, 22 Aug 2008 00:00:01 +0200, Kevin Downey wrote: > >> On Thu, Aug 21, 2008 at 2:56 PM, Kevin Downey wrote: >>> >>> On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore >>> wrote: >>>> >>>> Hello hackers, >>>> it's been a great summer for me working with the FreeBSD-project. It has >>>> truly been an educational experience for me and I would like to continue >>>> working on my project as well as other aspects of FreeBSD in the future. >>>> >>>> You can read about my project on the wiki-page[1] where you can read >>>> about >>>> the new features and some technical detail, there you will also find >>>> testing >>>> instructions for those of you who want to try it out. You can also >>>> download >>>> the source[2]. It will be greatly appreciated if you test it and report >>>> any >>>> bugs you discover. >>>> >>>> >>>> Thanks for a great summer! >>>> - Anders Nore >>>> >>>> >>>> [1] http://wiki.freebsd.org/AndersNore/pkg_improved >>>> [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz >>> >>> Is there a patch against 7-STABLE? Neither of the two patches on the >>> website (-CURRENT and 7.0-RELEASE) or the tarball build on 7-STABLE. >>> The patches are also kind of a pain because they contain diffs against >>> files like "/usr/src/usr.sbin/pkg_install/CVS/Entries" which you don't >>> seem to have if you just use csup. >>> > > The CVS entries should be removed from the latest patches and a patch for > RELENG_7_0 has been added. > You can get the new patches from http://home.no.net/andenore/patches/ > >>> >>> -- >>> The Mafia way is that we pursue larger goals under the guise of >>> personal relationships. >>> Fisheye >>> >> >> sorry, I tried the tarball again, and it built. I must have missed >> something. >> > > Maybe you tried to compile from a different directory than > /usr/src/usr.sbin/pkg_install ? > Makefile.inc will try to `.include "../Makefile.inc"' to get BINDIR, so if > you comment this out and specify your own BINDIR variable `BINDIR?= > /usr/sbin' it should be ok. > > > Thanks for your input! > - Anders Nore > > The tarball linked to from you email ended up building, I am not sure what I was doing wrong that it did not build before. The `.include "../Makefile.inc"' like in the Makefile was commented out so "make install" bombed out until I figured that out. running 'portupgrade --batch --force gnome\*' I am seeing stuff like ===> Registering installation for gnome-backgrounds-2.22.0_1 pkg_info: show_plist: unknown command type 21 (2008-08-22 09:58:11) ===> Cleaning for gnome-backgrounds-2.22.0_1 dunno if that is something important. -- The Mafia way is that we pursue larger goals under the guise of personal relationships. Fisheye From julian at elischer.org Fri Aug 22 18:37:00 2008 From: julian at elischer.org (Julian Elischer) Date: Fri Aug 22 18:37:10 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: <1d3ed48c0808221008x28dc28a0xe01c39ecfcdc895c@mail.gmail.com> References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> <1d3ed48c0808221008x28dc28a0xe01c39ecfcdc895c@mail.gmail.com> Message-ID: <48AF074C.5030008@elischer.org> Kevin Downey wrote: > On Fri, Aug 22, 2008 at 2:56 AM, Anders Nore wrote: >> On Fri, 22 Aug 2008 00:00:01 +0200, Kevin Downey wrote: >> >>> On Thu, Aug 21, 2008 at 2:56 PM, Kevin Downey wrote: >>>> On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore >>>> wrote: >>>>> Hello hackers, >>>>> it's been a great summer for me working with the FreeBSD-project. It has >>>>> truly been an educational experience for me and I would like to continue >>>>> working on my project as well as other aspects of FreeBSD in the future. >>>>> is there a document that outlines what architectural changes were made? From xcllnt at mac.com Fri Aug 22 19:00:24 2008 From: xcllnt at mac.com (Marcel Moolenaar) Date: Fri Aug 22 19:00:46 2008 Subject: the future of sun4v In-Reply-To: <20080822113317.GD32539@server.vk2pj.dyndns.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> Message-ID: <477C6946-2540-4122-AD66-B769A623FE01@mac.com> On Aug 22, 2008, at 4:33 AM, Peter Jeremy wrote: > [Replies re-directed to freebsd-sun4v] > > On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: >> I believe that there is a general expectation by freebsd users and >> developers that unsupported code should not be in CVS. Although sun4v >> is a very interesting platform for developers doing SMP work, I >> simply >> do not have the time or energy to maintain it. If someone else would >> like to step up and try his hand I would be supportive of his >> efforts. >> In the likely event that no one steps forward by the time that 7.1 is >> released I will ask that it be moved to the Attic. > > Since there are no other current SPARC CPUs that FreeBSD can run on > (the US-II has been obsolete for about 6 years and FreeBSD won't run > on any more recent sun4u chips), that will also remove the > justification for maintaining a SPARC64 port. Marius has been doing some great work towards US-III support. I have FreeBSD/sparc64 running on Netra SMP with US-III CPUs. While the code is not in SVN, It's in Perforce and from what I can see, it's in a very good shape. FYI, -- Marcel Moolenaar xcllnt@mac.com From pb at ludd.ltu.se Fri Aug 22 20:02:46 2008 From: pb at ludd.ltu.se (Peter B) Date: Fri Aug 22 20:08:47 2008 Subject: usb match() function Message-ID: <200808222002.m7MK2fvo004486@brother.ludd.ltu.se> Within the usb drivers (/usr/src/sys/dev/usb/u*.c) there's an matching routine where the 'uaa->iface' is supposed to be assigned before the routine is called. However for a new device or class this doesn't seem to work. Instead 'uaa' is set like for an generic device (two interfaces, no "default" in my case). So how is one supposed to make the kernel fill in 'uaa->iface' ..? Code excerpt (v7.x): static int *_match(device_t self) { struct usb_attach_arg *uaa = device_get_ivars(self); usb_interface_descriptor_t *id; DPRINTFN(10,("*_match\n")); if (uaa->iface == NULL) return (UMATCH_NONE); From marius at alchemy.franken.de Fri Aug 22 20:37:29 2008 From: marius at alchemy.franken.de (Marius Strobl) Date: Fri Aug 22 20:37:58 2008 Subject: the future of sun4v In-Reply-To: <48AEA699.10903@FreeBSD.org> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> Message-ID: <20080822201603.GA14444@alchemy.franken.de> On Fri, Aug 22, 2008 at 01:44:25PM +0200, Kris Kennaway wrote: > Peter Jeremy wrote: > >[Replies re-directed to freebsd-sun4v] > > > >On 2008-Aug-21 14:42:55 -0700, Kip Macy wrote: > >>I believe that there is a general expectation by freebsd users and > >>developers that unsupported code should not be in CVS. Although sun4v > >>is a very interesting platform for developers doing SMP work, I simply > >>do not have the time or energy to maintain it. If someone else would > >>like to step up and try his hand I would be supportive of his efforts. > >>In the likely event that no one steps forward by the time that 7.1 is > >>released I will ask that it be moved to the Attic. > > > >Since there are no other current SPARC CPUs that FreeBSD can run on > >(the US-II has been obsolete for about 6 years and FreeBSD won't run > >on any more recent sun4u chips), that will also remove the > >justification for maintaining a SPARC64 port. > > > >I don't have the knowledge or available time to maintain the sun4v > >port by myself but would be happy to be part of a team doing so. One > >impediment I have is that I don't have a T-1 or T-2 system that I can > >dedicate to FreeBSD. I could work on FreeBSD in a guest domain - but > >since FreeBSD doesn't support either the virtual disk or virtual > >network, actually getting FreeBSD running there presents somewhat of a > >challenge. > > > > There are two t1000 systems in the freebsd.org cluster that are > available for people to work on. Rink Springer has also expressed > interest in this. > > Perhaps Kip can explain some more about what things he looked at, but > the most serious bugs might be in pmap or perhaps trap handling. > Operationally, things like buildworld -jN die quickly with random > signals, kernel traps, etc. > > Kris > > P.S. It looks like marius has made progress on US III but sun4u is still > an architectural dead end. Well, let's see what architecture the upcoming Rock CPUs are; judging their feature list they appear to be a continuation of the Fujitsu sun4u line rather than a successor of UST1/2 :) Marius From kmacy at freebsd.org Fri Aug 22 20:41:47 2008 From: kmacy at freebsd.org (Kip Macy) Date: Fri Aug 22 20:42:05 2008 Subject: the future of sun4v In-Reply-To: <20080822201603.GA14444@alchemy.franken.de> References: <3c1674c90808211442t707966fq29997b53a70ed2f7@mail.gmail.com> <20080822113317.GD32539@server.vk2pj.dyndns.org> <48AEA699.10903@FreeBSD.org> <20080822201603.GA14444@alchemy.franken.de> Message-ID: <3c1674c90808221341i6c97be59wcfb10979305ffdb0@mail.gmail.com> > Well, let's see what architecture the upcoming Rock CPUs are; > judging their feature list they appear to be a continuation of > the Fujitsu sun4u line rather than a successor of UST1/2 :) That is not what I've heard. -Kip From kmacy at freebsd.org Fri Aug 22 22:03:19 2008 From: kmacy at freebsd.org (Kip Macy) Date: Fri Aug 22 22:03:25 2008 Subject: request for testers - xen support for domU in head Message-ID: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> Basic Xen support for 32-bit in PAE mode is in CVS. Please see the wiki for general information: http://wiki.freebsd.org/FreeBSD/Xen Please be forewarned that I am not claiming that this is production-ready. There are many known limitations. If you would like to take it for a test drive and report bugs please give it a spin. Thanks, Kip From peterjeremy at optushome.com.au Fri Aug 22 22:55:14 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Fri Aug 22 22:55:27 2008 Subject: sun4v arch In-Reply-To: <48AED560.8010001@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> Message-ID: <20080822225510.GI32539@server.vk2pj.dyndns.org> On 2008-Aug-22 17:04:00 +0200, Kris Kennaway wrote: >Just so everyone is on the same page, what is needed to keep sun4v >viable are people with experience with (or intention to learn about) low >level architectural and implementation details of the FreeBSD kernel What documentation is currently accurate for this beyond the source code? The only things I can quickly find are: "Design & Implementation of FreeBSD 5.2" and "FreeBSD Architecture Handbook". The former is getting quite old and I'm not sure how up-to-date the latter is kept. >the sun4v hardware platform, Is the documentation at http://www.opensparc.net/opensparc-t1/index.html and http://www.opensparc.net/opensparc-t2/index.html adequate for this or is there additional information that is needed? Is there any tutorial style documentation on the low-level T1/T2 details? > who know their way around things like >pmap.c and other MD places where the kernel interfaces with the "bare >metal", I've poked around the low-level details of FreeBSD/i386 and /Alpha in the past, though I'm nothing like an expert at it. sun4v/sun4v is only about twice the size of a 6th Edition kernel... > and who are willing to make a long term (multi-year) commitment >to supporting the platform. Yes. Is there a summary of the open issues somewhere? There are no sun4v PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't been touched since November 2006 and suggests that the only critical issue is lack of serial port support. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080822/b37c4801/attachment.pgp From pitney.brad at googlemail.com Fri Aug 22 23:37:05 2008 From: pitney.brad at googlemail.com (Brad Pitney) Date: Sat Aug 23 02:48:09 2008 Subject: request for testers - xen support for domU in head In-Reply-To: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> References: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> Message-ID: <3dd203290808221610h157caa1fqd66b8d243da3d383@mail.gmail.com> On Fri, Aug 22, 2008 at 11:03 PM, Kip Macy wrote: > Basic Xen support for 32-bit in PAE mode is in CVS. Please see the > wiki for general information: > > http://wiki.freebsd.org/FreeBSD/Xen > > Please be forewarned that I am not claiming that this is > production-ready. There are many known limitations. If you would like > to take it for a test drive and report bugs please give it a spin. > > Thanks, > Kip this is cool, I've been so eager to try I have a first bug report :) thank you for this! -- Best regards, Brad From glarkin at FreeBSD.org Sat Aug 23 03:04:52 2008 From: glarkin at FreeBSD.org (Greg Larkin) Date: Sat Aug 23 03:05:23 2008 Subject: request for testers - xen support for domU in head In-Reply-To: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> References: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> Message-ID: <48AF746A.1030804@FreeBSD.org> Kip Macy wrote: > Basic Xen support for 32-bit in PAE mode is in CVS. Please see the > wiki for general information: > > http://wiki.freebsd.org/FreeBSD/Xen > > Please be forewarned that I am not claiming that this is > production-ready. There are many known limitations. If you would like > to take it for a test drive and report bugs please give it a spin. > > Thanks, > Kip > Hi Kip, Thanks very much for the effort here. I'm looking forward to trying it out and providing feedback. I'm not really familiar with Xen, but perhaps enough to ask this question: Does this mean that Amazon EC2 will be able to boot FreeBSD instances? Thank you, Greg From kmacy at freebsd.org Sat Aug 23 03:15:12 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sat Aug 23 03:15:18 2008 Subject: request for testers - xen support for domU in head In-Reply-To: <48AF746A.1030804@FreeBSD.org> References: <3c1674c90808221503v5ee48f05td71f70f152e71ef8@mail.gmail.com> <48AF746A.1030804@FreeBSD.org> Message-ID: <3c1674c90808222015u543df3c3h540bbc2022f12ab5@mail.gmail.com> p >> > Hi Kip, > > Thanks very much for the effort here. I'm looking forward to trying it > out and providing feedback. > > I'm not really familiar with Xen, but perhaps enough to ask this > question: Does this mean that Amazon EC2 will be able to boot FreeBSD > instances? > The last time I spoke with them they were using 3.0.3 which uses some older interfaces which I don't currently support. Nonetheless, I do intend to support EC2 in the near future. Thanks, Kip From yanefbsd at gmail.com Sat Aug 23 05:36:04 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sat Aug 23 05:36:12 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> Message-ID: <7d6fde3d0808222236t45103e4eseb8f174ffb89fdca@mail.gmail.com> On Fri, Aug 22, 2008 at 2:56 AM, Anders Nore wrote: > On Fri, 22 Aug 2008 00:00:01 +0200, Kevin Downey wrote: > >> On Thu, Aug 21, 2008 at 2:56 PM, Kevin Downey wrote: >>> >>> On Thu, Aug 21, 2008 at 6:10 AM, Anders Nore >>> wrote: >>>> >>>> Hello hackers, >>>> it's been a great summer for me working with the FreeBSD-project. It has >>>> truly been an educational experience for me and I would like to continue >>>> working on my project as well as other aspects of FreeBSD in the future. >>>> >>>> You can read about my project on the wiki-page[1] where you can read >>>> about >>>> the new features and some technical detail, there you will also find >>>> testing >>>> instructions for those of you who want to try it out. You can also >>>> download >>>> the source[2]. It will be greatly appreciated if you test it and report >>>> any >>>> bugs you discover. >>>> >>>> >>>> Thanks for a great summer! >>>> - Anders Nore >>>> >>>> >>>> [1] http://wiki.freebsd.org/AndersNore/pkg_improved >>>> [2] http://home.no.net/andenore/patches/pkg_install-20080708.tar.gz >>> >>> Is there a patch against 7-STABLE? Neither of the two patches on the >>> website (-CURRENT and 7.0-RELEASE) or the tarball build on 7-STABLE. >>> The patches are also kind of a pain because they contain diffs against >>> files like "/usr/src/usr.sbin/pkg_install/CVS/Entries" which you don't >>> seem to have if you just use csup. >>> > > The CVS entries should be removed from the latest patches and a patch for > RELENG_7_0 has been added. > You can get the new patches from http://home.no.net/andenore/patches/ > >>> >>> -- >>> The Mafia way is that we pursue larger goals under the guise of >>> personal relationships. >>> Fisheye >>> >> >> sorry, I tried the tarball again, and it built. I must have missed >> something. >> > > Maybe you tried to compile from a different directory than > /usr/src/usr.sbin/pkg_install ? > Makefile.inc will try to `.include "../Makefile.inc"' to get BINDIR, so if > you comment this out and specify your own BINDIR variable `BINDIR?= > /usr/sbin' it should be ok. > > > Thanks for your input! > - Anders Nore How about this? For standalone packages, specify: Makefile.inc <-- redefine variables here. pkg_install/ <-- sources go here. Seems like a simple solution ;). As for diff, you probably what to use: --exclude-from=SCM_patterns.txt where SCM_patterns.txt consists of: -------------- CVS .git .svn .CC -------------- ... etc. As for patch, `patch -p0 < pkg_install.patch' does the trick if you do `diff -Naur .'. Cheers and good work on finishing off this awesome task. I'll gladly write up tests for you if you like =], -Garrett From imp at bsdimp.com Sat Aug 23 06:43:59 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 06:44:07 2008 Subject: MFC of r180753: ABI problems? In-Reply-To: <200808212351.13464.max@love2party.net> References: <200808212351.13464.max@love2party.net> Message-ID: <20080823.004209.1974818375.imp@bsdimp.com> In message: <200808212351.13464.max@love2party.net> Max Laier writes: : Hi, : : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated that he : doesn't have time to take care of it right now. : : It seems that changing the size of pcicfgregs (aka struct pcicfg) which is : part of struct pci_devinfo is out of the question, right? Ideas where to : store the HT related state or how to avoid storing the state are welcome. : : The merge result is attached for reference. This fix is essential for many : nforce based boards from ASUS which are rather common, I'm afraid. So it : would be good to have this in 7.1/6.4, I think. I think this is OK. pcicfgregs is an internal to pci implementation detail. You've added it at the end, so any leakage of the offsets won't matter. All subclasses of pci would be affected. Internal to the kernel isn't all that interesting, since they are all compiled at the same time. This would only matter for modules. Cardbus and acpi would be the only modules affected. That would mean you couldn't boot a 7.0 kernel with a 7.1 set of modules or vice versa. I'm not sure that is actually going to work anyway... Warner From imp at bsdimp.com Sat Aug 23 06:49:30 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 06:49:36 2008 Subject: Driver accessing other drivers/devices ? In-Reply-To: <10fba67b0808220034t2b9598cekbad7c976eed6975f@mail.gmail.com> References: <10fba67b0808220034t2b9598cekbad7c976eed6975f@mail.gmail.com> Message-ID: <20080823.004753.1477561239.imp@bsdimp.com> In message: <10fba67b0808220034t2b9598cekbad7c976eed6975f@mail.gmail.com> "Alex Hornung" writes: : Hello, : : I need to access the hard disk from within a driver that is not a FS. : I would also need to get a list of PCI devices connected. Is there a : way I can access these devices directly, at least in the first case, : issuing directly ATA/IDE commands to the hard disk? There's always ata_if.m... : In the case of PCI it would be even nicer to be able to communicate : with the pci driver... but if that's not possible, it's also ok if I : can access the PCI bus controller directly. The driver I'm writing is : not a PCI or PCI device driver either. : : Hope someone can help me out on this one, it's important that there's : no user-space code... Generally, you don't want to scan the PCI bus to look for drivers to talk to. That's bad kharma and likely begging to be abused. Having said that, I've had cooperative drivers in the kernel before. They usually look for each other and send messages to each other with kobj. It is better to look for "friend0" that you know can receive messages. kobj adds a layer of protection since it will gracefully give an error when you can't do it. Hey, wait, ata_if is kobj... You could likely expand it to allow queueing of commands and such. Warner From imp at bsdimp.com Sat Aug 23 06:53:16 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 06:53:28 2008 Subject: sun4v arch In-Reply-To: <48AEEE3C.7030006@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <48AEEE3C.7030006@FreeBSD.org> Message-ID: <20080823.005200.-335188553.imp@bsdimp.com> In message: <48AEEE3C.7030006@FreeBSD.org> Pietro Cerutti writes: : -----BEGIN PGP SIGNED MESSAGE----- : Hash: SHA512 : : Kris Kennaway wrote: : | Just so everyone is on the same page, what is needed to keep sun4v : | viable are people with experience with (or intention to learn about) low : | level architectural and implementation details of the FreeBSD kernel and : | the sun4v hardware platform, who know their way around things like : | pmap.c and other MD places where the kernel interfaces with the "bare : | metal", and who are willing to make a long term (multi-year) commitment : | to supporting the platform. : : If we had docs... There's a bunch of sun4v docs available. See http://www.sun.com/processors/documentation.html for example. Warner From aryeh.friedman at gmail.com Sat Aug 23 11:01:14 2008 From: aryeh.friedman at gmail.com (Aryeh Friedman) Date: Sat Aug 23 11:01:34 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up Message-ID: What is difference between /etc/rc.d called programs and ones called after login prompt shows up? The reason for asking is sysutils/fusefs-kmod gives an error if any mounts are attempted in /etc/rc but if the exactly the same command is issued by a user's .login/.xsession/etc. it works without problem (assuming proper permissions of course). a) Can anyone think of a reason why this would happen (the maintainer is non-responive) b) Is it possible to force something to run after /etc/rc exits but before init calls getty? From gary.jennejohn at freenet.de Sat Aug 23 13:33:57 2008 From: gary.jennejohn at freenet.de (Gary Jennejohn) Date: Sat Aug 23 13:34:04 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: Message-ID: <20080823153354.2ed632d4@peedub.jennejohn.org> On Sat, 23 Aug 2008 06:34:23 -0400 "Aryeh Friedman" wrote: > What is difference between /etc/rc.d called programs and ones called > after login prompt shows up? > > The reason for asking is sysutils/fusefs-kmod gives an error if any > mounts are attempted in /etc/rc but if the exactly the same command is > issued by a user's .login/.xsession/etc. it works without problem > (assuming proper permissions of course). > > a) Can anyone think of a reason why this would happen (the maintainer > is non-responive) > I suspect that fuse.ko is loaded by one of the scripts under /etc/rc.d since it seems to be installed under $PREFIX/modules where PREFIX is normally /usr/local. Until that happens you can't use mount_fusefs. > b) Is it possible to force something to run after /etc/rc exits but > before init calls getty? > Well, there are ways to force dependencies in the rc.d scripts, but I don't know the setup well enough to be helpful. I have no idea which script handles modules installed by ports and when it is invoked. You could try moving fuse.ko to /boot/modules and modify loader.conf to load fuse.ko at boot time. --- Gary Jennejohn From fbsd06 at mlists.homeunix.com Sat Aug 23 14:51:53 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Sat Aug 23 14:52:00 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: <20080823153354.2ed632d4@peedub.jennejohn.org> References: <20080823153354.2ed632d4@peedub.jennejohn.org> Message-ID: <20080823153552.3fc52542@gumby.homeunix.com.> On Sat, 23 Aug 2008 15:33:54 +0200 Gary Jennejohn wrote: > On Sat, 23 Aug 2008 06:34:23 -0400 > "Aryeh Friedman" wrote: > > > What is difference between /etc/rc.d called programs and ones called > > after login prompt shows up? > > > > The reason for asking is sysutils/fusefs-kmod gives an error if any > > mounts are attempted in /etc/rc but if the exactly the same command > > is issued by a user's .login/.xsession/etc. it works without problem > > (assuming proper permissions of course). > > > > a) Can anyone think of a reason why this would happen (the > > maintainer is non-responive) > > > Well, there are ways to force dependencies in the rc.d scripts, but I > don't know the setup well enough to be helpful. I have no idea which > script handles modules installed by ports and when it is invoked. > > You could try moving fuse.ko to /boot/modules and modify loader.conf > to load fuse.ko at boot time. There's no need for that, it's already handled by the rc.d scripts. Fuse-based filesystems should be mounted with the "late" option, so they get mounted after the kernel module is loaded. You might also need a patch so the mount can find the correct mount_* executable.I think it's needed in 7.0, I'm not sure about 7-stable and current. From jhb at freebsd.org Sat Aug 23 20:31:33 2008 From: jhb at freebsd.org (John Baldwin) Date: Sat Aug 23 20:31:40 2008 Subject: MFC of r180753: ABI problems? In-Reply-To: <20080823.004209.1974818375.imp@bsdimp.com> References: <200808212351.13464.max@love2party.net> <20080823.004209.1974818375.imp@bsdimp.com> Message-ID: <200808230742.10902.jhb@freebsd.org> On Saturday 23 August 2008 02:42:09 am M. Warner Losh wrote: > In message: <200808212351.13464.max@love2party.net> > > Max Laier writes: > : Hi, > : > : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated > : that he doesn't have time to take care of it right now. > : > : It seems that changing the size of pcicfgregs (aka struct pcicfg) which > : is part of struct pci_devinfo is out of the question, right? Ideas where > : to store the HT related state or how to avoid storing the state are > : welcome. > : > : The merge result is attached for reference. This fix is essential for > : many nforce based boards from ASUS which are rather common, I'm afraid. > : So it would be good to have this in 7.1/6.4, I think. > > I think this is OK. > > pcicfgregs is an internal to pci implementation detail. You've added > it at the end, so any leakage of the offsets won't matter. All > subclasses of pci would be affected. Internal to the kernel isn't all > that interesting, since they are all compiled at the same time. This > would only matter for modules. Cardbus and acpi would be the only > modules affected. That would mean you couldn't boot a 7.0 kernel with > a 7.1 set of modules or vice versa. I'm not sure that is actually > going to work anyway... ACPI (and OFW's) PCI bus code isn't going to care, and I doubt cardbus is either. Hmm, actually, cardbus doesn't, but ACPI actually does (acpi_pci uses its own extended ivars for PCI devices to cache ACPI handles). That said, this particular ABI was actually broken earlier by MSI (though I didn't realize it at the time. :( ). -- John Baldwin From aryeh.friedman at gmail.com Sat Aug 23 20:38:15 2008 From: aryeh.friedman at gmail.com (Aryeh Friedman) Date: Sat Aug 23 20:38:22 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: <20080823153354.2ed632d4@peedub.jennejohn.org> References: <20080823153354.2ed632d4@peedub.jennejohn.org> Message-ID: On Sat, Aug 23, 2008 at 8:27 AM, Garrett Cooper wrote: > On Sat, Aug 23, 2008 at 3:34 AM, Aryeh Friedman > wrote: >> What is difference between /etc/rc.d called programs and ones called >> after login prompt shows up? >> >> The reason for asking is sysutils/fusefs-kmod gives an error if any >> mounts are attempted in /etc/rc but if the exactly the same command is >> issued by a user's .login/.xsession/etc. it works without problem >> (assuming proper permissions of course). >> >> a) Can anyone think of a reason why this would happen (the maintainer >> is non-responive) >> b) Is it possible to force something to run after /etc/rc exits but >> before init calls getty? > > a) Bad credentials? Dependencies not started (yet)? > b) You can enforce ordering, if that's what you want. See: > http://www.freebsd.org/doc/en/articles/rc-scripting/ a) I use a custom /etc/rc thus I can place the mount command anywhere I want. No matter where I place I get the same error it is *ONLY* after /etc/rc terminates.... I am b) I load fuse.ko in /boot/loader.con (copied it from /usr/local/modules to /boot/modules) here is dmesg proof it is loaded: > dmesg|grep fuse fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8 fuse4bsd: compiled against kernel config /usr/obj/usr/src/sys/MONSTER c) See a additionally to prove all the above here is my /etc/rc (the last 2 lines where added just to prove the point): #!/bin/sh PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin swapon -a fsck -p mount -rw / mount -a hostname flosoft.no-ip.biz ifconfig re0 192.168.2.2 ifconfig lo0 127.0.0.1 route add default 192.168.2.1 named cupsd noip2 ntpdate pool.ntp.org sendmail -bd -q1m apachectl start moused -t auto -p /dev/ums0 vidcontrol -m on mount /mnt/win_c mount /mnt/win_d Here is /etc/fstab (set up as recommended in the docs for sysutils/fusefs-ntfs [which I am the co-maintainer of]): # Device Mountpoint FStype Options Dump Pass# /dev/ad8s2b none swap sw 0 0 /dev/ad8s2a / ufs rw 1 1 /dev/ad8s2e /tmp ufs rw 2 2 /dev/ad8s2f /usr ufs rw 2 2 /dev/ad8s2d /var ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 linproc /compat/linux/proc linprocfs rw 0 0 /dev/ad8s1 /mnt/win_c ntfs-3g rw,late 0 0 /dev/da0s1 /mnt/win_d ntfs-3g rw,late 0 0 The patch to mount recommended in the fusefs-ntfs docs has been applied. In order to show that the mount commands work post call to getty but not before: When the above /etc/rc is run: swapon: adding /dev/ad8s2b as swap device /dev/ad8s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2a: clean, 164555 free (3603 frags, 20119 blocks, 1.4% fragmentation) /dev/ad8s2e: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2e: clean, 253254 free (54 frags, 31650 blocks, 0.0% fragmentation) /dev/ad8s2f: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2f: clean, 210848941 free (53253 frags, 26349461 blocks, 0.0% fragmenta tion) /dev/ad8s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad8s2d: clean, 1970559 free (551 frags, 246251 blocks, 0.0% fragmentation) re0: link state changed to DOWN add net default: gateway 192.168.2.1 re0: link state changed to UP 23 Aug 09:02:00 ntpdate[48]: step time server 216.184.20.83 offset 0.794898 sec pid 54 (limits), uid 0: exited on signal 11 (core dumped) [Sat Aug 23 09:02:01 2008] [warn] (2)No such file or directory: Failed to enable the 'httpready' Accept Filter fuse: failed to exec mount program: No such file or directory fuse: failed to mount file system: Unknown error: 0 fuse: failed to exec mount program: No such file or directory fuse: failed to mount file system: Unknown error: 0 FreeBSD/i386 (flosoft.no-ip.biz) (ttyv0) login: Here is the .login for root and the .xsession for my main user account (I use xdm): > more ~root/.login # $FreeBSD: src/etc/root/dot.login,v 1.22 2000/07/15 03:25:14 rwatson Exp $ # # .login - csh login script, read by login shell, after `.cshrc' at login. # # see also csh(1), environ(7). # # Uncomment to display a random cookie each login: # [ -x /usr/games/fortune ] && /usr/games/fortune -s echo Mounting C: mount /mnt/win_c echo Mounting D: mount /mnt/win_d > more ~aryeh/.xsession sudo mount /mnt/win_c& sudo mount /mnt/win_d& mixer 100 mixer pcm 100 xfce4-session Sudo is configured to allow 'aryeh' to no password access. And finally proof that the two methods do in fact work: > df -k Filesystem 1024-blocks Used Avail Capacity Mounted on /dev/ad8s2a 507630 178520 288500 38% / devfs 1 1 0 100% /dev /dev/ad8s2e 507630 1124 465896 0% /tmp /dev/ad8s2f 443581998 21884342 386211098 5% /usr /dev/ad8s2d 4040654 99570 3617832 3% /var procfs 4 4 0 100% /proc linprocfs 4 4 0 100% /usr/compat/linux/proc /dev/fuse0 20972824 20196712 776112 96% /mnt/win_c /dev/fuse1 244196348 2463792 241732556 1% /mnt/win_d Thus it is clear that the *ONLY* difference between the /etc/rc calls and the post getty calls is when they are made. Thus the orginal question (i.e. I have verified this happens on any fusefs-* file system). I have attempted to call stuff via alternate methods like such as calling the mount_* directly and using equiv programs that have different names for each fusefs-* and did so with and without having the enteries in /etc/fstab > > -Garrett > From imp at bsdimp.com Sat Aug 23 21:52:56 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Aug 23 21:53:03 2008 Subject: MFC of r180753: ABI problems? In-Reply-To: <200808230742.10902.jhb@freebsd.org> References: <200808212351.13464.max@love2party.net> <20080823.004209.1974818375.imp@bsdimp.com> <200808230742.10902.jhb@freebsd.org> Message-ID: <20080823.155034.1260392773.imp@bsdimp.com> In message: <200808230742.10902.jhb@freebsd.org> John Baldwin writes: : On Saturday 23 August 2008 02:42:09 am M. Warner Losh wrote: : > In message: <200808212351.13464.max@love2party.net> : > : > Max Laier writes: : > : Hi, : > : : > : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated : > : that he doesn't have time to take care of it right now. : > : : > : It seems that changing the size of pcicfgregs (aka struct pcicfg) which : > : is part of struct pci_devinfo is out of the question, right? Ideas where : > : to store the HT related state or how to avoid storing the state are : > : welcome. : > : : > : The merge result is attached for reference. This fix is essential for : > : many nforce based boards from ASUS which are rather common, I'm afraid. : > : So it would be good to have this in 7.1/6.4, I think. : > : > I think this is OK. : > : > pcicfgregs is an internal to pci implementation detail. You've added : > it at the end, so any leakage of the offsets won't matter. All : > subclasses of pci would be affected. Internal to the kernel isn't all : > that interesting, since they are all compiled at the same time. This : > would only matter for modules. Cardbus and acpi would be the only : > modules affected. That would mean you couldn't boot a 7.0 kernel with : > a 7.1 set of modules or vice versa. I'm not sure that is actually : > going to work anyway... : : ACPI (and OFW's) PCI bus code isn't going to care, and I doubt cardbus is : either. Hmm, actually, cardbus doesn't, but ACPI actually does (acpi_pci CardBus' does because it creates a slightly larger pcicfgreg per device... : uses its own extended ivars for PCI devices to cache ACPI handles). That : said, this particular ABI was actually broken earlier by MSI (though I didn't : realize it at the time. :( ). Warner From fbsd06 at mlists.homeunix.com Sat Aug 23 22:13:53 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Sat Aug 23 22:14:00 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: <20080823153354.2ed632d4@peedub.jennejohn.org> Message-ID: <20080823231349.5941d9f3@gumby.homeunix.com.> On Sat, 23 Aug 2008 16:38:13 -0400 "Aryeh Friedman" wrote: > c) See a additionally to prove all the above here is my /etc/rc (the > last 2 lines where added just to prove the point): > > #!/bin/sh > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin > > swapon -a > fsck -p > ... > fuse: failed to exec mount program: No such file or directory > > Thus it is clear that the *ONLY* difference between the /etc/rc calls > and the post getty calls is when they are made. There's another difference: your /etc/rc script doesn't export PATH. From fbsd06 at mlists.homeunix.com Sat Aug 23 23:39:24 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Sat Aug 23 23:39:31 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: <20080823231349.5941d9f3@gumby.homeunix.com.> References: <20080823153354.2ed632d4@peedub.jennejohn.org> <20080823231349.5941d9f3@gumby.homeunix.com.> Message-ID: <20080824003920.34f6bf51@gumby.homeunix.com.> On Sat, 23 Aug 2008 23:13:49 +0100 RW wrote: > On Sat, 23 Aug 2008 16:38:13 -0400 > "Aryeh Friedman" wrote: > > > > c) See a additionally to prove all the above here is my /etc/rc (the > > last 2 lines where added just to prove the point): > > > > #!/bin/sh > > > > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin > > > > swapon -a > > fsck -p > > ... > > fuse: failed to exec mount program: No such file or directory > > > > Thus it is clear that the *ONLY* difference between the /etc/rc > > calls and the post getty calls is when they are made. > > There's another difference: your /etc/rc script doesn't export PATH. That does seem to be the answer. I was curious as to why it only fails on ntfs, so I had a look at the source. It seems that mount and fsck find mount_* and fsck_* through a hard-coded path of "/rescue:/sbin:/usr/sbin", but mount_ntfs-3g then additionally has to find mount_fusefs through the environment path. Perhaps sysutils/fusefs-libs should be patched to make the whole thing more self-consistent. From ivoras at freebsd.org Sun Aug 24 01:07:06 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sun Aug 24 01:07:13 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: <752.354102633213$1219529718@news.gmane.org> References: <20080823153354.2ed632d4@peedub.jennejohn.org> <752.354102633213$1219529718@news.gmane.org> Message-ID: RW wrote: > There's another difference: your /etc/rc script doesn't export PATH. And TERM. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080824/3d9bae63/signature.pgp From aryeh.friedman at gmail.com Sun Aug 24 02:02:20 2008 From: aryeh.friedman at gmail.com (Aryeh Friedman) Date: Sun Aug 24 02:02:27 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: <20080824003920.34f6bf51@gumby.homeunix.com.> References: <20080823153354.2ed632d4@peedub.jennejohn.org> <20080823231349.5941d9f3@gumby.homeunix.com.> <20080824003920.34f6bf51@gumby.homeunix.com.> Message-ID: On Sat, Aug 23, 2008 at 7:39 PM, RW wrote: > On Sat, 23 Aug 2008 23:13:49 +0100 > RW wrote: > >> On Sat, 23 Aug 2008 16:38:13 -0400 >> "Aryeh Friedman" wrote: >> >> >> > c) See a additionally to prove all the above here is my /etc/rc (the >> > last 2 lines where added just to prove the point): >> > >> > #!/bin/sh >> > >> > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin >> > >> > swapon -a >> > fsck -p >> > ... >> > fuse: failed to exec mount program: No such file or directory >> > >> > Thus it is clear that the *ONLY* difference between the /etc/rc >> > calls and the post getty calls is when they are made. >> >> There's another difference: your /etc/rc script doesn't export PATH. > > That does seem to be the answer. > > I was curious as to why it only fails on ntfs, so I had a look > at the source. It seems that mount and fsck find mount_* and fsck_* > through a hard-coded path of "/rescue:/sbin:/usr/sbin", but > mount_ntfs-3g then additionally has to find mount_fusefs through the > environment path. > > Perhaps sysutils/fusefs-libs should be patched to make the whole thing > more self-consistent. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > Thanks that did it... but you're incorrect in saying it is only ntfs it is all fuse based fs's I had a the same error when doing a fuse-ssh mount to my machine at work From aryeh.friedman at gmail.com Sun Aug 24 02:02:41 2008 From: aryeh.friedman at gmail.com (Aryeh Friedman) Date: Sun Aug 24 02:02:52 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: <20080823153354.2ed632d4@peedub.jennejohn.org> <752.354102633213$1219529718@news.gmane.org> Message-ID: On Sat, Aug 23, 2008 at 9:06 PM, Ivan Voras wrote: > RW wrote: > >> There's another difference: your /etc/rc script doesn't export PATH. > > And TERM. > > Since I never set TERM why export it? From sobomax at FreeBSD.org Sun Aug 24 02:08:44 2008 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Sun Aug 24 02:08:59 2008 Subject: sun4v arch In-Reply-To: <20080822225510.GI32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> Message-ID: <48B0BEC7.1070806@FreeBSD.org> Peter Jeremy wrote: > Is there a summary of the open issues somewhere? There are no sun4v > PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't > been touched since November 2006 and suggests that the only critical > issue is lack of serial port support. There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). -Maxim From yanefbsd at gmail.com Sun Aug 24 02:59:53 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Aug 24 03:00:00 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: <20080823153354.2ed632d4@peedub.jennejohn.org> <20080823231349.5941d9f3@gumby.homeunix.com.> <20080824003920.34f6bf51@gumby.homeunix.com.> Message-ID: <7d6fde3d0808231959i46027bd5xce2c142a21dcd940@mail.gmail.com> On Sat, Aug 23, 2008 at 7:02 PM, Aryeh Friedman wrote: > On Sat, Aug 23, 2008 at 7:39 PM, RW wrote: >> On Sat, 23 Aug 2008 23:13:49 +0100 >> RW wrote: >> >>> On Sat, 23 Aug 2008 16:38:13 -0400 >>> "Aryeh Friedman" wrote: >>> >>> >>> > c) See a additionally to prove all the above here is my /etc/rc (the >>> > last 2 lines where added just to prove the point): >>> > >>> > #!/bin/sh >>> > >>> > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin >>> > >>> > swapon -a >>> > fsck -p >>> > ... >>> > fuse: failed to exec mount program: No such file or directory >>> > >>> > Thus it is clear that the *ONLY* difference between the /etc/rc >>> > calls and the post getty calls is when they are made. >>> >>> There's another difference: your /etc/rc script doesn't export PATH. >> >> That does seem to be the answer. >> >> I was curious as to why it only fails on ntfs, so I had a look >> at the source. It seems that mount and fsck find mount_* and fsck_* >> through a hard-coded path of "/rescue:/sbin:/usr/sbin", but >> mount_ntfs-3g then additionally has to find mount_fusefs through the >> environment path. >> >> Perhaps sysutils/fusefs-libs should be patched to make the whole thing >> more self-consistent. Isn't the typical use-case for fuse-based FS'es to be executed in userland though by non-root users? -Garrett From yanefbsd at gmail.com Sun Aug 24 03:39:31 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Sun Aug 24 03:39:42 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> On Sat, Aug 23, 2008 at 6:52 PM, Maxim Sobolev wrote: > Peter Jeremy wrote: >> >> Is there a summary of the open issues somewhere? There are no sun4v >> PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't >> been touched since November 2006 and suggests that the only critical >> issue is lack of serial port support. > > There is a better interpretation, which is that the only critical issue is > lack of real users for this port, not lack of serial port support :). > > -Maxim Maybe some time should be spent looking at stuff from NetBSD to see whether or not they've solved some already critical porting pieces that FreeBSD lacks in this architecture? -Garrett From linimon at lonesome.com Sun Aug 24 04:00:42 2008 From: linimon at lonesome.com (Mark Linimon) Date: Sun Aug 24 04:10:02 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <20080824034055.GB12515@soaustin.net> On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote: > There is a better interpretation, which is that the only critical issue > is lack of real users for this port, not lack of serial port support :). My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) Our implementation of GNATS barely serves us as a problem report system; it fails almost completely as a system for listing missing features. We would need to have something like that to track the status of the non- Tier-1 ports. (I used to maintain a table of how feature-complete the various ports are, but it is now way out of date.) mcl From peterjeremy at optushome.com.au Sun Aug 24 04:23:43 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Sun Aug 24 04:24:01 2008 Subject: sun4v arch In-Reply-To: <20080824034055.GB12515@soaustin.net> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> Message-ID: <20080824042339.GM32539@server.vk2pj.dyndns.org> On 2008-Aug-23 22:40:55 -0500, Mark Linimon wrote: >My understanding is the the port is in a pre-alpha state due to unfinished >work in the kernel, so expecting there to be any userbase is premature. Except that the wiki gives a far more optimistic picture. >All of our 'new' architectures which are in this state have so few non- >developer users that there is hardly any reason to submit PRs. AFAICT >the active developers already know what's missing :-) That makes it very difficult for someone outside that group to come up to speed. I can't find anything in the freebsd-sun4v archvies. I was hoping that there would be a list somewhere of what state various subsystems were in and what remained to be done. wiki.freebsd.org sounds like the ideal place for this. On 2008-Aug-23 20:39:29 -0700, Garrett Cooper wrote: >Maybe some time should be spent looking at stuff from NetBSD to see >whether or not they've solved some already critical porting pieces >that FreeBSD lacks in this architecture? I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 port only covers the US-I/II families and there's no mention of sun4v. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080824/5c8c3739/attachment.pgp From kmacy at freebsd.org Sun Aug 24 04:39:35 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sun Aug 24 04:39:42 2008 Subject: sun4v arch In-Reply-To: <20080824042339.GM32539@server.vk2pj.dyndns.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824034055.GB12515@soaustin.net> <20080824042339.GM32539@server.vk2pj.dyndns.org> Message-ID: <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> Hi Peter, There really isn't any magic to bringing up a port. You compile it, install it, and then run it until it breaks. Once it breaks you spend a lot of time instrumenting the code to track down what went wrong. Then, depending on the amount of technical insight you have in to the issue, you go through a number of iterations until it is fixed. Fixing the pmap issue is "just" (notice the quotes) a matter of tracking down the missing TLB shootdowns. For anyone who chooses pick this up it will be very educational. It will also be very time consuming. -Kip On Sat, Aug 23, 2008 at 9:23 PM, Peter Jeremy wrote: > On 2008-Aug-23 22:40:55 -0500, Mark Linimon wrote: >>My understanding is the the port is in a pre-alpha state due to unfinished >>work in the kernel, so expecting there to be any userbase is premature. > > Except that the wiki gives a far more optimistic picture. > >>All of our 'new' architectures which are in this state have so few non- >>developer users that there is hardly any reason to submit PRs. AFAICT >>the active developers already know what's missing :-) > > That makes it very difficult for someone outside that group to come up > to speed. I can't find anything in the freebsd-sun4v archvies. I was > hoping that there would be a list somewhere of what state various > subsystems were in and what remained to be done. wiki.freebsd.org > sounds like the ideal place for this. > > On 2008-Aug-23 20:39:29 -0700, Garrett Cooper wrote: >>Maybe some time should be spent looking at stuff from NetBSD to see >>whether or not they've solved some already critical porting pieces >>that FreeBSD lacks in this architecture? > > I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 > port only covers the US-I/II families and there's no mention of sun4v. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed behaviour. > From kmacy at freebsd.org Sun Aug 24 04:49:49 2008 From: kmacy at freebsd.org (Kip Macy) Date: Sun Aug 24 04:50:07 2008 Subject: sun4v arch In-Reply-To: References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824042339.GM32539@server.vk2pj.dyndns.org> Message-ID: <3c1674c90808232149t58993f49x9bbc4ac561b40e4@mail.gmail.com> On Sat, Aug 23, 2008 at 9:34 PM, Sevan / Venture37 wrote: > > >> I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 >> port only covers the US-I/II families and there's no mention of sun4v. > > OpenBSD/sparc64 supports the sun4v architecture & has done for a while. > Heh. The bugs that FreeBSD exhibits on sun4v won't be hit on UP and are much less prevalent without preemption. -Kip From fbsd06 at mlists.homeunix.com Sun Aug 24 05:03:54 2008 From: fbsd06 at mlists.homeunix.com (RW) Date: Sun Aug 24 05:04:00 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: <20080823153354.2ed632d4@peedub.jennejohn.org> <20080823231349.5941d9f3@gumby.homeunix.com.> <20080824003920.34f6bf51@gumby.homeunix.com.> Message-ID: <20080824054821.1c9d923d@gumby.homeunix.com.> On Sat, 23 Aug 2008 22:02:14 -0400 "Aryeh Friedman" wrote: > Thanks that did it... but you're incorrect in saying it is only ntfs > it is all fuse based fs's I had a the same error when doing a fuse-ssh > mount to my machine at work I meant only ntfs out of all the other entries in your fstab. If PATH isn't exported then the question became: why are any of the mounts or fscks succeeding? Presumably all the fuse filesystems are mounted in the same way mount -t foo --> mount_foo --> mount_fusefs as opposed to mount -t foo --> mount_foo for native filesystems. Since it turns out that only the mount_foo --> mount_fusefs call needs a PATH variable, all fuse filesystems will fail if PATH isn't exported, but no native filesystem will be affected. From ivoras at freebsd.org Sun Aug 24 09:36:36 2008 From: ivoras at freebsd.org (Ivan Voras) Date: Sun Aug 24 09:36:43 2008 Subject: What is difference between /etc/rc called programs and ones called after login prompt shows up In-Reply-To: References: <20080823153354.2ed632d4@peedub.jennejohn.org> <752.354102633213$1219529718@news.gmane.org> Message-ID: Aryeh Friedman wrote: > On Sat, Aug 23, 2008 at 9:06 PM, Ivan Voras wrote: >> RW wrote: >> >>> There's another difference: your /etc/rc script doesn't export PATH. >> And TERM. > > Since I never set TERM why export it? Sorry, by rereading the thread I think I misunderstood the context of the post I was replying to. The reason for my suggestion was that I know some utilitites that don't work when called before the login environment is present because they use curses and somehow fail if there's no TERM. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080824/5db1f36b/signature.pgp From ticso at cicely7.cicely.de Sun Aug 24 12:02:57 2008 From: ticso at cicely7.cicely.de (Bernd Walter) Date: Sun Aug 24 12:03:13 2008 Subject: usb match() function In-Reply-To: <200808222002.m7MK2fvo004486@brother.ludd.ltu.se> References: <200808222002.m7MK2fvo004486@brother.ludd.ltu.se> Message-ID: <20080824120234.GM23672@cicely7.cicely.de> On Fri, Aug 22, 2008 at 10:02:41PM +0200, Peter B wrote: > > Within the usb drivers (/usr/src/sys/dev/usb/u*.c) there's an matching routine > where the 'uaa->iface' is supposed to be assigned before the routine is called. > > However for a new device or class this doesn't seem to work. Instead 'uaa' > is set like for an generic device (two interfaces, no "default" in my case). > > So how is one supposed to make the kernel fill in 'uaa->iface' ..? Your function is potentially getting called multiple times. First all drivers (except ugen) are asked for the whole device and if all refuses it splits the device into the interfaces and asks every driver again - if no driver claims at least a single interface ugen is asked for the whole device. So you have to refuse the whole device and wait for the interface run. If there's no interface run then another driver already claimed it or your device has no interfaces defined. > Code excerpt (v7.x): > static int > *_match(device_t self) > { > struct usb_attach_arg *uaa = device_get_ivars(self); > usb_interface_descriptor_t *id; > > DPRINTFN(10,("*_match\n")); > if (uaa->iface == NULL) > return (UMATCH_NONE); > -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From brad at comstyle.com Sun Aug 24 06:47:08 2008 From: brad at comstyle.com (Brad) Date: Sun Aug 24 14:15:42 2008 Subject: sun4v arch Message-ID: <20080824064655.GB11196@booyah.home.comstyle.com> > I can't find anything that suggests NetBSD runs on sun4v. Their sparc64 > port only covers the US-I/II families and there's no mention of sun4v. OpenBSD/sparc64 runs UltraSPARC-T1 and UltraSPARC-T2 systems... and the com port works too. ;) In addition to UltraSPARC III, III+, IIIi, IV and Fujitsu SPARC64 V, VI, VII systems (PRIMEPOWER / Mx000). console is /virtual-devices@100/console@1 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.4-current (GENERIC.MP) #7: Sun Aug 24 00:01:05 MDT 2008 root@sun4v.openbsd.org:/usr/src/sys/arch/sparc64/compile/GENERIC.MP real mem = 34225520640 (32640MB) avail mem = 33572167680 (32016MB) mainbus0 at root: SPARC Enterprise T5120 cpu0 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu1 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu2 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu3 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu4 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu5 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu6 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu7 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu8 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu9 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu10 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu11 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu12 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu13 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu14 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu15 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu16 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu17 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu18 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu19 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu20 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu21 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu22 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu23 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu24 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu25 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu26 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu27 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu28 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu29 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu30 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu31 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu32 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu33 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu34 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu35 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu36 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu37 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu38 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu39 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu40 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu41 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu42 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu43 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu44 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu45 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu46 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu47 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu48 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu49 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu50 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu51 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu52 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu53 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu54 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu55 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu56 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu57 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu58 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu59 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu60 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu61 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu62 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz cpu63 at mainbus0: SUNW,UltraSPARC-T2 (rev 0.0) @ 1165.379 MHz vbus0 at mainbus0 "flashprom" at vbus0 not configured "channel-devices" at vbus0 not configured "n2cp" at vbus0 not configured "ncp" at vbus0 not configured "random-number-generator" at vbus0 not configured vcons0 at vbus0 vrtc0 at vbus0 "niu" at mainbus0 not configured vpci0 at mainbus0: bus 2 to 18, dvma map 80000000-ffffffff pci0 at vpci0 ppb0 at pci0 dev 0 function 0 "PLX PEX 8533" rev 0xaa pci1 at ppb0 bus 3 ppb1 at pci1 dev 1 function 0 "PLX PEX 8533" rev 0xaa pci2 at ppb1 bus 4 ppb2 at pci2 dev 0 function 0 "PLX PEX 8517" rev 0xad pci3 at ppb2 bus 5 ppb3 at pci3 dev 1 function 0 "PLX PEX 8517" rev 0xad pci4 at ppb3 bus 6 ppb4 at pci4 dev 0 function 0 "PLX PEX 8112" rev 0xaa pci5 at ppb4 bus 7 ohci0 at pci5 dev 0 function 0 "NEC USB" rev 0x43: ivec 0x16, version 1.0 ohci1 at pci5 dev 0 function 1 "NEC USB" rev 0x43: ivec 0x17, version 1.0 ehci0 at pci5 dev 0 function 2 "NEC USB" rev 0x04: ivec 0x14 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "NEC EHCI root hub" rev 2.00/1.00 addr 1 usb1 at ohci0: USB revision 1.0 uhub1 at usb1 "NEC OHCI root hub" rev 1.00/1.00 addr 1 usb2 at ohci1: USB revision 1.0 uhub2 at usb2 "NEC OHCI root hub" rev 1.00/1.00 addr 1 ppb5 at pci3 dev 2 function 0 "PLX PEX 8517" rev 0xad pci6 at ppb5 bus 8 em0 at pci6 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x17, address 00:14:4f:d4:d2:c6 em1 at pci6 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c7 ppb6 at pci3 dev 3 function 0 "PLX PEX 8517" rev 0xad pci7 at ppb6 bus 9 em2 at pci7 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x14, address 00:14:4f:d4:d2:c8 em3 at pci7 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: ivec 0x15, address 00:14:4f:d4:d2:c9 ppb7 at pci1 dev 2 function 0 "PLX PEX 8533" rev 0xaa pci8 at ppb7 bus 10 mpi0 at pci8 dev 0 function 0 "Symbios Logic SAS1068E" rev 0x02: ivec 0x16 scsibus0 at mpi0: 112 targets, initiator 112 sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed sd0: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total sd1 at scsibus0 targ 1 lun 0: SCSI3 0/direct fixed sd1: 140009MB, 14089 cyl, 24 head, 848 sec, 512 bytes/sec, 286739329 sec total ppb8 at pci1 dev 8 function 0 "PLX PEX 8533" rev 0xaa pci9 at ppb8 bus 11 ppb9 at pci9 dev 0 function 0 "PLX PEX 8533" rev 0xaa pci10 at ppb9 bus 12 ppb10 at pci10 dev 1 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci11 at ppb10 bus 13 ppb11 at pci10 dev 2 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci12 at ppb11 bus 14 ppb12 at pci10 dev 8 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci13 at ppb12 bus 15 ppb13 at pci10 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci14 at ppb13 bus 16 ppb14 at pci10 dev 10 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x14 pci15 at ppb14 bus 17 ppb15 at pci1 dev 9 function 0 "PLX PEX 8533" rev 0xaa: ivec 0x16 pci16 at ppb15 bus 18 "pci-performance-counters" at mainbus0 not configured ebus0 at mainbus0 com0 at ebus0 addr ca0000-ca0007 ivec 0x13: ns16550a, 16 byte fifo umass0 at uhub0 port 2 configuration 1 interface 0 "Texas Instruments Incorporated 6250 FW: 03.05.02.22.562AD423" rev 2.00/2.00 addr 2 umass0: using SCSI over Bulk-Only scsibus1 at umass0: 2 targets, initiator 0 cd0 at scsibus1 targ 1 lun 0: SCSI0 5/cdrom removable uhub3 at uhub0 port 4 "Cypress Semiconductor USB2 Hub" rev 2.00/0.0b addr 3 softraid0 at root bootpath: /pci@0,0/pci@0,0/pci@2,0/scsi@0,0/disk@0,0 root on sd0a swap on sd0b dump on sd0b -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From gballet at gmail.com Sun Aug 24 20:01:26 2008 From: gballet at gmail.com (Guillaume Ballet) Date: Sun Aug 24 20:01:32 2008 Subject: Extending the ddb command set In-Reply-To: <200808181002.14885.jhb@freebsd.org> References: <48A70B37.60401@freebsd.org> <200808181002.14885.jhb@freebsd.org> Message-ID: On Mon, Aug 18, 2008 at 2:02 PM, John Baldwin wrote: > (snip) > A simpler approach is probably to make DB_COMMAND() use a SYSINIT to register > new functions instead of teaching DDB about that linker set. You just need > to write a shared "register_command()" function (and a deregister for > SYSUNINIT for module unload) that the SYSINIT uses. This also probably > requires changing the structure of the DDB tables, though you might be able > to make it simpler now. You could probably just make the tables be sorted > linked lists now instead of arrays. This would also remove the whole "aux > table" hack. > Following Sam and John's advice, I have rewritten the patch so as to use SYS(UN)INIT. It uses a linked list instead of an array to store commands. As the patch is more than 400 lines long, it is available for reviewing at: http://dl.free.fr/jQQQkB72h0 I used 7.0 ; 6.2 requires a bit more work. Many thanks to Sam, John and Kostik for their suggestions. Feedback is still welcome :) From pgj at FreeBSD.org Sun Aug 24 20:07:40 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Sun Aug 24 20:07:47 2008 Subject: Request for Comments: Update to developers-handbook/policies Message-ID: <48B1B972.1090500@FreeBSD.org> Dear Members, A few weeks ago, I started to work on docs/126030 [1] in cooperation with Gavin Atkinson (gavin@) and Giorgos Keramidas (keramida@) to update chapter ``Source Tree Guidelines and Policies'' of the ``FreeBSD Developers' Handbook'' [2]. Based on Gavin's original patch, I created drafts on how to fix the sections in question (and I linked them below). During the update, I found useful to include a section of Dag-Erling's Subversion Primer on the Wiki [3] about vendor imports. At the moment, I do not erase the old text (about vendor imports with CVS) but I kept it for compatibility reasons (and moved to a separate subsection as des@ advised). However, if somebody says it is deemed to be removed I will do that. Because I am not so experienced in vendor imports (as a doc committer) but I would like to help Gavin (and others who want this book updated), I ask you to review my changes and express your ideas, comments and suggestion. Note: This mail was posted to -doc a few days ago. I have not received any answer to it (maybe due to its highly technical nature), but I hope members of list will comment on this. Draft of section (5.1) MAINTAINER on Makefiles: http://people.freebsd.org/~pgj/for_review/2008-08-21/html/policies.html Draft of section (5.2) Contributed Software: http://people.freebsd.org/~pgj/for_review/2008-08-21/html/policies-contributed.html Diff for the curious: http://people.freebsd.org/~pgj/for_review/2008-08-21/books.developers-handbook.policies.diff Thank you in advance. Cheers, :g [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=docs%2F126030 [2] http://www.freebsd.org/doc/en/books/developers-handbook [3] http://wiki.freebsd.org/SubversionPrimer/VendorImports From nikhil.rao at intel.com Mon Aug 25 06:52:55 2008 From: nikhil.rao at intel.com (Rao, Nikhil) Date: Mon Aug 25 06:53:01 2008 Subject: pmap->pm_stats.resident_count In-Reply-To: <12A5C15467D5B94F8E0FF265D9498ADD0383F1CA@orsmsx419.amr.corp.intel.com> References: <20080818120021.751FB106568E@hub.freebsd.org> <12A5C15467D5B94F8E0FF265D9498ADD0383F1CA@orsmsx419.amr.corp.intel.com> Message-ID: <12A5C15467D5B94F8E0FF265D9498ADD038AA0E9@orsmsx419.amr.corp.intel.com> vm_daemon() looks at pmap->pm_stats.resident_count in the pmap structure using vmspace_resident_count() which calls pmap_resident_count(), pm_stats.resident_count is also incremented for device memory either if the device memory has been mapped using pmap_object_init_pt or using pmap_enter. Since these pages do not belong to memory that is managed by the kernel, they should not really be accounted in the if check below in vm_pageout.c ? if (limit >= 0 && size >= limit) { 1593 vm_pageout_map_deactivate_pages( 1594 &p->p_vmspace->vm_map, limit); 1595 } Is my understanding correct ? What do the members of this list think ? Thanks, Nikhil From vasanth.raonaik at gmail.com Mon Aug 25 12:42:34 2008 From: vasanth.raonaik at gmail.com (vasanth raonaik) Date: Mon Aug 25 12:42:42 2008 Subject: netstat: kvm_read: Bad address Message-ID: Hello Hackers, I am facing with this Issue. Though netstat -a does show some output but the error is consistently seen. Does any one has some pointers to the cause and fix for the same. Thanks, Vasanth From kris at FreeBSD.org Mon Aug 25 12:49:11 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Mon Aug 25 12:49:18 2008 Subject: netstat: kvm_read: Bad address In-Reply-To: References: Message-ID: <48B2AA41.4070608@FreeBSD.org> vasanth raonaik wrote: > Hello Hackers, > > I am facing with this Issue. Though netstat -a does show some output but the > error is consistently seen. Does any one has some pointers to the cause and > fix for the same. It is usually caused when your libkvm and/or netstat binary was compiled against different versions of the sources than your kernel. Rebuild world to fix it. Kris From koitsu at FreeBSD.org Mon Aug 25 12:49:31 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Mon Aug 25 12:49:47 2008 Subject: netstat: kvm_read: Bad address In-Reply-To: References: Message-ID: <20080825124931.GA78966@eos.sc1.parodius.com> On Mon, Aug 25, 2008 at 05:39:52PM +0530, vasanth raonaik wrote: > Hello Hackers, > > I am facing with this Issue. Though netstat -a does show some output but the > error is consistently seen. Does any one has some pointers to the cause and > fix for the same. I've seen this message when a user upgrades the kernel to newer sources (e.g. csup/cvsup), and rebuilds/reinstalls the kernel, but **does not** rebuild/reinstall userland program (e.g. world). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From olivier at gid0.org Mon Aug 25 13:20:03 2008 From: olivier at gid0.org (Olivier SMEDTS) Date: Mon Aug 25 13:20:11 2008 Subject: Call for testers - new ichwd ids Message-ID: <367b2c980808250552i630dd176wf500bb83960f64ed@mail.gmail.com> Hello hackers, If you have an Intel ICH chipset and the ichwd driver doesn't work for you, please test this patch : http://www.freebsd.org/cgi/query-pr.cgi?prp=126736-1-txt&n=/PATCH It adds new PCI IDs to the ichwd driver. It has been tested on an ICH10R-based motherboard (Asus P5Q3 Deluxe). The watchdog is detected and works (don't forget watchdogd_enable="YES" in /etc/rc.conf). See http://www.freebsd.org/cgi/query-pr.cgi?pr=126736 for more details. Olivier -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: olivier@gid0.org - against HTML email & vCards X www: http://www.gid0.org - against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." From vasanth.raonaik at gmail.com Mon Aug 25 13:52:20 2008 From: vasanth.raonaik at gmail.com (vasanth raonaik) Date: Mon Aug 25 13:52:28 2008 Subject: netstat: kvm_read: Bad address In-Reply-To: <20080825124931.GA78966@eos.sc1.parodius.com> References: <20080825124931.GA78966@eos.sc1.parodius.com> Message-ID: Both kernel and utility are in sync. Any more ideas? On Mon, Aug 25, 2008 at 6:19 PM, Jeremy Chadwick wrote: > On Mon, Aug 25, 2008 at 05:39:52PM +0530, vasanth raonaik wrote: > > Hello Hackers, > > > > I am facing with this Issue. Though netstat -a does show some output but > the > > error is consistently seen. Does any one has some pointers to the cause > and > > fix for the same. > > I've seen this message when a user upgrades the kernel to newer sources > (e.g. csup/cvsup), and rebuilds/reinstalls the kernel, but **does not** > rebuild/reinstall userland program (e.g. world). > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From koitsu at FreeBSD.org Mon Aug 25 14:42:47 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Mon Aug 25 14:44:32 2008 Subject: netstat: kvm_read: Bad address In-Reply-To: References: <20080825124931.GA78966@eos.sc1.parodius.com> Message-ID: <20080825144246.GA88631@eos.sc1.parodius.com> On Mon, Aug 25, 2008 at 07:22:19PM +0530, vasanth raonaik wrote: > Both kernel and utility are in sync. Any more ideas? > > On Mon, Aug 25, 2008 at 6:19 PM, Jeremy Chadwick wrote: > > > On Mon, Aug 25, 2008 at 05:39:52PM +0530, vasanth raonaik wrote: > > > Hello Hackers, > > > > > > I am facing with this Issue. Though netstat -a does show some output but > > the > > > error is consistently seen. Does any one has some pointers to the cause > > and > > > fix for the same. > > > > I've seen this message when a user upgrades the kernel to newer sources > > (e.g. csup/cvsup), and rebuilds/reinstalls the kernel, but **does not** > > rebuild/reinstall userland program (e.g. world). Nope, don't have any. Others will have to help. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From jhb at freebsd.org Mon Aug 25 20:05:03 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Aug 25 20:05:09 2008 Subject: MFC of r180753: ABI problems? In-Reply-To: <20080823.155034.1260392773.imp@bsdimp.com> References: <200808212351.13464.max@love2party.net> <200808230742.10902.jhb@freebsd.org> <20080823.155034.1260392773.imp@bsdimp.com> Message-ID: <200808251040.41587.jhb@freebsd.org> On Saturday 23 August 2008 05:50:34 pm M. Warner Losh wrote: > In message: <200808230742.10902.jhb@freebsd.org> > John Baldwin writes: > : On Saturday 23 August 2008 02:42:09 am M. Warner Losh wrote: > : > In message: <200808212351.13464.max@love2party.net> > : > > : > Max Laier writes: > : > : Hi, > : > : > : > : I'm wondering how to merge r180753 to stable/7 as luoqi@ has indicated > : > : that he doesn't have time to take care of it right now. > : > : > : > : It seems that changing the size of pcicfgregs (aka struct pcicfg) which > : > : is part of struct pci_devinfo is out of the question, right? Ideas where > : > : to store the HT related state or how to avoid storing the state are > : > : welcome. > : > : > : > : The merge result is attached for reference. This fix is essential for > : > : many nforce based boards from ASUS which are rather common, I'm afraid. > : > : So it would be good to have this in 7.1/6.4, I think. > : > > : > I think this is OK. > : > > : > pcicfgregs is an internal to pci implementation detail. You've added > : > it at the end, so any leakage of the offsets won't matter. All > : > subclasses of pci would be affected. Internal to the kernel isn't all > : > that interesting, since they are all compiled at the same time. This > : > would only matter for modules. Cardbus and acpi would be the only > : > modules affected. That would mean you couldn't boot a 7.0 kernel with > : > a 7.1 set of modules or vice versa. I'm not sure that is actually > : > going to work anyway... > : > : ACPI (and OFW's) PCI bus code isn't going to care, and I doubt cardbus is > : either. Hmm, actually, cardbus doesn't, but ACPI actually does (acpi_pci > > CardBus' does because it creates a slightly larger pcicfgreg per device... I thought it did but couldn't find it in the code. ACPI is basically doing the same thing. -- John Baldwin From jhb at freebsd.org Mon Aug 25 20:05:19 2008 From: jhb at freebsd.org (John Baldwin) Date: Mon Aug 25 20:05:32 2008 Subject: netstat: kvm_read: Bad address In-Reply-To: References: Message-ID: <200808251122.23325.jhb@freebsd.org> On Monday 25 August 2008 08:09:52 am vasanth raonaik wrote: > Hello Hackers, > > I am facing with this Issue. Though netstat -a does show some output but the > error is consistently seen. Does any one has some pointers to the cause and > fix for the same. Some parts of netstat still use direct kvm access to read kernel variables instead of sysctls for live kernels. If it tries to walk a linked list while the list is being changed, then it can end up following a free'd pointer and get this error. Is the system doing something like adding and deleting lots of psuedo-interfaces, addresses, etc.? -- John Baldwin From sobomax at FreeBSD.org Mon Aug 25 21:35:18 2008 From: sobomax at FreeBSD.org (Maxim Sobolev) Date: Mon Aug 25 21:35:46 2008 Subject: sun4v arch In-Reply-To: <48B0BEC7.1070806@FreeBSD.org> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> Message-ID: <48B3259E.8070601@FreeBSD.org> Maxim Sobolev wrote: > Peter Jeremy wrote: >> Is there a summary of the open issues somewhere? There are no sun4v >> PRs open. http://wiki.freebsd.org/FreeBSD/sun4v effectively hasn't >> been touched since November 2006 and suggests that the only critical >> issue is lack of serial port support. > > There is a better interpretation, which is that the only critical issue > is lack of real users for this port, not lack of serial port support :). Just to clarify a bit - my point was not to suggest that port is irrelevant, or that the FreeBSD should not go there. In fact I believe on contrary from what I know sun4v is good as a testbed for the future of multi-processor architectures today - definitely we will see ever increasing number of cores in commodity Intel/AMD servers in few years from now. So that in that sense sun4v work is very important if the FreeBSD project wants to keep ahead of things, not catching-up later. However, realistically immaturity of the port as well as scarcity of hardware limits number of users severely. Therefore, absence of PRs should not be surprising to anyone. -Maxim From gabor at kovesdan.org Tue Aug 26 18:25:11 2008 From: gabor at kovesdan.org (Gabor Kovesdan) Date: Tue Aug 26 18:30:53 2008 Subject: CFT: BSD grep Message-ID: <48B44A7D.3070108@kovesdan.org> Hello all, I've reviewed BSD grep based on your comments and the bug reports I received. The new version is committed to the ports tree as textproc/bsdgrep and there is a base patch available: http://kovesdan.org/patches/grep-base.diff I've asked portmgr to test my patch on pointyhat if they have available resources, but haven't got an answer yet. In the meantime, I'd like to ask for your comments and feedback on BSD grep. Currently, it is supposed to be highly compatible with GNU grep, except from some differences in the handling of the regular expressions. This comes from the different manners in the GNU regex library and in our regex library, thus it would be very difficult to fix at the level of grep. For example, GNU grep accepts empty subexpressions in regexes, like "(|b)", but BSD grep does not. I don't know how often such non-standard constructions are used, we need to see the results of a portbuild first, but I know that there are some in portmaster. That's why I CC'd Doug, I'm interested in his comments. There are another question to discuss. GNU grep supports -P for Perl regexes based on PCRE. This is not available in FreeBSD, though, but I'd be glad to add it to BSD grep. This would require us to import PCRE to base. It is BSD-licensed and maybe other tools would make use of it in the future. I don't know how this can cooperate with the ports version and how difficult it would be to maintain it in base. I remember that Perl was removed from base due to this overhead. What do you think about this? I've CC'd krion@, the maintainer of devel/pcre, maybe he can comment on this. Thanks, Gabor From andenore at freebsd.org Tue Aug 26 21:23:50 2008 From: andenore at freebsd.org (Anders Nore) Date: Tue Aug 26 21:23:57 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: <7d6fde3d0808222236t45103e4eseb8f174ffb89fdca@mail.gmail.com> References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> <7d6fde3d0808222236t45103e4eseb8f174ffb89fdca@mail.gmail.com> Message-ID: On Sat, 23 Aug 2008 07:36:02 +0200, Garrett Cooper wrote: > > How about this? > > For standalone packages, specify: > > Makefile.inc <-- redefine variables here. > pkg_install/ <-- sources go here. > > Seems like a simple solution ;). > > As for diff, you probably what to use: > > --exclude-from=SCM_patterns.txt > > where SCM_patterns.txt consists of: > -------------- > CVS > .git > .svn > .CC > -------------- > ... etc. > > As for patch, `patch -p0 < pkg_install.patch' does the trick if you do > `diff -Naur .'. > > Cheers and good work on finishing off this awesome task. I'll gladly > write up tests for you if you like =], > -Garrett I've been making a lot of mistakes trying to make correct patches, but I think I finally got a hang of it now :) I'd really appreciate some tests if you're willing to write some. I've also discovered two bugs in all -CURRENT, -RELENG_7 and -RELENG_7_0 of pkg_install: 1. Bug in pkg_info -W, it does not handle empty @cwd's correctly in the packinglist, so if you have any packages with an empty @cwd before the files listed it will not show as installed by a package. e.g., if you have the kdeadmin-4.1.0 package installed, one of the files it installs is `/usr/local/kde4/libdata/ldconfig/kdeadmin4' but running `pkg_info -W /usr/local/kde4/libdata/ldconfig/kdeadmin4' will not show that it installed by kdeadmin-4.1.0. 2. Bug in pkg_add, adding two packages where the first package recursively pkg_add's dependencies using slave mode will cause an `pkg_add: fatal error during execution: getcwd'. Because it doesn't save and recover previous working directories correctly. e.g., if you delete packages "joe-3.5,1", "gettext-0.16.1_3" and "zip-2.32", and run `pkg_add -r joe zip' this error will occur as joe depends on gettext. If you run `pkg_add -r zip joe' this error will not occur. Here's a patch for these errors: http://home.no.net/andenore/patches/pkg_install_bugfix-2008-08-26_RELENG_7.diff Can someone confirm these bugs, and if the patch is suitable? Thanks a bunch, Anders Nore From yanefbsd at gmail.com Wed Aug 27 00:32:10 2008 From: yanefbsd at gmail.com (Garrett Cooper) Date: Wed Aug 27 00:32:17 2008 Subject: pkg_improved GSoC 2008 finished In-Reply-To: References: <1d3ed48c0808211456h779bec94n9b6597c66f7741b2@mail.gmail.com> <1d3ed48c0808211500i4445b443t4a67da7cf514adaa@mail.gmail.com> <7d6fde3d0808222236t45103e4eseb8f174ffb89fdca@mail.gmail.com> Message-ID: <7d6fde3d0808261732w2dba8451ufd6683bc08d55a85@mail.gmail.com> On Tue, Aug 26, 2008 at 2:18 PM, Anders Nore wrote: > On Sat, 23 Aug 2008 07:36:02 +0200, Garrett Cooper > wrote: >> >> How about this? >> >> For standalone packages, specify: >> >> Makefile.inc <-- redefine variables here. >> pkg_install/ <-- sources go here. >> >> Seems like a simple solution ;). >> >> As for diff, you probably what to use: >> >> --exclude-from=SCM_patterns.txt >> >> where SCM_patterns.txt consists of: >> -------------- >> CVS >> .git >> .svn >> .CC >> -------------- >> ... etc. >> >> As for patch, `patch -p0 < pkg_install.patch' does the trick if you do >> `diff -Naur .'. >> >> Cheers and good work on finishing off this awesome task. I'll gladly >> write up tests for you if you like =], >> -Garrett > > > I've been making a lot of mistakes trying to make correct patches, but I > think I finally got a hang of it now :) > I'd really appreciate some tests if you're willing to write some. > > I've also discovered two bugs in all -CURRENT, -RELENG_7 and -RELENG_7_0 of > pkg_install: > > 1. Bug in pkg_info -W, it does not handle empty @cwd's correctly in the > packinglist, so if you have any packages with an empty @cwd before the files > listed it will not show as installed by a package. > e.g., if you have the kdeadmin-4.1.0 package installed, one of the files it > installs is `/usr/local/kde4/libdata/ldconfig/kdeadmin4' but running > `pkg_info -W /usr/local/kde4/libdata/ldconfig/kdeadmin4' will not show that > it installed by kdeadmin-4.1.0. > > 2. Bug in pkg_add, adding two packages where the first package recursively > pkg_add's dependencies using slave mode will cause an `pkg_add: fatal error > during execution: getcwd'. Because it doesn't save and recover previous > working directories correctly. > e.g., if you delete packages "joe-3.5,1", "gettext-0.16.1_3" and "zip-2.32", > and run `pkg_add -r joe zip' this error will occur as joe depends on > gettext. If you run `pkg_add -r zip joe' this error will not occur. > > Here's a patch for these errors: > http://home.no.net/andenore/patches/pkg_install_bugfix-2008-08-26_RELENG_7.diff > Can someone confirm these bugs, and if the patch is suitable? > > > Thanks a bunch, > Anders Nore I'll look through the diff at a later date to determine what new features you've added, but I'll be sure to add regression tests soon via Python / dev-pynose (sometime tonight if at all possible -- automation and testing Cisco stuff is eating up a lot of my free time :(...). Cheers, -Garrett From ken at mthelicon.com Wed Aug 27 00:37:43 2008 From: ken at mthelicon.com (Pegasus Mc Cleaft) Date: Wed Aug 27 00:37:51 2008 Subject: Call for testers - new ichwd ids In-Reply-To: <367b2c980808250552i630dd176wf500bb83960f64ed@mail.gmail.com> References: <367b2c980808250552i630dd176wf500bb83960f64ed@mail.gmail.com> Message-ID: <200808270037.35273.ken@mthelicon.com> On Monday 25 August 2008 12:52:48 Olivier SMEDTS wrote: > Hello hackers, > > If you have an Intel ICH chipset and the ichwd driver doesn't work for > you, please test this patch : Oliver, Thanks for the patch, but sadly this didnt help the situation I have with my motherboard. It identifies the ICH9R chipset, but sadly looks like the motherboard company has disabled the watchdog action. I have already spoken to the motherboard producers and they sware they have not, but looking at the code I cant see any other explanation for the behavior. The motherboard is a Gigabyte GA-X48-DS5 Bios F7 (latest) Output is: ichwd0: on isa0 ichwd0: ICH WDT present but disabled in BIOS or hardware device_attach: ichwd0 attach returned 6 I looked at the datasheet for the ICH9 chipset and I believe they have a pull-up on the speaker line that is telling the chip to disable the watchdog functions. Peg From ache at nagual.pp.ru Wed Aug 27 01:48:46 2008 From: ache at nagual.pp.ru (Andrey Chernov) Date: Wed Aug 27 02:22:28 2008 Subject: CFT: BSD grep In-Reply-To: <48B44A7D.3070108@kovesdan.org> References: <48B44A7D.3070108@kovesdan.org> Message-ID: <20080827013221.GA82176@nagual.pp.ru> On Tue, Aug 26, 2008 at 08:25:01PM +0200, Gabor Kovesdan wrote: > Hello all, > > I've reviewed BSD grep based on your comments and the bug reports I > received. The new version is committed to the ports tree as > textproc/bsdgrep and there is a base patch available: > http://kovesdan.org/patches/grep-base.diff Just from quick looking at the sources... This code looks suspicious: wend = sscanf(&l->dat[pmatch.rm_eo], "%lc", &wend); Perhaps it should be if (sscanf(&l->dat[pmatch.rm_eo], "%lc", &wend) != 1) r = REG_NOMATCH; The next thing is that perhaps each r = REG_NOMATCH; case should be isolated from others in this block (with "else if"?) F.e. failing mbstowcs() can leave buffer for sscanf() in junk. wbegin = grep_malloc(mbstowcs(NULL, l->dat, pmatch.rm_so)); grep_malloc() here could terminate program for invalid mbstowcs() sequence, but really must set only r = REG_NOMATCH; Think about files which, for various reasons, may contain not only valid MB sequences. fgrepcomp() uses toupper()/tolower() while should use wide chars analogs (MB chars can be in the pattern too). There are also many other places where pattern treated as single chars one, fastcomp() etc. grep_cmp() compares single chars toupper(data[]) too. There must be no plain ctype usage in the whole data _and_ pattern handling code. -- http://ache.pp.ru/ From barry.boes at acciodata.com Wed Aug 27 03:55:25 2008 From: barry.boes at acciodata.com (Barry Boes) Date: Wed Aug 27 04:40:11 2008 Subject: kvm on amd64 - >6G? Message-ID: <18612.51201.285688.628405@gargle.gargle.HOWL> With the advent of ZFS, Solaris users are devoting 30G or more to their ARC caches today. If FreeBSD 8 is going to up the KVM size, is there a reason to not increase the limit to something that will not be reached in the lifetime of 8? 100GB? -Barry From olli at lurza.secnetix.de Wed Aug 27 10:00:08 2008 From: olli at lurza.secnetix.de (Oliver Fromme) Date: Wed Aug 27 10:00:54 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <18612.51201.285688.628405@gargle.gargle.HOWL> Message-ID: <200808270959.m7R9xOMo086923@lurza.secnetix.de> Barry Boes wrote: > With the advent of ZFS, Solaris users are devoting 30G or more to > their ARC caches today. If FreeBSD 8 is going to up the KVM size, is > there a reason to not increase the limit to something that will not be > reached in the lifetime of 8? 100GB? I think Alan Cox recently increased the kmem limit in 8-current from 1.5 GB to 7 GB, and the default is 4.2 GB. http://svn.freebsd.org/viewvc/base?view=revision&revision=180311 I don't know if this will be MFCed. It will not be in 7.1-Release; it's too late for that. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Gesch?ftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M?n- chen, HRB 125758, Gesch?ftsf?hrer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From kris at FreeBSD.org Wed Aug 27 10:22:46 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Wed Aug 27 10:22:52 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <18612.51201.285688.628405@gargle.gargle.HOWL> References: <18612.51201.285688.628405@gargle.gargle.HOWL> Message-ID: <48B52AEE.9080205@FreeBSD.org> Barry Boes wrote: > With the advent of ZFS, Solaris users are devoting 30G or more to > their ARC caches today. If FreeBSD 8 is going to up the KVM size, is > there a reason to not increase the limit to something that will not be > reached in the lifetime of 8? 100GB? It's easily configurable on HEAD. From an email alc sent me: ---- This: Index: amd64/include/pmap.h =================================================================== --- amd64/include/pmap.h (revision 180373) +++ amd64/include/pmap.h (working copy) @@ -111,7 +111,7 @@ /* Initial number of kernel page tables. */ #ifndef NKPT -#define NKPT 32 +#define NKPT 1023 #endif #define NKPML4E 1 /* number of kernel PML4 slots */ Index: amd64/include/vmparam.h =================================================================== --- amd64/include/vmparam.h (revision 180373) +++ amd64/include/vmparam.h (working copy) @@ -163,7 +163,7 @@ */ #define VM_MAX_KERNEL_ADDRESS KVADDR(KPML4I, NPDPEPG-1, NPDEPG-1, NPTEPG-1) -#define VM_MIN_KERNEL_ADDRESS KVADDR(KPML4I, NPDPEPG-7, 0, 0) +#define VM_MIN_KERNEL_ADDRESS KVADDR(KPML4I, 0, 0, 0) #define DMAP_MIN_ADDRESS KVADDR(DMPML4I, 0, 0, 0) #define DMAP_MAX_ADDRESS KVADDR(DMPML4I+1, 0, 0, 0) will now get you this: vm.kvm_free: 547729960960 vm.kvm_size: 549755809792 on HEAD. :-) ---- Kris From doconnor at gsoft.com.au Wed Aug 27 11:45:13 2008 From: doconnor at gsoft.com.au (Daniel O'Connor) Date: Wed Aug 27 11:45:21 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <48B52AEE.9080205@FreeBSD.org> References: <18612.51201.285688.628405@gargle.gargle.HOWL> <48B52AEE.9080205@FreeBSD.org> Message-ID: <200808272042.43260.doconnor@gsoft.com.au> On Wed, 27 Aug 2008, Kris Kennaway wrote: > will now get you this: > > vm.kvm_free: 547729960960 > vm.kvm_size: 549755809792 > > on HEAD. :-) Holy fat cache Batman! Any chance it could be made a tunable? -- 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 GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part. Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080827/877a1845/attachment.pgp From kris at FreeBSD.org Wed Aug 27 11:51:46 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Wed Aug 27 11:51:53 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <200808272042.43260.doconnor@gsoft.com.au> References: <18612.51201.285688.628405@gargle.gargle.HOWL> <48B52AEE.9080205@FreeBSD.org> <200808272042.43260.doconnor@gsoft.com.au> Message-ID: <48B53FCB.4000107@FreeBSD.org> Daniel O'Connor wrote: > On Wed, 27 Aug 2008, Kris Kennaway wrote: >> will now get you this: >> >> vm.kvm_free: 547729960960 >> vm.kvm_size: 549755809792 >> >> on HEAD. :-) > > Holy fat cache Batman! > > Any chance it could be made a tunable? > I don't know what the impact might be of changing these constants to runtime variable accesses, if they are in a critical path somewhere. Kris From kris at FreeBSD.org Wed Aug 27 13:56:42 2008 From: kris at FreeBSD.org (Kris Kennaway) Date: Wed Aug 27 13:56:48 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <18613.21419.16360.120533@gargle.gargle.HOWL> References: <18612.51201.285688.628405@gargle.gargle.HOWL> <48B52AEE.9080205@FreeBSD.org> <18613.21419.16360.120533@gargle.gargle.HOWL> Message-ID: <48B55D13.1060609@FreeBSD.org> Barry Boes wrote: > I could apply such a patch to my servers, but there are two disadvantages : > o who wants to apply kernel patches to mission critical servers? Isn't > that a linux thing (joke!) A trivial tweak would let you set both parameters in your kernel configuration as an option. > o what about apps like the linuxulator that might not stand for this? Why do you think they will care? > On the tunable option : with today's kmem_size and kmem_size_max > tunables, would there also be a need to tune the portion of address > space available to kmem? Yes, it is still suballocated out of the kernel map. Kris From barry.boes at acciodata.com Wed Aug 27 13:16:29 2008 From: barry.boes at acciodata.com (Barry Boes) Date: Wed Aug 27 14:17:11 2008 Subject: kvm on amd64 - >6G? In-Reply-To: <48B52AEE.9080205@FreeBSD.org> References: <18612.51201.285688.628405@gargle.gargle.HOWL> <48B52AEE.9080205@FreeBSD.org> Message-ID: <18613.21419.16360.120533@gargle.gargle.HOWL> I could apply such a patch to my servers, but there are two disadvantages : o who wants to apply kernel patches to mission critical servers? Isn't that a linux thing (joke!) o what about apps like the linuxulator that might not stand for this? On the tunable option : with today's kmem_size and kmem_size_max tunables, would there also be a need to tune the portion of address space available to kmem? Thanks, Barry Kris Kennaway writes: > Barry Boes wrote: > > With the advent of ZFS, Solaris users are devoting 30G or more to > > their ARC caches today. If FreeBSD 8 is going to up the KVM size, is > > there a reason to not increase the limit to something that will not be > > reached in the lifetime of 8? 100GB? > > It's easily configurable on HEAD. From an email alc sent me: > > ---- > This: > > Index: amd64/include/pmap.h > =================================================================== > --- amd64/include/pmap.h (revision 180373) > +++ amd64/include/pmap.h (working copy) > @@ -111,7 +111,7 @@ > > /* Initial number of kernel page tables. */ > #ifndef NKPT > -#define NKPT 32 > +#define NKPT 1023 > #endif > > #define NKPML4E 1 /* number of kernel PML4 > slots */ > Index: amd64/include/vmparam.h > =================================================================== > --- amd64/include/vmparam.h (revision 180373) > +++ amd64/include/vmparam.h (working copy) > @@ -163,7 +163,7 @@ > */ > > #define VM_MAX_KERNEL_ADDRESS KVADDR(KPML4I, NPDPEPG-1, > NPDEPG-1, NPTEPG-1) > -#define VM_MIN_KERNEL_ADDRESS KVADDR(KPML4I, NPDPEPG-7, 0, 0) > +#define VM_MIN_KERNEL_ADDRESS KVADDR(KPML4I, 0, 0, 0) > > #define DMAP_MIN_ADDRESS KVADDR(DMPML4I, 0, 0, 0) > #define DMAP_MAX_ADDRESS KVADDR(DMPML4I+1, 0, 0, 0) > > will now get you this: > > vm.kvm_free: 547729960960 > vm.kvm_size: 549755809792 > > on HEAD. :-) > ---- > > Kris From jingshao at teekoo.com Wed Aug 27 17:02:12 2008 From: jingshao at teekoo.com (Jingshao Chen) Date: Wed Aug 27 17:02:20 2008 Subject: Recommend literature for beginner programer In-Reply-To: <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> References: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> <20080819070253.GH87062@nexus.in-nomine.org> <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> Message-ID: <20080827160819.GA770@teekoo.com> Hi, Since you have been unix admin for a few years, I guess you probably have some experience with C programming. This book is more advanced, but it is a really good one. Advanced Programming in the UNIX Environment: Paperback Edition (2nd Edition) http://www.amazon.com/Advanced-Programming-UNIX-Environment-Addison-Wesley/dp/0321525949/ref=sr_1_1?ie=UTF8&s=books&qid=1219855535&sr=1-1 Thanks, Jingshao On Tue, Aug 19, 2008 at 09:36:12AM +0200, Rudi Kramer - MWEB wrote: > > > Ruigrok van der Werven > > > > What is your goal? > > I learn how FreeBSD is put together and eventually contribute code to > the base. > > Rudi > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From stephen at math.missouri.edu Wed Aug 27 19:02:02 2008 From: stephen at math.missouri.edu (Stephen Montgomery-Smith) Date: Wed Aug 27 19:02:08 2008 Subject: Recommend literature for beginner programer In-Reply-To: <20080827160819.GA770@teekoo.com> References: <39DC135F7F0571489196E0B6F5D58B4A03B46055@MWBEXCH.mweb.com> <20080819070253.GH87062@nexus.in-nomine.org> <39DC135F7F0571489196E0B6F5D58B4A03B46056@MWBEXCH.mweb.com> <20080827160819.GA770@teekoo.com> Message-ID: <48B59B4B.9050500@math.missouri.edu> Jingshao Chen wrote: > Hi, > > Since you have been unix admin for a few years, I guess you probably have > some experience with C programming. This book is more advanced, but it > is a really good one. > > Advanced Programming in the UNIX Environment: Paperback Edition (2nd Edition) > http://www.amazon.com/Advanced-Programming-UNIX-Environment-Addison-Wesley/dp/0321525949/ref=sr_1_1?ie=UTF8&s=books&qid=1219855535&sr=1-1 > > Thanks, > Jingshao I have read some other books by (the late) Richard Stevens, and he writes really good books. Some of the info is slightly outdated or inapplicable for FreeBSD, but those finer points you can get from the man pages. But for getting a good overview, his writing style is so easy to follow. From peterjeremy at optushome.com.au Thu Aug 28 11:49:46 2008 From: peterjeremy at optushome.com.au (Peter Jeremy) Date: Thu Aug 28 11:50:29 2008 Subject: sun4v arch In-Reply-To: <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> References: <136a340a0808220719t3a170786s7fd4bcb662d0b981@mail.gmail.com> <48AED560.8010001@FreeBSD.org> <20080822225510.GI32539@server.vk2pj.dyndns.org> <48B0BEC7.1070806@FreeBSD.org> <7d6fde3d0808232039i78fadb9bu7373e1c36f4f37a1@mail.gmail.com> <20080824034055.GB12515@soaustin.net> <20080824042339.GM32539@server.vk2pj.dyndns.org> <3c1674c90808232139k76f8091bw34aa0f9b71437023@mail.gmail.com> Message-ID: <20080828114942.GN33600@server.vk2pj.dyndns.org> On 2008-Aug-23 21:39:34 -0700, Kip Macy wrote: >There really isn't any magic to bringing up a port. You compile it, >install it, and then run it until it breaks. Once it breaks you spend >a lot of time instrumenting the code to track down what went wrong. About what I expected. I've just bumped into your bsdtalk interview: http://cisx1.uma.maine.edu/~wbackman/bsdtalk/bsdtalk086.mp3 This appears to give a useful overview into the sun4v port. One thing you mention is that you'd started work on a virtual network driver. How far did this get and can you point me to the code, It seems that the latest OpenBSD runs on sun4v. I haven't investigated how well supported it is. -- Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20080828/d35a5425/attachment.pgp From killing at multiplay.co.uk Thu Aug 28 12:30:59 2008 From: killing at multiplay.co.uk (Steven Hartland) Date: Thu Aug 28 12:31:06 2008 Subject: lighttpd failing to accept new connections ( connection reset ) Message-ID: We're using lighttpd here for a new project and we're having issues where by it simply stops processing after a 1-2 days. Having looked at it in some detail this morning it seems that the kernel is resetting the connection without notifying the lighttpd process there is a new connection attempt. I assume that the listen queue is full but why kevent is not notifying lighttpd that there are outstanding events is beyond me. The following is a truss of the process which is currently in this state:- kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) gettimeofday({1219920575.149428},0x0) = 0 (0x0) kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) gettimeofday({1219920576.150443},0x0) = 0 (0x0) ktrace of the operation as well:- 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) 28363 lighttpd GIO fd 6 wrote 0 bytes "" 28363 lighttpd GIO fd 6 read 0 bytes "" 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) 28363 lighttpd GIO fd 6 wrote 0 bytes "" 28363 lighttpd GIO fd 6 read 0 bytes "" 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) 28363 lighttpd GIO fd 6 wrote 0 bytes "" 28363 lighttpd GIO fd 6 read 0 bytes "" 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) 28363 lighttpd GIO fd 6 wrote 0 bytes "" 28363 lighttpd GIO fd 6 read 0 bytes "" 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) 28363 lighttpd GIO fd 6 wrote 0 bytes "" 28363 lighttpd GIO fd 6 read 0 bytes "" 28363 lighttpd RET kevent 0 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) 28363 lighttpd RET gettimeofday 0 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) tcpdump shows:- 12:10:29.475255 IP (tos 0x10, ttl 64, id 9536, offset 0, flags [DF], proto: TCP (6), length: 64) client.61224 > server.80: S, cksum 0x6d22 (incorrect (-> 0xedfa), 291994449:291994449(0) win 65535 12:10:29.481396 IP (tos 0x0, ttl 61, id 25503, offset 0, flags [DF], proto: TCP (6), length: 60) server.80 > client.61224: S, cksum 0xbf22 (correct), 3444532576:3444532576(0) ack 291994450 win 65535 12:10:29.481419 IP (tos 0x10, ttl 64, id 9538, offset 0, flags [DF], proto: TCP (6), length: 52) client.61224 > server.80: ., cksum 0x6d16 (incorrect (-> 0x6bd2), 1:1(0) ack 1 win 33304 12:10:29.487519 IP (tos 0x10, ttl 61, id 25504, offset 0, flags [DF], proto: TCP (6), length: 40) server.80 > client.61224: R, cksum 0x20c7 (correct), 3444532577:3444532577(0) win 0 This may have been raised before back 2003 as bug kern/57380 but it was closed after no response from the reporter. Another possible issues related to this is:- http://trac.lighttpd.net/trac/ticket/1734 I've currently got one of the production machines offline with this error ( hence the important flag ) in the hope that someone can suggest a test which will shed more light on the issue before I restart it. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From koitsu at FreeBSD.org Thu Aug 28 13:27:01 2008 From: koitsu at FreeBSD.org (Jeremy Chadwick) Date: Thu Aug 28 13:32:51 2008 Subject: lighttpd failing to accept new connections ( connection reset ) In-Reply-To: References: Message-ID: <20080828131059.GA46853@icarus.home.lan> On Thu, Aug 28, 2008 at 01:13:57PM +0100, Steven Hartland wrote: > We're using lighttpd here for a new project and we're having issues > where by it simply stops processing after a 1-2 days. > > Having looked at it in some detail this morning it seems that > the kernel is resetting the connection without notifying the > lighttpd process there is a new connection attempt. I assume > that the listen queue is full but why kevent is not notifying > lighttpd that there are outstanding events is beyond me. > > > The following is a truss of the process which is currently in > this state:- > kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) > gettimeofday({1219920575.149428},0x0) = 0 (0x0) > kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) > gettimeofday({1219920576.150443},0x0) = 0 (0x0) > > ktrace of the operation as well:- > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > > > tcpdump shows:- > 12:10:29.475255 IP (tos 0x10, ttl 64, id 9536, offset 0, flags [DF], > proto: TCP (6), length: 64) client.61224 > server.80: S, cksum 0x6d22 > (incorrect (-> 0xedfa), 291994449:291994449(0) win 65535 1460,nop,wscale 1,nop,nop,timestamp 3661727139 0,sackOK,eol> > 12:10:29.481396 IP (tos 0x0, ttl 61, id 25503, offset 0, flags [DF], > proto: TCP (6), length: 60) server.80 > client.61224: S, cksum 0xbf22 > (correct), 3444532576:3444532576(0) ack 291994450 win 65535 1460,nop,wscale 9,sackOK,timestamp 3136311843 3661727139> > 12:10:29.481419 IP (tos 0x10, ttl 64, id 9538, offset 0, flags [DF], > proto: TCP (6), length: 52) client.61224 > server.80: ., cksum 0x6d16 > (incorrect (-> 0x6bd2), 1:1(0) ack 1 win 33304 3661727145 3136311843> > 12:10:29.487519 IP (tos 0x10, ttl 61, id 25504, offset 0, flags [DF], > proto: TCP (6), length: 40) server.80 > client.61224: R, cksum 0x20c7 > (correct), 3444532577:3444532577(0) win 0 > > This may have been raised before back 2003 as bug kern/57380 > but it was closed after no response from the reporter. > > Another possible issues related to this is:- > http://trac.lighttpd.net/trac/ticket/1734 > > > I've currently got one of the production machines offline > with this error ( hence the important flag ) in the hope > that someone can suggest a test which will shed more light > on the issue before I restart it. Can you change the polling method in lighttpd to use poll or select instead of kqueue? This would help in determining if the problem is with the daemon itself or the kevent system. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From killing at multiplay.co.uk Thu Aug 28 15:36:15 2008 From: killing at multiplay.co.uk (Steven Hartland) Date: Thu Aug 28 15:36:21 2008 Subject: lighttpd failing to accept new connections ( connection reset ) / possible kqueue bug References: <20080828131059.GA46853@icarus.home.lan> Message-ID: <8A808063A5604856845574C05FE96E0C@multiplay.co.uk> ----- Original Message ----- From: "Jeremy Chadwick" > > Can you change the polling method in lighttpd to use poll or select > instead of kqueue? This would help in determining if the problem is > with the daemon itself or the kevent system. Yep already scheduled that change for our London node tomorrow morning. ATM we are seeing this issue every 1 - 2 days so it may take a little while before I can answer that question. I've had a look through the source and I can't see any reason why kevent would suddenly stop notifying the app that new connections are present. Event registration appears to only be done once on app startup and similarly unregisters are only done on shutdown, so my current thinking is there may be an problem with kqueue itself. I don't suppose your aware of any way to query the status of this in the kernel or app given I have a node in this "hung" state? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From rwatson at FreeBSD.org Thu Aug 28 22:28:44 2008 From: rwatson at FreeBSD.org (Robert Watson) Date: Thu Aug 28 22:28:59 2008 Subject: lighttpd failing to accept new connections ( connection reset ) In-Reply-To: References: Message-ID: On Thu, 28 Aug 2008, Steven Hartland wrote: > We're using lighttpd here for a new project and we're having issues where by > it simply stops processing after a 1-2 days. > > Having looked at it in some detail this morning it seems that the kernel is > resetting the connection without notifying the lighttpd process there is a > new connection attempt. I assume that the listen queue is full but why > kevent is not notifying lighttpd that there are outstanding events is beyond > me. The connections getting reset without application notification is a classic symptom of a full listen queue. A couple of questions: (1) What FreeBSD version? (2) Are you using accept filters? (3) If possibly, are you able to instrument lighthttpd so that you can trigger it to query SO_LISTENQLIMIT, SO_LISTENQLEN, and SO_LISTENINCQLEN on the listen socket once things have gone wrong? The respectively (and perhaps obviously) querye the current administrative limit on queue depth, the number queue depth on completed connections, and the current queue depth on incomplete connections. The last of these will only be used with accept filters on recent FreeBSD network stacks (since the syncache was added). Hopefully doing (3) will allow us to try to determine whether it's indeed the case that somehow the listen queue or event handling has gotten "wedged" in some way. In terms of analyzing the state of the machine -- if you have a kernel.debug around and are willing to do a bit of digging, the best thing to do would be to track down the listen socket and directly inspect it using kgdb to dump its field contents. This can be done on a live box by attaching kgdb to kernel memory using /dev/mem as the target device. You can find the kernel memory address of the listen socket by tracking it down in fstat -- a typical entry might look like this: root inetd 1158 9* internet stream tcp c5350000 So you can do a "print *(socket *)0xc5350000" to print out the socket structure once attached to /dev/mem. If you need more pointers on how to do this, send me a private e-mail and I can walk you through it in detail. Robert N M Watson Computer Laboratory University of Cambridge > > > The following is a truss of the process which is currently in > this state:- > kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) > gettimeofday({1219920575.149428},0x0) = 0 (0x0) > kevent(6,0x0,0,{},11096,{1.000000000}) = 0 (0x0) > gettimeofday({1219920576.150443},0x0) = 0 (0x0) > > ktrace of the operation as well:- > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > 28363 lighttpd GIO fd 6 wrote 0 bytes > "" > 28363 lighttpd GIO fd 6 read 0 bytes > "" > 28363 lighttpd RET kevent 0 > 28363 lighttpd CALL gettimeofday(0x7fffffffeb20,0) > 28363 lighttpd RET gettimeofday 0 > 28363 lighttpd CALL kevent(0x6,0,0,0x800e66000,0x2b58,0x7fffffffeb20) > > > tcpdump shows:- > 12:10:29.475255 IP (tos 0x10, ttl 64, id 9536, offset 0, flags [DF], proto: > TCP (6), length: 64) client.61224 > server.80: S, cksum 0x6d22 (incorrect (-> > 0xedfa), 291994449:291994449(0) win 65535 1,nop,nop,timestamp 3661727139 0,sackOK,eol> > 12:10:29.481396 IP (tos 0x0, ttl 61, id 25503, offset 0, flags [DF], proto: > TCP (6), length: 60) server.80 > client.61224: S, cksum 0xbf22 (correct), > 3444532576:3444532576(0) ack 291994450 win 65535 9,sackOK,timestamp 3136311843 3661727139> > 12:10:29.481419 IP (tos 0x10, ttl 64, id 9538, offset 0, flags [DF], proto: > TCP (6), length: 52) client.61224 > server.80: ., cksum 0x6d16 (incorrect (-> > 0x6bd2), 1:1(0) ack 1 win 33304 > 12:10:29.487519 IP (tos 0x10, ttl 61, id 25504, offset 0, flags [DF], proto: > TCP (6), length: 40) server.80 > client.61224: R, cksum 0x20c7 (correct), > 3444532577:3444532577(0) win 0 > > This may have been raised before back 2003 as bug kern/57380 > but it was closed after no response from the reporter. > > Another possible issues related to this is:- > http://trac.lighttpd.net/trac/ticket/1734 > > > I've currently got one of the production machines offline > with this error ( hence the important flag ) in the hope > that someone can suggest a test which will shed more light > on the issue before I restart it. > > Regards > Steve > > > ================================================ > This e.mail is private and confidential between Multiplay (UK) Ltd. and the > person or entity to whom it is addressed. In the event of misdirection, the > recipient is prohibited from using, copying, printing or otherwise > disseminating it or any information contained in it. > In the event of misdirection, illegible or incomplete transmission please > telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From killing at multiplay.co.uk Fri Aug 29 00:36:30 2008 From: killing at multiplay.co.uk (Steven Hartland) Date: Fri Aug 29 00:36:37 2008 Subject: lighttpd failing to accept new connections ( connection reset ) References: Message-ID: <78454DA58F8C48F8A31196BD2E407110@multiplay.co.uk> ----- Original Message ----- From: "Robert Watson" > The connections getting reset without application notification is a classic > symptom of a full listen queue. A couple of questions: Yep thats what I thought. > (1) What FreeBSD version? 7.0-RELEASE-p2 (amd64) > (2) Are you using accept filters? The modules there but not loaded, so no. > (3) If possibly, are you able to instrument lighthttpd so that you can trigger > it to query SO_LISTENQLIMIT, SO_LISTENQLEN, and SO_LISTENINCQLEN on the > listen socket once things have gone wrong? The respectively (and perhaps > obviously) querye the current administrative limit on queue depth, the > number queue depth on completed connections, and the current queue depth > on incomplete connections. The last of these will only be used with > accept filters on recent FreeBSD network stacks (since the syncache was > added). > > Hopefully doing (3) will allow us to try to determine whether it's indeed the > case that somehow the listen queue or event handling has gotten "wedged" in > some way. This should be possible, I'll have a look, assuming the kgdb stuff doesn't turn up the required results. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From stef-list at memberwebs.com Sat Aug 30 17:06:55 2008 From: stef-list at memberwebs.com (Stef) Date: Sat Aug 30 17:07:01 2008 Subject: kvm on amd64 - >6G? References: <18612.51201.285688.628405@gargle.gargle.HOWL> <48B52AEE.9080205@FreeBSD.org> <18613.21419.16360.120533@gargle.gargle.HOWL> Message-ID: <20080830164305.0658229C1BBA@mx.npubs.com> Barry Boes wrote: > I could apply such a patch to my servers, but there are two disadvantages : > o who wants to apply kernel patches to mission critical servers? Isn't > that a linux thing (joke!) Unfortunately it's not. There's a whole raft of patches (with PR's filed) that are required when you're using certain configurations of FreeBSD. In particular my 6.3 production servers require: * A bunch of patches to ataraid to prevent panics, make the raid work during failures etc... Many can be found here: http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting * Patch to the 4BSD scheduler to prevent regular deadlocks on all quad core systems I have access to: http://www.mail-archive.com/freebsd-hackers@freebsd.org/msg64390.html * Patch for fixing devfs to have proper behavior with symlinks in jails: http://www.freebsd.org/cgi/query-pr.cgi?pr=114057 And there are one or two other patches on some deployed systems (eg: 'multi ip jail patches'). I used to be in the no-patches-on-my-production-servers camp, but I've found that it was unrealistic and resulted in less stable systems. Cheers, Stef Walter