Re: Chromium Crashes
Yes this is the latest build (5th June) of Chromium. I suppose I could revert to the 18.0.1025.168 version using portdowngrade until this fault is fixed. Glenn On Sun, 2012-06-10 at 10:37 +0530, Subhro Sankha Kar wrote: Hello, It looks like you have hit a documented bug. See this: http://code.google.com/p/chromium/issues/detail?id=125447 http://src.chromium.org/viewvc/chrome?view=revrevision=141116 Did you try upgrading your ports? Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On 10-Jun-2012, at 10:11 AM, The Todds wrote: I have just have built and installed Chromium 19.0.1084.52 from the ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 08:40:03 NZDT 2011 Portversion chromium-19.0.1084.52_2 = up-to-date with port On web sites which contains graphics Chromium crashes with the following error: [3152:171983296:14310963010:ERROR:CONSOLE(1)] Uncaught ReferenceError: ntp is not defined, source: (1) Any ideas how to resolve this issue. Glenn ___ 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: Chromium Crashes
Hello, On 10-Jun-2012, at 11:40 AM, The Todds wrote: Yes this is the latest build (5th June) of Chromium. I suppose I could revert to the 18.0.1025.168 version using portdowngrade until this fault is fixed. Glenn It looks like the port is lagging back from mainstream. You could also write to the maintainers. I am copying the maintainers just in case someone is already on it. Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On Sun, 2012-06-10 at 10:37 +0530, Subhro Sankha Kar wrote: Hello, It looks like you have hit a documented bug. See this: http://code.google.com/p/chromium/issues/detail?id=125447 http://src.chromium.org/viewvc/chrome?view=revrevision=141116 Did you try upgrading your ports? Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On 10-Jun-2012, at 10:11 AM, The Todds wrote: I have just have built and installed Chromium 19.0.1084.52 from the ports on my amd64 machine - 8.2-STABLE FreeBSD 8.2-STABLE #0: Sat Nov 5 08:40:03 NZDT 2011 Portversion chromium-19.0.1084.52_2 = up-to-date with port On web sites which contains graphics Chromium crashes with the following error: [3152:171983296:14310963010:ERROR:CONSOLE(1)] Uncaught ReferenceError: ntp is not defined, source: (1) Any ideas how to resolve this issue. Glenn ___ 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
Re: Problems with portupgrade libreoffice
On Sat, 09 Jun 2012 20:46:49 +, Walter Hurry wrote: On Sat, 09 Jun 2012 18:12:25 +0100, Dave Morgan wrote: On 09/06/12 at 04:41P, Walter Hurry wrote: FreeBSD 9 on x86_64. I am in the process of doing a portupgrade on libreoffice (from 3.4.4 to 3.5.2.5). During the build it has (so far) errored out 4 times, in the following modules: vcl framework sfx2 tail_build Each time, it told me to go into the subdirectory, do a gmake clean and a gmake -r there, then return to the top level and rerun make. This I duly did, but to my surprise, each time I ran the gmake -r, it completed successfully. When the top-level make finally succeeds, I intend simply to rerun the portupgrade, on the theory that seeing everything already made, it will just do the uninstall/reinstall, sort out the dependencies and so forth. Q1) Is this a sensible approach? Q2) Has anyone else seen this? What is going on? There is a thread in the forums which recommends removing boost-libs and boost-jam, building libreoffice then reinstalling them. I did this and it worked for me. Thanks. I'll try that and report back. Yes, that did the trick. It zoomed through! Very many thanks. I'll need to keep an eye on the forum, methinks. ___ 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: Making a bootable backup (hard)disk... how?
Hello. 2012/06/09 19:30:53 -0700 Ronald F. Guilmette r...@tristatelogic.com = To Arthur Chance : RFG Thank you Arthur, and yes, trying to back up a partition that's currently RFG mounted r/w using dd will almost certainly not produce the desired results. You can make snapshot to back up rw-mounted volume with dd. dump(8)ing rw-mounted ufs makes a snapshot behind the scenes. -- Peter Vereshagin pe...@vereshagin.org (http://vereshagin.org) pgp: A0E26627 ___ 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: Making a bootable backup (hard)disk... how?
On Sunday 10 June 2012 03:30:53 Ronald F. Guilmette wrote: I don't care to take own my system to make backups... and don't believe that I should have to do so, and thus, this is one of the reasons why I would prefer to use something like cpio. Also, I don't like backups taking longer than absolutely necessary, and this is why I am specifically _not_ attracted to either the dd solution or to dump/restore, Not an immediate solution but have you considered switching from UFS to ZFS ? If you have sufficient memory and CPU power then this might be worth the effort. Creating ZFS snapshots and backing them up incrementally with zfs send | zfs receive should be very quick. -- 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: Making a bootable backup (hard)disk... how?
From owner-freebsd-questi...@freebsd.org Sat Jun 9 21:33:57 2012 To: Arthur Chance free...@qeng-ho.org Date: Sat, 09 Jun 2012 19:30:53 -0700 From: Ronald F. Guilmette r...@tristatelogic.com Cc: freebsd-questions@freebsd.org Subject: Re: Making a bootable backup (hard)disk... how? In message 4fd38b9a.4010...@qeng-ho.org, Arthur Chance free...@qeng-ho.org wrote: There's a BFI (brute force and ignorance) way of doing it in the base system - dd. Provided your system disk is quiescent (ideally when running from a live CD or all partitions mounted read-only, otherwise pray to the deity of your choice) and the backup disk is a) at least as large as the system disk, and b) has the same sector size, then a simple dd from the system disk to the backup should work. Thank you Arthur, and yes, trying to back up a partition that's currently mounted r/w using dd will almost certainly not produce the desired results. And of course, as you correctly note also, the target partition had best be at least as big as the source (and perhaps even identical in size). I don't care to take own my system to make backups... and don't believe that I should have to do so, and thus, this is one of the reasons why I would prefer to use something like cpio. Also, I don't like backups taking longer than absolutely necessary, and this is why I am specifically _not_ attracted to either the dd solution or to dump/restore, because as I understand it, with either of these methods you end up copying perhaps a metric buttload worth of unallocated free disk space. (I would prefer not to do that. It just seems wasteful... of time, if nothing else.) Dump does *NOT* copy 'unallocated free disk space'. It does a directory- based traversal. And copies only the contents of the files encountered. does not copy 'deleted but still open' files, nor does it include deleted directory entries in the copy of the directory. dump _can_ be used on a r/w-mounted filesystem. It is smart enough to make multiple passes, note files that have changed since the prior pass, and re-copy those changed files into the archive. As long as changes are relatvely 'infrequent', and to 'small' files, dump will generally manage to outrun the changes. Since dump works through the O/S, it also catches data and/or meta-data changes that are buffered/cached in O/S memory that have not actually made it to disk, yet. Using dump on a mounted, active, writable filesystem is not recommended, but it -does- work adequately, assuming the write activity on the filesystem is low. *IF* the filesystem is fairly full, with source and dest arranged such that they do not saturate I/O controller capabilities, 'dd' (or, preferably 'ddd' which is a double-buffered drop-in replacement) with large buffers (several times the size of the 'on disk' cache'), _is_ the fastest way to make a backup of the data. Also, in one case, one of my partitions has one directory that contains a really massive amount of stuff, and I specifically _don't_ need any of that particular stuff (in that one directory) backed up. So again, I'm looking at tar or cpio or perhaps pax. (Of course cpio is more full-featured than tar, and I don't really know anything about pax, so that leaves me with cpio.) Pax (the portable archiver) is the new, improved, with miracle whitener cpio -- does everthing tradtional cpio does, and more. it will read/write four different (and mutually incompatable) 'cpio' formats, and two different 'tar' formats. One can replace pretty much any use of 'cpio' or 'tar' (or their cousins) with pax. It _is_ worth investigating. when. (Sigh. The good old daze when men were men, and the bits ran scared!) Moral of the story is that sometimes it actually does pay to be a smartass. Regards, rfg P.S. It really is a Damn Shame[tm] that nobody ever hacked FreeBSD cpio to make it be able to copy (a) the extra file flag/mode bits and/or (b) file ACLs and/or (c) file attributes. If pax doesn't already support extended flags, it would be a relatively trivial hack to get it to do so. Ditto for ACLs. pax uses libarchive (man 3 archive) which has the capabilities for handling those things in the description of an archive entry. One would probably want to declare it as a separate archive 'type' -- to support auto-detect of the inclusion of that 'extended' metadata. ___ 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 allow by MAC
Hi, how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support 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: Making a bootable backup (hard)disk... how?
In message alpine.bsf.2.00.1206092039260.71...@wonkity.com, you wrote: On Sat, 9 Jun 2012, Ronald F. Guilmette wrote: Also, I don't like backups taking longer than absolutely necessary, and this is why I am specifically _not_ attracted to either the dd solution or to dump/restore, because as I understand it, with either of these methods you end up copying perhaps a metric buttload worth of unallocated free disk space. No, that is one of the biggest advantages of dump over dd. dump knows UFS, and only copies occupied sectors and needed information. OK. I obviously got the Wrong Impression about dump/restore. Thanks for setting me straight. (I got the Wrong Impression, I think, because I have read assertions like ...dump backs up at the filesystem block level What does that mean exactly? Use of the term block level in this context makes me think of something operating along the lines of dd.) Also, in one case, one of my partitions has one directory that contains a really massive amount of stuff, and I specifically _don't_ need any of that... backed up. Directories and files can be skipped with the nodump flag. I am in your debt again. I really will start looking at dump/restore. P.S. It really is a Damn Shame[tm] that nobody ever hacked FreeBSD cpio to make it be able to copy (a) the extra file flag/mode bits and/or (b) file ACLs and/or (c) file attributes. A quick search shows dump should support ACLs. The other stuff is also there. Try it. http://www.wonkity.com/~wblock/docs/html/backup.html THANK YOU! I am finding the above document very helpful. It really never even occured to me that one could pipe the output of dump directly to restore. (Obviously, that pairing creates something very much along the lines of cpio's -p option... which is one thing that I _am_ already familiar with.) Now that I've read your helpful document, I do have three short follow-up questions... 1) In your example under the heading Copying Filesystems, the second shell command line shown is: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) Is that correct? Shouldn't it actually be this instead? dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt/usr restore -ruf -) I mean if the goal is to create a whole backup under /mnt that looks just like the whole original system, then shouldn't ``restoration'' of the /usr part of the original system go into /mnt/usr? 2) Towards the end of your document you mention rsync. Assuming that I have made a backup of my entire /usr partition (using dumprestore) into /mnt/usr and that at midnight every night from now on I want to simply refresh that and bring it up to date with the current contents of my actual /usr partition, what is the most proper way to do this? Should I use rsync for that? Or should I use dumprestore again? If that latter, then how exactly does that work? I mean if I do the pipeline from dump to restore as you have shown in your examples in your Copying Filesystems section, then what must I do in order prevent dump from dumping files that haven't changed? (And likewise, how do I prevent restore from trying to restore files under /mnt/usr that have not changed? Or is that answer to that question that I simply have to do the first thing, i.e. force dump not to dump any of the unchanged files?) 3) Assuming that I have a second disk to which I plan (now) to use dumprestore to make periodic copies of all of my ``normal'' (non-backup) filesystems onto. Assuming also that I've already installed the FreeBSD boot loader into the boot block on this second disk, and that I've already run fdisk bsdlabel on it so as to set up all of the partitioning to be essentially identical to my ``main'' system disk. Assuming that all of this is the case, by using dumprestore as you have shown in your document under the heading Copying Filesystems, will I have succeded at doing what I was first asking about in this thread, i.e. will I have successfully created a _bootable_ mirror of my main system disk... something that I can just plug in and go with, when and if disaster strikes and my main system disk suffers a horrifying head crash, you know, the day after the manufacturer's warranty period is up? Regards, rfg ___ 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 something we (as consumers of FreeBSD) need to be aware of?
On Sun, 10 Jun 2012 03:27:25 +0200 Damien Fleuriot articulated: On 9 Jun 2012, at 18:48, Chad Perrin per...@apotheon.com wrote: On Wed, Jun 06, 2012 at 11:42:37PM +0200, Damien Fleuriot wrote: On 6 Jun 2012, at 21:52, Dave U. Random anonym...@anonymitaet-im-inter.net wrote: Polytropon free...@edvax.de wrote: On Wed, 06 Jun 2012 11:47:11 +0100, Matthew Seaman wrote: Having to pay Verisign instead of Microsoft makes no difference: the point is why should I have to pay anything to a third party in order to run whatever OS I want on a piece of hardware I own? It's time to dump the Intel/Microshaft mafia forever. FreeBSD, OpenBSD, NetBSD, and even Linux have ports to many platforms. Why stay on Intel? It's an overgrown ugly mess. We need to stop buying Intel mafiaware with preinstalled Microshaft mafiware and run a free (or in the case of Linux apparently free) OS on free hardware. There are increasing numbers of SBCs and plenty of used servers on Ebay. They're all built better than commodity Intel mafiaware. Good riddance! You have no idea what you're talking about. This kind of religious propaganda post is neither constructive nor helpful. It should be noted that your tone is neither constructive nor helpful, to say nothing of your contentless response. Do you have anything useful to say in response to what Dave U. Random contributed -- perhaps a thoughtful refutation of some specific point(s)? I hope you have more of value to contribute than your obvious disdain for people who disagree with you about something (without even specifying on what points you disagree). If you had bothered to read all the other mails I've posted on this very specific thread, you wouldn't need to ask the question. If you're going to participate in the Linux zealots' propaganda that makes OSS defenders sound so ridiculous and delusional, so be it. Fact is, if Microsoft didn't deliver acceptable products, people wouldn't use them. Calling them a mafia is neither constructive (I invite you to look up the word mafia in a thesaurus), nor backed up by actual facts. OP is just going on a rampage about MS and intel. You want to follow his advice and advocate the exclusive use of alpha machines ? I guess we'll have to agree to disagree here. No, I'm not gonna use alphas. And no, I'm not going to let a random person (hey, choice words !) call intel or MS a mafia just because he's on a zealot crusade. You might want to take a minute to consider the contributions of both to computing. Without MS (and IBM amongst others) it's possible that computing would never have reached such an audience as it has. So I'm going with the (possibly false) assumption that without MS and other major actors, not many people would use computers nowadays. All this magnificent OSS wouldn't be of much use then. After all, who would need FreeBSD servers to host web sites that had neither visitors nor purpose ? One might see MS as the ultimate evil, yet they're strongly implemented in corporate IT. One might wonder why, before engaging in a crusade, and brandishing empty words as their weapons. I invite you to re-read OP's post and highlight what in mafiaware, wintel and microshaft you find constructive. I also invite you to read all his points about why exactly intel is an overgrown ugly mess. I regret to report I have found none, might you point them out for me ? Now, I shall leave you to read my other posts on this secure boot topic, that you might quit claiming I have nothing to contribute.___ It is fairly easy to understand both sides in this discussion. When Microsoft supporters refer to open-source software as open-sore or socialist-software the FOSS community becomes enraged. However, when the open-source community retaliates it is considered acceptable. Quite frankly I read far more Microsoft based forums than open-source based ones and I can say without a doubt, at least in my experience, Microsoft proponents never attack open-source with the venomous hatred that open-source attacks Microsoft. In fact, the majority of Microsoft users that I know could not care less about what they consider an overly burdensome (geeky) open-source operating system. The whole argument can probably be boiled do to this: Disparaging other operating systems (Microsoft) and pointing out its failures is beneficial, constructive and therapeutic. Pointing out problems and failures regarding your own OS is destructive and flame bait. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: Making a bootable backup (hard)disk... how?
On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: (I got the Wrong Impression, I think, because I have read assertions like ...dump backs up at the filesystem block level What does that mean exactly? Use of the term block level in this context makes me think of something operating along the lines of dd.) Rather than reading just the contents of files, dump operates at a lower level, backing up all of the blocks used by a filesystem. 1) In your example under the heading Copying Filesystems, the second shell command line shown is: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) Is that correct? Shouldn't it actually be this instead? dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt/usr restore -ruf -) I mean if the goal is to create a whole backup under /mnt that looks just like the whole original system, then shouldn't ``restoration'' of the /usr part of the original system go into /mnt/usr? The mount command above that is mount /dev/da0s1f /mnt The f indicates it's a split filesystem layout, where /, /var, /tmp, and /usr are separate filesystems in different partitions. That's a traditional layout in FreeBSD. bsdinstall in FreeBSD 9 creates a single filesystem, / . Restoring a dump of a /usr filesystem would go to /mnt/usr in that case. (That would mean you are converting from the split layout to a single filesystem, because with a combined filesystem you can't easily back up just /usr with dump. dump does not cross filesystems when making a backup.) 2) Towards the end of your document you mention rsync. Assuming that I have made a backup of my entire /usr partition (using dumprestore) into /mnt/usr and that at midnight every night from now on I want to simply refresh that and bring it up to date with the current contents of my actual /usr partition, what is the most proper way to do this? Should I use rsync for that? Or should I use dumprestore again? If that latter, then how exactly does that work? I mean if I do the pipeline from dump to restore as you have shown in your examples in your Copying Filesystems section, then what must I do in order prevent dump from dumping files that haven't changed? (And likewise, how do I prevent restore from trying to restore files under /mnt/usr that have not changed? Or is that answer to that question that I simply have to do the first thing, i.e. force dump not to dump any of the unchanged files?) See the dump man page about dump levels. I have not tried a dump level higher than zero with a dump|restore copy, but expect it to work. rsync will do it, and would be my choice for that; start with -aH for options, and --exclude might be used for some directories that don't need to be copied. Also see the sysutils/rsnapshot port for an interesting snapshot use. Combined with a bootable FreeBSD like mfsBSD (http://mfsbsd.vx.sk/), that might be a workable alternative to creating a bootable backup. 3) Assuming that I have a second disk to which I plan (now) to use dumprestore to make periodic copies of all of my ``normal'' (non-backup) filesystems onto. Assuming also that I've already installed the FreeBSD boot loader into the boot block on this second disk, and that I've already run fdisk bsdlabel on it so as to set up all of the partitioning to be essentially identical to my ``main'' system disk. Assuming that all of this is the case, by using dumprestore as you have shown in your document under the heading Copying Filesystems, will I have succeded at doing what I was first asking about in this thread, i.e. will I have successfully created a _bootable_ mirror of my main system disk... something that I can just plug in and go with, when and if disaster strikes and my main system disk suffers a horrifying head crash, you know, the day after the manufacturer's warranty period is up? With some tuning, yes. /etc/fstab mountpoints often won't match when such a drive is connected to a different port or new system. Use gpart(8) GPT labels or tunefs(8) filesystem labels. Likewise with the Ethernet board, so see rc.conf(5) about ifconfig_DEFAULT. gpart and GPT are easier than fdisk and bsdlabel. I really need to flip that disk setup article upside down, with gpart first as the new goodness. See also: http://www.wonkity.com/~wblock/docs/html/labels.html http://www.wonkity.com/~wblock/docs/html/disksetup.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: how to allow by MAC
come on , someone help please, On Sun, Jun 10, 2012 at 5:43 PM, Bill Yuan byc...@gmail.com wrote: Hi, how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support 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: how to allow by MAC
Hi, Reference: From: Bill Yuan byc...@gmail.com Date: Sun, 10 Jun 2012 21:09:01 +0800 Message-id: CAC+JH2ySQVCSXY+3Grh+Qe=li3wzsyu8czq3sa1w3azgpjp...@mail.gmail.com Bill Yuan wrote: come on , someone help please, On Sun, Jun 10, 2012 at 5:43 PM, Bill Yuan byc...@gmail.com wrote: Hi, how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Maybe others ignored it for the same reason I did: blocking by MAC number seems weird of no interest, I block pass by IP net number. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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 allow by MAC
Julian H. Stacey wrote: Bill Yuan wrote: come on , someone help please, On Sun, Jun 10, 2012 at 5:43 PM, Bill Yuan byc...@gmail.com wrote: Hi, how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Maybe others ignored it for the same reason I did: blocking by MAC number seems weird of no interest, I block pass by IP net number. as shown by ifconfig MAC : 6 byte IP : 4 byte (IPV4) Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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 something we (as consumers of FreeBSD) need to be aware of?
This is really missing the point. The issue is not open source vs. proprietary although many people seem to try to steer everything into that meaningless conflict. The point is the WinTel Mafia's many years of collusion and screwing over the customer. Try to buy a commodity PC in any major store and it will come with Windows, and you have to pay for it. Now the WinTel Mafia got many companies onboard with their system to lock you out from the box you just bought. Bad enough it comes with Windows and you had to pay for it, and you don't even get an install disk. But the WinTel Mafia adds insult to injury and stops you from installing whatever software you want on it. What does this have to do with OSS v. proprietary source? Nothing! It is just about the WinTel Mafia's illegal, abuse trade practices. ___ 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 something we (as consumers of FreeBSD) need to be aware of?
On 06/10/2012 08:09 AM, Nomen Nescio wrote: This is really missing the point. The issue is not open source vs. proprietary although many people seem to try to steer everything into that meaningless conflict. The point is the WinTel Mafia's many years of collusion and screwing over the customer. Try to buy a commodity PC in any major store and it will come with Windows, and you have to pay for it. Now the WinTel Mafia got many companies onboard with their system to lock you out from the box you just bought. Bad enough it comes with Windows and you had to pay for it, and you don't even get an install disk. But the WinTel Mafia adds insult to injury and stops you from installing whatever software you want on it. What does this have to do with OSS v. proprietary source? Nothing! It is just about the WinTel Mafia's illegal, abuse trade practices. ___ 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 Need to have that congitiive distortion ckecked out because it makes it difficult to bring a logical conclusion, and creates an ill perspective on reality and keeps the person with a child like mentality; which makes the person to excerise worlds like wintel mafia,etc. ___ 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 something we (as consumers of FreeBSD) need to be aware of?
On 10/06/2012 16:09, Nomen Nescio wrote: The point is the WinTel Mafia's many years of collusion and screwing over the customer. Try to buy a commodity PC in any major store and it will come with Windows, and you have to pay for it. Does Intel control AMD too? Last I checked there are plenty of AMD machines in major stores and they come with Windows too. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ports: make config-recursive doesn't really
I'm trying to build a script to rebuild and reinstall everything I have installed from ports. I don't want to have to keep checking on it and filling out the appropriate check boxes for options. I naively assumed: for port in $ports do cd /usr/port/$port make config-recursive cd ../.. done would allow me to set up all the dependencies before continuing with the install. It appears, however, that it doesn't really recurse properly. I say appears only because this is my first time trying this and despite doing the above setting of options, I am confronted with additional options screens as the build progresses. Is there a way to get around this? Thanks, Gary ___ 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
altfn going to X
What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. ___ 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 something we (as consumers of FreeBSD) need to be aware of?
On Sun, Jun 10, 2012 at 9:31 AM, Bruce Cran br...@cran.org.uk wrote: Does Intel control AMD too? Last I checked there are plenty of AMD machines in major stores and they come with Windows too. So... attempting to bring reason into the argument? That won't do, I'm afraid. ;-) ___ 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: altfn going to X
On 06/10/12 10:47, Gary Aitken wrote: What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. I see it's ctlaltfn when in X. However, once out of X on another vty, switching to the vty where X was started does not get me back to X. How do I get back to the X display which is running? ___ 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 3.0 delay in 'detecting' attached drive
Hi, I have a new machine with 2 USB 3.0 ports and 2 USB 2.0 ports. When I plug a USB 3.0 drive / cable into the USB 3.0 port it takes about 70 seconds for the drive to show up, on the USB 2.0 port it's instantly. I haven't used USB 3.0 with FreeBSD so I'm not sure if this is expected or maybe I need to reconfigure something or look at a different kernel config. here's my info $ uname -a FreeBSD hunny.waitman.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Sat Jun 2 01:25:21 PDT 2012 root@:/usr/obj/usr/src/sys/KEYSHIA amd64 Notice the time.. 9:36:49 plugin, 9:37:59 drive shows up. USB 3.0 connect: Jun 10 09:36:49 hunny kernel: ugen1.2: Seagate at usbus1 Jun 10 09:36:49 hunny kernel: umass0: Seagate FreeAgent GoFlex, class 0/0, rev 3.00/1.00, addr 1 on usbus1 Jun 10 09:36:49 hunny kernel: umass0: SCSI over Bulk-Only; quirks = 0x4100 Jun 10 09:36:49 hunny kernel: umass0:4:0:-1: Attached to scbus4 Jun 10 09:37:59 hunny kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 Jun 10 09:37:59 hunny kernel: da0: Fixed Direct Access SCSI-0 device Jun 10 09:37:59 hunny kernel: da0: 400.000MB/s transfers Jun 10 09:37:59 hunny kernel: da0: 476940MB (976773167 512 byte sectors: 255H 63S/T 60801C) Jun 10 09:40:30 hunny ntfs-3g[1098]: Mounted /dev/da0s1 (Read-Write, label MUSIC, NTFS 3.1) Jun 10 09:40:30 hunny ntfs-3g[1098]: Mount options: allow_other,nonempty,atime,fsname=/dev/da0s1 Jun 10 09:41:43 hunny ntfs-3g[1098]: Unmounting /dev/da0s1 (MUSIC) Jun 10 09:41:47 hunny kernel: (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 0 refs Jun 10 09:41:47 hunny kernel: (da0:umass-sim0:0:0:0): removing device entry USB 2.0 - instantly Jun 10 09:42:07 hunny kernel: ugen3.2: Seagate at usbus3 Jun 10 09:42:07 hunny kernel: umass0: Seagate FreeAgent GoFlex, class 0/0, rev 2.10/1.00, addr 2 on usbus3 Jun 10 09:42:07 hunny kernel: umass0: SCSI over Bulk-Only; quirks = 0x4100 Jun 10 09:42:07 hunny kernel: umass0:4:0:-1: Attached to scbus4 Jun 10 09:42:07 hunny kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 Jun 10 09:42:07 hunny kernel: da0: Seagate FreeAgent GoFlex 211 Fixed Direct Access SCSI-0 device Jun 10 09:42:07 hunny kernel: da0: 40.000MB/s transfers Jun 10 09:42:07 hunny kernel: da0: 476940MB (976773167 512 byte sectors: 255H 63S/T 60801C) Jun 10 09:42:24 hunny kernel: (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 0 refs Jun 10 09:42:24 hunny kernel: (da0:umass-sim0:0:0:0): removing device entry ... $ dmesg | grep USB xhci0: XHCI (generic) USB 3.0 controller mem 0xf0348000-0xf0349fff irq 18 at device 16.0 on pci0 xhci1: XHCI (generic) USB 3.0 controller mem 0xf034a000-0xf034bfff irq 17 at device 16.1 on pci0 ohci0: OHCI (generic) USB controller mem 0xf034f000-0xf034 irq 18 at device 18.0 on pci0 ehci0: EHCI (generic) USB 2.0 controller mem 0xf034e000-0xf034e0ff irq 17 at device 18.2 on pci0 ohci1: OHCI (generic) USB controller mem 0xf034d000-0xf034dfff irq 18 at device 19.0 on pci0 ehci1: EHCI (generic) USB 2.0 controller mem 0xf034c000-0xf034c0ff irq 17 at device 19.2 on pci0 usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 umass1: Generic USB Storage, class 0/0, rev 2.00/98.33, addr 2 on usbus3 $ pciconfig -lv xhci0@pci0:0:16:0: class=0x0c0330 card=0x358b103c chip=0x78121022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'Hudson USB XHCI Controller' class = serial bus subclass = USB xhci1@pci0:0:16:1: class=0x0c0330 card=0x358b103c chip=0x78121022 rev=0x03 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'Hudson USB XHCI Controller' class = serial bus subclass = USB ehci0@pci0:0:18:2: class=0x0c0320 card=0x358b103c chip=0x78081022 rev=0x11 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'Hudson USB EHCI Controller' class = serial bus subclass = USB ohci1@pci0:0:19:0: class=0x0c0310 card=0x358b103c chip=0x78071022 rev=0x11 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'Hudson USB OHCI Controller' class = serial bus subclass = USB ehci1@pci0:0:19:2: class=0x0c0320 card=0x358b103c chip=0x78081022 rev=0x11 hdr=0x00 vendor = 'Advanced Micro Devices [AMD]' device = 'Hudson USB EHCI Controller' class = serial bus subclass = USB Thank you, Waitman Gobble San Jose California 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: altfn going to X
On Sun, 10 Jun 2012, Gary Aitken wrote: What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. KVM does not allow VT switching (at last report), but changes are promised. Otherwise, in an xterm (or other terminal in X) dump xmodmap in its reloadable form: $xmodmap -pke foo.txt now you can edit foo.txt as you please. This is mine with ctrl-alt-Fn mapped to VT_switching. keycode 67 = F1 F1 F1 F1 F1 F1 XF86Switch_VT_1 keycode 68 = F2 F2 F2 F2 F2 F2 XF86Switch_VT_2 You may want, for example: keycode 67 = F1 F1 F1 F1 XF86Switch_VT_1 F1 F1 keycode 68 = F2 F2 F2 F2 XF86Switch_VT_2 F2 F2 when you have finished editing, save this file to .xmodmap because you used -pke and were careful in your editing, this can be loaded by your window manager. In fvwm2 that loading looks like: + I exec xmodmap .xmodmap as in, for example: DestroyFunc InitFunction AddToFunc InitFunction + I Module FvwmBanner + I exec xphoon + I exec xmodmap .xmodmap + I exec xmodmap -e keysym Num_Lock = Num_Lock Pointer_EnableKeys + I exec xclipboard You can also load .xmodmap by running $xmodmap .xmodmap in an xterm. But you almost certainly want it loaded automatically (as in the fvwm2 example above), but how to do this in your particular window manager you will have to discover from the documentation of your window manger. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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: altfn going to X
On Sun, 10 Jun 2012, Gary Aitken wrote: On 06/10/12 10:47, Gary Aitken wrote: What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. I see it's ctlaltfn when in X. However, once out of X on another vty, switching to the vty where X was started does not get me back to X. How do I get back to the X display which is running? Switch to the one that X is running on. It's defined in /etc/ttys, normally ttyv8, so alt-f9 for X. ___ 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: altfn going to X
On Sun, 10 Jun 2012, Gary Aitken wrote: On 06/10/12 10:47, Gary Aitken wrote: What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. I see it's ctlaltfn when in X. However, once out of X on another vty, switching to the vty where X was started does not get me back to X. How do I get back to the X display which is running? Oh, you have to swith to the vtty where X is running, which certainly is NOT where you started X. Look in /etc/ttys for a line like this: ttyvb /usr/local/bin/xdm -nodaemonxterm off secure The above is not standard on installation, so probably the 'ttyv?' is different. The ? is the ttyv number (in hex) where your X should be running - BUT the hex number start at 0 (zero) while your F keys start with 1. For example, the above says X should run in ttyv b = 11 decimal, but that is associated with F12 (so that F1 can be mapped to ttyv0). It is possible to run some gui programs like zgv without a terminal, but in that case there is no way to switch terminals into or out of them. You can only launch them and quit them. Maybe (or not) X could run like that if you did not have a dedicated ttyv set up in /etc/ttys. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ 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 allow by MAC
In freebsd-questions Digest, Vol 418, Issue 18, Message: 1 On Sun, 10 Jun 2012 17:43:39 +0800 Bill Yuan byc...@gmail.com wrote: how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Bill, you did get some good clues in the earlier thread, but it's not clear if you took note of them. There's also been some confusion .. Firstly, read up on layer2 (ethernet, MAC-level) filtering options in ipfw(8). Thoroughly, several times, until you've got it. Seriously. After enabling sysctl net.link.ether.ipfw=1 (add it to /etc/sysctl.conf) ipfw will be invoked 4 times instead of the normal 2, on every packet. Read carefully ipfw(8) section 'PACKET FLOW', and see that only on the inbound pass invoked from ether_demux() and the outbound pass invoked from ether_output_frame() can you test for MAC addresses (or mac-types); the 'normal' layer3 passes examine packets that have no layer2 headers. You could just add 'layer2' to any rules filtering on MAC addresses, and omit MAC addresses from all layer 3 (IP) rules, but I'd recommend using a method like shown there to separate layer2 and layer3 flows early on: # packets from ether_demux ipfw add 10 skipto 1000 all from any to any layer2 in # packets from ip_input ipfw add 10 skipto 2000 all from any to any not layer2 in # packets from ip_output ipfw add 10 skipto 3000 all from any to any not layer2 out # packets from ether_output_frame ipfw add 10 skipto 4000 all from any to any layer2 out So at (eg) 1000 and 4000 place your incoming and outgoing MAC filtering rules (remembering the reversed order of MAC addresses vs IP addresses, and to allow broadcasts as well), pass good guys and/or block bad guys, then deal with your normal IPv4|v6 traffic in a separate section(s). Or you could just split the flows into two streams, one for layer2 for your MAC filtering, the other for layer3, ie the rest of your ruleset. HTH, Ian [please cc me on any reply] ___ 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: ports: make config-recursive doesn't really
You can have a look at port-mgmt/portmaster. Thanks Subhro -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On 10-Jun-2012, at 10:07 PM, Gary Aitken wrote: I'm trying to build a script to rebuild and reinstall everything I have installed from ports. I don't want to have to keep checking on it and filling out the appropriate check boxes for options. I naively assumed: for port in $ports do cd /usr/port/$port make config-recursive cd ../.. done would allow me to set up all the dependencies before continuing with the install. It appears, however, that it doesn't really recurse properly. I say appears only because this is my first time trying this and despite doing the above setting of options, I am confronted with additional options screens as the build progresses. Is there a way to get around this? Thanks, Gary ___ 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
nanobsd on usb-stick
Hi, I'm struggling with nanobsd (9.0). Tried with cd-rom (error 19). The USB-Config (UsbDevice Generic 8000) with NANO_DRIVE=da0 contains no real image and dd if=...disk.full of=/dev/da0 bs=64k woks but is not mountable after writing. Is there any current and complete documentation how to use an usb-stick with nanobsd? Thanks Reinhard ___ 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 something we (as consumers of FreeBSD) need to be aware of?
Too much hot air preaching to the choir is counter productive would die away after internal argument. Better be active Externaly. Defend our future by alerting governments there is an upcoming issue. (eg EU has mega fined MS before for monopoly abuse, EU etc could warn off MS if we alert governments there's something to monitor). Free source OSs, ie inc *BSD *Linux etc, need to co-ordinate with eg - A few short anodyne sentences summarising the MS Win8 UEFI problem, (better too little text than too much, to reduce work, avoid risk of discredit from getting anything wrong). - List of links to specification analysis discussion forums. - List of contacts to alert: politicians officials responsible for anti monopoly anti restraint of trade policing. - List of volunteers: people in each OS project to contact governments. - A brief simple sample letter to send to alert politicians officials (maybe via paper post or phone, not email to spam box ;-) As a start here's : http://berklix.org/uefi/ URLs welcome. Contact names welcome. Volunteers welcome. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
[solved] Re: altfn going to X
ah... Thanks both Warren and Lars What's the trick to allow altfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. I see it's ctlaltfn when in X. However, once out of X on another vty, switching to the vty where X was started does not get me back to X. How do I get back to the X display which is running? Oh, you have to swith to the vtty where X is running, which certainly is NOT where you started X. Look in /etc/ttys for a line like this: ttyvb/usr/local/bin/xdm -nodaemonxtermoff secure The above is not standard on installation, so probably the 'ttyv?' is different. The ? is the ttyv number (in hex) where your X should be running - BUT the hex number start at 0 (zero) while your F keys start with 1. For example, the above says X should run in ttyv b = 11 decimal, but that is associated with F12 (so that F1 can be mapped to ttyv0). ___ 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
Firefox Script Problems
Hello All, I just upgraded Firefox to the latest available in ports. Since this upgrade Firefox is near unresponsive. Messages keep popping up about unresponsive script errors on the page being viewed. Would anyone have any ideas on how to best approach this problem to find the fix? Thanks in advance, 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
Re: altfn going to X
2012-06-10 19:02, Gary Aitken skrev: On 06/10/12 10:47, Gary Aitken wrote: What's the trick to allowaltfn to still be used to switch vtys when running X? At first I thought it was the wm grabbing it, but I've disabled that and now it goes to whatever app has the focus. Seems like something in the kernel has to grab it before it gets passed on to X. I see it'sctlaltfn when in X. However, once out of X on another vty, switching to the vty where X was started does not get me back to X. How do I get back to the X display which is running? Alt+F9 ___ 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 something we (as consumers of FreeBSD) need to be aware of?
On Sun, 10 Jun 2012 22:06:26 +0200 Julian H. Stacey articulated: Too much hot air preaching to the choir is counter productive would die away after internal argument. Better be active Externaly. Defend our future by alerting governments there is an upcoming issue. (eg EU has mega fined MS before for monopoly abuse, EU etc could warn off MS if we alert governments there's something to monitor). Free source OSs, ie inc *BSD *Linux etc, need to co-ordinate with eg - A few short anodyne sentences summarising the MS Win8 UEFI problem, (better too little text than too much, to reduce work, avoid risk of discredit from getting anything wrong). - List of links to specification analysis discussion forums. - List of contacts to alert: politicians officials responsible for anti monopoly anti restraint of trade policing. - List of volunteers: people in each OS project to contact governments. - A brief simple sample letter to send to alert politicians officials (maybe via paper post or phone, not email to spam box ;-) As a start here's : http://berklix.org/uefi/ URLs welcome. Contact names welcome. Volunteers welcome. It is posts like this that basically turn my stomach. A product, any product, should succeed or fail based on its own merits and not because some government agency aided or thwarted it. Most, it not nearly all PC manufacturers exist solely because of Microsoft. The PC market balloons every time Microsoft releases a new version of Windows. Seriously now, how many PC were sold because FreeBSD released version 9 of its OS? If you want to beat someone, you make a better product. You don't go running to your mamma asking for protection. That stinks of socialism/fascism. The UEFI specification has existed for years. Supposedly, Linux has been capable of using it for 8+ years. I have no idea if FreeBSD is even capable of handling it. It wouldn't surprise me it if couldn't though. What this really tells me is that there has been way to much procrastination by the FOSS. Microsoft simply took advantage of an existing standard (remember standards something the FOSS is always crying about) and now FOSS is begging for mercy. This is more than just slightly funny, it is pathetic. If 1% of the effort of spreading this BS over UEFI had gone into working on a solution for UEFI two years ago, we wouldn't be having this discussion at all. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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
xfce 4.10 update problems
Hi, after portmaster update: - there are missing icons in main menu and that of Terminal - startx fails when moused enabled (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) xinit: connection to X server lost Any known solutions ? jb ___ 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 3.0 delay in 'detecting' attached drive
On Sun, Jun 10, 2012 at 1:56 PM, Julian H. Stacey j...@berklix.com wrote: Waitman Gobble wrote: Hi, I have a new machine with 2 USB 3.0 ports and 2 USB 2.0 ports. When I plug a USB 3.0 drive / cable into the USB 3.0 port it takes about 70 seconds for the drive to show up, on the USB 2.0 port it's instantly. I haven't used USB 3.0 with FreeBSD so I'm not sure if this is expected or maybe I need to reconfigure something or look at a different kernel config. Might be a marginal power issue. USB 3 devices are allowed to consume 1.0 Amps. USB2 ports only need provide 0.5. I have a tower wont recognise my USB disc on its USB2 ports. On my new PCI express card in same tower, it comes up quickly. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ Thanks. Not sure if there's anything I can do about that. It's a new HP dv6 laptop which according to box was mfg in May 2012... I would assume hardware would be designed and put together properly. :) Waitman ___ 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: Making a bootable backup (hard)disk... how?
In message alpine.bsf.2.00.1206100543280.75...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: 1) In your example under the heading Copying Filesystems, the second shell command line shown is: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) Is that correct? Shouldn't it actually be this instead? dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt/usr restore -ruf -) ... The mount command above that is mount /dev/da0s1f /mnt Ah! OK. I failed to notice that. Yes, that clarifies things entirely. ... I mean if I do the pipeline from dump to restore as you have shown in your examples in your Copying Filesystems section, then what must I do in order prevent dump from dumping files that haven't changed? (And likewise, how do I prevent restore from trying to restore files under /mnt/usr that have not changed? Or is that answer to that question that I simply have to do the first thing, i.e. force dump not to dump any of the unchanged files?) See the dump man page about dump levels. OK, I'm looking at it, and to be honest, the subject of dump levels is not covered at all well there. (Neither does it seem to be covered well in other online documents, found via Google, that purport to describe dump restore.) The reference to modified Tower of Hanoi algorithm and the subsequent suggested dumplevel sequence are especially opaque and perplexing. Well, nevermind about that. I get the general idea, i.e. that dumping at level N causes dumping of everything that has changed since the last dump at level N-1. What I don't understand (and what I wish someone would enlighten me about) is just this: It would seem that in order to implement these dump levels, dump must be keeping a record somewhere, for each file in the filesystem, of the level at which that file was last dumped. But where is this infor- mation stored, exactly?? I won't be able to sleep until I know. (Aside: One of the reasons I hate Windoze is that everything is hidden. One of the reasons I love UNIX is that everything is out in the open, which is to say documented. But even after reading the dump(1) man page, it ain't in the least bit obvious to me where dump is recording the last dump level for each node in the filesystem. This info must be stored SOMEWHERE. But where?) I have not tried a dump level higher than zero with a dump|restore copy, but expect it to work. rsync will do it, and would be my choice for that; start with -aH for options, and --exclude might be used for some directories that don't need to be copied. Humm... well, I am reminded of all of the reasons why I have been convinced (now) to use dump/restore, specifically the security of knowing that _all_ info will be copied across, in particular (a) extra mode bits/flags and (b) ACLs and (c) file attributes. (This is not to even mention correct handling of other obscure filesystem things like, e.g. sparse files.) So the obvious question is: If I am going to use rsync to keep my backup disk up-to-date, does rsync handle all of these additional small but important filesystem details properly too? If not, then I had best just stick with dump/restore, and use the dumplevels. Also see the sysutils/rsnapshot port for an interesting snapshot use. Combined with a bootable FreeBSD like mfsBSD (http://mfsbsd.vx.sk/), that might be a workable alternative to creating a bootable backup. Thanks. I've installed that port and I am looking at the man page, but I believe that I do still want to reach my goal of just having a (recovery) hard disk that I can just boot directly from. 3) Assuming that I have a second disk to which I plan (now) to use dumprestore to make periodic copies of all of my ``normal'' (non-backup) filesystems onto. Assuming also that I've already installed the FreeBSD boot loader into the boot block on this second disk, and that I've already run fdisk bsdlabel on it so as to set up all of the partitioning to be essentially identical to my ``main'' system disk. Assuming that all of this is the case, by using dumprestore as you have shown in your document under the heading Copying Filesystems, will I have succeded at doing what I was first asking about in this thread, i.e. will I have successfully created a _bootable_ mirror of my main system disk... With some tuning, yes. /etc/fstab mountpoints often won't match when such a drive is connected to a different port or new system. Right. There's that. So I will need to diddle the /etc/fstab in the backup. Use gpart(8) GPT labels... Ummm... I don't know pooh about this, but I am reading about it now, and the idea make me _very_ nervous. Apparently, `MBR' is traditional, and I am very much of a traditionalist. (Mostly I find that I only get into trouble when I try to buck pre-existing conventions.) or tunefs(8) filesystem labels. I guess you must mean the -L volname option. I'm not at all sure
Re: Making a bootable backup (hard)disk... how?
Warren? Just a couple more quick questions. You recommend: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) I'm real curious about you suggestions for the -C and -b values. I have what amounts to a personal workstation. Yea, OK, it is running mail, web, and FTP servers also, but fundementailly, it is not that busy most of the time. And it's got 4GB of main installed. On average, I suspect that I ain't even using half of that. Given all that, why shouldn't I specify (e.g.): -C512 -b1024 ? Wouldn't that all make the dump go faster? Remember, I'm just gonna do like in your examples and pipe the output of dump to restore, so whereas if I was going to tape (or even to a .dump disk file), -b1024 would be rather wasteful, in my case all I am wasting is a bit of kernel time (for a bit more stuff being passed through the pipe). Regards, rfg ___ 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: Making a bootable backup (hard)disk... how?
On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: In message alpine.bsf.2.00.1206100543280.75...@wonkity.com, Warren Block wbl...@wonkity.com wrote: On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: 1) In your example under the heading Copying Filesystems, the second shell command line shown is: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) Is that correct? Shouldn't it actually be this instead? dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt/usr restore -ruf -) ... The mount command above that is mount /dev/da0s1f /mnt Ah! OK. I failed to notice that. Yes, that clarifies things entirely. ... I mean if I do the pipeline from dump to restore as you have shown in your examples in your Copying Filesystems section, then what must I do in order prevent dump from dumping files that haven't changed? (And likewise, how do I prevent restore from trying to restore files under /mnt/usr that have not changed? Or is that answer to that question that I simply have to do the first thing, i.e. force dump not to dump any of the unchanged files?) See the dump man page about dump levels. OK, I'm looking at it, and to be honest, the subject of dump levels is not covered at all well there. (Neither does it seem to be covered well in other online documents, found via Google, that purport to describe dump restore.) The reference to modified Tower of Hanoi algorithm and the subsequent suggested dumplevel sequence are especially opaque and perplexing. It's diffs. One complete copy to start, then a partial dump, just the files that have changed since the first. And then another partial, just the files that have changed since the second. Start over with a full dump every so often, because that reduces the amount of backups that have to be restored until you get to the final version of the file. As far as I can recall, I've always used level zero. What I don't understand (and what I wish someone would enlighten me about) is just this: It would seem that in order to implement these dump levels, dump must be keeping a record somewhere, for each file in the filesystem, of the level at which that file was last dumped. But where is this infor- mation stored, exactly?? I won't be able to sleep until I know. (Aside: One of the reasons I hate Windoze is that everything is hidden. One of the reasons I love UNIX is that everything is out in the open, which is to say documented. But even after reading the dump(1) man page, it ain't in the least bit obvious to me where dump is recording the last dump level for each node in the filesystem. This info must be stored SOMEWHERE. But where?) Sorry, I've never checked. File dates, maybe. The source for dump would be the place to look. rsync will do it, and would be my choice for that; start with -aH for options, and --exclude might be used for some directories that don't need to be copied. Humm... well, I am reminded of all of the reasons why I have been convinced (now) to use dump/restore, specifically the security of knowing that _all_ info will be copied across, in particular (a) extra mode bits/flags and (b) ACLs and (c) file attributes. (This is not to even mention correct handling of other obscure filesystem things like, e.g. sparse files.) So the obvious question is: If I am going to use rsync to keep my backup disk up-to-date, does rsync handle all of these additional small but important filesystem details properly too? If not, then I had best just stick with dump/restore, and use the dumplevels. It does many of those things, enough that many people use it for backup. Right. There's that. So I will need to diddle the /etc/fstab in the backup. Use gpart(8) GPT labels... Ummm... I don't know pooh about this, but I am reading about it now, and the idea make me _very_ nervous. Apparently, `MBR' is traditional, and I am very much of a traditionalist. (Mostly I find that I only get into trouble when I try to buck pre-existing conventions.) or tunefs(8) filesystem labels. I guess you must mean the -L volname option. I'm not at all sure that I see how that would help anything. When a mountpoint is /dev/gpt/myrootfs, it doesn't matter whether the drive shows up as ada0 or ad4 or da2, the mount still works. Likewise with the Ethernet board, so see rc.conf(5) about ifconfig_DEFAULT. Something else (the Handbook?) mentioned something about the ethernet card(s) in the context also. I just don't get it. Why would I even need to think about that in this context? My current system disk is alive well and already has all of the proper ifconfig stuff in /etc/rc.conf to make the local ethernet card work properly on my network. I am engaged in making a _verbatim_ backup of my main system disk to another hard disk that, in an emergency, would be plugged in to the exact same system (with the exact same ethernet card) and if I have made the verbatim backup properly, then it also will have the proper
Re: Making a bootable backup (hard)disk... how?
On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: What I don't understand (and what I wish someone would enlighten me about) is just this: It would seem that in order to implement these dump levels, dump must be keeping a record somewhere, for each file in the filesystem, of the level at which that file was last dumped. But where is this infor- mation stored, exactly?? I won't be able to sleep until I know. Only the dates of the levels of backup are stored, in /etc/dumpdates. Then the fact that a file has been dumped is inferred by comparing the file's last mod date with the dates in /etc/dumpdates. See the -T and -u options of the dump man page where this is implied but perhaps not actually stated. It does occur to me that /etc is not a felicitous place to keep this information, but given the desirability of dumping filesystems in read only state, placing the dump dates in the filesystem itself isn't feasible. daniel feenberg ___ 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: Making a bootable backup (hard)disk... how?
Ronald F. Guilmette r...@tristatelogic.com wrote: Warren Block wbl...@wonkity.com wrote: On Sun, 10 Jun 2012, Ronald F. Guilmette wrote: ... I mean if I do the pipeline from dump to restore as you have shown in your examples in your Copying Filesystems section, then what must I do in order prevent dump from dumping files that haven't changed? (And likewise, how do I prevent restore from trying to restore files under /mnt/usr that have not changed? Or is that answer to that question that I simply have to do the first thing, i.e. force dump not to dump any of the unchanged files?) See the dump man page about dump levels. OK, I'm looking at it, and to be honest, the subject of dump levels is not covered at all well there. (Neither does it seem to be covered well in other online documents, found via Google, that purport to describe dump restore.) The reference to modified Tower of Hanoi algorithm and the subsequent suggested dumplevel sequence are especially opaque and perplexing. Well, nevermind about that. I get the general idea, i.e. that dumping at level N causes dumping of everything that has changed since the last dump at level N-1. That's about all -really- need to know. The sequencing stuff is just a recommendation on a way to do multiple levels of incremental backups. What I don't understand (and what I wish someone would enlighten me about) is just this: It would seem that in order to implement these dump levels, dump must be keeping a record somewhere, for each file in the filesystem, of the level at which that file was last dumped. But where is this infor- mation stored, exactly?? I won't be able to sleep until I know. First, your assumption is incorrect. *grin* All that dump stores is the timestamp of the completion of the last dump at each level. As for where that information is stored. RTFM applies. the 'files' section. By default '/etc/dumpdates', but modifiable by the -D option. (Aside: One of the reasons I hate Windoze is that everything is hidden. One of the reasons I love UNIX is that everything is out in the open, which is to say documented. But even after reading the dump(1) man page, it ain't in the least bit obvious to me where dump is recording the last dump level for each node in the filesystem. This info must be stored SOMEWHERE. But where?) Wrong assumptions lead to looking for the wrong things. grin Why store the date for every node, when storing the date of the dump sufficies? (assuming you're consisently using the same dump command for dumps recorded to the same 'dumpfile', that is, and using different dumpfiles for different 'selective' dump commands) _Anything_ modified after the last dump at the next lower level needs to be saved as part of -this- dump, unless it is 'excluded' from this dump. A level 0 dump backs up 'everything', except things which are expliclitly excluded. A level 1 dump backs up 'everything that has changed since the last level 0 dump' (whether or not it was inclued in the level 0 dump), except for things which are eplicitly excluded. A subsequent level 1 dump catches everything since the last level _0_ dump. A level 2 dump backs up 'everything that has changed since the last level 1 dump' (whether or not it was inclued in the level 1 dump, or level 0 dump), except for things which are eplicitly excluded. A level 3 dump backs up 'everything that has changed since the last level 2 dump' (whether or not it was inclued in the level 2, 1, or 0 dump), except for things which are eplicitly excluded. A subsequent level 2 dump catches everything since the last level _1_ dump. Another level 1 dump -here- catches everything singe the prior level 0 dump. and kills the record of any level 2 (or higher) dump. A level 3 dump here -- with dump anything since the level 1 dump (since there was no 'current' level 2 dump). So the obvious question is: If I am going to use rsync to keep my backup disk up-to-date, does rsync handle all of these additional small but important filesystem details properly too? If not, then I had best just stick with dump/restore, and use the dumplevels. It doesn't matter what anybody tells you. what matters is what the machine does. Thus the authoritative response is try it and find out. grin I was first asking about in this thread, i.e. will I have successfully created a _bootable_ mirror of my main system disk... With some tuning, yes. /etc/fstab mountpoints often won't match when such a drive is connected to a different port or new system. Right. There's that. So I will need to diddle the /etc/fstab in the backup. 'dump'/'restore' doesn't do -everything- necessary. You have to: set up slices/partitions as needed. 'label' as appropriate INSTALL BOOT BLOCKS 'newfs' the appropriate filesystems then dump/restore the filesystems on the disk. Likewise with the Ethernet board, so see rc.conf(5) about
Re: Is this something we (as consumers of FreeBSD) need to be aware of?
Jerry wrote It is posts like this that basically turn my stomach Never argue with a drunk. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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 3.0 delay in 'detecting' attached drive
Waitman Gobble wrote: On Sun, Jun 10, 2012 at 1:56 PM, Julian H. Stacey j...@berklix.com wrote: Waitman Gobble wrote: Hi, I have a new machine with 2 USB 3.0 ports and 2 USB 2.0 ports. When I plug a USB 3.0 drive / cable into the USB 3.0 port it takes about 70 seconds for the drive to show up, on the USB 2.0 port it's instantly. I haven't used USB 3.0 with FreeBSD so I'm not sure if this is expected or maybe I need to reconfigure something or look at a different kernel config. Might be a marginal power issue. USB 3 devices are allowed to consume 1.0 Amps. USB2 ports only need provide 0.5. I have a tower wont recognise my USB disc on its USB2 ports. On my new PCI express card in same tower, it comes up quickly. Cheers, Julian Thanks. Not sure if there's anything I can do about that. It's a new HP dv6 laptop which according to box was mfg in May 2012... I would assume hardware would be designed and put together properly. :) Sounds new enough :-) My USB3 disc on my newish laptop with USB 2 socket 8.2 9.0 come up fast enough, not noticed problems, not specificaly timed it though. Try external power if you have a socket on disk box ? Try disk on another known good FreeBSD USB3 card on a tower (my card cost 30 Euro BTW) Or try a power doubler cable (connected via a female to female adapter, which Ive never seen on sale, I made my own by cutting up a dead mainboard), to the USB 3 male to male cable. (for any who dont know, cant omit that cable as USB3 socket on lapop size drives is a different shape, flater, wider. I wonder if it might be taking time dropping back to USB2 speed. if eg you don't have xhci in kernel ? I have all of config -x/boot/kernel/kernel | grep hci device uhci device ohci device xhci device ehci I just havent taken some out yet. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ ___ 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: xfce 4.10 update problems
On Sun, 10 Jun 2012, jb wrote: Hi, after portmaster update: - there are missing icons in main menu and that of Terminal - startx fails when moused enabled (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) xinit: connection to X server lost Any known solutions ? Disable hal in xorg.conf, ServerLayout section: Option AutoAddDevices Off ___ 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
Chromium 19 core dumps on launch...
Friday I installed Chromium again because it would be nice to have a browser to test in other than Firefox and Opera. It was installed using portinstall -R chromium, which *appeared* to function properly. However, trying to run chrome results in: pid 50993 (chrome), uid 1001: exited on signal 11 (core dumped) From what I found online, it looked like I may have been encountering an issue with devel/google-perftools, but on reinstall was able to confirm that this is building with gcc not clang. I have also removed my ~/.config/chromium directory with no change in behavior. Not sure if it's relevant, but the last version of Chromium that was *functional* for me was 12. Versions 13-16 didn't support loading web pages (the browser would launch, but if I entered a URL in the address bar, I could leave the browser running overnight and it still wouldn't have started loading a page). Then when 17 and 18 wouldn't even compile (marked ignore), I just removed package. Looking for suggestions on getting Chromium to at least launch... ___ 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: Making a bootable backup (hard)disk... how?
Ronald F. Guilmette writes: Warren? Just a couple more quick questions. You recommend: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) I'm real curious about you suggestions for the -C and -b values. I have what amounts to a personal workstation. Yea, OK, it is running mail, web, and FTP servers also, but fundementailly, it is not that busy most of the time. And it's got 4GB of main installed. On average, I suspect that I ain't even using half of that. Given all that, why shouldn't I specify (e.g.): -C512 -b1024 ? Wouldn't that all make the dump go faster? There are many possible obstacles to faster dump speed; enumerating them is left as an exercise for the reader. As it happens, I have a set-up very similar to what you describe ... except with 8g of memory. A few years ago I did some testing with various cache sizes (as part of diagnosing other problems) and ended up with C=32. (I should probably run the tests again, given some hardware changes since.) That machine's level 0 runs tonight; I will try to remember to (retain and) post the results. 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: Making a bootable backup (hard)disk... how?
On Sun, 10 Jun 2012, Robert Huff wrote: Ronald F. Guilmette writes: Warren? Just a couple more quick questions. You recommend: dump -C16 -b64 -0uanL -h0 -f - /usr | (cd /mnt restore -ruf -) I'm real curious about you suggestions for the -C and -b values. I have what amounts to a personal workstation. Yea, OK, it is running mail, web, and FTP servers also, but fundementailly, it is not that busy most of the time. And it's got 4GB of main installed. On average, I suspect that I ain't even using half of that. Given all that, why shouldn't I specify (e.g.): -C512 -b1024 ? Wouldn't that all make the dump go faster? There are many possible obstacles to faster dump speed; enumerating them is left as an exercise for the reader. As it happens, I have a set-up very similar to what you describe ... except with 8g of memory. A few years ago I did some testing with various cache sizes (as part of diagnosing other problems) and ended up with C=32. (I should probably run the tests again, given some hardware changes since.) That machine's level 0 runs tonight; I will try to remember to (retain and) post the results. -C16 is a little small because it's hard to tell how much memory someone running the example will have. I usually use -C32 on machines with plenty of memory. Remember that dump forks multiple times, so it's not 32M, but N*32M. -b64 is the largest safe buffer size to use. People have experienced problems with larger amounts. ___ 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 3.0 delay in 'detecting' attached drive
On Sun, Jun 10, 2012 at 4:59 PM, Julian H. Stacey j...@berklix.com wrote: Waitman Gobble wrote: On Sun, Jun 10, 2012 at 1:56 PM, Julian H. Stacey j...@berklix.com wrote: Waitman Gobble wrote: Hi, I have a new machine with 2 USB 3.0 ports and 2 USB 2.0 ports. When I plug a USB 3.0 drive / cable into the USB 3.0 port it takes about 70 seconds for the drive to show up, on the USB 2.0 port it's instantly. I haven't used USB 3.0 with FreeBSD so I'm not sure if this is expected or maybe I need to reconfigure something or look at a different kernel config. Might be a marginal power issue. USB 3 devices are allowed to consume 1.0 Amps. USB2 ports only need provide 0.5. I have a tower wont recognise my USB disc on its USB2 ports. On my new PCI express card in same tower, it comes up quickly. Cheers, Julian Thanks. Not sure if there's anything I can do about that. It's a new HP dv6 laptop which according to box was mfg in May 2012... I would assume hardware would be designed and put together properly. :) Sounds new enough :-) My USB3 disc on my newish laptop with USB 2 socket 8.2 9.0 come up fast enough, not noticed problems, not specificaly timed it though. Try external power if you have a socket on disk box ? Try disk on another known good FreeBSD USB3 card on a tower (my card cost 30 Euro BTW) Or try a power doubler cable (connected via a female to female adapter, which Ive never seen on sale, I made my own by cutting up a dead mainboard), to the USB 3 male to male cable. (for any who dont know, cant omit that cable as USB3 socket on lapop size drives is a different shape, flater, wider. I wonder if it might be taking time dropping back to USB2 speed. if eg you don't have xhci in kernel ? I have all of config -x/boot/kernel/kernel | grep hci device uhci device ohci device xhci device ehci I just havent taken some out yet. Cheers, Julian -- Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Reply below not above, cumulative like a play script, indent with . Format: Plain text. Not HTML, multipart/alternative, base64, quoted-printable. Mail from @yahoo dumped @berklix. http://berklix.org/yahoo/ I believe it uses ohci for usb 2.0, xhci for 3.0, ehci for 1.0 (which I suppose might be connected to some device internally even if you do not have 1.0 port?) I originally built this system on a different machine, with different hardware, but it really shouldn't make a different AFAIK. ... But I did just csup and rebuild everything on the laptop... i needed to build some devices into the kernel anyhow, and NOW the usb 3.0 connect is instantly, there is now no 70 second delay. I'd have to check, maybe there was a change in xhci between June 2 and today which could have caused the issue. Or it was just a 'weird harold' event, for some reason it just felt like sitting there a minute. Thanks for your help, Waitman ___ 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: xfce 4.10 update problems
On Sun, Jun 10, 2012 at 5:12 PM, Warren Block wbl...@wonkity.com wrote: On Sun, 10 Jun 2012, jb wrote: Hi, after portmaster update: - there are missing icons in main menu and that of Terminal - startx fails when moused enabled (EE) xf86OpenSerial: Cannot open device /dev/psm0 Device busy. (EE) PS/2 Mouse: cannot open input device (EE) PreInit returned NULL for PS/2 Mouse (EE) config/hal: NewInputDeviceRequest failed (8) xinit: connection to X server lost Any known solutions ? Disable hal in xorg.conf, ServerLayout section: Option AutoAddDevices Off __**_ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/**mailman/listinfo/freebsd-**questionshttp://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-** unsubscr...@freebsd.org freebsd-questions-unsubscr...@freebsd.org for missing icons in xfce4.10, here is explanation in a pr with 3 solutions.. http://www.freebsd.org/cgi/query-pr.cgi?pr=168688 Waitman Gobble San Jose California 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: altfn going to X
On Sun, 10 Jun 2012 12:17:10 -0500 (CDT), Lars Eighner wrote: But you almost certainly want it loaded automatically (as in the fvwm2 example above), but how to do this in your particular window manager you will have to discover from the documentation of your window manger. It's easy loading xmodmap settings prior to the window manager and therefore independent of it, using the X startup file which is ~/.xinitrc or ~/.xsession (or a chain loader of them). [ -f ~/.xmodmaprc ] xmodmap ~/.xmodmaprc # other initialisation ... start fvwn2 However, the default key combination Ctrl+Alt+Fx should work without alteration in any window manager; at least it does in the few I've tried. -- 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 allow by MAC
Hi Lan, Thanks for your reply, I am reading some old emails which you sent in 2008 while other place asked a same question as mine, On Mon, Jun 11, 2012 at 1:53 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 418, Issue 18, Message: 1 On Sun, 10 Jun 2012 17:43:39 +0800 Bill Yuan byc...@gmail.com wrote: how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Bill, you did get some good clues in the earlier thread, but it's not clear if you took note of them. There's also been some confusion .. Firstly, read up on layer2 (ethernet, MAC-level) filtering options in ipfw(8). Thoroughly, several times, until you've got it. Seriously. After enabling sysctl net.link.ether.ipfw=1 (add it to /etc/sysctl.conf) ipfw will be invoked 4 times instead of the normal 2, on every packet. Read carefully ipfw(8) section 'PACKET FLOW', and see that only on the inbound pass invoked from ether_demux() and the outbound pass invoked from ether_output_frame() can you test for MAC addresses (or mac-types); the 'normal' layer3 passes examine packets that have no layer2 headers. You could just add 'layer2' to any rules filtering on MAC addresses, and omit MAC addresses from all layer 3 (IP) rules, but I'd recommend using a method like shown there to separate layer2 and layer3 flows early on: # packets from ether_demux ipfw add 10 skipto 1000 all from any to any layer2 in # packets from ip_input ipfw add 10 skipto 2000 all from any to any not layer2 in # packets from ip_output ipfw add 10 skipto 3000 all from any to any not layer2 out # packets from ether_output_frame ipfw add 10 skipto 4000 all from any to any layer2 out So at (eg) 1000 and 4000 place your incoming and outgoing MAC filtering rules (remembering the reversed order of MAC addresses vs IP addresses, and to allow broadcasts as well), pass good guys and/or block bad guys, then deal with your normal IPv4|v6 traffic in a separate section(s). Or you could just split the flows into two streams, one for layer2 for your MAC filtering, the other for layer3, ie the rest of your ruleset. HTH, Ian [please cc me on any reply] ___ 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 allow by MAC
forget to po the link here http://lists.freebsd.org/pipermail/freebsd-questions/2008-June/177636.html On Mon, Jun 11, 2012 at 11:16 AM, Bill Yuan byc...@gmail.com wrote: Hi Lan, Thanks for your reply, I am reading some old emails which you sent in 2008 while other place asked a same question as mine, On Mon, Jun 11, 2012 at 1:53 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 418, Issue 18, Message: 1 On Sun, 10 Jun 2012 17:43:39 +0800 Bill Yuan byc...@gmail.com wrote: how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Bill, you did get some good clues in the earlier thread, but it's not clear if you took note of them. There's also been some confusion .. Firstly, read up on layer2 (ethernet, MAC-level) filtering options in ipfw(8). Thoroughly, several times, until you've got it. Seriously. After enabling sysctl net.link.ether.ipfw=1 (add it to /etc/sysctl.conf) ipfw will be invoked 4 times instead of the normal 2, on every packet. Read carefully ipfw(8) section 'PACKET FLOW', and see that only on the inbound pass invoked from ether_demux() and the outbound pass invoked from ether_output_frame() can you test for MAC addresses (or mac-types); the 'normal' layer3 passes examine packets that have no layer2 headers. You could just add 'layer2' to any rules filtering on MAC addresses, and omit MAC addresses from all layer 3 (IP) rules, but I'd recommend using a method like shown there to separate layer2 and layer3 flows early on: # packets from ether_demux ipfw add 10 skipto 1000 all from any to any layer2 in # packets from ip_input ipfw add 10 skipto 2000 all from any to any not layer2 in # packets from ip_output ipfw add 10 skipto 3000 all from any to any not layer2 out # packets from ether_output_frame ipfw add 10 skipto 4000 all from any to any layer2 out So at (eg) 1000 and 4000 place your incoming and outgoing MAC filtering rules (remembering the reversed order of MAC addresses vs IP addresses, and to allow broadcasts as well), pass good guys and/or block bad guys, then deal with your normal IPv4|v6 traffic in a separate section(s). Or you could just split the flows into two streams, one for layer2 for your MAC filtering, the other for layer3, ie the rest of your ruleset. HTH, Ian [please cc me on any reply] ___ 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 allow by MAC
I would ask what problem do you want to solve here; is it preventing a userjust from getting out unless they are using their assigned address, or something else? On Jun 10, 2012 8:16 PM, Bill Yuan byc...@gmail.com wrote: Hi Lan, Thanks for your reply, I am reading some old emails which you sent in 2008 while other place asked a same question as mine, On Mon, Jun 11, 2012 at 1:53 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 418, Issue 18, Message: 1 On Sun, 10 Jun 2012 17:43:39 +0800 Bill Yuan byc...@gmail.com wrote: how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Bill, you did get some good clues in the earlier thread, but it's not clear if you took note of them. There's also been some confusion .. Firstly, read up on layer2 (ethernet, MAC-level) filtering options in ipfw(8). Thoroughly, several times, until you've got it. Seriously. After enabling sysctl net.link.ether.ipfw=1 (add it to /etc/sysctl.conf) ipfw will be invoked 4 times instead of the normal 2, on every packet. Read carefully ipfw(8) section 'PACKET FLOW', and see that only on the inbound pass invoked from ether_demux() and the outbound pass invoked from ether_output_frame() can you test for MAC addresses (or mac-types); the 'normal' layer3 passes examine packets that have no layer2 headers. You could just add 'layer2' to any rules filtering on MAC addresses, and omit MAC addresses from all layer 3 (IP) rules, but I'd recommend using a method like shown there to separate layer2 and layer3 flows early on: # packets from ether_demux ipfw add 10 skipto 1000 all from any to any layer2 in # packets from ip_input ipfw add 10 skipto 2000 all from any to any not layer2 in # packets from ip_output ipfw add 10 skipto 3000 all from any to any not layer2 out # packets from ether_output_frame ipfw add 10 skipto 4000 all from any to any layer2 out So at (eg) 1000 and 4000 place your incoming and outgoing MAC filtering rules (remembering the reversed order of MAC addresses vs IP addresses, and to allow broadcasts as well), pass good guys and/or block bad guys, then deal with your normal IPv4|v6 traffic in a separate section(s). Or you could just split the flows into two streams, one for layer2 for your MAC filtering, the other for layer3, ie the rest of your ruleset. HTH, Ian [please cc me on any reply] ___ 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: how to allow by MAC
Hi Brian, Thanks for your care, Execute me for my English is not that good , I am from Singapore :) I want to create a white list MAC address, Only the machine which it's MAC in the white list will be allowed, all others will be blocked. Thanks On Mon, Jun 11, 2012 at 11:21 AM, Brian W. br...@brianwhalen.net wrote: I would ask what problem do you want to solve here; is it preventing a userjust from getting out unless they are using their assigned address, or something else? On Jun 10, 2012 8:16 PM, Bill Yuan byc...@gmail.com wrote: Hi Lan, Thanks for your reply, I am reading some old emails which you sent in 2008 while other place asked a same question as mine, On Mon, Jun 11, 2012 at 1:53 AM, Ian Smith smi...@nimnet.asn.au wrote: In freebsd-questions Digest, Vol 418, Issue 18, Message: 1 On Sun, 10 Jun 2012 17:43:39 +0800 Bill Yuan byc...@gmail.com wrote: how to allow by MAC in ipfw currently i set the rule like below 1 allow ip from any to any MAC any to MAC Address 1 1 allow ip from any to any MAC MAC Address 1 any 2 deny all from any to any i want to only allow the mac address to go through the freebsd firewall, but I found it is not working on my freebsd but it works on pfsense! so maybe that means the environment is not the same ? and how to setup the ipfw properly to support this ? Bill, you did get some good clues in the earlier thread, but it's not clear if you took note of them. There's also been some confusion .. Firstly, read up on layer2 (ethernet, MAC-level) filtering options in ipfw(8). Thoroughly, several times, until you've got it. Seriously. After enabling sysctl net.link.ether.ipfw=1 (add it to /etc/sysctl.conf) ipfw will be invoked 4 times instead of the normal 2, on every packet. Read carefully ipfw(8) section 'PACKET FLOW', and see that only on the inbound pass invoked from ether_demux() and the outbound pass invoked from ether_output_frame() can you test for MAC addresses (or mac-types); the 'normal' layer3 passes examine packets that have no layer2 headers. You could just add 'layer2' to any rules filtering on MAC addresses, and omit MAC addresses from all layer 3 (IP) rules, but I'd recommend using a method like shown there to separate layer2 and layer3 flows early on: # packets from ether_demux ipfw add 10 skipto 1000 all from any to any layer2 in # packets from ip_input ipfw add 10 skipto 2000 all from any to any not layer2 in # packets from ip_output ipfw add 10 skipto 3000 all from any to any not layer2 out # packets from ether_output_frame ipfw add 10 skipto 4000 all from any to any layer2 out So at (eg) 1000 and 4000 place your incoming and outgoing MAC filtering rules (remembering the reversed order of MAC addresses vs IP addresses, and to allow broadcasts as well), pass good guys and/or block bad guys, then deal with your normal IPv4|v6 traffic in a separate section(s). Or you could just split the flows into two streams, one for layer2 for your MAC filtering, the other for layer3, ie the rest of your ruleset. HTH, Ian [please cc me on any reply] ___ 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: Firefox Script Problems
Hello Sean, Can you run FF from a terminal and report back what you see? Thanks -- Subhro Sankha Kar System Administrator Working and Playing with FreeBSD since 2002 On 11-Jun-2012, at 1:44 AM, sean wrote: Hello All, I just upgraded Firefox to the latest available in ports. Since this upgrade Firefox is near unresponsive. Messages keep popping up about unresponsive script errors on the page being viewed. Would anyone have any ideas on how to best approach this problem to find the fix? Thanks in advance, 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 ___ 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
