Re: Interactive tool for installing packages
Marin Atanasov Nikolov dna...@gmail.com wrote: in order to install the program, you need to: # git clone git://git.unix-heaven.org/public/pkg_add_it ... Surely, there's room for improvement, but that's a start.. :) Dunno about anyone else, but from my standpoint it would be a _big_ improvement to provide a more recent snapshot than the 6-month-old pkg_add_it-1.2.tar.gz on ftp.freebsd.org so one doesn't have to install git, with its boatload of dependencies*, to see the recent improvements. * The amount of stuff downloaded by cd /usr/ports/devel/git ; make fetch-recursive is, shall we say, impressive. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [PATCH] Simplify uart_bus_pci_probe
On Tue, Nov 9, 2010 at 10:29 PM, Marcel Moolenaar xcl...@mac.com wrote: On Nov 6, 2010, at 11:22 AM, Garrett Cooper wrote: Some of the logic could have been simplified in the probe. The proposed patch makes the detection process a tad bit more straightforward. Comments, review (and maybe a commit :P) are more than welcome :). The patch is logically wrong for non-ns8250 based UARTs. Leave the code as is. Hi Marcel, Is the layout of the pci_ns8250_ids PCI ID table correct then, as there are a large number of ns16550 chips and other non-ns8250 chips in the table? Thanks, -Garrett ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Interactive tool for installing packages
On Wed, Nov 10, 2010 at 10:01 AM, per...@pluto.rain.com wrote: Marin Atanasov Nikolov dna...@gmail.com wrote: in order to install the program, you need to: # git clone git://git.unix-heaven.org/public/pkg_add_it ... Surely, there's room for improvement, but that's a start.. :) Dunno about anyone else, but from my standpoint it would be a _big_ improvement to provide a more recent snapshot than the 6-month-old pkg_add_it-1.2.tar.gz on ftp.freebsd.org so one doesn't have to install git, with its boatload of dependencies*, to see the recent improvements. If you do not have git installed, you could still get the latest snapshot of pkg_add_it via the Cgit repo. [1] Currently the latest version of the program is tagged as RELEASE_1_3, so just go to [1] and get a compressed snapshot of the program, then extract and compile it. I'm planning to submit a PR to update the port soon, but before that I still need to finish a few things. Regards, Marin [1] http://git.unix-heaven.org/cgit.cgi/pkg_add_it/ * The amount of stuff downloaded by cd /usr/ports/devel/git ; make fetch-recursive is, shall we say, impressive. -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
kern.smp.topology
Hello! People. Who can explain the purpose of sysctl variable kern.smp.topology? What does it affect? It may take such values: 1 -Dual core with no sharing. 2 -No topology, all cpus are equal. 3 -Dual core with shared L2. 4 -quad core, shared l3 among each package, private l2. 5 -quad core, 2 dualcore parts on each package share l2. 6 -Single-core 2xHTT 7 -quad core with a shared l3, 8 threads sharing L2. default-Default, ask the system what it wants. Does it make sense to set its value manually, if I know that my CPU Core2Duo? How to do this, select a value? I not found this explanation in any of the official guides ... Thanks! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: kern.smp.topology
On 11/10/10 11:56, Ivan Klymenko wrote: Hello! People. Who can explain the purpose of sysctl variable kern.smp.topology? What does it affect? It may take such values: 1 -Dual core with no sharing. 2 -No topology, all cpus are equal. 3 -Dual core with shared L2. 4 -quad core, shared l3 among each package, private l2. 5 -quad core, 2 dualcore parts on each package share l2. 6 -Single-core 2xHTT 7 -quad core with a shared l3, 8 threads sharing L2. default-Default, ask the system what it wants. Does it make sense to set its value manually, if I know that my CPU Core2Duo? How to do this, select a value? I not found this explanation in any of the official guides ... Short answer is: you should not have to touch it, ever. Long answer: it's used mostly for testing ULE and debugging topology-related problems. It's even less relevant in recent kernels (9, 8-stable) where a better topology parser has been committed. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: kern.smp.topology
В Wed, 10 Nov 2010 12:20:45 +0100 Ivan Voras ivo...@freebsd.org пишет: On 11/10/10 11:56, Ivan Klymenko wrote: Hello! People. Who can explain the purpose of sysctl variable kern.smp.topology? What does it affect? It may take such values: 1 -Dual core with no sharing. 2 -No topology, all cpus are equal. 3 -Dual core with shared L2. 4 -quad core, shared l3 among each package, private l2. 5 -quad core, 2 dualcore parts on each package share l2. 6 -Single-core 2xHTT 7 -quad core with a shared l3, 8 threads sharing L2. default-Default, ask the system what it wants. Does it make sense to set its value manually, if I know that my CPU Core2Duo? How to do this, select a value? I not found this explanation in any of the official guides ... Short answer is: you should not have to touch it, ever. Long answer: it's used mostly for testing ULE and debugging topology-related problems. It's even less relevant in recent kernels (9, 8-stable) where a better topology parser has been committed. Thank you! I understood. :) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [PATCH] Simplify uart_bus_pci_probe
On Nov 10, 2010, at 12:44 AM, Garrett Cooper wrote: On Tue, Nov 9, 2010 at 10:29 PM, Marcel Moolenaar xcl...@mac.com wrote: On Nov 6, 2010, at 11:22 AM, Garrett Cooper wrote: Some of the logic could have been simplified in the probe. The proposed patch makes the detection process a tad bit more straightforward. Comments, review (and maybe a commit :P) are more than welcome :). The patch is logically wrong for non-ns8250 based UARTs. Leave the code as is. Hi Marcel, Is the layout of the pci_ns8250_ids PCI ID table correct then, as there are a large number of ns16550 chips and other non-ns8250 chips in the table? ns16550 is a ns8250 class UART. They are in the same family. Non-ns8250 UARTs include Zilog Z8530, Siemens SAB 82532, Freescale's PowerQUICC SCC, and even SGI's firmware based serial console of you like. FYI, -- Marcel Moolenaar xcl...@mac.com ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Interactive tool for installing packages
In the last episode (Nov 10), per...@pluto.rain.com said: Marin Atanasov Nikolov dna...@gmail.com wrote: in order to install the program, you need to: # git clone git://git.unix-heaven.org/public/pkg_add_it ... Surely, there's room for improvement, but that's a start.. :) Dunno about anyone else, but from my standpoint it would be a _big_ improvement to provide a more recent snapshot than the 6-month-old pkg_add_it-1.2.tar.gz on ftp.freebsd.org so one doesn't have to install git, with its boatload of dependencies*, to see the recent improvements. * The amount of stuff downloaded by cd /usr/ports/devel/git ; make fetch-recursive is, shall we say, impressive. I use the devel/hg-git port to pull all the git trees I need to access using mercurial. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
libkvm: consumers of kvm_getprocs for non-live kernels?
Hi, I have this cleanup of libkvm sitting in my tree and it needs a little bit of testing, especially the function kvm_proclist, which is only called from kvm_deadprocs which is only called from kvm_getprocs when kd is not ALIVE. The only consumer in our tree that I can make out is *probably* kgdb, as ps(1), top(1), w(1), pkill(1), fstat(1), systat(1), pmcstat(8) and bsnmpd don't really work on coredumps But, the kgdb file gnu/usr.bin/binutils/gdb/kvm-fbsd.c, where kvm_getprocs is probably called on a dead kernel is not even used during build! So I guess I'm staring at dead code here, any kvm people around that can clue me in? Thanks, Uli ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: libkvm: consumers of kvm_getprocs for non-live kernels?
On 2010-11-10 21:41, Ulrich Spörlein wrote: But, the kgdb file gnu/usr.bin/binutils/gdb/kvm-fbsd.c, where kvm_getprocs is probably called on a dead kernel is not even used during build! So I guess I'm staring at dead code here, any kvm people around that can clue me in? In gnu/usr.bin/binutils, the gasp, gdb and gdbreplay directories have been disconnected from the build for years now. I plan on garbage collecting them when merging the binutils-2.17 project branch (where they are already removed). ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: libkvm: consumers of kvm_getprocs for non-live kernels?
On 11/10/10 12:41 PM, Ulrich Spörlein wrote: Hi, I have this cleanup of libkvm sitting in my tree and it needs a little bit of testing, especially the function kvm_proclist, which is only called from kvm_deadprocs which is only called from kvm_getprocs when kd is not ALIVE. The only consumer in our tree that I can make out is *probably* kgdb, as ps(1), top(1), w(1), pkill(1), fstat(1), systat(1), pmcstat(8) and bsnmpd don't really work on coredumps they used to. you should ask on -current because more people who know hang out there. But, the kgdb file gnu/usr.bin/binutils/gdb/kvm-fbsd.c, where kvm_getprocs is probably called on a dead kernel is not even used during build! So I guess I'm staring at dead code here, any kvm people around that can clue me in? Thanks, Uli ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: libkvm: consumers of kvm_getprocs for non-live kernels?
On Wed, Nov 10, 2010 at 09:41:52PM +0100, Ulrich Spörlein wrote: I have this cleanup of libkvm sitting in my tree and it needs a little bit of testing, especially the function kvm_proclist, which is only called from kvm_deadprocs which is only called from kvm_getprocs when kd is not ALIVE. The only consumer in our tree that I can make out is *probably* kgdb, as ps(1), top(1), w(1), pkill(1), fstat(1), systat(1), pmcstat(8) and bsnmpd don't really work on coredumps But, the kgdb file gnu/usr.bin/binutils/gdb/kvm-fbsd.c, where kvm_getprocs is probably called on a dead kernel is not even used during build! So I guess I'm staring at dead code here, any kvm people around that can clue me in? It is a while ago that I last used this, but ps and fstat definitely worked on crashdumps, to some extent. /usr/sbin/crashinfo uses this. -- Jilles Tjoelker ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
python + build ports = failure (threading problem)
Hi, I've found a problem in FreeBSD's implementation for threads, pth does not have this problem. The following test case consistantly reproduces the problem: --- start --- #! /usr/bin/env python from subprocess import Popen, PIPE from threading import Lock, Thread def runner(): process = Popen((make, -C, /usr/ports/graphics/kdegraphics4, clean, all), close_fds=True) process.wait() # If runner called directly then port compiles correctly, otherwise it stalls Thread(target=runner).start() --- end --- The port stalls with snip/ grep: writing output: Broken pipe grep: writing output: Broken pipe grep: writing output: Broken pipe - found === Configuring for kdegraphics-4.5.3 /bin/mkdir -p /usr/ports/graphics/kdegraphics4/work/kdegraphics-4.5.3/build end/ The grep errors appear to be mostly harmless, `ps` shows: snip/ 17648 4 D 0:00.03 python test.py 17649 4 D 0:00.08 make -C /usr/ports/graphics/kdegraphics4 clean all 17974 4 D 0:00.03 [cmake] 17978 4 Z 0:00.03 defunct snip/ I suspect any port using cmake will have this problem (unconfirmed) and if memory serves me correct then building lang/perl causes the same problem (although the stall happens much later on in the build). Using WITH_PTH when building python fixes the problem so I suspect libthr as the cause of the problem. I hope someone finds this information useful. David P.S. Should a PR be filed for this? P.S.S. It is possible that one of pythons test cases can reproduce this... signature.asc Description: This is a digitally signed message part.
Re: Interactive tool for installing packages
Marin Atanasov Nikolov dna...@gmail.com wrote: If you do not have git installed, you could still get the latest snapshot of pkg_add_it via the Cgit repo. [1] [1] http://git.unix-heaven.org/cgit.cgi/pkg_add_it/ Aha! I'm sure I looked at that page before posting, but did not see how to pull down a snapshot (vs browsing individual files) the first time. It seems to have been reorganized since 1.2, as well as having grown quite a bit :) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Interactive tool for installing packages
On Thu, Nov 11, 2010 at 8:01 AM, per...@pluto.rain.com wrote: Marin Atanasov Nikolov dna...@gmail.com wrote: If you do not have git installed, you could still get the latest snapshot of pkg_add_it via the Cgit repo. [1] [1] http://git.unix-heaven.org/cgit.cgi/pkg_add_it/ Aha! I'm sure I looked at that page before posting, but did not see how to pull down a snapshot (vs browsing individual files) the first time. It seems to have been reorganized since 1.2, as well as having grown quite a bit :) Yep, quite a lot of changes went to 1.3, the program was completely rewritten and introduced a lot of new features :) Most significant changes were: - own-styled lists were replaced by queue(3) macros, so generally now everything is dynamic and memory leak-free. - a lot of new functions dealing with packages, added a configuration module - etc... :) One thing that can be improved is the recursion introduced by DEPS_FULL_TREE=true, so that dependencies can be found easier and faster from INDEX, but I'm looking into this already, since I think that feature is very useful when you need to know the dependencies of a package in a tree-view. Regards, Marin -- Marin Atanasov Nikolov dnaeon AT gmail DOT com daemon AT unix-heaven DOT org http://www.unix-heaven.org/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
