Re: Finding Drivers For winWiFi Card
On 1/23/2010 10:51 PM, Polytropon wrote: On Sat, 23 Jan 2010 22:35:32 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I hope ifconfig will help more then dmesg as I have no way of getting files (like dmesg.log that I created) off the box (floppy drive isn't even hooked up, IIRC) and rl0 is my wired NIC, non-internal. The ifconfig program (often used as ifconfig -a) tells you only about NICs that are already connected to a driver. Most wireless NICs require loading a specific kernel module (which is not in the GENERIC kernel), and therefore it's helpful to know what exact model it is, so you can load the correct driver. There are of course programs that help you with this: pciconf -lv and usbdevs -v are common tools snip Thanks, this probably wouldn't be such an issue if I hadn't thrown away the box two-three weeks ago (at least, I think I threw it out; I've had the card for about a two years). no...@pci0:2:2:0: class 0x2 card=0x1faa11ab chip=0x00351033 rev=0x43 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology LLC)' device = 'Marvell Libertas 02.llb/g Wireless (8335)' class = network subclass = ethernet I can't find any wlan modules in /boot/kernel that aren't already loaded. P.S.: I'm subscribed to the list, no need to CC me. -- PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Finding Drivers For winWiFi Card
On Sun, Jan 24, 2010 at 05:31:53AM -0600, Programmer In Training wrote: Thanks, this probably wouldn't be such an issue if I hadn't thrown away the box two-three weeks ago (at least, I think I threw it out; I've had the card for about a two years). no...@pci0:2:2:0: class 0x2 card=0x1faa11ab chip=0x00351033 rev=0x43 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology LLC)' device = 'Marvell Libertas 02.llb/g Wireless (8335)' class = network subclass = ethernet zgrep Libertas /usr/share/man/man4/* /usr/share/man/man4/if_malo.4.gz:.Nd Marvell Libertas IEEE 802.11b/g wireless network driver So go and read if_malo(4). It looks like your card is supported, but you need to download a firmware package. This driver was added in 7.1, according to the manpage. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpqDkPTXuf6t.pgp Description: PGP signature
Re: Finding Drivers For winWiFi Card
Do not CC me. I am subscribed to the list. There is no need. THANK YOU. On 1/24/2010 6:22 AM, Roland Smith wrote: snip zgrep Libertas /usr/share/man/man4/* /usr/share/man/man4/if_malo.4.gz:.Nd Marvell Libertas IEEE 802.11b/g wireless network driver So go and read if_malo(4). It looks like your card is supported, but you need to download a firmware package. This driver was added in 7.1, according to the manpage. Roland Thanks. -- PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Finding Drivers For winWiFi Card
On 1/24/2010 6:27 AM, Programmer In Training wrote: Do not CC me. I am subscribed to the list. There is no need. THANK YOU. On 1/24/2010 6:22 AM, Roland Smith wrote: snip zgrep Libertas /usr/share/man/man4/* /usr/share/man/man4/if_malo.4.gz:.Nd Marvell Libertas IEEE 802.11b/g wireless network driver So go and read if_malo(4). It looks like your card is supported, but you need to download a firmware package. This driver was added in 7.1, according to the manpage. Roland Thanks. Thanks for the help folks. I've found everything I need, I believe, now to just do what needs to be done. I'll post here later on today, after I've burned the file to disc (no floppy drive on either computer). -- PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: pf rules
Doug Hardie wrote:
1. pf allows short cuts, but these also makes it more difficult to debug. I'd
separate NAT from filtering,
Ok. I guess you want some white space between them? Here it is with the white
space and comments:
ext_if=dc0
table blackhole persist file /etc/blackhole
table spamd persist
table spamd-white persist
table spamd-white-local persist file /etc/mail/whitelist
MAILHOSTS = {zool.lafn.org}
# NAT/RDR Rules
no rdr on { lo0, lo1 } from any to any
no rdr inet proto tcp from spamd-white-local to any port smtp
no rdr inet proto tcp from spamd-white to any port smtp
rdr pass log inet proto tcp from any to any port smtp - 127.0.0.1 port spamd
# Filter Rules
pass in log inet proto tcp to $MAILHOSTS port smtp keep state
pass in log on sis0 reply-to (sis0 192.168.25.1) proto tcp from any to any port
75 keep state
block in quick log on $ext_if from blackhole to any
Other than the comments I don't see the difference.
you didn't separate nat from filtering, and you didn't add interfaces on
your rdr rules. When you make these shortcuts, maybe your ruleset
becomes more compact, maybe it works, but it becomes more difficult to
debug.
that is never use rdr pass even though pf allows it. You also need to
understand when rdr takes place to write your filtering rules.
That would be really helpful if that information were available somewhere it could be found. I have not been able to find that anywhere.
Basically, for rdr, the address translation takes place before the
packet is parsed by the filter rules. For nat, it takes place after the
filtering. For binat, you can think of it as nat in one direction rdr in
the other.
This is for the first packet, keep state and you don't have to worry
about the rest.
se also,
http://www.openbsd.org/faq/pf/rdr.html
http://www.openbsd.org/faq/pf/nat.html
2. you can deploy one of two policies: Default block with a whitelist or
default pass with a black list. Mixing these is a bad idea.
This is one thing you should see to clarify in your ruleset above. When
you have both whitelist and blacklist what happens to those that are in
neither? what happens to those that are in both.
Which default policy makes sense depends on the service. You may want to
use black lists for smtp but whitelist for ssh for example.
anyway, to interpret the output of pflog, you need the output from pfctl -sr
and pfctl -sn rather than your config file.
zool# pfctl -sr
No ALTQ support in kernel
ALTQ related functions disabled
pass in log inet proto tcp from any to 206.117.18.7 port = smtp flags S/SA keep
state
pass in log on sis0 reply-to (sis0 192.168.25.1) inet proto tcp from any to any
port = 75 flags S/SA keep state
block drop in log quick on dc0 from blackhole to any
so your filter rules are numbered 0, 1, 2
zool# pfctl -sn
No ALTQ support in kernel
ALTQ related functions disabled
no rdr on lo0 all
no rdr on lo1 all
no rdr inet proto tcp from spamd-white-local to any port = smtp
no rdr inet proto tcp from spamd-white to any port = smtp
rdr pass log inet proto tcp from any to any port = smtp - 127.0.0.1 port 8025
your rdr rules are numbered 0, .. 4, but you only have log in rule 4.
So, when you see matches in your pflog, rule 0 .. 2 are filter rules and
rule 4 is rdr rule, which you can also see from the action logged, pass,
block or rdr. That seems to explain why you have no matches for rule 3.
So, to solve your problem, separate first NAT and filtering. Things becomes so
much more clear.
Repeated: Get rid of that rdr pass make an rdr rule and a pass rule.
Yes, it's the rule recommended by the spamd man page, but if you want to
see and understand what's going on, that kind of rules can really make
things obscure.
BR, Erik
--
Erik Nørgaard
Ph: +34.666334818/+34.915211157 http://www.locolomo.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
automating network configuration
Hello, I am looking for a way to automate the configuration of my network depending on its topology (don't know if it's the good word) : I would like to check the wired interface to see if a cable is plugged in (by looking at carrier status), if so, bring up the wired interface, if no bring up the wireless interface. Is there a way to do this? I was wondering if it is possible to do so by scripting rc.conf? Thanks in advance for any advice, Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: sysinstall and the Right Terminal
On Sat, Jan 23, 2010 at 12:48:32PM -0700, Dale Scott wrote: Using Ubuntu 9.10 (Karmic Koala) and GNOME Terminal 2.28.1, $TERM is Xterm. $ echo $TERM Xterm $ The only thing I'd change about the mapping is that I'd rather flash the screen instead of ringing the bell. Put: XTerm*visualBell:true in ~/.Xdefaults and that should fix it. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader, MBR and the boot process
2010/1/22, Dan Naumov dan.nau...@gmail.com: Putting the swap into it's own slice and then putting FreeBSD into it's own slice worked fine. So why the hell can't they both coexist in 1 slice if the swap comes first? Similar problem here: I have a full-zfs system in a bsd slice, but I have the zfs-freebsd partition before the swap one. The problem is that the system doesn't seem to detect the swap partition partition (I see swapon: /dev/ada0s1b: No such file or directory during boot) % bsdlabel /dev/ada0s1 # /dev/ada0s1: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 530432000 ZFS b: 9883342 53043200 swap c: 629265420unused0 0 # raw part, don't edit but to see ada0s1b in /dev/ I have to reload geom_bsd module (loading it at boot time doesn't work). Even though (but this seems to be another problem): % sudo swapon /dev/ada0s1b swapon: /dev/ada0s1b: Operation not permitted Regards, Romain ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: automating network configuration
Romain Garbage wrote: Hello, I am looking for a way to automate the configuration of my network depending on its topology (don't know if it's the good word) : I would like to check the wired interface to see if a cable is plugged in (by looking at carrier status), if so, bring up the wired interface, if no bring up the wireless interface. Is there a way to do this? I was wondering if it is possible to do so by scripting rc.conf? Normally you really don't have to think, just enable both, assuming you use dhcp. Wired configuration with dhcp will fail if there is no cable, wireless will fail if there is no signal. You usually won't experience problems even if both are configured. BR, Erik -- Erik Nørgaard Ph: +34.666334818/+34.915211157 http://www.locolomo.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
The New Era in Aesthetic Dentistry
[http://www.cappmea.com/cadcam4/] The Tooth Preparation for CAD CAM Technology Dr. Nadim Aboujaoude Speaker at the 4th CAD/CAM Computerized Dentistry International Conference. The development of the computer aided technology in design and manufacturing made it possible to have the infrastructures for crown and bridges made bypassing the craftsmanship of the laboratory technicians. But this revolutionary input in our daily dental work implies some adaptations and modifications of the tooth preparations to adapt to technical possibilities and limitations. In this presentation we will discuss: The tooth preparation for CAD CAM technology The appropriate design of the preparation The limitations of the cutting machines. Meet Dr. Nadim Aboujaoude and learn about Tooth Preparation for CAD CAM Technology at the [http://www.cappmea.com/cadcam4] 4th CAD/CAM Computerized Dentistry Internationa Conference REGISTER TODAY! 00971 50 2793711 or [http://www.cappmea.com/cadcam4/pages/registration.php] ONLINE Promotion up to February 15, 2010 [http://www.cappmea.com/cadcam4/pages/callforpapers.php] [http://www.cappmea.com/cadcam4/index.htm] [http://www.cappmea.com/cadcam4/pages/orgcom.htm] [http://www.cappmea.com/cadcam4/pages/program.htm] [http://www.cappmea.com/cadcam4/pages/sponsorship.htm] [http://www.cappmea.com/cadcam4/pages/statistics.htm] [http://www.cappmea.com/cadcam4/pages/press.htm] [http://www.cappmea.com/cadcam4/pages/image_slideshow-5.html] [http://www.cappmea.com/cadcam4/pages/venue.htm] [http://www.cappmea.com/cadcam4/pages/accommodation.htm] [http://www.cappmea.com/cadcam4/pages/contact.php] ORGANIZERS SOCIAL NETWORKS [http://www.facebook.com/pages/Center-for-Advanced-Professional-Practices/133952242941] [http://twitter.com/cappmea] VENUE The Address Dubai Marina Contact CAPP: Hotline: +971 50 2793711 | Tel: +971 4 3616174 | Fax: +971 4 3686883 Email: [mailto:i...@cappmea.com] i...@cappmea.com | Web: [http://www.cappmea.com/cadcam4] www.cappmea.com/cadcam4 This message was sent by: CAPP, Kv, Bldg.9, Off.8, Dubai, none 502221, United Arab Emirates Email Marketing by iContact: http://freetrial.icontact.com Manage your subscription: http://app.icontact.com/icp/mmail-mprofile.pl?r=46571418l=22740s=LOEFm=351799c=517422 Forward to a friend: http://app.icontact.com/icp/sub/forward?m=351799s=46571418c=LOEFcid=517422 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Migration planning - old system to new
On Sat, Jan 23, 2010 at 11:35:20PM -0800, Doug Hardie wrote:
On 23 January 2010, at 22:42, John wrote:
On Sun, Jan 24, 2010 at 10:55:14AM +0800, Erich Dollansky wrote:
Hi,
On 24 January 2010 am 01:08:27 John wrote:
doing this on a new machine! And I don't need any migration
storage, because, well, gosh - it's tcp, people! ;) I just
did the first transfer of home, and it went swell:
how did you handle the strange group IDs?
Have not done that yet. My current best plan (which I'm not really
crazy about, but haven't come up with anything better) is to do
121 find /home -uid ... -exec chown {} + and 37
find /home -gid ... -exec chgrp {} + commands. This is also called
Let's modify every inode in the filesystem. Twice. Oh, well, the
ctimes are blown up by the migration anyway (as they really should be).
I have to be careful, if there are any IDs that are used on both
systems, but with different associations, to do the change in
the right order (sigh). I could try to get really fancy and just
find the distinct combinations of uid:gid and do only one
chown uid:gid for each file, but, getting it done will be more
important than being pretty at some point.
You might check out tar. At one time it had the option to use user and group
names and not ids. Hence the ids could change between the 2 systems. It
seems like it was on FreeBSD 3 or 4 that I last did that.
I just tried it with FreeBSD 7.2 creating a tar file. Digging through the
file it shows the ascii names for owner and group - not uid/gid. I un-tar'd
it on a Mac and sure enough it used the names and the uids are quite
different for the two systems.
Well, that would just serve me right after dissing tar in favor of
dump/restore earlier in this thread, now wouldn't it? I think you
can preserve the mtimes, too, if I recall correctly. The reason
that I don't want to do this, though, is that I don't believe
there's anyway to preserve the atime on either system. The last
access time of every file in the file system would be when I did
the migration (because tar is reading the files through the
filesystem, rather than reading the file system structure on the
disk, like dump does), rather than when they were really last used.
--
John Lind
j...@starfire.mn.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader, MBR and the boot process
On Fri, Jan 22, 2010 at 07:02:53AM +0200, Dan Naumov wrote:
On Fri, Jan 22, 2010 at 6:49 AM, Dan Naumov dan.nau...@gmail.com wrote:
On Fri, Jan 22, 2010 at 6:12 AM, Thomas K. f...@gothschlampen.com wrote:
On Fri, Jan 22, 2010 at 05:57:23AM +0200, Dan Naumov wrote:
Hi,
I recently found a nifty FreeBSD ZFS root installation script and
been reworking it a bit to suit my needs better, including changing it
from GPT to MBR partitioning. However, I was stumped, even though I
had done everything right (or so I thought), the system would get
stuck at Loader and refuse to go anywhere. After trying over a dozen
probably this line is the cause:
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s1a skip=1 seek=1024
Unless by swap first you meant the on-disk location, and not the
partition letter. If swap is partition a, you're writing the loader
into swapspace.
Regards,
Thomas
At first you made me feel silly, but then I decided to double-check, I
uncommented the swap line in the partitioning part again, ensured I
was writing the bootloader to ${TARGETDISK}s1b and ran the script.
Same problem, hangs at loader. Again, if I comment out the swap,
giving the entire slice to ZFS and then write the bootloader to
${TARGETDISK}s1a, run the script, everything works.
I have also just tested creating 2 slices, like this:
gpart create -s mbr ${TARGETDISK}
gpart add -s 3G -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s1
gpart add -t freebsd-swap ${TARGETDISK}s1
gpart add -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s2
gpart add -t freebsd-zfs ${TARGETDISK}s2
gpart set -a active -i 2 ${TARGETDISK}
gpart bootcode -b /mnt2/boot/boot0 ${TARGETDISK}
and later:
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s2 count=1
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s2a skip=1 seek=1024
Putting the swap into it's own slice and then putting FreeBSD into
it's own slice worked fine. So why the hell can't they both coexist in
1 slice if the swap comes first?
I know what the answer to this USED to be, but I don't know if it is
still true (obviously, I think so, I or wouldn't waste your time).
The filesystem code is all carefully written to avoid the very
first few sector of the partition. That's because the partition
table is there for the first filesystem of the slice (or disk).
That's a tiny amout of space wasted, because it's also skipped on
all the other filesystems even though there's not actually anything
there, but it was a small inefficency, even in the 70's.
Swap does not behave that way. SWAP will begin right at the slice
boundry, with 0 offset. As long as it's not the first partition, no
harm, no foul. If it IS the first partition, you just nuked your partition
table. As long as SWAP owns the slice, again, no harm, no foul, but
if there were filesystems BEHIND it, you just lost 'em.
That's the way it always used to be, and I think it still is. SWAP can
only be first if it is the ONLY thing using that slice (disk), otherwise,
you need a filesystem first to protect the partition table.
--
John Lind
j...@starfire.mn.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader, MBR and the boot process
On Sun, Jan 24, 2010 at 5:29 PM, John j...@starfire.mn.org wrote:
On Fri, Jan 22, 2010 at 07:02:53AM +0200, Dan Naumov wrote:
On Fri, Jan 22, 2010 at 6:49 AM, Dan Naumov dan.nau...@gmail.com wrote:
On Fri, Jan 22, 2010 at 6:12 AM, Thomas K. f...@gothschlampen.com wrote:
On Fri, Jan 22, 2010 at 05:57:23AM +0200, Dan Naumov wrote:
Hi,
I recently found a nifty FreeBSD ZFS root installation script and
been reworking it a bit to suit my needs better, including changing it
from GPT to MBR partitioning. However, I was stumped, even though I
had done everything right (or so I thought), the system would get
stuck at Loader and refuse to go anywhere. After trying over a dozen
probably this line is the cause:
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s1a skip=1 seek=1024
Unless by swap first you meant the on-disk location, and not the
partition letter. If swap is partition a, you're writing the loader
into swapspace.
Regards,
Thomas
At first you made me feel silly, but then I decided to double-check, I
uncommented the swap line in the partitioning part again, ensured I
was writing the bootloader to ${TARGETDISK}s1b and ran the script.
Same problem, hangs at loader. Again, if I comment out the swap,
giving the entire slice to ZFS and then write the bootloader to
${TARGETDISK}s1a, run the script, everything works.
I have also just tested creating 2 slices, like this:
gpart create -s mbr ${TARGETDISK}
gpart add -s 3G -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s1
gpart add -t freebsd-swap ${TARGETDISK}s1
gpart add -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s2
gpart add -t freebsd-zfs ${TARGETDISK}s2
gpart set -a active -i 2 ${TARGETDISK}
gpart bootcode -b /mnt2/boot/boot0 ${TARGETDISK}
and later:
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s2 count=1
dd if=/mnt2/boot/zfsboot of=/dev/${TARGETDISK}s2a skip=1 seek=1024
Putting the swap into it's own slice and then putting FreeBSD into
it's own slice worked fine. So why the hell can't they both coexist in
1 slice if the swap comes first?
I know what the answer to this USED to be, but I don't know if it is
still true (obviously, I think so, I or wouldn't waste your time).
The filesystem code is all carefully written to avoid the very
first few sector of the partition. That's because the partition
table is there for the first filesystem of the slice (or disk).
That's a tiny amout of space wasted, because it's also skipped on
all the other filesystems even though there's not actually anything
there, but it was a small inefficency, even in the 70's.
Swap does not behave that way. SWAP will begin right at the slice
boundry, with 0 offset. As long as it's not the first partition, no
harm, no foul. If it IS the first partition, you just nuked your partition
table. As long as SWAP owns the slice, again, no harm, no foul, but
if there were filesystems BEHIND it, you just lost 'em.
That's the way it always used to be, and I think it still is. SWAP can
only be first if it is the ONLY thing using that slice (disk), otherwise,
you need a filesystem first to protect the partition table.
--
John Lind
j...@starfire.mn.org
This explanation does sound logical, but holy crap, if this is the
case, you'd think there would be bells, whistles and huge red label
warnings in EVERY FreeBSD installation / partitioning guide out there
warning people to not put swap first (unless given a dedicated slice)
under any circumstances. The warnings were nowhere to be seen and lots
of pointy hair first greyed and were then lost during the process of
me trying to figure out why my system would install but wouldn't boot.
- Sincerely,
Dan Naumov
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Mouse selection overeagerness
Mouse selection in both xfce4's Terminal and the FreeBSD console is a bit touchy. Select a block, click in another window to paste, and... it's now highlighted a block in the target window. Or maybe a whole line. Mouse speed and click-to-focus are fine the way they are, it'd just be nice if there was a way to reduce this selection oversensitivity. Is there a place to increase the threshold that defines when a selection is taking place? Somewhere between moused and syscons, maybe, but a cursory [hah] look at their man pages didn't show an adjustment. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
Note: Since my issue is slow performance right off the bat and not performance degradation over time, I decided to start a separate discussion. After installing a fresh pure ZFS 8.0 system and building all my ports, I decided to do some benchmarking. At this point, about a dozen of ports has been built installed and the system has been up for about 11 hours, No heavy background services have been running, only SSHD and NTPD: == bonnie -s 8192: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 8192 23821 61.7 22311 19.2 13928 13.7 25029 49.6 44806 17.2 135.0 3.1 During the process, TOP looks like this: last pid: 83554; load averages: 0.31, 0.31, 0.37 up 0+10:59:01 17:24:19 33 processes: 2 running, 31 sleeping CPU: 0.1% user, 0.0% nice, 14.1% system, 0.7% interrupt, 85.2% idle Mem: 45M Active, 4188K Inact, 568M Wired, 144K Cache, 1345M Free Swap: 3072M Total, 3072M Free Oh wow, that looks low, alright, lets run it again, just to be sure: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 8192 18235 46.7 23137 19.9 13927 13.6 24818 49.3 44919 17.3 134.3 2.1 OK, let's reboot the machine and see what kind of numbers we get on a fresh boot: === ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 8192 21041 53.5 22644 19.4 13724 12.8 25321 48.5 43110 14.0 143.2 3.3 Nope, no help from the reboot, still very low speed. Here is my pool: === zpool status pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror ONLINE 0 0 0 ad10s1a ONLINE 0 0 0 ad8s1a ONLINE 0 0 0 === diskinfo -c -t /dev/ad10 /dev/ad10 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. WD-WCAVY0301430 # Disk ident. I/O command overhead: time to read 10MB block 0.164315 sec =0.008 msec/sector time to read 20480 sectors 3.030396 sec =0.148 msec/sector calculated command overhead =0.140 msec/sector Seek times: Full stroke: 250 iter in 7.309334 sec = 29.237 msec Half stroke: 250 iter in 5.156117 sec = 20.624 msec Quarter stroke: 500 iter in 8.147588 sec = 16.295 msec Short forward:400 iter in 2.544309 sec =6.361 msec Short backward: 400 iter in 2.007679 sec =5.019 msec Seq outer: 2048 iter in 0.392994 sec =0.192 msec Seq inner: 2048 iter in 0.332582 sec =0.162 msec Transfer rates: outside: 102400 kbytes in 1.576734 sec =64944 kbytes/sec middle:102400 kbytes in 1.381803 sec =74106 kbytes/sec inside:102400 kbytes in 2.145432 sec =47729 kbytes/sec === diskinfo -c -t /dev/ad8 /dev/ad8 512 # sectorsize 2000398934016 # mediasize in bytes (1.8T) 3907029168 # mediasize in sectors 3876021 # Cylinders according to firmware. 16 # Heads according to firmware. 63 # Sectors according to firmware. WD-WCAVY1611513 # Disk ident. I/O command overhead: time to read 10MB block 0.176820 sec =0.009 msec/sector time to read 20480 sectors 2.966564 sec =0.145 msec/sector calculated command overhead =0.136 msec/sector Seek times: Full stroke: 250 iter in 7.993339 sec = 31.973 msec Half stroke: 250 iter in 5.944923 sec = 23.780 msec Quarter stroke: 500 iter in 9.744406 sec = 19.489 msec Short forward:400 iter in 2.511171 sec =
PCIe audio cards: what is tob be preferred with FreeBSD 8.0/9-CURRENT?
Well, At this very moment I utilise a M-Audio 5.1 PCI-audio board with which I'm really satisfied. My next box doesn't have PCI slots at all (ASUS P6T6-WS Revolution) and due to the fact I'm using Windows 7 sometimes for recreational gaming, I'd like to have a moderate expensive audio board with the workstation which is supported by FreeBSD 8/9. In the past - means two or three ywars ago, I had problems with Soundblaster PCIe boards, so I was recommended avoiding those and choosing the more elabotrated M-Audio cards for the PCI bus. At this moment, I look for the Soundblaster X-Fi range of PCIe cards, but I'm not sure whether they are supported by FreeBSd 8/9. Any suggestions? Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Sun, Jan 24, 2010 at 7:05 PM, Jason Edwards sub.m...@gmail.com wrote: Hi Dan, I read on FreeBSD mailinglist you had some performance issues with ZFS. Perhaps i can help you with that. You seem to be running a single mirror, which means you won't have any speed benefit regarding writes, and usually RAID1 implementations offer little to no acceleration to read requests also; some even just read from the master disk and don't touch the 'slave' mirrored disk unless when writing. ZFS is alot more modern however, although i did not test performance of its mirror implementation. But, benchmarking I/O can be tricky: 1) you use bonnie, but bonnie's tests are performed without a 'cooldown' period between the tests; meaning that when test 2 starts, data from test 1 is still being processed. For single disks and simple I/O this is not so bad, but for large write-back buffers and more complex I/O buffering, this may be inappropriate. I had patched bonnie some time in the past, but if you just want a MB/s number you can use DD for that. 2) The diskinfo tiny benchmark is single queue only i assume, meaning that it would not scale well or at all on RAID-arrays. Actual filesystems on RAID-arrays use multiple-queue; meaning it would not read one sector at a time, but read 8 blocks (of 16KiB) ahead; this is called read-ahead and for traditional UFS filesystems its controlled by the sysctl vfs.read_max variable. ZFS works differently though, but you still need a real benchmark. 3) You need low-latency hardware; in particular, no PCI controller should be used. Only PCI-express based controllers or chipset-integrated Serial ATA cotrollers have proper performance. PCI can hurt performance very badly, and has high interrupt CPU usage. Generally you should avoid PCI. PCI-express is fine though, its a completely different interface that is in many ways the opposite of what PCI was. 4) Testing actual realistic I/O performance (in IOps) is very difficult. But testing sequential performance should be alot easier. You may try using dd for this. For example, you can use dd on raw devices: dd if=/dev/ad4 of=/dev/null bs=1M count=1000 I will explain each parameter: if=/dev/ad4 is the input file, the read source of=/dev/null is the output file, the write destination. /dev/null means it just goes no-where; so this is a read-only benchmark bs=1M is the blocksize, howmuch data to transfer per time. default is 512 or the sector size; but that's very slow. A value between 64KiB and 1024KiB is appropriate. bs=1M will select 1MiB or 1024KiB. count=1000 means transfer 1000 pieces, and with bs=1M that means 1000 * 1MiB = 1000MiB. This example was raw reading sequentially from the start of the device /dev/ad4. If you want to test RAIDs, you need to work at the filesystem level. You can use dd for that too: dd if=/dev/zero of=/path/to/ZFS/mount/zerofile.000 bs=1M count=2000 This command will read from /dev/zero (all zeroes) and write to a file on ZFS-mounted filesystem, it will create the file zerofile.000 and write 2000MiB of zeroes to that file. So this command tests write-performance of the ZFS-mounted filesystem. To test read performance, you need to clear caches first by unmounting that filesystem and re-mounting it again. This would free up memory containing parts of the filesystem as cached (reported in top as Inact(ive) instead of Free). Please do make sure you double-check a dd command before running it, and run as normal user instead of root. A wrong dd command may write to the wrong destination and do things you don't want. The only real thing you need to check is the write destination (of=). That's where dd is going to write to, so make sure its the target you intended. A common mistake made by myself was to write dd of=... if=... (starting with of instead of if) and thus actually doing something the other way around than what i was meant to do. This can be disastrous if you work with live data, so be careful! ;-) Hope any of this was helpful. During the dd benchmark, you can of course open a second SSH terminal and start gstat to see the devices current I/O stats. Kind regards, Jason Hi and thanks for your tips, I appreciate it :) [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test1 bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 36.206372 secs (29656156 bytes/sec) [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test2 bs=1M count=4096 4096+0 records in 4096+0 records out 4294967296 bytes transferred in 143.878615 secs (29851325 bytes/sec) This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Sun, Jan 24, 2010 at 7:42 PM, Dan Naumov dan.nau...@gmail.com wrote: On Sun, Jan 24, 2010 at 7:05 PM, Jason Edwards sub.m...@gmail.com wrote: Hi Dan, I read on FreeBSD mailinglist you had some performance issues with ZFS. Perhaps i can help you with that. You seem to be running a single mirror, which means you won't have any speed benefit regarding writes, and usually RAID1 implementations offer little to no acceleration to read requests also; some even just read from the master disk and don't touch the 'slave' mirrored disk unless when writing. ZFS is alot more modern however, although i did not test performance of its mirror implementation. But, benchmarking I/O can be tricky: 1) you use bonnie, but bonnie's tests are performed without a 'cooldown' period between the tests; meaning that when test 2 starts, data from test 1 is still being processed. For single disks and simple I/O this is not so bad, but for large write-back buffers and more complex I/O buffering, this may be inappropriate. I had patched bonnie some time in the past, but if you just want a MB/s number you can use DD for that. 2) The diskinfo tiny benchmark is single queue only i assume, meaning that it would not scale well or at all on RAID-arrays. Actual filesystems on RAID-arrays use multiple-queue; meaning it would not read one sector at a time, but read 8 blocks (of 16KiB) ahead; this is called read-ahead and for traditional UFS filesystems its controlled by the sysctl vfs.read_max variable. ZFS works differently though, but you still need a real benchmark. 3) You need low-latency hardware; in particular, no PCI controller should be used. Only PCI-express based controllers or chipset-integrated Serial ATA cotrollers have proper performance. PCI can hurt performance very badly, and has high interrupt CPU usage. Generally you should avoid PCI. PCI-express is fine though, its a completely different interface that is in many ways the opposite of what PCI was. 4) Testing actual realistic I/O performance (in IOps) is very difficult. But testing sequential performance should be alot easier. You may try using dd for this. For example, you can use dd on raw devices: dd if=/dev/ad4 of=/dev/null bs=1M count=1000 I will explain each parameter: if=/dev/ad4 is the input file, the read source of=/dev/null is the output file, the write destination. /dev/null means it just goes no-where; so this is a read-only benchmark bs=1M is the blocksize, howmuch data to transfer per time. default is 512 or the sector size; but that's very slow. A value between 64KiB and 1024KiB is appropriate. bs=1M will select 1MiB or 1024KiB. count=1000 means transfer 1000 pieces, and with bs=1M that means 1000 * 1MiB = 1000MiB. This example was raw reading sequentially from the start of the device /dev/ad4. If you want to test RAIDs, you need to work at the filesystem level. You can use dd for that too: dd if=/dev/zero of=/path/to/ZFS/mount/zerofile.000 bs=1M count=2000 This command will read from /dev/zero (all zeroes) and write to a file on ZFS-mounted filesystem, it will create the file zerofile.000 and write 2000MiB of zeroes to that file. So this command tests write-performance of the ZFS-mounted filesystem. To test read performance, you need to clear caches first by unmounting that filesystem and re-mounting it again. This would free up memory containing parts of the filesystem as cached (reported in top as Inact(ive) instead of Free). Please do make sure you double-check a dd command before running it, and run as normal user instead of root. A wrong dd command may write to the wrong destination and do things you don't want. The only real thing you need to check is the write destination (of=). That's where dd is going to write to, so make sure its the target you intended. A common mistake made by myself was to write dd of=... if=... (starting with of instead of if) and thus actually doing something the other way around than what i was meant to do. This can be disastrous if you work with live data, so be careful! ;-) Hope any of this was helpful. During the dd benchmark, you can of course open a second SSH terminal and start gstat to see the devices current I/O stats. Kind regards, Jason Hi and thanks for your tips, I appreciate it :) [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test1 bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 36.206372 secs (29656156 bytes/sec) [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test2 bs=1M count=4096 4096+0 records in 4096+0 records out 4294967296 bytes transferred in 143.878615 secs (29851325 bytes/sec) This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Sun, Jan 24, 2010 at 8:12 PM, Bob Friesenhahn bfrie...@simple.dallas.tx.us wrote: On Sun, 24 Jan 2010, Dan Naumov wrote: This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached to the same controller. Only difference was that in Windows the disks weren't in a mirror configuration but were tested individually. I do understand that a mirror setup offers roughly the same write speed as individual disk, while the read speed usually varies from equal to individual disk speed to nearly the throughput of both disks combined depending on the implementation, but there is no obvious reason I am seeing why my setup offers both read and write speeds roughly 1/3 to 1/2 of what the individual disks are capable of. Dmesg shows: There is a mistatement in the above in that a mirror setup offers roughly the same write speed as individual disk. It is possible for a mirror setup to offer a similar write speed to an individual disk, but it is also quite possible to get 1/2 (or even 1/3) the speed. ZFS writes to a mirror pair requires two independent writes. If these writes go down independent I/O paths, then there is hardly any overhead from the 2nd write. If the writes go through a bandwidth-limited shared path then they will contend for that bandwidth and you will see much less write performance. As a simple test, you can temporarily remove the mirror device from the pool and see if the write performance dramatically improves. Before doing that, it is useful to see the output of 'iostat -x 30' while under heavy write load to see if one device shows a much higher svc_t value than the other. Ow, ow, WHOA: atombsd# zpool offline tank ad8s1a [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test3 bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 16.826016 secs (63814382 bytes/sec) Offlining one half of the mirror bumps DD write speed from 28mb/s to 64mb/s! Let's see how Bonnie results change: Mirror with both parts attached: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 8192 18235 46.7 23137 19.9 13927 13.6 24818 49.3 44919 17.3 134.3 2.1 Mirror with 1 half offline: ---Sequential Output ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 1024 22888 58.0 41832 35.1 22764 22.0 26775 52.3 54233 18.3 166.0 1.6 Ok, the Bonnie results have improved, but only very little. - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Thunderbird language should be Swedish but it's not!
Leslie Jensen said the following on 2010-01-23 15:54: When I install Thunderbird3 thunderbird-3.0.1 thunderbird-dictionaries-20060220_4 thunderbird3-i18n-3.0.1 It does not adapt to what I have in /etc/make.conf # Firefox-i18n FIREFOX_I18N=sv-SE # Thunderbird-i18n THUNDERBIRD_I18N=sv-SE You need thunderbird3-i18n not thunderbird-i18n. Firefox instals xpi-quick-locale-switcher-1.7 set to Swedish. It can be disabled and Firefox keeps the swedish setting. Any suggestions on how to get Thunderbird to display Swedish? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Sun, Jan 24, 2010 at 8:34 PM, Jason Edwards sub.m...@gmail.com wrote: ZFS writes to a mirror pair requires two independent writes. If these writes go down independent I/O paths, then there is hardly any overhead from the 2nd write. If the writes go through a bandwidth-limited shared path then they will contend for that bandwidth and you will see much less write performance. What he said may confirm my suspicion on PCI. So if you could try the same with real Serial ATA via chipset or PCI-e controller you can confirm this story. I would be very interested. :P Kind regards, Jason This wouldn't explain why ZFS mirror on 2 disks directly, on the exact same controller (with the OS running off a separate disks) results in expected performance, while having the OS run off/on a ZFS mirror running on top of MBR-partitioned disks, on the same controller, results in very low speed. - Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Loader, MBR and the boot process
In message cf9b1ee01001240759j2476cf3es2babd8b32a90f...@mail.gmail.com, Dan N
aumov writes:
On Sun, Jan 24, 2010 at 5:29 PM, John j...@starfire.mn.org wrote:
On Fri, Jan 22, 2010 at 07:02:53AM +0200, Dan Naumov wrote:
On Fri, Jan 22, 2010 at 6:49 AM, Dan Naumov dan.nau...@gmail.com wrote=
:
On Fri, Jan 22, 2010 at 6:12 AM, Thomas K. f...@gothschlampen.com wro=
te:
On Fri, Jan 22, 2010 at 05:57:23AM +0200, Dan Naumov wrote:
Hi,
I recently found a nifty FreeBSD ZFS root installation script and
been reworking it a bit to suit my needs better, including changing =
it
from GPT to MBR partitioning. However, I was stumped, even though I
had done everything right (or so I thought), the system would get
stuck at Loader and refuse to go anywhere. After trying over a dozen
probably this line is the cause:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s1a skip=3D1 seek=
=3D1024
Unless by swap first you meant the on-disk location, and not the
partition letter. If swap is partition a, you're writing the loader
into swapspace.
Regards,
Thomas
At first you made me feel silly, but then I decided to double-check, I
uncommented the swap line in the partitioning part again, ensured I
was writing the bootloader to ${TARGETDISK}s1b and ran the script.
Same problem, hangs at loader. Again, if I comment out the swap,
giving the entire slice to ZFS and then write the bootloader to
${TARGETDISK}s1a, run the script, everything works.
I have also just tested creating 2 slices, like this:
gpart create -s mbr ${TARGETDISK}
gpart add -s 3G -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s1
gpart add -t freebsd-swap ${TARGETDISK}s1
gpart add -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s2
gpart add -t freebsd-zfs ${TARGETDISK}s2
gpart set -a active -i 2 ${TARGETDISK}
gpart bootcode -b /mnt2/boot/boot0 ${TARGETDISK}
and later:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2 count=3D1
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2a skip=3D1 seek=3D=
1024
Putting the swap into it's own slice and then putting FreeBSD into
it's own slice worked fine. So why the hell can't they both coexist in
1 slice if the swap comes first?
I know what the answer to this USED to be, but I don't know if it is
still true (obviously, I think so, I or wouldn't waste your time).
The filesystem code is all carefully written to avoid the very
first few sector of the partition. =A0That's because the partition
table is there for the first filesystem of the slice (or disk).
That's a tiny amout of space wasted, because it's also skipped on
all the other filesystems even though there's not actually anything
there, but it was a small inefficency, even in the 70's.
Swap does not behave that way. =A0SWAP will begin right at the slice
boundry, with 0 offset. =A0As long as it's not the first partition, no
harm, no foul. =A0If it IS the first partition, you just nuked your parti=
tion
table. =A0As long as SWAP owns the slice, again, no harm, no foul, but
if there were filesystems BEHIND it, you just lost 'em.
That's the way it always used to be, and I think it still is. =A0SWAP can
only be first if it is the ONLY thing using that slice (disk), otherwise,
you need a filesystem first to protect the partition table.
--
John Lind
j...@starfire.mn.org
This explanation does sound logical, but holy crap, if this is the
case, you'd think there would be bells, whistles and huge red label
warnings in EVERY FreeBSD installation / partitioning guide out there
warning people to not put swap first (unless given a dedicated slice)
under any circumstances. The warnings were nowhere to be seen and lots
of pointy hair first greyed and were then lost during the process of
me trying to figure out why my system would install but wouldn't boot.
From man bsdlabel.
offset The offset of the start of the partition from the beginning of
the drive in sectors, or * to have bsdlabel calculate the correct
offset to use (the end of the previous partition plus one, ignor-
ing partition `c'. For partition `c', * will be interpreted as
an offset of 0. The first partition should start at offset 16,
because the first 16 sectors are reserved for metadata.
- Sincerely,
Dan Naumov
___
freebsd-sta...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send
Re: PCIe audio cards: what is tob be preferred with FreeBSD 8.0/9-CURRENT?
O. Hartmann wrote: Well, At this very moment I utilise a M-Audio 5.1 PCI-audio board with which I'm really satisfied. My next box doesn't have PCI slots at all (ASUS P6T6-WS Revolution) and due to the fact I'm using Windows 7 sometimes for recreational gaming, I'd like to have a moderate expensive audio board with the workstation which is supported by FreeBSD 8/9. In the past - means two or three ywars ago, I had problems with Soundblaster PCIe boards, so I was recommended avoiding those and choosing the more elabotrated M-Audio cards for the PCI bus. At this moment, I look for the Soundblaster X-Fi range of PCIe cards, but I'm not sure whether they are supported by FreeBSd 8/9. Any suggestions? I would first test on-board HDA codec, placed on that motherboard. They are free and usually work with FreeBSD just out of the box, using snd_hda driver. Now snd_hda and snd_uaudio are only two drivers supporting multichannel playback. If you need analog connection, snd_hda can usually provide multichannel 24bit/192kHz playback. But also it supports digital SPDIF I/O, including AC3/DTS pass-through. Together with SPDIF-connected external audio receiver, even simple HDA codec could become very interesting high-quality choice. Personally I am completely fulfilled with combination of simple Realtek HDA codec, digitally connected via SPDIF to Marantz SR4001 receiver, loaded to the full-sized Eltax 7.1 speaker set. Previously I was using Creative Audigy2 ZS, but now it just collecting dust in my table. It works, but I really don't need it. PS: If you want to look cool, you may use optical SPDIF connection. :) -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
Dan Naumov wrote: This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached to the same controller. Only difference was that in Windows the disks weren't in a mirror configuration but were tested individually. I do understand that a mirror setup offers roughly the same write speed as individual disk, while the read speed usually varies from equal to individual disk speed to nearly the throughput of both disks combined depending on the implementation, but there is no obvious reason I am seeing why my setup offers both read and write speeds roughly 1/3 to 1/2 of what the individual disks are capable of. Dmesg shows: atapci0: SiI 3124 SATA300 controller port 0x1000-0x100f mem 0x90108000-0x9010807f,0x9010-0x90107fff irq 21 at device 0.0 on pci4 ad8: 1907729MB WDC WD20EADS-32R6B0 01.00A01 at ata4-master SATA300 ad10: 1907729MB WDC WD20EADS-00R6B0 01.00A01 at ata5-master SATA300 8.0-RELEASE, and especially 8-STABLE provide alternative, much more functional driver for this controller, named siis(4). If your SiI3124 card installed into proper bus (PCI-X or PCIe x4/x8), it can be really fast (up to 1GB/s was measured). -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Determine usb-storage capacity
Greetings! A short question: is there a way to determine usb-storage and md-device capacity( for further fdisk and bsdlabel applying ) from within a sh script, in which device's /dev file-name is present? Something similar to atacontrol cap | grep lba... . (c) Lame English Inc. noams...@home ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Determine usb-storage capacity
In the last episode (Jan 25), Ivan Borodin said: Greetings! A short question: is there a way to determine usb-storage and md-device capacity( for further fdisk and bsdlabel applying ) from within a sh script, in which device's /dev file-name is present? Something similar to atacontrol cap | grep lba... Works for all disk devices: diskinfo /dev/da0 Works for devices attached via CAM: camcontrol readcap da0 See the respective manpages for more info. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Unique process id (not pid) and accounting daemon
Hello. I am trying to create an accounting daemon that would be more precise than usual BSD system accounting. It should read the whole process tree from time to time (say, every 10 seconds) and log changes in usage of CPU, I/O operations and memory per process. After daemon notices process exit, it should read /var/account/acct to get a last portion of accounting data and make a last entry for the process. Also daemon should read /var/account/acct to find information about processes that had been running between taking process tree snapshots. There is a problem: it is not always possible to link a process in a process tree against matching process in an accounting file. Only command name, user/group id and start time will match, but: * start time may change (i. e. after ntpdate); * command name saved in /var/account/acct is 15 characters max (AC_COMM_LEN in sys/sys/acct.h), while command name in the process tree is 19 characters max (MAXCOMLEN in sys/sys/param.h). To ensure that process in the process tree and process in the accounting file are the same, I want to add unique process identifier (uint64_t) to 'proc' struct in sys/sys/proc.h and increment it for every process fork. I see it is possible to do this just before sx_sunlock() in fork1() in sys/kern/kern_fork.c. I'll have to add saving of this identifier in kern_acct.c, of course. This way I will be extremely easy to remember a process in the process tree and find a matching one in the accounting file after it finishes. Am I looking in a right direction or should I try some other way? Thanks in advance. -- // cronfy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Sun, Jan 24, 2010 at 11:53 PM, Alexander Motin m...@freebsd.org wrote: Dan Naumov wrote: This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached to the same controller. Only difference was that in Windows the disks weren't in a mirror configuration but were tested individually. I do understand that a mirror setup offers roughly the same write speed as individual disk, while the read speed usually varies from equal to individual disk speed to nearly the throughput of both disks combined depending on the implementation, but there is no obvious reason I am seeing why my setup offers both read and write speeds roughly 1/3 to 1/2 of what the individual disks are capable of. Dmesg shows: atapci0: SiI 3124 SATA300 controller port 0x1000-0x100f mem 0x90108000-0x9010807f,0x9010-0x90107fff irq 21 at device 0.0 on pci4 ad8: 1907729MB WDC WD20EADS-32R6B0 01.00A01 at ata4-master SATA300 ad10: 1907729MB WDC WD20EADS-00R6B0 01.00A01 at ata5-master SATA300 8.0-RELEASE, and especially 8-STABLE provide alternative, much more functional driver for this controller, named siis(4). If your SiI3124 card installed into proper bus (PCI-X or PCIe x4/x8), it can be really fast (up to 1GB/s was measured). -- Alexander Motin Sadly, it seems that utilizing the new siis driver doesn't do much good: Before utilizing siis: iozone -s 4096M -r 512 -i0 -i1 random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 28796 287665161050695 After enabling siis in loader.conf (and ensuring the disks show up as ada): iozone -s 4096M -r 512 -i0 -i1 random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 28781 288974721450540 I've checked with the manufacturer and it seems that the Sil3124 in this NAS is indeed a PCI card. More info on the card in question is available at http://green-pcs.co.uk/2009/01/28/tranquil-bbs2-those-pci-cards/ I have the card described later on the page, the one with 4 SATA ports and no eSATA. Alright, so it being PCI is probably a bottleneck in some ways, but that still doesn't explain the performance THAT bad, considering that same hardware, same disks, same disk controller push over 65mb/s in both reads and writes in Win2008. And agian, I am pretty sure that I've had close to expected results when I was booting an UFS FreeBSD installation off an SSD (attached directly to SATA port on the motherboard) while running the same kinds of benchmarks with Bonnie and DD on a ZFS mirror made directly on top of 2 raw disks. - Sincerely, Dan Naumov ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
On Mon, Jan 25, 2010 at 2:14 AM, Dan Naumov dan.nau...@gmail.com wrote: On Sun, Jan 24, 2010 at 11:53 PM, Alexander Motin m...@freebsd.org wrote: Dan Naumov wrote: This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached to the same controller. Only difference was that in Windows the disks weren't in a mirror configuration but were tested individually. I do understand that a mirror setup offers roughly the same write speed as individual disk, while the read speed usually varies from equal to individual disk speed to nearly the throughput of both disks combined depending on the implementation, but there is no obvious reason I am seeing why my setup offers both read and write speeds roughly 1/3 to 1/2 of what the individual disks are capable of. Dmesg shows: atapci0: SiI 3124 SATA300 controller port 0x1000-0x100f mem 0x90108000-0x9010807f,0x9010-0x90107fff irq 21 at device 0.0 on pci4 ad8: 1907729MB WDC WD20EADS-32R6B0 01.00A01 at ata4-master SATA300 ad10: 1907729MB WDC WD20EADS-00R6B0 01.00A01 at ata5-master SATA300 8.0-RELEASE, and especially 8-STABLE provide alternative, much more functional driver for this controller, named siis(4). If your SiI3124 card installed into proper bus (PCI-X or PCIe x4/x8), it can be really fast (up to 1GB/s was measured). -- Alexander Motin Sadly, it seems that utilizing the new siis driver doesn't do much good: Before utilizing siis: iozone -s 4096M -r 512 -i0 -i1 random random bkwd record stride KB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 4194304 512 28796 28766 51610 50695 After enabling siis in loader.conf (and ensuring the disks show up as ada): iozone -s 4096M -r 512 -i0 -i1 random random bkwd record stride KB reclen write rewrite read reread read write read rewrite read fwrite frewrite fread freread 4194304 512 28781 28897 47214 50540 Just to add to the numbers above, exact same benchmark, on 1 disk (detached 2nd disk from the mirror) while using the siis driver: random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 57760 563716886774047 - Dan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Finding Drivers For winWiFi Card
On Sun, 24 Jan 2010 07:13:05 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I'll post here later on today, after I've burned the file to disc (no floppy drive on either computer). No possibility to transfer the file via wired network? Your RealTek NIC works out of the box. Or maybe use an USB stick? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Migration planning - old system to new
Hi,
On 24 January 2010 pm 14:42:11 John wrote:
On Sun, Jan 24, 2010 at 10:55:14AM +0800, Erich Dollansky wrote:
how did you handle the strange group IDs?
Have not done that yet. My current best plan (which I'm not
really crazy about, but haven't come up with anything better)
is to do 121 find /home -uid ... -exec chown {} + and 37
have you ever thought that it does not really matter as you have
control over the group file. You can leave your strange group IDs
but you must maintain your group file by hand. You might have to
check it after each new software installation but for the
operation for machine, it should not matter.
And, of course, there's the whole matter of migrating the
passwords...
This I never did.
It probably is, but I see so much of other servers running on
similar hardware with a certain other operating system that
have a reguluar 30-day scheduled reboot, it still delights me.
I just wanted to share my delight!
Is it a Tuesday?
Erich
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Migration planning - old system to new
Hi, On 24 January 2010 pm 15:35:20 Doug Hardie wrote: On 23 January 2010, at 22:42, John wrote: I just tried it with FreeBSD 7.2 creating a tar file. Digging through the file it shows the ascii names for owner and group - not uid/gid. I un-tar'd it on a Mac and sure enough it used the names and the uids are quite different for the two systems.___ what happens if you first create the user names on the target system and then open the archive? It would be then very easy to move files accross systems. I never have had to do this. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to troubleshoot a frozen boot sequence
I am not sure why, but here was my solution.
I determined through a lot of poking that the Master Boot Record of each
drive. Here is what I found out:
1. My backup drive (ad0) had the FreeBSD boot manager installed.
2. My main drive (twed0) had the FreeBSD MBR installed.
So, what is the problem? All I could figure is to install the boot manager
(called boot0cfg) onto my main drive. Silly, but it worked.
Why, I don't have a clue. I do, by the way, remember purposely using this
setup when I ran sysinstall to configure this machine. I felt that the ad0
drive needed a boot manager (just in case it was used someplace else) and the
main drive would not need a boot manager. But nothing ever indicated to me
that a standard MBR on twed0 would not work if ad0 was missing.
Here is my partition table from twed0:
# /dev/twed0
g c60801 h255 s63
p 1 0xa5 63 976768002
a 1
Notice there is just one partition and it is active. But it wouldn't boot
until I ran:
bootcfg -B twed0
which keeps the slice table the same.
Once I was done, the server will now boot with or without the ad0 drive. In
case of a backup drive failure, I had to also mess with fstab:
1. I had to add the noauto option, as someone suggested.
2. I had to disable all fsck passes (3 didn't work --0) or fsck failure will
boot single user.
My question is now, do I write a script to mount the drive (too late, I did)
during boot and then to run fsck also? I am not sure how fsck should be run,
but I assume it is kind of important.
My main challenge was determining when to mount the disk. Here is my solution
and my script so far that seems to work.
=
#!/bin/sh
# mounts my special drive
# TODO: Need to fsck it
# PROVIDE: mountbackup
# REQUIRE: mail
# KEYWORD: nojail
. /etc/rc.subr
name=mountbackup
start_cmd=mountbackup_start
stop_cmd=:
THIS=/disk250
HOSTNAME=`/bin/hostname`
mailto=r...@${hostname}
TOD=`/bin/date`
mountbackup_start()
{
local err
# Mount backup filesystems.
echo -n Mounting $THIS Backup filesystems
mount $THIS
err=$?
echo '.'
case ${err} in
0)
;;
*)
echo Mounting $THIS filesystems failed, \
but it's okay for now. Sending mail to $MAILTO
(echo Mounting $THIS filesystems failed on boot!
echo
echo Host: $HOST Date: $TOD | \
mail -s FAILURE to mount $THIS on $HOST $MAILTO
;;
esac
}
load_rc_config $name
run_rc_command $1
=
Billy Newsom wrote:
Nathan Vidican wrote:
To me, it sounds like you have two issues to deal with here:
#1 - booting off of the twed0 disk, what is your systems' BIOS currently
set to boot from, from the way you describe it's almost as if the system
is booting from ad0 - in which case yes, you will have to put a valid
boot config onto twed0
I feel that I have run across a common and old SCSI v IDE battle (The
FreeBSD Handbook still talks about it). Even though I make the drive
controller (the twe = 3Ware SATA controller) as my first boot drive in
BIOS (effectively 0x80 as I understand it), FreeBSD does not ever pay
attention to the BIOS's numerical order. (See my reason below*) It wants
to find stuff on ad0 and boot that drive if it exists.
My supposition is that since I had twe0 and ad0 running during my 7.2
install, that the correct drive partition and MBR stuff were applied to
get it to boot AS-IS, but...
When it is not as it is now, It freezes at the boot loader, attempting
to find ad0.
It is either
a. Finding ad0 in fstab and really wishing it was there
or
b. The boot strap code is physically on ad0 and not twed0 because the
Sysinstall process never wrote it there.
I think it is b. If b, the boot process may be:
Stage 1: BIOS picks twe0 to be the first drive to attempt a boot.
Stage 2: MBR (boot 0) -- located on twe0
Stage 3: boot1 -- located on twed0 (BTX Boot Loader?)
Stage 4: boot2 -- located on ad0 (FreeBSD/i386 bootstrap loader 1.1?)
Stage 5: Boot Loader -- shows menu on twed0s1a
Stage 6: Kernel boots up on twed0s1a
And so when I remove ad0 to simulate a backup drive failure, the stage 4
tries to run a missing bootstrap loader from twed0.
Stage 4: boot2 -- missing on twed0, system hangs.
I think this is happening because it is the BTX loader which may find
and concatenate the BIOS drives, getting confused, and switching the
boot to ad0 for just the one stage that finishes the bootstrap.
I think one solution is to (next time) not install my backup drive until
after Sysinstall is long done! I think it's a sysinstall bug, some of this.
* My Reason for saying that is my guess that the sysinstall program saw
the ad0 as something important, and included it in the chain of the
boot. For example, when I was done SLICING my drives in Sysinstall, the
silly thing then got the w write command and
Raw sockets in jails
I'm just curious as to whether FreeBSD8.0 can support raw sockets on some jails and not on others. I'm trying to find the jail flags to allow this to happen. Not having much luck. Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Finding Drivers For winWiFi Card
On 1/24/2010 6:35 PM, Polytropon wrote: On Sun, 24 Jan 2010 07:13:05 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I'll post here later on today, after I've burned the file to disc (no floppy drive on either computer). No possibility to transfer the file via wired network? Your RealTek NIC works out of the box. Or maybe use an USB stick? No. Right now I'd have to move the box halfway across the house into a room that's already too crammed for what's in there. I have considered just running the cable, but I'd have to do so on a day my 3 year old nephew isn't home (one home, 8 people, don't ask) or risk all sorts of problems (nephew tripping and hurting self (biggest concern), nephew tripping and ripping out the cable from the connector, nephew tripping and damaging the router (which would kill entire home network), dogs doing same thing). No floppy disk drive, so only safe option is to burn a CD. IF I can do the run-to-router-with-CAT5 option, that would be ideal (and then there would be no issue, I'd be installing ports like mad until I had the system set up the way I want). -- PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Finding Drivers For winWiFi Card
On 1/24/2010 9:55 PM, Programmer In Training wrote: On 1/24/2010 6:35 PM, Polytropon wrote: On Sun, 24 Jan 2010 07:13:05 -0600, Programmer In Training p...@joseph-a-nagy-jr.us wrote: I'll post here later on today, after I've burned the file to disc (no floppy drive on either computer). No possibility to transfer the file via wired network? Your RealTek NIC works out of the box. Or maybe use an USB stick? snip Forgot to mention, I don't own a USB Stick (yet). I intend to get about two dozen 4GB models when I can (so I can start distributing my PGP Pub Key in person with others so I can say I fully trust them and that key and vice-versa, important for taking steps in doing other verification for products like the Pidgin plugin, OTR (Off-the-Record)). -- PIT Emails are not formal business letters, whatever businesses may want. signature.asc Description: OpenPGP digital signature
Re: Loader, MBR and the boot process
On Mon, 2010-01-25 at 07:57 +1100, Mark Andrews wrote:
In message cf9b1ee01001240759j2476cf3es2babd8b32a90f...@mail.gmail.com, Dan
N
aumov writes:
On Sun, Jan 24, 2010 at 5:29 PM, John j...@starfire.mn.org wrote:
On Fri, Jan 22, 2010 at 07:02:53AM +0200, Dan Naumov wrote:
On Fri, Jan 22, 2010 at 6:49 AM, Dan Naumov dan.nau...@gmail.com wrote=
:
On Fri, Jan 22, 2010 at 6:12 AM, Thomas K. f...@gothschlampen.com
wro=
te:
On Fri, Jan 22, 2010 at 05:57:23AM +0200, Dan Naumov wrote:
Hi,
I recently found a nifty FreeBSD ZFS root installation script and
been reworking it a bit to suit my needs better, including changing =
it
from GPT to MBR partitioning. However, I was stumped, even though I
had done everything right (or so I thought), the system would get
stuck at Loader and refuse to go anywhere. After trying over a dozen
probably this line is the cause:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s1a skip=3D1 seek=
=3D1024
Unless by swap first you meant the on-disk location, and not the
partition letter. If swap is partition a, you're writing the loader
into swapspace.
Regards,
Thomas
At first you made me feel silly, but then I decided to double-check, I
uncommented the swap line in the partitioning part again, ensured I
was writing the bootloader to ${TARGETDISK}s1b and ran the script.
Same problem, hangs at loader. Again, if I comment out the swap,
giving the entire slice to ZFS and then write the bootloader to
${TARGETDISK}s1a, run the script, everything works.
I have also just tested creating 2 slices, like this:
gpart create -s mbr ${TARGETDISK}
gpart add -s 3G -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s1
gpart add -t freebsd-swap ${TARGETDISK}s1
gpart add -t freebsd ${TARGETDISK}
gpart create -s BSD ${TARGETDISK}s2
gpart add -t freebsd-zfs ${TARGETDISK}s2
gpart set -a active -i 2 ${TARGETDISK}
gpart bootcode -b /mnt2/boot/boot0 ${TARGETDISK}
and later:
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2 count=3D1
dd if=3D/mnt2/boot/zfsboot of=3D/dev/${TARGETDISK}s2a skip=3D1 seek=3D=
1024
Putting the swap into it's own slice and then putting FreeBSD into
it's own slice worked fine. So why the hell can't they both coexist in
1 slice if the swap comes first?
I know what the answer to this USED to be, but I don't know if it is
still true (obviously, I think so, I or wouldn't waste your time).
The filesystem code is all carefully written to avoid the very
first few sector of the partition. =A0That's because the partition
table is there for the first filesystem of the slice (or disk).
That's a tiny amout of space wasted, because it's also skipped on
all the other filesystems even though there's not actually anything
there, but it was a small inefficency, even in the 70's.
Swap does not behave that way. =A0SWAP will begin right at the slice
boundry, with 0 offset. =A0As long as it's not the first partition, no
harm, no foul. =A0If it IS the first partition, you just nuked your parti=
tion
table. =A0As long as SWAP owns the slice, again, no harm, no foul, but
if there were filesystems BEHIND it, you just lost 'em.
That's the way it always used to be, and I think it still is. =A0SWAP can
only be first if it is the ONLY thing using that slice (disk), otherwise,
you need a filesystem first to protect the partition table.
--
John Lind
j...@starfire.mn.org
This explanation does sound logical, but holy crap, if this is the
case, you'd think there would be bells, whistles and huge red label
warnings in EVERY FreeBSD installation / partitioning guide out there
warning people to not put swap first (unless given a dedicated slice)
under any circumstances. The warnings were nowhere to be seen and lots
of pointy hair first greyed and were then lost during the process of
me trying to figure out why my system would install but wouldn't boot.
From man bsdlabel.
offset The offset of the start of the partition from the beginning of
the drive in sectors, or * to have bsdlabel calculate the correct
offset to use (the end of the previous partition plus one, ignor-
ing partition `c'. For partition `c', * will be interpreted as
an offset of 0. The first partition should start at offset 16,
because the first 16 sectors are reserved for metadata.
Ok, now this has my attention... My gut feeling right now is that this
is a bug in geom_part_bsd. I don't understand why the label isn't
protected. (Adding -b 16 when adding the swap partition fixes this)
Another project to goes on my list...
If anyone knows why this is done like this... please share.
robert.
- Sincerely,
Dan Naumov
Re: PCIe audio cards: what is tob be preferred with FreeBSD 8.0/9-CURRENT?
O. Hartmann ohart...@mail.zedat.fu-berlin.de wrote: At this very moment I utilise a M-Audio 5.1 PCI-audio board with which I'm really satisfied. My next box doesn't have PCI slots at all ... I look for the Soundblaster X-Fi range of PCIe cards, It's possible to get an adapter that plugs into a PCIe slot and provides a PCI slot, which might enable you to continue using your current card. I've never actually seen one, so don't know about the mechanics; it could turn out that it can only be used by leaving the cover off of the box :( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re : polkit-0.95_3: update fails
You could read /usr/ports/UPDATING because there is section for policikit and polkit. --- En date de : Ven 22.1.10, O. Hartmann ohart...@zedat..fu-berlin.de a écrit : De: O. Hartmann ohart...@zedat.fu-berlin.de Objet: polkit-0.95_3: update fails À: freebsd-questions@freebsd.org, freebsd-po...@freebsd.org Date: Vendredi 22 Janvier 2010, 15h45 I try to update ports via 'portmaster -av' on a regular basis and ran into a sticky problem with poolkit and docbook I'm incapable to solve. Error message follows. Does anybody has any hint or tip? Please email me in CC. Regards, Oliver === Starting build for for ports that need updating === === Launching child to update polkit-0.95_3 === Port directory: /usr/ports/sysutils/polkit === Starting check for build dependencies === Gathering dependency list for sysutils/polkit from ports === Starting dependency check === Checking dependency: devel/eggdbus === Checking dependency: devel/gettext === Checking dependency: devel/glib20 === Checking dependency: devel/gmake === Checking dependency: devel/gobject-introspection === Checking dependency: devel/pkg-config === Checking dependency: textproc/docbook-410 === Launching child to update textproc/docbook-410 polkit-0.95_3 textproc/docbook-410 === Port directory: /usr/ports/textproc/docbook-410 === Starting check for build dependencies === Gathering dependency list for textproc/docbook-410 from ports === Starting dependency check === Checking dependency: archivers/unzip === Dependency check complete for textproc/docbook-410 polkit-0.95_3 textproc/docbook-410 === Cleaning for docbook-4.1_3 === Vulnerability check disabled, database not found === Extracting for docbook-4.1_3 = MD5 Checksum OK for docbk41.zip. = SHA256 Checksum OK for docbk41.zip. === docbook-4.1_3 depends on file: /usr/local/bin/unzip - found === Patching for docbook-4.1_3 === Configuring for docbook-4.1_3 === Starting check for runtime dependencies === Gathering dependency list for textproc/docbook-410 from ports === Starting dependency check === Checking dependency: textproc/iso8879 === Launching child to update textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Port directory: /usr/ports/textproc/iso8879 === Starting check for build dependencies === Gathering dependency list for textproc/iso8879 from ports === Starting dependency check === Checking dependency: archivers/unzip === Dependency check complete for textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Cleaning for iso8879-1986_2 === Vulnerability check disabled, database not found === Extracting for iso8879-1986_2 = MD5 Checksum OK for isoENTS.zip. = SHA256 Checksum OK for isoENTS.zip. === Patching for iso8879-1986_2 === iso8879-1986_2 depends on executable: unzip - found === Configuring for iso8879-1986_2 === Starting check for runtime dependencies === Gathering dependency list for textproc/iso8879 from ports === Starting dependency check === Checking dependency: textproc/xmlcatmgr === Dependency check complete for textproc/iso8879 polkit-0.95_3 textproc/docbook-410 textproc/iso8879 === Installing for iso8879-1986_2 === Generating temporary packing list xmlcatmgr: entry already exists for `iso8879/catalog' of type `CATALOG' *** Error code 1 Stop in /usr/ports/textproc/iso8879. === Installation of iso8879-1986_2 (textproc/iso8879) failed === Aborting update === Update for textproc/iso8879 failed === Aborting update === Update for textproc/docbook-410 failed === Aborting update === Update for polkit-0.95_3 failed === Aborting update ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re : polkit-0.95_3: update fails
Please don't crosspost to -ports and -questions. On 01/24/10 22:35, Alexandre L. wrote: You could read /usr/ports/UPDATING because there is section for policikit and polkit. Correct. I'll add (since I could see from the OP that you're a portmaster user) that I tested the following and it worked for me: portmaster sysutils/policykit sysutils/polkit Of course, make sure that you update your ports tree FIRST, since there apparently was a docbook-related issue in the early stages that was fixed recently. Also, there is a new version of portmaster out as of yesterday so update your ports tree, update portmaster to 2.17, THEN do the above. :) hth, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 8.0-RELEASE/amd64 - full ZFS install - low read and write disk performance
Dan Naumov wrote: On Mon, Jan 25, 2010 at 2:14 AM, Dan Naumov dan.nau...@gmail.com wrote: On Sun, Jan 24, 2010 at 11:53 PM, Alexander Motin m...@freebsd.org wrote: Dan Naumov wrote: This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and 4GB in 143.8 seconds / 28,4mb/s and somewhat consistent with the bonnie results. It also sadly seems to confirm the very slow speed :( The disks are attached to a 4-port Sil3124 controller and again, my Windows benchmarks showing 65mb/s+ were done on exact same machine, with same disks attached to the same controller. Only difference was that in Windows the disks weren't in a mirror configuration but were tested individually. I do understand that a mirror setup offers roughly the same write speed as individual disk, while the read speed usually varies from equal to individual disk speed to nearly the throughput of both disks combined depending on the implementation, but there is no obvious reason I am seeing why my setup offers both read and write speeds roughly 1/3 to 1/2 of what the individual disks are capable of. Dmesg shows: atapci0: SiI 3124 SATA300 controller port 0x1000-0x100f mem 0x90108000-0x9010807f,0x9010-0x90107fff irq 21 at device 0.0 on pci4 ad8: 1907729MB WDC WD20EADS-32R6B0 01.00A01 at ata4-master SATA300 ad10: 1907729MB WDC WD20EADS-00R6B0 01.00A01 at ata5-master SATA300 8.0-RELEASE, and especially 8-STABLE provide alternative, much more functional driver for this controller, named siis(4). If your SiI3124 card installed into proper bus (PCI-X or PCIe x4/x8), it can be really fast (up to 1GB/s was measured). -- Alexander Motin Sadly, it seems that utilizing the new siis driver doesn't do much good: Before utilizing siis: iozone -s 4096M -r 512 -i0 -i1 random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 28796 287665161050695 After enabling siis in loader.conf (and ensuring the disks show up as ada): iozone -s 4096M -r 512 -i0 -i1 random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 28781 288974721450540 Just to add to the numbers above, exact same benchmark, on 1 disk (detached 2nd disk from the mirror) while using the siis driver: random randombkwd record stride KB reclen write rewritereadrereadread writeread rewrite read fwrite frewrite fread freread 4194304 512 57760 563716886774047 If both parts of mirror uses same controller, it doubles it's bus traffic. That may reduce bandwidth twice. The main benefit of siis(4) is a command queuing. You should receive more benefits on multithread random I/O. -- Alexander Motin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Problem with GnuPG
On Sat, Jan 23, 2010 at 06:19:58AM -0500, Jerry wrote: I posted this recently on the GnuPG forum; however, no one had ever seen it before. FreeBSD-7.2 gpg (GnuPG) 2.0.14 libgcrypt 1.4.4 gpa 0.9.0 I honestly have no idea what the problem is here. I recently installed GnuPG on my system. Everything appeared to go fine. For some reason, I have numerous keys listed that I have no knowledge of. This URL shows the keys: http://seibercom.net/gnupg/KeyListing.png These are not OpenPGP keys, but x.509 certificates. I have no idea why they are showing up in the listing, nor can I delete them. GnuPG no longer works with my MUA either.I have tried deleting GnuPG in its entirety and the ~/.gnupg directory. That did not alleviate the problem. Once I reinstalled them, the problem resurfaced. I've never heard of anything like this with GnuPG either, and I'm really not sure how you'd end up with a bunch of X.509 certificates in a GnuPG keyring. I do have a hypothesis for you to investigate, however: You're using a tool I don't know anything about from personal experience. Specifically, I'm talking about GPA. I've always just used the command line tools. Because what you describe doesn't seem to make any sense for the functionality of GnuPG, and you have this featureful GUI application for managing keys, I thought maybe that was the place to look. The contents of the pkg-descr file for security/gpa say: The GNU Privacy Assistant is a graphical frontend to GnuPG and may be used to manage the keys and encrypt/decrypt/sign/check files. It is much like Seahorse. WWW: http://gpa.wald.intevation.org/ Checking the site didn't really give me any information at all, but the pkg-descr file for Seahorse says: Seahorse is a Gnome front end for GnuPG - the Gnu Privacy Guard program. It is a tool for secure communications and data storage. Data encryption and digital signature creation can easily be performed through a GUI and Key Management operations can easily be carried out through an intuitive interface. WWW: http://seahorse.sourceforge.net/ Looking at the Seahorse site, it says it supports GnuPG keys *and* SSH keys. It lists a few other things it does, including an ambiguous and frustratingly undefined More I hunted around a bit and, on the developer wiki, found a short list labeled To Do (Grand Plans and Quackery) that included Support X.509 certificates as its first item. My thought is, if the GPA developers are following a similar path to what the Seahorse developers are doing, they might even have gotten to X.509 certs first. If that's the case, GPA may have just automagically hunted up the X.509 certificates used by your browser and added them to the list of managed keys. Given the notion that GPA may have a bunch of functionality and features that aren't even known to the user, and that it may try to magically do things its developers assume people want, it's possible that it is interfering somehow in the proper operation of GnuPG with regard to your MUA. Perhaps some configuration file(s) for GPA, separate from the GnuPG configuration directory itself, are surviving the uninstalls and reinstalls of your various OpenPGP related tools -- and maybe that's the reason it isn't currently working with your MUA. It could be worth investigating. Is the manpage for GPA any help at all (since there doesn't appear to be any documentation at all on the Website)? I'm curious about what's causing the problem, so if/when you get this sorted out, I'd appreciate it if you'd let me know anything you learn about the problem. I may try to help you investigate the matter further as well if you keep me abreast of what you uncover about the matter. Of course, I don't plan to install GPA anywhere, so my ability to look into it is *somewhat* limited, but I might be able to pitch in a little as time permits. Other than dumping the whole system, reformatting and re-installing the OS, has anyone ever heard of this happening before; and if so, how to correct it? I'm sure there's *something* you can do without nuking and paving -- even if it's somewhat drastic, like selecting a different MUA (if, for instance, a change in one of the tools or in the MUA itself has introduced an incompatibility somewhere). Oh, that reminds me . . . is it possible that a change has been made to some configuration for the MUA itself, without your knowledge? What *is* your MUA, anyway? Good luck. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpLFxPjHBt2w.pgp Description: PGP signature
