Re: disk recovery help
On Mon, 2004-Jul-26 14:30:08 -0400, Charles Sprickman wrote: I did get confirmation from Adaptec that it does go from the outside sectors in. In which case one of the first things to be over-written would have been the first superblock and fsck should complain and stop immediately if this is invalid. I ended up using sysutils/ffsrecov to grab the alternate superblocks. Maybe that was the tool I was thinking of. I have a reasonably OK fsck'd filesystem mounted now. I have another copy to work on, and my question there is this: When you run fsck it creates a lost+found directory to put files that are unreferenced anywhere (I think that's the terminology). At some point during the fsck, it starts spitting errors about there not being enough space in lost+found. Is there any way to remedy that problem? Is there some way to grow the filesystem *before* fsck-ing it? fsck will grow the lost+found directory if necessary but it can only grow it to the limit of the direct blocks (12 filesystem blocks). The only way to pre-grow the lost+found directory would be to mount the filesystem read/write, create a large number of (preferably large) filenames and then delete them[1]. I'm not sure if the fsck code can understand indirect blocks in the lost+found directory so I don't know if this would work. It also relies on the filesystem to be sane enough for normal block allocation to work. One option might be to force a read/write mount, rename lost+found, umount the filesystem and redo the fsck until it fills the new lost+found. Renaming a directory entry is fairly safe, especially if you don't change the entry size. Alternatively, do this with fsdb - which is definitely safe. [1] Directories are only shrunk when an entry is created, not when one is deleted. -- Peter Jeremy ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
May-June 2004 FreeBSD Status Report
May-June 2004 Status Report Introduction This installment of the Bi-Monthly Status Report is a few days late, but I'm pleased to say that it is chocked full of over 30 articles. May and June were yet again busy months; the Netperf project passed major milestones and can now be run with the debug.mpsafenet tunable turned on from sources in CVS. The ARM, MIPS, and PPC ports saw quite a bit of progress, as did several other SMPng and Netgraph projects. FreeBSD 5.3 is just around the corner, so don't hesitate to grab a snapshot and test the progress! On a more serious note, it's very important to remember that code freeze for FreeBSD 5.3 will happen on August 15, 2004. This is only a few weeks away and there is still a lot to do. The TODO list for the release can be found at . If you are looking for a way to contribute to the release, this TODO list has several items that are in urgent and in need of attention. Testing is also very important. The tree has had some stability stability problems in the past few weeks, but there are work-arounds that should allow everyone to continue testing and using FreeBSD. We absolutely must have FreeBSD 5.3 be a rock-solid release, so every little bit of contributed effort helps! Thanks, Scott Long * Bluetooth stack for FreeBSD (Netgraph implementation) * ALTQ import * Buf Junta project * CAM Lockdown * Cronyx Adapters Drivers * EuroBSDCon 2004 registration now open * FreeBSD Brazilian Documentation Project * FreeBSD Dutch Documentation Project * FreeBSD Handbook, 3rd Edition, Volume II: Administrator Guide * FreeBSD ports monitoring system * FreeBSD profile.sh * FreeBSD/arm * FreeBSD/MIPS Status Report * HP Network Scanjet 5 * i386 Interrupt Code PCI Interrupt Routing * Improved Multibyte/Wide Character Support * IPFilter Upgraded to 3.4.35 * KDE on FreeBSD * kgi4BSD * Low-overhead performance monitoring for FreeBSD * Network interface naming changes * Network Stack Locking * Packet Filter - pf * PowerPC Port * Project Mini-Evil * SMPng Status Report * Sync protocols (Netgraph and SPPP) * TTY subsystem realignment * Various GEOM classes and geom(8) utility * VuXML and portaudit Bluetooth stack for FreeBSD (Netgraph implementation) Contact: Maksim Yevmenkin [EMAIL PROTECTED] Bluetooth code was marked as non-i386 specific. It is now possible to build it on all supported platforms. Please help with testing. Other then this there was not much progress during last few months. I've been very busy with Real Life. _ ALTQ import URL: http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ URL: http://www.rofug.ro/projects/freebsd-altq/ URL: http://kerneltrap.org/node.php?id=505 URL: http://people.freebsd.org/~mlaier/ALTQ_driver/ Contact: Max Laier [EMAIL PROTECTED] The ALTQ framework is part of KAME for more than 4 years and has been adopted by Net- and OpenBSD since more than 3 years. It provides means of managing outgoing packets to do QoS and bandwidth limitations. OpenBSD developed a different way to interact with ALTQ using pf, which was adopted by KAME as the default for everyday use. The Romanian FreeBSD Users Group has had a project to work towards integration of ALTQ into FreeBSD, which provided a very good starting point for the final import. The import only provides the pf mode configuration and classification API as the older ALTQ3 API does not suit to our SMP approach. A reworked configuration API (decoupled from pf) is in the making as are additional driver modifications. Both should be done before 5-STABLE is branched, although additional drivers can be imported during the lifetime of 5-STABLE as well. _ Buf Junta project Contact: Poul-Henning Kamp [EMAIL PROTECTED] The buf-junta project is underway, I am trying to bisect the code such that we get a struct bufobj which is the handle and method carrier for a buffer-cache object. All vnodes contain a bufobj, but as filesystems get migrated to GEOM backing, bufobj's will exist which do not have an associated vnode. The work is ongoing. _ CAM Lockdown Contact: Scott Long [EMAIL PROTECTED] Not much coding has taken place on this lately, with the recent focus being on refining the design. We are currently investigating per-CPU completion queues and threads in order to reduce locks and increase concurrency. Also reviewing the BSD/OS CAM lockdown to see what ideas can be shared. Work should hopefully puck back up in late July. Development is
Re: bus_alloc_resource question
Apparently, On Mon, Jul 26, 2004 at 06:59:24PM -0700, Chuck Tuffli said words to the effect of; I'm having some trouble adding a bus resource and am hoping someone can point out where I goofed. The host bus to a new x86 chipset has a memory mapped region in PCI space that provides access to status and control registers. For a driver to get access to this region, I figured it should call bus_alloc_resource() the same as for any other memory mapped region. This currently doesn't just work as the region is not a part of any device's BARs. To add this region as a resource, I used bus_set_resource() device_t dev; uint32_t e_mem = 0xe000; struct resource *ecfg_res; dev = pci_find_device(PCI_VENDOR_INTEL, ...); bus_set_resource(dev, SYS_RES_MEMORY, e_mem, 0xe000, 0x1000); but a subsequent call to bus_alloc_resource() returns NULL ecfg_res = bus_alloc_resource(dev, SYS_RES_MEMORY, e_mem, 0, ~0, 1, RF_ACTIVE | RF_SHAREABLE); A call to bus_get_resource() shows that the resource did get set as the call returns the correct starting address and count. Is there something else that needs to happen between the set and the alloc? Is this even the correct approach? Thanks in advance! If this is anything like the soekris board where 0xe000 is just a physical address that you want to map in and read or write you can use pmap_mapdev as a quick way to do it, eg, volatile void *ptr = pmap_mapdev(0xe000, ...); Be warned that this, as well as bus_alloc_resource(SYS_RES_MEMORY), will allocate virtual address space for the mapping, so you should only map in exactly what you need, I imagine its just a page or 2. 0x1000 is way too much, you will not be able to allocate that much virtual address space. Jake ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Simulate device-file in userland?
On Sun, Jul 25, 2004 at 06:57:00PM +0200, Jan Branbergen wrote: Content-Description: body i was wondering if it is possible to simulate a device-file ( for example a serial port or videograbbing device ) in userland? You may want to look at ng_device. Be prepared for rough edges though ;) Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
new files in kernel build
Hi, If I want to add some files into kernel sources, what am I supposed to do to them compile? I added some into sys/net80211/ but they dont compile... I tried sys/conf/files but it does help, just prints a message about having it defined before... thnx for help roman ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new files in kernel build
In message: [EMAIL PROTECTED] Divacky Roman [EMAIL PROTECTED] writes: : Hi, : : If I want to add some files into kernel sources, what am I supposed to do to : them compile? I added some into sys/net80211/ but they dont compile... : : I tried sys/conf/files but it does help, just prints a message about having it : defined before... Exact error messages would be helpful. Generally, you put them in sys/conf/files, re-run config and life is good. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus_alloc_resource question
On Mon, Jul 26, 2004 at 09:54:53PM -0600, M. Warner Losh wrote: ... Generally, one doesn't need to set the resource value. Doing so usually indicates the presence of some bug in the system. Also, just I realize now that the original email wasn't clear. This is a bus driver for a new bus. Think of the physical addresses from 0xe000 - 0xefff as being a memory mapped config space for devices. Each 4KB segment of this region maps the configuration space for every possible bus, device, function number combination. I was thinking that each of these segments was a bus resource, but maybe that isn't the right approach. Any thoughts as to a better approach? Jake Burkholder suggested using pmap_mapdev() for small sections of memory, but cautioned that this uses up virtual address space. The bus driver could map each segment to test if a device was there and unmap the segments that didn't contain devices. -- Chuck Tuffli Agilent Technologies, Storage Area Networking ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bus_alloc_resource question
Apparently, On Tue, Jul 27, 2004 at 09:51:25AM -0700, Chuck Tuffli said words to the effect of; On Mon, Jul 26, 2004 at 09:54:53PM -0600, M. Warner Losh wrote: ... Generally, one doesn't need to set the resource value. Doing so usually indicates the presence of some bug in the system. Also, just I realize now that the original email wasn't clear. This is a bus driver for a new bus. Think of the physical addresses from 0xe000 - 0xefff as being a memory mapped config space for devices. Each 4KB segment of this region maps the configuration space for every possible bus, device, function number combination. I was thinking that each of these segments was a bus resource, but maybe that isn't the right approach. Any thoughts as to a better approach? Jake Burkholder suggested using pmap_mapdev() for small sections of memory, but cautioned that this uses up virtual address space. The bus driver could map each segment to test if a device was there and unmap the segments that didn't contain devices. Ok, I think what you want to do is make an rman (resource manager) that manages the device memory, and that child devices will allocate from. In your attach routine you would then probe the bus by mapping in portions of whatever size you need and adding the child device's resources to a resource list, for each child found. An example of this (oddly enough) is the sparc64 nexus (in -current), sparc64/sparc64/nexus.c, and the sparc64 sbus driver, sparc64/sbus/sbus.c. The MI pci bus drivers as well, but this is a bit closer to what you're doing, I think. You won't be able to allocate the region from pci unless its described by pci, but that doesn't really matter as long as no one else tries to use it. HTH, Jake ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: new files in kernel build
M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Divacky Roman [EMAIL PROTECTED] writes:
: Hi,
:
: If I want to add some files into kernel sources, what am I supposed to do to
: them compile? I added some into sys/net80211/ but they dont compile...
:
: I tried sys/conf/files but it does help, just prints a message about having it
: defined before...
Exact error messages would be helpful.
Generally, you put them in sys/conf/files, re-run config and life is
good.
if you want to add these files without editing /sys/conf/files you can
add them to /sys/conf//files.{YOURCONFIG}
e.g. we backported the firewire to an older kernel and have a
proprietary driver as well..
our files.VICOR looks like:
%cat files.VICOR
xdcpdrvr.o optionalxdcp\
dependency $S/dev/xdcp/xdcpdrvr.o.uu \
compile-withuudecode $S/dev/xdcp/xdcpdrvr.o.uu \
no-implicit-rule
dev/firewire/firewire.c optional firewire
dev/firewire/fwcrom.c optional firewire
dev/firewire/fwdev.coptional firewire
dev/firewire/fwmem.coptional firewire
dev/firewire/fwohci.c optional firewire
dev/firewire/fwohci_pci.c optional firewire pci
dev/firewire/if_fwe.c optional fwe
dev/firewire/sbp.c optional sbp
without looking at the source to config, it seems to use teh entry on
the 'ident' line to
look for these files..
Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel GENERIC config file
Hi, I need the kernel GENERIC config file for freebsd 4.7. I am able to find only the config file for freeBSD 5.2 online... can n'ybody either mail me the freeBSD 4.7 GENERIC file or gimme a link to it? Thank you. HKR - Do you Yahoo!? Y! Messenger - Communicate in real time. Download now. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel GENERIC config file
On Tue, 27 Jul 2004, bsd hack wrote: I need the kernel GENERIC config file for freebsd 4.7. I am able to find only the config file for freeBSD 5.2 online... can n'ybody either mail me the freeBSD 4.7 GENERIC file or gimme a link to it? This doesn't belong on hackers. Get it yourself from CVS via the cvsweb interface: see http://www.freebsd.org/ -- Dan Langille - http://www.langille.org/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
jdk13 native plugin stopped working on native mozilla on -CURRENT
I know this is off topic here, but I'm hoping that I can get a quick answer rather than tromping off to ports or java. I'm runiing a recent -CURRENT and ports cvsupped and compiled today and my native-mode jdk13 is no longer working as a plugin. I get an unresloved symbol at mozilla startup and no plugin. The relevant versions are: mozilla-1.7.1,2 The open source, standards compliant web browser jdk-1.3.1p9_4 Java Development Kit 1.3 and the errors from mozilla are: bug:~$ mozilla Error: No running window found. LoadPlugin: failed to initialize shared library /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so: Undefined symbol _ZTV16nsQueryInterface] LoadPlugin: failed to initialize shared library /usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so [/usr/local/jdk1.3.1/jre/plugin/i386/ns600/libjavaplugin_oji.so: Undefined symbol _ZTV16nsQueryInterface] I also am running the linux shockwave plugin with no problem, if that's important. Any help would be great. Thanks. -- Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#SIG pgpkIK0sCwVkw.pgp Description: PGP signature
