Re: Restricting tar or pax to a single file system
In the last episode (Nov 21), jaymax said: > How does one restrict tar or fax to a single file system when tarring or > paxing from root (/) ? For tar: --one-file-system (-W one-file-system) (c, r, and u modes) Do not cross mount points. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Restricting tar or pax to a single file system
How does one restrict tar or fax to a single file system when tarring or paxing from root (/) ? Thanks! -- View this message in context: http://old.nabble.com/Restricting-tar-or-pax-to-a-single-file-system-tp26463168p26463168.html Sent from the freebsd-questions mailing list archive at Nabble.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: sending mail with attachments always fail (FreeBSD/pf)
On Sat, 21 Nov 2009 23:36:33 +0600, Victor Lyapunov wrote: >> This kind of thing is often due to a mtu blackhole - when a larger >> email causes a full size IP packet to be sent. I don't see why PF >> should make a difference though, IFAIK it's supposed to let ICMP through >> when it's learned state on a tcp connection. > > Thanks for your answer. > Don't know whether it is relevant to the particular issue, but i tried > both rulesets first with `scrub in all fragment reassemble` and > another one without it, but neither worked for me. I'm kinda upset by > the fact that pf can't handle large emails. > > Any other ideas how to possibly fix it, please? If on FreeBSD 7 or higher you can get rid of the keep state. It's implicit. Secondly, please test if the problem disappears by removing the rules and simply allowing outgoing traffic. Your rules would be: scrub in on $ext_if fragment reassemble block in on $ext_if pass out on $ext_if from $int_if:network to any If that works, then your problem is likely that you're creating 2 states for one connection causing confusion. -- Mel ___ 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: upgrading firefox
On Sun, Nov 22, 2009 at 04:13:01AM +, Steven Seipel wrote: > I have freebsd 7.2 with gnome. It has firefox 2.0.0.20. What will I need to > do to upgrade to firefox 3.anything? I have tried pkg_add -r with all the > versions listed on the ports page but it is always "unable to fetch" them. > When I just typed pkg_add -r firefox it told me I already have version > 2.0.0.20 installed. So what do I do to get a more recent version? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html -- Jonathan Chen -- Power corrupts, Absolute Power is pretty neat ___ 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 can I rescue my passwd file after corrupting it (and why does it still work) ?
I do some automated account creation on a FreeBSD 6.x system ... and unbeknownst to me, the '/' filesystem was completely full when I did my last account creation, resulting in: /: write failed, filesystem is full pwd_mkdb: /etc/pwd.db to /etc/pwd.db.tmp: No space left on device pw: passwd file update: No space left on device pwd_mkdb: corrupted entry pwd_mkdb: at line #187 pwd_mkdb: /mnt/etc/master.passwd: Inappropriate file type or format My situation is now as follows: passwd and master.passwd have a lot of lines missing, and one or two mangled lines toward the end. So a LOT of user accounts are gone. BUT, all of those missing accounts still work. So ... 1) why do all of the accounts that are missing from both passwd and master.passwd continue to work properly (they can authenticate and log in over SSH and so on) ? 2) how can I get back to healthy ? I suspect that somehow my (s)pwd.db files are still healthy ... is it possible to reconstruct complete passwd/master.passwd files using the existing (s)pwd.db files ? 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"
fsck_ffs DIOCGINFO ioctl?
I am not sure how this ioctl (DIOCGDINFO) in fsck_ffs/setup.c is returned from
kernel. Seems like there is only one place in sys/geom/geom_bsd.c, I have
enabled GEOM_BSD option in config file, but not able to see it. Could someone
point out how this ioctl is returned from kernel? I see it is returning -1 from
somewhere, so cannot be this place in geom_bsd.c, then where from?
thanks
naeem
sys/geom/geom_bsd.c
.
static int
g_bsd_ioctl(struct g_provider *pp, u_long cmd, void *data, int fflag, struct
thread *td)
{
struct g_geom *gp;
struct g_bsd_softc *ms;
struct g_slicer *gsp;
u_char *label;
int error;
gp = pp->geom;
gsp = gp->softc;
ms = gsp->softc;
switch(cmd) {
case DIOCGDINFO:
/* Return a copy of the disklabel to userland. */
bsd_disklabel_le_dec(ms->label, data, MAXPARTITIONS);
printf(">>> DIOCGDINFO <<<\n");
return(0);
case DIOCBSDBB: {
--
sbin/fsck_ffs/setup.c:
static struct disklabel *
692 getdisklabel(char *s, int fd)
693 {
694 static struct disklabel lab;
695 696 if (ioctl(fd, DIOCGDINFO, (char *)&lab) < 0) {
697 if (s == NULL)
698 return (NULL);
699 pwarn("ioctl (GCINFO): %s\n", strerror(errno));
700 errexit("%s: can't read disk label\n", s);
701 }
702 return (&lab);
703 }
___
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"
upgrading firefox
I have freebsd 7.2 with gnome. It has firefox 2.0.0.20. What will I need to do to upgrade to firefox 3.anything? I have tried pkg_add -r with all the versions listed on the ports page but it is always "unable to fetch" them. When I just typed pkg_add -r firefox it told me I already have version 2.0.0.20 installed. So what do I do to get a more recent version? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
8.0-RC USB problem -- how to recover a damaged USB stick
It seems this is more serious problem in 8.0, and I hope it could be resolved before a formal release. I can help to diagnose this if people need more information (this is destructive). I have picked a USB stick (DataTraveler 2GB), that has two partitions s0 for DOS and s1 for FreeBSD. Both USB hard drive and the USB stick have worked under FreeBSD 6.2, 6.3, 6.4 and 7.2 for a few years without any problem. Plugged USB stick in 8.0-RC and mounted it on /mnt; then untar a file, tarred one day ago from FreeBSD 6.3 machine onto stick,to a IDE drive then tar it back to the USB stick. During tar writting from IDE to USB stick, did "ls /mnt", and "tar" paused and "ls" hangs. A couple of minutes later, ls comes back, but tar still pauses. Hit ^C on tar process around 14:30, it took another minutes to stop the process. Tried tar again, and system disallowed to write on the USB stick. "ls" shows all file still there (probably cached inods). Went out for a few hours, and came back found /var/log/message are flooded with following message: -rw-r--r-- 1 root wheel 167181 Nov 21 19:02 messages -rw-r--r-- 1 root wheel7390 Nov 21 18:00 messages.0.bz2 -rw-r--r-- 1 root wheel7509 Nov 21 17:00 messages.1.bz2 -rw-r--r-- 1 root wheel9365 Nov 21 16:00 messages.2.bz2 -rw-r--r-- 1 root wheel 20598 Nov 21 15:00 messages.3.bz2 Nov 21 18:00:00 wolf newsyslog[2635]: logfile turned over due to size>384K Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625688576, length=1 31072)]error = 5 Nov 21 18:00:27 wolf kernel: g_vfs_done():da0s2[WRITE(offset=625819648, length=1 31072)]error = 5 . Nov 21 18:19:03 wolf kernel: g_vfs_done():da0s2[WRITE(offset=524451840, length=1 6384)]error = 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=5586944, length=204 8)]error = 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=65536, length=2048) ]error = 5 Nov 21 18:19:33 wolf kernel: g_vfs_done():da0s2[WRITE(offset=114688, length=1638 4)]error = 5 Nov 21 18:20:05 wolf kernel: g_vfs_done():da0s2[WRITE(offset=349700096, length=1 and has to reboot the system, and reboot was not able to umount everything (boot up message): Nov 21 18:24:03 wolf kernel: da0: Removable Dir ect Access SCSI-2 device Nov 21 18:24:03 wolf kernel: da0: 40.000MB/s transfers Nov 21 18:24:03 wolf kernel: da0: 1947MB (3987456 512 byte sectors: 255H 63S/T 2 48C) Nov 21 18:24:03 wolf kernel: WARNING: / was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /data was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /home was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /tmp was not properly dismounted Nov 21 18:24:03 wolf kernel: WARNING: /usr was not properly dismounted ... # mount /dev/da0s2 /mnt mount: /dev/da0s2 : Operation not permitted The USB stick cannot be mount under any FreeBSD OS now, and everything on the drive has lost. Does anyone know if it is possible to revocer such damaged USB stick? -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Wed 11/18/2009 3:13 AM To: freebsd-...@freebsd.org Cc: Guojun Jin; freebsd-sta...@freebsd.org; questi...@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore completely > fails: (I had experienced another similar problem on an IDE, which works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 > g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == > 0xa, scs i status == 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to it; > expect data loss. > > 99 23:19 sysinstall >100 23:20 newfs /dev/da0s3d >101 23:20 newfs /dev/da0s3e >102 23:21 mount /dev/da0s3d /mnt >103 23:21 cd /mnt >104 23:21 dump -0f - /home | restore -rf - >105 23:27 history 15 > > > > -Original Message- > From: Guojun Jin > Sent: Tue 11/17/2009 11:0
Re: Postgresql download site
On Sun, Nov 22, 2009 at 4:16 AM, Peter Steele wrote: > What's the best place to pick up the latest 7.0 and 8.0 packages for > postgresql client and server? > > ___ > 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" > At the moment, postgresql ports are being very actively maintained. You can try compiling it on your own, if you want 8.4.1 version. With regards Amitabh ___ 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"
Pulse Meter with Cellular communication
This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. ___ 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: Dump
Chris Rees said the following on 2009-11-21 17:44: 2009/11/21 Bernt Hansson : Matthew Seaman skrev: Bernt Hansson wrote: Hello list. I've been testing backups with dump, works well BUT -L does not work. For example dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d I believe that you need to tell dump the mount point of the file system in order for it to create a snapshot, rather than the device file for the partition. (ie. snapshotting only makes sense on a mounted read-write filesystem). Also, if you're dumping a snapshotted FS to a local file, then bump up the cachesize to improve performance a lot. Add '-C 32' to your command-line. Ok. I've tested this dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 /usr/home The error is mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory Just for sanity... Are you root? Yes! 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: Dump
George Davidovich said the following on 2009-11-21 17:14: On Sat, Nov 21, 2009 at 04:12:42AM +0100, Bernt Hansson wrote: Matthew Seaman skrev: Bernt Hansson wrote: I've been testing backups with dump, works well BUT -L does not work. For example dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d I believe that you need to tell dump the mount point of the file system in order for it to create a snapshot, rather than the device file for the partition. (ie. snapshotting only makes sense on a mounted read-write filesystem). Also, if you're dumping a snapshotted FS to a local file, then bump up the cachesize to improve performance a lot. Add '-C 32' to your command-line. Ok. I've tested this dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 /usr/home dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 /usr/home The error is mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory Aargh. Must have missed the above when I last replied. That error message indicates you're running dump without proper privileges. Run dump as root, or add yourself to the operator group: I did run it as root and got this error message: mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or director ___ 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: device hint -> disable firewire or sbp driver
> And if I'm reading the SVN commit right, it went to -STABLE (aka > RELENG_8) but not head (aka "."). It still won't fix all of FreeBSD 7 > install mediums, right? or is that "to come", maybe in 7.3? > > > Also, if I'm reading the commit right, 8.0-RELEASE is going to have > sbp(4) enabled in GENERIC too. Can someone make sure I'm reading that > right? > Just so that this is crystal clear: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/amd64/conf/GENERIC As of this moment, device sbp is commented out of the GENERIC kernel configuration for RELENG_8_0 branch *and* tagged with the RELENG_8_0_0_RELEASE tag, so the release build will have sbp disabled in the default GENERIC kernel configuration. (In other words, you should not have boot hangs by default due to firewire in 8.0 release) As far is 7.x is concerned, the current RELENG_7 branch (as of this moment) still has device sbp enabled. As far as 7.3 or future MFC to RELENG_7 of a fix or workaround, that remains to be seen, but the best thing to do is to make certain that the PR has all the necessary information provided, and to occasionally test with the latest -current (9.0) source and provide any debugging information if asked. 9.0 (aka -current) specifically left device sbp enabled so that people can continue to test and fix this bug (gives better exposure to the code). Make sense ? Good Luck. --_Dave ___ 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: Postgresql download site
On Sat, Nov 21, 2009 at 11:46 PM, Peter Steele wrote: > What's the best place to pick up the latest 7.0 and 8.0 packages for > postgresql client and server? > > just go to /usr/ports/databases and do a "ls | grep post" then go into a directory and do "make install" if you have objections to this method, please elaborate. regards, usleep ___ > 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"
Ford 400 AD Sale - Save 35% until 11/30/2009
Use Promo Code: Ford400 ... to save 35% off all CarProperty.com listings ... this 0ffer expires November 30, 2009 @ 11:59pm PST GO HERE FOR THE FULL DETAILS: http://www.carproperty.com/page.php?id=33 Try the CarProperty.com Map Search at this link http://www.carproperty.com/mapsearch.php Your AD will show up on this incredible map searching tool and it will be very easy to find! We love these guys ... check them out: America's Car Show http://www.AmericasCarShow.com, broadcast live on Sirius XM Radio ... listen to it live on Sundays 10pm EST - 12AM EST this is the world's best automotive broadcast bar none!! New Monthly Feature: Car Tips, brought to you by Americas Car Show, hosted by Tom Torbjornsen and heard on Sirius 108 and XM 139 Read the full articles here http://eliteautorepairshops.wordpress.com Sports Car Market Magazine Family and Internet Resources http://www.sportscarmarket.com/family CarProperty.com sent this informational newsletter to questi...@freebsd.org based on your CarProperty.com optional user preferences. Click here to update your profile http://letters.carproperty.com/p_m.php?mi=218&nl=4&ei=cXVlc3Rpb25zQGZyZWVic2Qub3Jn&eid=MjQ1Nzc4. Send this to a friend http://letters.carproperty.com/p_f.php?mi=218&nl=4&ei=cXVlc3Rpb25zQGZyZWVic2Qub3Jn&eid=MjQ1Nzc4 If you no longer wish to receive our non-system messages, you can remove yourself from our mailing list by clicking here http://letters.carproperty.com/box.php?funcml=unsub2&nl=4&mi=218&email=questions%40freebsd.org or mail your request to Car Property Group. 1620 Central Ave, Suite 202, Cheyenne, WY 82001(please allow 3 - 4 weeks using this unsubscribe method). Toll Free: 1-888-628-3683. If you received a forwarded copy of the Car Property News, you can subscribe by registering on www.CarProperty.com. Car Property News is sent from time to time but not on a set schedule. To help make sure you get our emails, please put our domain address of @carproperty.com in your email programs address book or safe senders list that monitors your inbox. You may have to forward this information to a systems administrator who runs your email systems so they can put us on your safe list. Please give them our domain address of @carproperty.com. If you need help putting our domain address in your email programs address book or safe senders list, please click on this link: How to Add an Address to Your Address Book or Safe Senders List CarProperty.com is a registered Trademark as are the phrases Car Property and Car Properties, by the Car Property Group. This notice is compliant with the US Governments regulations regarding emails. To Unsubscribe, please click here : http://letters.carproperty.com/box.php?funcml=unsub2&nl=4&mi=218&email=questions%40freebsd.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"
Postgresql download site
What's the best place to pick up the latest 7.0 and 8.0 packages for postgresql client and server? ___ 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: Glassfish v3 server: Admin port in use
On Saturday 21 November 2009 15:01:55 Frank Staals wrote: > Hey everyone, > > I'm trying to deploy a Glassfish v3 server on my workstation since I > need to do some jsf-developement. However when I try to start the server > it keeps telling me the admin port I'm trying to use is allready in use > by an other process, no matter what port I use. However I'm 100% certain > there is nothing running on the port it should use (sockstat confirms > that). Has anyone seen this type of behaviour and/or knows how to fix it > ? I'm running FreeBSD 8.0-RC1 with jdk16 installed from ports. Full log > is here: http://fstaals.net/junk/glassfish.txt Perhaps this is an error specific to glassfish 3. I used to have Glassfish 2.1.1 working on FreeBSD/head (i386). I don't know what your requirements are but maybe that version will suffice? I used the "Linux" installer if I remember correctly. You can also try asking freebsd-j...@freebsd.org. Good luck, Pieter de Goeje ___ 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: device hint -> disable firewire or sbp driver
On 11/21/09, David Horn wrote: > On Sat, Nov 21, 2009 at 2:15 PM, Tim Judd wrote: >> On 11/21/09, Chris Whitehouse wrote: >>> Tim Judd wrote: Any way via tunables, environment, sysctl or device hints that one can disable firewire on the install medium of recent (7.2 and newer) Install CD/DVDs? more than one person is having problems with kernel panics on startup due to firewire, and I can't google my way out of this one. Any advice from the pros? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >>> Tim, >>> >>> I've got one of the affected motherboards if this is the problem you >>> mean: >>> >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 >>> >>> The things that have worked for me are disabling firewire in the BIOS >>> and using a GENERIC kernel or building a kernel with device sbp disabled >>> and having firewire enabled in the BIOS. >> >> See though, the guys coming to FreeBSD from $another-OS gets a panic >> from the install medium, which isn't speaking very well of our >> quality. >> >> I got caught with this because the guy I was helping online had an >> amd64-capable system, to which I don't. I can't build a install CD or >> kernel to help him. I have a PCI firewire card that runs sbp, but the >> livecd doesn't panic when i was booting from it. >> >> >> I tried all sorts of disabling hints, tried to go upstream (see it's >> dependencies and disable it's dependencies) and it still gave me a sbp >> when the system finished booting. >> >> >> Thought about asking him to run the memstick and disabling it from >> there, but he still can't get past it booting to tweak anything. He >> didn't have an option to disable firewire in the BIOS, and there was >> no bios update from Sony for his Vaio. >> >> >> I got stuck, and it started to wear thin that we have such a major >> panic on install CDs. My mentality is to offer disk, cd and network >> support in the kernel on the install CD/DVDs, but the generic kernel >> that's installed has everything. >> >> >> If others would like to offer suggestions, I'm still open for them. >> >> >>> >>> hint.sbp.0.disabled="1" in /boot/device.hints with GENERIC kernel - >>> still get a panic >>> >>> sbp_load="YES" in /boot/loader.conf with sbp disabled in the kernel - >>> get panic. >>> >>> It seems ok to kldload sbp after the system is up, ie the machine >>> doesn't panic, but I don't have anything firewire to test with. >>> >>> Would it be an option to have sbp disabled by default in the install >>> CD's? Those without the problem can put sbp_load in loader.conf, those >>> with the problem will have to kldload it later but at least they will be >>> able to install. > > As per svn and cvs: > > r199112 | kensmith | 2009-11-09 16:39:42 -0500 (Mon, 09 Nov 2009) | 11 lines > Changed paths: >M /stable/8/sys/amd64/conf/GENERIC >M /stable/8/sys/i386/conf/GENERIC >M /stable/8/sys/ia64/conf/GENERIC >M /stable/8/sys/powerpc/conf/GENERIC >M /stable/8/sys/sparc64/conf/GENERIC > > Comment out the sbp(4) entry for GENERIC config files that contain it. > There are known issues with this driver that are beyond what can be > fixed for 8.0-RELEASE and the bugs can cause boot failure on some systems. > It's not clear if it impacts all systems and there is interest in getting > the problem fixed so for now just comment it out instead of remove it. > > Commit straight to stable/8, this is an 8.0-RELEASE issue. Head was left > alone so work on it can continue there. > > Reviewed by:Primary misc. architecture maintainers (marcel, marius) > > Looks like sbp(4) is disabled on the 8.0 branch already. And if I'm reading the SVN commit right, it went to -STABLE (aka RELENG_8) but not head (aka "."). It still won't fix all of FreeBSD 7 install mediums, right? or is that "to come", maybe in 7.3? Also, if I'm reading the commit right, 8.0-RELEASE is going to have sbp(4) enabled in GENERIC too. Can someone make sure I'm reading that right? > > --Dave > ___ 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: ukbd_set_leds_callback:700: error=USB_ERR_STALLED
On Saturday 21 November 2009 10:10:27 O. Hartmann wrote: > My personal workstation runs FreeBSD 8.0-PRE/amd64 on an oldish hardware > (AMD socket 939 platform). Since I replaced my good old but broken IBM > Model-M keyboard with a high-quality keyboard 'DASkeyboard', I receive > this error message on the console: > > > ukbd_set_leds_callback:700: error=USB_ERR_STALLED > > What does it means? Hi, It means that there was an error updating the LED information on your keyboard. Does the NUM-lock LED work for example? There is a sysctl to disable this feature: sysctl hw.usb.ukbd.no_leds=1 --HPS ___ 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: device hint -> disable firewire or sbp driver
On Sat, Nov 21, 2009 at 2:15 PM, Tim Judd wrote: > On 11/21/09, Chris Whitehouse wrote: >> Tim Judd wrote: >>> Any way via tunables, environment, sysctl or device hints that one can >>> disable firewire on the install medium of recent (7.2 and newer) >>> Install CD/DVDs? >>> >>> more than one person is having problems with kernel panics on startup >>> due to firewire, and I can't google my way out of this one. >>> >>> >>> >>> Any advice from the pros? >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to >>> "freebsd-questions-unsubscr...@freebsd.org" >>> >> Tim, >> >> I've got one of the affected motherboards if this is the problem you mean: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 >> >> The things that have worked for me are disabling firewire in the BIOS >> and using a GENERIC kernel or building a kernel with device sbp disabled >> and having firewire enabled in the BIOS. > > See though, the guys coming to FreeBSD from $another-OS gets a panic > from the install medium, which isn't speaking very well of our > quality. > > I got caught with this because the guy I was helping online had an > amd64-capable system, to which I don't. I can't build a install CD or > kernel to help him. I have a PCI firewire card that runs sbp, but the > livecd doesn't panic when i was booting from it. > > > I tried all sorts of disabling hints, tried to go upstream (see it's > dependencies and disable it's dependencies) and it still gave me a sbp > when the system finished booting. > > > Thought about asking him to run the memstick and disabling it from > there, but he still can't get past it booting to tweak anything. He > didn't have an option to disable firewire in the BIOS, and there was > no bios update from Sony for his Vaio. > > > I got stuck, and it started to wear thin that we have such a major > panic on install CDs. My mentality is to offer disk, cd and network > support in the kernel on the install CD/DVDs, but the generic kernel > that's installed has everything. > > > If others would like to offer suggestions, I'm still open for them. > > >> >> hint.sbp.0.disabled="1" in /boot/device.hints with GENERIC kernel - >> still get a panic >> >> sbp_load="YES" in /boot/loader.conf with sbp disabled in the kernel - >> get panic. >> >> It seems ok to kldload sbp after the system is up, ie the machine >> doesn't panic, but I don't have anything firewire to test with. >> >> Would it be an option to have sbp disabled by default in the install >> CD's? Those without the problem can put sbp_load in loader.conf, those >> with the problem will have to kldload it later but at least they will be >> able to install. As per svn and cvs: r199112 | kensmith | 2009-11-09 16:39:42 -0500 (Mon, 09 Nov 2009) | 11 lines Changed paths: M /stable/8/sys/amd64/conf/GENERIC M /stable/8/sys/i386/conf/GENERIC M /stable/8/sys/ia64/conf/GENERIC M /stable/8/sys/powerpc/conf/GENERIC M /stable/8/sys/sparc64/conf/GENERIC Comment out the sbp(4) entry for GENERIC config files that contain it. There are known issues with this driver that are beyond what can be fixed for 8.0-RELEASE and the bugs can cause boot failure on some systems. It's not clear if it impacts all systems and there is interest in getting the problem fixed so for now just comment it out instead of remove it. Commit straight to stable/8, this is an 8.0-RELEASE issue. Head was left alone so work on it can continue there. Reviewed by:Primary misc. architecture maintainers (marcel, marius) Looks like sbp(4) is disabled on the 8.0 branch already. --Dave ___ 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"
gif ip4 to ip4 tunnel with Dynamic IP
hello list, I have a FreeBSD 8.x setup and I am using the gif device to setup a ip4 to ip4 tunnel (not IPSEC) I have searched google and I am having trouble finding a recipe for /etc/rc.conf that will allow one side of my tunnel to be dynamic. the client if you will is a FreeBSD machine running FreeBSD 8.0 connecting via DSL with a dynamic IP (using mpd5 to dial) the server is FreeBSD 8.0 and always has a static IP. I would have thought this setup would be easy to find a answer to but I haven't found it. Thank you for any help. Sam Fourman Jr. Fourman Networks ___ 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: device hint -> disable firewire or sbp driver
On 11/21/09, Chris Whitehouse wrote: > Tim Judd wrote: >> Any way via tunables, environment, sysctl or device hints that one can >> disable firewire on the install medium of recent (7.2 and newer) >> Install CD/DVDs? >> >> more than one person is having problems with kernel panics on startup >> due to firewire, and I can't google my way out of this one. >> >> >> >> Any advice from the pros? >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscr...@freebsd.org" >> > Tim, > > I've got one of the affected motherboards if this is the problem you mean: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 > > The things that have worked for me are disabling firewire in the BIOS > and using a GENERIC kernel or building a kernel with device sbp disabled > and having firewire enabled in the BIOS. See though, the guys coming to FreeBSD from $another-OS gets a panic from the install medium, which isn't speaking very well of our quality. I got caught with this because the guy I was helping online had an amd64-capable system, to which I don't. I can't build a install CD or kernel to help him. I have a PCI firewire card that runs sbp, but the livecd doesn't panic when i was booting from it. I tried all sorts of disabling hints, tried to go upstream (see it's dependencies and disable it's dependencies) and it still gave me a sbp when the system finished booting. Thought about asking him to run the memstick and disabling it from there, but he still can't get past it booting to tweak anything. He didn't have an option to disable firewire in the BIOS, and there was no bios update from Sony for his Vaio. I got stuck, and it started to wear thin that we have such a major panic on install CDs. My mentality is to offer disk, cd and network support in the kernel on the install CD/DVDs, but the generic kernel that's installed has everything. If others would like to offer suggestions, I'm still open for them. > > hint.sbp.0.disabled="1" in /boot/device.hints with GENERIC kernel - > still get a panic > > sbp_load="YES" in /boot/loader.conf with sbp disabled in the kernel - > get panic. > > It seems ok to kldload sbp after the system is up, ie the machine > doesn't panic, but I don't have anything firewire to test with. > > Would it be an option to have sbp disabled by default in the install > CD's? Those without the problem can put sbp_load in loader.conf, those > with the problem will have to kldload it later but at least they will be > able to install. > > FreeBSD eco.config 8.0-RC2 FreeBSD 8.0-RC2 #1: Thu Oct 29 14:04:02 GMT > 2009 r...@eco.config:/usr/obj/usr/src/sys/GENERIC_NO_SBP i386 > > > 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: device hint -> disable firewire or sbp driver
Tim Judd wrote: Any way via tunables, environment, sysctl or device hints that one can disable firewire on the install medium of recent (7.2 and newer) Install CD/DVDs? more than one person is having problems with kernel panics on startup due to firewire, and I can't google my way out of this one. Any advice from the pros? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Tim, I've got one of the affected motherboards if this is the problem you mean: http://www.freebsd.org/cgi/query-pr.cgi?pr=136327 The things that have worked for me are disabling firewire in the BIOS and using a GENERIC kernel or building a kernel with device sbp disabled and having firewire enabled in the BIOS. hint.sbp.0.disabled="1" in /boot/device.hints with GENERIC kernel - still get a panic sbp_load="YES" in /boot/loader.conf with sbp disabled in the kernel - get panic. It seems ok to kldload sbp after the system is up, ie the machine doesn't panic, but I don't have anything firewire to test with. Would it be an option to have sbp disabled by default in the install CD's? Those without the problem can put sbp_load in loader.conf, those with the problem will have to kldload it later but at least they will be able to install. FreeBSD eco.config 8.0-RC2 FreeBSD 8.0-RC2 #1: Thu Oct 29 14:04:02 GMT 2009 r...@eco.config:/usr/obj/usr/src/sys/GENERIC_NO_SBP i386 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: GPUs on FBSD?
On Sat, 21 Nov 2009 12:06:13 -0500 Robert Huff wrote: > > usleepl...@gmail.com writes: > > > > > as far as i know there have been Nvidia maintained/improved > > > > drivers for FreeBSD for ages ( ls /usr/ports/x11 | grep -i > > > > nvid ) > > > > > > And see this from the Makefile: > > > > > > # Starting with version 1.0-7667, NVidia has dropped support for > > > # numerous "legacy" GPUs. Consult NVidia README (the Appendix) > > > to # find out whether you need to use legacy driver version and > > > install # one of corresponding `x11/nvidia-driver-71', > > > # `x11/nvidia-driver-96', or `x11/nvidia-driver-173' slave ports. > > > > > > > > are you trying to be right afterall? > > Someone's confused. If it's me, that needs to get fixed. You're confused on more than one level because this thread is not about graphics drivers, however: nv is the basic open-source x11 driver provided with xorg, it has poor 2-d performance and no 3-d support, nouveau is a open-source fork from nv that aims to improve performance and add 3-d support. nvidia is the the proprietary binary provided by nvidia, it's been around for years, but nvidia were not prepared to release an amd64 version until FreeBSD provided certain features in the kernel. Those features will be in 8.0, so nvidia are now working on an amd64 version. ___ 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: sending mail with attachments always fail (FreeBSD/pf)
> This kind of thing is often due to a mtu blackhole - when a larger > email causes a full size IP packet to be sent. I don't see why PF > should make a difference though, IFAIK it's supposed to let ICMP through > when it's learned state on a tcp connection. Thanks for your answer. Don't know whether it is relevant to the particular issue, but i tried both rulesets first with `scrub in all fragment reassemble` and another one without it, but neither worked for me. I'm kinda upset by the fact that pf can't handle large emails. Any other ideas how to possibly fix it, please? ___ 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.2, usb mouse, uhub0: device problem (IOERROR)
Thanks to all who replied. It's working now, apparently spontaneously. It may have started as a connection problem--that's all I can think of. The first time I plugged it in and rebooted, the error occurred. I tried moving it to other ports, but I neglected to reboot--after all, USB is supposed to be hot-pluggable, unlike the PS/2 keyboard, right? At some point, the error messages stopped after a reboot. I can only speculate that there was something in the first USB connector that prevented a good contact, and that it got scraped out after a move or two. Anyone know why the USB/mouse system can't recognize a connection after a reboot, or what administrator action might allow it? Now I have to get the nvidia driver up. Cross your fingers. ___ 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: kern.polling.lost_polls
On Fri, 20 Nov 2009 19:07:42 -0700, Brett Glass wrote: > At 06:25 PM 11/20/2009, Mel Flynn wrote: > >>So that means that you give the kernel .25 microseconds to poll and act on >>any pending network IO. That's probably not enough. > > I think that you mean ".25 milliseconds," not ".25 microseconds," above. Yes, sorry. It should be enough, but...it's related to CPU speed and number of interfaces. On FreeBSD-net they can give you better advice, most notably whether all 6 interfaces are done in one poll and so each task needs to be completed within 1/HZ/N? I cannot say this with certainty. >>It is further explained by >>the >>comment in sys/kern/kern_poll.c: >>/* >> * Hook from hardclock. Tries to schedule a netisr, but keeps track >> * of lost ticks due to the previous handler taking too long. >> * Normally, this should not happen, because polling handler should >> * run for a short time. However, in some cases (e.g. when there are >> * changes in link status etc.) the drivers take a very long time >> * (even in the order of milliseconds) to reset and reconfigure the >> * device, causing apparent lost polls. >> * >> * The first part of the code is just for debugging purposes, and tries >> * to count how often hardclock ticks are shorter than they should, >> * meaning either stray interrupts or delayed events. >> */ > > Well, even at HZ=2000, kern.polling.lost_polls and > kern.polling.suspect are both incrementing, as is kern.polling.stalled: > > stargate# sysctl -a | grep polling > kern.polling.burst: 150 > kern.polling.burst_max: 150 > kern.polling.each_burst: 5 > kern.polling.idle_poll: 0 > kern.polling.user_frac: 50 > kern.polling.reg_frac: 20 > kern.polling.short_ticks: 0 > kern.polling.lost_polls: 41229 > kern.polling.pending_polls: 0 > kern.polling.residual_burst: 0 > kern.polling.handlers: 2 That bugs me: if you have 6 devices, the number of handlers should be 6. /* * Try to register routine for polling. Returns 0 if successful * (and polling should be enabled), error code otherwise. * A device is not supposed to register itself multiple times. * * This is called from within the *_ioctl() functions. */ Unless this should really read "drivers", but I think it's devices. > kern.polling.enable: 0 > kern.polling.phase: 0 > kern.polling.suspect: 31653 > kern.polling.stalled: 10 > kern.polling.idlepoll_sleeping: 1 > hw.acpi.thermal.polling_rate: 10 > > But if I slow the clock down to 1000 Hz, it's unclear if the > machine will be able to keep up with traffic. I was already getting > more than 1,000 network interrupts per second before I tried > polling, and I'm not sure how many packets the interfaces (some > fxp, some em) can buffer up. I'm going to try it, but if it doesn't > work I will have to go back to interrupt-driven operation. You might be able if your network architecture allows it, to bring down the task load by increasing the MTU and enable jumbo frames. >From em(4): Support for Jumbo Frames is provided via the interface MTU setting. Selecting an MTU larger than 1500 bytes with the ifconfig(8) utility con‐ figures the adapter to receive and transmit Jumbo Frames. The maximum MTU size for Jumbo Frames is 16114. -- Mel ___ 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: GPUs on FBSD?
usleepl...@gmail.com writes: > > > as far as i know there have been Nvidia maintained/improved > > > drivers for FreeBSD for ages ( ls /usr/ports/x11 | grep -i nvid ) > > > > And see this from the Makefile: > > > > # Starting with version 1.0-7667, NVidia has dropped support for > > # numerous "legacy" GPUs. Consult NVidia README (the Appendix) to > > # find out whether you need to use legacy driver version and install > > # one of corresponding `x11/nvidia-driver-71', > > # `x11/nvidia-driver-96', or `x11/nvidia-driver-173' slave ports. > > > > > are you trying to be right afterall? Someone's confused. If it's me, that needs to get fixed. Robert Huff ___ 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: sending mail with attachments always fail (FreeBSD/pf)
On Sat, 21 Nov 2009 16:27:20 +0100 Matthias Apitz wrote: > El día Saturday, November 21, 2009 a las 08:59:12PM +0600, Victor > Lyapunov escribió: > > > Hi all, > > > > I have production network with FreeBSD box acting as firewall. The > > problem emerge as soon as users send mail with attachments. (Sending > > mail without attachments always succeeds). Basically, when a user > > tries to send a message, only part of it transmitted before > > connection is interrupted and sending fails. The problem persists > > only when pf is enabled. > > I think concerning TCP/IP there is no diff between a mail with or w/o > attachment, it is just talking SMTP to a remote server and only the > size, i.e, the number of IP pkgs, differs; the content is anyway; This kind of thing is often due to a mtu blackhole - when a larger email causes a full size IP packet to be sent. I don't see why PF should make a difference though, IFAIK it's supposed to let ICMP through when it's learned state on a tcp connection. > I never used S/SA as flags in my rules, only S. S/SA is correct, it mean look at SYN and ACK and match if only SYN is set, S matches on SYN irrespective of whether ACK is set. ___ 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: Dump
2009/11/21 Bernt Hansson : > Matthew Seaman skrev: >> >> Bernt Hansson wrote: >>> >>> Hello list. >>> >>> I've been testing backups with dump, works well BUT >>> -L does not work. For example >>> >>> dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d >> >> I believe that you need to tell dump the mount point of the file system in >> order for it to create a snapshot, rather than the device file for the >> partition. (ie. snapshotting only makes sense on a mounted read-write >> filesystem). >> >> Also, if you're dumping a snapshotted FS to a local file, then bump up the >> cachesize to improve performance a lot. Add '-C 32' to your command-line. > > Ok. I've tested this > dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 > /usr/home > > The error is > mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument > dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory > Just for sanity... Are you root? Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ 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: 7.2, usb mouse, uhub0: device problem
> Date: Fri, 20 Nov 2009 15:58:27 -0500
> From: Jerry
> Subject: Re: 7.2, usb mouse, uhub0: device problem
> (IOERROR),
> To: freebsd-questions@freebsd.org
> Message-ID: <20091120155827.7526e...@scorpio.seibercom.net>
> Content-Type: text/plain; charset=US-ASCII
>
>
> Thanks! I guess the 'wireless' menu item is either not
> working, or I am
> using it incorrectly on that site.
There is no "wireless" menu item on the product search page:
http://www.usb.org/kcompliance/view
The "Wireless Products Only" Radio button refers to products using the Wireless
USB Standard that I assume is supposed to be some kind of blue-tooth killer.
("All Retail Categories" returns only 117 results)
http://www.usb.org/developers/wusb/
If you select the "Hi-Speed Products Only" option, only one mouse is returned.
(I never found serial mice working at only 9600bps unresponsive; barring dirty
rollers. Newer mice have higher resolution I guess.)
Regards,
James Phillips
PS: I genuinely did not see the radio buttons when looking for menu items (I
did check the drop-down lists). Not sure how proper it is to declare radio
buttons "not menu items." In my mind, menu items have an immediate effect. I
have seen web-pages where choosing a drop-down item affects other drop-down
lists in the page.
PPS: The choices of "effect" and "affect" are intentional. This page agrees
with me (Still not sure if I'm correct):
http://www.writersblock.ca/tips/monthtip/tipsep99a.htm
__
Ask a question on any topic and get answers from real people. Go to Yahoo!
Answers and share what you know at http://ca.answers.yahoo.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: Dump
On Sat, Nov 21, 2009 at 04:12:42AM +0100, Bernt Hansson wrote: > Matthew Seaman skrev: > > Bernt Hansson wrote: > > > > > > I've been testing backups with dump, works well BUT > > > -L does not work. For example > > > > > > dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d > > > > I believe that you need to tell dump the mount point of the file system in > > order for it to create a snapshot, rather than the device file for the > > partition. (ie. snapshotting only makes sense on a mounted read-write > > filesystem). > > > > Also, if you're dumping a snapshotted FS to a local file, then bump up the > > cachesize to improve performance a lot. Add '-C 32' to your command-line. > > Ok. I've tested this > dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 > /usr/home > dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 > /usr/home > > The error is > mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument > dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory Aargh. Must have missed the above when I last replied. That error message indicates you're running dump without proper privileges. Run dump as root, or add yourself to the operator group: pw groupmod operator -m bernt -- George ___ 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: sending mail with attachments always fail (FreeBSD/pf)
El día Saturday, November 21, 2009 a las 08:59:12PM +0600, Victor Lyapunov escribió: > Hi all, > > I have production network with FreeBSD box acting as firewall. The > problem emerge as soon as users send mail with attachments. (Sending > mail without attachments always succeeds). Basically, when a user > tries to send a message, only part of it transmitted before connection > is interrupted and sending fails. The problem persists only when pf is > enabled. I think concerning TCP/IP there is no diff between a mail with or w/o attachment, it is just talking SMTP to a remote server and only the size, i.e, the number of IP pkgs, differs; the content is anyway; > My ruleset: > scrub in all fragment reassemble > block drop on em0 all > pass inet proto tcp from 192.168.0.0/24 to any port = smtp flags S/SA keep > state > pass inet proto tcp from 192.168.0.0/24 to any port = pop3 flags S/SA keep > state > pass inet proto tcp from 192.168.0.0/24 to any port = imap flags S/SA keep > state > pass inet proto tcp from 192.168.0.0/24 to any port = smtps flags S/SA > keep state > pass inet proto tcp from 192.168.0.0/24 to any port = pop3s flags S/SA > keep state > pass proto udp from any to any port = domain keep state I never used S/SA as flags in my rules, only S. More I can' see. HIH (if not watch with some tcpdump(1) what's going on between the NIC and the remote server). matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu ___ 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: GPUs on FBSD?
On Sat, Nov 21, 2009 at 4:04 PM, Robert Huff wrote: > > usleepl...@gmail.com writes: > > > as far as i know there have been Nvidia maintained/improved > > drivers for FreeBSD for ages ( ls /usr/ports/x11 | grep -i nvid ) > > And see this from the Makefile: > > # Starting with version 1.0-7667, NVidia has dropped support for > # numerous "legacy" GPUs. Consult NVidia README (the Appendix) to > # find out whether you need to use legacy driver version and install > # one of corresponding `x11/nvidia-driver-71', > # `x11/nvidia-driver-96', or `x11/nvidia-driver-173' slave ports. > > are you trying to be right afterall? regards, usleep > > >Robert Huff > > ___ 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: php4-gd
On Sat, 21 Nov 2009 13:23:39 +0100, Ruben de Groot wrote: > On Sat, Nov 14, 2009 at 11:39:34PM +0100, Roman Neuhauser typed: > > more like: you should have upgraded to PHP5 two years ago. PHP4 is dead, > > baby. it's dead... > > Like COBOL and FORTRAN are dead? > > ;) More as... dead like the mainframe. :-) -- 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: GPUs on FBSD?
usleepl...@gmail.com writes: > as far as i know there have been Nvidia maintained/improved > drivers for FreeBSD for ages ( ls /usr/ports/x11 | grep -i nvid ) And see this from the Makefile: # Starting with version 1.0-7667, NVidia has dropped support for # numerous "legacy" GPUs. Consult NVidia README (the Appendix) to # find out whether you need to use legacy driver version and install # one of corresponding `x11/nvidia-driver-71', # `x11/nvidia-driver-96', or `x11/nvidia-driver-173' slave ports. Robert Huff ___ 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: GPUs on FBSD?
usleepl...@gmail.com writes: > as far as i know there have been Nvidia maintained/improved drivers for > FreeBSD for ages ( ls /usr/ports/x11 | grep -i nvid ) I was looking at x11-drivers: h...@jerusalem>> dir /usr/ports/x11-drivers | grep video-n drwxr-xr-x 2 root wheel 512 Aug 21 20:20 xf86-video-neomagic drwxr-xr-x 2 root wheel 512 Aug 21 20:20 xf86-video-newport drwxr-xr-x 2 root wheel 512 Aug 21 20:20 xf86-video-nouveau drwxr-xr-x 2 root wheel 512 Aug 21 20:20 xf86-video-nsc drwxr-xr-x 2 root wheel 512 Aug 21 20:20 xf86-video-nv If that's true, shouldn't the nvidia-drivers be moved? Robert Huff ___ 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"
sending mail with attachments always fail (FreeBSD/pf)
Hi all, I have production network with FreeBSD box acting as firewall. The problem emerge as soon as users send mail with attachments. (Sending mail without attachments always succeeds). Basically, when a user tries to send a message, only part of it transmitted before connection is interrupted and sending fails. The problem persists only when pf is enabled. My ruleset: scrub in all fragment reassemble block drop on em0 all pass inet proto tcp from 192.168.0.0/24 to any port = smtp flags S/SA keep state pass inet proto tcp from 192.168.0.0/24 to any port = pop3 flags S/SA keep state pass inet proto tcp from 192.168.0.0/24 to any port = imap flags S/SA keep state pass inet proto tcp from 192.168.0.0/24 to any port = smtps flags S/SA keep state pass inet proto tcp from 192.168.0.0/24 to any port = pop3s flags S/SA keep state pass proto udp from any to any port = domain keep state This is what i get from pfctl -si just after #/etc/rc.d/pf start # pfctl -si Status: Enabled for 0 days 00:00:09 Debug: Urgent State Table Total Rate current entries0 searches 00.0/s inserts00.0/s removals 00.0/s Counters match 00.0/s bad-offset 00.0/s fragment 00.0/s short 00.0/s normalize 00.0/s memory 00.0/s bad-timestamp 00.0/s congestion 00.0/s ip-option 00.0/s proto-cksum00.0/s state-mismatch 00.0/s state-insert 00.0/s state-limit00.0/s src-limit 00.0/s synproxy 00.0/s After I try to send some mail with attachments a couple of times(which always fail), i get this from pfctl -si: Status: Enabled for 0 days 00:02:58 Debug: Urgent State Table Total Rate current entries 48 searches13137.4/s inserts 1310.7/s removals 830.5/s Counters match1520.9/s bad-offset 00.0/s fragment 00.0/s short 00.0/s normalize 00.0/s memory 00.0/s bad-timestamp 00.0/s congestion 00.0/s ip-option 00.0/s proto-cksum00.0/s state-mismatch220.1/s state-insert 00.0/s state-limit00.0/s src-limit 00.0/s synproxy 00.0/s Any suggestions/ideas would be appreciated, Best regards, Victor FreeBSD router 7.2-RELEASE FreeBSD 7.2-RELEASE #4: Sun May 3 23:29:04 2009 r...@router:/usr/obj/usr/src/sys/GENERIC i386 ___ 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: GPUs on FBSD?
On Sat, Nov 21, 2009 at 3:06 PM, Robert Huff wrote: > > usleepl...@gmail.com writes: > > > The talk/announcement on the Nvidia forum is about a native video > > driver for amd64 i believe. A lot of people are waiting for this > > ( currently there is only Nvidia support for i386 ). > > I do not believe this is correct. _As I understand it_ there > are (currently) two options: > >1) "nv" driver; written by nVidia, but does not support >recent (last N generations) cards, works only for i386, >and does not support 100% of 3d functions. Breakage >fixed, but no new features added. >2) "noveau" driver; written by third parties, works for i386 >and amd64 (maybe for others). For what works, see the >(hopefully outdated) web page. > >Under development: > >3) ""; written (and maintained/improved) by nVidia, words >for i386 and amd64, supports all cards, supports all >functionality. ETA not announced; no public testing yet. > >If anyone knows better, please correct this. > > as far as i know there have been Nvidia maintained/improved drivers for FreeBSD for ages ( ls /usr/ports/x11 | grep -i nvid ) and for example: %kldstat Id Refs AddressSize Name 18 0xc040 5ec918 kernel 21 0xc09ed000 753c90 nvidia.ko 31 0xc497c000 e000 fuse.ko 41 0xc4b64000 2000 rtc.ko The announcement may be about a unified driver, i don't know about that. 3. "nvidia". have X use the Nvidia supplied driver. Works for me? xorg.conf: Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" Option "AddARGBGLXVisuals" "True" Option "DisableGLXRootClipping" "true" Option "TwinView" "True" Option "SecondMonitorHorizSync" "31-80" Option "SecondMonitorVertRefresh" "56-76" Option "TwinViewOrientation" "RightOf" Option "MetaModes" "1280x1024, 1280x1024" Option "DamageEvents" "True" EndSection Is this not what you meant? regards, usleep >Robert Huff > > > > ___ 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: Dump
George Davidovich said the following on 2009-11-21 10:52: On Sat, Nov 21, 2009 at 04:12:42AM +0100, Bernt Hansson wrote: Matthew Seaman skrev: Bernt Hansson wrote: I've been testing backups with dump, works well BUT -L does not work. For example dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d I believe that you need to tell dump the mount point of the file system in order for it to create a snapshot, rather than the device file for the partition. (ie. snapshotting only makes sense on a mounted read-write filesystem). Actually, the above isn't correct. A device special is fine. From the dump(8) manpage: The file system to be dumped is specified by the argument filesystem as either its device-special file or its mount point (if that is in a standard entry in /etc/fstab). The criteria unique to live dumps is that /dev/ad0s2d must be already mounted, and there must be a .snap directory in its root. You've since changed your command, so I won't address what the problem might have been. Also, if you're dumping a snapshotted FS to a local file, then bump up the cachesize to improve performance a lot. Add '-C 32' to your command-line. Ok. I've tested this dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 /usr/home Was the change from 'dump -0' to 'dump -1' intentional? Yes. Dump levels are rarely chosen to be sequential, but a level of 1 or greater is generally performed after a level 0 dump. Yes. I've done a level 0 dump. The error is mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory The directory exist. drwxrwx--- 2 root operator 512 16 Nov 19:19 .snap You've now specified what's likely a directory (/usr/home), not a device-special or mount point. Your choices of valid filesystems can be determined by running df(1) and examining the first and last columns. On a typical install those two columns might be: Filesystem Mounted on /dev/ad0s1a / devfs /dev # ignore this line /dev/ad0s1e /tmp /dev/ad0s1f /usr /dev/ad0s1d /var Pick one. I prefer device names. This is from my original post dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d ad0s2d is /usr/home FWIW, if you're going to be using dump regularly (i.e. multiple dump levels and/or multiple hosts) and dumping to files, I'd suggest a naming convention of I am going to use it on a regular basis, at least that is my intention. If I can get the -L flag to work hostname-20090405-usr-0 I see what you mean. But since I already have a script (tar) that takes care of that. to save you the grief of date fragility, and give you a meaningful display in 'ls -l' when restoring. So, for a level 0 dump on your system, your commands might be: dumpdir=/home/bernt/disk2 dump -0auL -C 64 -f $dumpdir/hostname-20091121-root-0 -h 0 / dump -0auL -C 64 -f $dumpdir/hostname-20091121-usr-0 -h 0 /usr dump -0auL -C 64 -f $dumpdir/hostname-20091121-var-0 -h 0 /var ___ 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: GPUs on FBSD?
usleepl...@gmail.com writes: > The talk/announcement on the Nvidia forum is about a native video > driver for amd64 i believe. A lot of people are waiting for this > ( currently there is only Nvidia support for i386 ). I do not believe this is correct. _As I understand it_ there are (currently) two options: 1) "nv" driver; written by nVidia, but does not support recent (last N generations) cards, works only for i386, and does not support 100% of 3d functions. Breakage fixed, but no new features added. 2) "noveau" driver; written by third parties, works for i386 and amd64 (maybe for others). For what works, see the (hopefully outdated) web page. Under development: 3) ""; written (and maintained/improved) by nVidia, words for i386 and amd64, supports all cards, supports all functionality. ETA not announced; no public testing yet. If anyone knows better, please correct this. Robert Huff ___ 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"
Glassfish v3 server: Admin port in use
Hey everyone, I'm trying to deploy a Glassfish v3 server on my workstation since I need to do some jsf-developement. However when I try to start the server it keeps telling me the admin port I'm trying to use is allready in use by an other process, no matter what port I use. However I'm 100% certain there is nothing running on the port it should use (sockstat confirms that). Has anyone seen this type of behaviour and/or knows how to fix it ? I'm running FreeBSD 8.0-RC1 with jdk16 installed from ports. Full log is here: http://fstaals.net/junk/glassfish.txt -- - Frank ___ 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: php4-gd
On Sat, 21 Nov 2009 13:23:39 +0100 Ruben de Groot replied: >Like COBOL and FORTRAN are dead? Maybe not "DEAD", but definitely comatose. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | A friend of mine won't get a divorce, because he hates lawyers more than he hates his wife. ___ 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: Dump
Mike Clarke said the following on 2009-11-21 10:03: On Saturday 21 November 2009, Bernt Hansson wrote: Ok. I've tested this dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 /usr/home The error is mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or directory Does the .snap directory exist, and with the correct ownership and permissions? Yes and yes drwxrwx--- 2 root operator 512 16 Nov 19:19 .snap From the man page: "If the .snap directory does not exist in the root of the file system being dumped, a warning will be issued and the dump will revert to the standard behavior. This problem can be corrected by creating a .snap directory in the root of the file system to be dumped; its owner should be ``root'', its group should be ``operator'', and its mode should be ``0770''." ___ 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: php4-gd
On Sat, Nov 14, 2009 at 11:39:34PM +0100, Roman Neuhauser typed: > > more like: you should have upgraded to PHP5 two years ago. PHP4 is dead, > baby. it's dead... Like COBOL and FORTRAN are dead? ;) ___ 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: GPUs on FBSD?
2009/11/20 Gary Kline : > On Fri, Nov 20, 2009 at 02:56:03PM +, Chris Rees wrote: >> 2009/11/20 Anton Shterenlikht : >> > Anybody knows of working GPUs under FBSD on any arch? >> > Any advice? >> > >> >> Your question could have been phrased better but that's the teacher in >> me! >> >> Nvidia GPUs work on IA-32 machines, but AFAIK there's still no amd64 driver. >> >> Food for thought: http://forums.freebsd.org/showthread.php?t=398 >> >> My advice: Get an Nvidia card, and install FreeBSD/i386. >> >> Chris >> > > hi chris, > > i'm taking this offlist so i don't show my totsl ignorance about > running X11 and my new intel duo with i386 and 7.2. > > do i need a nvidia card to run X? the graphics show the dell > circle just before the boot sequence but that may be built into the > bios. > > (another reason for keeping this offlist is that my network pal says > to NOT run X on my server ... simply for the sake of simplicity. i > will not use the computer for anything except CTWM for root, which > will make doing sysadmin tasks vastly easier. nutshell: if i do need > a video card for my dell inspiron 530, what kind? > > tia, > > gary > Nah, X will run on more or less anything; it's not particularly heavy. If you just want to do the odd thing, you might be better off with /u/p/net/vnc and display it on another machine. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ 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: GPUs on FBSD?
On Sat, Nov 21, 2009 at 12:28 PM, Anton Shterenlikht wrote: > On Fri, Nov 20, 2009 at 08:11:57PM +0100, usleepl...@gmail.com wrote: > > On Fri, Nov 20, 2009 at 6:16 PM, Daniel C. Dowse > wrote: > > > > > On Fri, 20 Nov 2009 11:46:57 + > > > Anton Shterenlikht wrote: > > > > > > > Anybody knows of working GPUs under FBSD on any arch? > > > > Any advice? > > > > > > > > > > I using a nvidia fx5500 with the latest driver 173.14.22 on i386 and > > > it works perfect. And it was no pain to get 3d working for games. > > > > > > I am still wondering what this thread is actually about: is it about > > hardware accelerated video or about offloading general computation to the > > GPU ( CUDA et al. ). > > the latter. My question was about HPC application of GPUs. Use of GPGPUs > for HPC under linux is growing very fast, with cuda and opencl. However, > I doubt any GPUs will be supported on fbsd. At least not at this stage. > Unless somebody knows better? > > many thanks > I looked at CUDA lately and according to Nvidia the library stuff/driver you need is not available for FreeBSD ( Linux, Windows ). I forgot about if it is supported on Mac. The talk/announcement on the Nvidia forum is about a native video driver for amd64 i believe. A lot of people are waiting for this ( currently there is only Nvidia support for i386 ). I don't think they are talking about including CUDA support. There is no OpenCL implementation for FreeBSD that i am aware of ( did look ). regards, usleep > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > ___ 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: BTX Loader crashes -- Help wanted
Ronald F. Guilmette wrote: [snip] >>Try 8RC3 and see if any difference. I believe some work in this area may >>have occurred. > > I just tried it. Alas, same result. I follow the -CURRENT and -STABLE mail lists as well as this one. Though this particular problem does not pertain to me, I seem to recall some traffic off and on about this subject occasionally. So it is known. The place to get the developers to look is wrt to 8.0, so if the problem is well documented they may be more inclined to look into it. If the bootonly, install CD, or LiveFS CD for 8-RC3 can be used to reproduce the problem concentrate here. >>I don't believe you are the first to experience this. > Well, I'm just about to file a new PR on this, but I'll refrain if > someone else has alreadyt done so. Do you have an eisting PR number > on this? There are quite a number and a few of which are very similar in that they directly reference boot loader crashes. You could review the ones that seem to match the closest to your situation directly (e.g. hardware and crash- dump wise), particularly the BTX crash associated with booting from SATA CD/DVD. Eye them towards using as a template to get started. The more exacting and succinct the PR the more likely to stimulate interest. You can reference the handful that match the closest by number in your own PR. Be very exact to localize the trouble to specifically SATA CD/DVD hardware. If the box will boot and install fine from a PATA CD/DVD drive to a SATA hard drive be sure to include this. You have a VIA VT8237A controller on that board so that aspect should work. This will serve to isolate and confine the problem to be examined to a very specific issue. This increases the chances someone may look into it. [snip] > > Shsh! I literally _just_ bought this new SATA DVD drive, and I went > with SATA because I believed that (a) the world is slowly but surely > switching everything over to SATA and (b) SATA has been around long enough > now that FreeBSD related bugs should have all been shaken out by now. > > Please excuse my snarkiness, but... I guess I was wrong about the latter. > >>If 8 does the same thing file a PR in order to bring the attention of the >>developers. There may be one, or more, already on the subject. > > Well, I did a search on the PR database for "BTX" and I'm looking at all > those PRs... some of them going back to 2004, which doesn't exactly > inspire confidence about a possible timely fix... and I don't see anything > in the subjects that quite matched up to what I'm talking about. If you just need the box to work immediately use a PATA CD/DVD. If you have the time to deal with it, attract the attention of developer(s), and have the time to work with them it serves the interests of the larger community. Others have had and will have your problem and getting it fixed for you will just mean many others will not go through what you are currently experiencing. > And ah... while we are on the subject... > > If I do file a PR on this, then at long last I'll need to know the answers > to the two questions that have been in the back of my mind for ages, > regarding PRs... > >1) What do the various severity codes mean? >2) What do the various proirity codes mean? http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/ http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pr-guidelines/ Might be good reading. I should read them again myself. It's been a while. > > I've never filed a PR with severity "critical" or with priority "high" > because I've always figured that this may be a good way to get the > developers to view _all_ one's future (and past) PRs with a suspicious/ > jaundiced eye... you know... the-boy-who-cried-wolf syndrome. > > I don't want to be labeled as a nut case or an incessant complainer, but > for _this_ issue I'm thinking that severity==critical and/or > priority==high > may be appropriate. I mean jeezzz Louise! If one can't even install from > the distribution CDs/DVDs on perfectly good hardware... (And it's not > like the whole SATA interface standard is exactly ``new'' or anything > anymore.) > > So? Any advice? Should I stick my neck out and label this PR either > severity==critical or priority==high ? > There is always going to be a certain subjectivity present here. What is life and death important to one person may not be to another. I believe a commonly accepted dividing line can be found when you consider the usage of the system(s) in question. If you are a sysadmin or consultant who is being paid money to maintain mission critical servers then it warrants a higher level of concern than a single user at home with a desktop PC. If you are racking a hundred Dell 2950's and have a problem it is critical. If you are a single PC user at home with a desktop, not so much. I do understand your concern wrt to "the boy who cried wolf" and it does matter. You stand more of a c
Re: GPUs on FBSD?
On Fri, Nov 20, 2009 at 08:11:57PM +0100, usleepl...@gmail.com wrote: > On Fri, Nov 20, 2009 at 6:16 PM, Daniel C. Dowse wrote: > > > On Fri, 20 Nov 2009 11:46:57 + > > Anton Shterenlikht wrote: > > > > > Anybody knows of working GPUs under FBSD on any arch? > > > Any advice? > > > > > > > I using a nvidia fx5500 with the latest driver 173.14.22 on i386 and > > it works perfect. And it was no pain to get 3d working for games. > > > > I am still wondering what this thread is actually about: is it about > hardware accelerated video or about offloading general computation to the > GPU ( CUDA et al. ). the latter. My question was about HPC application of GPUs. Use of GPGPUs for HPC under linux is growing very fast, with cuda and opencl. However, I doubt any GPUs will be supported on fbsd. At least not at this stage. Unless somebody knows better? many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 ___ 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: Dump
On Sat, Nov 21, 2009 at 04:12:42AM +0100, Bernt Hansson wrote: > Matthew Seaman skrev: > > Bernt Hansson wrote: > > > > > > I've been testing backups with dump, works well BUT > > > -L does not work. For example > > > > > > dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d > > > > I believe that you need to tell dump the mount point of the file > > system in order for it to create a snapshot, rather than the device > > file for the partition. (ie. snapshotting only makes sense on a > > mounted read-write filesystem). Actually, the above isn't correct. A device special is fine. From the dump(8) manpage: The file system to be dumped is specified by the argument filesystem as either its device-special file or its mount point (if that is in a standard entry in /etc/fstab). The criteria unique to live dumps is that /dev/ad0s2d must be already mounted, and there must be a .snap directory in its root. You've since changed your command, so I won't address what the problem might have been. > > Also, if you're dumping a snapshotted FS to a local file, then bump > > up the cachesize to improve performance a lot. Add '-C 32' to your > > command-line. > > Ok. I've tested this > dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 > /usr/home Was the change from 'dump -0' to 'dump -1' intentional? Dump levels are rarely chosen to be sequential, but a level of 1 or greater is generally performed after a level 0 dump. > The error is mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: > Invalid argument dump: Cannot create /usr/home/.snap/dump_snapshot: No > such file or directory You've now specified what's likely a directory (/usr/home), not a device-special or mount point. Your choices of valid filesystems can be determined by running df(1) and examining the first and last columns. On a typical install those two columns might be: Filesystem Mounted on /dev/ad0s1a / devfs /dev # ignore this line /dev/ad0s1e /tmp /dev/ad0s1f /usr /dev/ad0s1d /var Pick one. I prefer device names. FWIW, if you're going to be using dump regularly (i.e. multiple dump levels and/or multiple hosts) and dumping to files, I'd suggest a naming convention of hostname-20090405-usr-0 to save you the grief of date fragility, and give you a meaningful display in 'ls -l' when restoring. So, for a level 0 dump on your system, your commands might be: dumpdir=/home/bernt/disk2 dump -0auL -C 64 -f $dumpdir/hostname-20091121-root-0 -h 0 / dump -0auL -C 64 -f $dumpdir/hostname-20091121-usr-0 -h 0 /usr dump -0auL -C 64 -f $dumpdir/hostname-20091121-var-0 -h 0 /var -- George ___ 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: Dump
On Saturday 21 November 2009, Bernt Hansson wrote: > Ok. I've tested this > dump -1 -a -u -L -C 64 -h 0 -f > /usr/home/bernt/disk2/dump.backup.home.2 /usr/home > > The error is > mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid > argument dump: Cannot create /usr/home/.snap/dump_snapshot: No such > file or directory Does the .snap directory exist, and with the correct ownership and permissions? From the man page: "If the .snap directory does not exist in the root of the file system being dumped, a warning will be issued and the dump will revert to the standard behavior. This problem can be corrected by creating a .snap directory in the root of the file system to be dumped; its owner should be ``root'', its group should be ``operator'', and its mode should be ``0770''." -- Mike Clarke ___ 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: BTX Loader crashes -- Help wanted
"Ronald F. Guilmette" wrote: > If one can't even install from the distribution CDs/DVDs > on perfectly good hardware ... it's not like the whole SATA > interface standard is exactly ``new'' or anything anymore.) > > ... Should I stick my neck out and label this PR > either severity==critical or priority==high ? Before filing a PR at all, you might want to check what kind of SATA controller chip you've got. There have been several postings on the FreeBSD lists reporting that the Silicon Image 3112 should not be considered "perfectly good hardware". ___ 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"
ukbd_set_leds_callback:700: error=USB_ERR_STALLED
My personal workstation runs FreeBSD 8.0-PRE/amd64 on an oldish hardware (AMD socket 939 platform). Since I replaced my good old but broken IBM Model-M keyboard with a high-quality keyboard 'DASkeyboard', I receive this error message on the console: ukbd_set_leds_callback:700: error=USB_ERR_STALLED What does it means? Greatings, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
