Re: carp(4) on FreeBSD 8.2
Victor Sudakov schreef: Colleagues, Are there any success stories or known issues with carp(4) on FreeBSD 8.2? I have configured a carp interface: router1# ifconfig le0 le0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8VLAN_MTU ether 08:00:27:aa:6a:bd inet 10.14.135.88 netmask 0xfe00 broadcast 10.14.135.255 media: Ethernet autoselect status: active router1# router1# ifconfig carp0 carp0: flags=49UP,LOOPBACK,RUNNING metric 0 mtu 1500 inet 10.14.134.99 netmask 0xfe00 carp: MASTER vhid 1 advbase 1 advskew 0 router1# But for some reason I can ping 10.14.135.88, but cannot ping 10.14.134.99. There seem to be ARP responses however: $ arp -an | grep 10.14.134.99 ? (10.14.134.99) at 00:00:5e:00:01:01 on re0 [ethernet] This looks like a VRRP MAC address for sure. And this MAC address is present in the switch forwarding table: Core5sh mac-address-table | i .5e00.0101 1.5e00.0101DYNAMIC Fa0/18 What is even more strange, tcpdump on le0 does not even see ICMP echo requests addressed to 10.14.134.99. What am I doing wrong? Can you show your relevant rc.conf settings. For both master and slave machine, also the relevant sysctl.conf settings could help. regards Johan Hendriks ___ 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: Forward error correction routines?
On 12/14/2011 5:45 AM, Dennis Glatting wrote: I am looking for /any/ forward error correction code under FreeBSD, whether Hamming Codes, Golay Codes, Reed-Solomon, BCH codes, etc. or convolution encoders/decoders. All I've found is: * libfec, which only runs under i386 (I am 64 bit), and * reed-solomon, which is merely a library and no executables. Is there any usable utilities? Clue please. You could try this: http://users.softlab.ntua.gr/~ttsiod/rsbep.html It is meant to be used with storage devices and does interleaving so it can recover a lost sector. Hint: the decoded output contains garbage at the end, you have to use the included utility(or dd) to get the correct file size. HTH, Nikos ___ 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: carp(4) on FreeBSD 8.2
Johan Hendriks wrote: Are there any success stories or known issues with carp(4) on FreeBSD 8.2? I have configured a carp interface: [dd] But for some reason I can ping 10.14.135.88, but cannot ping 10.14.134.99. There seem to be ARP responses however: [dd] What am I doing wrong? Can you show your relevant rc.conf settings. What settings are relevant? I really did not use rc.conf to configure carp. I just did manually ifconfig carp0 create ifconfig carp0 vhid 1 pass X 10.14.134.99/23 and the same on the other host. For both master and slave machine, also the relevant sysctl.conf settings could help. sysctl.conf is really empty, these are just vanilla boxes in a lab. router1# sysctl -a | grep carp net.inet.ip.same_prefix_carp_only: 0 net.inet.carp.allow: 1 net.inet.carp.preempt: 0 net.inet.carp.log: 1 net.inet.carp.arpbalance: 0 net.inet.carp.suppress_preempt: 0 router1# ipfw list 65535 allow ip from any to any Well, _almost_ vanilla boxes. They have custom kernels: include GENERIC ident FW device carp device lagg options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT#allow everything by default options IPDIVERT#divert sockets options IPFIREWALL_FORWARD #packet destination changes options IPFIREWALL_NAT #ipfw kernel nat support options LIBALIAS options QUOTA #enable disk quotas options ROUTETABLES=4 # $Header: svn://big/configs/kernels/trunk/FW 2967 2011-12-13 10:08:29Z sudakov $ -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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
some troble with compilation of newkernel
Hi users! I`ve got freeBSD8.2 system. Before the assemblage of a kernel the file has been checked up by config. The syntax of a file was correct. But the compilation was not completed .. Stop in /usr/obj/usr/src/sys/newkernel. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ... About the error see in compile_err lile, and remaining information about the hardware and the kernel file see the attached files. Many thanks for attention... Kernel build for newkernel started on Wed Dec 14 10:02:13 UTC 2011 -- === newkernel mkdir -p /usr/obj/usr/src/sys -- stage 1: configuring the kernel -- cd /usr/src/sys/i386/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/newkernel /usr/src/sys/i386/conf/newkernel Kernel build directory is /usr/obj/usr/src/sys/newkernel Don't forget to do ``make cleandepend make depend'' -- stage 2.1: cleaning up the object tree -- cd /usr/obj/usr/src/sys/newkernel; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION=FreeBSD 8.2-RELEASE i386 802000 INSTALL=sh /usr/src/tools/install.sh PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin NO_CTF=1 make KERNEL=kernel cleandir rm -f *.o *.so *.So *.ko *.s eddep errs kernel kernel kernel.symbols linterrs makelinks tags vers.c vnode_if.c vnode_if.h vnode_if_newproto.h vnode_if_typedef.h agp_if.c ata_if.c eisa_if.c miibus_if.c mmcbr_if.c mmcbus_if.c card_if.c power_if.c pci_if.c pcib_if.c ppbus_if.c uart_if.c usb_if.c g_part_if.c isa_if.c bus_if.c clock_if.c cpufreq_if.c device_if.c linker_if.c serdev_if.c acpi_if.c acpi_wmi_if.c agp_if.h ata_if.h eisa_if.h miibus_if.h mmcbr_if.h mmcbus_if.h card_if.h power_if.h pci_if.h pcib_if.h ppbus_if.h uart_if.h usb_if.h g_part_if.h isa_if.h bus_if.h clock_if.h cpufreq_if.h device_if.h linker_if.h serdev_if.h acpi_if.h acpi_wmi_if.h acpi_quirks.h miidevs.h pccarddevs.h teken_state.h usbdevs.h usbdevs_data.h acpi_wakecode.h acpi_wakecode.o acpi_wakecode.bin rm -f .depend machine compiling. cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /usr/src/sys/x86/isa/nmi.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /usr/src/sys/x86/pci/qpi.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror /usr/src/sys/x86/x86/dump_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes
Files End Up Read-Only With Samba
I am running FreeBSD-8.2-STABLE-amd64, last update was a few weeks ago. I run Samba-3.6 on this server and it has served me well for my Windows clients to store and share files. All was working fine until recently I've began to notice that whenever I save a file to this server, they always end up with permissions which force me to open them in RO mode when I access them later. The message I'm seeing on the Windows clients is that the file is locked by another user. I check and the owners of the file are root:my_user_account. The permissions are set to rwxr-xr-x. I'm not sure why the root account shows up in the ownership and like I said this was working fine before. ___ 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: I am FreeBSD user.
On 05/12/2011 13:35, Matthew Seaman wrote: On 05/12/2011 12:39, Chris Whitehouse wrote: I thought the odd bit was ssuuddoo --VV | --hh | --ll | --LL | --vv | --kk | --KK | --ss | [ --HH ] [--PP ] [--SS ] [ --bb ] | [ --pp prompt ] [ --cc class|- ] [ --aa auth_type ] [ --uu username|#uid ] from the first link. Does anyone else see that or is it my browser? firefox-3.6.10,1 No -- your eyes are perfectly fine. It's a failure to render that text properly as bold. On an ancient teletype that would have been done by retyping the same character on top of the first one, which is ultimately where all those doubled characters come from. Cheers, Matthew I know it's trivial but I sent a PR (163149) with a patch (of sorts). Chris ___ 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: carp(4) on FreeBSD 8.2
I've used carp very successfully in the past, both in the standard mode and ARP load-balancing mode, to build fail-over sets of firewalls. It worked well enough that one of our firewalls was down for a week before we noticed (and none of our clients did). I just did a mock-up of your scenario on a system at home (using the GENERIC kernel), and it seemed to work for me. I see you have a managed switch; you might see if some features like port security are disabled for that port. What is even more strange, tcpdump on le0 does not even see ICMP echo requests addressed to 10.14.134.99. That is strange. You might try tcpdump -nevvv -i interface host 10.14.134.99 on the sending system and see if it's even sending the packets at all. If there's a remote chance that something else is using carp or VRRP on that network, you might try using a different VHID. Hope I can help, Matt Mullins ___ 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: freebsd is really bsd?
On Tue, 13 Dec 2011 12:55:14 -0500 Sean Cavanaugh millenia2...@hotmail.com wrote: The best explanation I have ever seen to give people fresh to the BSD project is the following youtube clip from years ago. It traces all the way back to its origins and gives nice examples of some of the small companies that use BSD derived code in their programs. http://www.youtube.com/watch?v=g7tvI6JCXD0feature=relmfu Thanks for providing that link; I really enjoyed watching it. :-) To everyone else: if you're interested in the history of BSD, with a lighthearted, humorous and entertaining presentation, check out the above. Fun stuff! A lot of similarly entertaining and interesting links will turn up in the process as well. -- Conrad J. Sabatier conr...@cox.net ___ 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: AHCI driver and static device names
On 12/3/11 11:04 AM, CyberLeo Kitsana wrote: To answer your question, though: You cannot combine GPT with glabel (or any other geom class that writes data to the first or last 34 sectors of a disk, like gmirror) due to layout conflicts. MBR and BSD schemes can be used, since they occupy only the first sectors of the device, and their monikers will be appended to the label. Thus, labeling a single-slice MBR disk (/dev/ada0) with 'test' would produce /dev/ada0, /dev/ada0s1, /dev/label/test, and /dev/label/tests1; nesting a BSD table within s1 would add /dev/ada0s1a and /dev/label/tests1a as well. Do gpt labels work the same as glabel, ie provide a static device name that can be acted upon with /etc/fstab, zfs, gmirror, etc? The other option seems to be to use tunefs or a partitioning tool to label each partition, which is even more ugly imo. Ugly how? Labels appear a lot more semantically elegant than the opaque 'ada4s1a' moniker. Ugly in that the driver has created a situation where we need workarounds to perform the tasks we need. *nix systems have always relied upon static device nodes, and using dynamic names without updating the relating tools/methods is ugly. The workarounds also could fail if someone forgets to perform them (specifically labels), since it's not necessary on just about any other *nix system. It's perfectly within reason to assume people will forget to apply a label when replacing a disk. Case in point. I have a system with 15 drives in it. I decided I wanted to install on the 2nd device instead of the 1st, but I partitioned all the other 14 drives. I completed installation and when to boot the system and it failed. Stupid me, the GPT boot loader found disk1 with a partitioning scheme but no fs. So, I popped out disk 1 and when to boot again. Hey, now it starts to boot only to fail to find the root fs because it's looking on ada1 and the fs is on ada0. That is a mess. This is not necessarily common, but also not uncommon. More likely is the case where you add a drive to the system and the above scenario plays out because the device names get re-ordered. I'm not sure the problem the dynamic device nodes intends to solve, but it's certainly caused all sorts of pain and the need for the 2 (that I know of) workarounds. I dislike the idea of having to use labels to get static functionality (increases the likelihood of something going wrong for a disk replace operation if I forget to label), but I'll give gpt labels a try. Rob ___ 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: AHCI driver and static device names
Can glabels, gpt, and zfs all work together? I have a system where I have disks with 4 gpt partitions. Partitions 2 and 3 are part of gmirror arrays, and partition 4 is part of a zfs pool. glabel says it writes to the end of the partition, which I believe zfs also writes to doesn't it? Rob On 12/4/11 4:28 AM, per...@pluto.rain.com wrote: CyberLeo Kitsanacyber...@cyberleo.net wrote: You cannot combine GPT with glabel (or any other geom class that writes data to the first or last 34 sectors of a disk, like gmirror) due to layout conflicts. This is overstated. Since a GPT ordinarily is intended to be booted from, and so must be recognized by the BIOS, it must be written directly on the actual drive -- the rank 1 provider in GEOM terms -- because that is the only way for the GPT metadata to be located where the BIOS expects to find it (at both the beginning and the end of the drive). It is, however, possible to combine GPT with gmirror, gjournal, etc. by using GPT partitions, rather than drives, as providers for the other geoms. For example, create a mirror from ad0p1 and ad2p1 rather than from ad0 and ad2. Similarly, it should be possible to glabel a GPT partition -- although this seems unlikely to be useful in practice since GPT provides its own labelling scheme. ___ 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
acpi problem on dell latitude d830
Hello! I`ve just installed freebsd 8.2 i386 stable on a Dell Latitude D830. I`m using gnome 2 with HAL and DBUS successfully. My notebook is not able to go into sleeping mode, it doesn`t work when I use acpiconf -s 3 or acpiconf -s 4. Mode S3 gets it into sleep mode, but it freezes after wake-up with a distorted screen. In mode S4 (suspend-to-disk) it isn`t even able to get into sleeping mode. I want to initiate S4 state by closing the lid. I also want to use the docking station. I would like to use the hot-docking functionality. The docking station has a power switch, which functions properly. It also has an undocking-button, which causes a freeze of the system. The audio-out on the docking-station is also not working. PS/2 keyboard, ethernet and USB on the docking-station is working. My kernel was compiled with acpi_dock. dmesg says: acpi_dock0: ACPI Docking Station on acpi0 acpi_dock0: _DCK failed Xueyu ___ 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
opening vim with a flag: ready to write?
hi y'all:) i am making steady progress in learning gtk. i'll spare the list my usual rambling and get rt to the point. is the a way of starting off vim or gvim and be able to type into the editor _without_ first typing: a,i,o,O,I,A, or any other character? or is this just one more thing to include in my brief tutorial? tia, gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ 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: opening vim with a flag: ready to write?
From owner-freebsd-questi...@freebsd.org Wed Dec 14 18:46:46 2011 Date: Wed, 14 Dec 2011 16:42:31 -0800 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: opening vim with a flag: ready to write? hi y'all:) i am making steady progress in learning gtk. i'll spare the list my usual rambling and get rt to the point. is the a way of starting off vim or gvim and be able to type into the editor _without_ first typing: a,i,o,O,I,A, or any other character? Did you bother to look at the manpage for the program in question, *BEFORE* mailing the list?? If so, what did you find? What did you try? And what were the results? If not, *WHY*NOT*?? be specific. ___ 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: AHCI driver and static device names
On 12/14/2011 03:20 PM, Rob wrote: Can glabels, gpt, and zfs all work together? I have a system where I have disks with 4 gpt partitions. Partitions 2 and 3 are part of gmirror arrays, and partition 4 is part of a zfs pool. glabel says it writes to the end of the partition, which I believe zfs also writes to doesn't it? Yup. However, all nestable geoms protect their metadata (when it exists) by providing a device that is smaller, so any nested consumer never even sees the provider's metadata. The end of the glabel device to which zfs writes its metadata in your implied example is actually several sectors prior to the end of the device or partition to which glabel writes its metadata. Explicit glabels are not strictly necessary with the GPT partitioning scheme, since the glabel module can peek into the GPT data structure, extract label names from there, and automatically create appropriate /dev/gpt/ entries for those labels. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net cyber...@cyberleo.net Furry Peace! - http://.fur.com/peace/ ___ 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: AHCI driver and static device names
On 12/14/2011 03:18 PM, Rob wrote: On 12/3/11 11:04 AM, CyberLeo Kitsana wrote: To answer your question, though: You cannot combine GPT with glabel (or any other geom class that writes data to the first or last 34 sectors of a disk, like gmirror) due to layout conflicts. MBR and BSD schemes can be used, since they occupy only the first sectors of the device, and their monikers will be appended to the label. Thus, labeling a single-slice MBR disk (/dev/ada0) with 'test' would produce /dev/ada0, /dev/ada0s1, /dev/label/test, and /dev/label/tests1; nesting a BSD table within s1 would add /dev/ada0s1a and /dev/label/tests1a as well. Do gpt labels work the same as glabel, ie provide a static device name that can be acted upon with /etc/fstab, zfs, gmirror, etc? Yes. It's actually handled by the same geom class. The other option seems to be to use tunefs or a partitioning tool to label each partition, which is even more ugly imo. Ugly how? Labels appear a lot more semantically elegant than the opaque 'ada4s1a' moniker. Ugly in that the driver has created a situation where we need workarounds to perform the tasks we need. *nix systems have always relied upon static device nodes, and using dynamic names without updating the relating tools/methods is ugly. The workarounds also could fail if someone forgets to perform them (specifically labels), since it's not necessary on just about any other *nix system. It's perfectly within reason to assume people will forget to apply a label when replacing a disk. Anything fails if you forget to do it. Administrative failure should not be confused with technical failure. Static device nodes are appropriate when the topology is fixed and can be reasonably anticipated. With variable topologies, such as USB, iSCSI, multipath, and PCI hotswap, the disk controllers may not even exist at boot, or may be reordered based on probe order, or the order in which the remote units respond; and that's before the kernel even gets around to setting up the devices attached to those controllers. You cannot reasonably expect the system to statically allocate device nodes for every possible configuration that may exist for all technologies that might be added to a machine, so why offer the expectation when the system cannot possibly hope to fulfill it for even a fraction of the common cases? Case in point. I have a system with 15 drives in it. I decided I wanted to install on the 2nd device instead of the 1st, but I partitioned all the other 14 drives. I completed installation and when to boot the system and it failed. Stupid me, the GPT boot loader found disk1 with a partitioning scheme but no fs. So, I popped out disk 1 and when to boot again. Hey, now it starts to boot only to fail to find the root fs because it's looking on ada1 and the fs is on ada0. That is a mess. Sounds like a bug in the BIOS or boot loader. The boot loader should be able to ask the BIOS for the device from which it read the boot code, and use that instead of just naively using the the first available device in the system; the only instances where I've seen this fail have been on machines that should've been put down years ago. Which isn't to say it doesn't still happen. This is not necessarily common, but also not uncommon. More likely is the case where you add a drive to the system and the above scenario plays out because the device names get re-ordered. I'm not sure the problem the dynamic device nodes intends to solve, but it's certainly caused all sorts of pain and the need for the 2 (that I know of) workarounds. How about when you add a PATA drive to a machine, but the cable is blocking the last available bay; so you have to move an existing drive to a different position on the cable to make room for the one you're installing? Static device numbering won't save you now. Or how about those silly BIOSes that assume that you must really want to boot to the new disk you just attached to the machine, so helpfully rearrange your boot order for you so now you're booting to a strange disk with who knows what on it? Honestly, there's so much that can go wrong. That's what sysadmins are for. I dislike the idea of having to use labels to get static functionality (increases the likelihood of something going wrong for a disk replace operation if I forget to label), but I'll give gpt labels a try. I find that labels solve more problems than they introduce, when applied properly. The semantic meaning given to the devices often mean I can discover what's on a particular disk in my pile'o'drives just by plugging it in and looking at the kernel log; no mounting necessary. Likewise, when juggling disks or controllers around, I don't have to worry about remembering to update the fstab, since the labels follow the data. This is a lot better than my Linux machine, where I have to do some rather interesting hacks in the initrd just to make sure the root mirror is
[PATCH] Re: Forward error correction routines?
On 12/13/2011 22:45, Dennis Glatting wrote:
I am looking for /any/ forward error correction code under FreeBSD,
whether Hamming Codes, Golay Codes, Reed-Solomon, BCH codes, etc. or
convolution encoders/decoders.
All I've found is:
* libfec, which only runs under i386 (I am 64 bit), and
Here are patches allowing libfec to compile on amd64. I'll submit a pr.
*** libfec/Makefile.orig2011-12-14 20:34:24.653733990 -0500
--- libfec/Makefile 2011-12-14 20:50:52.306036812 -0500
***
*** 22,31
GNU_CONFIGURE=yes
USE_GMAKE=yes
USE_LDCONFIG= yes
! ONLY_FOR_ARCHS= i386
PLIST_FILES= include/fec.h lib/libfec.so lib/libfec.a
post-patch:
@${REINPLACE_CMD} -e 's|gcc|${CC}|g' ${WRKSRC}/makefile.in
.include bsd.port.mk
--- 22,35
GNU_CONFIGURE=yes
USE_GMAKE=yes
USE_LDCONFIG= yes
! ONLY_FOR_ARCHS= i386 amd64
PLIST_FILES= include/fec.h lib/libfec.so lib/libfec.a
post-patch:
@${REINPLACE_CMD} -e 's|gcc|${CC}|g' ${WRKSRC}/makefile.in
.include bsd.port.mk
+
+ .if ${ARCH} == amd64
+ CFLAGS+= -fPIC
+ .endif
*** /dev/null 2011-12-14 20:57:48.0 -0500
--- libfec/files/patch-dotprod.c2011-12-14 20:44:01.336529860 -0500
***
*** 0
--- 1,12
+ *** dotprod.c 2006-10-12 21:10:53.0 -0400
+ --- ../../foowork/fec-3.0.1/dotprod.c 2011-12-14 20:43:00.132752233 -0500
+ ***
+ *** 54,59
+ --- 54,60
+ switch(Cpu_mode){
+ case PORT:
+ default:
+ + return feedp_port(p);
+ #ifdef __i386__
+ case MMX:
+ case SSE:
___
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: opening vim with a flag: ready to write?
On Wed, Dec 14, 2011 at 07:11:20PM -0600, Robert Bonomi wrote: Date: Wed, 14 Dec 2011 19:11:20 -0600 (CST) From: Robert Bonomi bon...@mail.r-bonomi.com Subject: Re: opening vim with a flag: ready to write? To: freebsd-questions@freebsd.org, kl...@thought.org Cc: From owner-freebsd-questi...@freebsd.org Wed Dec 14 18:46:46 2011 Date: Wed, 14 Dec 2011 16:42:31 -0800 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: opening vim with a flag: ready to write? hi y'all:) i am making steady progress in learning gtk. i'll spare the list my usual rambling and get rt to the point. is the a way of starting off vim or gvim and be able to type into the editor _without_ first typing: a,i,o,O,I,A, or any other character? Did you bother to look at the manpage for the program in question, *BEFORE* mailing the list?? If so, what did you find? What did you try? And what were the results? If not, *WHY*NOT*?? be specific. of course i checked the man page; that doesnt mean there is some undocumented method that someone here found. ___ 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 -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.57a release of Jottings: http://jottings.thought.org Twenty-five years of service to the Unix community. ___ 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
Wine-fbsd64 updated to 1.3.34 (32bit Wine for 64bit FreeBSD)
Hi, Packages [1] for wine-fbsd64-1.3.34 have been uploaded to mediafire [2]. There are many reports that wine does not work with a clang compiled world (help in fixing this problem is appreciated as it affects quite a few users). The patch [3] for nVidia users is now included in the package and is run on installation (if the relevant files are accessable). Please read the installation messages for further information. Regards, David [1] MD5 (freebsd8/wine-fbsd64-1.3.34,1.tbz) = 772fc62a7278f9838b273b04c64aba00 MD5 (freebsd9/wine-fbsd64-1.3.34,1.txz) = b8267c46e9dc6727f23138ec146abf68 [2] http://www.mediafire.com/wine_fbsd64 [3] The patch is located at /usr/local/share/wine/patch-nvidia.sh signature.asc Description: This is a digitally signed message part.
Re: freebsd is really bsd?
On Wed, Dec 14, 2011 at 3:06 PM, Conrad J. Sabatier conr...@cox.net wrote: To everyone else: if you're interested in the history of BSD, with a lighthearted, humorous and entertaining presentation, check out the above. Fun stuff! A lot of similarly entertaining and interesting links will turn up in the process as well. I already told cool! ___ 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: AHCI driver and static device names
On 12/14/11 8:05 PM, CyberLeo Kitsana wrote: The other option seems to be to use tunefs or a partitioning tool to label each partition, which is even more ugly imo. Ugly how? Labels appear a lot more semantically elegant than the opaque 'ada4s1a' moniker. Ugly in that the driver has created a situation where we need workarounds to perform the tasks we need. *nix systems have always relied upon static device nodes, and using dynamic names without updating the relating tools/methods is ugly. The workarounds also could fail if someone forgets to perform them (specifically labels), since it's not necessary on just about any other *nix system. It's perfectly within reason to assume people will forget to apply a label when replacing a disk. Anything fails if you forget to do it. Administrative failure should not be confused with technical failure. When you're changing a paradigm that is known to administrators for decades, it's unreasonable not to expect a decent degree of failure. Especially when the reason for the technical change isn't clear and the new method isn't at all like the old (ie no disk is guaranteed to get the same id). Static device nodes are appropriate when the topology is fixed and can be reasonably anticipated. With variable topologies, such as USB, iSCSI, multipath, and PCI hotswap, the disk controllers may not even exist at boot, or may be reordered based on probe order, or the order in which the remote units respond; and that's before the kernel even gets around to setting up the devices attached to those controllers. You cannot reasonably expect the system to statically allocate device nodes for every possible configuration that may exist for all technologies that might be added to a machine, so why offer the expectation when the system cannot possibly hope to fulfill it for even a fraction of the common cases? I grant you variable topologies makes things incredibly hairy, but there's no need to take that mess and inject it into how the fixed topology (the physical hw in the box) is handled. Trying to handle all topology types in a single space can be messy. This problem wouldn't exist if a fixed topology used the old naming (adXX) and the variable topologies used the new naming (adaXX). Even this is less than ideal because your variable topologies provide no guarantee of anything being the same, thus your system could boot 1 day and fail the next because someone added a new piece of hardware to the network. That's probably more the name of the game in variable topologies (adminA changes the configuration on $ImportantBootDevice and stuff breaks), but I certainly don't want that uncertainty with the hardware in a machine. I stated that updating the device naming w/o updating the methodologies that rely upon that device naming is asking for trouble. I can't say I know a solution nor that I'm an expert, but this seems like it will cause many more problems than it will solve. Case in point. I have a system with 15 drives in it. I decided I wanted to install on the 2nd device instead of the 1st, but I partitioned all the other 14 drives. I completed installation and when to boot the system and it failed. Stupid me, the GPT boot loader found disk1 with a partitioning scheme but no fs. So, I popped out disk 1 and when to boot again. Hey, now it starts to boot only to fail to find the root fs because it's looking on ada1 and the fs is on ada0. That is a mess. Sounds like a bug in the BIOS or boot loader. The boot loader should be able to ask the BIOS for the device from which it read the boot code, and use that instead of just naively using the the first available device in the system; the only instances where I've seen this fail have been on machines that should've been put down years ago. Which isn't to say it doesn't still happen. No bug in the BIOS at all. It's simply a case of device boot order, and being that I installed on disk 2 but put a bootloader on disk 1 with no OS the result was expected. This is not necessarily common, but also not uncommon. More likely is the case where you add a drive to the system and the above scenario plays out because the device names get re-ordered. I'm not sure the problem the dynamic device nodes intends to solve, but it's certainly caused all sorts of pain and the need for the 2 (that I know of) workarounds. How about when you add a PATA drive to a machine, but the cable is blocking the last available bay; so you have to move an existing drive to a different position on the cable to make room for the one you're installing? Static device numbering won't save you now. This is not the same thing at all. If I move a physical cable, or a drive on a cable, then yes I should expect things to change. I have made a physical change to the disk's connections, and I should expect something to come out of it. In my case, I have not moved the cabling of a disk at all and thus expect the
Re: carp(4) on FreeBSD 8.2
Matt Mullins wrote: I've used carp very successfully in the past, both in the standard mode and ARP load-balancing mode, to build fail-over sets of firewalls. It worked well enough that one of our firewalls was down for a week before we noticed (and none of our clients did). I just did a mock-up of your scenario on a system at home (using the GENERIC kernel), and it seemed to work for me. I see you have a managed switch; you might see if some features like port security are disabled for that port. It turned out even more interesting. The lab is virtual, and promiscuous mode was prohibited in the virtual NICs' properties on the hypervisor. Thanks to all who responded. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ 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
