Re: [FreeBSD Questions] Filesystem image as root
--- On Sun, 11/15/09, CyberLeo Kitsana wrote: > James Phillips wrote: > >> Date: Sat, 14 Nov 2009 20:29:59 -0600 > >> From: CyberLeo Kitsana > >> Subject: [FreeBSD Questions] Filesystem image as > root > >> > >> The single IDE connector is accessible via the > legacy ISA > >> ports, and is > >> thus limited to PIO modes (about 1.6MB/sec max, > even with > >> an actual hard > >> drive instead of a CF card). > > > > You are off by an order of magnitude (base 2 or 10): > > Pio mode 0 is ~3.3 MB/s > > Pio mode 4 is ~16.7 MB/s > > > > http://www.pcguide.com/ref/hdd/if/ide/modesPIO-c.html > > > > You can probably set PIO mode 4 for with: > > # atacontrol mode ad0 PIO4 > > If only that were true in this case. > > (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 > current mode = PIO2 > (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 > current mode = PIO2 > (85eef1f3)[r...@ss4200 ~]# dd if=/dev/ad0 of=/dev/null > bs=4096 count=4096 > 4096+0 records in > 4096+0 records out > 16777216 bytes transferred in 10.111748 secs (1659181 > bytes/sec) > > Nothing I've tried seems to boost the throughput, hence the > desire to > use a compressed cached filesystem image. > > Thanks for the suggestions, though! Ouch! I thought the laptop I was "fixing" last week was bad: running Vista with a 10MB/s transfer rate :P The drive in my Pentium 166 gets 11-12MB/s. I actually looked up both the PIO modes: http://en.wikipedia.org/wiki/Programmed_input/output And the spec sheet (assuming Tom's hardware was wrong) before composing my original reply: Intel® Entry Storage System SS4200-E Technical product specification [PDF] http://download.intel.com/support/motherboards/server/ss4200-e/sb/ss4200e_tps_11.pdf I noted that the ATA port is not listed as a feature, which is not a good sign. It does appear in the block-diagram labeled:DOM Glossary definition: Disk On Module If I had to guess: Intel did something "weird" or "non-standard" to the port, so the standard BSD driver does not work properly. Have you read the ata(4) manual page? The following /boot/device.hints are suggested for ISA: hint.ata.0.at="isa" hint.ata.0.port="0x1f0" hint.ata.0.irq="14" . . . port '1' probably not needed I had a thought: it could just as easily be "pc98" if they don't intend for you to touch the "firmware." The firmware has source code available under a GPL license. EMCLifeLineOEMSW-1.0-GPLComponents.tar.gz Ver:1.0 Date:9/24/2009 Size:125585 (KB) EMCLifeLineOEMSW-1.1-GPLComponents.tar.gz Ver:1.1 Date:9/24/2009 Size:244406 (KB) If you are worried about license contamination, you may have to get somebody to look through that and document any changes (to the ATA interface). Hopefully it is based on a well-know code-base like Linux and the "diff" utility can be used. Of course, the term "components" implies they only expose a HAL of some kind. Regards, James Phillips PS:"# atacontrol mode ad0" will simply print out the current mode. __ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! at http://downloads.yahoo.com/ca/internetexplorer/ ___ 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 Questions] Filesystem image as root
James Phillips wrote: > > --- On Sun, 11/15/09, CyberLeo Kitsana wrote: >> James Phillips wrote: Date: Sat, 14 Nov 2009 20:29:59 -0600 From: CyberLeo Kitsana Subject: [FreeBSD Questions] Filesystem image as >> root The single IDE connector is accessible via the >> legacy ISA ports, and is thus limited to PIO modes (about 1.6MB/sec max, >> even with an actual hard drive instead of a CF card). >>> You are off by an order of magnitude (base 2 or 10): >>> Pio mode 0 is ~3.3 MB/s >>> Pio mode 4 is ~16.7 MB/s >>> >>> http://www.pcguide.com/ref/hdd/if/ide/modesPIO-c.html >>> >>> You can probably set PIO mode 4 for with: >>> # atacontrol mode ad0 PIO4 >> If only that were true in this case. >> >> (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 >> current mode = PIO2 >> (85eef1f3)[r...@ss4200 ~]# atacontrol mode ad0 PIO4 >> current mode = PIO2 >> (85eef1f3)[r...@ss4200 ~]# dd if=/dev/ad0 of=/dev/null >> bs=4096 count=4096 >> 4096+0 records in >> 4096+0 records out >> 16777216 bytes transferred in 10.111748 secs (1659181 >> bytes/sec) >> >> Nothing I've tried seems to boost the throughput, hence the >> desire to >> use a compressed cached filesystem image. >> >> Thanks for the suggestions, though! > Ouch! > > I thought the laptop I was "fixing" last week was bad: running Vista with a > 10MB/s transfer rate :P > > The drive in my Pentium 166 gets 11-12MB/s. > > I actually looked up both the PIO modes: > http://en.wikipedia.org/wiki/Programmed_input/output > > And the spec sheet (assuming Tom's hardware was wrong) before composing my > original reply: > Intel® Entry Storage System SS4200-E > Technical product specification [PDF] > http://download.intel.com/support/motherboards/server/ss4200-e/sb/ss4200e_tps_11.pdf > > I noted that the ATA port is not listed as a feature, which is not a good > sign. It does appear in the block-diagram labeled:DOM > Glossary definition: Disk On Module The model I have is the SS-4200EHW. Identical, save the lack of a DOM and firmware. And price. > If I had to guess: Intel did something "weird" or "non-standard" to the port, > so the standard BSD driver does not work properly. > Have you read the ata(4) manual page? > The following /boot/device.hints are suggested for ISA: > hint.ata.0.at="isa" > hint.ata.0.port="0x1f0" > hint.ata.0.irq="14" This is actually how I got the amd64 build to recognize the port. These lines were present in x86, but missing in amd64 device.hints. > . . . port '1' probably not needed > I had a thought: it could just as easily be "pc98" if they don't intend for > you to touch the "firmware." Hm. This might be something to look into. > The firmware has source code available under a GPL license. > EMCLifeLineOEMSW-1.0-GPLComponents.tar.gz > Ver:1.0 Date:9/24/2009 Size:125585 (KB) > > EMCLifeLineOEMSW-1.1-GPLComponents.tar.gz > Ver:1.1 Date:9/24/2009 Size:244406 (KB) I checked previously, and Linux has the same limitations. The port is recognized as a legacy ISA IDE port by the ide-generic driver, and maxes out at a ludicrously low throughput. The official firmware gets around this by preloading filesystems into RAM. > If you are worried about license contamination, you may have to get somebody > to look through that and document any changes (to the ATA interface). > Hopefully it is based on a well-know code-base like Linux and the "diff" > utility can be used. > > Of course, the term "components" implies they only expose a HAL of some kind. > > Regards, > > James Phillips > > PS:"# atacontrol mode ad0" will simply print out the current mode. -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.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"
NFS and crossmount
Hi All ! I'm chaning fileserver to a FreeBSD 7.2 from my old linux and can't find how to define the option "crossmnt" (crossmount) for NFS. Does anyone know if it's supported under FreeBSD 7 and if so, how to define it ? Thanks //paus ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Sun, 15 Nov 2009 21:18:36 -0700 (MST) Warren Block replied: >On Mon, 16 Nov 2009, Polytropon wrote: > >> On Mon, 16 Nov 2009 02:21:28 +0200, Manolis Kiagias >> wrote: >>> Just the fact that I now have to edit an xml file to simply add a >>> Greek keyboard layout is annoying enough. >> >> The fact that annoys me is that configuration seems to have >> disassembled into several parts that are not located in a >> central file (such as xorg.conf has been); I have no problem >> with editing text files if I need to, but now it's getting >> somewhat complicated - I'm not confortable with the fact that >> FreeBSD is (getting) complicated, I always loved it because >> everything is so simple. > >But xorg is not FreeBSD, so this is an unreasonable statement. >FreeBSD is simple. X has never been particularly simple, and the fact >that complexity grows over time is nothing new, either. > >> But I am not complaining! :-) I've been told that those changes >> are absolutely needed to design the creation of new software >> more efficiently and cheaper; this is often confused with "bloat", >> but it's not, it's evolution! And there's no way around. > >Of course there is: if you're happy with the state of your software, >stop there! Don't upgrade. Don't replace what's working with >something newer. > >That option is usually more difficult than it initially seems. The >rest of the world tends to keep on evolving. > >> I would be more happy if things would really get better, or >> even not worse, but sadly, they seem to. Software gets slower >> as well as less accessible - Gtk 2, used by many programs, is >> a good (bad) example. Am I supposed to buy new computer to replace >> perfectly running systems just to keep the "overall usage speed" >> of everything at the same level? > >As above, you don't *have* to upgrade. Keep the old software, and the >old hardware will run it. > >Like everybody, I grumble about changes that don't seem to improve >things at the user level. But I try to remember that without change, >nothing can improve. > >It's also worth remembering that open source projects like xorg give >the users the rare privilege of being able to make a difference. Test >code, provide hardware, document bugs or fixes, do or fund development. If that were true, it might be worth noting. Unfortunately, it rarely works like that. I recently started using a Logitech wireless mouse/keyboard. Of course the mouse did not work in "X", although it performed fine outside of "X". After investing valuable time in Googling for a solution, I ended up editing files for HAL and adding Section "ServerFlags" Option "AllowEmptyInput" "OFF" EndSection to the 'xorg.conf' file. Honestly, that is not acceptable. On every Windows and MAC system I tested, the combo works without this garbage. It just works. No drivers to install, unless I want the extended capabilities of the keyboard/mouse. Why does it have to be so freak-in difficult here. How the hell are we suppose to entice potential users to non Window's platforms when a simple thing like adding a keyboard or mouse to a system becomes a challenge. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Do unto others before they undo you. ___ 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"
LinkedIn Messages, 11/16/2009
LinkedIn REMINDERS: Invitation Reminders: * View Invitation from lokesh bevara http://www.linkedin.com/e/1o3bCy0npDqyzD3wjrAbLV0nLmqMr8R-MulSGyDnb3nr/blk/I1518943135_2/39vdjcNcPgVe34RckALqnpPbOYWrSlI/svi/ PENDING MESSAGES: There are a total of 66 messages awaiting your response. Visit your InBox now: http://www.linkedin.com/e/1o3bCy0npDqyzD3wjrAbLV0nLmqMr8R-MulSGyDnb3nr/inb/ -- Don't want to receive email notifications? Adjust your message settings: https://www.linkedin.com/e/1o3bCy0npDqyzD3wjrAbLV0nLmqMr8R-MulSGyDnb3nr/prv/ LinkedIn values your privacy. At no time has LinkedIn made your email address available to any other LinkedIn user without your permission. (c) 2009, LinkedIn Corporation. ___ 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: Partition naming, fstab, and geli
On Sun, Nov 15, 2009 at 07:23:15PM -0700, David Allen wrote: > Say I have performed a standard installation of FreeBSD onto a single IDE > drive with the following entries in /etc/fstab: > > /dev/ad0s1b none swap sw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1d /var ufs rw 2 2 > /dev/ad0s1e /tmp ufs rw 2 2 > /dev/ad0s1f /usr ufs rw 2 2 > > Then I added more drives. > > 1. The Handbook suggests there is a convention that when partitioning a a > drive that's been added, to label the first new partition on that drive as > 'e' as opposed to 'a' (which is reserved for the /root partition). Does > the following satisfy that convention, or would starting with 'a' in each > case make more sense? It really doesn't matter. Just don't use 'c' and I usually skip using 'b' and even often use it for a little additional swap. But, just pick a habit that works for you and stick with it. > > /dev/ad1e /foo1 ufs rw 2 2 > /dev/ad1f /bar1 ufs rw 2 2 > /dev/ad1g /baz1 ufs rw 2 2 > > /dev/ad2e /foo2 ufs rw 2 2 > /dev/ad2f /bar2 ufs rw 2 2 > > /dev/ad3e /foo3 ufs rw 2 2 > /dev/ad3f /bar3 ufs rw 2 2 > > 2. My second question is in regards to using the 'xx' fstype to have the > system ignore that device. Leave the fstype alone. Use the noauto option. Probably set dump and pass to 0 also. So, for example, if you do not want it to try and mount /dev/ad3f at boot time, the line would look like: /dev/ad3f /bar3 ufs rw,noauto 0 0 > > Consider, for example, a geli encrypted partition. The .eli device > doesn't exist at boot time. I discovered by accident that the system > won't boot with an fstab entry for a device that doesn't exist. So if I > was to record an entry in fstab, I couldn't use > > /dev/ad1e.eli /home/david/private ufs rw 0 0 > > Does that mean that the following is what's typically to record fstab > entries for ignored devices? > > /dev/ad1e.eli /home/david/private xx rw 0 0 > /dev/ad3e /fakexx rw 0 0 > /dev/ad3f /reservedxx rw 0 0 > > Thanks. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Partition naming, fstab, and geli
On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: > 2. My second question is in regards to using the 'xx' fstype to have > the system ignore that device. > > Consider, for example, a geli encrypted partition. The .eli device > doesn't exist at boot time. I discovered by accident that the system > won't boot with an fstab entry for a device that doesn't exist. So > if I was to record an entry in fstab, I couldn't use > > /dev/ad1e.eli /home/david/private ufs rw 0 0 > geli partitions can exist at mount time, but you either have to be present at the console to type-in the pass-phrase or configure it to use a passfile. If you attach your geli-partitions manually then you can either set the fstab entries to noauto, or omit them altogether. ___ 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"
ZFS Snaphost & Hardware RAID
Hello all. I plan to set up backup server with 24x1Tb HDD and use ZFS with FreeBSD-8.0 on it. I prefare to have "ZFS only" system but as I see there is no any easy way to do so. I would like to use ZFS snapshots - is I undestand right what snaphots work OVER ZFS raidz\storage? So I can`t use hardware RAID and must make a raidz? I would love to head any other suggestion about using FreeBSD with ZFS as backup server. -- Best regards, Proskurin Kirill ___ 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: ZFS Snaphost & Hardware RAID
>Hello all. >I plan to set up backup server with 24x1Tb HDD and use ZFS with >FreeBSD-8.0 on it. >I prefare to have "ZFS only" system but as I see there is no any easy >way to do so. >I would like to use ZFS snapshots - is I undestand right what snaphots >work OVER ZFS raidz\storage? So I can`t use hardware RAID and must make >a raidz? >I would love to head any other suggestion about using FreeBSD with ZFS >as backup server. >-- >Best regards, >Proskurin Kirill An option is reading this thread on the FreeBSD forums. http://forums.freebsd.org/showthread.php?t=3689 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"
Virtual box to do cross-browser testing
Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am looking for a way to run virtual Windows machines to do cross-browser testing... Don't need sound card or anything complex... if I can get it working good enough to have access to IE 6, 7, and 8 (with 3 different virtual boxes, probably), that would be enough for me. But before I jump through the hoops of setting up a new FreeBSD box and setting up this virtual box software, I'd like to hear how others have fared with this software. Any experience, much appreciated. -- John ___ 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: Partition naming, fstab, and geli
In freebsd-questions Digest, Vol 285, Issue 2, Message 2 On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: > Say I have performed a standard installation of FreeBSD onto a single IDE > drive with the following entries in /etc/fstab: > > /dev/ad0s1b none swap sw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1d /var ufs rw 2 2 > /dev/ad0s1e /tmp ufs rw 2 2 > /dev/ad0s1f /usr ufs rw 2 2 > > Then I added more drives. > > 1. The Handbook suggests there is a convention that when partitioning a a > drive that's been added, to label the first new partition on that drive as > 'e' as opposed to 'a' (which is reserved for the /root partition). Does > the following satisfy that convention, or would starting with 'a' in each > case make more sense? > > /dev/ad1e /foo1 ufs rw 2 2 > /dev/ad1f /bar1 ufs rw 2 2 > /dev/ad1g /baz1 ufs rw 2 2 > > /dev/ad2e /foo2 ufs rw 2 2 > /dev/ad2f /bar2 ufs rw 2 2 > > /dev/ad3e /foo3 ufs rw 2 2 > /dev/ad3f /bar3 ufs rw 2 2 If you added these with sysinstall (or sade) it will tend to choose 'd' for the first partition on other than the / partition (which is named 'a' on install). Or at least, it's always started with 'd' for me :) But if you're doing it manually starting with 'e' is fine. I suspect the handbook section you quoted to Polytropon later is more an example than definitive. You can happily mount an 'a' partition from another drive that was once a system disk; it's more of a convention really. > 2. My second question is in regards to using the 'xx' fstype to have the > system ignore that device. > > Consider, for example, a geli encrypted partition. The .eli device > doesn't exist at boot time. I discovered by accident that the system > won't boot with an fstab entry for a device that doesn't exist. So if I > was to record an entry in fstab, I couldn't use > > /dev/ad1e.eli /home/david/private ufs rw 0 0 > > Does that mean that the following is what's typically to record fstab > entries for ignored devices? > > /dev/ad1e.eli /home/david/private xx rw 0 0 > /dev/ad3e /fakexx rw 0 0 > /dev/ad3f /reservedxx rw 0 0 Yes. Here I must differ with Polytropon, though your format for the options isn't perhaps quite right. From an old fstab here: # DeviceMountpoint FStype Options DumpPass# /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdosfs ro,noauto 0 0 /dev/ad0s2b noneswapsw 0 0 /dev/ad0s2a / ufs rw 1 1 /dev/ad0s2d /varufs rw,noatime 2 2 /dev/ad0s2e /usrufs rw,noatime 2 2 /dev/ad0s4d /paqi4.5ufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 3 /dev/ad0s4e /paqi4.5/varufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 /dev/ad0s4f /paqi4.5/usrufs ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 # 25Apr06 ext 20Gb USB disk. DON'T autoadd these, deadly if da0 absent! # .. xx fsopts, everything incl fsck must ignore .. /dev/da0s3d /usbdsk ufs xx,noauto,nosymfollow 3 3 /dev/da0s3e /usbdsk/var ufs xx,noauto,nosymfollow 4 4 /dev/da0s3f /usbdsk/usr ufs xx,noauto,nosymfollow 4 4 # 26May06 shintaro 1G flashdrive .. just doc, can't mount using these .. /dev/da0s1 /flash/dos msdosfs xx,noauto 0 0 /dev/da0s2d /flash/ufs ufs xx,noauto,noatime 3 3 /dev/da0s3d /flash/pvt ufs xx,noauto,noatime 3 3 As you say they're useful for doc, and not hard to edit into action. Note the additions above were assigned starting at 'd' by sysinstall. cheers, Ian ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009, Jerry wrote: On Sun, 15 Nov 2009 21:18:36 -0700 (MST) Warren Block replied: It's also worth remembering that open source projects like xorg give the users the rare privilege of being able to make a difference. Test code, provide hardware, document bugs or fixes, do or fund development. If that were true, it might be worth noting. Unfortunately, it rarely works like that. I recently started using a Logitech wireless mouse/keyboard. Of course the mouse did not work in "X", although it performed fine outside of "X". After investing valuable time in Googling for a solution, I ended up editing files for HAL and adding Section "ServerFlags" Option "AllowEmptyInput" "OFF" EndSection to the 'xorg.conf' file. It appears the thread has mutated from "it's unpleasant when X changes" to "why doesn't xorg support my hardware?" Which are at opposite ends of the spectrum. Honestly, that is not acceptable. Evidently no one has been in the position to fix the problem. The opportunity is there, as I was saying above. Certainly there have been reports of problems with wireless keyboard/mouse of several brands; maybe a slightly different protocol with the wireless versions. Whether the problem is with hal or xorg-server or the keyboard and mouse drivers or USB or some interaction, I don't know. You have the hardware; how about doing some research to help improve this? Just knowing what causes the problem would be a long way towards a real solution. On every Windows and MAC system I tested, the combo works without this garbage. It just works. No drivers to install, unless I want the extended capabilities of the keyboard/mouse. Why does it have to be so freak-in difficult here. Because the number of people using xorg are so small in relation to Windows and OS X. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Virtual box to do cross-browser testing
John Almberg a écrit : Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am looking for a way to run virtual Windows machines to do cross-browser testing... Don't need sound card or anything complex... if I can get it working good enough to have access to IE 6, 7, and 8 (with 3 different virtual boxes, probably), that would be enough for me. But before I jump through the hoops of setting up a new FreeBSD box and setting up this virtual box software, I'd like to hear how others have fared with this software. Any experience, much appreciated. -- John ___ 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" It seems that VirtualBox still has problems, according to the FreeBSD wiki : http://wiki.freebsd.org/VirtualBox Maybe you should try qemu instead, as it seems much more stable now : http://wiki.freebsd.org/qemu I used qemu to virtualize Windows Server 2003 some time ago (on Gentoo and Mandriva boxes), and it was working (as long as you consider that a Windows system "works"). Julien Gormotte This message was sent using IMP, the Internet Messaging Program. ___ 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: Virtual box to do cross-browser testing
On Mon, Nov 16, 2009 at 10:02 AM, John Almberg wrote: > Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am looking > for a way to run virtual Windows machines to do cross-browser testing... > > Don't need sound card or anything complex... if I can get it working good > enough to have access to IE 6, 7, and 8 (with 3 different virtual boxes, > probably), that would be enough for me. > > But before I jump through the hoops of setting up a new FreeBSD box and > setting up this virtual box software, I'd like to hear how others have fared > with this software. > > Any experience, much appreciated. > > -- John > > VirtualBox overall works great for me on both i386 and amd64, much faster than qemu. Just following http://wiki.freebsd.org/VirtualBox if you fun into problems. -- Adam Vande More ___ 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: Virtual box to do cross-browser testing
John Almberg wrote: > > Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am > looking for a way to run virtual Windows machines to do cross-browser > testing... > > Don't need sound card or anything complex... if I can get it working > good enough to have access to IE 6, 7, and 8 (with 3 different virtual > boxes, probably), that would be enough for me. > > But before I jump through the hoops of setting up a new FreeBSD box and > setting up this virtual box software, I'd like to hear how others have > fared with this software. > > Any experience, much appreciated. I've been using it for several months. Older versions were a bit fussy, but the latest seems to be really solid. The only problem I have with it is that high graphic usage will basically steal the VM away from the user (i.e. if I run a video inside a vbox machine, I can't access the mouse until the video is done running). Been running Windows WP inside a Virtual Box on FreeBSD 7. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Virtual box to do cross-browser testing
On Mon, Nov 16, 2009 at 11:02:59AM -0500, John Almberg wrote: > Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am > looking for a way to run virtual Windows machines to do cross-browser > testing... I've been using it to do some .NET programming, and it's been pretty good. No major problem, aside from the lack of CPU cycles the odd time or so. -- Jonathan Chen -- The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Am Sun, 15 Nov 2009 15:19:29 -0800 schrieb "Ronald F. Guilmette" : > I _did_ go and read the Handbook section that Manolis Kiagias > kindly posted a link to, and I have now tried _both_ of the two > ways described there to re-enable CNTL-ALT-BACKSPACE functionality > for the X server, and sadly I must report that for me, at least > _neither_ of those methods worked Put the following to your xorg.conf: Section "ServerFlags" Option "DontZap" "off" Option "AllowEmptyInput" "off" Option "AutoAddDevices" "off" EndSection Section "InputDevice" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection This works for me very reliable (xorg-7.4_2). HTH ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Philipp Lengemann wrote: > Am Sun, 15 Nov 2009 15:19:29 -0800 > schrieb "Ronald F. Guilmette" : > > >> I _did_ go and read the Handbook section that Manolis Kiagias >> kindly posted a link to, and I have now tried _both_ of the two >> ways described there to re-enable CNTL-ALT-BACKSPACE functionality >> for the X server, and sadly I must report that for me, at least >> _neither_ of those methods worked >> > > > Put the following to your xorg.conf: > > > Section "ServerFlags" > Option "DontZap" "off" > Option "AllowEmptyInput" "off" > Option "AutoAddDevices" "off" > EndSection > > Section "InputDevice" > Option "XkbOptions" "terminate:ctrl_alt_bksp" > EndSection > > > This works for me very reliable (xorg-7.4_2). > > If you stick with HAL however (using "AllowEmptyInput" bypasses the autodetection), you can just use the policy file in the Handbook and just add the "DontZap" option in "ServerFlags" or "ServerLayout" section. In fact, I've just written a patch for the Handbook that adds this information and will be committed soon. In the meantime, you can view it here: http://www.freebsdgr.org/handbook-mine/x-config.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Partition naming, fstab, and geli
On Tue, Nov 17, 2009 at 03:04:27AM +1100, Ian Smith wrote: > In freebsd-questions Digest, Vol 285, Issue 2, Message 2 > On Sun, 15 Nov 2009 19:23:15 -0700 David Allen wrote: > > > Say I have performed a standard installation of FreeBSD onto a single IDE > > drive with the following entries in /etc/fstab: > > > > /dev/ad0s1b none swap sw 0 0 > > /dev/ad0s1a / ufs rw 1 1 > > /dev/ad0s1d /var ufs rw 2 2 > > /dev/ad0s1e /tmp ufs rw 2 2 > > /dev/ad0s1f /usr ufs rw 2 2 > > > > Then I added more drives. > > > > 1. The Handbook suggests there is a convention that when partitioning a a > > drive that's been added, to label the first new partition on that drive as > > 'e' as opposed to 'a' (which is reserved for the /root partition). Does > > the following satisfy that convention, or would starting with 'a' in each > > case make more sense? > > > > /dev/ad1e /foo1 ufs rw 2 2 > > /dev/ad1f /bar1 ufs rw 2 2 > > /dev/ad1g /baz1 ufs rw 2 2 > > > > /dev/ad2e /foo2 ufs rw 2 2 > > /dev/ad2f /bar2 ufs rw 2 2 > > > > /dev/ad3e /foo3 ufs rw 2 2 > > /dev/ad3f /bar3 ufs rw 2 2 > > If you added these with sysinstall (or sade) it will tend to choose 'd' > for the first partition on other than the / partition (which is named > 'a' on install). Or at least, it's always started with 'd' for me :) Generally, using 'a' for root is needed if the slice is a device and root (/) will be there. But, probably because of that, the tradition of reserving 'a' is strong enough that many people and some utilities just do it that way unless specifically directed otherwise. But, if it is a second (third, fourth, etc) slice/drive that will not have a root partition, it doesn't actually matter. I tend to use 'a' if the drive will be entirely one slice and one partition used for some special work or scratch space, but stick with 'd..h' if there will be more than one partition and just leave 'a' alone - for no other reason than habit. As for 'd' vs 'e', sometime a long time and many generations ago there was a convention of reserving 'd' for something. I don't remember what it was. It was pre FreeBSD 3 and pre 1997 and maybe even pre any FreeBSD and applied in some earlier Unix-en before the court cases, but not after. That old convention accounts for documentation starting with using 'e' for extra partitions and skipping 'd'. But, whatever that old convention was, it has not been used for so long that it is meaningless nowdays and 'd' can be used for whatever extra partition you want. jerry > > But if you're doing it manually starting with 'e' is fine. I suspect > the handbook section you quoted to Polytropon later is more an example > than definitive. You can happily mount an 'a' partition from another > drive that was once a system disk; it's more of a convention really. > > > 2. My second question is in regards to using the 'xx' fstype to have the > > system ignore that device. > > > > Consider, for example, a geli encrypted partition. The .eli device > > doesn't exist at boot time. I discovered by accident that the system > > won't boot with an fstab entry for a device that doesn't exist. So if I > > was to record an entry in fstab, I couldn't use > > > > /dev/ad1e.eli /home/david/private ufs rw 0 0 > > > > Does that mean that the following is what's typically to record fstab > > entries for ignored devices? > > > > /dev/ad1e.eli /home/david/private xx rw 0 0 > > /dev/ad3e /fakexx rw 0 0 > > /dev/ad3f /reservedxx rw 0 0 > > Yes. Here I must differ with Polytropon, though your format for the > options isn't perhaps quite right. From an old fstab here: > > # DeviceMountpoint FStype Options DumpPass# > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > /dev/ad0s1 /dosmsdosfs ro,noauto 0 0 > /dev/ad0s2b noneswapsw 0 0 > /dev/ad0s2a / ufs rw 1 1 > /dev/ad0s2d /varufs rw,noatime 2 2 > /dev/ad0s2e /usrufs rw,noatime 2 2 > /dev/ad0s4d /paqi4.5ufs > ro,noauto,nodev,noexec,nosymfollow,noatime 2 3 > /dev/ad0s4e /paqi4.5/varufs > ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 > /dev/ad0s4f /paqi4.5/usrufs > ro,noauto,nodev,noexec,nosymfollow,noatime 2 4 > # 25Apr06 ext 20Gb USB disk. DON'T autoadd these, deadly if da0 absent! > # .. xx fsopts, everything incl fsck must ignore .. > /dev/da0s3d /usbdsk ufs xx,noauto,nosymfollow 3 3 > /dev/da0s3e /usbdsk/var ufs xx,noauto,nosymfollow 4 4 > /dev/da0s3f /usbdsk/usr ufs xx,
Re: Re: diskless - NFS root mount problem
Hi,
thanks again for your response:
here's what I have, what I do and what I want to happen
1. I have my desktop machine which is running FreeBSD-7.2-STABLE-amd64 from
June.
I created a new distribution like that (as shown in the handbook -
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html):
mkdir /storage0/diskless
cd /usr/src
export DESTDIR=/storage0/diskless
make buildworld buildkernel installworld distribution installkernel
and created /storage0/diskless/etc/fstab with the following content:
192.168.0.1:/storage0/diskless / nfs ro 0 0
and I put this in /etc/exports (having in mind your advice about the group)
/storage0/diskless -maproot=0:0 -ro -alldirs 192.168.0.3
/usr -ro -alldirs 192.168.0.3
and this is in my dhcpd.conf (I tried with and without the comments - no
difference, same result)
host laptop {
hardware ethernet 00:1E:68:45:0D:98;
#option host-name "laptop";
#ddns-hostname "laptop";
#next-server 192.168.0.1;
fixed-address 192.168.0.3;
filename "pxeboot";
option root-path "192.168.0.1:/storage0/diskless";
}
2. And I do this:
rpcbind
nfsd -u -t -n 4
mountd -r
/etc/rc.d/ineted onestart # I have my TFTP root set to /boot
/usr/local/etc/rc.d/isc-dhcpd onestart
then I start my laptop (which has a 64bit CPU therefore it should be compatible
with my amd64 kernel) enter the boot menu and choose the network boot option
and I can see that it acquires its IP address then fetches pxeboot over TFTP
then pxeboot loads the kernel and the kernel starts bringing the system
up...and these are the last few lines where the system stops:
...
...
Trying to mount root from nfs:192.168.0.1:/storage0/diskless
NFS ROOT: 192.168.0.1:/storage0/diskless
nfs send error 13 for server 192.168.0.1:/storage0/diskless
bge0: link state changed to DOWN
bge0: link state changed to UP
3. What I want is to have a server that multiple clients can boot from
(diskless-ly as you say). And I want all file systems provided by the server to
be read-only (which means I don't need lockd, do I...)
Do you have an idea what could be my problem? ...obviously my TFTP and DHCP
services are fine, even the NFS as pxeboot is able to download the
kernel...maybe something in my distribution in /storage0/diskless is not OK?
thanks
mgp
>Please compare my working configuration to yours to check. I found
>lots of odd problems in your post and I thought it'd be best to just
>run with this clean slate.
>
>Network config:
> One low-power PC Engines ALIX board running as the NFS server, with
>a microdrive partitioned off for it's own system, plus a separate
>mounted partition for diskless clients. This config works best with
>one diskless client, and is not the documented way from FreeBSD
>handbook to accomplish diskless workstations. I'll note what I
>immediately saw as an error in your config during these snippets.
>
>alix# bsdlabel /dev/ad0s1
># /dev/ad0s1:
>8 partitions:
>#size offsetfstype [fsize bsize bps/cpg]
> a: 1048576 164.2BSD 2048 16384 8
> c: 120001770unused0 0 # "raw" part, don't
> edit
> h: 10951585 10485924.2BSD 2048 16384 28552
>
>alix# cat /etc/fstab
>/dev/ad0s1a / ufs rw 0 0
>/dev/ad0s1h /diskless ufs rw 0 0
>
>alix# cat /etc/exports
>/diskless -maproot=0:0-network 192.168.0.0 -mask 255.255.255.0
>
>*** maproot needs a user and group definition.
>
>alix# cat /etc/rc.conf
>rpcbind_enable="YES"
>nfs_server_enable="YES"
>rpc_statd_enable="YES"
>rpc_lockd_enable="YES"
>
>*** rpc_lockd provides file locking, rpc_lockd depends on rpc_statd
>
>
>** Diskless side
>
>*** I believe the root filesystem information is passed on from dhcp,
>to pxeboot, to the kernel, in order to mount the root filesystem. You
>can have a 0-size fstab file for read-write access, or provide the
>read-o
Re: Bad Blocks... Should I RMA?
On Sun, Nov 15, 2009 at 04:06:55PM -0800, Ronald F. Guilmette wrote: > > In one of my systems, I've got a Seagate SATA 500GB drive (ST3500320AS) > which is actually not very old... purchased 12/11/2008. > same single block. Here's the relevant lines from /var/log/messages: > > Nov 15 15:24:17 coredump kernel: ad4: FAILURE - READ_DMA > status=51 error=40 LBA=256230591 > Nov 15 15:24:43 coredump kernel: ad4: FAILURE - READ_DMA > status=51 error=40 LBA=256230591 > Nov 15 15:24:46 coredump kernel: ad4: FAILURE - READ_DMA > status=51 error=40 LBA=256230591 > > (Don't be confused... The name of the host system here is "coredump"... my > lame attempt at humor.) Install the smartmontools port, and check the drive with 'smartctl -a /dev/ad4'. If you see a non-zero Reallocated_Sector_Ct, RMA it immediately, as it is about to fail. If see other errors reported, RMA it. (S)ATA disk have spare sectors available. If a sector fails, it is replaced by one of the spares by the firmware. If you see a non-zero Reallocated_Sector_Ct, it means that the drive has run out of spares. This is bad news. > P.S. If I _do_ end up RMA'ing the thing back, do I need to worry about > scrubing the drive squeaky clean first... you know... using one of these > multiple write-over progs (like `wipe') if I am paranoid... as I am... > about the possibility of old credit card numbers lying around in unallocated > sectors on the drive? (The drive is empty _now_, but earlier it was in > serious/heavy use.) No. Just fill it with zeros. There was a paper presented at Usenix 1996 that you could potentially read erased data from the sidebands. But that was looking at disks make in the early nineties using MFM and RLL encoding. The encoding on todays disks is very different. The author of te original paper thinks it is almost impossible to recover overwritten data on a current harddisk. To quote from the epilogue from [http://www.cs.auckland.ac.nz/~pgut001/pubs/secure_del.html]: Any modern drive will most likely be a hopeless task, what with ultra-high densities and use of perpendicular recording... > I guess what I'm asking is: Do Segate and the other manufacturers care > enough about their customer's privacy to securely wipe old drives/platters > that come in to them for RMA? Or do I need to worry 'bout that for my own > self? I would always wipe them myself. You cannot guarantee that the manufacturer will do it. But I was under the impression that the information on a platter can only be properly read by the same arm/head it was written with. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOS9tMIB7pl.pgp Description: PGP signature
Re: No /dev/da0
On Sun, Nov 15, 2009 at 07:11:14PM +0100, Sabine Baer wrote: > Well my problem is mounting my digital camera. If I remember correctly > I did it with > mount_msdosfs /dev/da0s1 /lumix > I think that was under FreeBSD 6.n > But now, upgraded to 7.2, there ist no /dev/da0. > Attached to an iBook with Mac OS X 10.4 the cards were well mounted as > 'disk2s1'. Ok, then mounting it should work. > If I attach the camera to the FreeBSD PC the console gives > [attaching the camera] > | umass0: on > |uhub0 > |(probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > |(probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error > |(probe0:umass-sim0:0:0:0): SCSI Status: Check Condition > |(probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 > |(probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have > |changed > |(probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) > |da0 at umass-sim0 bus 0 target 0 lun 0 > |da0: Removable Direct Access SCSI-2 device > |da0: 1.000MB/s transfers > |da0: 14MB (29121 512 byte sectors: 64H 32S/T 14C) I sometimes get error reports like this as well with USB sticks. I can usually see it on the drive as well, the drive's indicator light doesn't light up. Pulling out the USB cable and trying again usually helps, in my experience. Try another cable or another USB port if available. Sometimes it is necessary to use camcontrol(8) as per the earlier reply. > I haven't any clue if it's FreeBSD's fault, the camera's or mine. > Is there somone who can give me some hint? The USB stack in 7.2 doesn't always handle quirky hardware well. There could be a regression on your hardware going from 6.x to 7.2. The USB stack has been rewritten for 8.0. In my limited testing it works better. I've got 8.0-PRERELEASE running on a laptop without problems. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp0zXAHm0tr6.pgp Description: PGP signature
Re: Virtual box to do cross-browser testing
Jonathan Chen wrote: On Mon, Nov 16, 2009 at 11:02:59AM -0500, John Almberg wrote: Anyone have experience using Sun's "Virtual Box" on FreeBSD? I am looking for a way to run virtual Windows machines to do cross-browser testing... I've been using it to do some .NET programming, and it's been pretty good. No major problem, aside from the lack of CPU cycles the odd time or so. That sounds encouraging enough to give it a try. Thanks. -- John ___ 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: no sshd on new server...
On Sun, 15 Nov 2009 23:00:56 -0800, Gary Kline wrote:
> there were stderrs output when i tried to exec sshd. reason
> was that the rc.conf entry was not in rc.conf. (this is all
> going into my .howto file
The rc.d mechanism suggests to use /etc/rc.d/sshd control
script for SSH server operations instead of the "bare"
binary. The control script checks for the variable
${sshd_enable} which has to be set, or it won't start.
By the way, it's not a problem if /etc/rc.conf is empty.
In this case, defaults are used, but:
% grep sshd /etc/defaults/rc.conf
sshd_enable="NO"# Enable sshd
As you see, sshd_enable is set to "NO" by default.
--
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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009 19:35:54 +0200, Manolis Kiagias wrote: > If you stick with HAL however (using "AllowEmptyInput" bypasses the > autodetection), you can just use the policy file in the Handbook and > just add the "DontZap" option in "ServerFlags" or "ServerLayout" section. ^^ Or? Arbitrary locations again? :-) -- 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"
[solved] Re: Re: Re: diskless - NFS root mount problem
Hi,
it turned out I was stupid enough to misconfigure the kernel...I forgot that I
had left the IPFIREWALL options turned on and as you know it's default to deny
so once the kernel initializes ipfw it blocks everything including NFS so that
was the whole problem...I removed the IPFIREWALL option and all went fine.
thanks again
mgp
> Hi,
>thanks again for your response:
>here's what I have, what I do and what I want to happen
>
>1. I have my desktop machine which is running FreeBSD-7.2-STABLE-amd64 from
>June.
> I created a new distribution like that (as shown in the handbook -
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-diskless.html):
>
>
>mkdir /storage0/diskless
>cd /usr/src
>export DESTDIR=/storage0/diskless
>make buildworld buildkernel installworld distribution installkernel
>
>
>and created /storage0/diskless/etc/fstab with the following content:
>
>
>192.168.0.1:/storage0/diskless / nfs ro 0 0
>
>
>and I put this in /etc/exports (having in mind your advice about the group)
>
>
>/storage0/diskless -maproot=0:0 -ro -alldirs 192.168.0.3
>/usr -ro -alldirs 192.168.0.3
>
>
>and this is in my dhcpd.conf (I tried with and without the comments - no
>difference, same result)
>
>
> host laptop {
>hardware ethernet 00:1E:68:45:0D:98;
>#option host-name "laptop";
>#ddns-hostname "laptop";
>#next-server 192.168.0.1;
>fixed-address 192.168.0.3;
>filename "pxeboot";
>option root-path "192.168.0.1:/storage0/diskless";
> }
>
>
>2. And I do this:
>
>
>rpcbind
>nfsd -u -t -n 4
>mountd -r
>/etc/rc.d/ineted onestart # I have my TFTP root set to /boot
>/usr/local/etc/rc.d/isc-dhcpd onestart
>
>
>then I start my laptop (which has a 64bit CPU therefore it should be
>compatible with my amd64 kernel) enter the boot menu and choose the network
>boot option and I can see that it acquires its IP address then fetches
>pxeboot over TFTP then pxeboot loads the kernel and the kernel starts
>bringing the system up...and these are the last few lines where the system
>stops:
>
>
>...
>...
>Trying to mount root from nfs:192.168.0.1:/storage0/diskless
>NFS ROOT: 192.168.0.1:/storage0/diskless
>nfs send error 13 for server 192.168.0.1:/storage0/diskless
>bge0: link state changed to DOWN
>bge0: link state changed to UP
>
>
>3. What I want is to have a server that multiple clients can boot from
>(diskless-ly as you say). And I want all file systems provided by the server
>to be read-only (which means I don't need lockd, do I...)
>
>Do you have an idea what could be my problem? ...obviously my TFTP and DHCP
>services are fine, even the NFS as pxeboot is able to download the
>kernel...maybe something in my distribution in /storage0/diskless is not OK?
>
>thanks
>mgp
>
>
> >Please compare my working configuration to yours to check. I found
> >lots of odd problems in your post and I thought it'd be best to just
> >run with this clean slate.
> >
> >Network config:
> > One low-power PC Engines ALIX board running as the NFS server, with
> >a microdrive partitioned off for it's own system, plus a separate
> >mounted partition for diskless clients. This config works best with
> >one diskless client, and is not the documented way from FreeBSD
> >handbook to accomplish diskless workstations. I'll note what I
> >immediately saw as an error in your config during these snippets.
> >
> >alix# bsdlabel /dev/ad0s1
> ># /dev/ad0s1:
> >8 partitions:
> >#size offsetfstype [fsize bsize bps/cpg]
> > a: 1048576 164.2BSD 2048 16384 8
> > c: 120001770unused0 0 # "raw" part, don't
> > edit
> > h: 10951585 10485924.2BSD 2048 16384 28552
> >
> >alix# cat /etc/fstab
> >/dev/ad0s1a / ufs rw 0 0
> >/dev/ad0s1h /diskless ufs rw 0 0
> >
> >alix# cat /etc/exports
> >/diskless -maproot=0
Re: Default cannot install 8.0 rc2 in mobo P5QL-EM Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: sti
vuthecuong wrote: Hello, I am trying to install FreeBSD 8.0 rc2 on mobo ASUS P5QL-EM, but under the boot of the install dvd I get this run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config and then 120, 180 etc. Anyone know whats wrong? thanks http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
Polytropon wrote: > On Mon, 16 Nov 2009 19:35:54 +0200, Manolis Kiagias wrote: > >> If you stick with HAL however (using "AllowEmptyInput" bypasses the >> autodetection), you can just use the policy file in the Handbook and >> just add the "DontZap" option in "ServerFlags" or "ServerLayout" section. >> > ^^ > Or? Arbitrary locations again? :-) > > Hehe, both places will work actually. A default xorg.conf generated with the '-configure' option, will not have a "ServerFlags" section (which is entirely optional), but will certainly have a "ServerLayout" one. 'DontZap' (and other options) work in both places. Disclaimer: Xorg people will probably break this again in about 15days. Handle with care! ___ 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: [solved] Re: Re: Re: diskless - NFS root mount problem
On 11/16/09, Mario Pavlov wrote: > Hi, > it turned out I was stupid enough to misconfigure the kernel...I forgot that > I had left the IPFIREWALL options turned on and as you know it's default to > deny so once the kernel initializes ipfw it blocks everything including NFS > so that was the whole problem...I removed the IPFIREWALL option and all went > fine. > Ah, one of those moments. I have them too. Good to know it's working for you, and I would just because I'm the perfectionist personality type, change a couple of things that won't make a negative impact. The server's exports has no reason to export the diskless root with -alldirs. The system isn't asking for any mountpoint within / so you can leave off the -alldirs. 2nd, you buildworld and installworld into the diskless root, but never use it. You're using disk space you can reclaim. > thanks again > mgp Glad it's working, enjoy! ___ 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: [solved] Re: Re: Re: diskless - NFS root mount problem
Mario Pavlov wrote: > Hi, it turned out I was stupid enough to misconfigure the > kernel...I forgot that I had left the IPFIREWALL options turned on You're not a real sysadmin until you've firewalled yourself out of at least one mission-critical system. Bonus points if it has no out-of-band control plane. Further bonus points if it is more than 100 miles away, and you are the one who has to drive to the data center. -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Bad Blocks... Should I RMA?
On Mon, 16 Nov 2009 19:23:58 +0100 Roland Smith wrote: > Install the smartmontools port, and check the drive with > 'smartctl -a /dev/ad4'. If you see a non-zero Reallocated_Sector_Ct, > RMA it immediately, as it is about to fail. If see other errors > reported, RMA it. > > (S)ATA disk have spare sectors available. If a sector fails, it is > replaced by one of the spares by the firmware. If you see a non-zero > Reallocated_Sector_Ct, it means that the drive has run out of spares. > This is bad news. Surely it's the other way around - if you see a value of zero in the "value" column the drive has run out of spare sectors and it's time to RMA the drive? From what I've seen the 'raw' column appears to count the number of sectors the drive has remapped using the spares buffer. If it gets into the hundreds it's probably time to think about RMA'ing the drive - if you trust that the 'raw' column is reporting what you think it is (you should really only base your decision on the value, worst and threshold columns). -- Bruce Cran ___ 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: Trivial questions about CNTL-ALT-DEL and CNTL-ALT-BACKSPACE
On Mon, 16 Nov 2009, Philipp Lengemann wrote: Am Sun, 15 Nov 2009 15:19:29 -0800 schrieb "Ronald F. Guilmette" : I _did_ go and read the Handbook section that Manolis Kiagias kindly posted a link to, and I have now tried _both_ of the two ways described there to re-enable CNTL-ALT-BACKSPACE functionality for the X server, and sadly I must report that for me, at least _neither_ of those methods worked Put the following to your xorg.conf: Section "ServerFlags" Option "DontZap" "off" Option "AllowEmptyInput" "off" Option "AutoAddDevices" "off" EndSection Section "InputDevice" Option "XkbOptions" "terminate:ctrl_alt_bksp" EndSection This works for me very reliable (xorg-7.4_2). That InputDevice entry is interesting. It has to be added to a Keyboard section, not standalone as shown (unless I missed something). (If it was standalone, it would nicely eliminate the need for the setxkbmap -option terminate:ctrl_alt_bksp entry in my .xinitrc.) For those who want to do that with hal, for all keyboards, here's a patch for /usr/local/share/hal/fdi/policy/10osvendor/10-x11-input.fdi: --- 10-x11-input.fdi.orig 2009-11-16 14:47:01.0 -0700 +++ 10-x11-input.fdi2009-11-16 14:54:01.0 -0700 @@ -22,6 +22,7 @@ string="Linux"> evdev + terminate:ctrl_alt_bksp -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Bad Blocks... Should I RMA?
On Mon, Nov 16, 2009 at 09:43:31PM +, Bruce Cran wrote: > On Mon, 16 Nov 2009 19:23:58 +0100 > Roland Smith wrote: > > > Install the smartmontools port, and check the drive with > > 'smartctl -a /dev/ad4'. If you see a non-zero Reallocated_Sector_Ct, > > RMA it immediately, as it is about to fail. If see other errors > > reported, RMA it. > > > > (S)ATA disk have spare sectors available. If a sector fails, it is > > replaced by one of the spares by the firmware. If you see a non-zero > > Reallocated_Sector_Ct, it means that the drive has run out of spares. > > This is bad news. > > Surely it's the other way around - if you see a value of zero in the > "value" column the drive has run out of spare sectors and it's time to > RMA the drive? I was talking about the _RAW_VALUE column. There seems to be some differences in interpretation between vendors as to what the VALUE column means. Most of the advice I've seen over the years says to look at the RAW_VALUE. See http://en.wikipedia.org/wiki/S.M.A.R.T. as well. > From what I've seen the 'raw' column appears to count > the number of sectors the drive has remapped using the spares buffer. > If it gets into the hundreds it's probably time to think about RMA'ing > the drive Yes, the raw value is the number of sectors allocated from the spares. I originally thought it was the number of reallocations _beyond_ the spares. That's a misunderstanding on my part. Nevertheless this attribute (along with several) is marked on the Wikipedia page for smart as a "Potential indicator of imminent electromechanical failure". You can find the same attributes marked as critical when perusing mailing list archives. For me, my data is worth much more than the harddisk it is on. Some of it is literally irreplacable. So my policy is to go look for a replacement harddisk as soon as the RAW_VALUEs of any of these critical indicators start going up from zero. And store any data at least on two harddisks, whether in a mirror or in a cron+rsync setup. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpnAt8LPu3hn.pgp Description: PGP signature
panic? i386 on dell duo
something panicked my dell. more than twice. i have loaded, the i386 7.2-R Dvd. the panic was something like PHY#1 panic[y/n]y then something about cpu 0 being involved. i have the 8.0 rc3 bootonly.iso cd. should i try that? or did dell ship me a bad computer? ideas? gary -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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: [solved] Re: Re: Re: diskless - NFS root mount problem
In message <4b01c4df.4040...@freebsd.org>, Doug Barton writes: > Mario Pavlov wrote: > > Hi, it turned out I was stupid enough to misconfigure the > > kernel...I forgot that I had left the IPFIREWALL options turned on > > You're not a real sysadmin until you've firewalled yourself out of at > least one mission-critical system. > > Bonus points if it has no out-of-band control plane. > > Further bonus points if it is more than 100 miles away, and you are > the one who has to drive to the data center. Triple bonus points if it is +20 hours of flight time away. Home data center and angry wife w/o Internet access. Yes I managed to stuff up a home machine while in Ireland. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: no sshd on new server...
On Mon, Nov 16, 2009 at 08:31:49PM +0100, Polytropon wrote:
> On Sun, 15 Nov 2009 23:00:56 -0800, Gary Kline wrote:
> > there were stderrs output when i tried to exec sshd. reason
> > was that the rc.conf entry was not in rc.conf. (this is all
> > going into my .howto file
>
> The rc.d mechanism suggests to use /etc/rc.d/sshd control
> script for SSH server operations instead of the "bare"
> binary. The control script checks for the variable
> ${sshd_enable} which has to be set, or it won't start.
>
> By the way, it's not a problem if /etc/rc.conf is empty.
> In this case, defaults are used, but:
>
> % grep sshd /etc/defaults/rc.conf
> sshd_enable="NO"# Enable sshd
>
> As you see, sshd_enable is set to "NO" by default.
>
darn, but that would've been that last thing i would have
expected... . i dont see any rationale...
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
___
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"
Lockup problems on FreeBSD disks
I have a USB hard drive. Whenever I open two programs which utilise the USB hard drive simultaneously, these programs, i assume when they attempt to write to the hard drive lock up due to what i suspect must be some issue with the USB driver and perhaps a deadlock involving multiple concurrent accesses to the drive. When they attempt to access the drive the programs can lock up for several minutes before being unblocked. When only one program is using the drive this behaviour does not seem to occur. It seems most likely that this is a USB level problem involving the USB drivers. I am using FreeBSD 7.1. It is annoying behaviour to say the least and I wonder what can be done about it, and if this issue is being addressed, perhaps in the recent redesign of the USB code. It seems to be a pretty consistent issue, happening with multiple installs of FreeBSD and different drives. Thank you. ___ 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: [solved] Re: Re: Re: diskless - NFS root mount problem
On Nov 16, 2009, at 13:32 , Doug Barton wrote: > You're not a real sysadmin until you've firewalled yourself out of at > least one mission-critical system. > > Bonus points if it has no out-of-band control plane. > > Further bonus points if it is more than 100 miles away, and you are > the one who has to drive to the data center. Extreme bonus points if said system is on another continent, and you have to get on a plane _right_now_ (spending the flight wondering why the OOB system is dead). -aDe ___ 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: panic? i386 on dell duo
Hi On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline wrote: > > something panicked my dell. more than twice. i have loaded, the > i386 7.2-R Dvd. the panic was something like > > PHY#1 > panic[y/n]y Do you have a crash report in /var/crash ? > > then something about cpu 0 being involved. > > i have the 8.0 rc3 bootonly.iso cd. should i try that? or did > dell ship me a bad computer? > I'll keep my opinions to myself... > ideas? > > gary > > > -- Glen Barber ___ 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: panic? i386 on dell duo
On Mon, Nov 16, 2009 at 07:57:19PM -0500, Glen Barber wrote: > Hi > > On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline wrote: > > > > something panicked my dell. more than twice. i have loaded, the > > i386 7.2-R Dvd. the panic was something like > > > > PHY#1 > > panic[y/n]y > > Do you have a crash report in /var/crash ? > no, nada. i didnt know about /var/crash until now, thanks for the datapoint. it is empty. > > > > then something about cpu 0 being involved. > > > > i have the 8.0 rc3 bootonly.iso cd. should i try that? or did > > dell ship me a bad computer? > > > > I'll keep my opinions to myself... > well, i'd laugh, glen, but i hurt my back twisting over to my right [[ with my left hand]] to use the dell keybd. yes, why would any body do anybody else a bad deed. here is more complete version of the events of the day. my network bud down in dallas is helping me get the dell as my new server. my old hp kayak is from 1998 and on its death-bed. okay: i have 7.2-R, i386. installs fine. jon horne changed the IP that the op sys | DHCP suite chose from 10.47.0.112 to 10.47.0.230. i do not know why, but he change the ifconfig line in /etc/rc.conf from ="DHCP" to ="inet 10.47.0.230 netmask 10.0.0.255" or something similar. jon says that the IP can't or shouldn't be D=Dynamic but stable. surely this is right. ---in my old config prior to jan 2008 or dec 2007 i had every local IP tied down in a file in /usr/local/etc/dhcpd.conf [or similar]. it worked flawlessly. now i am using pfSense and i *think* there is a config file in there that makes local IP's stable. anybody know if i'm right? anyway, after my dell was reset to 0.230 from 0.112, things began to fail. i do not know very much about networking or dhcp; just enough to know that if something works, that is a Good sigh! i need to move over my /etc/namedb/* files; i need to set up mail-- dovecot[?]; and lastly, apache22. i've got the files, just don't know how-to make the switch from my 1998 server to my 2009 computer. thanks to all who have read this far. ideas, suggestions very welcome. a severe wind storm tonight may take down my network any time. sooner is better, :-) gary > > ideas? > > > > gary > > > > > > > > > > -- > Glen Barber -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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: panic? i386 on dell duo
Hi Gary, On Mon, Nov 16, 2009 at 10:28 PM, Gary Kline wrote: > On Mon, Nov 16, 2009 at 07:57:19PM -0500, Glen Barber wrote: >> Hi >> >> On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline wrote: >> > >> > something panicked my dell. more than twice. i have loaded, the >> > i386 7.2-R Dvd. the panic was something like >> > >> > PHY#1 >> > panic[y/n]y >> >> Do you have a crash report in /var/crash ? >> > > no, nada. i didnt know about /var/crash until now, thanks for the > datapoint. it is empty. > Very important location on your system after a (possible) panic. > >> > >> > then something about cpu 0 being involved. >> > >> > i have the 8.0 rc3 bootonly.iso cd. should i try that? or did >> > dell ship me a bad computer? >> > >> >> I'll keep my opinions to myself... >> > > well, i'd laugh, glen, but i hurt my back twisting over to my right > [[ with my left hand]] to use the dell keybd. yes, why would any > body do anybody else a bad deed. > > here is more complete version of the events of the day. > > my network bud down in dallas is helping me get the dell as my > new server. my old hp kayak is from 1998 and on its death-bed. > > okay: i have 7.2-R, i386. installs fine. jon horne changed the > IP that the op sys | DHCP suite chose from 10.47.0.112 to > 10.47.0.230. i do not know why, but he change the ifconfig line in > /etc/rc.conf from ="DHCP" to ="inet 10.47.0.230 netmask 10.0.0.255" > or something similar. jon says that the IP can't or shouldn't be > D=Dynamic but stable. surely this is right. ---in my old config > prior to jan 2008 or dec 2007 i had every local IP tied down in a > file in /usr/local/etc/dhcpd.conf [or similar]. it worked > flawlessly. now i am using pfSense and i *think* there is a config > file in there that makes local IP's stable. > Network configuration "should not" provoke a panic, unless the driver is at fault (which you have not stated which driver this is). > anybody know if i'm right? > No clue about pfsense > anyway, after my dell was reset to 0.230 from 0.112, things began to > fail. i do not know very much about networking or dhcp; just enough > to know that if something works, that is a Good sigh! > > i need to move over my /etc/namedb/* files; i need to set up mail-- > dovecot[?]; and lastly, apache22. i've got the files, just don't > know how-to make the switch from my 1998 server to my 2009 > computer. > > thanks to all who have read this far. ideas, suggestions very > welcome. a severe wind storm tonight may take down my network any > time. sooner is better, :-) > > gary > >> > ideas? >> > >> > gary >> > >> > >> > >> >> -- Glen Barber ___ 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: No /dev/da0
On Mon, Nov 16, 2009 at 01:56:59AM +, Frank Shute wrote: [...] > Have you tried playing around with camcontrol(8)? Yes, but the only effect was a freezing controlling terminal. Only # camcontrol devlist at scbus0 target 0 lun 0 (da0,pass0) # Shutting down the system I can read "Some processes wouldn't die" > Maybe after you've plugged it in, try: > > # camcontrol load 0:0:0 > > then: > > # camcontrol devlist > > and then try mounting it if it shows up given the above command. > > Sometimes, you have to: > > # camcontrol stop 0:0:0 > # camcontrol rescan 0:0:0 > # camcontrol load 0:0:0 > > to get it to behave. > > Before unplugging it, unmount it and then: > > # camcontrol eject 0:0:0 Thank You. Might be I did a mistake, but now even /dev/pass0 has gone. Sabine -- Le cardinal César Baronius avait raison: "Le Saint-Esprit nous apprend comment aller au ciel et non pas comment va le ciel". (Kardinal Poupard) ___ 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: No /dev/da0
On Mon, Nov 16, 2009 at 07:39:12PM +0100, Roland Smith wrote: [...] > The USB stack in 7.2 doesn't always handle quirky hardware well. > There could be a regression on your hardware going from 6.x to 7.2. > The USB stack has been rewritten for 8.0. In my limited testing it > works better. I've got 8.0-PRERELEASE running on a laptop without > problems. OK, thanks. I haven't an idle notebook, but I'll try a 8.0 on a bootable stick, just for seeing /dev/da0(s1), not the card's content. Sabine -- "Wissenschaftlich betrachtet wird das Häuschen kaputt sein." (Th. Waschke in dswc auf die Frage eines wissenschftlich Interessierten, was mit einem Holzhaus, in dem eine Atombombe gezuendet wird, passiere.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Re: [solved] Re: Re: Re: diskless - NFS root mount problem
indeed you get bonus points if you firewall yourself :) and of course this is not the first time I do that so my score is pretty good however my favourite is to forget about net.inet.ip.forwarding when I upgrade routers with many clients :) Tim, thanks for your hints...but I don't understand this one: >2nd, you buildworld and installworld into the diskless root, but never >use it. You're using disk space you can reclaim. how so I never use it and can reclaim diskspace ? thanks, mgp - Вижте водещите новини от Vesti.bg! http://www.vesti.bg ___ 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"
Iomega REV Drive
I have recently found a used Iomega REV drive for a cheap price, and thought it might work as a good low cost backup solution on my home FreeBSD server. However, I haven't been able to figure out how to make it work with FreeBSD. FreeBSD finds it as a CDROM drive, has anyone managed to make one of these drives work on FreeBSD? This is the 36G IDE version of the drive, I picked the drive up cheap, along with one used disk, if it doesn't work it's no big loss. I have tried searching the lists, and have found people asking questions in the past, but never found an answer to them. The dmesg output for the drive shows it as: acd0: CDROM at ata0-slave UDMA66 Thanks, Dean Weimer Network Administrator ___ 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: panic? i386 on dell duo
On Mon, Nov 16, 2009 at 11:28:44PM -0500, Glen Barber wrote: > Hi Gary, > > On Mon, Nov 16, 2009 at 10:28 PM, Gary Kline wrote: > > On Mon, Nov 16, 2009 at 07:57:19PM -0500, Glen Barber wrote: > >> Hi > >> > >> On Mon, Nov 16, 2009 at 5:58 PM, Gary Kline wrote: > >> > > >> > something panicked my dell. more than twice. i have loaded, the > >> > i386 7.2-R Dvd. the panic was something like > >> > > >> > PHY#1 > >> > panic[y/n]y > >> > >> Do you have a crash report in /var/crash ? > >> > > > > no, nada. i didnt know about /var/crash until now, thanks for the > > datapoint. it is empty. > > > > Very important location on your system after a (possible) panic. > > > > >> > > >> > then something about cpu 0 being involved. > >> > > >> > i have the 8.0 rc3 bootonly.iso cd. should i try that? or did > >> > dell ship me a bad computer? > >> > > >> > >> I'll keep my opinions to myself... > >> > > > > well, i'd laugh, glen, but i hurt my back twisting over to my right > > [[ with my left hand]] to use the dell keybd. yes, why would any > > body do anybody else a bad deed. > > > > here is more complete version of the events of the day. > > > > my network bud down in dallas is helping me get the dell as my > > new server. my old hp kayak is from 1998 and on its death-bed. > > > > okay: i have 7.2-R, i386. installs fine. jon horne changed the > > IP that the op sys | DHCP suite chose from 10.47.0.112 to > > 10.47.0.230. i do not know why, but he change the ifconfig line in > > /etc/rc.conf from ="DHCP" to ="inet 10.47.0.230 netmask 10.0.0.255" > > or something similar. jon says that the IP can't or shouldn't be > > D=Dynamic but stable. surely this is right. ---in my old config > > prior to jan 2008 or dec 2007 i had every local IP tied down in a > > file in /usr/local/etc/dhcpd.conf [or similar]. it worked > > flawlessly. now i am using pfSense and i *think* there is a config > > file in there that makes local IP's stable. > > > > Network configuration "should not" provoke a panic, unless the driver > is at fault (which you have not stated which driver this is). > dunno about the driver. doubt it. anyway, busy fixing things while the power stays on! -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php ___ 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"
