Re: Is anyone working on a port of ZFS to FreeBSD
On Jun 1, 2006, at 9:50 AM, Robert Watson wrote: On Thu, 1 Jun 2006, Eric Anderson wrote: Agreed it would be. I'd love to see it (I'm an advocate for as many filesystems available as possible actually). So, the real question is, who's going to volunteer to start actually porting it? People interested in volunteering can expect lots of help and interest, but should go into it knowing that it's a highly complex multi man year project, and definitely not a summer project or free weekends sort of thing. I'm happy to be proven wrong on that point, but it would be dishonest for me to suggest it will be easy. :-) I thought that I'd mentioned this on this list a few days ago, but there is a SoC project to port ZFS to FUSE. The person doing the work is specifically targeting Linux for this, but since we already have FUSE running on FreeBSD it seems like a pretty good way to at least get something working (assuming the SoC project completes). Jeff Bonwick's blog about it: http://blogs.sun.com/roller/page/ bonwick?entry=zfs_on_fuse_linux ZFS on FUSE blog: http://zfs-on-fuse.blogspot.com/ ZFS on FUSE website/wiki: http://www.wizy.org/wiki/ZFS_on_FUSE I doubt that I'd be any help making the code work, but I certainly like to see this make to FreeBSD is possible. If there are other things that I can do to help then I'd be open to suggestions. -- Joseph Scott http://joseph.randomnetworks.com [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ZFS on FUSE/Linux
One of the Google Summer of Code projects is ZFS for FUSE/Linux. More info: Google SoC app: http://code.google.com/soc/opsol/appinfo.html? csaid=1EEF6B271FE5408B Blog: http://zfs-on-fuse.blogspot.com/2006/05/announcing-zfs-on- fuselinux.html Since there is FUSE for FreeBSD now, any chance this can be leveraged to make ZFS work on FreeBSD? -- Joseph Scott http://joseph.randomnetworks.com [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using any network interface whatsoever
On Apr 10, 2006, at 2:23 PM, Darren Pilgrim wrote: I think at this point it's been pretty well established that: - Device naming and unit numbering is not stable enough to avoid breakage across hardware changes. - There is a need for generic and/or descriptive interface naming independent of driver- and probe-order-based naming. - There are static bits of information available about each device in the system that can be used to locate a specific device that would be sufficient to allow assignment of a network configuration to a physical device, not it's attached name. If I were to write an rc.d script to use descriptive network interface names and wire configs to static hardware identification, would there be support for such a feature? Being mostly a lurker on this list I don't know that my vote would count for much, but yes I'd support such a feature. Thank you also for outlining the issues for this thread in a simple manner. -- Joseph Scott [EMAIL PROTECTED] http://joseph.randomnetworks.com/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sun DTrace on FreeBSD
On Mar 15, 2006, at 10:58 PM, Peter Jeremy wrote: About six months ago, there was a lot of press publicity given to a port of Sun's DTrace code to FreeBSD. Does anyone know what (if anything) is happening to this? Google doesn't turn up anything more recent and I don't recall reading anything on the mailing lists. The person working on it was Devon O’Dell (http://www.sitetronics.com/ wordpress/). I haven't seen any updates on his blog about it for quite some time (September 2005 ?). -- Joseph Scott [EMAIL PROTECTED] http://joseph.randomnetworks.com/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
[FreeBSD PR bin/15416] addr2line broken
FreeBSD PR bin/15416 (addr2line is unable to find line numbers) indicates that addr2line appears to be broken. This PR was submitted at the end of 99 when 4.x was -current. It hasn't been touched since. The PR gives a test case where addr2line appears to be broken. I ran this exact test case on a 4-stable box and saw the same issue. The version addr2line reports is 2.12.1 [FreeBSD] 2002-07-20. I tested it on 5-DP2 and it appears to work correctly, the version there is 2.13 [FreeBSD] 2002-10-10. What's the correct thing to do with this PR? The issue does appear to be fixed in -current (with the newer addr2line). I suppose the PR should at least be set to a status of patched. Thanks. -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
FreeBSD PR bin/981
FreeBSD PR bin/981 (clnt_broadcast() is not aware of aliases) hasn't been touched since mid 1997. The bug reported in the PR was apparently fixed back in March of 1996, but fenner mentions that this left another bug. I've looked through the cvs history for src/lib/libc/rpc/pmap_rmt.c and it doesn't appear the bug mentioned by fenner was ever fixed even though a patch was suggested. My question is, it's been like this for many years, does this bug still need fixing or can this PR now be closed? Someone who knows what the right behaviour is can take a look at this that would be great. -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
PR Close Request
Looking through some of the old kern PRs I can across PR kern/5863 (Kernel support for sorted SHUTDOWN SHUTDOWN_POWEROFF queues). I haven't looked through the whole thing, but it appears that the idea behind this PR has committed by msmith@ some four years ago (see rev 1.41 of sys/kern/kern_shutdown.c for starters). Will someone take a quick look at this and confirm that this PR has been dealt with and close it. Thanks. -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: context or unified diffs in PRs?
On Sat, 10 Mar 2001, Michael Lucas wrote: Hello, I'm afraid I might be walking up to a bikeshed with a can of paint here, but the flood of email in the last twenty-four hours has convinced me to ask. In an article O'Reilly published yesterday, I stated (per the Handbook) that context diffs were the correct way to submit patches with PRs. I've had several people claim that unified diffs are the way to go, and that the handbook is just wrong. Is the Handbook correct, or are unified diffs preferred? I'll be happy to fix my article and submit a PR to correct the Handbook if this is the case. When I read your article I thought that perhaps that was a mistake, but quickly started looking at something else and forgot about it. I'd always thought unified was better, and felt justified after reading this section in the FreeBSD Porter's Handbook http://www.freebsd.org/docs/en/books/porters-handbook/port-upgrading.html third paragraph, where the example diff they use is diff -ruN for upgrading a port. -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Handspring.
On Fri, 9 Feb 2001, Kenny Drobnack wrote: # Do you mean getting FreeBSD ported to the Handspring, or do you mean # using FreeBSD to sync with it? As for porting FreeBSD to it it sounds # like Brooks knows what he's talking about. As far as syncing a # Handspring Visor with FreeBSD - dunno. Tried using the coldsync program # which was meant for syncing Palm Pilots, and the coldsync web page # claims that it works with Visors too. When I run coldsync, I get a # message "Please press the hotsync button" and when I hit the button I # get the message two more times, and then either it locked up or the # whole system locks up. Same results using a serial cradle instead of # the USB cradle that came with it. I noticed Linux has a Handspring # Visor driver, not sure what's up with that. I've been using J-Pilot (which uses pilot-link port to actually talk to the Visor) to sync with my Visor. I've only used the serial link, but I believe the USB link would work also. # # What are the chances of porting to this baby? # # None what so ever. The processor on the Handsping (and all other current # PalmOS based devices) doesn't have an MMU and most UNIX-like OSes assume # you have one. There is a Linux port of some sort and I've heard mention # that there's some intrest in the NetBSD community, but itty-bitty, # feature-poor processors don't really fit with FreeBSD's server/embedded # (generally high-end embedded systems) focus. In the future there may # be PalmOS based devices that you could port FreeBSD to, but that will # be after then finish the hardware abstraction layer. Once someone gets # around to doing the work, the StrongARM port should work on HP iPAQs, # but that's not what you were asking. # # -- Brooks # # -- # Any statement of the form "X is the one, true Y" is FALSE. # # To Unsubscribe: send mail to [EMAIL PROTECTED] # with "unsubscribe freebsd-hackers" in the body of the message # # # To Unsubscribe: send mail to [EMAIL PROTECTED] # with "unsubscribe freebsd-hackers" in the body of the message # To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: processing incoming mail messages (FreshPorts 2)
On Sun, 17 Dec 2000, Dan Langille wrote: # Which list would be more appropriate for asking advice on designing a # mail processing strategy for FreshPorts 2 (i.e. processing all of cvs-all, # not just the ports)? # # I'm looking for recommendations and guidance on how to capture the # incoming messages and process them one at a time. As opposed to # starting a separate perl script for each message (which is the the # existing strategy and is usually fine, except when large numbers of # messages turn up in a short period of time). If you don't want to process a message the instant it comes in (via feeding it to a perl script or what ever) you'll need to setup some sort of queue, then have a cron job come through and process the queue. If the problem is load then another approach would be to heavily nice(1) the perl script the is launched when a commit mail comes in. *** * Joseph Scott The Office Of Water Programs * * [EMAIL PROTECTED] [EMAIL PROTECTED]* *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: processing incoming mail messages (FreshPorts 2)
On Mon, 18 Dec 2000, Vivek Khera wrote: # "JSF" == Joseph Scott [EMAIL PROTECTED] writes: # # JSF If you don't want to process a message the instant it comes in # JSF (via feeding it to a perl script or what ever) you'll need to setup some # JSF sort of queue, then have a cron job come through and process the # JSF queue. # # Or, you could use a mailer system that does it for you. You can # configure postfix to deliver at most N messages to a specific local # destination at once, the rest getting queued in the local mail spool. # If you set this limit to 1, you'd avoid the need for any additional # file locking as well. How does postfix determine that a message has been delivered though? From reading Dan's first message, my though was the problem was doing the processing of the commit, all the db stuff, which would happen after the perl script had already accepted delivery of the message. *** * Joseph Scott The Office Of Water Programs * * [EMAIL PROTECTED] [EMAIL PROTECTED]* *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: processing incoming mail messages (FreshPorts 2)
On Tue, 19 Dec 2000, Dan Langille wrote: # If you don't want to process a message the instant it comes in # (via feeding it to a perl script or what ever) you'll need to setup some # sort of queue, then have a cron job come through and process the queue. # # Thanks. Since posting my original message, the proposed design has # drifted to this strategy (which I posted to the FreshPorts develop list last # night): # # On Mon, 18 Dec 2000, Dan Langille wrote: # # ok folks, brain pick time: I'm thinking about redoing the FreshPorts # mail-database interface. At present, each incoming email from cvs-all # initiates a separate perl script. Not nice if you get say 100 emails all # in 1 minute for some reason. Now I'm thinking of using procmail to # dump each email to a separate file on disk. Then processing each # file thus freeing up the MTA ASAP. Sound good so far? # # Suggestions? Ideas? # # As for processing the files once they are on disk, I like the idea of # processing the messages ASAP. Therefore, I'd like to have a daemon / # script sitting there running all the time. This process is notified when a # new message arrives (in the above case, that would be part of the # procmail delivery process). This process would then "wake up" and # process all available message files one at a time. Perhaps moving each # processed file to an archive. When there are no more message files, it # would stop and wait to be notified again. # # If the problem is load then another approach would be to heavily # nice(1) the perl script the is launched when a commit mail comes in. # # That's already done. It's just the volume which can occur. If a large # number of messages arrive at once. Starting up 50 perl jobs on the box # can stress it a bit. It also makes better sense to process the # messages in the order in which they arrive rather than concurrently. A # side effect will be less change of database lockouts or conflicts during # updates. On item that may help on this then is checking two things every time you add something to the queue to help balance things out, the amount of time since the last time the queue was processed and the number of items in the queue. Let's say, at a minimum you want the queue to run every 30 minutes. However, if there are a large number of commits in the queue, you may want to be able ramp up to queue processing as quickly as every 5 minutes. If there's only two items in the queue though, there's really no reason to run it every 5 minutes. Just some thoughts. *** * Joseph Scott The Office Of Water Programs * * [EMAIL PROTECTED] [EMAIL PROTECTED]* *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: processing incoming mail messages (FreshPorts 2)
On Tue, 19 Dec 2000, Dan Langille wrote: # On 18 Dec 2000, at 12:03, Joseph Scott wrote: # # Let's say, at a minimum you want the queue to run every 30 # minutes. However, if there are a large number of commits in the queue, # you may want to be able ramp up to queue processing as quickly as every 5 # minutes. If there's only two items in the queue though, there's really no # reason to run it every 5 minutes. # # I would rather process the queue as soon as a new message arrives. # Rather than have a message sit there. Hence, the "notification" of a # waiting process: OI! you got mail Then my original answer should have simply been, find a box that will host FreshPorts that can take the load of processing 5000 commit mails in a minute. :-) # # Just some thoughts. # # appreciated. *** * Joseph Scott The Office Of Water Programs * * [EMAIL PROTECTED] [EMAIL PROTECTED]* *** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: smbfs-1.3.0 released
On Thu, 26 Oct 2000, Boris Popov wrote: On Mon, 23 Oct 2000, Joseph Scott wrote: When is this going to be brought into -current? This was planned to be done in early September, but got some troubles with import of iconv library. I can't import smbfs without i18n support because many people use it. In any way, future smbfs releases will support 4.x and recent -current. I've only got -stable boxes around here, I was asking simply because the sooner it makes it into -current the sooner it gets into -stable :-) Thanks again for your work on this, I look forward to seeing this in the base system. --- Joseph Scott [EMAIL PROTECTED] The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: smbfs-1.3.0 released
When is this going to be brought into -current? Boris Popov wrote: Hello, At first, I'm want to say 'thank you' for everybody who provided me with feedback on my work. So, here is a records from the HISTORY file for last two releases: 20.10.2000 1.3.0 - Network IO engine significantly reworked. Now it uses kernel threads to implement 'smbiod' process which handles network traffic for each VC. Previous model were incapable to serve large number of mount points and didn't work well with intensive IO operations performed on a different files on the same mount point. Special care was taken on better usage of MP systems. Unfortunately, kernel threads aren't supported by FreeBSD 3.X and for now it is excluded from the list of supported systems. - Reduce overhead caused by using single hash table for each mount point. 26.09.2000 1.2.8 (never released) - More SMP related bugs are fixed. - Make smbfs compatible with the Linux emulator. - smbfs now known to work with IBM LanManager (special thanks to Eugen Averin) - Fix problem with files bigger than 2GB (reported by Lee McKenna) - Please note that smbfs may not work properly with FreeBSD 3.X. New version can be downloaded from: ftp://ftp.butya.kz/pub/smbfs/smbfs.tar.gz -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message -- Joseph Scott [EMAIL PROTECTED] The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Routing issues
On Sat, 14 Oct 2000, Gregory Sutter wrote: I'm setting up a network that looks like this: --InternetRouter---Firewall | | /--- host SwitchNAT-- host | \- host |\- etc... - | | email ns When I first looked at this, is there a reason why it isn't something like this instead : ---Internet---Router---| | | Firewall---Nat (Many Hosts) | | | (Multiple Servers) You have to have a hub/switch between the firewall and each network (the NAT and the server). You end up with a firewall with three nics. One the surface what I'd probably do with something like this is actually NAT both the many hosts and the servers network, but on the servers use a 1:1 IP mapping (bimap if you are using IPFilter). The thing that would interest me is if you could use bridging between the outside firewall nic and the servers network in conjuction with NAT'ing the many hosts network. This is something I've wondered about but never tried. If if it's doable I'm not sure it would be a good idea. Having the three nics would allow you to filter based on that entire network based on which nic the traffic is coming from or heading to. In other words, a fairly typical small network. I've got an 8-IP subnet; all hosts outside the NAT have real IPs: router: 1.2.3.193 firewall: 1.2.3.196 fxp0 1.2.3.197 fxp1 nat: 1.2.3.198 email:1.2.3.194 ns: 1.2.3.195 The problem I'm having is with my routing. Surprise. Here is the routing table for the firewall: default 1.2.3.193 fxp0 1.2.3.193 link#1 fxp0 1.2.3.192/29 link#2 fxp1 1.2.3.196 lo0 1.2.3.197 lo0 The gateway_enable (net.inet.ip.forwarding) is also enabled on the firewall. From the firewall, I can reach any host with no problems. However, from hosts inside the firewall, I cannot reach outside, and vice versa. I feel I must be missing something obvious, but have played with routes for hours to no avail. Does anyone see a problem with the routing of this network? Greg -- Gregory S. SutterComputing is a terminal addiction. mailto:[EMAIL PROTECTED] http://www.zer0.org/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message --- Joseph Scott [EMAIL PROTECTED] The Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Maestro2E patch (Was: US$100 prize for adding ESSAudiodrivesupport to pcm)
Munehiro Matsuda wrote: Hello Joseph, From: Joseph Scott [EMAIL PROTECTED] Date: Thu, 10 Aug 2000 17:36:52 -0700 :: I have created a patch that trys to enable internal speakers. :: :: The first part of the patch (for maestro.c) didn't apply cleanly for ::me, so I ended up doing it by hand. Thats funny. Did you aply my patch to the original 2725 version? Yes. I even went and redownloaded it to make sure. The first patch you included below didn't apply cleanly either. I applied it by hand again. :: It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works :: for everybody. Patch is based on Linux driver, but simplified. :: :: If it does not work, 1) try setting GPIO values to what your PC is at :: when rebooting from Windows, 2) try original way the Linux driver do. :: Let me know, if you want to know what Linux driver does. :: :: Unfortunately this didn't work for mine (Dell Inspiron 7500). How to ::I find out the GPIO values that make windows work? I'm open to trying ::what the Linux driver does. Mind you my C programing skills are ::pretty much useless, but I'm willing to try things out :-) Aha, Dell Inspiron 7500! There was some extra stuff in the Linux driver for it. I have recreated my patch (mstr2_spk.patch2) to include them. Please aply the new patch to the original 2725 version source code! This seems to have to done the trick! I now get sound out of both internal speakers! Yeah And also, I added a small patch (mstr2_gpio.patch) that should print GPIO values. Aply GPIO patch after the mstr2_spk.patch2! I didn't try this patch since the first one got the speakers working. Would it be helpful to find out GPIO values at this point? If so let me know and I'll apply the patch and see what I get. Otherwise I'll just go with what I've got. Let me know how that works out. BTW, I'll be out of town for few days. So my reply may get delayed. sorry. Thank you, Haro No problem. Thank you again, now I won't have to carry about headphones or external speakers with my notebook :-) -- Joseph Scott [EMAIL PROTECTED] Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Maestro2E patch (Was: US$100 prize for adding ESS Audiodrivesupport to pcm)
Munehiro Matsuda wrote: Hi all, From: Joseph Scott [EMAIL PROTECTED] Date: Tue, 08 Aug 2000 08:44:08 -0700 :: On a simmilar note: what about a driver for ESS Maestro 2E? I'm certainly :: [...] :: Add $100 from me. There is one that works for some folks out there :: by [EMAIL PROTECTED], but it does not work for me. :: :: where do you find this? :: :: I'm not sure about Alan, but I got it from an email from Taku ::YAMAMOTO [EMAIL PROTECTED]. I've included the email below. ::One thing to note, myself and a few others have only been able to get ::sound to work out of the audio out jack. For some reason the internal ::speakers just don't work. I've played with the settings on the ::notebook quite a bit, and they do still work when I boot into ::Windows. However, sound, even without the internal speakers, is ::better than no sound at all :-) I have created a patch that trys to enable internal speakers. The first part of the patch (for maestro.c) didn't apply cleanly for me, so I ended up doing it by hand. It worked for me (NEC VersaProNX VA26D), but I'm not sure if it works for everybody. Patch is based on Linux driver, but simplified. If it does not work, 1) try setting GPIO values to what your PC is at when rebooting from Windows, 2) try original way the Linux driver do. Let me know, if you want to know what Linux driver does. Unfortunately this didn't work for mine (Dell Inspiron 7500). How to I find out the GPIO values that make windows work? I'm open to trying what the Linux driver does. Mind you my C programing skills are pretty much useless, but I'm willing to try things out :-) Thanks again to the people working on this, it's nice to have sound working. The patch is based on Taku YAMAMOTO's maestro driver found at: http://access.cent.saitama-u.ac.jp/~taku/freebsd/maestro/releng4-2725.tar.gz FYI, I also was writing Maestro2E driver myself, but I stopped. Because YAMAMOTO-san's driver works better than mine. :-) Thank you, Haro -- Joseph Scott [EMAIL PROTECTED] Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Linux ioctl not implemented error
Kenneth Wayne Culver wrote: Any wierd things I should do to get it running? On Tue, Nov 30, 1999, Kenneth Wayne Culver wrote: Wait... vmware for linux works under FreeBSD now??? or it just runs freebsd??? It runs on FreeBSD. Here's pointer to the announcement on -hackers and to the web page for the port on Daily Damon News : http://daily.daemonnews.org/view_story.php3?story_id=270 -- Joseph Scott [EMAIL PROTECTED] Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
