Re: CMS
Paul Schmehl wrote: > I manage a couple of FreeBSD servers for a friend. He's gotten all > excited about content management and thinks that's the way to go. The > system he's familiar with is Windows only. I've done a little research, > but I'm wondering if anyone reading the list has experience with a CMS > on FreeBSD - one that's in ports preferably. > I've used Joomla, Wordpress and Nucleus in the past. Dropped Joomla, because it was too big (for me) and maintaining the plugins (modules?) was too much of a hassle. The nucleus site is a nostalgic site, the Joomla site has been converted to Wordpress. The latter can be upgraded from the browser. Neither of these are installed by ports, all by source. MySQL is from ports, btw, as is all supporting software, like apache, gd, whatever. Peter -- http://www.boosten.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: CMS
On 2009-10-15, at 10:38 PM, Paul Schmehl wrote: I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Whatever you choose, make sure that the port maintainer is active with security updates. Sometimes it's better to give them web space and a DB, and let them handle updates themselves. It's worth it to subscribe to the security list of whatever CMS you choose. I've used Drupal on FreeBSD (not from ports) without issues. Pretty much anything aimed at *nix will work fine, especially if it's open source. --Andrew
Re: Security blocking question
> > > > Is there a way that I could configure the server so that if there are for > example X attempts from an IP address then for the next Y hours all the SSH > requests would be ignored from that IP address? There are only a handful of > people who have access to that server. > > Yes. > > In pf.conf: > > table persist > > [...] > > block drop in log quick on $ext_if from > > [...] > > pass in on $ext_if proto tcp \ > from any to $ext_if port ssh \ > flags S/SA keep state \ > (max-src-conn-rate 3/30, overload flush global) > > plus you'll need to add a cron job to clear old entries out of the > ssh-bruteforce > table after a suitable amount of time has passed. Use expiretable to do > that. Note: in practice I've found that it's a *really good idea* to > implement > a SSH whitelist of addresses that will never be bruteforce blocked like this > -- > it's very easy to lock yourself out even if everything you're doing is > entirely > legitimate. Coding that is left as an exercise for the reader. > What is the best way of testing the PF rule? Is there a quick way to mimic a brute force? Is there a way that I could review the content of the table through pfctl -s all 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"
Re: Best procedure for full backup of live system
On Thu, 15 Oct 2009, Nerius Landys wrote: Thanks for your help guys. I have decided to attempt the following. With a filesystem snapshot, take a dump 0 of all filesystems. Back up these dumps to a 500GB disk I have sitting at home (the server I'm backing up is in a data center). Perform this maybe once a week or once a month. Just a general note: backup to a hard drive isn't bad, but it's not the same as removable media. One failure can kill all of your backups... I am now looking at this: http://www.freebsd.org/doc/en/books/handbook/backup-basics.html#AEN25994 For step 1, I'm a little unsure what they are talking about. I assume that to begin with I would do this: > bsdlabel ad4s1 Since that is my disk and it has one partition. The first step there has you print out the bsdlabel. That can be valuable because it's a lot easier to have that information on hand than to try to reconstruct it after a failure. I would probably also want to do this: > dd if=/dev/ad4 of=MBR_backup bs=512 count=1 Handy to have, and takes little space. to back up the MBR, so I can recontruct the boot program and partition table. But they don't mention that in the Handbook. Then it says to back up /etc/fstab, but I'm not quite sure how I'd use this in a restore. Mostly it's reference information you might need after a failure, to see which partition goes to which mountpoint: "Aha! On that drive, /usr is s1g, not s1f." Lastly, it says save all boot messages. Do they mean the output of dmesg? Why is this useful? It would show what hardware was in the old machine and what services are running on startup. Backup in general is making copies of information you won't need as long as you have a backup of it. Of course I would complement all of these things with the actual dump 0 of all sectors on the primary partition of the single hard drive that I have. dump(8) doesn't do all sectors, just ones used by the filesystem. Also, dump doesn't cross filesystems. In a typical FreeBSD install, /, /var, and /usr are separate filesystems. A dump of / won't get them all at once. My server should boot fine with the FreeBSD CDROM (fixit), because it uses a subset of the GENERIC kernel device drivers. If you can, try that before an actual emergency. So I probably don't need to pay attention to the instuctions talking about floppies. Not any more. A full FreeBSD install CD or DVD along with the fixit gives a lot more options. -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: CMS
Paul - I used to work with the guys at Appalachian State that did phpWebSite (I was their SA) and it worked great on FreeBSD. I can't say how well it works *now* but it ran fine as of a year ago on Apache2 + PostGreSQL. As far as a CMS or application framework went, it was a cinch. I just never could get into the others. kmw On 15/10/2009, Paul Schmehl wrote: > I manage a couple of FreeBSD servers for a friend. He's gotten all > excited about content management and thinks that's the way to go. The > system he's familiar with is Windows only. I've done a little research, > but I'm wondering if anyone reading the list has experience with a CMS on > FreeBSD - one that's in ports preferably. > > Pros? Cons? Any known security issues? > > Paul Schmehl, If it isn't already > obvious, my opinions are my own > and not those of my employer. > ** > WARNING: Check the headers before replying > > ___ > 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" > -- Sent from my mobile device Whenever there is in any country, uncultivated lands and unemployed poor, it is clear that the laws of property have been so far extended as to violate natural right. The earth is given as a common stock for man to labour and live on. -- Thomas Jefferson, 1785 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: sysinstall colours
On Tue, Oct 13, 2009 at 2:23 PM, Alexander Best < alexbes...@math.uni-muenster.de> wrote: > > just did a quick research and google soc sponsored the finstaller in 2007 > and > the bsdinstaller in 2005. > > personally if i spent a lot of time on such a project i'd be expecting it > to > get integrated into the base system. if not i'd get rather upset and would > probably switch to linux or opensolaris. > > just my 2 cents. > > alex > Personally if I spent a lot of time on such a project, I'd be sure to have the "is this going to make it into freebsd base?" conversation first. -- randi ___ 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: CMS
Howdy On Thu, Oct 15, 2009 at 10:38 PM, Paul Schmehl wrote: > I manage a couple of FreeBSD servers for a friend. He's gotten all excited > about content management and thinks that's the way to go. The system he's > familiar with is Windows only. I've done a little research, but I'm > wondering if anyone reading the list has experience with a CMS on FreeBSD - > one that's in ports preferably. > I've used both Drupal and Wordpress (both in ports). I'd have to gear more towards Drupal than anything else, though to be honest, I feel the same about Drupal as the author of mutt feels about mail clients - "they all suck; this one sucks less." > Pros? Cons? Any known security issues? > Yes to all three. -- 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"
CMS
I manage a couple of FreeBSD servers for a friend. He's gotten all excited about content management and thinks that's the way to go. The system he's familiar with is Windows only. I've done a little research, but I'm wondering if anyone reading the list has experience with a CMS on FreeBSD - one that's in ports preferably. Pros? Cons? Any known security issues? Paul Schmehl, If it isn't already obvious, my opinions are my own and not those of my employer. ** WARNING: Check the headers before replying ___ 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: booting from wrong disk
On 10/15/09, PJ wrote: > While trying to learn and understand the dump-retore process, I messed > up the ad4s1a partition and could not boot. To fix it I restored a > dumpfile of ad12s1a which is, for all intents and purposes, the same as > ad4s1a. I then boot from ad4 and surprise, surprise... > #df shows we have been booted from ad12 and all partitions are ad12 > Booting from ad12s1a gives exactly the same results. > So, how can I get ad4s1a to boot from ad4? > I imagine it is something in the boot files... but how to fix that? Probably because ad12's /etc/fstab tell it to mount ad12's filesystems. rewriting mbrs and stuff probably won't help. check your fstab. ___ 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: Best procedure for full backup of live system
Thanks for your help guys. I have decided to attempt the following. With a filesystem snapshot, take a dump 0 of all filesystems. Back up these dumps to a 500GB disk I have sitting at home (the server I'm backing up is in a data center). Perform this maybe once a week or once a month. I am now looking at this: http://www.freebsd.org/doc/en/books/handbook/backup-basics.html#AEN25994 For step 1, I'm a little unsure what they are talking about. I assume that to begin with I would do this: > bsdlabel ad4s1 Since that is my disk and it has one partition. I would probably also want to do this: > dd if=/dev/ad4 of=MBR_backup bs=512 count=1 to back up the MBR, so I can recontruct the boot program and partition table. But they don't mention that in the Handbook. Then it says to back up /etc/fstab, but I'm not quite sure how I'd use this in a restore. Lastly, it says save all boot messages. Do they mean the output of dmesg? Why is this useful? Of course I would complement all of these things with the actual dump 0 of all sectors on the primary partition of the single hard drive that I have. My server should boot fine with the FreeBSD CDROM (fixit), because it uses a subset of the GENERIC kernel device drivers. So I probably don't need to pay attention to the instuctions talking about floppies. Am I correct in all of this? ___ 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: usb key problem
On Thu, 15 Oct 2009 20:12:06 -0400, PJ wrote: > I do hate MS, but can't totally avoid it. I'm totally MICROS~1 free for more than 15 years now. :-) > Now, I hope the key works to transfer the dumpfiles even if it's in Fat32... It should work, BUT... I think I remember that there was a size limit of some GB so that larger files got truncated... I am not sure if this is still the case. You should check the backup files, but that won't be a problem because you still have the source system. You shoudln't have problems with the stupid +x attributes because the files are only read. > I think I'll be able to float by myself... for a while at least. We all float down here. :-) -- 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: usb key problem
On Thu, 15 Oct 2009 20:06:08 -0400, PJ wrote: > Anyway, I found the solution on the web... couldn't belive it was that > simple: just ignore the crap spewed out on the screen and just mount iit > as you would any other disk. > # mount -t msdosfs /dev/da0s1 /mnt > and that's it Additionally, when you use mount_msdosfs, you can specify masks (-m and -M) in order not to have +x attributes on all the files; the MS-DOS file system on the stick could give you unwanted results, for example if you have a .jpg file on the stick and want to open it (with the default app for .jpg file type), the system will try to execute it. > Now to see how I can use it to restore stuff. :-D If you want to use the stick for FreeBSD operations, why not give it a real file system (i. e. UFS) instead of some old FAT? You can simply # newfs /dev/da0 and then access it in the standard way: # mount /dev/da0 /mnt See that file owner:group, permissions and flags are now supported, and files that are not supposed to be executables don't have +x attribute (as in opposite to FAT / msdosfs). You could even add an entry in /etc/fstab like this: /dev/da0s1 /media/stick msdosfs rw,noauto,noatime 0 0 or, for proper UFS: /dev/da0 /media/stick ufs rw,noauto,noatime 0 0 Keep in mind that when using device names, it's a matter of in which sequence device are detected that result in the corresponding device name (da0, da1 etc.); using labels is the more elegant way here. -- 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: usb key problem
Polytropon wrote: > On Thu, 15 Oct 2009 19:18:45 -0400, PJ wrote: > >> Now that I have had a few moments to think about it, maybe I have to >> give good old cruze and enema and format it under XP ... maybe all it >> needs is a clean system on it. ;-) >> > > I'm not sure if USB sticks tend to degrade filesystem-wise, > but when you put such a stick into random "Windows" PCs, it's > quite possible that data gets messed up. The most ideal > solution of course is to simply newfs the stick and give it > a UFS file system, but sadly, "Windows" PC are resistent to > standards, so they won't read it, but will force you to use > old-fashioned MS-DOS-like file systems. :-) > > > I do hate MS, but can't totally avoid it. Now, I hope the key works to transfer the dumpfiles even if it's in Fat32... Anyway, thanks much for your guidance and patience. :-) I think I'll be able to float by myself... for a while at least. ___ 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: usb key problem
Polytropon wrote: > On Thu, 15 Oct 2009 18:19:16 -0400, PJ wrote: > >> I am running 7.2 but cannot properly attach/detach cruze 8gb and 4gb USB >> keys. >> When inserted, generate errors: >> da0 seems to be read correctly >> but then comes arow of >> (probe0:umass-sim0:0:0:1): snip CAM Status: SCSI Status Error >> snip NOT READY asc:3a,0 >> Medium not present >> Unretryable error >> then >> cd0 at umass-sim0 dada,dada,dada >> attempt to query device size failed; UNIT ATTENTION, Not ready to ready >> change, medium may have changed >> >> # camcontrol devlist >> at scbus1 target 0 lun 0 (da0,pass0) >> same as above - --- lun 1 (pass1,cd0) >> > > It would be good if you provide the full dmesg lines that > are corresponding with this problem. > > By the way, I had problems with "defective by design" SanDisk > USB sticks, too. This is how it looked: > > % dmesg | tail > umass0: on uhub2 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Removable Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present > umass0: at uhub2 port 2 (addr 2) disconnected > (da0:umass-sim0:0:0:0): lost device > (da0:umass-sim0:0:0:0): removing device entry > umass0: detached > > I could not access the stick, /dev/da0 was the only device > that appeared, and I could only dump the partition table > (in terms of "DOS primary partitions", i. e. slices) with > the "fdisk da0" command. But I could not access it. > > Finally, I printed out dmesg on a line printer (looks very > impressing), marked the lines shown above and returned it to > the shop. I'm now happy with a Sony USB stick which works > excellently. > > > > >> Something is not functioning & I don't understand. It did function a >> while (some weeks) ago but now, no go... >> > > It did function, and now no more? I would say that if you didn't > change anything on your system, the SanDisk stick is broken. > > Could you try the stick in another system for reference? > > > > >> I did look on the web, but... >> >> > > Did you see a spider that made the web? :-) > Yeah, and it scared the shit out of me... ;-) Anyway, I found the solution on the web... couldn't belive it was that simple: just ignore the crap spewed out on the screen and just mount iit as you would any other disk. # mount -t msdosfs /dev/da0s1 /mnt and that's it I don't know if it makes any difference, but I did delete everything on the key and formatted with Fat32. That got rid of everything and only took up 4k instead of 32 when not formatted and I could put my own label on the disk. Yea! Now to see how I can use it to restore stuff. :-D ___ 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: usb key problem
On Thu, 15 Oct 2009 19:18:45 -0400, PJ wrote: > Now that I have had a few moments to think about it, maybe I have to > give good old cruze and enema and format it under XP ... maybe all it > needs is a clean system on it. ;-) I'm not sure if USB sticks tend to degrade filesystem-wise, but when you put such a stick into random "Windows" PCs, it's quite possible that data gets messed up. The most ideal solution of course is to simply newfs the stick and give it a UFS file system, but sadly, "Windows" PC are resistent to standards, so they won't read it, but will force you to use old-fashioned MS-DOS-like file systems. :-) -- 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: booting from wrong disk
On Thu, 15 Oct 2009 19:08:12 -0400, PJ wrote: > Gag is really about the simplest you can find... it is installed on the > main drive that is selected by bios and it works from there. I have > found it to be quite safe and reliable. Only difficulty is sometimes to > figure ;out what dist it is booting from but that can be worked out be > trial and error. I've tried the rest, this is the best KISS. The last time I did dual boot is long ago; I used FreeBSD's boot manager for this, it worked well, so there was no need for something else to try. :-) > the boot... it could be seen in the onscreen mesages... and then the > boot oviously failed... Seems that the first boot stage finds ad12 BEFORE ad4, which is quite strange... or is the setting hardcoded somewhere in the boot loader? > I noticed that but have not yet had the opportunity to look into it. That would be a good point to start diagnostics. The most obvious is often such a point... > The fstab did cure the problem and showed some of the pitfalls one can > encounter. After fixing the fstab, the boot did not complete because the > fstab from the source disk had anextra partition (/backups) which were > not present in the original ad4 disk. But that was easiily fixed by > simply removing the fstab entry for that /backups partition. Now it > works fine. Excellent! And you have learned something new. :-) -- 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: usb key problem
On Thu, 15 Oct 2009 18:19:16 -0400, PJ wrote: > I am running 7.2 but cannot properly attach/detach cruze 8gb and 4gb USB > keys. > When inserted, generate errors: > da0 seems to be read correctly > but then comes arow of > (probe0:umass-sim0:0:0:1): snip CAM Status: SCSI Status Error > snip NOT READY asc:3a,0 > Medium not present > Unretryable error > then > cd0 at umass-sim0 dada,dada,dada > attempt to query device size failed; UNIT ATTENTION, Not ready to ready > change, medium may have changed > > # camcontrol devlist > at scbus1 target 0 lun 0 (da0,pass0) > same as above - --- lun 1 (pass1,cd0) It would be good if you provide the full dmesg lines that are corresponding with this problem. By the way, I had problems with "defective by design" SanDisk USB sticks, too. This is how it looked: % dmesg | tail umass0: on uhub2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: Attempt to query device size failed: UNIT ATTENTION, Medium not present umass0: at uhub2 port 2 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached I could not access the stick, /dev/da0 was the only device that appeared, and I could only dump the partition table (in terms of "DOS primary partitions", i. e. slices) with the "fdisk da0" command. But I could not access it. Finally, I printed out dmesg on a line printer (looks very impressing), marked the lines shown above and returned it to the shop. I'm now happy with a Sony USB stick which works excellently. > Something is not functioning & I don't understand. It did function a > while (some weeks) ago but now, no go... It did function, and now no more? I would say that if you didn't change anything on your system, the SanDisk stick is broken. Could you try the stick in another system for reference? > I did look on the web, but... > Did you see a spider that made the web? :-) -- 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: usb key problem
PJ wrote: > I am running 7.2 but cannot properly attach/detach cruze 8gb and 4gb USB > keys. > When inserted, generate errors: > da0 seems to be read correctly > but then comes arow of > (probe0:umass-sim0:0:0:1): snip CAM Status: SCSI Status Error > snip NOT READY asc:3a,0 > Medium not present > Unretryable error > then > cd0 at umass-sim0 dada,dada,dada > attempt to query device size failed; UNIT ATTENTION, Not ready to ready > change, medium may have changed > > # camcontrol devlist > at scbus1 target 0 lun 0 (da0,pass0) > same as above - --- lun 1 (pass1,cd0) > > Something is not functioning & I don't understand. It did function a > while (some weeks) ago but now, no go... > I did look on the web, but... > > > Now that I have had a few moments to think about it, maybe I have to give good old cruze and enema and format it under XP ... maybe all it needs is a clean system on 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: how to prepare disk for dump/restore
Tobias Rehbein wrote: > Am Thu, Oct 15, 2009 at 09:17:43PM +0200 schrieb Polytropon: > >> On Thu, 15 Oct 2009 14:59:51 -0400, PJ wrote: >> >> You can use sysinstall from the Fixit CD, too. That's the way >> I'm mostly doing this kind of thing: Preparing the disk with >> the sysinstall tool, then dropping to CLI for the restoring >> process. >> > > If all you want to do is to prepare the disks you can leave sysinstall alone > and > use sade(8). > > Hmmm, very, very interesting... Will check it out. 8-) ___ 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 prepare disk for dump/restore
Polytropon wrote: > On Thu, 15 Oct 2009 14:59:51 -0400, PJ wrote: > >> I would like to just partition, label and newfs the disk; livefs wants >> to waste my time by installing other stuff like the kernel & man pages >> etc that I have not even selected; >> > > Just don't go through the whole installation cycle; from the > sysinstall main menu, select "Custom" and perform slicing > (setting disk active, adding standard MBR) and partitioning > (creating partitions, format them with "w" or "z"). Then > leave the menu and use the shell. You can get to the "Fdisk" > and "Label" through "Configure" in the main menu, too. > > > > >> and if I use postinstall >> configuration, that doesn't do anything. Or should I use fixit and then >> do the manual thing? >> > > You can use sysinstall from the Fixit CD, too. That's the way > I'm mostly doing this kind of thing: Preparing the disk with > the sysinstall tool, then dropping to CLI for the restoring > process. > > > > >> Sysinstall requires already being booted... ??? >> > > No. You can execute it even on a running system. > That's what I meant. :-) > > > >> Or do I do it manually as per Polytropon's recipe of fdisk, bsdlabel, >> newfs mount, dump/restore and use/play? ;-) >> > > This method is quite usable when you completely understood what > you're doing; furthermore, it enables scripting automated > processes, which is very handy especially when you want to > provide larger numbers of cloned systems. > > In any case: Be sure which device you're operating on, and keep > in mind that it may (!) be a different device when in the place > where it should go. > > For example, if you intend to prepare a disk to be ad4 in the > target system, let it be (if possible) ad4 in the source system, > and boot your source system from ad12. From this running system, > perform the cloning. If everything is done, check references > for ad12 and change them to ad4 (even *that* can be scripted); > eyes on /etc/fstab. After you've done everything, shut down the > running system, unplug ad12 and let the system boot from ad4. > Everything should be alright now. Extract ad4 and take it to > its new system. > I think i'm at the stage where my stumbling is beginning to get straightened out... ;-) ___ 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: booting from wrong disk
Polytropon wrote: > On Thu, 15 Oct 2009 14:42:24 -0400, PJ wrote: > >> But sysinstall will overwrite all the info on the disk and that defeats >> the whole purpose of the exercise. >> > > If you only change a slice's state and add an MBR, it won't > do anything to the data inside the slice. > > > > >> What complicates matters is the use of GAG as boot manager. >> > > Hmmm... I'm not familar with that, nor have I ever heared of > it. > > > > >> If I select >> to boot from ad4 and the boot is from ad12, then there is something >> wrong. >> > > Check /etc/fstab as suggested. Furthermore, check what GAG > actually does - just to be sure it boots the correct device. > I always assumed that you use the standard MBR which does, > as I explained, simply boot the first "active" slice on the > first disk it finds. Maybe GAG acts differently. > > Gag is really about the simplest you can find... it is installed on the main drive that is selected by bios and it works from there. I have found it to be quite safe and reliable. Only difficulty is sometimes to figure ;out what dist it is booting from but that can be worked out be trial and error. I've tried the rest, this is the best KISS. > > >> It indicates to me that the mbr is loading the wrong disk. >> > > In this case, it's good to read how booting works. MBR, and > bootN, the FreeBSD loader and the kernel own specified points > in this race. :-) > > > > >> I noticed this when trying to boot a disk on my other computer... it was >> looking for ad12 when there was no ad12 installed. >> > > "Who" was looking for ad12? Was it at the "boot>" or the "Ok" > prompt? > the boot... it could be seen in the onscreen mesages... and then the boot oviously failed... > > > >> I found that strange, >> but then I recalled thatManolis Klagias had warned about something of >> the sort. Now, I'll have to sort that out. >> > > You have to be entirely sure that the booting process works as > intended. The easiest way to ensure this is to first use only > one disk at once in the system. There are different stages where > things can get messed up, such as the loader or /etc/fstab. > They have to match the situation. > > As a sidenote, GEOM supports labelling partitions so it does not > matter anymore if, for example, a / partition is ad4s1a or ad12s1a. > There's a section in the handbook that illustrates how to get rid > of device names in /etc/fstab. > I noticed that but have not yet had the opportunity to look into it. The fstab did cure the problem and showed some of the pitfalls one can encounter. After fixing the fstab, the boot did not complete because the fstab from the source disk had anextra partition (/backups) which were not present in the original ad4 disk. But that was easiily fixed by simply removing the fstab entry for that /backups partition. Now it works fine. > > > > > ___ 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: network setup
On Thu, Oct 15, 2009 at 4:42 PM, Ilych narmonov wrote: > Guys, > > I'm new with freeBSD setup. I hope somebody here who will give some links > on how I will buil my network using freeBSD. > > I'm planning to use it as my router and dhcp server. > > > Thanks everyone.. > > > Carlos Narmonov > ___ > 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" > Here you'll find specifics on virtually all common tasks including the ones you mentioned. http://www.freebsd.org/doc/en/books/handbook/ -- 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"
network setup
Guys, I'm new with freeBSD setup. I hope somebody here who will give some links on how I will buil my network using freeBSD. I'm planning to use it as my router and dhcp server. Thanks everyone.. Carlos Narmonov ___ 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"
usb key problem
I am running 7.2 but cannot properly attach/detach cruze 8gb and 4gb USB keys. When inserted, generate errors: da0 seems to be read correctly but then comes arow of (probe0:umass-sim0:0:0:1): snip CAM Status: SCSI Status Error snip NOT READY asc:3a,0 Medium not present Unretryable error then cd0 at umass-sim0 dada,dada,dada attempt to query device size failed; UNIT ATTENTION, Not ready to ready change, medium may have changed # camcontrol devlist at scbus1 target 0 lun 0 (da0,pass0) same as above - --- lun 1 (pass1,cd0) Something is not functioning & I don't understand. It did function a while (some weeks) ago but now, no go... I did look on the web, but... ___ 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: phpMyAdmin install stopped in dependency 'libXau-1.0.4'
Kikachi Kozumi wrote: > Hi, > > I tried installing phpMyAdmin in an ezjail created jail already > installed with apache22, mysql and php5 running FreeBSD 7.1-RELEASE > i386 with no X11 (headless). > The port install failed when dependency 'libXau-1.0.4' configure > couldn't find gnome-config: > > ... > checking for XAU... gnome-config: not found > configure: error: Package requirements (xproto) were not met. > ... > > I'm not sure if this issue is specific to my system or is it a ports > issue but I found that libXau-1.0.4 was in the ports tree since > January 2009 so it's less likely to be an issue with the port itself. > > Right now I'm not sure if the required gnome-config is lost from my > system or was never there in the 1st place. What can I do to continue > with phpMyAdmin installation? > > I'm also curious why the phpMyAdmin port requires libX11 libraries to > build while the phpMyAdmin website states that php, mysql and apache > are the requirements for running phpMyAdmin? > [snip] Try placing WITHOUT_X11=yes into /etc/make.conf so it will build without the X related nonsense. -Mike ___ 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"
phpMyAdmin install stopped in dependency 'libXau-1.0.4'
Hi, I tried installing phpMyAdmin in an ezjail created jail already installed with apache22, mysql and php5 running FreeBSD 7.1-RELEASE i386 with no X11 (headless). The port install failed when dependency 'libXau-1.0.4' configure couldn't find gnome-config: ... checking for XAU... gnome-config: not found configure: error: Package requirements (xproto) were not met. ... I'm not sure if this issue is specific to my system or is it a ports issue but I found that libXau-1.0.4 was in the ports tree since January 2009 so it's less likely to be an issue with the port itself. Right now I'm not sure if the required gnome-config is lost from my system or was never there in the 1st place. What can I do to continue with phpMyAdmin installation? I'm also curious why the phpMyAdmin port requires libX11 libraries to build while the phpMyAdmin website states that php, mysql and apache are the requirements for running phpMyAdmin? Below are the outputs from my system when phpMyAdmin build failed: # cd /usr/ports/databases/phpmyadmin # make install clean ===> Installing for phpMyAdmin-3.2.2.1 ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/include/php/main/php.h - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/ctype.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/mysql.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/session.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/spl.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/filter.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/bz2.so - found ===> phpMyAdmin-3.2.2.1 depends on file: /usr/local/lib/php/20060613/gd.so - not found ===>Verifying install for /usr/local/lib/php/20060613/gd.so in /usr/ports/graphics/php5-gd ===> php5-gd-5.2.11_1 depends on file: /usr/local/bin/phpize - found ===> php5-gd-5.2.11_1 depends on file: /usr/local/libdata/pkgconfig/xpm.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xpm.pc in /usr/ports/x11/libXpm ===> libXpm-3.5.7 depends on file: /usr/local/libdata/pkgconfig/xextproto.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xextproto.pc in /usr/ports/x11/xextproto ===> Returning to build of libXpm-3.5.7 ===> libXpm-3.5.7 depends on file: /usr/local/libdata/pkgconfig/xproto.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xproto.pc in /usr/ports/x11/xproto ===> Returning to build of libXpm-3.5.7 ===> libXpm-3.5.7 depends on file: /usr/local/libdata/pkgconfig/x11.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/x11.pc in /usr/ports/x11/libX11 ===> libX11-1.2.1_1,1 depends on file: /usr/local/libdata/pkgconfig/xcb.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xcb.pc in /usr/ports/x11/libxcb ===> libxcb-1.4 depends on file: /usr/local/lib/libcheck.a - found ===> libxcb-1.4 depends on executable: xsltproc - found ===> libxcb-1.4 depends on file: /usr/local/libdata/pkgconfig/xcb-proto.pc - found ===> libxcb-1.4 depends on package: xcb-proto>=1.5 - found ===> libxcb-1.4 depends on file: /usr/local/libdata/pkgconfig/pthread-stubs.pc - found ===> libxcb-1.4 depends on file: /usr/local/bin/python2.6 - found ===> libxcb-1.4 depends on executable: gmake - found ===> libxcb-1.4 depends on file: /usr/local/libdata/pkgconfig/xau.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xau.pc in /usr/ports/x11/libXau ===> libXau-1.0.4 depends on file: /usr/local/libdata/pkgconfig/xproto.pc - not found ===>Verifying install for /usr/local/libdata/pkgconfig/xproto.pc in /usr/ports/x11/xproto ===> Returning to build of libXau-1.0.4 ===> libXau-1.0.4 depends on executable: pkg-config - found ===> Configuring for libXau-1.0.4 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether build environment is sane... yes checking for a thread-safe mkdir -p... ./install-sh -c -d checking for gawk... no checking for mawk... no checking for nawk... nawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking if xorg-macros used to generate configure is at least 1.1... yes, 1.1.6 checking for gcc... cc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether cc accepts -g... yes checking for cc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of cc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking whether ln -s works...
Re: how to prepare disk for dump/restore
On Thu, 15 Oct 2009 21:31:20 +0200, Tobias Rehbein wrote: > If all you want to do is to prepare the disks you can leave sysinstall alone > and > use sade(8). Very good advice! Sadly, it makes me feel that all my knowledge is very outdated because sade didn't come into my mind at fist place. :-) The use of sysinstall is just a suggestion when you're booting from a FreeBSD live file system, so you end up in sysinstall anyway. On a system already running, sade definitely is the better tool. -- 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 prepare disk for dump/restore
Am Thu, Oct 15, 2009 at 09:17:43PM +0200 schrieb Polytropon: > On Thu, 15 Oct 2009 14:59:51 -0400, PJ wrote: > > You can use sysinstall from the Fixit CD, too. That's the way > I'm mostly doing this kind of thing: Preparing the disk with > the sysinstall tool, then dropping to CLI for the restoring > process. If all you want to do is to prepare the disks you can leave sysinstall alone and use sade(8). -- Tobias Rehbein PGP key: 4F2AE314 server: keys.gnupg.net fingerprint: ECDA F300 1B6E 9B87 8524 8663 E8B6 3138 4F2A E314 pgpXD2nA0ImOP.pgp Description: PGP signature
Re: how to prepare disk for dump/restore
On Thu, 15 Oct 2009 14:59:51 -0400, PJ wrote: > I would like to just partition, label and newfs the disk; livefs wants > to waste my time by installing other stuff like the kernel & man pages > etc that I have not even selected; Just don't go through the whole installation cycle; from the sysinstall main menu, select "Custom" and perform slicing (setting disk active, adding standard MBR) and partitioning (creating partitions, format them with "w" or "z"). Then leave the menu and use the shell. You can get to the "Fdisk" and "Label" through "Configure" in the main menu, too. > and if I use postinstall > configuration, that doesn't do anything. Or should I use fixit and then > do the manual thing? You can use sysinstall from the Fixit CD, too. That's the way I'm mostly doing this kind of thing: Preparing the disk with the sysinstall tool, then dropping to CLI for the restoring process. > Sysinstall requires already being booted... ??? No. You can execute it even on a running system. > Or do I do it manually as per Polytropon's recipe of fdisk, bsdlabel, > newfs mount, dump/restore and use/play? ;-) This method is quite usable when you completely understood what you're doing; furthermore, it enables scripting automated processes, which is very handy especially when you want to provide larger numbers of cloned systems. In any case: Be sure which device you're operating on, and keep in mind that it may (!) be a different device when in the place where it should go. For example, if you intend to prepare a disk to be ad4 in the target system, let it be (if possible) ad4 in the source system, and boot your source system from ad12. From this running system, perform the cloning. If everything is done, check references for ad12 and change them to ad4 (even *that* can be scripted); eyes on /etc/fstab. After you've done everything, shut down the running system, unplug ad12 and let the system boot from ad4. Everything should be alright now. Extract ad4 and take it to its new system. -- 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: booting from wrong disk
On Thu, 15 Oct 2009 14:42:24 -0400, PJ wrote: > But sysinstall will overwrite all the info on the disk and that defeats > the whole purpose of the exercise. If you only change a slice's state and add an MBR, it won't do anything to the data inside the slice. > What complicates matters is the use of GAG as boot manager. Hmmm... I'm not familar with that, nor have I ever heared of it. > If I select > to boot from ad4 and the boot is from ad12, then there is something > wrong. Check /etc/fstab as suggested. Furthermore, check what GAG actually does - just to be sure it boots the correct device. I always assumed that you use the standard MBR which does, as I explained, simply boot the first "active" slice on the first disk it finds. Maybe GAG acts differently. > It indicates to me that the mbr is loading the wrong disk. In this case, it's good to read how booting works. MBR, and bootN, the FreeBSD loader and the kernel own specified points in this race. :-) > I noticed this when trying to boot a disk on my other computer... it was > looking for ad12 when there was no ad12 installed. "Who" was looking for ad12? Was it at the "boot>" or the "Ok" prompt? > I found that strange, > but then I recalled thatManolis Klagias had warned about something of > the sort. Now, I'll have to sort that out. You have to be entirely sure that the booting process works as intended. The easiest way to ensure this is to first use only one disk at once in the system. There are different stages where things can get messed up, such as the loader or /etc/fstab. They have to match the situation. As a sidenote, GEOM supports labelling partitions so it does not matter anymore if, for example, a / partition is ad4s1a or ad12s1a. There's a section in the handbook that illustrates how to get rid of device names in /etc/fstab. -- 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: torrentflux
Ok, now is up and running. In case any of you have the same problem try this ones: Search in httpd.conf for /usr/local/www/apache22/data and replace it with /usr/local/www/data Have a nice day! Laci From: Dánielisz László Subject: Re: torrentflux I found out that there is an httpd.conf problem, I fixed that but now I'm thinking how to put php module in apache without reinstalling apache. From: Polytropon To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Thu, October 15, 2009 8:22:04 PM Subject: Re: torrentflux On Thu, 15 Oct 2009 10:19:55 -0700 (PDT), Dánielisz László wrote: > Hello, > > Ok, I know it sounds numb, but how can I actually start > torrentflux on my freebsd machine? I haven't used this torrent client so far (ctorrent is my choice at the moment), but according to > # pkg_info |grep torrent > torrentflux-2.0.b1 A PHP based BitTorrent client that runs on a web server it seems that you have to run a web server (I think locally), e. g. Apache, and then connect to this server in order to perform the actions with your client, such as entering http://127.0.0.1 in your web browser - this assumes that the web server is running and the PHP script is properly installed. It's possible that you need to connect to a specific port (e. g. ":631" after the local IP). > but I can not find how to start it and torrentflux forum > is down, do you have any idea? Doesn't torrentflux come with some documentation? Have a look for it in /usr/local/share/doc where it should be. The packagin list in the port's directory mentions "install.txt", maybe this file contains the information needed? Finally, does torrentflux.com (the homepage of the project) have some information? -- 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" ___ 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"
how to prepare disk for dump/restore
I would like to just partition, label and newfs the disk; livefs wants to waste my time by installing other stuff like the kernel & man pages etc that I have not even selected; and if I use postinstall configuration, that doesn't do anything. Or should I use fixit and then do the manual thing? Sysinstall requires already being booted... ??? Or do I do it manually as per Polytropon's recipe of fdisk, bsdlabel, newfs mount, dump/restore and use/play? ;-) ___ 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: booting from wrong disk
Polytropon wrote: > On Thu, 15 Oct 2009 12:22:29 -0600 (MDT), Warren Block > wrote: > >> The /etc/fstab from ad12 will point at ad12. After restoring on ad4, >> did you edit fstab to now have ad4 entries? >> > > Ha! Excellent point; I missed to see this obvious thing. > Next to booting, the /etc/fstab mechanism is very important > to have a look at when cloning disks that will have a > different "signature" in the target than in the source. > > > AHA! Now, we're getting somewhere... cut's the workload. ;-) I'll try it ASAP. ___ 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: Graphics card recommendation
On Wed,14-10-2009 [23:48:26], Polytropon wrote: > On Wed, 14 Oct 2009 10:55:05 -0600 (MDT), Warren Block > wrote: > > All of my cards are ATI and I don't know of the "mtrr" problem you're > > talking about. This X1650 works fine on i386 with both 7-STABLE and > > 8-STABLE. > > I had an old-fashioned ATI Radeon 9200 RV250 AGP with both a VGA > and a VGA-on-DVI monitor. With also old-fashioned XFree86 this > setting worked good performance-wise, which was in FreeBSD 5, > but I haven't tested this in FreeBSD 7 with Xorg yet because > I'm very upset about the speed-loss of "modern" software. :-( > Furthermore, I don't have the second 21" CRT anymore, so no > dual-head for me at the moment. > > I am nearly sure that for today's requirements, Intel GPUs > seem to be the most fitting ones, but as I don't own any of > them, I can't give you clues from a user's point of view. > In the past, ATI always was my first choice, but today, I > would triple-check anything. > Having had a _lot_ of troubles with Intel video recently I'd not recommend using it. Poor performance (both 2D and 3D) and various glitches after several updates of intel-video driver. And still having that bug with broken xv out driver of mplayer. :( -- Best regards, Jeff | "Nobody wants to say how this works. | | Maybe nobody knows ..." | | Xorg.conf(5)| ___ 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: booting from wrong disk
Polytropon wrote: > On Thu, 15 Oct 2009 12:13:08 -0400, PJ wrote: > >> add another thought... >> >> If I change the mbr on the ad12 then mount ad4s1a to /mnt copy >> /mnt/boot/boot0 to /boot/boot0.tmp and then copy the modified >> /boot/boot0 (for ad4) back to /mnt/boot/ and then umount ad4s1a --- I >> should be ok, OK? Have I got it? >> > > Why not just remove the "active" marking from the disk you do > not want to be booted from? Furthermore, I'm not sure if the > desired operation can be performed UFS-file-wise... > > The easiest way really is to use sysinstall. It's the lazy man's > swiss army knife. :-) > > > Yeh, but even with a swill army knife you can cut yourself. ;-) But sysinstall will overwrite all the info on the disk and that defeats the whole purpose of the exercise. What complicates matters is the use of GAG as boot manager. If I select to boot from ad4 and the boot is from ad12, then there is something wrong. It indicates to me that the mbr is loading the wrong disk. I noticed this when trying to boot a disk on my other computer... it was looking for ad12 when there was no ad12 installed. I found that strange, but then I recalled thatManolis Klagias had warned about something of the sort. Now, I'll have to sort that out. And you think you're lazy... this is back-braking work for me... :-D ___ 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: booting from wrong disk
On Thu, 15 Oct 2009 12:22:29 -0600 (MDT), Warren Block wrote: > The /etc/fstab from ad12 will point at ad12. After restoring on ad4, > did you edit fstab to now have ad4 entries? Ha! Excellent point; I missed to see this obvious thing. Next to booting, the /etc/fstab mechanism is very important to have a look at when cloning disks that will have a different "signature" in the target than in the source. -- 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: torrentflux
I found out that there is an httpd.conf problem, I fixed that but now I'm thinking how to put php module in apache without reinstalling apache. From: Polytropon To: Dánielisz László Cc: freebsd-questions@freebsd.org Sent: Thu, October 15, 2009 8:22:04 PM Subject: Re: torrentflux On Thu, 15 Oct 2009 10:19:55 -0700 (PDT), Dánielisz László wrote: > Hello, > > Ok, I know it sounds numb, but how can I actually start > torrentflux on my freebsd machine? I haven't used this torrent client so far (ctorrent is my choice at the moment), but according to > # pkg_info |grep torrent > torrentflux-2.0.b1 A PHP based BitTorrent client that runs on a web server it seems that you have to run a web server (I think locally), e. g. Apache, and then connect to this server in order to perform the actions with your client, such as entering http://127.0.0.1 in your web browser - this assumes that the web server is running and the PHP script is properly installed. It's possible that you need to connect to a specific port (e. g. ":631" after the local IP). > but I can not find how to start it and torrentflux forum > is down, do you have any idea? Doesn't torrentflux come with some documentation? Have a look for it in /usr/local/share/doc where it should be. The packagin list in the port's directory mentions "install.txt", maybe this file contains the information needed? Finally, does torrentflux.com (the homepage of the project) have some information? -- 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" ___ 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: booting from wrong disk
On Thu, 15 Oct 2009, PJ wrote: While trying to learn and understand the dump-retore process, I messed up the ad4s1a partition and could not boot. To fix it I restored a dumpfile of ad12s1a which is, for all intents and purposes, the same as ad4s1a. I then boot from ad4 and surprise, surprise... #df shows we have been booted from ad12 and all partitions are ad12 Booting from ad12s1a gives exactly the same results. The /etc/fstab from ad12 will point at ad12. After restoring on ad4, did you edit fstab to now have ad4 entries? -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: torrentflux
On Thu, 15 Oct 2009 10:19:55 -0700 (PDT), Dánielisz László wrote: > Hello, > > Ok, I know it sounds numb, but how can I actually start > torrentflux on my freebsd machine? I haven't used this torrent client so far (ctorrent is my choice at the moment), but according to > # pkg_info |grep torrent > torrentflux-2.0.b1 A PHP based BitTorrent client that runs on a web server it seems that you have to run a web server (I think locally), e. g. Apache, and then connect to this server in order to perform the actions with your client, such as entering http://127.0.0.1 in your web browser - this assumes that the web server is running and the PHP script is properly installed. It's possible that you need to connect to a specific port (e. g. ":631" after the local IP). > but I can not find how to start it and torrentflux forum > is down, do you have any idea? Doesn't torrentflux come with some documentation? Have a look for it in /usr/local/share/doc where it should be. The packagin list in the port's directory mentions "install.txt", maybe this file contains the information needed? Finally, does torrentflux.com (the homepage of the project) have some information? -- 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: booting from wrong disk
On Thu, 15 Oct 2009 12:13:08 -0400, PJ wrote: > add another thought... > > If I change the mbr on the ad12 then mount ad4s1a to /mnt copy > /mnt/boot/boot0 to /boot/boot0.tmp and then copy the modified > /boot/boot0 (for ad4) back to /mnt/boot/ and then umount ad4s1a --- I > should be ok, OK? Have I got it? Why not just remove the "active" marking from the disk you do not want to be booted from? Furthermore, I'm not sure if the desired operation can be performed UFS-file-wise... The easiest way really is to use sysinstall. It's the lazy man's swiss army knife. :-) -- 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: booting from wrong disk
On Thu, 15 Oct 2009 12:07:17 -0400, PJ wrote: > I see from the boot process that this should fix it... > # fdisk -B -b /boot/boot0 ad4 > but... > how do I get this onto the right disk? If I boot from ad4 or ad12 and > change the mbr, then it will be the ad12 that will be booting from ad4 > and vice versa... or have I got it wrong? But in the end, I suppose it > really doesn't matter, or does it? The "active" flag on the partition tells the MBR loader from which device to boot. In other words, the FIRST device that is market as "active" will be booted. If you have, for example, ad4 ad ad12 in your system, and ad4 is detected first, then it will be booted, no matter if ad12 is marked "active", too. Of course, ad4's boot loader can refer to another device as bootdev (booting device), but that's out of scope for now. If you have two disks ad4 and ad12, both marked "active", and you exchange them physically, boot order will change, too. A similar setting could involve things like a mix of ATA, SCSI and SATA disks. Again, who comes first will be booted - but as I said, only if the device is marked "active"; if not, it will be ignored. -- 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: booting from wrong disk
On Thu, 15 Oct 2009 11:36:56 -0400, PJ wrote: > I imagine it is something in the boot files... but how to fix that? The easiest way is to prepare the disk with sysinstall. The steps usually involve: 1. creation of slice, usually covering whole disk 2. marking the slice "active" 3. installing the standard MBR 4. partitioning the slice as intended 5. format the partitions And as I said, sysinstall's slice and partition editor are often my tools of choice, allthough you can do all this with the correct command line tools (which you obviously do when scripting automated processes). -- 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"
torrentflux
Hello, Ok, I know it sounds numb, but how can I actually start torrentflux on my freebsd machine? I installed by ports ... # pkg_info |grep torrent torrentflux-2.0.b1 A PHP based BitTorrent client that runs on a web server but I can not find how to start it and torrentflux forum is down, do you have any idea? Thank you! Laci ___ 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"
Request for Text Link
-- Hi, I am looking for relevant material and I found your website " http://www.pl.freebsd.org/"; really informative. I would like to do business with you. I basically have an offer of buying text-links on your site. Let me know if you would be interested in hearing more. Kind regards Sherry ___ 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: booting from wrong disk
PJ wrote: > While trying to learn and understand the dump-retore process, I messed > up the ad4s1a partition and could not boot. To fix it I restored a > dumpfile of ad12s1a which is, for all intents and purposes, the same as > ad4s1a. I then boot from ad4 and surprise, surprise... > #df shows we have been booted from ad12 and all partitions are ad12 > Booting from ad12s1a gives exactly the same results. > So, how can I get ad4s1a to boot from ad4? > I imagine it is something in the boot files... but how to fix that? > ___ > 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" > > add another thought... If I change the mbr on the ad12 then mount ad4s1a to /mnt copy /mnt/boot/boot0 to /boot/boot0.tmp and then copy the modified /boot/boot0 (for ad4) back to /mnt/boot/ and then umount ad4s1a --- I should be ok, OK? Have I got 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: booting from wrong disk
PJ wrote: > While trying to learn and understand the dump-retore process, I messed > up the ad4s1a partition and could not boot. To fix it I restored a > dumpfile of ad12s1a which is, for all intents and purposes, the same as > ad4s1a. I then boot from ad4 and surprise, surprise... > #df shows we have been booted from ad12 and all partitions are ad12 > Booting from ad12s1a gives exactly the same results. > So, how can I get ad4s1a to boot from ad4? > I imagine it is something in the boot files... but how to fix that? > ___ > 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 see from the boot process that this should fix it... # fdisk -B -b /boot/boot0 ad4 but... how do I get this onto the right disk? If I boot from ad4 or ad12 and change the mbr, then it will be the ad12 that will be booting from ad4 and vice versa... or have I got it wrong? But in the end, I suppose it really doesn't matter, or does 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: ZFS boot
I just ran into the very same problem, although I use UFS instead of ZFS, but I think this doesn't matter for this problem. I updated to tinyBIOS v0.99h and now it works fine. Cheers, Anselm > Hi, > > I'm trying to boot a PC-engines board off GPT+ZFS, but the GPT MBR does not > support CHS layout and requests data per LBA, which the PC Engines BIOS > does > not support. > > Anyone have a solution for this laying around? > > --HPS > > PC Engines ALIX.2 v0.99 > 640 KB Base Memory > 261120 KB Extended Memory > > 01F0 Master 044A CF 1GB > Phys C/H/S 1966/16/63 Log C/H/S 983/32/63 > Invalid partition table > > sys/boot/i386/pmbr > > %grep Invalid pmbr.s > err_pt: movw $msg_pt,%si# "Invalid partition > msg_pt: .asciz "Invalid partition table" ___ 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 this Intel CPU ok for 7.2 AMD64?
> > Does it matter whether I run IA64 or AMD64 in the above Dell 1850? > > Len > This is a case where I wish the architecture types were renamed to modern day nomenclature. Most people outside the *nix world know i386 as the x86 architecture and AMD64 as either x86-64 or straight x64. IA64 is for Itanium architecture only and will not work on any x86 or derrived architecture. -Sean ___ 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"
booting from wrong disk
While trying to learn and understand the dump-retore process, I messed up the ad4s1a partition and could not boot. To fix it I restored a dumpfile of ad12s1a which is, for all intents and purposes, the same as ad4s1a. I then boot from ad4 and surprise, surprise... #df shows we have been booted from ad12 and all partitions are ad12 Booting from ad12s1a gives exactly the same results. So, how can I get ad4s1a to boot from ad4? I imagine it is something in the boot files... but how to fix that? ___ 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: FWD: is this Intel CPU ok for 7.2 AMD64?
On Thu, Oct 15, 2009 at 03:13:49PM +0200, Len Conrad wrote: > > -- Original Message -- > From: "Len Conrad" > Reply-To: > Date: Wed, 14 Oct 2009 22:48:26 +0200 > > the FreeBSD 6.2 i386 dmesg.boot shows: > > CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > > Features=0xbfebfbff > Features2=0x659d> > AMD Features=0x2010 > Logical CPUs per core: 2 > real memory = 3220963328 (3071 MB) > avail memory = 3150913536 (3004 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0: Changing APIC ID to 8 > ioapic1: Changing APIC ID to 9 > ioapic1: WARNING: intbase 32 != expected base 24 > ioapic2: Changing APIC ID to 10 > ioapic2: WARNING: intbase 64 != expected base 56 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 32-55 on motherboard > ioapic2 irqs 64-87 on motherboard > > thanks, > Len > > == > > So, is there a definite, unique answer? Yes. > > Does it matter whether I run IA64 or AMD64 in the above Dell 1850? > Yes. Run AMD64. It is not an Itanium which is the IA64. It is a I686 which is the long standing ...86 family which, in 64 bit is supported on FreeBSD by AMD64. jerry > Len > > > > ___ > 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: Best procedure for full backup of live system
On Wed, Oct 14, 2009 at 08:42:47PM -0700, Nerius Landys wrote: > My server is increasingly having important work stored on it, and I > need to start taking backups of a lot of directories, especially > /home, /opt, /etc, /usr/local/etc, and maybe others. The ideal backup > (and what I've done in the past) is to take a full low-level dd image > of the disk while the system is down (this is easy to do in a > situation where you have dual boot). Or, since the output of dd would > take up tons of space and would only be usable on an identical hard > drive, use "dump" to take the backup while the machine is turned off > (again easy to do on a dual boot). But now, I cannot bring down the > machine. My plan is to do a tar gzip of / on the fly, and pipe that > to ssh (remote machine). However, the system is live, and files will > be in the progress of changing. > > My question is, what is the recommended procedure of taking a full > backup on a live system? Ideally, if my hard drive were to crash, I > would like to have such a backup so as to make it possible to copy > over the entire backup to a new identical harddrive without doing any > reinstall or configuration. Should I use tar/gzip? dump? What exact > command should I use? I guess I'll back up all of / including system > files, because there is not too much data. I will be piping the > output to ssh. Use dump(8) to back up each filesystem that is important and that cannot be easily recreated (such as by reinstalling). Don't bother with any of that tar and dd stuff as long as the dump will be read on a similar system (FreeBSD). Use the -L switch for making a dump on a live filesystem. It forces a snapshot so files are not in transition while the backup is done - or rather, makes it so the backup is of an intact image. Your big issue then is where to write the dump, how often to do it and how many copies you want to keep of it. You can do full dumps and dumps of just what has changed since the last time a file was dumped. I call those full dumps and change dumps. The documentation referrs to them as level 0 for full dump and level 1-9 as the change dumps. The man pages give a complicated scheme for managing full and change dumps. Probably most people really need only a level 0 and a level 1, maybe a level 2. Basically the point of the change dumps is to make smaller backup images which takes less time and less media. You only make the full dump (level 0) once every week or every month - whatever your needs are. Then, in between you only dump the files that have changed since the last full dump. If that change dump file gets too big as well, then you jump to the next level on change dump. So, you do a level 0, then, the next day a level 1. If it is small (meaning only a relatively few files have changed) then the third day you still make a level 1. If the level 1 dump is now real big (meaning a lot of files changed) then on day 4 you go to a level 2 dump, etc. It is probably a good idea to regularize the process of choosing levels. That is why the man page has such a complicated scheme that covers all conditions. But, as I indicated, most people with a personal or office/department level server often need only a need the regular full (level 0) dump, plus a daily level 1 dump in between the full dumps.In fact, I have some servers that are small enough that I just make level 0 dumps each time. Now, if you have a big system with lots of new files and changed files all the time, then you will have to organize your dumps in a more sophisticated manner. Generally, level 0 dumps take whatever amount of media they need to contain the whole filesystem. Then, for the change dumps (level 1..9) you hope to keep then to only one unit of media. If a change dump goes over one unit of media, then you move up a level the next time. The same goes for if the change dump starts to take a lot of extra time. As for media, it can be to an external disk, a tape or over the net to some big storage space. Try to spread it out so that each set of dumps is not on the same physical media as other ones - eg rotate your media. jerry > ___ > 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 this Intel CPU ok for 7.2 AMD64?
On Thu, Oct 15, 2009 at 3:13 PM, Len Conrad wrote: > Does it matter whether I run IA64 or AMD64 in the above Dell 1850? You wont even et IA64 booting as that is a compilation for Itanium processors. For the 64bit enabled Xeon processors Intel licensed the AMD64 instruction set. Therefor the correct distro to use on this machine would be AMD64 or i386 if you have a need to run 32bit software. -- "Opportunity is most often missed by people because it is dressed in overalls and looks like work." Thomas Alva Edison Inventor of 1093 patents, including: The light bulb, phonogram and motion pictures. ___ 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: clone-dump-restore
On Wed, Oct 14, 2009 at 09:29:42PM -0400, PJ wrote: > I believe that my problems arise out of subliminal refuse syndrome: the > brain refuses to comprehend dump and restore TOs and FROMs. > In other words, I'm beginning to see that > dump -0af TO ( - or device/file) FROM (device or directory/file) > and > restore -rf (TO curr.dir FROM device or file) > > or > dump -0af - (FROM device or file) | restore -rf - (TO device or directory) > > or do I still not have it right? > It's the stdout and stdin that makes me stumble. > Do I really need to mount the partitions or can I just dump and restore > from device to device directly? > The manual says I should be able to dump & restore across the lan too... Basically. on dump, the filesystem to be dumped comes last on the command line. The place to write the dump is that which is named right after the -f If there is no -f then it defaults to a tape device. If a '-' follows the -f, then it writes to standard out. The name must be the first thing after the -f or it will get confused. On restore, there is no filesystem name to come last. You have to be cd-ed to where you want it written. So, the only thing to consider is its -f. For restore, that tells from where to read. If it is a device or file name, it reads from that. If it is '-' it reads from standard in. If there is no -f it defaults to the tape device. Again, the name must be the first thing after the -f if there is a -f. The pipe '|' tells the system to take the standard out from the first process and feed it to the standard in of the second. That passing is not a function of dump/restore, but of the system. The pipe just passes data. It doesn't force the utilities (dump or restore) to do anything about it. But, putting the '-' on dump and restore tells them to pay attention to standard out/in. You can cause dump to send standard out over the net and restore to read standard in from the net.I used to do that, but it has been a long time and I don't have time at the moment to go and check the details to make sure I tell it correctly. jerry > ___ > 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: zfs root
2009/10/3 krad > Hi, > > I have a quick question about freebsd on zfs root. I have built a few test > systems all work fine. I have one question though. Does the loader replay > any information when it accesses the pool? > > Basically im interested in how or what is done on reboot after the kernel > panic or power loss. Are there any safe gaurds with regard to the zpool > integrity? > > > > anybody? ___ 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"
7.0 stable + postfix - how to setup chroot?
What I already did: syslogd_flags="-s -l /var/spool/postfix/var/run/log" # put into /etc/rc.conf Then I changed "n" to "y" for all lines in /usr/local/etc/postfix/master.cf in the "chroot" column. But I don't know how to create chrooted environment under /var/spool/postfix. Is there a command that can create it for me? Or is there a manual telling what files I need to copy from my root fs? Thanks, Laszlo ___ 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: Graphics card recommendation
On Wed, 14 Oct 2009 11:59:49 -0400 Jerry wrote: > nVidia (AMD64) is not supported in 7.x versions of FreeBSD as far as I > know. There was some talk of it being supported in 8.x, but I have > not heard from anyone actually doing so. The existing driver is 32 bit and will never run on amd64. What's happened is that 8-current has provided some of the VM features that nVidia regard as prerequisites for a new 64-bit driver. > All my machines use nvidea > cards, and the lack of support for it in FBSD, even after an extended > period of time, is a real PIA. Right, but for most of that time the ball has been in FreeBSD's court. ___ 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: FWD: is this Intel CPU ok for 7.2 AMD64?
On Thu, Oct 15, 2009 at 03:13:49PM +0200, Len Conrad wrote: > > -- Original Message -- > From: "Len Conrad" > Reply-To: > Date: Wed, 14 Oct 2009 22:48:26 +0200 > > the FreeBSD 6.2 i386 dmesg.boot shows: > > CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > > Features=0xbfebfbff > Features2=0x659d> > AMD Features=0x2010 > Logical CPUs per core: 2 > real memory = 3220963328 (3071 MB) > avail memory = 3150913536 (3004 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0: Changing APIC ID to 8 > ioapic1: Changing APIC ID to 9 > ioapic1: WARNING: intbase 32 != expected base 24 > ioapic2: Changing APIC ID to 10 > ioapic2: WARNING: intbase 64 != expected base 56 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 32-55 on motherboard > ioapic2 irqs 64-87 on motherboard > > thanks, > Len > > == > > So, is there a definite, unique answer? > > Does it matter whether I run IA64 or AMD64 in the above Dell 1850? It matters very much. AMD64 should work fine. IA64 will will not work at all. -- Erik Trulsson ertr1...@student.uu.se ___ 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"
FWD: is this Intel CPU ok for 7.2 AMD64?
-- Original Message -- From: "Len Conrad" Reply-To: Date: Wed, 14 Oct 2009 22:48:26 +0200 the FreeBSD 6.2 i386 dmesg.boot shows: CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x659d> AMD Features=0x2010 Logical CPUs per core: 2 real memory = 3220963328 (3071 MB) avail memory = 3150913536 (3004 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 32 != expected base 24 ioapic2: Changing APIC ID to 10 ioapic2: WARNING: intbase 64 != expected base 56 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard ioapic2 irqs 64-87 on motherboard thanks, Len == So, is there a definite, unique answer? Does it matter whether I run IA64 or AMD64 in the above Dell 1850? Len ___ 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"
tbs 8920
hi how can i install tbs 8920 dvb card in free bsd? ___ 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: Unknown devices
Grate thanks!I had installed from 3 CD FreeBSD 7.2 with default (I hope) options.I don't understand - why it occurs, but now I understand - where to look.I think - I will reinstall the system, but if You have idea about this trouble - say me.Unfortunately I can not ask your last question because I very novice in FreeBSD. I just followed the instruction for FreeBSD router. Once more thanks, Arkady Tokaev > Date: Thu, 15 Oct 2009 00:38:03 +0200 > From: free...@edvax.de > To: tok...@hotmail.com > CC: freebsd-questions@freebsd.org > Subject: Re: Unknown devices > > On Wed, 14 Oct 2009 23:04:51 +0400, Arkady Tokaev wrote: > > > > While I was trying to update ports I have received message > > about absence disk space.It's impossible, I thought.But df > > command said: > > > $ df -h > > Filesystem SizeUsed Avail Capacity Mounted on > > /dev/ad0s1a 23G3.5G 18G16%/ > > devfs 1.0K1.0K 0B 100%/dev > > /dev/md0 9.4M2.8M6.5M30%/etc > > /dev/md131M 16M 13M55%/usr/local/etc > > /dev/md219M 18K 19M 0%/root > > /dev/md331M6.1M 24M20%/var > > $ > > What is the md devices?How I can remove them? > > See "man md": The md devices refer to memory disks, RAM that > "emulates" a hard disk. > > Sadly, I don't recognize a reason why your /etc, /usr/local/etc, > /root and /var subtrees are mounted onto memory disks... seems > that you're not running a default install, do you? > > Regarding your initial problem - updating ports - this involves > writing operations in the ports directory (usually /usr/ports > which may be a subtree of /dev/ad0s1a on / in your setting) as > well as in /var, especially /var/db/pkg, the installed packages > database, and /var/ports. When /var is a memory disk with 30 MB, > it may be too small for such a process. Furthermore, if I see this > correctly, you're loosing the content of the package database > on reboot; is this intended? > > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... _ Не хотите, чтобы кто-то знал, что вы делали в Интернете вчера? Вам нужен Internet Explorer 8. http://www.microsoft.ru/ie8___ 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"
Invitation to connect on LinkedIn
LinkedIn Artem Kazakov requested to add you as a connection on LinkedIn: -- Jerry, I'd like to add you to my professional network on LinkedIn. - Artem Accept invitation from Artem Kazakov http://www.linkedin.com/e/1o3bCy0npDqyzD3wjrAbLV0nLmqMr8R-MulSGyDnb3nr/blk/I1507158794_2/pmpxnSRJrSdvj4R5fnhv9ClRsDgZp6lQs6lzoQ5AomZIpn8_cBYQejsUdj4Tc3kNiiZDhk8PdSVRjiYNd3gMdzsUejsLrCBxbOYWrSlI/EML_comm_afe/ View invitation from Artem Kazakov http://www.linkedin.com/e/1o3bCy0npDqyzD3wjrAbLV0nLmqMr8R-MulSGyDnb3nr/blk/I1507158794_2/39vd3ATe3kNdP0RckALqnpPbOYWrSlI/svi/ -- (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: NTP Client synchronization with a Windows 2003/2008
> > If I may pipe up... Can you not set the clock manually, then let ntpd take > it from there? Seems like your clock would become synced a lot faster if it > started out "close". Sorry if I'm being naive, but this seemed like the > obvious thing to do. > > Don't apologize! Any input is valuable! But I don't quite understand what you meant about "let ntpd take it from here" or "if it started out close"... (I am French and maybe you're using a figure of language I don't understand...) Are you running with an elevated securelevel? No the Secure Level is -1... But I've found the beginning of a solution... It doesn't come from ntpd but from the Windows Time Server. When configured to sync with its internal clock, the NTP Server IP packets that goes to the client contain strange values (rootdispersion, etc.) that are higher than expected. Thus, ntpd doesn't consider the Windows Server as a reliable source. But once the windows server configured to sync with an external source, it works! The IP packets generated from the windows server begin to look like "real" and reliable answer to ntpd... I'm working now on a correct configuration of the Windows Server. Thanks again to all! ___ 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: NTP Client synchronization with a Windows 2003/2008
2009/10/15 Chris Hill > On Wed, 14 Oct 2009, Jacques Henry wrote: > > The 19 minutes between when I sent my suggestions and you responded is hardly enough time to see if ntpd was slewing the time. Slewing 587 seconds takes days. >>> >>> >> The thing is that ntpd is not slewing the time at all, even after several >> hours!! >> > > If I may pipe up... Can you not set the clock manually, then let ntpd take > it from there? Seems like your clock would become synced a lot faster if it > started out "close". Sorry if I'm being naive, but this seemed like the > obvious thing to do. > > -- > Chris Hill ch...@monochrome.org > ** [ Busy Expunging <|> ] > > ___ > 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" > sometimes the crude and simple methods are the best 8) ___ 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: mkisofs error
Be _very_ careful, genisoimage is full of bugs and creates defective filesystems. Do not use it, genisoimage is unmaintained and does not even support files > 4 GB! Other well known bugs in genisoimage create defective directory entries for "." and "..". This is because genisoimage is based on a 5 year old version of mkisofs with additional bugs added that never have been in the original software. Mkisofs has no known bugs and is well maintained. I see no reason why mkisofs should be the cause for your problem... Well you did not describe the problem in a way that could allow to analyse the background. Possible reasons for your problem could be read errors on the medium, check using: readcd f=/dev/null whether the medium is fully readable. Another possible reason could be a problem in the filesystem driver of the kernel. If a file gives a read error, there should be a kernel message related to the problem. If you are able to extract the file using "isoinfo" using the ISO-9660 name of the file (be careful not to use the defective "isoinfo" that comes with "cdrkit"), the problem is definitely not in mkisofs. BTW: do you use a recent or an outdated mkisofs? The latest version of mkisofs is 2.01.01a66 and FreeBSD by default unfortunately distributes extremely outdated versions. Jörg -- EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin j...@cs.tu-berlin.de(uni) joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily ___ 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"
Adding up kernel mem usage
If I subtract vmstat and kldstat from wired, I'm missing approx 100M. What am I doing wrong or what should I be adding up to find the total mem in use by the kernel and a breakdown of that usage? Thanks. top -SH -d 1 1000 | egrep '^Mem:' Mem: 114M Active, 65M Inact, 258M Wired, 468K Cache, 46M Buf, 551M Free vmstat -m | sed -E 's,^(.),,' | awk '{print $2}' | sed 's,K,,' | egrep -v MemUse | add 143920 { printf 'ibase=16\n' ; kldstat | tr '[:lower:]' '[:upper:]' | egrep -v SIZE | awk '{print $4}' | tr '\n' '\+' | sed 's,+$,,' ; } | bc 13986028 vmstat procs memory pagedisks faults cpu r b w avmfre flt re pi pofr sr ad0 ad4 in sy cs us sy id 1 0 0461M 551M68 0 0 088 0 0 0 26 1189 654 3 1 97 ___ 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: Adding up kernel mem usage
Is multiplying out the size and used columns from vmstat -z completely in addition to the amount used in vmstat -m, or do some of them overlap? vmstat -z | sed 's,^.*:,,' | sed -E 's,^ +,,' | sed -E 's/^([0-9]+),[^,]+, +/\1*/;s/,.*$//' | egrep '^[0-9]' | bc | add 58483416 Is netstat -m accounted for in one of the two vmstat's? systat -vm 1 Mem:KBREALVIRTUAL Tot Share TotShareFree Act 191564 39548 46134848380 566632 All 423996 42600 261968053448 I'm not sure what Share means in this context? 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"