Re: FreeBSD on SSD on ASUS P5KPL-C
On Sat, 24 Nov 2012, Matthias Apitz wrote: El día Wednesday, November 21, 2012 a las 09:19:24PM -0700, Warren Block escribió: On Wed, 21 Nov 2012, Warren Block wrote: The fdisk/bsdlabel section of my disk setup article has been rewritten to use gpart. Feedback welcome. http://www.wonkity.com/~wblock/docs/html/disksetup.html Hi Warren, When the page is opened with konqueror of KDE 3.5.10 the JS functions for Table Of Content generator are generating in an endless loop the links. That's... unexpected. It's a stock AsciiDoc-generated feature. The PDF version is at: http://www.wonkity.com/~wblock/docs/pdf/disksetup.pdf___ 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: do I need agp(4) on my amd64 laptop
On 22 November 2012 06:19, Anton Shterenlikht me...@bristol.ac.uk wrote: It is not clear for me from the agp(4) man page, whether I need this device in the kernel or not. The pciconf -lv output is below. Or do I need to show dmesg? Please advise Thanks Anton hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 Host Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (Internal gfx)' class = bridge subclass = PCI-PCI pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' class = bridge subclass = PCI-PCI pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' class = bridge subclass = PCI-PCI pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' class = bridge subclass = PCI-PCI ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 Non-Raid-5 SATA' class = mass storage subclass = ATA ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI0)' class = serial bus subclass = USB ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI1)' class = serial bus subclass = USB ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI2)' class = serial bus subclass = USB ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI3)' class = serial bus subclass = USB ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI4)' class = serial bus subclass = USB ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB Controller (EHCI)' class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 rev=0x14 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 SMBus Controller' class = serial bus subclass = SMBus atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 IDE' class = mass storage subclass = ATA hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 Azalia (Intel HDA)' class = multimedia subclass = HDA isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 PCI to LPC Bridge' class = bridge subclass = PCI-ISA pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 PCI to PCI Bridge' class = bridge subclass = PCI-PCI hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x06 card=0x chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] Address Map' class = bridge subclass = HOST-PCI hostb3@pci0:0:24:2: class=0x06 card=0x chip=0x11021022 rev=0x00
Re: Should newfs include -S 4096? was Re: boot problem after freebsd-update from 9.1-RC2 to 9.1-RC3
On Fri, 23 Nov 2012, free...@johnea.net wrote: One of the complications was getting old metadata off of the drive. After trying a couple of 'dd' invocations: # overwriting the first sector dd if=/dev/zero of=/dev/ada0 bs=512 count=1 # also tried overwriting the last sector diskinfo ada0 | cut -f4 3907029168 (subtract 34, per WB) (I actually just subtracted the trailing 68) dd if=/dev/zero of=/dev/ada0 seek=3907029100 This would still seem to not delete all of the metadata, since after issuing: gmirror label -b split gm0 /dev/ada0 gmirror load # repartition new mirror gpart create -s MBR mirror/gm0 # ignore mirror/gm0s1 added, but partition is not aligned on 4096 bytes after add gpart add -t freebsd -a 4k mirror/gm0 # create the bsdlabel partitions in slice 1 (s1) gpart create -s BSD mirror/gm0s1 I would see that the old gm0s1a and gm0s1b had reappeared, even though I had not yet issued the 'add -t freebsd-ufs'. I'm not sure if they came back with the 'add -t freebsd' or the 'create -s BSD'. Saved this since yesterday, thinking maybe I could come up with an idea, but so far I can't think what would cause that. It might not hurt to force a retaste after the dd. The only thing that seemed to fix it was: gpart destroy -F /dev/ada0 I also tried at one point: gpart destroy -F ada0 gpart create -s gpt ada0 gpart destroy -F ada0 The thing I wonder about now: Should newfs include -S 4096? I used: newfs -U /dev/mirror/gm0s1a Will this lead to 512 byte sector access to the disk through the file system? Will this impact performance or longevity of the mirror? It's a good question; I have not tried it. ___ 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: do I need agp(4) on my amd64 laptop
On 24 November 2012 10:14, ill...@gmail.com ill...@gmail.com wrote: On 22 November 2012 06:19, Anton Shterenlikht me...@bristol.ac.uk wrote: It is not clear for me from the agp(4) man page, whether I need this device in the kernel or not. The pciconf -lv output is below. Or do I need to show dmesg? Please advise Thanks Anton hostb0@pci0:0:0:0: class=0x06 card=0x30c2103c chip=0x79101002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 Host Bridge' class = bridge subclass = HOST-PCI pcib1@pci0:0:1:0: class=0x060400 card=0x30c2103c chip=0x79121002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (Internal gfx)' class = bridge subclass = PCI-PCI pcib2@pci0:0:4:0: class=0x060400 card=0x30c2103c chip=0x79141002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' class = bridge subclass = PCI-PCI pcib3@pci0:0:5:0: class=0x060400 card=0x30c2103c chip=0x79151002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 1)' class = bridge subclass = PCI-PCI pcib4@pci0:0:6:0: class=0x060400 card=0x30c2103c chip=0x79161002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'RS690 PCI to PCI Bridge (PCI Express Port 2)' class = bridge subclass = PCI-PCI ahci0@pci0:0:18:0: class=0x01018f card=0x43801002 chip=0x43801002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 Non-Raid-5 SATA' class = mass storage subclass = ATA ohci0@pci0:0:19:0: class=0x0c0310 card=0x30c2103c chip=0x43871002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI0)' class = serial bus subclass = USB ohci1@pci0:0:19:1: class=0x0c0310 card=0x30c2103c chip=0x43881002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI1)' class = serial bus subclass = USB ohci2@pci0:0:19:2: class=0x0c0310 card=0x30c2103c chip=0x43891002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI2)' class = serial bus subclass = USB ohci3@pci0:0:19:3: class=0x0c0310 card=0x30c2103c chip=0x438a1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI3)' class = serial bus subclass = USB ohci4@pci0:0:19:4: class=0x0c0310 card=0x30c2103c chip=0x438b1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB (OHCI4)' class = serial bus subclass = USB ehci0@pci0:0:19:5: class=0x0c0320 card=0x30c2103c chip=0x43861002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 USB Controller (EHCI)' class = serial bus subclass = USB none0@pci0:0:20:0: class=0x0c0500 card=0x30c2103c chip=0x43851002 rev=0x14 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 SMBus Controller' class = serial bus subclass = SMBus atapci0@pci0:0:20:1:class=0x010182 card=0x30c2103c chip=0x438c1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 IDE' class = mass storage subclass = ATA hdac0@pci0:0:20:2: class=0x040300 card=0x30c2103c chip=0x43831002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 Azalia (Intel HDA)' class = multimedia subclass = HDA isab0@pci0:0:20:3: class=0x060100 card=0x30c2103c chip=0x438d1002 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SB600 PCI to LPC Bridge' class = bridge subclass = PCI-ISA pcib5@pci0:0:20:4: class=0x060401 card=0x chip=0x43841002 rev=0x00 hdr=0x01 vendor = 'Advanced Micro Devices [AMD] nee ATI' device = 'SBx00 PCI to PCI Bridge' class = bridge subclass = PCI-PCI hostb1@pci0:0:24:0: class=0x06 card=0x chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb2@pci0:0:24:1: class=0x06 card=0x chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'K8 [Athlon64/Opteron] Address Map' class = bridge subclass = HOST-PCI
Anyone using squid and pf?
I've upgraded squid from 3.1 to 3.2. Starting squid 3.2 with the same configuration file now gives me errors in cache.log when one tries to access any site, and of course no access! 2012/11/24 16:24:56 kid1| WARNING: Forwarding loop detected for: Reverting back to 3.1 works. I know there are some changes in 3.2 that does this + 3.2 intercept port receiving forward-proxy requests will reject them due to NAT failure/lies. + 3.2 Host header validation *will* reject if forward traffic is validated as being intercepted. I would appreciate suggestions for changes to squid.conf so that squid will work for me with version 3.2. Thanks /Leslie ___ 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: PF and tables for disabling network
On 23/11/2012 15:58, Fleuriot Damien wrote: On Nov 23, 2012, at 3:46 PM, David Demelier demelier.da...@gmail.com wrote: Hello, I would like to disable the network traffic for specific IPs, for the moment I just add to my pf.conf a rule that will block everything for a specified table like this : table closed [...] others rules [...] block from closed Then I just need to add my IP using pfctl, it will works, no packet can be send / recv to the machine, however if that machine had some active connections, these won't be closed and they can still use them (a SSH client, game, ...) How can I disable everything then? Cheers -- Demelier David First, you might want to use block in quick on $externalif inet from closed , to have: - a quick rule, which stops ruleset evaluation immediately - a more specific rule, which applies only to your WAN interface's inbound traffic Be careful with the quick keyword, it's going to match packets immediately and entirely block these IPs. Then, if you want to kill the active connections from people in the closed table, you might want to script a bit, like: for i in `pfctl -t closed -T show` do pfctl -kK $i done Would that do the trick for you ? Thank you that works very well :) Cheers, -- David Demelier ___ 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
Multi-boot Linux + FreeBSD
Hi, as a long time Linux user I'll test FreeBSD, because I've got issues with my sound card on Linux. I'm already subscribed to FreeBSD multimedia. Perhaps later today I'll install 9.0 amd64. If possible I'll keep my Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or something similar to boot FreeBSD from /dev/sda1? FWIW I made backups of my HDD's MBRs. I wonder if the installer will overwrite the MBR? I also would like to know, if there's a way to recover the partition table, including a primary FreeBSD partition/slice, if this ever should get broken and there should be no backup of the partition table be available. TIA, Ralf [1] $ cat /boot/grub/menu.lst timeout 8 default 0 color light-blue/black light-cyan/blue title Ubuntu Quantal,kernel 3.6.5-rt14 root (hd1,8) kernel /boot/vmlinuz-3.6.5-rt14 root=/dev/sdb9 ro quiet initrd /boot/initrd.img-3.6.5-rt14 title Ubuntu Quantal,kernel 3.5.0-18-lowlatency threadirqs root (hd1,8) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb9 ro quiet threadirqs initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Quantal,kernel 3.5.0-18-lowlatency (recovery mode) root (hd1,8) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb9 ro single initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Studio Quantal, Kernel 3.6.5-rt14 root=(hd1,12) kernel /boot/vmlinuz-3.6.5-rt14 root=/dev/sdb13 ro quiet initrd /boot/initrd.img-3.6.5-rt14 title Ubuntu Studio Quantal, Kernel 3.5.0-18-lowlatency threadirqs root=(hd1,12) kernel /boot/vmlinuz-3.5.0-18-lowlatency root=/dev/sdb13 ro quiet threadirqs initrd /boot/initrd.img-3.5.0-18-lowlatency title Ubuntu Studio Precise, Kernel 3.0.30 threadirqs root=(hd1,0) kernel /boot/vmlinuz-3.0.30 root=UUID=338316fb-364e-4a43-8deb-738127f878ce ro quiet threadirqs initrd /boot/initrd.img-3.0.30 title Ubuntu Studio Precise, Kernel 3.2.0-23-lowlatency threadirqs root=(hd1,0) kernel /boot/vmlinuz-3.2.0-23-lowlatency root=UUID=338316fb-364e-4a43-8deb-738127f878ce ro quiet threadirqs initrd /boot/initrd.img-3.2.0-23-lowlatency title AVlinux 5.0.3, Kernel 3.0.23-rt40 root=(hd1,10) kernel /boot/vmlinuz-3.0.23-rt40 root=/dev/sdb11 ro quiet initrd /boot/initrd.img-3.0.23-rt40 title AVlinux 5.0.3, Kernel 3.0.23-avl-7-pae threadirqs root=(hd1,10) kernel /boot/vmlinuz-3.0.23-avl-7-pae root=/dev/sdb11 ro threadirqs quiet initrd /boot/initrd.img-3.0.23-avl-7-pae title Edubuntu 10.10,Kernel 2.6.33.9-rt31 root=(hd1,7) kernel /boot/vmlinuz-2.6.33.9-rt31 root=UUID=ded93dfb-37ae-48cf-a3a3-b613aa5704fd ro initrd /boot/initrd.img-2.6.33.9-rt31 title Ubuntu Studio Oz, Kernel 3.0.0-17-generic root=(hd1,5) kernel /boot/vmlinuz-3.0.0-17-generic root=UUID=0241b2ac-a0ab-44de-8d73-0ed084e152e6 initrd /boot/initrd.img-3.0.0-17-generic title Ubuntu Studio Oz, Kernel 3.0.0-20-generic root=(hd1,5) kernel /boot/vmlinuz-3.0.0-20-generic root=UUID=0241b2ac-a0ab-44de-8d73-0ed084e152e6 initrd /boot/initrd.img-3.0.0-20-generic title Arch Linux Rt root (hd0,8) kernel /boot/vmlinuz-linux-rt root=/dev/sda9 ro initrd /boot/initramfs-linux-rt.img title Arch Linux root (hd0,8) kernel /boot/vmlinuz-linux root=/dev/sda9 ro initrd /boot/initramfs-linux.img title Arch Linux Fallback root (hd0,8) kernel /boot/vmlinuz-linux root=/dev/sda9 ro initrd /boot/initramfs-linux-fallback.img title openSUSE 11.2, Kernel 2.6.31.6-rt19 root (hd0,6) kernel /boot/vmlinuz-2.6.31.6-rt19 root=/dev/sda7 initrd /boot/initrd-2.6.31.6-rt19 title Ubuntu Quantal memtest86+ root (hd1,8) kernel /boot/memtest86+.bin ___ 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
Is FreeBSD 9 Production Ready?
I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. TIA, -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
Bug or feature - arp command on vlan in 9.0
Hi, I have about 120 FBSD routers - diskless. I use FBSD 8.2, with no problems. But now I am trying 9.0, the same configuration I found difference of behavior command arp between 8.2 and 9.0. In 8.2 I can see arp of ip on all devices, physical and vlans. vlan356: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM inet 10.201.15.65 netmask 0xffe0 broadcast 10.201.15.95 %arp 10.201.15.65 ? (10.201.15.65) at 00:25:90:50:29:82 on vlan356 permanent [vlan] On 9.0 i can see arp only on physical interface em0, on vlans no: vlan319: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=3RXCSUM,TXCSUM inet 10.219.5.193 netmask 0xffe0 broadcast 10.219.5.223 %ping 10.219.5.193 PING 10.219.5.193 (10.219.5.193): 56 data bytes 64 bytes from 10.219.5.193: icmp_seq=0 ttl=64 time=0.032 ms ^C --- 10.219.5.193 ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.032/0.032/0.032/0.000 ms %arp 10.219.5.193 10.219.5.193 (10.219.5.193) -- no entry Is it bug or feature? Thanks Radek ___ 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: Multi-boot Linux + FreeBSD
Hi Ralf,
On 2012.11.24 17:06, Ralf Mardorf wrote:
Perhaps later today I'll install 9.0 amd64. If possible I'll keep my
Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or
something similar to boot FreeBSD from /dev/sda1?
I don't know if GRUB v1 allows that, on a multiboot system I use GRUB 2
to either load FreeBSD's loader(8) :
menuentry FreeBSD (Loader) {
insmod part_bsd
set root='hd0,msdos2,bsd1'
echo Loading FreeBSD loader
kfreebsd /boot/loader
echo Starting FreeBSD loader
}
or to run its kernel directly, after having passed it optional device hints:
menuentry FreeBSD (Direct Boot) {
insmod ufs2
set root='hd0,msdos2,bsd1'
echo Loading FreeBSD kernel
kfreebsd /boot/kernel/kernel
echo Loading FreeBSD environment
kfreebsd_loadenv /boot/device.hints
set kfreebsd.vfs.root.mountfrom=ufs:/dev/ada0s2
echo Booting FreeBSD
}
I'm not saying it's impossible, but I'm unable to chainload to the
loader code on my system with this:
menuentry FreeBSD (Chainload) {
insmod chain
set root='hd0,msdos2'
chainloader +1
}
FWIW I made backups of my HDD's MBRs.
I wonder if the installer will overwrite the MBR?
Always a good thing to have backups. From what I've experienced and
read, 9.0-RELEASE's installer is not always predictable in that regard,
it's probably safer to assume it'll won't do what you want, and just
restore your MBR after the installation, to go back to using GRUB for
dual-booting.
Here's the pitfall, though: the MBR also holds the partition table. So
make a fresh backup after you've created/reorganized the primary
partitions (slices) on your disk using a tool you're familiar with.
(Logical partitions and BSD partitions are stored differently, so they
will survive an MBR restore, provided it doesn't modify the primary
partition they're contained in.)
I also would like to know, if there's a way to recover the partition
table, including a primary FreeBSD partition/slice, if this ever should
get broken and there should be no backup of the partition table be
available.
The partition table is held alongside the MBR, in the first logical
sector of your disk. Restoring one will restore the other.
For extra safety, you can save the output of partitioning tools like
fdisk or GNU parted expressed in sectors.
Hope this helps,
___
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: Is FreeBSD 9 Production Ready?
On 2012.11.24 17:38, Tim Daneliuk wrote: I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? This probably won't help much, but I wouldn't call any system production ready until I've tested it as thoroughly as possible and qualified it myself for the purpose I intend to use it. I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. As far as FreeBSD release engineering goes, I believe all -RELEASE versions are aimed at maximum stability. But obviously no person or organization can ever test all possible hardware, software and settings combinations. ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 11:19 AM, Lucas B. Cohen wrote: I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. In general, I'd agree with you. Certainly, that's been the case with Linux, AIX, and so on over the years. But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Compatability for various USB 3.0 / PCIe cards ?
On 2012.11.23 22:11, Ronald F. Guilmette wrote: Well friends, it's that time of year again... yep, it's shop till you drop time! For me it's usually *after* Christmas season, but whatever works :) I can't imagine that there is really that much different about the pricey ones to make them worth the extra money.) I can imagine it. For a controller, negotiating USB 3.0 / XHCI protocol with a device is one thing, delivering the expected bandwidth is another. I've toyed around with enough cheap IDE and SATA adapters to know it takes more than a logo on the packaging to get decent throughput. Also, the bus needs to offer enough bandwidth to avoid being a bottleneck. Theoretical maximum speed for USB3 is 5 Gbits/s, that's a bit more than 2 PCIe lanes can sustain, so you'll want an adapter than plugs into a full-sized PCIe connector, unlike the Syba one. Hope this helps, ___ 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: RME audio card user new to FreeBSD
In article 1353768334.2641.21.camel@q you write: Thank you! You're welcome! On Sat, 2012-11-24 at 15:14 +0100, Juergen Lock wrote: Don't want to try 9.1RC3? I thought it would be better to start with something stable as a newbie and now burning already is in progress. Well I don't think there'll be many changes from RC3 to release, and you can use freebsd-update to get to -release after it's out anyway. (I think you can also back it up, but make sure you don't restore the slice table in the mbr too if you add the bsd slice from bsdinstall, only the actual bootcode.) I backup the first 512 bytes: dd if=/dev/sda of=MBR_sda-$BACKUP_NAME_ADD bs=512 count=1 So I should restore from byte 0 to byte 439 only if a restore should be needed? That does sound correct. (tho I haven't verified the exact number 439.) I assume that there's also a way to recover a broken partition table with BSD information if needed and no backup should be available? There is sysutils/scan_ffs in ports tho I didn't have to try it yet. HTH, :) Juergen PS: I have Cc'd the freebsd-questions list as this no longer really is a multimedia topic... (Yes I should have done that earlier, sorry.) ___ 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: Is FreeBSD 9 Production Ready?
Tim Daneliuk tun...@tundraware.com writes: On 11/24/2012 11:19 AM, Lucas B. Cohen wrote: I wouldn't blindly trust and drop an operating system on production servers, no matter how good the feedback from outside my organization sounds. In general, I'd agree with you. Certainly, that's been the case with Linux, AIX, and so on over the years. I have a very small server of my own for the house, and I generally update it to major versions within a few weeks of updating. I think I had it on RELENG_9 within two months of 9.0 being released. As far as I recall, I had very few problems making the jump. But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? I wouldn't use the new toolchain for this server. The old toolchain is still the default anyway. ___ 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: Odd X11 over SSH issue
Paul Kraus p...@kraus-haus.org writes: On Fri, Nov 23, 2012 at 4:31 PM, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Yup, I just have not had a chance to chase that one down, and given that it happens once per SSH session, has not been a high priority. I mentioned it in the spirit of full disclosure. I would chock it up to network slowness, but I do not see the same behavior with Firefox, xload, or xclock. That's not a fair comparison, because tunneling a whole X server involves passing a lot more events than tunneling an application to run on your local server. This is particularly painful because the X protocols are highly serial. The VIrtualBox GUI (not the underlying VM console) should be comparable to Firefox in terms of network load. Yes, xclock and xload are much lower overhead as they are simpler apps. The difference between Firefox (measured at under 10 seconds to open the window) and VirtualBox (measured at 157 seconds to open the window) indicates that _something_ is wrong. Sorry if I was unclear. Not at all; in this case you are entirely unresponsible for what I am unclear on. I was, in fact, thinking of the console. The console is, in fact, what I was thinking of. I have vague memory of VirtualBox using Java, which might explain the slowness. That's more in your area of expertise than mine. I can't back that up, though, so I may be way off. I am running 3 different VMs on this server (soon to be more :-). One is WIn 2008 server as an RDP host for a specific application, the others ar FreeBSD VMs, one for DNS and DHCP, and the other for email / webmail. I manage the underlying Win 2008 instance via RDP (and that is how the end users connect), the two FreeBSD VMs do not run a window manager at all and they are managed via SSH connections. I use the VBoxHeadless executable to run the VMs for production use. Normally I make config changes with the command line tool VBoxManage, but in this case I had a FreeBSD VM that was not booting so I needed the console (and to make various changes to the config). It is running the VBox management GUI on the physical layer server that I am having fits with. If it is a network/protocol issue, ssh makes it harder to troubleshoot. Verbose output from the initiating side might tell you what is happening, although you would probably need to do some log analysis to separate out the different channels. I went back and checked the truss output, and the EAGAIN errors aren't interesting; they just mean there was no input on a non-blocking read from the socket. You also might want to check with the VirtualBox support channels, the freebsd-emulation list, and other obvious suspects. Also, building with a different frontend might make the X connection more lightweight. Is there any particular reason you don't let the X server run remotely and attach to it with something more latency-friendly, like vnc? I would expect that to work vastly better on any OS, just because you get X (specifically, its tendency to head-of-line blocking) out of its own way. The short answer to why X11 via SSH and not VNC for the management is that I have not found a very clean way to have the VNC service running for root without manual intervention to start it. Yes, I know I could script it, but that adds one additional layer that needs to be supported. That makes sense. You shouldn't have to run an X server on the base level system at all. P.S. I did get my VM repaired, very slowly and painfully, but I still need to track down the VBox GUI issue. Being able to clone, import, and export VMs is one of the reasons I use them at all... Be well. ___ 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: Multi-boot Linux + FreeBSD
While no expert, I would advise against running the kernel directly.
The loader allows you to boot in single user which may come handy at times.
On 24 Nov 2012, at 18:08, Lucas B. Cohen l...@bnrlabs.com wrote:
Hi Ralf,
On 2012.11.24 17:06, Ralf Mardorf wrote:
Perhaps later today I'll install 9.0 amd64. If possible I'll keep my
Linux GRUB legacy. Can I use my menu.lst [1] and add a chainloader or
something similar to boot FreeBSD from /dev/sda1?
I don't know if GRUB v1 allows that, on a multiboot system I use GRUB 2
to either load FreeBSD's loader(8) :
menuentry FreeBSD (Loader) {
insmod part_bsd
set root='hd0,msdos2,bsd1'
echo Loading FreeBSD loader
kfreebsd /boot/loader
echo Starting FreeBSD loader
}
or to run its kernel directly, after having passed it optional device hints:
menuentry FreeBSD (Direct Boot) {
insmod ufs2
set root='hd0,msdos2,bsd1'
echo Loading FreeBSD kernel
kfreebsd /boot/kernel/kernel
echo Loading FreeBSD environment
kfreebsd_loadenv /boot/device.hints
set kfreebsd.vfs.root.mountfrom=ufs:/dev/ada0s2
echo Booting FreeBSD
}
I'm not saying it's impossible, but I'm unable to chainload to the
loader code on my system with this:
menuentry FreeBSD (Chainload) {
insmod chain
set root='hd0,msdos2'
chainloader +1
}
FWIW I made backups of my HDD's MBRs.
I wonder if the installer will overwrite the MBR?
Always a good thing to have backups. From what I've experienced and
read, 9.0-RELEASE's installer is not always predictable in that regard,
it's probably safer to assume it'll won't do what you want, and just
restore your MBR after the installation, to go back to using GRUB for
dual-booting.
Here's the pitfall, though: the MBR also holds the partition table. So
make a fresh backup after you've created/reorganized the primary
partitions (slices) on your disk using a tool you're familiar with.
(Logical partitions and BSD partitions are stored differently, so they
will survive an MBR restore, provided it doesn't modify the primary
partition they're contained in.)
I also would like to know, if there's a way to recover the partition
table, including a primary FreeBSD partition/slice, if this ever should
get broken and there should be no backup of the partition table be
available.
The partition table is held alongside the MBR, in the first logical
sector of your disk. Restoring one will restore the other.
For extra safety, you can save the output of partitioning tools like
fdisk or GNU parted expressed in sectors.
Hope this helps,
___
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
Another question about pkgng
When I issue 'pkg version -R' it does not actually use the remote repository for comparison; instead it uses the local cache of the remote repository, i.e. it checks local.sqlite against repo.sqlite. That's fine, but should it not do a 'pkg update' first? ___ 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
I Guess I Don't Understand NFS As Well As I Thought
Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Multi-boot Linux + FreeBSD
Thank you Damien, Lucas and Juergen :) btw. the off topic on multimedia is my bad, I wasn't subscribed to FreeBSD questions. While reading howtos I missed http://www.freebsd.org/doc/faq/disks.html#grub-loader I'll add title FreeBSD 9.0 root (hd0,a) kernel /boot/loader to my menu.lst and then install FreeBSD. Regards, Ralf ___ 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 Guess I Don't Understand NFS As Well As I Thought
On 24 November 2012, at 12:32, Tim Daneliuk wrote: Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. What are the permissions on the directory /usr/foo/bar? ___ 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: Is FreeBSD 9 Production Ready?
On 24/11/2012 16:38, Tim Daneliuk wrote: I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. 9-STABLE works for me. I've run into a few quite minor bugs, but certainly nothing really significant. Stability is rock-solid as ever. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. Upgrading by compiling world+kernel from source is an effective method. Works just as well for 8-9 as for any of the previous upgrades you mention. It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Another question about pkgng
On 24/11/2012 20:28, Walter Hurry wrote: When I issue 'pkg version -R' it does not actually use the remote repository for comparison; instead it uses the local cache of the remote repository, i.e. it checks local.sqlite against repo.sqlite. That's fine, but should it not do a 'pkg update' first? That would be consistent with the way 'pkg upgrade' and 'pkg install' behave, so personally I think that would be a yes. Can you open an issue on Github so this point does not get forgotten please? https://github.com/pkgng/pkgng/issues Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
How to create a partition for FreeBSD 9.0?
I use the amd64 install DVD. With or without deleting, I can't format a bootable FreeBSD partition to ada0s1, aka Linux /dev/sda1. FWIW if I reinstall GRUB legacy to /dev/sda, the boot flag will be set for the extended partition. /dev/sda1 is an empty ext3 partition, size 57.83 GiB. Regards, Ralf PS: spinymouse@q:~$ sudo fdisk -l /dev/sda Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000f2fc6 Device Boot Start End Blocks Id System /dev/sda1 63 12127468460637311 83 Linux /dev/sda2 * 121274746 625137344 251931299+ 5 Extended /dev/sda5 121274748 183751469312383617 HPFS/NTFS/exFAT /dev/sda6 183751533 24642103431334751 83 Linux /dev/sda7 246421098 30928337931431141 83 Linux /dev/sda8 309283443 36196761526342086+ 83 Linux /dev/sda9 361969664 43561779136824064 83 Linux /dev/sda10 435618603 440164934 2273166 82 Linux swap / Solaris /dev/sda11 440164998 56187337460854188+ 83 Linux /dev/sda12 561873438 569215079 3670821 83 Linux /dev/sda13 569215143 61551440923149633+ 83 Linux /dev/sda14 615514473 625137344 4811436 83 Linux spinymouse@q:~$ sudo fdisk -l /dev/sdb Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000525e5 Device Boot Start End Blocks Id System /dev/sdb1 634297387421486906 83 Linux /dev/sdb242973936 976768064 466897064+ 5 Extended /dev/sdb5429739388593168421478873+ 83 Linux /dev/sdb685931748 12869671421382483+ 83 Linux /dev/sdb7 128696778 133789319 2546271 82 Linux swap / Solaris /dev/sdb8 133789383 17594387921077248+ 83 Linux /dev/sdb9 175943943 21919085921623458+ 83 Linux /dev/sdb10 219190923 220211199 510138+ 83 Linux /dev/sdb11 220213248 24668774313237248 83 Linux /dev/sdb12 246689792 34754969550429952 83 Linux /dev/sdb13 347550273 557309951 104879839+ 83 Linux /dev/sdb14 557312000 976766975 209727488 83 Linux spinymouse@q:~$ sudo grub-install /dev/sda Searching for GRUB installation directory ... found: /boot/grub Installing GRUB to /dev/sda as (hd0)... Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (fd0) /dev/fd0 (hd0) /dev/sda (hd1) /dev/sdb ___ 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: Odd X11 over SSH issue
On Fri, Nov 23, 2012 at 6:43 PM, Paul Kraus p...@kraus-haus.org wrote: I am seeing very poor response time running the VitrualBox GUI via X11 tunneled over SSH via the Internet. The issue _appears_ to be limited to the VBox GUI as Firefox is reasonable. I am well aware of the latency issues tunneling X11 over SSH across the Internet, but that is what we are stuck with for the moment. The server is running FreeBSD 9 and is patched as of about 4 weeks ago. I see the same thing. But doing the same thing with CentOS(that is, CentOSis the host that VirtualBox runs on) goes pretty fast. My guess is that it is related to QT. -- chs, ___ 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 Guess I Don't Understand NFS As Well As I Thought
On 11/24/2012 03:25 PM, Doug Hardie wrote: On 24 November 2012, at 12:32, Tim Daneliuk wrote: Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. What are the permissions on the directory /usr/foo/bar? 775 Let me correct something. The files in that directory are owned by root:wheel (not root:root - I got my *nixes confused), but they definitely have 600 perms. On Machine A, user 'myid' is IN the wheel group but I still don't see how he's getting permission to rename the file. ___ 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 -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 03:48 PM, Matthew Seaman wrote: It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. So I am discovering. I moved the system to 9.1-PRE today with a source compile. After I then did a make remove-old, the system started complaining about missing libraries. So ... I temporarily fixed this with appropriate /etc/libmap.conf entires. I am now about to do a portupgrade -aARrvf to redo the ports. We'll see how that goes... -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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 create a partition for FreeBSD 9.0?
On Sat, 24 Nov 2012 23:14:40 +0100, Ralf Mardorf wrote: I use the amd64 install DVD. With or without deleting, I can't format a bootable FreeBSD partition to ada0s1, aka Linux /dev/sda1. You mention ada0s1. This is not a partition. It's called a slice (different term: DOS primary partition). You need to create partitions inside the slice (or one covering the whole slice, typically not recommended). To _format_ a partition (freebsd-ufs GPT, or MBR slice + partitions), newfs is the tool. I know this might sound confusing, taking DOS primary partitions, DOS extended partition and logical volume inside a DOS extended partition into account. Still it's helpful to know the proper BSD terminology for those things, and the understanding of _what_ a partition is (it's a part of a DOS primary partition, so to say - it works like the logical volume inside a DOS extended partition, but without requiring the DOS extended partition). FWIW if I reinstall GRUB legacy to /dev/sda, the boot flag will be set for the extended partition. /dev/sda1 is an empty ext3 partition, size 57.83 GiB. I think it would be better to delete the partition (not empty partition, but then no partition) and let the installer allocate the free space to a slice. Then you shouldn't need to bother with boot flags as you're probably going to chainload per GRUB. When you have created the partition, either by using gpart for the more convenient GPT or MBR approach (gpart supports this mechanism), or by using fdisk for the traditional MBR approach, you can create partitions inside this slice, for example a root partition, a swap partition, and maybe partitions for functional separation of OS and data components, such as /tmp, /var, /usr and /home. You can do this as mentioned with fdisk + bsdlabel (MBR approach) or gpart (GPT approach, but only if this is supported by the rest of your disk organisation). Device Boot Start End Blocks Id System /dev/sda1 63 12127468460637311 83 Linux This is the partition you're going to install FreeBSD to? Good, just delete it and let the installer do the work. :-) You can also switch to manual mode and use the CLI tools to create a slice and partitions. It's not very complicated and should be possible from the Fixit live system (not tested). See this document for details on partitioning preparation and disk initialisation: http://www.wonkity.com/~wblock/docs/html/disksetup.html -- 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: How to create a partition for FreeBSD 9.0?
On Sat, 2012-11-24 at 23:35 +0100, Polytropon wrote: Device Boot Start End Blocks Id System /dev/sda1 63 12127468460637311 83 Linux This is the partition you're going to install FreeBSD to? Good, just delete it and let the installer do the work. :-) Yes, but the install doesn't do it! I can delete it now, instead of trying to delete it with the installer and see if the installer will work then. To be continued ... Thank you, Ralf ___ 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 Guess I Don't Understand NFS As Well As I Thought
On 24 November 2012, at 14:37, Tim Daneliuk wrote: On 11/24/2012 03:25 PM, Doug Hardie wrote: On 24 November 2012, at 12:32, Tim Daneliuk wrote: Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. What are the permissions on the directory /usr/foo/bar? 775 Let me correct something. The files in that directory are owned by root:wheel (not root:root - I got my *nixes confused), but they definitely have 600 perms. On Machine A, user 'myid' is IN the wheel group but I still don't see how he's getting permission to rename the file.\ Renaming a file does not change the file itself. It updates the directory. Any user in group wheel has the authority to write to the directory (e.g., change a file's name). The directory permissions are rwx for group wheel. You can either try a user on machine B who is not in group wheel or change the directory permissions to 755 on /usr/foo/bar. Then it would work as you expect. ___ 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 create a partition for FreeBSD 9.0?
On Sat, 2012-11-24 at 23:35 +0100, Polytropon wrote: You can also switch to manual mode I did this first and it didn't work. Regards, Ralf PS: I very often receive mails two times :(, from the list and directly send to me. I notice that mailing list options for the MUA are broken. Is mailman misconfigured or did I miss something I should take care off? I don't have such issues with other mailing lists. ___ 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 create a partition for FreeBSD 9.0?
On Sun, 25 Nov 2012 00:07:09 +0100, Ralf Mardorf wrote: On Sat, 2012-11-24 at 23:35 +0100, Polytropon wrote: Device Boot Start End Blocks Id System /dev/sda1 63 12127468460637311 83 Linux This is the partition you're going to install FreeBSD to? Good, just delete it and let the installer do the work. :-) Yes, but the install doesn't do it! I can delete it now, instead of trying to delete it with the installer and see if the installer will work then. That sounds good. The installer should be able to detect the free space and assign it to a slice (that can then used to create partitions inside it) or GPT partitions (until the free space is consumed). On Sun, 25 Nov 2012 00:14:49 +0100, Ralf Mardorf wrote: On Sat, 2012-11-24 at 23:35 +0100, Polytropon wrote: You can also switch to manual mode I did this first and it didn't work. I meant the really manual mode (CLI) as to be seen in Fig. 3-10, named Shell (that's why the confusion, sorry). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-partitioning.html I have to admit that I'm not very familiar with the new installer (bsdinstall), I've been occassionally using the old installer (sysinstall) in the past, with less options where one could do something wrong. :-) It's important that you either make sure there is one free slice (means: max. 3 DOS primary partitions are defined, one slot is free), or use GPT (command line tool: gpart). This is what you should be able to do when using the Shell option, even though the guided and manual mode should work. What's exceptional in your case: You have defined a lot of partitions for Linux, maybe this confuses the new installer. :-) You also should decide _which_ partitioning approach works for you - MBR or (probably) GPT. This also depends on how you have organized your Linusi. The use of the CLI tools for this approach are documented in Warren's article I've mentioned in a previous message. PS: I very often receive mails two times :(, from the list and directly send to me. I notice that mailing list options for the MUA are broken. Is mailman misconfigured or did I miss something I should take care off? I don't have such issues with other mailing lists. Sorry, don't mind: This is obviously a problem on _my_ side, the reply all vs. reply to mailing-list. The list system should be working properly; you should receive this message now from the list (as it is intended). I'm just too stupid to use a computer. :-) -- 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: I Guess I Don't Understand NFS As Well As I Thought
On 11/24/2012 05:13 PM, Doug Hardie wrote: On 24 November 2012, at 14:37, Tim Daneliuk wrote: On 11/24/2012 03:25 PM, Doug Hardie wrote: On 24 November 2012, at 12:32, Tim Daneliuk wrote: Can someone kindly explain what is going on here: Machine A: FreeBSD - was running 8, just upgraded to 9.1-PRE (I don't recall seeing the behavior described below in V8, but then, I don't think I ever tried it). Machine B: Linux Mint Desktop - Machine A acts as an NFS server for Machine B. - Machine A exports a particular directory like this: /usr/foo -maproot=myid -network ... - /usr/foo/bar is owned by root on Machine A and has files therein owned as root:root with permissions of 600. - If I access /usr/foo/bar/file1 from Machine B, I cannot read it but - and this is the part I don't get - I CAN *rename* it. What's going on? Since /foo/bar/ is owned by root and everything in it is 600 root:root, I would not expect a remote access to allow things like renaming. Clearly I am missing something here, but I don't get it. What are the permissions on the directory /usr/foo/bar? 775 Let me correct something. The files in that directory are owned by root:wheel (not root:root - I got my *nixes confused), but they definitely have 600 perms. On Machine A, user 'myid' is IN the wheel group but I still don't see how he's getting permission to rename the file.\ Renaming a file does not change the file itself. It updates the directory. Any user in group wheel has the authority to write to the directory (e.g., change a file's name). The directory permissions are rwx for group wheel. You can either try a user on machine B who is not in group wheel or change the directory permissions to 755 on /usr/foo/bar. Then it would work as you expect. D'oh ... of course that's it. Thanks. -- Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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
OT: How to create a partition for FreeBSD 9.0?
On Sun, 2012-11-25 at 00:27 +0100, Polytropon wrote: I'm just too stupid to use a computer. :-) I once wanted to delete a broken Linux, before restoring it from a backup, but by accident deleted the broken Linux + the only backup too. No drugs involved. In around 20 years using computers, I was able to pull off a feat like this for only one time. ___ 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: Is FreeBSD 9 Production Ready?
Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. Irony is now that I am writing you this on a 10.0 machine. Only 10 has had the support I needed for my new toy. 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: Another question about pkgng
On Sat, 24 Nov 2012 21:54:50 +, Matthew Seaman wrote: On 24/11/2012 20:28, Walter Hurry wrote: When I issue 'pkg version -R' it does not actually use the remote repository for comparison; instead it uses the local cache of the remote repository, i.e. it checks local.sqlite against repo.sqlite. That's fine, but should it not do a 'pkg update' first? That would be consistent with the way 'pkg upgrade' and 'pkg install' behave, so personally I think that would be a yes. Can you open an issue on Github so this point does not get forgotten please? https://github.com/pkgng/pkgng/issues Thanks, Matthew. Done - Issue #396 ___ 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: Is FreeBSD 9 Production Ready?
On 25/11/2012 04:06, Tim Daneliuk wrote: But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? If you want to build with clang wait for 9.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=threads/165173 I have been running 9.0 built with clang for most of the year as my desktop machine without any other issues. As far as your make.conf goes that will depend on what you have in there. Most gcc flags will either work or be ignored. ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 05:58 PM, Erich Dollansky wrote: Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? That's exactly what I don't want to do. I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. I used to take this approach. However, I discovered the pain of fixing a configuration that jumped several major releases was way higher than tracking them each as they became stable. I did the 9.1-PRE upgrade today and - once the new system was compiled and ready to be installed - had only very minor conversion issues. In my case, the most painful part of conversion is the mail infrastructure. The server in question is the domain's mail server and it has a LOT of moving parts with custom configurations: sendmail, greylisting, mailscanner, spam assassin, mailman, SASL ... That is pretty much always what breaks. Doing smaller leaps tends to make this more tractable to control. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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: Another question about pkgng
- Sent via BlackBerry from Thai Citrus -Original Message- From: Walter Hurry walterhu...@gmail.com Sender: owner-freebsd-questions@freebsd.orgDate: Sun, 25 Nov 2012 00:02:51 To: freebsd-questions@freebsd.org Subject: Re: Another question about pkgng On Sat, 24 Nov 2012 21:54:50 +, Matthew Seaman wrote: On 24/11/2012 20:28, Walter Hurry wrote: When I issue 'pkg version -R' it does not actually use the remote repository for comparison; instead it uses the local cache of the remote repository, i.e. it checks local.sqlite against repo.sqlite. That's fine, but should it not do a 'pkg update' first? That would be consistent with the way 'pkg upgrade' and 'pkg install' behave, so personally I think that would be a yes. Can you open an issue on Github so this point does not get forgotten please? https://github.com/pkgng/pkgng/issues Thanks, Matthew. Done - Issue #396 ___ 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: Is FreeBSD 9 Production Ready?
On 11/24/2012 06:16 PM, Shane Ambler wrote: On 25/11/2012 04:06, Tim Daneliuk wrote: But I have had essentially no problems doing in-place major rev updates with FreeBSD thus far. The only breakage I am worried about now is whether the new compiler change breaks things that used to work just fine. For example, will my make.conf settings be properly observed by the new tool chain? If you want to build with clang wait for 9.1 http://www.freebsd.org/cgi/query-pr.cgi?pr=threads/165173 I plan to stay conservative and only switch to clang when it is THE way to build everything. i.e., When GCC is finally retired for use in the base OS. Tim Daneliuk tun...@tundraware.com PGP Key: http://www.tundraware.com/PGP/ ___ 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 create a partition for FreeBSD 9.0?
On Sun, 2012-11-25 at 00:27 +0100, Polytropon wrote: I meant the really manual mode (CLI) as to be seen in Fig. 3-10, named Shell (that's why the confusion, sorry). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-partitioning.html Manually Create Partitions doesn't work. The MD5sum for the ISO was ok and the burned DVD was verified. I did not test Shell until now and it's to late to search and read a howto. When startup finished I push enter Install keyboard: German ISO-8859-1 hostname: freebsd [*] doc, games, lib32, ports, src Guided Partitioning Select the disk on which to install FreeBSD: ada0 Partition (not Entire Disk) Continuing doesn't work, or I don't know what to do. FWIW, I'll use MBR and if possible / only. Regards, Ralf ___ 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 create a partition for FreeBSD 9.0?
On Sun, 2012-11-25 at 02:34 +0100, Ralf Mardorf wrote: On Sun, 2012-11-25 at 00:27 +0100, Polytropon wrote: I meant the really manual mode (CLI) as to be seen in Fig. 3-10, named Shell (that's why the confusion, sorry). PS: Don't worry, it was clear what you wanted to say. As a newbie regarding to this kind of partitioning, I just prefer to test the ncurses way first. ___ 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: Is FreeBSD 9 Production Ready?
On Sat, 24 Nov 2012, Tim Daneliuk wrote: On 11/24/2012 03:48 PM, Matthew Seaman wrote: It is not however sufficient to get you a completely upgraded system: you will still have to re-install all of your ports. Otherwise, as you end up trying to upgrade ports by ones and twos over time, you'll end up with a complete rat's nest of contradictory shared library dependencies and programs crashing left, right and centre. So I am discovering. I moved the system to 9.1-PRE today with a source compile. After I then did a make remove-old, the system started complaining about missing libraries. So ... I temporarily fixed this with appropriate /etc/libmap.conf entires. I am now about to do a portupgrade -aARrvf to redo the ports. We'll see how that goes... portupgrade -avf is equivalent (-r and -R are redundant with -a). Including -c helps to get the config screens out of the way up front. ___ 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: Is FreeBSD 9 Production Ready?
--On November 24, 2012 10:38:35 AM -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). I am contemplating moving to the FBSD 9 family. Is this branch ready for production or should I wait a while yet? I ordinarily avoid x.0 releases of anything and I know 9.1 is soon going to be with us. In a related note, if I do move to 9.x is it sufficient to grab the appropriate source tree and compile world and kernels, install and reboot? That is, it is reasonable to do an in-place upgrade. This is how I migrated 4-6, 6-7, and 7-8 and I am hoping this is till the case since a complete reinstall is painful and slow. I upgraded to 9 on a server that is basically doing what yours is. I used freebsd-update and it did all the right things no problems. Been running on 9 without any issues pretty much since it came out. However, the only thing remotely fancy I'm doing is running root ZFS and link aggregation on my NIC's. ___ 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 create a partition for FreeBSD 9.0?
On Sat, 24 Nov 2012, Ralf Mardorf wrote: I use the amd64 install DVD. With or without deleting, I can't format a bootable FreeBSD partition to ada0s1, aka Linux /dev/sda1. FWIW if I reinstall GRUB legacy to /dev/sda, the boot flag will be set for the extended partition. /dev/sda1 is an empty ext3 partition, size 57.83 GiB. Delete it, or set it to type 0xa5. I think the first is probably better for bsdinstall to see it as available. Expect boot loaders to be overwritten, so make a backup, preferably of everything. ___ 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: Is FreeBSD 9 Production Ready?
On 24 November 2012, at 16:36, Tim Daneliuk wrote: On 11/24/2012 05:58 PM, Erich Dollansky wrote: Hi, On Sat, 24 Nov 2012 10:38:35 -0600 Tim Daneliuk tun...@tundraware.com wrote: I am currently running FBSD 8.3-STABLE on a production server that provides http, dns, smtp, and so on for a small domain. This is not a high arrival rate environment but it does need to be rock solid (which FBSD 4-8 have been). why would you like to break a running system? That's exactly what I don't want to do. I am contemplating moving to the FBSD 9 family. Is this branch ready I would stay with 8.x until the end of its support and move only then to a new branch. It could be then 9.x or 10.y. I would then - but only then - prefer the 10.y branch. I retired my 7.4 only because of lightning strike this spring. Robustness is my main goal here. Any change which brings only the risk is avoided. I used to take this approach. However, I discovered the pain of fixing a configuration that jumped several major releases was way higher than tracking them each as they became stable. I did the 9.1-PRE upgrade today and - once the new system was compiled and ready to be installed - had only very minor conversion issues. In my case, the most painful part of conversion is the mail infrastructure. The server in question is the domain's mail server and it has a LOT of moving parts with custom configurations: sendmail, greylisting, mailscanner, spam assassin, mailman, SASL ... That is pretty much always what breaks. Doing smaller leaps tends to make this more tractable to control. I am in a similar situation. Reliability is more important than anything else. I run similar mail configurations on one server, although I use different machines for incoming and outgoing mail. Jumps across versions have been more difficult. I have kept records of the steps I used for each upgrade and theose help me prepare for the next one. I am in the middle of jumping from 7.2 to 9.1. One machine is completely converted and working just fine. I had reliability problems with 9.0. It kept rebooting or crashing every few days. I am on 9.1-RC2 at the moment and its been up and working for 34 days now. I will upgrade it to 9.1 when its released. This one had to be upgraded early because it was new hardware. The old machine completely died. I have another server also running 9.1-RC2 but it is not moved into production yet. It is primarily a news server and has a large news cache that has to be moved. I am waiting for 9.1 for that. On some of my test machines I have found that 9.1 is the first release to support the built-in wireless NICs. The service command is really helpful. I frequently can't remember which service is in etc and which in /usr/local/etc. The largest problem I encountered in the upgrade was the disk structure. My disks were setup when using FreeBSD 3.5/3.7. As a result, the root partition is way too small today. I was able to shoe horn 7.2 in by deleting the kernel symbol files while they were being installed. 9.0/9.1 just didn't fit at all. Restructuring the disks is a time consuming job and fairly error prone in getting everything back that is needed to run production. There is also the issue that the default formatting uses SU+J which is not compatible with dump live filesystems. Now I am going to have to find the time to bring the systems down to remove journaling with no one on-site who has a clue what they are doing. I currently have 9.1-RCx running on 5 systems and have not had any stability issues with it. One system is in production but the others are lightly used. One of them is a 200 MHz machine with either 32 Meg or 64 Meg memory. It seems to be faster then when it ran 8.2 but I haven't actually done any measurements. ___ 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
