Re: prune ports tree?
On 8 June 2012 23:21, Polytropon wrote: > On Sat, 09 Jun 2012 00:06:39 -0600, Gary Aitken wrote: >> Is it possible to specify that parts of the ports tree should never be used? > This approach does _not_ work well when using portsnap. From > the portsnap.conf manpage: "Note that operating with an incomplete > ports tree is not supported and may cause unexpected results." Note that the issue of incomplete ports trees has nothing to do with portsnap - it is unsupported no matter how you obtain ports. -- Eitan Adler ___ freebsd-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: prune ports tree?
On Sat, 09 Jun 2012 00:06:39 -0600, Gary Aitken wrote: > Is it possible to specify that parts of the ports tree should never be used? How do you want to understand by "parts" and "not used"? The easiest way to "not use" some part of the ports tree is to remove that part. You can do that by manually deleting the port(s) and even omitting them when updating your ports tree. If you use csup, you can make /etc/sup/ports.sup like this: Don't use ports-all, but only list the categories you want to have updated. This works category-wise. You'll find examples in /usr/share/examples/cvsup/ports-supfile which you can use as a template for your own configuration file. An example of /etc/sup/ports.sup could look like this: *default host=cvsup.freebsd.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix *default compress ports-base ports-accessibility #ports-arabic ports-archivers [ ... list shortened ... ] ports-x11-servers ports-x11-themes ports-x11-toolkits ports-x11-wm Only the listed ports categories will be updated. Then you can add this to /etc/make.conf: SUP=/usr/bin/csup <--- SUP_UPDATE= /usr/bin/csup <--- SUPFLAGS= -L 2<--- SUPHOST=cvsup.freebsd.org SUPFILE=/etc/sup/stable.sup PORTSSUPFILE= /etc/sup/ports.sup <--- DOCSUPFILE= /etc/sup/doc.sup DOC_LANG= en_US.ISO8859-1 de_DE.ISO8859-1 The important lines are marked with a <---. Now you can do this: # cd /usr/ports # make update and you'll get the latest ports tree _excluding_ what you have already removed. You can also use /usr/ports/.cvsignore to specify the directories csup should ignore; defaults are "distfiles" and "packages". You can list "offending" ports here. This approach does _not_ work well when using portsnap. From the portsnap.conf manpage: "Note that operating with an incomplete ports tree is not supported and may cause unexpected results." -- 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: prune ports tree?
On 8 June 2012 23:06, Gary Aitken wrote: > Is it possible to specify that parts of the ports tree should never be used? yes, but don't do it. the ports tree needs to be complete to be guaranteed to function. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
prune ports tree?
Is it possible to specify that parts of the ports tree should never be used? ___ freebsd-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: Performance and mouse problems
On Fri, 8 Jun 2012, Albert Shih wrote: After some time, and read new messages ont this mailing list, I find a solution. Deactivate hald deactivate dbus Option "AutoAddDevices" "Off" put moused_enable="On" in /etc/rc.conf and reboot and everything work fine again. I don't known why by using /usr/local/etc/rc.d/hald stop /usr/local/etc/rc.d/dbus stop /etc/rc.d/moused start it's not working It should not be a dbus problem, and some things can benefit from dbus. Try it and see if the problem comes back. FWIW, I thought I suggested this a while back. It is what I run: hal not installed, but moused enabled. When hal is not installed, turning AutoAddDevices off should also not be needed. ___ freebsd-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 filter network by MAC and IP at the same time
rule like below #allow the traffic which source mac is belong to the machine ipfw add 1 allow all from any to any MAC any #allow the .. destination mac is that machine ipfw add 1 allow all from any to any MAC any ipfw add 1 deny all from any to any it is not working , all the traffic will be block by the deny !!! how come ? On Sat, Jun 9, 2012 at 4:30 AM, Lowell Gilbert < freebsd-questions-lo...@be-well.ilk.org> wrote: > Bill Yuan writes: > > > i am using freebsd 9.0 as a firewall and i want to filter the traffic by > > the mac and the ip at the same time, > > > > for example, i only allow my laptop can go throught the > > firewalll when it's using IP > > > > for how to config the firewall rules? > > > > > > I tried to configure the firewall by the rule below , but it doesnt work > > > > ipfw add 1 allow all from to any MAC any > > ipfw add 1 allow all from any to MAC any 1> > > Well, for one thing if I understand your intent, you have the MAC > addresses in the wrong order. Unless your firewall is acting as a > bridge, you also need to keep in mind that the MAC addresses are changed > when passing through, so those rules will only work on one side (i.e., > you'll need "in via" type rules). > > > but it doesnt work. also found the explanation on google, someone already > > asked this question before. > > I don't understand. Was there a suggested approach or not? > > > but I did not find the solution for this requirement. can someone tell > me > > how ? thanks in advance. > > I can't guarantee this will work, and I don't have any way to test it, > but my above comments would suggest something more like: > > > ipfw add 1 allow all from to any MAC any in via $iif > > > ipfw add 1 allow all from any to MAC > any out via $oif > > Good luck. > ___ freebsd-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: Mouse stopped working in X
On Sat, 09 Jun 2012 06:06:49 +0200, Bernt Hansson wrote: > > > 2012-05-22 10:44, Polytropon skrev: > > On Tue, 22 May 2012 10:17:16 +0200, Bernt Hansson wrote: > >> There is a second way of doing this stunt. > >> > >> Start X > >> When X is up and running press CTRL+ALT+F3 or any F* frpm F3 up to F8 > >> then you get to the console > >> Su to root in the console and type in > >> > >> /usr/local/etc/rc.d/dbus restart&& /usr/local/etc/rc.d/hald restart > >> > >> Then press ALT+F9 to get back to X > > > > So if that is the _solution_ > > It is not near any solution. > > I do not think this issue have anything to do with hal or dbus. I didn't claim it was a solution, I just wanted to make the therapy "more elegant"; see the difference between therapy (treating symptoms) and the actual cure of a disease (removing the cause). As I'm only running old-fashioned stuff here, I can't be more specific regarding the newest inventions of why X stopped acting as expected. In the past, simply removing HAL and DBUS altogether and using a xorg.conf file to make the required settings has worked at least for me. My idea of automating the manual step of restarting HAL and DBUS (which _seems_ to have treated the symptoms of a non-working mouse) was to put that into the X initialisation file: "sudo /usr/local/etc/rc.d/dbus restart && sudo /usr/local/etc/rc.d/hald restart". Of couse that doesn't even remotely touch a possible problem caused elsewhere. And does it look totally stupid? Sure it does. It looks so wrong, but sometimes the wrongest thing "just works" (TM). :-) > My machine at the office running the same hal and X as the one at home > does not have this kind of problems. That might be a good indicator that there actually is something different in those machines, and this difference causes the problem. Maybe it's something simple, and really not related to HAL. As I said, I'm not sure, as I'm not using it. -- 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: Configuration problem with IPv6 router ("cannot forward src")
On 08/06/2012 06:59, Matthew Seaman wrote: Probably. The good news is that once you've got it running the IPv6 support in FreeBSD is rock solid and works like a charm. It turns out that PF was being too helpful and trying to NAT for both IPv4 and IPv6 - adding 'inet' to the "nat on $ext_if..." line fixed it. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Making a bootable backup (hard)disk... how?
On Fri, Jun 8, 2012 at 4:58 PM, Warren Block wrote: > On Fri, 8 Jun 2012, Robert Huff wrote: > > >> Ronald F. Guilmette writes: >> >> I got a lot of disks here, so that part is not a problem. I just >>> need to make sure that I'm gonna do this the Right Way[tm]. >>> (I've already been making my own ham-fisted disk-to-disk backups >>> in the past, but I'm sure that the way I have been doing that is >>> sub-optimal, so I'm here seeking knowledge of how to do this the >>> Right Way.) >>> >>> The bottom line is this... I know how to use cpio, and would like >>> to use it to create a complete and _bootable_ backup of my main >>> system disk. (My main system disk has only one BIOS partition, >>> and that is sub-divided into the usual set of FreeBSD partitions, >>> you know, /, /dev, /tmp, /usr, /var, /usr/compat/linux/proc, and >>> /var/named/dev.) >>> >> >>As far as I know, the only way guaranteed to preserve metadata >> is dump/restore. See previous (not necessarily recent) discussion >> (on this list, and possibly in the Handbook) for more information. >> > > The rsync port has a flags option. I haven't tried it for a full backup. > Even if it can copy all filesystem attributes like dump, there are still > non-filesystem things needed for booting that neither can copy, like > partition tables and boot blocks. There might be something for a bootable > backup in ports, or it could be done with a script using gpart. Set up the > disk with GPT labels to make it relocatable, use dump to copy everything > the first time, fix up a few things like fstab and ifconfig_DEFAULT in the > same script. > > Afterwards, rsync may be enough for fast updates. > I am applying the following technique in Linux ( because I am not using FreeBSD ) : On the same computer : (1) I am disconnecting power cable of the existing HDD . (2) I am connecting a new disk ( by attaching Channel Zero SATA Cable to it ) . (3) I am installing a new operating system on HDD (4) I am installing mc ( Midnight Commander ) . (5) After obtaining a working new HDD , I am connecting the power cable of the previous disk . (6) I am booting the computer . The new operating system is "seeing" previous HDD . (7) I am mounting previous HDD . (8) By using mc , I am copying required files/directories into new HDD . Mostly I am using KDE4 . Dolphin in KDE4 has a memory leak which is causing disaster for very large list of files because for each file , it is consuming irrecoverable memory loss from 600 bytes to 1000 bytes during copying . (9) I am keeping previous HDD as bootable by disconnecting its power cable because it is not necessary to keep it powered . You can do the following : (1) Install your operating system on back-up HDD . (2) By using a script , copy required files /directories onto back-up HDD . With this technique , you can maintain a revolving back-up HDD units : Create back-up HDD 1 . Create back-up HDD 2 . . . . Create back-up HDD n . When n-th HDD is created , and a new back-up is required switch to HDD 1 . Using rsync you may update only required files / directories . Full copy is not required to update subsequent HDD units because it is very likely that many files are the same . In that form , EACH back-up HDD is bootable when it is required . You may consider HAST for a single HDD . You may use external USB HDD by selecting a robust model . Disconnecting power cable of existing HDD during a new operating system install on another HDD is preventing an accidental loss of data because naming the recognized HDD units is NOT standard and very unreliable . Thank you very much . Mehmet Erol Sanliturk ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
XBMC home theater PC
Hi, I've recently got a Dell Optiplex 760 that I'm using as a home theatre PC set up with FreeBSD (9.0-STABLE) and XBMC. It's mostly working very well but there are just a couple of niggles I'd like to work out to see it working perfectly. 1. Suspend and resume is working well if the usb modules are kld(un/)loaded before and after suspend. I've just been gifted a radeon hd RV610 graphics card which seems quite nice. I'd like to get the card to work with suspend, but the card doesn't like resume If I do a kldunload/kldload on the radeonhd module or don't bother I see the following errors in /var/log/Xorg.0.log: > (EE) RADEONHD(0): RHDCSStop: Command Submission backend is not active! > rhd_crtc.c:586: DxModeRestore: Assertion '!RHD_CHECKDEBUGFLAG(rhdPtr, > VGA_SETUP)' failed. > > FatalError re-entered, aborting > Server aborting or > Segmentation fault: 11 at address 0x4 > > Fatal server error: > Caught signal 11 (Segmentation fault: 11). Server aborting and in both cases, a load of: > (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY Also there are loads of the following in /var/log/messages: > Jun 8 21:13:02 xbmc kernel: info: [drm] wait idle failed status : 0xA0003030 > 0x0003 Googling for these error messages returns threads dated around 2009. I would have thought that if this was an issue then it would have been solved, although they weren't related to suspend/resume. Has anyone else seen this error or know of a fix for it? Currency I just restart the X server on resume. 2. If the machine is powerd down I am able to WOL to boot the computer, but if I put the computer into suspend I am not able to. The nic light is still on but doesn't wake the computer. I'm wondering if this is the OS not the card in the same way as during a shutdown. Does anyone know of a solution to this or a work around? 3. Finally, I think this may be a bit of a shot in the dark, but is it possible to have a USB event wake the computer? I imagine that the hardware determines if this is possible (like WOL) and if not all the USB code has been unloaded from the kernel anyway. I'd still be interested to hear thoughts though. Regards, David Collins ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
XBMC home theater PC
Hi, I've recently got a Dell Optiplex 760 that I'm using as a home theatre PC set up with FreeBSD and XBMC. It's mostly working very well but there are just a couple of niggles I'd like to work out to see it working perfectly. 1. Suspend and resume is working well if the usb modules are kld(un/)loaded before and after suspend. I've just been gifted a radeon hd RV610 graphics card which seems quite nice. I'd like to get the card to work with suspend, but the card doesn't like resume If I do a kldunload/kldload on the radeonhd module or don't bother I see the following errors in /var/log/Xorg.0.log: > (EE) RADEONHD(0): RHDCSStop: Command Submission backend is not active! > rhd_crtc.c:586: DxModeRestore: Assertion '!RHD_CHECKDEBUGFLAG(rhdPtr, > VGA_SETUP)' failed. > > FatalError re-entered, aborting > Server aborting or > Segmentation fault: 11 at address 0x4 > > Fatal server error: > Caught signal 11 (Segmentation fault: 11). Server aborting and in both cases, a load of: > (WW) RADEONHD(0): DRMCPIdle: DRM CP IDLE returned BUSY Also there are loads of the following in /var/log/messages: > Jun 8 21:13:02 xbmc kernel: info: [drm] wait idle failed status : 0xA0003030 > 0x0003 Googling for these error messages returns threads dated around 2009. I would have thought that if this was an issue then it would have been solved, although they weren't related to suspend/resume. Has anyone else seen this error or know of a fix for it? Currency I just restart the X server on resume. 2. If the machine is powerd down I am able to WOL to boot the computer, but if I put the computer into suspend I am not able to. The nic light is still on but doesn't wake the computer. I'm wondering if this is the OS not the card in the same way as during a shutdown. Does anyone know of a solution to this or a work around? 3. Finally, I think this may be a bit of a shot in the dark, but is it possible to have a USB event wake the computer? I imagine that the hardware determines if this is possible (like WOL) and if not all the USB code has been unloaded from the kernel anyway. I'd still be interested to hear thoughts though. Regards, David Collins ___ freebsd-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: Which FreeBSD for Intel i7-2600S and DQ67SWB3?
On 06/07/2012 06:40 PM, Daniel Staal wrote: On 06/08/2012 01:07 AM, Thomas Mueller wrote: Thanks for the replies. :-) David ___ freebsd-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 Fri, 8 Jun 2012, Robert Huff wrote: Ronald F. Guilmette writes: I got a lot of disks here, so that part is not a problem. I just need to make sure that I'm gonna do this the Right Way[tm]. (I've already been making my own ham-fisted disk-to-disk backups in the past, but I'm sure that the way I have been doing that is sub-optimal, so I'm here seeking knowledge of how to do this the Right Way.) The bottom line is this... I know how to use cpio, and would like to use it to create a complete and _bootable_ backup of my main system disk. (My main system disk has only one BIOS partition, and that is sub-divided into the usual set of FreeBSD partitions, you know, /, /dev, /tmp, /usr, /var, /usr/compat/linux/proc, and /var/named/dev.) As far as I know, the only way guaranteed to preserve metadata is dump/restore. See previous (not necessarily recent) discussion (on this list, and possibly in the Handbook) for more information. The rsync port has a flags option. I haven't tried it for a full backup. Even if it can copy all filesystem attributes like dump, there are still non-filesystem things needed for booting that neither can copy, like partition tables and boot blocks. There might be something for a bootable backup in ports, or it could be done with a script using gpart. Set up the disk with GPT labels to make it relocatable, use dump to copy everything the first time, fix up a few things like fstab and ifconfig_DEFAULT in the same script. Afterwards, rsync may be enough for fast updates. ___ freebsd-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: UEFI Secure Boot Specs - And some sanity
>> Isn't there a lot of needless handwaving going on when the spec is >> pretty clear that installing your own complete PKI tree will all >> boil down to what is effectively a jumper on the motherboard? > Hoping a jumper Might be under an easily unscrewable panel seems unlikely. I did say "effectively". If people would actually read that chapter in the spec (minimally 27.5) they would find that they can: - Load a new PK without asking if in default SetupMode - If not in SetupMode, chainload a new PK provided it is signed by the current PK. - Clear the PK in a 'secure platform specific method'. There's nothing that says PK SetupMode has to be a jumper. Entering the equivalent of good old pre-boot BIOS setup mode would work so long as the OS can't get to it without the request being signed by the current PK. The point of Secure Boot is firmware checked protection against software access... not physical access protection. The spec speaks liberally of 'platform owner' being able to do whatever they want. More handwaving about EULA's and branding aside, that means US. I seriously think that people are blowing this topic way out of context, and seeing it everywhere is getting really old. People should instead be working on the facts and writing the various motherboard manufacturers to ask them what their expected PK update model will be, and to educate them if not. And to work at committing it to their OS. And yes, that includes Compal and Quanta and those sorts of OEM laptop/embedded makers. I'll send $100 to the FreeBSD foundation if those retail board makers I listed don't give the option to install/replace the PK. Nuff said. ps: I don't really care what MS does with their own branded products in the embedded/small space. Plenty of millionaires out there now who are in tune with opensource who could startup, buy the same ARM/ATOM/etc chips, the same support chips, load Android and sell it to the masses. Lot's of overseas ODM's out there for them to pick from too. Phones, tablets, notebooks, laptops... it's all there. FreeBSD on your phone in 10 years. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD: SOLVED: FreeBSD9 - I can't get my mouse to work (was : FreeBSD9 - I can't get my mouse to work)
On Fri, 08 Jun 2012 20:58:49 +0200, Bernt Hansson wrote: > 2012-06-08 17:51, Walter Hurry skrev: >> On Fri, 08 Jun 2012 15:39:22 +, Walter Hurry wrote: >> Never mind: Stupid moi. The answer was staring me in the face in man >> rc.conf. moused_port. >> >> > You also have moused_flags="Put your flags here" > > That does not help, not me anyway. Indeed you do. But I didn't need moused_flags (nor moused_type) - just moused_port. I was then able to restore /etc/rc.d/moused to its pristine state. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Making a bootable backup (hard)disk... how?
Ronald F. Guilmette writes: > I got a lot of disks here, so that part is not a problem. I just > need to make sure that I'm gonna do this the Right Way[tm]. > (I've already been making my own ham-fisted disk-to-disk backups > in the past, but I'm sure that the way I have been doing that is > sub-optimal, so I'm here seeking knowledge of how to do this the > Right Way.) > > The bottom line is this... I know how to use cpio, and would like > to use it to create a complete and _bootable_ backup of my main > system disk. (My main system disk has only one BIOS partition, > and that is sub-divided into the usual set of FreeBSD partitions, > you know, /, /dev, /tmp, /usr, /var, /usr/compat/linux/proc, and > /var/named/dev.) As far as I know, the only way guaranteed to preserve metadata is dump/restore. See previous (not necessarily recent) discussion (on this list, and possibly in the Handbook) for more information. 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"
Making a bootable backup (hard)disk... how?
I've been lucky. Over about the past 20 years I've never had a hard
disk go bad on me. (Knock on wood.) Of course I _do_ only buy the
better quality ones (with the 5 year warranties), and I'm sure that
has helped. Still, one never knows, and it is best to be prepared.
Primarily however, I am mostly afraid of the fumble-finger scenario...
you know... cd /; rm -fr *
I read a little bit about UFS filesystem snashots, and they could probably
help me deal effectively with fumble-finger incidents, but I still think
that I would prefer to have a whole separate physical disk as my backup.
(I mean what the hell? They are so cheap these days anyway.)
I got a lot of disks here, so that part is not a problem. I just
need to make sure that I'm gonna do this the Right Way[tm]. (I've already
been making my own ham-fisted disk-to-disk backups in the past, but I'm
sure that the way I have been doing that is sub-optimal, so I'm here
seeking knowledge of how to do this the Right Way.)
The bottom line is this... I know how to use cpio, and would like to use
it to create a complete and _bootable_ backup of my main system disk.
(My main system disk has only one BIOS partition, and that is sub-divided
into the usual set of FreeBSD partitions, you know, /, /dev, /tmp, /usr,
/var, /usr/compat/linux/proc, and /var/named/dev.)
I'm not a complete dummy, so I can can easily figure out how to use cpio
to make copies of all of the things in these filesystems to another
physical drive, however, there are a couple of issues that I really don't
know how to deal with properly, to wit:
1) How can one induce cpio to copy over the extra magical FreeBSD-specific
file flags, such as the "immutable" flag, and so forth? (Naturally, I _do_
want to preserve all of these in my backup.)
2) Of necessity, the drive/partition designators of my backup disk and my
``real'' original system disk will be different. The original is a SATA
drive, designator(s) /dev/ad4s1{a,e,f,d}, but due to the limitations of what
I have on hand, my backup drive will be an older PATA drive, designator(s)
/dev/ad2s1{a,e,f,d}. Obviously, cpio doesn't give a darn about such things,
and so making my backup will not be a problem at all. The problem will,
I suspect, arise when and if I actually have to try to use my backup disk to
recover from a system failure. Then, the identity of the drive that will
actually hold the root partition will be new and different from whatever it
is set to currently on my ``real''/original drive... which will probably
cause the disk not to boot... and also, of course, a lot of the entries in
/etc/fstab will be wrong for the backup drive and will have to be diddled
at some time... either at the time I make my backup, or later, when I go
to actually _use_ the backup disk. I need to know he Right Way to deal
with these (drive designator) problems also.
I guess that I can figure out for myself how to diddle the /etc/fstab file
on the backup drive in an appropriate way (and I can probably even cook up
a trivial script to do this diddling for me routinely, each time I make a
new disk-to-disk backup). So I guess the only think that is still making
me nervous is my dim recollection... leftover from FreBSD releases of long
long ago, e.g. the 6.x series... that there was also something hard-coded
somewhere that told the kernel the identity of the root partition. If that
hard coded thing still exists somewhere (i.e. in 8.3) then I'll need to
make it a point, when making my bootbale backup disk, to find and diddle that
thing too, in addition to diddling the /etc/fstab entries.
So my question is simple: Do I need to diddle anything other than /etc/fstab
in order to allow for the fact that all of the drive designators will be
different for my backup disk, as compared to my original disk? And if so,
where is/are the additional things that will need to be manually diddled?
Any help/advice/insight regarding the above topics will be much appreciated.
Regards,
rfg
P.S. Maybe I just overlooked it, but I really didn't see any option listed
on the man page for cpio(1)... aka bsdcpio(1)... that would permit copying/
preservation of the various file flags discussed in the man pages for
chflags(1) and chflags(2). Is it just me, or can cpio really not copy
these? If so, it seems like one helluva big oversight. (Even if there
is as issue where these additional file flags cannot be preserved, i.e.
in cpio archive files, you know, because of backward archive format com-
patability issues, at the very least there could be / should be a way to
get cpio to copy these things over when the -p (pass) option is being used...
no?
Hummm... come to think of it, I'm also not seeing any way to induce cpio
to copy over things like per-file ACLs and/or per-file file attributes
either.
Is it just me, or does _everyone_ who uses cpio for backups loose all of
this good stuff when making backups?
Color me preplexed.
Re: Performance and mouse problems
Le 29/04/2012 ? 00:58:01+0200, Jerome Herman a écrit > >>> > >>> I've got two very strange problem > >>> > >>> I'm running 9-stable on a Dell Laptop E4200. > >>> > >>> Since this morning when I put a USB mouse (I've try three mouses to be > >>> sure) it's not working. The kernel and HAL see the mouse but Xorg don't > >>> seem do anything. > >>> > >>> The second point is the load of the system is alway more than 1 (~1.5-2) > >>> event I do nothing. I kill all services, daemon, software and the load > >>> never drop. > >>> > >>> I've stop : > >>> > >>> hald > >>> dbus > >>> powerd > >>> etc... > >>> > >>> and ps don't show any process eating some ressource. But the load is high > >>> (and the laptop is very hot). > >>> > >>> I make a csup of world and build new userland, and news kernel. And > >>> nothing > >>> change > >>> > >> http://www.wonkity.com/~wblock/docs/html/aei.html > > Well I don't see why this can be from a misconfiguration, the usb mouse > > work well before I update hald and world. > > > > But I read you link and I don't have those option in my configuration of > > xorg. > > > > Any other idea ? > > > > But thanks. > > > > For the problem about performance I submit this problem on stable mailing > > list. > > > > Regards > > > > JAS > > > > I was afraid this would happen. And I fear it is just the begining. > I assume you did not create any custom hald rule. Did you ? > > The first thing to do is to add > > Option "AutoAddDevices" "Off" > > In your ServerLayout section of xorg.conf. > Then restart X and try to plug a mouse again. It may result in your mouse not > working in X, but at least it should stop your computer from using all it's > CPU trying to map the mouse. > > > If indeed the CPU load does not reach skyhigh levels when you plug a USB > mouse, we will be able to conclude that there is a DBus/hald problem. > After some time, and read new messages ont this mailing list, I find a solution. Deactivate hald deactivate dbus Option "AutoAddDevices" "Off" put moused_enable="On" in /etc/rc.conf and reboot and everything work fine again. I don't known why by using /usr/local/etc/rc.d/hald stop /usr/local/etc/rc.d/dbus stop /etc/rc.d/moused start it's not working Thank all those help. Regards. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex Téléphone : 01 45 07 76 26/06 86 69 95 71 xmpp: j...@jabber.obspm.fr Heure local/Local time: ven 8 jui 2012 23:06:01 CEST ___ freebsd-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 filter network by MAC and IP at the same time
Bill Yuan writes: > i am using freebsd 9.0 as a firewall and i want to filter the traffic by > the mac and the ip at the same time, > > for example, i only allow my laptop can go throught the > firewalll when it's using IP > > for how to config the firewall rules? > > > I tried to configure the firewall by the rule below , but it doesnt work > > ipfw add 1 allow all from to any MAC any > ipfw add 1 allow all from any to MAC any Well, for one thing if I understand your intent, you have the MAC addresses in the wrong order. Unless your firewall is acting as a bridge, you also need to keep in mind that the MAC addresses are changed when passing through, so those rules will only work on one side (i.e., you'll need "in via" type rules). > but it doesnt work. also found the explanation on google, someone already > asked this question before. I don't understand. Was there a suggested approach or not? > but I did not find the solution for this requirement. can someone tell me > how ? thanks in advance. I can't guarantee this will work, and I don't have any way to test it, but my above comments would suggest something more like: > ipfw add 1 allow all from to any MAC any $iif > ipfw add 1 allow all from any to MAC any > out via $oif Good luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD: SOLVED: FreeBSD9 - I can't get my mouse to work (was : FreeBSD9 - I can't get my mouse to work)
2012-06-08 17:51, Walter Hurry skrev: On Fri, 08 Jun 2012 15:39:22 +, Walter Hurry wrote: Never mind: Stupid moi. The answer was staring me in the face in man rc.conf. moused_port. You also have moused_flags="Put your flags here" That does not help, not me anyway. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
cvsup of RELENG_8_1
I keep getting this error when trying to update source on 8.1: TreeList failed: Error in "/var/db/sup/src-all/checkouts.cvs:RELENG_8_1": 13890: Could not parse status record. Delete it and try again. I realize that 8.1 isn't formally supported anymore, but should cvsup still work? I can't upgrade right now because of the conflict between GPT and gmirror what was introduced in 8.2. -- Jim C. Nasby, Database Architect j...@nasby.net 512.569.9461 (cell) http://jim.nasby.net ___ freebsd-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 do I determine support for $xx?
Hi Devin There were some great tips in your last post. Would be great if they couldfo in FreeBSD handbook somewhere. 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 do I determine support for $xx?
Matthew/Devin, Thanks for the feedback.
After I sent this email, I determined that the Intel i350 is indeed
supported as a machine I built with FreeBSD was utilizing this NIC.
I've tried the BCM5719 with stable/8 (5/21/2012) and it kernel panics
when the interface is configured. I was told by a source contributor
that the BCM5720 does not work (confirmed as recently as within the
last week), but I've not tested it. I'm just passing this on as
information...I don't expect any feedback with regards to this.
On Fri, Jun 8, 2012 at 1:06 PM, Devin Teske wrote:
>
> On Jun 8, 2012, at 9:45 AM, Devin Teske wrote:
>
>> Hi Rick (!),
>>
>> On Jun 8, 2012, at 8:07 AM, Rick Miller wrote:
>>
>
> [snip]
>
>>>
>>> I browsed the source and found many references to the BCM5719 and
>>> BCM5720. However, I am unfamiliar enough with driver programming in C
>>> to identify if a controller is fully supported.
>>>
>>
>
> [snip]
>
>> If you were running, say, 8.0-R, even if you have the bge(4) driver loaded,
>> you would see this in /var/run/dmesg.boot:
>>
>> pciN: (vendor=0x1106, dev=0x165f) at X.Y
>>
>
> Correction, (specific to BCM5720) you'd see:
>
> pciN: (vendor=0x14e4, dev=0x165f) at X.Y
>
> Which, btw, you can confirm to yourself by executing the following within
> 8.3-R (with attached bge(4)):
>
> $ pciconf -lv | awk '/^bge/{print $1,$4}'
> bge0@pciN:A:B:C: chip=0x165f14e4
>
> Otherwise, you can see an unknown (non-working bge(4)) Broadcom BCM5720
> hardware by executing (on 8.0-R for example):
>
> $ grep unk /var/run/dmesg.boot | grep 0x14e4
> pciN: (vendor=0x14e4, dev=0x165f) at X.Y
>
> NOTE: On a system where all hardware is probed/attached, "grep unk
> /var/run/dmesg.boot" should not produce any results. In this case, pciconf is
> your tool for probing vendor/device IDs.
>
>
>> NOTE: Insert random numbers for "N", and "X.Y"
>>
>> How you know that 8.3-R's bge(4) driver supports the BCM5720 is because this
>> source file:
>>
>> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bgereg.h?annotate=1.83.2.35.2.1
>>
>> NOTE: I specifically pointed you at CVS instead of SVN so that you can see
>> the version tagged for 8.3-R
>>
>> Specifically, this line:
>>
>> 2309: #define BCOM_DEVICEID_BCM5720 0x165F
>
> [snip]
>
> --
> Devin
>
> _
> The information contained in this message is proprietary and/or confidential.
> If you are not the intended recipient, please: (i) delete the message and all
> copies; (ii) do not disclose, distribute or use the message in any manner;
> and (iii) notify the sender immediately. In addition, please be aware that
> any message addressed to our domain is subject to archiving and review by
> persons other than the intended recipient. Thank you.
--
Take care
Rick Miller
___
freebsd-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 do I determine support for $xx?
On Jun 8, 2012, at 9:45 AM, Devin Teske wrote:
> Hi Rick (!),
>
> On Jun 8, 2012, at 8:07 AM, Rick Miller wrote:
>
[snip]
>>
>> I browsed the source and found many references to the BCM5719 and
>> BCM5720. However, I am unfamiliar enough with driver programming in C
>> to identify if a controller is fully supported.
>>
>
[snip]
> If you were running, say, 8.0-R, even if you have the bge(4) driver loaded,
> you would see this in /var/run/dmesg.boot:
>
> pciN: (vendor=0x1106, dev=0x165f) at X.Y
>
Correction, (specific to BCM5720) you'd see:
pciN: (vendor=0x14e4, dev=0x165f) at X.Y
Which, btw, you can confirm to yourself by executing the following within 8.3-R
(with attached bge(4)):
$ pciconf -lv | awk '/^bge/{print $1,$4}'
bge0@pciN:A:B:C: chip=0x165f14e4
Otherwise, you can see an unknown (non-working bge(4)) Broadcom BCM5720
hardware by executing (on 8.0-R for example):
$ grep unk /var/run/dmesg.boot | grep 0x14e4
pciN: (vendor=0x14e4, dev=0x165f) at X.Y
NOTE: On a system where all hardware is probed/attached, "grep unk
/var/run/dmesg.boot" should not produce any results. In this case, pciconf is
your tool for probing vendor/device IDs.
> NOTE: Insert random numbers for "N", and "X.Y"
>
> How you know that 8.3-R's bge(4) driver supports the BCM5720 is because this
> source file:
>
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bgereg.h?annotate=1.83.2.35.2.1
>
> NOTE: I specifically pointed you at CVS instead of SVN so that you can see
> the version tagged for 8.3-R
>
> Specifically, this line:
>
> 2309: #defineBCOM_DEVICEID_BCM5720 0x165F
[snip]
--
Devin
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. Thank you.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: How do I determine support for $xx?
Hi Rick (!), On Jun 8, 2012, at 8:07 AM, Rick Miller wrote: > Hi All, > > If this question is better suited for a different list please let me > know. Simply stated, my question is 'What is the best source for > identifying supported hardware?'. The source! Actually, pciconf and "grep unknown /var/run/dmesg.boot" and using pcidatabase.com are all good starts (for me at least). When I'm integrating new/old hardware there isn't "one path" that I take. It really depends on what the situation is. (and so to give you the best advice, I read-on) > Having said that, allow me to pose > an example... > > I've attempted to identify if various ethernet controllers are > supported by FreeBSD and the drivers. I used the hardware notes and > manpages for the respective ethernet drivers. The information between > the two sometimes seems inconsistent and/or inaccurate. For example, > the BCM5719 and BCM5720 are unsupported in FreeBSD at this time. That *was* true, but it's integrated quite well now with 8.3-R. We have a few NEC workstations eval's fresh for testing that are using that hardware. > The > hardware notes at freebsd.org do not specify these controllers are > supported. Inspection of the bge(4) manpage implies that the > controllers are supported as seen in the description section where it > states: > > "The bge driver provides support for various NICs based on the > Broadcom BCM570x, 571x, 572x, 575x, 576x, 578x, 5776x and 5778x > Gigabit Ethernet controller chips and the 590x and 5779x Fast Ethernet > controller chips." > > I browsed the source and found many references to the BCM5719 and > BCM5720. However, I am unfamiliar enough with driver programming in C > to identify if a controller is fully supported. > You really need to know the 4-digit hexadecimal Vendor ID and Model ID of the chipset to KNOW that a source module will probe/attach to a given hardware by-spec. Probing/attaching is mostly done by registry arrays defining these hex values as what to attach to during probe. Of course, booting the OS is the best way. If your HW device is not picked up by any module (built-in or otherwise), then you'll get a line like the following in /var/run/dmesg.boot: pci0: (vendor=0x1106, dev=0x3057) at 4.4 There's those hex values. If you take the device value and enter it into pcidatabase.com you'll get: http://pcidatabase.com/search.php?device_search_str=0x3057&device_search=Search Which comes up as: "ACPI Power Management Controller" by "VIA Technologies, Inc" That's the unknown device. But, let's focus on BCM5720… If you were running, say, 8.0-R, even if you have the bge(4) driver loaded, you would see this in /var/run/dmesg.boot: pciN: (vendor=0x1106, dev=0x165f) at X.Y NOTE: Insert random numbers for "N", and "X.Y" How you know that 8.3-R's bge(4) driver supports the BCM5720 is because this source file: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/bge/if_bgereg.h?annotate=1.83.2.35.2.1 NOTE: I specifically pointed you at CVS instead of SVN so that you can see the version tagged for 8.3-R Specifically, this line: 2309: #defineBCOM_DEVICEID_BCM5720 0x165F > Also, I attempted to identify whether the Intel i350 is supported. > It's not listed in the hardware notes or the igb(4) manpage so I > suspect it is not supported. Boot up and see if it shows up as an unknown device. HINT: 0x8086 is often Intel's Vendor ID It's easier to start that route and get the vendor/device hex so you can recursively grep src/sys/dev for those hex values (make sure to do it case insensitively). Investigating each match (especially if it ends in "_reg.h" or "_reg.c" or "hw.c" etc.) should show you (in code) which modules may (or may not) support a given unknown hardware (either in your current branch or another). If you're commonly dealing with new hardware on an often-enough basis, then it's advisable to have a copy of HEAD checked out for keeping src/sys/dev up to date for recursive grepping to find out if hardware is supported (in the previously described manner). > When I view the igb source, the i350 is > referenced numerous times. Are these references simply code in > preparation for support of the i350? > Maybe. If you have HW specs for the board you're trying to integrate, check for the vendor/device id's and see if they match the references that you're finding in code. -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-question
Re: How do I determine support for $xx?
On 08/06/2012 16:07, Rick Miller wrote: > If this question is better suited for a different list please let me > know. Simply stated, my question is 'What is the best source for > identifying supported hardware?'. Having said that, allow me to pose > an example... > > I've attempted to identify if various ethernet controllers are > supported by FreeBSD and the drivers. I used the hardware notes and > manpages for the respective ethernet drivers. The information between > the two sometimes seems inconsistent and/or inaccurate. For example, > the BCM5719 and BCM5720 are unsupported in FreeBSD at this time. The > hardware notes at freebsd.org do not specify these controllers are > supported. Inspection of the bge(4) manpage implies that the > controllers are supported as seen in the description section where it > states: > > "The bge driver provides support for various NICs based on the > Broadcom BCM570x, 571x, 572x, 575x, 576x, 578x, 5776x and 5778x > Gigabit Ethernet controller chips and the 590x and 5779x Fast Ethernet > controller chips." The Hardware notes do not contain definitive lists of all of the hardware that is supported. Support for NICs generally goes by what chipset is used in the NIC, but may be confounded by some manufacturers using unusual firmware. If a particular device is listed in a man page, that indicates that device has been tested and is known to work. If the source code makes reference to a specific device, then generally that device will work too: part working or in-progress code is not generally committed to the FreeBSD sources. If a devices' chipset is listed in a man page, but there's no reference to a specific device, then the device stands a good chance of working. If such a device doesn't work, then frequently it can be fixed quite easily by specifying appropriate device quirks. > I browsed the source and found many references to the BCM5719 and > BCM5720. However, I am unfamiliar enough with driver programming in C > to identify if a controller is fully supported. > > Also, I attempted to identify whether the Intel i350 is supported. > It's not listed in the hardware notes or the igb(4) manpage so I > suspect it is not supported. When I view the igb source, the i350 is > referenced numerous times. Are these references simply code in > preparation for support of the i350? As I said above, this would be unusual. The development process in FreeBSD nowadays is to work on projects (eg. the addition of a driver for a new piece of hardware) off-line and only commit the code to the mainline sources once it is basically complete and ready for exposure to a wider audience for testing. Ultimately the best way to tell if any particular device is supported is to try it. There are plenty of USB-stick images of FreeBSD or PC-BSD readily downloadable so you can test boot up a candidate machine without committing to install the OS on it. While most manufacturers won't "support" FreeBSD per-se, if you can find the right sort of techy person to talk to, they'll often tip you off about whether FreeBSD is known to work or not. Hardware from big-name suppliers (Dell, HP and the like for complete systems; Intel, Broadcomm for NICs) is a priority for support although it may take a few months for the code to become generally available for the newest bits of kit. In fact, so long as the components you want to use have been on the market for around 6 months (very approximately) and they are aimed at use in server hardware rather than personal or casual use, the chances are good that they will just work in FreeBSD. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: UEFI Secure Boot Specs - And some sanity
grarpamp wrote: > Isn't there a lot of needless handwaving going on when the spec is > pretty clear that installing your own complete PKI tree will all > boil down to what is effectively a jumper on the motherboard? The hope for a jumper is insufficient. Cracking open laptops is no fun. It's not often that they unscrew easily; usually considerable fear of breaking innards or chassis. Hoping a jumper Might be under an easily unscrewable panel seems unlikely. 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: Configuration problem with IPv6 router ("cannot forward src")
On 07/06/2012 23:56, Robert Bonomi wrote: Please provide the output from these two commands: ifconfig -a netstat -nr on both the router and on an 'inside' machine. (identifying which is which:) There is also a question of 'where' the /48 comes from -- and how traffic to those addresses is being routed from the outside world. The /48 came from my ISP, so it should be getting routed correctly. ifconfig -a (with ral0/lo0 removed): em0: flags=8843 metric 0 mtu 1500 options=4219b ether [em0_MAC] inet 192.168.2.1 netmask 0xff00 broadcast 192.168.2.255 inet6 fe80::[em0_MAC]%em0 prefixlen 64 scopeid 0x1 inet6 [prefix]:a::b prefixlen 64 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active em1: flags=8843 metric 0 mtu 1500 options=4219b ether [em1_MAC] inet6 fe80::[em1_MAC]%em1 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active tun0: flags=8051 metric 0 mtu 1492 options=8 inet6 fe80::[em0_MAC]%tun0 prefixlen 64 scopeid 0xf inet [MYADDR] --> [HISADDR] netmask 0xff00 inet6 [prefix]:c::b prefixlen 64 nd6 options=21 Opened by PID 1092 Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default[HISADDR] UGS 0 2476 tun0 [MYADDR] link#15UHS 00lo0 [HISADDR] link#15UH 00 tun0 127.0.0.1 link#14UH 00lo0 192.168.2.0/24 link#1 U 0 3985em0 192.168.2.1link#1 UHS 00lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRSlo0 => default fe80::[em0_MAC]%tun0 UGS tun0 ::1 link#14 UH lo0 :::0.0.0.0/96 ::1 UGRSlo0 [prefix]:c::/64 link#15 U tun0 [prefix]:c::1 link#15 UHS lo0 [prefix]:a::/64 link#1 U em0 [prefix]:a::1 link#1 UHS lo0 fe80::/10 ::1 UGRSlo0 fe80::%em0/64 link#1 U em0 fe80::[em0_MAC]%em0 link#1UHS lo0 fe80::%em1/64 link#2 U em1 fe80::[em1_MAC]%em1 link#2UHS lo0 fe80::%lo0/64 link#14 U lo0 fe80::1%lo0 link#14 UHS lo0 fe80::%tun0/64link#15 US tun0 fe80::[em0_MAC]%tun0 link#15 UHS lo0 ff01::%em0/32 fe80::[em0_MAC]%em0 U em0 ff01::%em1/32 fe80::[em1_MAC]%em1 U em1 ff01::%lo0/32 ::1 U lo0 ff01::%tun0/32fe80::[em0_MAC]%tun0 US tun0 ff02::/16 ::1 UGRSlo0 ff02::%em0/32 fe80::[em0_MAC]%em0 U em0 ff02::%em1/32 fe80::[em1_MAC]%em1 U em1 ff02::%lo0/32 ::1 U lo0 ff02::%tun0/32fe80::[em0_MAC]%tun0 UGS tun0 rtadvd.conf contains: em0:\ :addrs#1:addr="[prefix]:a::":prefixlen#64;tc=ether:raflags="o": rc.conf contains: ifconfig_em0=" inet 192.168.2.1 netmask 255.255.255.0" ifconfig_em0_ipv6=" inet6 [prefix]:a::b" ifconfig_em1="up" pf_enable="YES" gateway_enable="YES" ppp_enable="YES" ppp_nat="NO" ppp_goscomb_mode="ddial" ppp_goscomb_nat="NO" ppp_profile="isp" ipv6_gateway_enable="YES" ipv6_network_interfaces="em0 em1 tun0" dhcpd_enable="YES" dhcpd6_enable="NO" dhcpd_flags="-q" dhcpd6_flags="-q" dhcpd_conf="/usr/local/etc/dhcpd.conf" dhcpd6_conf="/usr/local/etc/dhcpd6.conf" dhcpd_ifaces="em0" dhcpd6_ifaces="em0" dhcpd_withumask="022" dhcpd6_withumask="022" dhcpd_chuser_enable="YES" dhcpd6_chuser_enable="YES" dhcpd_withuser="dhcpd" dhcpd6_withuser="dhcpd" dhcpd_withgroup="dhcpd" dhcpd6_withgroup="dhcpd" dhcpd_chroot_enable="YES" dhcpd6_chroot_enable="YES" dhcpd_devfs_enable="YES" dhcpd6_devfs_enable="YES" dhcpd_rootdir="/var/db/dhcpd" dhcpd6_rootdir="/var/db/dhcpd6" rtadvd_enable="NO" rtadvd_interfaces="em0" I've tried configuring a machine with a static configuration, bypassing any issues with rtadvd/dhcpd6 so I'm fairly sure the problem is on the router. -- Bruce Cran ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD: SOLVED: FreeBSD9 - I can't get my mouse to work (was : FreeBSD9 - I can't get my mouse to work)
On Fri, 08 Jun 2012 15:39:22 +, Walter Hurry wrote: > On Thu, 07 Jun 2012 14:59:01 -0400, Jerry wrote: > >> Ubuntu, >> Debian, and Fedora, and projects such as KDE, GNOME and X.org are in >> the process of deprecating HAL as it has "become a large monolithic >> unmaintainable mess". > > Well, I finally got it working. I'm far from an expert in this area, but > what I think was happening was that the touchpad was grabbing /dev/psm0, > and then X.org tried to allocate the same port for the USB mouse, which > of course failed (even though I had specified a Device of /dev/ums0, and > set AutoAddDevices to Off so as to take hald out of the picture). > > The solution for me was to run moused *on port /dev/ums0* and then > specify the device as /dev/sysmouse in xorg.conf. > > However, that leads me to another question: my amateurish way to get > moused to run on /dev/ums0 was to hack /etc/rc.d/moused and hard code > it. > I don't think that's very good, and I suspect that the "right" way to do > it was to set some variable in /etc/rc.conf. > > Can anyone guide me on how that should be done, or point me to a fine > manual? > > Thamks to all for the responses. > Never mind: Stupid moi. The answer was staring me in the face in man rc.conf. moused_port. ___ freebsd-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: Configuration problem with IPv6 router ("cannot forward src")
Make sure you are only advertising a /64 addr prefixlen in rtadvd.conf, and not the entire /48. On 6/7/2012 4:36 PM, Bruce Cran wrote: I'm trying to set up a IPv6 router (running -current) on my home network. My ISP gives me a /128 via PPP and I have a /48 allocation, which I use to give em0 and tun0 public addresses in different subnets (tun0 is assigned the address via ppp.linkup). I've added all the IPv6 settings to rc.conf (ipv6_gateway_enable, ipv6_network_interfaces, rtadvd_enable etc.) and I can ping IPv6 sites from the router. The problem is that rtadvd continues advertising the default gateway as tun0's link-local address - and pinging from a machine on the network results in "cannot forward src" messages on the router (strangely, despite hisaddr being fe80::205:... in ppp.log, the kernel logs the address as fe80:f::205:...). Is there some extra configuration I've likely missed that's needed when using IPv6 via PPP? ___ freebsd-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: SOLVED: FreeBSD9 - I can't get my mouse to work (was : FreeBSD9 - I can't get my mouse to work)
On Thu, 07 Jun 2012 14:59:01 -0400, Jerry wrote: > Ubuntu, > Debian, and Fedora, and projects such as KDE, GNOME and X.org are in the > process of deprecating HAL as it has "become a large monolithic > unmaintainable mess". Well, I finally got it working. I'm far from an expert in this area, but what I think was happening was that the touchpad was grabbing /dev/psm0, and then X.org tried to allocate the same port for the USB mouse, which of course failed (even though I had specified a Device of /dev/ums0, and set AutoAddDevices to Off so as to take hald out of the picture). The solution for me was to run moused *on port /dev/ums0* and then specify the device as /dev/sysmouse in xorg.conf. However, that leads me to another question: my amateurish way to get moused to run on /dev/ums0 was to hack /etc/rc.d/moused and hard code it. I don't think that's very good, and I suspect that the "right" way to do it was to set some variable in /etc/rc.conf. Can anyone guide me on how that should be done, or point me to a fine manual? Thamks to all for the responses. ___ freebsd-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 do I determine support for $xx?
Hi All, If this question is better suited for a different list please let me know. Simply stated, my question is 'What is the best source for identifying supported hardware?'. Having said that, allow me to pose an example... I've attempted to identify if various ethernet controllers are supported by FreeBSD and the drivers. I used the hardware notes and manpages for the respective ethernet drivers. The information between the two sometimes seems inconsistent and/or inaccurate. For example, the BCM5719 and BCM5720 are unsupported in FreeBSD at this time. The hardware notes at freebsd.org do not specify these controllers are supported. Inspection of the bge(4) manpage implies that the controllers are supported as seen in the description section where it states: "The bge driver provides support for various NICs based on the Broadcom BCM570x, 571x, 572x, 575x, 576x, 578x, 5776x and 5778x Gigabit Ethernet controller chips and the 590x and 5779x Fast Ethernet controller chips." I browsed the source and found many references to the BCM5719 and BCM5720. However, I am unfamiliar enough with driver programming in C to identify if a controller is fully supported. Also, I attempted to identify whether the Intel i350 is supported. It's not listed in the hardware notes or the igb(4) manpage so I suspect it is not supported. When I view the igb source, the i350 is referenced numerous times. Are these references simply code in preparation for support of the i350? -- Take care Rick Miller ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Dear Customer:Andriod Tablet PC Start From $55
If this e-mail is not d= isplayed properly, use the following link: [1]http://emaillink2.priceangels.com/u/ gm.php?prm=3mkxZ04mg2_143435532_225003_2792 [2] 3D"PriceAngels.com" [3] Home<= /td> [4] New Arrivals [5] Best Sellers<= a href="http://emaillink2.priceangels.com/u/nrd.php?p=3mkxZ04mg2_279 2_2= 25003_1_5" style="text-decoration: none;"> Spec= ial Offers [6] $0= .99 Gadgets [7] Drop Shipping [8][socialn=] [9] [=] <= /a> [10]3D"Android 3D"Free <= /td>[11] 3D" New &a= mp; On Sale 10% OFF 10% OFF 12% = OFF 10% OFF[12]3D"Free [13] 3D"Free[14]=3D"Free[15] 3D"Fr = [16] LED Sport Watch w= ith Colorful Strap [17] Sport Digi= tal Waterproof Wrist Watch [18] L= eather Case for iPhone 4S[19]R= /C Toy Preschool Toy for Children $6.16 $5.54 <= td width="163" valign="middle" height="30" align="center">[DEL: $9.35 :DEL] $8.41[DEL: $10.08 :DEL] $8.87 [DEL: $7.87 :DEL] $7.08 12% OFF 8% OFF 1= 0% OFF 12% OFF [20] 3D"Free[21] 3D"Free[22] 3D"Free [23] 3D"Free [24] LED Fl= ashlight Warning Light for Motorcycle Car [25] 10-inch Anti Shock Handbag for Laptop Notebook <= td width="163" valign="top" align="center"> Wireless Optical Mouse with Battery [26]Solar Energy Saving Lamp Camping La= mp Lantern LED Light [DEL: $2.47 :DEL] $2.17 [DEL: $25.29 :DEL] $23.27 = [DEL: $10.49 :DEL] $9.44[DEL: $7.89 :DEL] $6.94 12% OFF 11% OF= F 10% OFF 10% OFF = 3D"Free[27] 3D"Free [28]3D"Free [29]3D"Free [30] Waterproof Bike Wheel 2-Mode LED = Lights <= a style="font: 11px/18px Verdana; padding: 5px 8px; text-decoration: none= ; color: rgb(0, 0, 0);" href="http://emaillink2.priceangels.com/u/nrd.php ?p=3mkxZ04mg2_2792_225003_1_32" target="_blank"> Android 4.0 Tablet PC = with 9.7-inch Capacitive Touch Screen [31] Android 2.3 8GB Tablet PC [32] Nintendo Wii Console <= del style="font-size: 14px; font-family: Calibri; color: rgb(153, 153, 15= 3); text-decoration: line-through;">$7.06$6.21 [DEL: $356.27 :DEL] $317.08 [DEL: $132.79$119.51 :DEL] [DEL: $117.63 :DEL] $105.87 10% OFF 12% OFF 12% OFF 12% OF= F [33] 3D"Free 3D"Free[34] 3D"Free[35] ="Free [36] Aputure CR3= N Combo Camera Shutter Control [37] US Charger/Earphone/Car Charger/Data Cable for Apple iPhone 4G 3G 3GS [38] Multifunctional Cycling Bike = Bicycle Bag [39]USB Powered Coo= ling Fan for Notebook [DEL: $8.54 :DEL] $7.69 [DEL: $6.91 :DEL] $6.08 = [DEL: $14.24 :DEL] $12.53 [DEL: [DEL: $3.92 :DEL] $3.45 :DEL] 10% OFF 10% OFF 15% OFF 12% OFF [40]="Free [41] 3D"Free <= td width="163" valign="middle" height="150" align="center"> 3D"Free[42] 3D"Free [43] Sun Visor UV Protection Riding Leg Pad [44] Solar Powered Electronic Calculator= [45] Paper Currency Style Passport Holder Case [46]Soda Push Style Dispenser with Mi= ni Tap [DEL: $12.07 :DEL] $10.86 [DEL: $3.71 :DEL] $3.34 [DEL: [DEL: [DEL: $6.29 :DEL] $5.54 :DEL] :DEL] <= tr> [47]3D"US [48]3D"facebook" [49]Facebo= ok [50]3D"twitter" [51]twitte= r [52]3D"youtube" [53]youtub= e = Note:Pl= ease do not reply to this email. if you have any questions please [54]contact us Price Angels CO | Limited Flatr= m /704 7/F Bright Way Tower,33 Mong Kok Road ,Mong Kok, Kl Tel:+86 755 86382312. [55]Privacy Notice =Copyright @ 2011 PriceAngels.com. All rights reserved. If you want to unsubscribe from our mailing = list, use the following link: [56]http://emaillink2.priceangels.com/u/un.php?par=3mkx Z04mg2_225003_2792_$sid$ [ema=] References 1. 3D"http://emaillink2=/ 2. 3D"http://emaillink2.price=/ 3. 3D"http://em=/ 4. 3D"http://emaillink2.priceangels.com=/ 5. 3D"http://emaillink2.priceangels.com/u/nrd.php?p=3 6. 3D"http: 7. file://localhost/tmp/3D"http 8. 3D"http://b.ems.to/fw/t/WIEv:rgt:Sy5*k"; 9. file://local
Re: find date of last boot
On Fri, 08 Jun 2012 12:08:20 +0100 Matthew Seaman articulated: >In passing, apparently it seems that creating a user with a username of >'reboot' is probably not recommended. That would seem like a good idea. Interestingly enough, I had a friend who had a password: "PassWord" that he used as a joke. On day he tried it on an internet site for a throw away account he was creating and the site rejected it claiming it was not a valid password. Perhaps FreeBSD could have some sort of validation in place to refuse to accept certain user-IDs such as "reboot". -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ signature.asc Description: PGP signature
Re: find date of last boot
On 08/06/2012 07:19, Matthew Seaman wrote:
> On 08/06/2012 05:50, Randal L. Schwartz wrote:
>> Sure, but the question was likely involving a stock system, so yes, your
>> mileage may vary, but let's consider a solution that works for a default
>> system. "last reboot" isn't it.
>
> It's not that. 'last reboot' seems to be broken at the moment, at least
> on stable/9:
>
> lucid-nonsense:~:% uname -a
> FreeBSD lucid-nonsense.infracaninophile.co.uk 9.0-STABLE FreeBSD
> 9.0-STABLE #15 r236465: Sat Jun 2 23:14:59 BST 2012
> r...@lucid-nonsense.infracaninophile.co.uk:/usr/obj/usr/src/sys/LUCID-NONSENSE
> amd64
>
> I rebooted a few days ago:
>
> lucid-nonsense:~:% uptime
> 7:14AM up 3 days, 8:18, 1 user, load averages: 0.03, 0.01, 0.01
>
> And the utx.log file was last rotated over a week ago:
>
> lucid-nonsense:~:% ls -la /var/log/utx*
> -rw-r--r-- 1 root wheel394 Jun 7 17:51 /var/log/utx.lastlogin
> -rw-r--r-- 1 root wheel 16841 Jun 8 07:06 /var/log/utx.log
> -rw-r--r-- 1 root wheel 24878 May 31 22:41 /var/log/utx.log.0
> -rw-r--r-- 1 root wheel 13741 Apr 30 08:50 /var/log/utx.log.1
> -rw-r--r-- 1 root wheel 27886 Mar 31 22:52 /var/log/utx.log.2
>
> but last(1) isn't coming up with the goods:
>
> lucid-nonsense:~:% last reboot
>
> wtmp begins Fri Jun 1 06:14:46 BST 2012
>
> (nor does it work if I tell last to use the older utx.log files)
Having investigated, the problem appears to be that wtmp used to use the
literal string 'reboot' in the username field of its records, while in
struct utmpx, that field is left blank but the record type field
indicates if this is the time the system shutdown or rebooted.
The attached patch fixes the problem for me. Or see
http://www.freebsd.org/cgi/query-pr.cgi?pr=168844
lucid-nonsense:~:% /usr/obj/usr/src/usr.bin/last/last reboot
boot time Mon Jun 4 22:58
shutdown time Mon Jun 4 22:54
boot time Sun Jun 3 09:43
shutdown time Sun Jun 3 09:39
wtmp begins Fri Jun 1 06:14:46 BST 2012
In passing, apparently it seems that creating a user with a username of
'reboot' is probably not recommended.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
JID: matt...@infracaninophile.co.uk Kent, CT11 9PW
Index: usr.bin/last/last.c
===
--- usr.bin/last/last.c (revision 236465)
+++ usr.bin/last/last.c (working copy)
@@ -64,6 +64,7 @@
typedef struct arg {
char*name; /* argument */
+#defineREBOOT_TYPE -1
#defineHOST_TYPE -2
#defineTTY_TYPE-3
#defineUSER_TYPE -4
@@ -180,6 +181,8 @@
if (argc) {
setlinebuf(stdout);
for (argv += optind; *argv; ++argv) {
+ if (strcmp(*argv, "reboot") == 0)
+ addarg(REBOOT_TYPE, *argv);
#defineCOMPATIBILITY
#ifdef COMPATIBILITY
/* code to allow "last p5" to work */
@@ -391,6 +394,11 @@
for (step = arglist; step; step = step->next)
switch(step->type) {
+ case REBOOT_TYPE:
+ if (bp->ut_type == BOOT_TIME ||
+ bp->ut_type == SHUTDOWN_TIME)
+ return (YES);
+ break;
case HOST_TYPE:
if (!strcasecmp(step->name, bp->ut_host))
return (YES);
signature.asc
Description: OpenPGP digital signature
Re: FreeBSD on the ASUS P8H67-M LGA1155 H67 motherboard
Victor Sudakov wrote: > > > > 2. It looses one of the HDDs during intensive read/write operations: > > > > Jun 2 00:55:33 vas kernel: ahcich1: Timeout on slot 4 port 0 > > Jun 2 00:55:33 vas kernel: ahcich1: is cs 00c0 ss 00f0 rs > > 00f0 tfd c0 serr cmd c617 > > Jun 2 00:56:48 vas kernel: ahcich1: Timeout on slot 0 port 0 > > Jun 2 00:56:48 vas kernel: ahcich1: is cs 0001 ss rs > > 0001 tfd c0 serr cmd c017 > > Jun 2 00:57:20 vas kernel: ahcich1: AHCI reset: device not ready after > > 31000ms (tfd = 0080) > > > > I shall of course check the HDD and cable, but they worked flawlessly on > > the previous system. > > The cable is OK. I have tried different SATA slots on the motherbord too, > the HDD losses persist. How can a rule out a kernel driver bug in ahci > or ada, perhaps a PR is due? Well, there is already a very similar PR kern/161248 -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-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: Which FreeBSD for Intel i7-2600S and DQ67SWB3?
Snippet from David Christensen : > http://lists.freebsd.org/pipermail/freebsd-questions/2012-March/239742.html > It looks like -STABLE are daily development/ test builds (?): > ftp://ftp.allbsd.org/pub/FreeBSD-snapshots/amd64-amd64/ > I'm looking for stability. I'll try the 9.0-RELEASE: > ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/amd64/ISO-IMAGES/9.0/ I had a weird problem with 9.0-RELEASE: after updating a NetBSD source tree by "cvs up -dP", the system froze and I needed the Reset button. A couple days later, after better than 24 hours inactivity, I heard sounds of reboot and verified by looking. File system was not cleanly umounted and had to be fsck'ed, which was dome automatically on the reboot. Given my very new hardware, I figured to upgrade to STABLE, building from source. That worked, and the weird problem has not reappeared. I didn't even ask the list for help. I suppose I could also have tried RELENG_9_0, maybe a patch would have fixed the problem, but my very new hardware and new Xorg version in the works led me to go to STABLE. Daily development/test builds sound more like HEAD (=CURRENT) than STABLE. STABLE is more tested than HEAD. I think if I ever try FreeBSD-HEAD, I'd install to a separate partition and keep the STABLE installation intact. Tom ___ freebsd-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: setting gcc46 as default compiler?
Jeff Hamann написал: I've built and installed the gcc46 compiler(s) - need gfortran - and I can't seem to find the correct documentation on how to update /etc/make.conf for including the gfortran46. This is what mine currently looks like: $ cat make.conf # added by use.perl 2012-06-07 03:03:21 PERL_VERSION=5.10.1 ..if !empty(.CURDIR:M/usr/ports/*)&& exists(/usr/local/bin/gcc46) CC=gcc46 CXX=g++46 CPP=cpp46 FC=gfortran46 ..endif FFLAGS=-O2 -mtune=athlon64 CC=gcc46 CXX=g++46 CPP=cpp46 FC=gfortran46 $ Am I close? Help? When I want some port to use gcc46 I use USE_GCC=4.6+. This takes care of depending ports on gcc port. -- Sphinx of black quartz judge my vow. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
