Re: Just a test
Sam Stein wrote: I'm trying to get my mail stuff all working correctly... this is just a test. Please use the freebsd-test mailing list for further test as it was designed just for the purpose of testing. Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Don't buy AMD products (was Re: Xorg and ATI card query.)
Andrew Reilly wrote: On Tue, 13 Mar 2007 14:17:00 -0800 (PST) Doug Ambrisko <[EMAIL PROTECTED]> wrote: One thing that is a plus with nv is that X has some support for it, whereas, the newer ati cards have no support :-( I was a fan of ati since it was easier to get support. Now I'm starting to lean towards Nvidia :-( Does anyone know if there are *any* contemporary graphics cards that have 3D acceleration supported by some flavour of open-source x.org? Doesn't have to be a super-fast 'leet gamer system to be better than a non-accelerated frame buffer. Matrox used to have a reputation for goodness (I used to have a G400 or the like), but it's been a long time... (I'm currently using a lowish-end NVidia card under the x.org nv driver, but it has issues (of which no 3D accel is but one...) Cheers, Try the 'vesa' xorg driver. It may not be fancy or all that accelerated but it works quite well. I have an nvidia card and cannot get it to work for the life of me. the drive attached, but nothing happens after that. It might be the fact that I have a PCI express card. But the vesa driver is working just fine for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsnap and cvsup for rebuilding world - Which one?
frzburn wrote: Well, again, thanks for all your replies! =) After all you told me, I guess this guides describes the right tools to use and the right way for rebuilding world. http://www.bsdguides.org/guides/freebsd/beginners/update_freebsd.php Thanks! frzburn On 3/4/07, Ronald Klop <[EMAIL PROTECTED]> wrote: On Sun, 04 Mar 2007 04:23:55 +0100, frzburn <[EMAIL PROTECTED]> wrote: > Hi everyone, [cut some text] > So here come my questions: > Is portsnap syncing the sources correctly for rebuilding world, or must I > use cvsup? > If so, of what use is portsnap if I must use cvsup for synchronizing my > source? > > In fact, I'm just looking at the most up-to-date/approved/correct > technique/tool to synchronize my source for ``rebuilding world'' with the > latest sources from FreeBSD-6-STABLE. Read this. It tells you why portsnap is invented. And why cvsup/csup is still better for other things then ports. http://www.daemonology.net/portsnap/ Ronald. -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" It might be worth noting you can set KERNCONF in your make.conf and you can just do make kernel instead of make buildkernel && make installkernel. it just runs both for you. There's no difference it is just a shorter path (not much though). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dd as an imaging solution.
John-Mark Gurney wrote: Antony Mawer wrote this message on Tue, Feb 06, 2007 at 17:04 +1100: On 6/02/2007 1:47 PM, Sean Bryant wrote: Dominic Marks wrote: Check out G4U (NetBSD based) The only problem I can see here is that multiple parallel reads will have serious performance impacts, thus greatly increasing the cloning of the disk. The solution with dd, tee and netcat would just daisy chain the copy across the network which would be way faster. Now all you need is G4U to operate in a multicast manner like Symantec Ghost Corporate Edition, and your transfer speed wouldn't reduce with each additional client (eg. 100mbps for 1 client, 50mbps each for 2 clients, 33.3mbps each for 3 clients, ...) Add FEC to the multicast, and you can constantly stream the data, and not have to worry about dropped segments as much... Can you explain this? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dd as an imaging solution.
Antony Mawer wrote: On 6/02/2007 1:47 PM, Sean Bryant wrote: Dominic Marks wrote: Check out G4U (NetBSD based) The only problem I can see here is that multiple parallel reads will have serious performance impacts, thus greatly increasing the cloning of the disk. The solution with dd, tee and netcat would just daisy chain the copy across the network which would be way faster. Now all you need is G4U to operate in a multicast manner like Symantec Ghost Corporate Edition, and your transfer speed wouldn't reduce with each additional client (eg. 100mbps for 1 client, 50mbps each for 2 clients, 33.3mbps each for 3 clients, ...) --Antony Exactly. That's what I was really going for. Except Freesbie 2.0 sorta doesn't let me write to the character device over the network . ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dd as an imaging solution.
Dominic Marks wrote: On Sat, 03 Feb 2007 19:43:42 -0500 Sean Bryant <[EMAIL PROTECTED]> wrote: Several months ago I was using Freesbie 1.x to dd a harddrive across the network as a drive duplication effort. This worked 7 computers got the image. I'm trying to do this again so I got the new Freesbie release 2.0 and fired it up across the computers and tried something simple such as: dd if=/dev/ad0 bs=1m | nc othercomputer 1 on the image provider nc -l 1 | dd of=/dev/ad0 bs=1m on the computer to receive the image. I received an operation not permitted. My first thought was they must be mounted. a quick check, and it seems they weren't. Next, am I really root? And sure enough I was. After a bit of discussion in #freesbie on freenode got me to set kern.geom.debugflags to 16 and I was able to write to ad0 like I had previously done. Yet when I tried to write to an individual slice I was presented with the same error. Anyone have any clue ? The eventual goal is to have a mass imaging all at once with dd, nc and tee Check out G4U (NetBSD based) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" The only problem I can see here is that multiple parallel reads will have serious performance impacts, thus greatly increasing the cloning of the disk. The solution with dd, tee and netcat would just daisy chain the copy across the network which would be way faster. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
dd as an imaging solution.
Several months ago I was using Freesbie 1.x to dd a harddrive across the network as a drive duplication effort. This worked 7 computers got the image. I'm trying to do this again so I got the new Freesbie release 2.0 and fired it up across the computers and tried something simple such as: dd if=/dev/ad0 bs=1m | nc othercomputer 1 on the image provider nc -l 1 | dd of=/dev/ad0 bs=1m on the computer to receive the image. I received an operation not permitted. My first thought was they must be mounted. a quick check, and it seems they weren't. Next, am I really root? And sure enough I was. After a bit of discussion in #freesbie on freenode got me to set kern.geom.debugflags to 16 and I was able to write to ad0 like I had previously done. Yet when I tried to write to an individual slice I was presented with the same error. Anyone have any clue ? The eventual goal is to have a mass imaging all at once with dd, nc and tee ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Building a kernel with config ?
Gouverneur, Thomas wrote: Make buildkernel KERNCONF=CONFIG Make installkernel KERNCONF=CONFIG This is enough for only compiling kernel and not world and this is the Smartest way according to FreeBSD handbook. -- Thomas Gouverneur Junior UNIX Administrator TI Automotive -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pete French Sent: mardi 26 septembre 2006 12:24 To: freebsd-stable@freebsd.org Subject: Building a kernel with config ? On Mon, 25 Sep 2006 11:34:42 -0700, "Kevin Oberman" <[EMAIL PROTECTED]> wrote: 2. Building a kernel with config is not officially supported. It's at your risk and may not work in all cases. Build a kernel with: cd /usr/src make buildkernel I was not aware that you wern't supposed to use config anymore - and I am not convinced that the suggested alternative is actually a replacement as I thought that buildkernel required you to have built the world first ? Is this no longer true ? If it *is* true thhen what is the alternative to using 'config' which should be used if you are on a system where you do not have the time or the disc space to rebuild the world and simply want to recompile the kernel ? -pete. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Another way you could achieve the same thing is: make kernel KERNCONF=KERNNAME this will combine both steps in to one. Also for those who want to omit the KERNCONF step set KERNCONF in /etc/make.conf and you can omit the KERNCONF argument. Its sometimes nice to keep things really simple. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.x on an IBM T42 laptop
Works like a charm.
On 5/4/06, Nik Clayton <[EMAIL PROTECTED]> wrote:
I've got an IBM T42 laptop that's currently running 5.4, and it's working
nicely at the moment. ACPI works well enough that suspend to RAM works
('zzz'), the audio works, USB devices are recognised, and the battery life's
reasonable (with est enabled).
Is anyone aware of any regressions in laptop functionality going from 5.4 to
6.x?
N
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Sean Bryant
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipw2100 vs ndis(4) -- does it work for anybody?
Fails on build saying that stuff is used but not defined. Lots of warnings all over the place. And the nic is 100% nids compatible. On 5/4/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: On 5/3/06, Sean Bryant <[EMAIL PROTECTED]> wrote: > On 5/3/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: > > On 5/2/06, Sean Bryant <[EMAIL PROTECTED]> wrote: > > > ndisgen is broken on 6.1 RC1 if I remember correctly. > > > > ndisgen wasn't broken, wpa_supplicant was broken as it didn't > > recognize the ndis interfaces. The fix has since been applied to > > -CURRENT and MFC'd to the RELENG_6 and RELENG_6_1 branches. > > > ndisgen fails for me on 6.1-RC1 and 6.1-RC2. > > Any ideas? How is it failing? Yesterday I updated to the latest RELENG_6, and ndisgen built the driver module for my Broadcom Wirless device (bcmwl564_sys.ko) on FreeBSD/amd64. -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. -- Sean Bryant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipw2100 vs ndis(4) -- does it work for anybody?
ndisgen fails for me on 6.1-RC1 and 6.1-RC2. Any ideas? On 5/3/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: On 5/2/06, Sean Bryant <[EMAIL PROTECTED]> wrote: > ndisgen is broken on 6.1 RC1 if I remember correctly. ndisgen wasn't broken, wpa_supplicant was broken as it didn't recognize the ndis interfaces. The fix has since been applied to -CURRENT and MFC'd to the RELENG_6 and RELENG_6_1 branches. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. -- Sean Bryant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipw2100 vs ndis(4) -- does it work for anybody?
ndisgen is broken on 6.1 RC1 if I remember correctly. On 5/2/06, Scot Hetzel <[EMAIL PROTECTED]> wrote: On 5/2/06, Ulrich Spoerlein <[EMAIL PROTECTED]> wrote: > Good day, > > since the ipw(4) driver can't do WPA, I wanted to give ndis(4) a try. > This *used* to work back on 5.3 (memory is a bit vague) but it ain't > happening on 6.1-RC. > > I'm using the same driver as last time, which is the version 1.2.2.8 > from Intel. I also downloaded the newest one, version 1.2.4.35, but none > of them attach, when loading the if_ndis module. > > /sys/modules/if_ndis# make clean > /sys/modules/if_ndis# ndiscvt -i /compat/ndis/w70n51.inf -s /compat/ndis/w70n51.sys -o ndis_driver_data.h You need to use the ndisgen script to create the NDIS kernel module for your card. ndisgen /compat/ndis/w70n51.inf /compat/ndis/w70n51.sys then you use kldload to load the module: kldload w70n51_sys.ko Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Sean Bryant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cc can't build 32-bit executables on amd64
Then why not work on adding the functionality? I'm sure freebsd people would love to have a proper working 32 bit compatibility layer happening. On 5/1/06, Mikhail Teterin <[EMAIL PROTECTED]> wrote: понеділок 01 травень 2006 18:55, Jonathan Noack написав: > Did you miss the previous reply which mentioned using '-B/usr/lib32 > -B/usr/local/lib32' in addition to '-m32'? I did not miss this work-around. But it is not a proper way -- one need not specify -B/usr/lib in the 64-bit case. Nor should one need to specify -B/usr/lib32, when using the -m32 flag. The gcc's multilib.h functionality is just for that. We just aren't using it (although we do for for aout) -- presumably, because there *was* a much bigger fish to fry to enable such compiles... -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Sean Bryant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fwd: cc can't build 32-bit executables on amd64
Sorry incase any of you else are interested. Read Below. -- Forwarded message -- From: Sean Bryant <[EMAIL PROTECTED]> Date: May 1, 2006 4:41 PM Subject: Re: cc can't build 32-bit executables on amd64 To: Mikhail Teterin <[EMAIL PROTECTED]> add the flag -B/usr/lib32 and -B/usr/local/lib32 to cc. This will fix linking. So its not a problem. On 5/1/06, Mikhail Teterin <[EMAIL PROTECTED]> wrote: Can I direct someone's attention to the annoying but easy to fix bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 There are still a few days left to make sure, FreeBSD-6.1 is shipped with amd64 being able to link 32-bit executables. Release Engineers insist, it must be fixed in current first... Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Sean Bryant -- Sean Bryant ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[patch[ twa, bus_dma.h, busdma_machdep.c (amd64)
I loaded up 6.1-Stable on a Dual Dual Core Opteron, with a 3ware 9550sx-4lp raid card in it and noticed a horrid boot time. Well after investigating the issue it turns out the twa driver had problems creating the bus_dmamaps. It was creating 255 request buffers and giving each of them a dma map. Yippie! This leaves me with about a 7 - 10 minute boot time. To correct this problem I created a bus_dmamap_create_v (should probably be called bus_dmamap_create_many as mux suggested) and this creates a large amount of dma maps all at once. Obviously to test I modified the twa driver to use the new function. I've seen no problems so far. let me know if you see any glaring errors. As there are probably some. Disk performance remained the same just speed up boot time considerably. This is only tested with amd64 code. The code *should* work with i386, but I wasn't able to test it. Please test and let me know of any problems. And I apologize ahead of time if this is useless I don't know much about the topic but was in need of a quick fix. -- Sean Bryant busdma_machdep.c.patch Description: Binary data bus_dma.h.patch Description: Binary data tw_osl_freebsd.c.patch Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
James Tanis wrote: For whatever reason, I have had a similar problem which was solved by entering the machines that you are logging in from into the hosts file. I'm guessing it attempts a reverse lookup and your (as well as my) dns/hostname does not match its reverse lookup entry. On 12/23/05, Michael A. Koerber <[EMAIL PROTECTED]> wrote: All, I have three machines that have had 5.4 and 6.0 installed. Two of the three machines have very well behaved "ssh". However, the machine (laptop) named OBOE does not. Specifically "ssh oboe" will (most of the time) hang for around one minute before asking for a prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other machines) a password is requested within a couple seconds. (I said most of the time, since on occasion I can reboot OBOE and ssh will work just fine...hmmm.) I have looked through the /var/log files for clues and skimmed "man ssh" for time out related stuff, but no luck. Where should I start looking for clues? All machines have had clean installs from "newfs'd" drive under both 5.4 and 6.0 so I'm sure no left over configs are getting propagated. -- - Dr Michael A. Koerber x3250 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- James Tanis [EMAIL PROTECTED] http://pycoder.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" Try disabling sendmail. I don't remember exactly how I came up with this solution but I remember sendmail was the problem. This might work for you as well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
