Re: SMP Version of tar
On Oct 2, 2012, at 12:36 AM, Yamagi Burmeister li...@yamagi.org wrote: On Mon, 1 Oct 2012 22:16:53 -0700 Tim Kientzle t...@kientzle.com wrote: There are a few different parallel command-line compressors and decompressors in ports; experiment a lot (with large files being read from and/or written to disk) and see what the real effect is. In particular, some decompression algorithms are actually faster than memcpy() when run on a single processor. Parallelizing such algorithms is not likely to help much in the real world. The two popular algorithms I would expect to benefit most are bzip2 compression and lzma compression (targeting xz or lzip format). For decompression, bzip2 is block-oriented so fits SMP pretty naturally. Other popular algorithms are stream-oriented and less amenable to parallelization. Take a careful look at pbzip2, which is a parallelized bzip2/bunzip2 implementation that's already under a BSD license. You should be able to get a lot of ideas about how to implement a parallel compression algorithm. Better yet, you might be able to reuse a lot of the existing pbzip2 code. Mark Adler's pigz is also worth studying. It's also license-friendly, and is built on top of regular zlib, which is a nice technique when it's feasible. Just a small note: There's a parallel implementation of xz called pixz. It's build atop of liblzma and libarchiv and stands under a BSD style license. See: https://github.com/vasi/pixz Maybe it's possible to reuse most of the code. See also below, which has some bugfixes/improvements that AFAIK were never committed in the original project (though they were submitted). https://github.com/jlrobins/pixz JN ___ 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: LED support for ALIX 2/3 series
On Dec 15, 2010, at 7:12 AM, Michael Reifenberger wrote: On Wed, 15 Dec 2010, Emanuel Haupt wrote: Date: Wed, 15 Dec 2010 12:38:23 +0100 From: Emanuel Haupt eha...@freebsd.org To: freebsd-hackers@FreeBSD.org Subject: LED support for ALIX 2/3 series Is anyone interested in porting leds-alix.c [1] for the ALIX 2/3 series [2]? The following version uses linux API's. I'd gladly write a port for it if someone could port it. Probably it should use the led(4) framework and reside in the base OS. Like sys/arm/xscale/ixp425/cambria_led.c The LED's on my Alix 3d2 work just fine already with led(4) under 8.2. I think the code gets pulled in by options CPU_GEODE. I have three device nodes under /dev/led/ that work as described in the led(4) manpage. Am I missing something? JN ___ 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: an alternative to powerpoint
On Jul 13, 2010, at 11:48 AM, Ivan Voras wrote: On 07/13/10 06:15, Luigi Rizzo wrote: Have fun, it would be great if you could report how it works on fancy devices (iphone, ipad, androids...) For what it's worth, it doesn't work at all on Android :) (and the layout is messed up) The front page appears to come up fine on my iPhone (3GS+IOS 4) but I'm not able to navigate to any other slides (tap clicking doesn't work and I don't have the option of supplying keyboard input). JN ___ 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: Laptop suggestions?
On Thursday 24 July 2008, Frank Mayhar wrote: My old Dell Inspiron 5160 has developed problems that I can't fix, sigh, so it's time to replace it. I'm hoping for some good suggestions from this list (cc'd to hackers for the exposure, I know everyone doesn't read -mobile). I haven't played with one hands-on, but the laptop I was going to buy until $work supplied a different one was a Fujitsu Lifebook E8410. It has a few customization options if you get it from Fujitsu directly. Among these are Intel graphics and Atheros wireless, 2 of the main things I was looking for for good FreeBSD hw support. My criteria: * 3D acceleration. check ought to work w/ intel(4x) driver on i386 or amd64 * MiniPCI wireless (don't care which card, I'll replace it anyway). AFAIK. I was planning to select the Atheros option and leave it.. * At least 15 screen. 15.4 Wide with WSXGA+ option * Decent power consumption. Unknown, but available 8-cell main and 6-cell modular batteries. * Plays well with FreeBSD 7-stable. AFAIK. Nice to have: * Dual core. check. * 4GB memory. =4GB avail. (can you get more on a laptop yet?) * Working suspend/hibernate mode (and no, I'm not holding my breath). unknown. has any progress been made WRT suspend/resume + SMP on FreeBSD in general? So, suggestions? BTW, if I get a decent response I'll summarize it for the list, along with the one I chose and my experience after ordering/installing it. Best of luck and do post your experiences. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia working?
Quoting Chuck Robey [EMAIL PROTECTED]: I was wondering ... I have (I think) nvidia working on my box, or at least, I am calling out the nvidia driver in the xorg.conf, but I was wondering if there is any program that only works with the nvidia hardware, some way I can absolutely prove that I have the real nvidia card working here? Before I had it working, I was using the vesa driver, and most things look exactly the same, and if I could fine some program that shows the 8600GTS's abilities, I would sure like that. btw -questions would probably have been a better forum for this question than -hackers. The most straightforward approach is probably to review the output of your Xorg log, e.g. /var/log/Xorg.0.log. Output from the nvidia driver will be prefixed by NVIDIA (rather than VESA or NV if you were using a different driver). There is also x11/nvidia-settings port. It's a control panel of sorts that will show you nvidia-specific information. In theory it lets you control some settings as well but personally I've never found it useful for that. YMMV. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Verizon Wireless Card v620 (Novatel Wireless)
On Saturday 01 September 2007, Anthrax De Oracle wrote: Success ... on device from ugen1 to ucom0 ucom0: Novatel Wireless Inc. Novatel Wireless Merlin CDMA, rev 1.10/0.00, addr 2 ..I have successfully gotten my device to detect as ucom.. (ucom0: Novatel Wireless Inc. Novatel Wireless Merlin CDMA, rev 1.10/0.00, addr 2) and not ugen.. HOWEVER, my problem here is connecting... each time i type ppp ,... it says 'ucom0: ubsa_request STALLED. and the stalled messages keep coming.. when i type ping google.com to see if i'm online it shows me host look up failure, thus meaning im not connected. Please what can i do to solve this problem, it's eating me up.. i really need this.. I have even recompiled my kernel (from 6.2-RELEASE to 6.2-STABLE) ... and its still not working .. what can i do to solve this .. please help. See my thread about this from a few months ago on the freebsd-mobile mailing list. I saw strings of STALLED messages as well but it always worked fine for me. You might want to compare my patches to yours. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI boot mussings
On Friday 16 March 2007 07:34, Danny Braniss wrote: Hi, Now that I have my hands on a server that can boot iSCSI, I started to look into it. After figuring out what magic is needed in the dhcpd.conf (just add option root-path iscsi:target-iptarget-name) I can boot FreeBSD to the point that it can't find a root device, and assuming that some more magic can be applied (ala NFS), I'm just wondering aloud, if it's realy worth the efford. For a PXE based diskless solution, you need 1 - a working dhcpd 2 - a working tftpd 3 - a working NFS server with the exported root fs. appplying some minor magic, you can have only one read-only fs. For an iSCSI based diskless solution, you need 1- a working dhcpd 2- a working iscsi-initiator, unless the BIOS can be used. 3- a working target with a root fs (one for each client, unless applying 3 from the above). Hybrid solution: boot via PXE, but mount root via iSCSI So, what say you all? From the kernel's perspective (at the moment just prior to mounting root), is there a difference between the last two approaches? The situation as I see it (in both cases) is that the kernel is loaded into memory (by some magical means which is at this point irrelevant), and now has to locate a root device using only what it already has to bootstrap the process. If what it already has includes BOOTP code then it's possible to get some additional information externally. Whether the initial magic was PXE or BIOS-based iSCSI, the kernel has to have its own storage drivers and do its own network setup, right? I think there are some benefits to being able to do this, but perhaps 90% of them could be realized with what we already have (iscontrol and the iscsi_initiator kernel module) plus some rc and fstab glue. Any kind of diskless server farm needs at least one master server to run dhcpd, and if you have it doing that you might as well have it do NFS and tftpd as well. Pretty much any client you'd want to use as an iSCSI initiator will have a decent NIC which nowadays implies PXE support. So it shouldn't be hard to get root mounted using currently available means (local disk or PXE+NFS), and from there have the option of using iSCSI for other partitions (including /usr). A truly standalone iSCSI client will most likely want to use a TOE card, which to the OS looks like any other SCSI adapter. (I'm unsure which if any such cards are currently supported in FreeBSD, but that's a tangential question.) Machines with iSCSI-capable BIOS'es are an inbetween case. Allowing such machines to be standalone clients would require things like the initiator name, the initiator's IP address and netmask, the target's IP address, and the target's (volume) name to be hard-coded in the kernel. It would be nice to support this scenario, but IMO it's the one with the lowest benefit/cost ratio. Making it easy to integrate iSCSI into existing environments (diskless or not) is IMO the biggest hole in the current implementation (the missing rc and fstab bits I mentioned before). JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade O(n^m)?
On Wednesday 14 February 2007 12:41, David Gilbert wrote: I have 734 ports installed on my laptop right now. I'm pretty sure, at times, I've had over 1000 ports on my laptop. On machine with moderate numbers of ports (most servers seem to have 50 to 200 ports), portupgrade takes a moderate amount of time to start work. On machines like my laptop, portupgrade seems to take much more time to run. I assume it's solving the dependency graph before it decides what to upgrade first, but is this truly a O(n^2) problem? It seems like the implemented algorithm is O(n^2). Just a me too. I noticed a huge increase in time for portupgrade when I started using the modular Xorg ports tree and upgraded to X.org 7.2RC. The number of installed ports on my machine went from just over 300 to well over 600 as a result of the upgrade. Specifying small numbers of ports (without globbing) to portupgrade doesn't seem to take much more time, but portupgrade -a or anything similar takes forever now. If there is an optimization to be made there it would be good to do it before modular xorg hits the official tree. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Best practices for using gjournal with gmirror?
I have a few questions for pjd (or anyone else) about using gjournal, particularly when used with gmirror. 1) I'm running 6-STABLE and plan to test with gjournal6_20061030.patch (from the mailing list; updated version of 20061024 that applies cleanly). Is there a better/newer version for -STABLE that I should use instead? 2) When using gjournal and for a gmirror volume, does the journal need to be mirrored as well to maintain redundancy? If so, when storing the journal on the same physical disks as the mirror, is it better to mirror at the slice level (journal and fs on different partitions in the same mirror) or at the partition level (journal and fs each have their own mirror) or does it matter? 3) I remember reading where pjd said that gjournal plus gmirror or graid3 would eliminate the need to re-sync the array after a crash. While clearly a design goal, is that actually the case with the version of the patch mentioned above? If so, are any config changes needed or will it just happen automagically? 4) In the same vein as 3)--does a gjournal volume need to be fsck'ed after a crash? If not, will it just work (e.g. fsck -p sees that the filesystem is clean) or does it need to be disabled somehow? 5) Finally, how dangerous is this code? I realize it's experimental and only plan to use it with data that has recent backups, but how much should I worry about it blowing up my system or corrupting my files? Thanks! JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI disconnects dilema
On Tuesday 09 January 2007 02:06, Danny Braniss wrote: Hi, While I think I have almost solved the problem of network disconnects, It downed on me a major problem: When a 'local' disk crashes, the kernel will probably hang/panic/crash. if i don't try to recover, then there is no change in the above scenario. if i try to recover, then the client does not know that it should umount/fsck/mount. While all this seems familiar, removing a floppy/disk-on-key while it's mounted, we could always say you shouldn't have done that!, with a network connection, it can happen very often - rebooting the target, a network hickup, etc. So, any ideas? I think that an iSCSI network disconnect (if handled properly) is more like a bad/flakey set of sectors and/or extremely high latency than a total disk crash. The initiator should stall as long as it can while trying to reconnect the session, and then send hardware timeout errors up the stack. The the rest of the OS should handle those the same as it would any other timeout errors--retry a certain number of times and then fail. I don't know how graceful the failure case is (perhaps not very), but it's an honest approximation. The above approach is IMO more than adequate for network interruptions lasting a few seconds (or a bit more). I'm not sure there's anything you can realistically do more than that. Administrators who intentionally reboot a nonredundant iSCSI target while it has active sessions are asking for trouble, and if the reboot is accidental they should do one or more of a) know to run fsck manually, b) get a better UPS, c) get a more stable/redundant iSCSI target device. Disclaimer: I know next to nothing about kernel programming, device driver development, or scsi in general. I've just been playing with and thinking about iSCSI on FreeBSD a fair amount lately. Thanks for your continued work on this. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI disconnects dilema
Forwarding a relevant comment from a parallel discussion on -questions. -- Forwarded Message -- Subject: Re: iSCSI Date: Tuesday 09 January 2007 11:35 From: Dan Nelson [EMAIL PROTECTED] To: DAve [EMAIL PROTECTED] Cc: Free BSD Questions list freebsd-questions@freebsd.org In the last episode (Jan 09), DAve said: The developers response, for those who are interested. hi Dave, the initiator for iSCSI will hit stable/current real soon now. that was the good news, now for the down side: what was missing all along was recovery from network disconnects, so while I think I have it almost worked out, I've come across a major flow in the iscsi design: when the targets crashes, and comes back, there is no way to tell the client to run an fsck. This is not a problem if the client is mounting the iscsi partition read only. danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. On Tuesday 09 January 2007 02:06, Danny Braniss wrote: Hi, While I think I have almost solved the problem of network disconnects, It downed on me a major problem: When a 'local' disk crashes, the kernel will probably hang/panic/crash. if i don't try to recover, then there is no change in the above scenario. if i try to recover, then the client does not know that it should umount/fsck/mount. While all this seems familiar, removing a floppy/disk-on-key while it's mounted, we could always say you shouldn't have done that!, with a network connection, it can happen very often - rebooting the target, a network hickup, etc. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Intel 945GM chipset support
On Wednesday 07 June 2006 11:34, Vladimir Terziev wrote: This doesn't sound good :( As i found in XOrg's documentation, i945 graphics chip is supported by i810 XOrg driver, but i suppose the apg support must be provided by the kernel ?! I suspect that you will have agp support if you run a recent (post 6.1) -stable or -current. I have an 845G and it started working (without any patching from me) a little while ago: agp0: Intel 82845G (845G GMCH) SVGA controller mem 0x8800-0x8fff,0x8000-0x8007 irq 16 at device 2.0 on pci0 drmsub0: Intel i845G GMCH: (child of agp_i810.c) on agp0 Also, there is an entry for the i945G and i945GM in src/sys/dev/drm/drm_pciids.h on my system (recent 6-STABLE). HTH, JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: increasing dd disk to disk transfer rate
On Friday 13 January 2006 08:29 am, Christoph P. Kukulies wrote: On Thu, Jan 12, 2006 at 02:23:37PM -0700, Kenneth D. Merry wrote: written by phk) that is designed to do disk-to-disk recovery - it copys data in big slabs until it gets an error and then works around the faulty area block by block. It's called 'recoverdisk', and is in src/tools/tools/recoverdisk. I used it to copy a friend's hard drive, and it worked well. (Although the supposedly 'bad' disk didn't turn out to have any bad sectors.) I was able to recover. The 0.9980 copy of my damaged disk to the identical new one, using recoverdisk /dev/ad2 /dev/ad3 turned out to have been successful. The program was still trying to improve the result but I didn't see any increase of recoverd block, so I terminated it. Just for the record: Before I wanted to give back in my faulty disk to my computer supplier as a case for warranty, I zeroed out the faulty disk. dd if=/dev/zero of=/dev/ad2 bs=1m It took half an hour to zero out the 80GB. Transferrate 44 MB/s? And not a single error ? Or is this normal? Then I tried to read back dd if=/dev/ad2 of=/dev/zero bs=2m Yes, just for the fun I said 2m blocksiye. And now we come back to FreeBSD contents: The system froze at this command (FreeBSD 5.2.1 on that machine) I don't know if this is why the system froze, but /dev/zero is probably not a useful output device. You could use of=/dev/null just to see if the disk reads succeed w/o errors. I've also done cmp /dev/adX /dev/zero before, but you don't have any control over how the disk reads are handled that way. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sata
On Thursday 13 October 2005 01:29, rusel wrote: Hello, does any FreeBSD relase supports Intel`s SATA Controller? 1) You should have been able to find this out on your own. Specifically here: http://www.freebsd.org/releases/5.4R/hardware-i386.html (which is linked to from the Release Information page of the main FreeBSD website) and here: http://www.freebsd.org/cgi/man.cgi?query=atasektion=4manpath=FreeBSD+5.4-RELEASE (which is linked to from the above link, among other places) 2) Even if you couldn't find this info on your own, this is entirely the wrong mailing list. -questions or -stable might have been more appropriate. 3) Which Intel SATA controller are you asking about? 4) The answer is probably yes. The ata driver in FreeBSD 6.0 supports every mainstream Intel ATA controller I'm aware of, up to and including ICH6 (ICH5 for FreeBSD 5.4 according to the manpage above). JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel.gz.aa kernel.gz.ab
On Monday 05 September 2005 04:56 am, Matthew West wrote: On Fri, Sep 02, 2005 at 08:47:30AM -0400, John Nielsen wrote: On Friday 02 September 2005 08:35, Donatas wrote: wonder how could I decompress $subj filesthey doesn't seems to be in tar or gzip formats. files are taken from kern1.flp nad kern2.flp on 5.4-RELEASE/floppies cat kernel.gz.aa kernel.gz.ab kernel.gz gunzip kernel.gz You're still missing the first part of the file. You also need to grab kernel.gz.boot from the boot.flp image. Then you can do a: cat kernel.gz.boot kernel.gz.aa kernel.gz.ab kernel.gz That makes sense. Do you know offhand what the other file on the boot floppy is for (kernel.gz.split, I believe)? JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel.gz.aa kernel.gz.ab
On Monday 05 September 2005 07:58 pm, John Nielsen wrote: On Monday 05 September 2005 04:56 am, Matthew West wrote: On Fri, Sep 02, 2005 at 08:47:30AM -0400, John Nielsen wrote: On Friday 02 September 2005 08:35, Donatas wrote: wonder how could I decompress $subj filesthey doesn't seems to be in tar or gzip formats. files are taken from kern1.flp nad kern2.flp on 5.4-RELEASE/floppies cat kernel.gz.aa kernel.gz.ab kernel.gz gunzip kernel.gz You're still missing the first part of the file. You also need to grab kernel.gz.boot from the boot.flp image. Then you can do a: cat kernel.gz.boot kernel.gz.aa kernel.gz.ab kernel.gz That makes sense. Do you know offhand what the other file on the boot floppy is for (kernel.gz.split, I believe)? .. or I could just follow your advice: Take a look at src/release/scripts/split-file.sh to see how these files are generated. Sorry for the noise. (kenel.gz.split is the split index file) JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kernel.gz.aa kernel.gz.ab
On Friday 02 September 2005 08:35, Donatas wrote: wonder how could I decompress $subj filesthey doesn't seems to be in tar or gzip formats. files are taken from kern1.flp nad kern2.flp on 5.4-RELEASE/floppies cat kernel.gz.aa kernel.gz.ab kernel.gz gunzip kernel.gz JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Locating obsolete ports distfiles
On Monday 22 August 2005 12:43 am, Mike Meyer wrote: In [EMAIL PROTECTED], Peter Jeremy [EMAIL PROTECTED] typed: I currently have just over 8GB is /usr/ports/distfiles. Some of these files are more than 10 years old and long obsolete. Does anyone have any suggestions on how to identify which files are no longer referenced by current ports? Doing a 'make checksum' on every installed port and then looking at the atimes is one approach but this doesn't handle: - ports that I don't currently have installed but might need - ports installed on systems that mount /usr/ports readonly Install sysutils/portupgrade, and do a portsclean -D. That will remove all the distfiles that aren't referenced by any port in the tree. Do portsclean -DD and it'll remove all distfiles not used by an installed port. Alternatively there is the distclean.sh script in ports/Tools/scripts. Run it with the -f switch to delete outdated distfiles without confirmation. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nForce3 NIC on 5.3 (i386)
On Wednesday 19 January 2005 12:29 am, Sven Ahtama wrote: Anyone here who have managed to get the nForce3 MCP NIC to work with FreeBSD 5.3 on i386 platform? FWIW, I've had pretty much the same experience, although you were more thorough than I was. I installed 5.3-R on a new motherboard with an MCP chipset and installed the net/nvnet port. No complaints, no errors, no NIC. I'm using a PCI card for the time being but I would love to hear about a way to get the onboard NIC working if there is one. JN ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and MySQL - mysqld eats CPU alive
On Saturday 31 July 2004 21:08, adp wrote: I recently posted the following message to MySQL discussion list. The response there, and the one I keep finding on Google, is that this is a long-standing issue betweeen FreeBSD and MySQL. For me this has been happening since FreeBSD 4.4. I don't have any additional info about the problem, but as you say it does seem to be a long-standing issue. The hosting company I use (johncompanies.com -- highly recommended) has a nanny script that you may find useful: http://www.johncompanies.com/collocation/knowledge/freebsd_mysqld_nanny.txt HTH, JN ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB support for new HP printers?
On Monday 02 December 2002 05:13, Bernd Walter wrote: On Sun, Aug 25, 2002 at 11:36:15PM -0600, John Nielsen wrote: Are there plans to add USB support for HP's newer printers to FreeBSD? Specificially, the OfficeJets and the LaserJet 1200? They use a new/different/broken USB interface so they're just recognized as ugen devices at the moment.. Can you tell details about the difference? Not really. Pretty much everything I know I learned from corresponding with David Paschal on the hpoj-devel mailing list (see hpoj.sourceforge.net). If Geocrawler ever comes back up today you can browse the list. See the thread FreeBSD howto? starting August 26 2002. Here is a quote from Mr. Paschal in one of those e-mails: Hi, John. The LaserJet 1200 advertises several alternate settings for the printer-class interface: 7/1/3 (for IEEE 1284.4 packets, the new and different USB interface you mentioned), 7/1/2 (bidirectional raw print data), and 7/1/1 (unidirectional raw print data). If you can somehow convince the ulpt driver to bind to 7/1/2 or 7/1/1 rather than just blindly binding to the first alternate setting it finds, then that should be all you need. The above quote is in reference to getting printing (and only printing) to work on an LJ 1200. For full functionality, you'd need to do a bit more. I think the hpoj project was leaning towards a cross-platform userland solution (hack?) rather than doing kernel mods on several different platforms. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Arp and Route Commands
On Sunday 17 November 2002 13:53, Karl Timmermann wrote: I'm new to the list and was hoping maybe someone could help me. These commands work in Linux (and in this order), but not in FreeBSD/Mac OS X as the arp and route commands are different: arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 arp -s 10.10.10.0 00:00:ca:13:4b:54 -i eth1 route add -net 10.10.10.0 netmask 255.255.255.0 dev eth1 route add default gw 10.10.10.0 dev eth1 anyone know how i would change these commands to work with the FreeBSD versions of arp and route? man arp man route ask on -questions and because I'm feeling helpful: arp -s 10.10.10.1 00:00:ca:13:4b:54 arp -s 10.10.10.2 00:00:ca:13:4b:54 route add -net 10.10.10.0 -netmask 255.255.255.0 -interface fxp0 route add default 10.10.10.1 -interface fxp0 FreeBSD's arp doesn't allow you to specify an interface. Adding the same host to the arp table twice is pointless and would probably produce an error, so I changed the addresses. Replace fxp0 with the name of the interface in question. With a netmask of 255.255.255.0, 10.10.10.0 is a network address and can't (or at least shouldn't) be used as a router or client address (changed in the example above). I'm forced to wonder why you would want to run this sequence of commands and if there isn't a better way to achieve the desired result. Please reply off-list if you feel so inclined. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: USB support for new HP printers?
On Monday 26 August 2002 02:51, Marco Molteni wrote: On Sun, 25 Aug 2002 23:36:15 -0600, John Nielsen [EMAIL PROTECTED] wrote: Are there plans to add USB support for HP's newer printers to FreeBSD? Specificially, the OfficeJets and the LaserJet 1200? They use a new/different/broken USB interface so they're just recognized as ugen devices at the moment.. have a look at hpoj.sourceforge.net they plan FreeBSD USB support for a next release I've been all over the site and read some of the docs. The most useful piece of information I found was this: FreeBSD, NetBSD, and OpenBSD are not yet supported in USB mode, due to missing functionality in the kernel ulpt driver (bidirectional I/O, device ID retrieval, switching to 7/1/3, and HP channel-change-request). The only FreeBSD information in the TODO section has to do with fixing the build so it works [better]. I don't get the idea that they are planning to add the missing kernel functionality themselves; they don't seem to have done any of that for Linux--they just list using a supported kernel as a requirement for USB. Since I'm mostly just interested in printing to an LJ 1200, I don't know if I'd even use the hpoj stuff unless necessary (although it does look interesting). I'm just wondering if kernel support for these beasties is already being worked on, and where I can get more information. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
USB support for new HP printers?
Are there plans to add USB support for HP's newer printers to FreeBSD? Specificially, the OfficeJets and the LaserJet 1200? They use a new/different/broken USB interface so they're just recognized as ugen devices at the moment.. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: offtopic: low level format of IDE drive.
Julian Elischer [EMAIL PROTECTED] wrote: One of my FreeBSD development boxes had a hernia last week when it lost power while writing to disk. The drive wrote out garbage to a track. I want to reformat the drive, (low level) but the bios doesn't have any support to do this (In the past That is how I did this). The machiine has 1 CD drive and no floppy.. anyone with any ideas as to how one can reformat a hard drive feel free to lend me a clue.. Boot from a fixit CD, and use dd to zero out the whole disk, e.g.: dd if=/dev/zero of=/dev/ad0c JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: multi-link 802.11b through netgraph yields poor performance.
John Kozubik wrote: Julian, Archie, et al, I have experimented with a multi-link 802.11b connection between two laptops. Both are 4.5-RELEASE, one has two aironet LMC352 cards, and one has two Lucent gold cards. I have successfully used ng_one2many, etc., to establish a working multi-link between the two systems - however, I would appreciate any comments regarding the very poor performance I see when networked in this manner. The problem I see is that, when using `ping` on either machine, exactly every other packet is dropped. After running `ping` for many minutes, trying it from both machines, it is clear that _exactly_ every other packet is dropped. Further, echo response time is between 2.2 and 2.5 milliseconds, which seems very high. snip Any comments as to why the problems I am seeing (half of packets dropped and high latency) exist are appreciated. I am using a multilink connection between a fileserver and a switch, and it works fine. This is with regular 100Mbit ethernet cards. On one occasion I unplugged the secondary NIC from the switch without undoing the one2many setup. And every other packet to the machine was dropped. I saw the same thing you were seeing with your pings. So.. I would think that netgraph is doing its thing, distributing packets evenly between your two interfaces, but that one of the interfaces isn't behaving. My one2many script is essentially the same as yours except for the order. I don't know if it makes a difference (it _shouldn't_), but in my script I bring the secondary interface up before doing anything else (and then I load the ng_ether and ng_one2many modules, but I assume you're doing that elsewhere). I don't know a great deal about any of this, but I thought this might give you a clue as to what to look for. Good luck, JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 2.2.x ISO images.
- Original Message - From: Jefferson Harlough [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, June 23, 2002 12:19 PM Subject: FreeBSD 2.2.x ISO images. Where might I find ISO images for the FreeBSD 2.2.x releases? Do such files exist? I have an older system with a non-IDE Creative CD-ROM drive, and FreeBSD 4.x seems to not support that drive any more. I do have several FreeBSD 3.x releases, but they always hang with a kernel panic when booting via the included bootdisks. Would the FreeBSD 2.2.x series of releases work with such a CD-ROM drive? You CD-ROM is _probably_ usable under 4.x with one of either the mcd, scd, or matcd drivers. These have been removed from the GENERIC kernel, but are still available as options for a custom kernel. See their respective manpages (as well as LINT) for more info. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: I Volunteer
- Original Message - From: Evan Dower [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 18, 2002 11:35 PM Subject: I Volunteer I don't know who might have use of my services (or what my services might be for that matter), but I hereby offer them up. I'm a student at the University of Washington and I'll be applying to the Computer Science major in February. I'd like to get involved with the OS that is serving me so well. I'll do what I can to help with whatever. Just let me know if anyone needs a minion. I could use the experience. Probably the best thing you can do for the project is to show some initiative. The problem reports database (accessible over the web at http://www.freebsd.org/prstats/index.html) can always use a good looking-over. Some reports are outdated and just need to be closed; some have a working patch included but have fallen through the cracks; and depending on your interests and level of coding ability, some could be relatively easy to fix. Do some work, make some noise, and express your interests and then whoever wants you as a minion will be more likely to find you. Whether or not coding is your forte, you can support the project in other ways as well. FreeBSD has great documentation, but it can always be improved or added to. I tend to proofread everything I read, so I've sent in a couple bug reports about manpage typos. I've been pleasantly surprised at both the promptness with which they were addressed and the gratitude expressed for my filing the reports. Evangelism and peer support are other great things you can do. Educate people at your school about FreeBSD and suggest ways that using FreeBSD might improve a lab/program/service. Answer questions on the -questions mailing list and/or the comp.unix.bsd.freebsd.misc newsgroup. FreeBSD is a great platform with an even greater user/developer community, so letting people know about it is always a good thing. Just a few ideas from my own experience... :) JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: gif(4) tunnel through MSN DSL modem
- Original Message -
From: Nielsen [EMAIL PROTECTED]
To: John Nielsen [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, June 14, 2002 1:31 AM
Subject: Re: gif(4) tunnel through MSN DSL modem
I have this working fine. On the BSD machine behind NAT the tunnel looks
like it's between a 192.168.x.x IP and the public IP of the machine across
the internet. On the remote machine it looks like a normal tunnel between
the two IPs. NAT takes care of the translation on the tunnel packets.
That's good news! However, I'm not sure I can do the same in this case.
I've used gif tunnels, vtund, and even IPSEC in this configuration just
fine. Of course holes have to punched in NAT (bimap, port mapping or
whatever it's called on your DSL). That's for reliability and so that the
tunnel can be initiated from either end.
Do you mean the NAT that the modem is doing? If so, that's a problem. I'm
using an Arescom NetDSL 800 series modem, which comes pre-configured per
stringent specifications from MSN. And (as far as I know--and I've looked)
there is no way for me to do any kind of configuration on it at all. If
that weren't the case, I'd just put the thing in bridge mode and have done
with it.
If it were up to me, I'd switch to a sane ISP--but it's not up to me in this
case. If I've misunderstood and you think this will work without being able
to reconfigure the modem at all, then by all means please provide some more
detail. :)
JN
- Original Message -
From: John Nielsen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, June 11, 2002 13:20
Subject: gif(4) tunnel through MSN DSL modem
Hi folks,
I tried this on -questions without any luck, so I'm hoping for a better
response here . :)
I remotely administer a FreeBSD 4.5 machine that is connected to the
internet through and MSN DSL modem. This modem does NAT (for a single
client) rather than bridging the connection. So the FreeBSD machine
thinks
its public address is 192.168.1.2 (when in reality the modem is the only
device with a public address). This machine is itself doing NAT, acting
as
a firewall and gateway for a private network.
I would like to establish a gif(4) tunnel between this machine and my
firewall here in order to link the two private networks into one virtual
network. I have done this before with two machines that were directly
connected to the internet, but in this case the DSL modem on the far end
seems to be fouling things up. The modem seems to be passing everything
through, but I haven't gotten gif to work.
Any ideas? Here's what I've tried--this is how I'd set it up if the DSL
modem weren't in the way.
[excerpts from rc.conf on far (DSL) end]
# Private interface
ifconfig_xl0=inet 192.168.6.1 netmask 255.255.255.0
# Public interface -- 192.168.1.2 netmask 255.255.255.252
ifconfig_ed0=DHCP
gif_interfaces=gif0
gifconfig_gif0=DSL.public.ip myend.public.ip
ifconfig_gif0=192.168.6.1 192.168.0.1
static_routes=john
route_john=-net 192.168.0 -interface gif0
[excerpts from rc.conf on this {my) end]
# Private interface
ifconfig_ep0=inet 192.168.0.1 netmask 255.255.255.0
# Public interface
ifconfig_ed0=DHCP
gif_interfaces=gif0
gifconfig_gif0=myend.public.ip DSL.public.ip
ifconfig_gif0=192.168.0.1 192.168.6.1
static_routes=DSL
route_DSL=-net 192.168.6 -interface gif0
I've tried both the modem's (real) public address and 192.168.1.1 (the
public interface's address) for DSL.public.ip, but neither seems to
work.
Can this be made to work? Can gif be hacked so it will work?
I can't justify switching to a more expensive provider just so this
tunnel
will work, since it will mostly be a convenience for me and not the
client.
As far as I know, there's no way to modify any settings on the DSL modem
itself. I do have full access to both FreeBSD machines. Again, any
suggestions or even a detailed description of why this won't work would
be
appreciated.
Thanks,
JN
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
gif(4) tunnel through MSN DSL modem
Hi folks,
I tried this on -questions without any luck, so I'm hoping for a better
response here . :)
I remotely administer a FreeBSD 4.5 machine that is connected to the
internet through and MSN DSL modem. This modem does NAT (for a single
client) rather than bridging the connection. So the FreeBSD machine thinks
its public address is 192.168.1.2 (when in reality the modem is the only
device with a public address). This machine is itself doing NAT, acting as
a firewall and gateway for a private network.
I would like to establish a gif(4) tunnel between this machine and my
firewall here in order to link the two private networks into one virtual
network. I have done this before with two machines that were directly
connected to the internet, but in this case the DSL modem on the far end
seems to be fouling things up. The modem seems to be passing everything
through, but I haven't gotten gif to work.
Any ideas? Here's what I've tried--this is how I'd set it up if the DSL
modem weren't in the way.
[excerpts from rc.conf on far (DSL) end]
# Private interface
ifconfig_xl0=inet 192.168.6.1 netmask 255.255.255.0
# Public interface -- 192.168.1.2 netmask 255.255.255.252
ifconfig_ed0=DHCP
gif_interfaces=gif0
gifconfig_gif0=DSL.public.ip myend.public.ip
ifconfig_gif0=192.168.6.1 192.168.0.1
static_routes=john
route_john=-net 192.168.0 -interface gif0
[excerpts from rc.conf on this {my) end]
# Private interface
ifconfig_ep0=inet 192.168.0.1 netmask 255.255.255.0
# Public interface
ifconfig_ed0=DHCP
gif_interfaces=gif0
gifconfig_gif0=myend.public.ip DSL.public.ip
ifconfig_gif0=192.168.0.1 192.168.6.1
static_routes=DSL
route_DSL=-net 192.168.6 -interface gif0
I've tried both the modem's (real) public address and 192.168.1.1 (the
public interface's address) for DSL.public.ip, but neither seems to work.
Can this be made to work? Can gif be hacked so it will work?
I can't justify switching to a more expensive provider just so this tunnel
will work, since it will mostly be a convenience for me and not the client.
As far as I know, there's no way to modify any settings on the DSL modem
itself. I do have full access to both FreeBSD machines. Again, any
suggestions or even a detailed description of why this won't work would be
appreciated.
Thanks,
JN
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: gif(4) tunnel through MSN DSL modem
- Original Message - From: Lars Eggert [EMAIL PROTECTED] To: John Nielsen [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, June 11, 2002 4:13 PM Subject: Re: gif(4) tunnel through MSN DSL modem John Nielsen wrote: [excerpts from rc.conf on far (DSL) end] # Private interface ifconfig_xl0=inet 192.168.6.1 netmask 255.255.255.0 # Public interface -- 192.168.1.2 netmask 255.255.255.252 ifconfig_ed0=DHCP gif_interfaces=gif0 gifconfig_gif0=DSL.public.ip myend.public.ip ifconfig_gif0=192.168.6.1 192.168.0.1 static_routes=john route_john=-net 192.168.0 -interface gif0 The problem (one part, at least) is that you use the same IP address (192.168.6.1) on your xl0 and gif0 interfaces (on both ends). You'll want the tunnel addresses to be in a different subnet. I have another tunnel set up this way and it works fine. Why should the tunnel addresses be on a different subnet? Also, the netmask in the infconfig_xl0 line doesn't match the comment, which one is wrong? The public interface (ed0) always gets the same address from the DSL modem, even though it's using DHCP. I think you associated the comment with the wrong ifconfig line (I've added a break between them to clarify). I'm starting to think that it would be easier to use ppp/tun and ssh rather than gif in this instance, even though I'm less familiar with that arrangement. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: load balancing with 2 nic cards possible?
- Original Message -
From: Gary Stanley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, April 26, 2002 9:47 PM
Subject: load balancing with 2 nic cards possible?
Is it possible to split the load of IP traffic with 2 ethernet cards on a
4.x machine? I'm new to load balancing in a sense, however, I'd like to
try something that seems more robust
The netgraph one2many framework allows you to aggregate 2 or 4 NICs together
even on an unmanaged switch. Obviously, this is only really beneficial if
the machine is serving several clients attached to the same switch or if
there is another machine set up similarly (also on the same switch), since
unmanaged switches generally only have one uplink port.
See the ng_one2many(4) manpage for details. Following is a script I use to
set this up (I call it from rc.local). fxp0 is the primary interface and
rl0 is the secondary.
JN
-
#!/bin/sh
ifconfig rl0 up
kldload /modules/ng_ether.ko
kldload /modules/ng_one2many.ko
ngctl mkpeer fxp0: one2many upper one
ngctl connect fxp0: fxp0:upper lower many0
ngctl connect rl0: fxp0:upper lower many1
ngctl msg rl0: setpromisc 1
ngctl msg rl0: setautosrc 0
ngctl msg fxp0:upper setconfig {xmitAlg=1 failAlg=1 enabledLinks =[ 1
1 ] }
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: firewall and ports
- Original Message - From: Martin Vana [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, March 12, 2002 3:55 PM Subject: firewall and ports hi, I sit behind a tough firewall, and none of the ports in port collection is able to fetch files need for install. How could I overcome the firewall? This belongs more on -questions than it does on -hackers. Also, you don't give any specifics on what your firewall does and does not allow you to do. You may be able to fetch through your firewall by enabling passive mode. To do so, set the environment variable FTP_PASSIVE_MODE to anything but no. fetch(1) also has a -p flag that does the same thing. See the manpages for fetch(1) and fetch(3) for other options, including using an ftp and/or an http proxy. JN To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
