Re: pkg_add and 9.1 Release
This path does not exist on ftp.freebsd.org. Quite so. It's because of this: http://www.freebsd.org/news/2012-compromise.html As a consequence, large parts of the package building infrastructure are quarantined, pending reinstallation. Also there is a lot of work going into revising the software used to build the packages with security enhancements in mind. So there simply aren't packages available yet to go with 9.1-RELEASE. Cheers, Matthew Hi Matthew, In this case for a new Nas4free machine, will you recommend to base it on 9.0 or 9.1 ? Thanks, Peter ___ freebsd-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: pkg_add and 9.1 Release
On 02/01/2013 08:00, Zyumbilev, Peter wrote: In this case for a new Nas4free machine, will you recommend to base it on 9.0 or 9.1 ? Either. Whichever one works best for you, and if you can't distinguish them on performance or bug-fixes, choose 9.1. However, don't fall into the trap of thinking 'because I'm running OS version 9.0 I have to use the binary packages for 9.0.' You don't. And in fact, if it's more than a month or so since the OS was released, you should be checking for updates. Unfortunately, since the security problem, there haven't been updates to package sets for *any* OS versions available. So your best recourse is to pull down a copy of the ports tree and build what packages you need for yourself. This is time consuming, but not particularly difficult. Cheers, Matthew ___ freebsd-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: GIT instaed of SVN?
When it comes to keeping sources, most developer and most large dislocated and non-centralized projects prefer GIT over Subversion. FreeBSD has moved from the ancient CVS to Subversion not long ago and I was wondering why freeBSD would have done this, since Subversion lacks in so many aspects of a modern revision system. Well, I face several odds now since I need a kind of hot replication system that replicates my Subversion repositories and I feel uncomfortable with the way Subversion performs this. I decided to move forward to GIT which seems more appropriate in any aspect and while I do not have so much legacy to carry on with, I think for me pesonally the move is more logical. But what is with the FreeBSD project? Are there any attempts or intentions to bring GIT also to the sources (the base system, the ports)? oh signature.asc Description: OpenPGP digital signature
Re: FreeBSD: GIT instaed of SVN?
On 01/02/2013 02:31 AM, O. Hartmann wrote: When it comes to keeping sources, most developer and most large dislocated and non-centralized projects prefer GIT over Subversion. FreeBSD has moved from the ancient CVS to Subversion not long ago and I was wondering why freeBSD would have done this, since Subversion lacks in so many aspects of a modern revision system. Well, I face several odds now since I need a kind of hot replication system that replicates my Subversion repositories and I feel uncomfortable with the way Subversion performs this. I decided to move forward to GIT which seems more appropriate in any aspect and while I do not have so much legacy to carry on with, I think for me pesonally the move is more logical. But what is with the FreeBSD project? Are there any attempts or intentions to bring GIT also to the sources (the base system, the ports)? http://wiki.freebsd.org/Git http://wiki.freebsd.org/GitDrawbacks Basically, the workflow practiced by the FreeBSD developers and release engineers would have to change completely, otherwise Git would fight them every step of the way. There are those of us who maintain Git mirrors of the project repos (with or without local patchsets), but they are in no way official. -- Fuzzy love, -CyberLeo Furry Peace! - http://www.fur.com/peace/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ssh server hashcode change on nanoBSD
On Tue, 1 Jan 2013 18:59:05 +0330, takCoder wrote: thank you for the details mentioned :) but now, a questions occurred to me about this ssh key. as i don't know enough about its process, would you please tell me whether this key is a shared key for all ssh clients who send a request? or it differs as the client changes? The key received in the first step of a SSH session is the host key which identifies the host (in your case: the nanoBSD box). This key is stored in the SSH client's key database for reference because the key of a box typically does not change. If it changes - there should be a valid reason for it, or it might look like there's something wrong here. As explained, this host key is generated when no key is found at startup. As soon as you make it permanent to your nanoBSD installation, the key will obviously stay the same, and the SSH client won't complain. -- 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
defines in system headers
I ran into a problem with /usr/include/xlocale/_ctype.h in 9.1 Line 56 is - #if __GNUC__ !__GNUC_STDC_INLINE__ but within a tinderbox on a 9.0 system (yes I know that setup isn't actually supported) using gcc as the compiler __GNUC_STDC_INLINE__ isn't defined and generates a ! has no right operand error. Isn't the correct way to test that #if defined(__GNUC__) !defined(__GNUC_STDC_INLINE__) ___ freebsd-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: GIT instaed of SVN?
Git is also not BSD licensed. I believe it may require bringing Python into base as well. ___ freebsd-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: 9.1 won't install - GEOM/GRAID issues
Mike. the.li...@mgm51.com wrote: My FreeBSD server had been running fine, no issues. This evening I tried to update it to 9.1. I don't update in place, I update by wiping the prior version and letting the new version have its way with the disk. Well, 9.1 has issues with my system (dmesg is at the end of this message). When I boot from the install DVD, I see a lot of messages along the lines of ~Root mount waiting for GRAID~, then eventually that times out and I am allowed to select the Install option. However, when I get to the partitioning (btw, it's another issue, but the new set of screens to partition the drive really suck. I've never been so confused by a FreeBSD install. But I digress...) I eventually selected auto partitioning. Then I am greeted with a pop up that informs me that ada0 is not valid for some unmentioned reason. (did I mention that the new partitioning screens suck?). At this point I give up, and I am now in the process of re-installing 9.0. I'm not a long-time user of FreeBSD, I've only been using it since 2005, with installs to keep it up to date through the varied and sundry versions. But this is The First Time that a FreeBSD install has failed. What's goin' on? Probably there's corrupt raid metadata (or something that can be confused with raid metadata) on the disk(s). You could try booting with kern.geom.raid.enable set to 0 or without the module loaded. Sanitising the disk(s) should work as well. Fabian signature.asc Description: PGP signature
Re: 9.1 on FTP
On Sat, 08 Dec 2012 13:20:43 +, Matthew Seaman wrote: Yes, 9.1-RELEASE is delayed. Some of that is due to the effects of the security compromise, some is down to the release process not being pushed through as efficiently as it might be. It is coming. Soon. After the announcement the other day I have upgraded a test box (using freebsd-update) from 9.1-RC3 to 9.1-RELEASE. Entirely smooth and painless. Congratulations and heartfelt thanks to all concerned. ___ freebsd-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: ssh server hashcode change on nanoBSD
On Tue, Jan 1, 2013 at 10:41 PM, Lowell Gilbert wrote: Don't top-post, please. Sorry for top-posting.. i'll try to keep an eye on it from now on :) well, cause i got my answer, let's have a conclusion: According to: On Tue, Jan 1, 2013 at 10:41 PM, Lowell Gilbert wrote: There are a number of keys involved in ssh. The host keys are used at the start of the connection to make sure that some other machine doesn't impersonate the one you wanted. and On Wed, Jan 2, 2013 at 2:22 PM, Polytropon wrote: The key received in the first step of a SSH session is the host key which identifies the host (in your case: the nanoBSD box). This key is stored in the SSH client's key database for reference because the key of a box typically does not change. .. As explained, this host key is generated when no key is found at startup. As soon as you make it permanent to your nanoBSD installation, the key will obviously stay the same, and the SSH client won't complain i made my ssh server key permanent on my nanoBSD server, by moving /etc/ssh/ files to /cfg/ssh files (i think those two files named dsa_key are enough, but in this test, i copied all files in the source dir..) and now there are no compliments from any clients, thanks to Polytropon and Lowell and Aldis. :) Cryptography in general is quite complicated, and ssh is a lot more complicated than just its cryptography. and also thank you all for your patience and good explanations :) Best Regards, t.a.k ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Could not access root and user account after installing xorg-minimal
I am running FreeBSD-9 After installing xorg-minimal by #pkg_add -r xorg-minimal and installing fonts by #cd /usr/port/x11-fonts/urwfonts #make install clean I installed Irsis. The problem occured after I issued the #startx , an error message appeared for a very short time.I could not read it.But think it was reading monitor. Now I can not access any account.wrong password message appears after typing the password. Thanks in advance. ___ freebsd-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: pkg_add and 9.1 Release
Matthew Seaman wrote: On 02/01/2013 08:00, Zyumbilev, Peter wrote: In this case for a new Nas4free machine, will you recommend to base it on 9.0 or 9.1 ? Either. Whichever one works best for you, and if you can't distinguish them on performance or bug-fixes, choose 9.1. However, don't fall into the trap of thinking 'because I'm running OS version 9.0 I have to use the binary packages for 9.0.' You don't. And in fact, if it's more than a month or so since the OS was released, you should be checking for updates. Unfortunately, since the security problem, there haven't been updates to package sets for *any* OS versions available. So your best recourse is to pull down a copy of the ports tree and build what packages you need for yourself. This is time consuming, but not particularly difficult. Cheers, Matthew what is the status of ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-current/Latest/ which is on the ftp servers? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
is csup broken?
Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 ___ freebsd-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 csup broken?
On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? -- 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: is csup broken?
On Wed, Jan 02, 2013 at 04:20:25PM +0100, Polytropon wrote: Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? ISTM that SVN is not the default method for users; but portsnap is the preferred method for users. Developers, OTOH, may find SVN useful. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html I have no idea if the OP is a user or a developer; but I do know that at least a cursory reading of the Handbook is a good idea, since the OP question seems to be directly addressed in the Handbook. Regards, Joe ___ freebsd-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 csup broken?
On Wednesday 02 January 2013 10:14:17 am Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 It must have to do with the security incident that took place a couple of months ago. It affects all package updates for 9.1 via pkg_add and csup, I guess. Dimitri -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-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 csup broken?
Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. Really between a rock and a hard place. What the heck are the Freebsd officials doing? They really mucked up 9.1 release big time. ___ freebsd-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: 9.1 won't install - GEOM/GRAID issues
On 1/2/2013 at 2:38 PM Fabian Keil wrote: |Mike. the.li...@mgm51.com wrote: | | My FreeBSD server had been running fine, no issues. This evening I | tried to update it to 9.1. I don't update in place, I update by | wiping the prior version and letting the new version have its way with | the disk. | | Well, 9.1 has issues with my system (dmesg is at the end of this | message). | | When I boot from the install DVD, I see a lot of messages along the | lines of ~Root mount waiting for GRAID~, then eventually that times out | and I am allowed to select the Install option. However, when I get to | the partitioning (btw, it's another issue, but the new set of screens | to partition the drive really suck. I've never been so confused by a | FreeBSD install. But I digress...) I eventually selected auto | partitioning. Then I am greeted with a pop up that informs me that | ada0 is not valid for some unmentioned reason. (did I mention that | the new partitioning screens suck?). | | At this point I give up, and I am now in the process of re-installing | 9.0. | | I'm not a long-time user of FreeBSD, I've only been using it since | 2005, with installs to keep it up to date through the varied and sundry | versions. But this is The First Time that a FreeBSD install has | failed. | | What's goin' on? | |Probably there's corrupt raid metadata (or something that can be |confused with raid metadata) on the disk(s). | |You could try booting with kern.geom.raid.enable set to 0 or |without the module loaded. Sanitising the disk(s) should work |as well. | |Fabian = Thanks for the reply. The disk in question has never been used for RAID, so if there is RAID metadata on the disk, I do not know how it got there. The disk is (I believe --- it's been a while since I have been inside that box) on a Promise SATA RAID controller, but RAID is not used and has never been used (I have a 3Ware controller for RAID on that box). When things settle down, I'll try to figure out how to sanitize the disk and try to install 9.1 again. Thanks again for your quick reply. Mike. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: is csup broken?
Joe Altman wrote: On Wed, Jan 02, 2013 at 04:20:25PM +0100, Polytropon wrote: Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? ISTM that SVN is not the default method for users; but portsnap is the preferred method for users. Developers, OTOH, may find SVN useful. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-portsnap.html I have no idea if the OP is a user or a developer; but I do know that at least a cursory reading of the Handbook is a good idea, since the OP question seems to be directly addressed in the Handbook. Regards, Joe As the OP I see no need to pollute my system with a complete ports tree when I only have to compile php5 to enable the apache module. Thats over kill in my book. Sure the handbook says to use portsnap but that still loads the complete ports tree. crazy. My ports tree only has the ports I have to recompile to change defaults used in package. This approach saves disk and backup times. ___ freebsd-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 csup broken?
On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. -- 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: is csup broken?
Dimitri Yioulos wrote: On Wednesday 02 January 2013 10:14:17 am Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 It must have to do with the security incident that took place a couple of months ago. It affects all package updates for 9.1 via pkg_add and csup, I guess. Dimitri I am not talking about packages here. subject says is csup broken? I use csup to fetch individual ports not packages. ___ freebsd-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: pkg_add and 9.1 Release
In freebsd-questions Digest, Vol 448, Issue 3, Message: 24 - please pardon the loss of threading - On Wed, 2 Jan 2013 02:47:41 -0500 (EST) d...@safeport.com wrote: On Wed, 2 Jan 2013, Matthew Seaman wrote: On 02/01/2013 05:20, doug wrote: Is this command being phased out? pkg_add -r uses a default environment of ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9.1-release/Latest/ In fact, yes, pkg_add and the other pkg_tools commands are being phased out in favour of pkgng. However it is early days yet, and the problem you're seeing has nothing to do with that process. pkgng won't become the default in 9.x until the next release: until then the status quo ante persists. Looking forward to using pkgng on my next 9.1 laptop, thanks Matthew. This path does not exist on ftp.freebsd.org. Quite so. It's because of this: http://www.freebsd.org/news/2012-compromise.html As a consequence, large parts of the package building infrastructure are quarantined, pending reinstallation. Also there is a lot of work going into revising the software used to build the packages with security enhancements in mind. So there simply aren't packages available yet to go with 9.1-RELEASE. Ah yes, thank you Matthew. I had forgotten about that. I guess the 9.1RC3 packages were removed for the same reason. ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/ is still there, though. I ran into this from the installed 9.1-RELEASE /etc/motd's suggestion of adding Handbook, FAQ etc by using pkg_add -r en-freebsd-doc. I browsed to ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/docs/en-freebsd-doc-39278,1.tbz dated October, and figured that should do for now :) I could have set PACKAGESITE but it was as easy to fetch(1) that file then pkg_add it. If I were going to install say X + KDE on that laptop - which I'm not - I'd merrily use what was fresh in October and upgrade as packages become available again, and build anything needing 'more freshness' from ports. cheers, Ian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: is csup broken?
Polytropon wrote: On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. Still behind the 8 ball. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I'm fubarbed Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is BAD public relations for FreeBSD. ___ freebsd-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 csup broken?
On Wed, 02 Jan 2013 11:08:24 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:34:54 -0500, Fbsd8 wrote: Polytropon wrote: On Wed, 02 Jan 2013 10:14:17 -0500, Fbsd8 wrote: Been using same script for years to fetch selected port files. Today I get error message Unknown collection ports-sysutils Running 9.1 and this worked in 2012 Maybe this is related to the removal of CVS-related services for obtaining src and ports? Have you tried checking out via SVN which now is the desired default method (even though it's not integrated in the base install and the make scripting mechanism)? This is a catch 22 problem. How can I use svn when it's not part of the 9.1 base release? Have to csup it down first and csup is broken. You actually don't _have_ to use CSV. You can install SVN from binary packages via the new pkg command (pkgng instead of traditional pkg_* tools). Or you can obtain a ports tree first with portsnap or from the installation media you've been using, install svn from this, and then continue using svn to obtain updates for ports (and src, if you want). However, you're right about the fact that svn isn't part of the base installation (yet?) and it doesn't fully integrate with what worked with CVS for many years. Still behind the 8 ball. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I'm fubarbed There is an option, even thogh possibly considered unelegant in your situation: Install the ports tree from the installation media and then install the svn port from that outdated ports tree. Afterwards delete the ports tree and use svn to get the components you need. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. That's true - SVN (formerly CVS) provided you with ad hoc changes to the ports tree, whereas portsnap provides a snapshot that might not be enough up to date. I'd really like to see a svn command being part of the base installation, with integration into the comfortable make update mechanism for ports and system sources so it can _really and actually_ replace csup. -- 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
Trying to find out how to mount as user
Hello. I want to write a script, where I as a normal user, can back up my files with rsync to another machine (pc01), which shares a directory via NFS. I have an entry in the local machines /etc/fstab pc01:/backup /mnt/backupnfs rw,noauto 0 0 The command: mount /mnt/backup works as root. If I do sudo mount /mnt/backup I get [tcp] pc01:/backup: Permission denied I'm a member of the local wheel group and at the remote machine as well(pc01) pc01:/backup has drwxrwxr-x 28 root wheel 1024 1 Jan 14:44 backup/ The local mount point /mnt/backup has drwxr-xr-x 5 root wheel 512 1 Jan 17:18 mnt/ drwxr-xr-x 2 root wheel 512 1 Jan 11:38 backup/ I've tried to ad write permissions to the group, but it did not help me. I understand that I have a permission problem but I can't figure it out. Help Please! Thanks /Leslie ___ freebsd-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: 9.1 won't install - GEOM/GRAID issues
Mike. wrote: [snip] Thanks for the reply. The disk in question has never been used for RAID, so if there is RAID metadata on the disk, I do not know how it got there. The disk is (I believe --- it's been a while since I have been inside that box) on a Promise SATA RAID controller, but RAID is not used and has never been used (I have a 3Ware controller for RAID on that box). When things settle down, I'll try to figure out how to sanitize the disk and try to install 9.1 again. If somehow some RAID controller ever wrote out metadata to the disk it will be the last sector or two at the very end. Sometimes some GPT partitioning schemes corrupt this too. If some alien form of GPT partitioning or some form of RAID has written anything to this area it will throw an error when GEOM 'tastes' the disk. You can zero both these areas with dd if=/dev/zero plus disk plus some arithmetic. Another way, and I do sometimes when I go to reuse a disk that's been used for a while, is to use the mfr's diagnostic utility. I know the WD diag utility has an option to write 0's to the entire drive. Sometimes I do this and then run the extended diags just to get a 'feel good' factor on the media. Trouble with this is the larger the disk gets the longer it takes. I just like media scans on old disks before I recycle them to a new project. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
SOLVED...Re: Trying to find out how to mount as user
2013-01-02 17:29, Leslie Jensen skrev: Hello. I want to write a script, where I as a normal user, can back up my files with rsync to another machine (pc01), which shares a directory via NFS. I have an entry in the local machines /etc/fstab pc01:/backup /mnt/backupnfs rw,noauto 0 0 The command: mount /mnt/backup works as root. If I do sudo mount /mnt/backup I get [tcp] pc01:/backup: Permission denied I'm a member of the local wheel group and at the remote machine as well(pc01) pc01:/backup has drwxrwxr-x 28 root wheel 1024 1 Jan 14:44 backup/ The local mount point /mnt/backup has drwxr-xr-x 5 root wheel 512 1 Jan 17:18 mnt/ drwxr-xr-x 2 root wheel 512 1 Jan 11:38 backup/ I've tried to ad write permissions to the group, but it did not help me. I understand that I have a permission problem but I can't figure it out. Help Please! Thanks /Leslie I was on a wired connection first and the on wifi so I had two different IP-addresses! New question: Instead of having the following in my /etc/exports /backup machine01 machine02 Can I put my internal network as 192.168.0/24? /Leslie ___ freebsd-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: 9.1 won't install - GEOM/GRAID issues
Michael Powell wrote:
Mike. wrote:
[snip]
Thanks for the reply. The disk in question has never been used for
RAID, so if there is RAID metadata on the disk, I do not know how it
got there. The disk is (I believe --- it's been a while since I have
been inside that box) on a Promise SATA RAID controller, but RAID is
not used and has never been used (I have a 3Ware controller for RAID on
that box).
When things settle down, I'll try to figure out how to sanitize the
disk and try to install 9.1 again.
If somehow some RAID controller ever wrote out metadata to the disk it will
be the last sector or two at the very end. Sometimes some GPT partitioning
schemes corrupt this too. If some alien form of GPT partitioning or some
form of RAID has written anything to this area it will throw an error when
GEOM 'tastes' the disk.
You can zero both these areas with dd if=/dev/zero plus disk plus some
arithmetic. Another way, and I do sometimes when I go to reuse a disk that's
been used for a while, is to use the mfr's diagnostic utility. I know the WD
diag utility has an option to write 0's to the entire drive. Sometimes I do
this and then run the extended diags just to get a 'feel good' factor on the
media. Trouble with this is the larger the disk gets the longer it takes. I
just like media scans on old disks before I recycle them to a new project.
-Mike
Here is a little script named gpart.nuke that may help you
#! /bin/sh
echo What disk do you want
echo to wipe? For example - da1 :
read disk
echo OK, in 10 seconds I will destroy all data on $disk!
echo Press CTRL+C to abort!
sleep 10
diskinfo ${disk} | while read disk sectorsize size sectors other
do
# Delete MBR and partition table.
dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} count=1
# Delete GEOM metadata.
dd if=/dev/zero of=/dev/${disk} bs=${sectorsize} oseek=`expr $sectors
- 2` count=2
done
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SOLVED...Re: Trying to find out how to mount as user
On Wed, Jan 2, 2013 at 8:47 AM, Leslie Jensen les...@eskk.nu wrote: I was on a wired connection first and the on wifi so I had two different IP-addresses! New question: Instead of having the following in my /etc/exports /backup machine01 machine02 Can I put my internal network as 192.168.0/24? man exports ___ freebsd-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 csup broken?
On Wed, 2 Jan 2013 11:08:24 -0500 fb...@a1poweruser.com wrote: This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is FUD. Stop being afraid of change. Users use portsnap Power users use svn There's no use trying to cover everyone's edge cases. You'll never keep everyone happy. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. Please don't commit ports to the ports tree if you have not tested them! ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
Hi This can be considered a follow up to the message How to keep freebsd-update from trashing custom kernel? sent to this list by Brett Glass on August 13th 2012 (see [1]). Unfortunately there is no solution to the problem in that thread (or I cannot see it). I am running currently running 9.0-RELEASE-p4 and freebsd-update recommends to update to p5. It states: - The following files will be updated as part of updating to 9.0-RELEASE-p5: /boot/kernel/kernel snip - And from experience this is what it will do: replace /boot/kernel/kernel which is my custom kernel with a GENERIC kernel. As it seems that freebsd-update works by comparing a hash of /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ (see [3]). So why is freebsd-update going to overwrite my custom kernel? And how can I prevent it from doing so? By the way there is a post on superuser.com describing the same issue (see [2]). Best Regards andreas [1] http://freebsd.1045724.n5.nabble.com/How-to-keep-freebsd-update-from-trashing-custom-kernel-tt5733932.html#none [2] http://superuser.com/questions/507322/freebsd-update-patches-custom-boot-kernel-kernel-which-breaks-remote-access [3] # md5 /boot/kernel/kernel MD5 (/boot/kernel/kernel) = 5757af02283522328c3537b8550a286a # sha1 /boot/kernel/kernel SHA1 (/boot/kernel/kernel) = a513c6d0d0a71fa5d74156c000952a5211e41465 # md5 /boot/GENERIC/kernel MD5 (/boot/GENERIC/kernel) = 3795c8766abf8e16088b5f1305931483 # sha1 /boot/GENERIC/kernel SHA1 (/boot/GENERIC/kernel) = 3a32246b3ce5f13ddeef336c010adf8f354443da ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: SOLVED...Re: Trying to find out how to mount as user
On Wed, 2 Jan 2013 17:47:15 +0100 Leslie Jensen les...@eskk.nu wrote: I was on a wired connection first and the on wifi so I had two different IP-addresses! FYI a cool trick is to bridge your ethernet and wifi so you can keep your IP and roam between wired and wireless :) ___ freebsd-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: pkg_add and 9.1 Release
On 02/01/2013 14:42, Fbsd8 wrote: what is the status of ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-current/Latest/ which is on the ftp servers? The latest packages there are what was compiled before the security incident. It hasn't been updated since. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: is csup broken?
Mark Felder wrote: On Wed, 2 Jan 2013 11:08:24 -0500 fb...@a1poweruser.com wrote: This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. This is FUD. Stop being afraid of change. Users use portsnap Power users use svn There's no use trying to cover everyone's edge cases. You'll never keep everyone happy. Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. Please don't commit ports to the ports tree if you have not tested them! Hay cutting out part of the post to make things look different than they are is just wrong. As the thread explains the situation which you conveniently cut out. If my words were not clear. My port works at my end, but I also check that the comment port process does not get kinked messing up the port at the ports system end. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
using /etc/portsnap.conf
When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? ___ freebsd-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 csup broken?
On 01/02/13 10:08, Fbsd8 wrote: snip Still behind the 8 ball. No, I'm sorry but that's you. The new pkg is not part of the base in 9.1 and there is no ftp packages for 9.1 and the disc1.iso media I installed from has no packages. I don't know what crap you're talking, but if you would have installed the ports tree upon installation this wouldn't be an issue. Yes, you want to save space and cut down on back-up times, awesome goals, but you should have been following on the list and in the handbook where CVS has been deprecated (whether for good or bad, it's done) and portsnap/SVN are now the preferred methods. I'm fubarbed No, just too lazy to pull off a few extra steps for a one-off with portsnap or svn (which you will have to compile yourself, I'm afraid, though maybe someone will make a package for ya) Now I just had a port I maintain committed yesterday and I have no way to test it to verify the port is working. And? Pull it in with svn. I use svn to keep tabs on tk85 (and I only pull in tk85) in my user folder and I use svn to update my ports tree nightly. And doing a portsnap which may not contain my updated port for a few days if ever until all the other problem are addressed. portsnap shouldn't be affected by the pkgbeta site being down, someone else with more knowledge on the subject should feel free to correct me. This 9.1 release was released prematurely. It has more problems them 5.0 had which had a re-release 2 weeks later to fix problems. Prematurely? Depending on what source you go to it's at least two months behind. This is BAD public relations for FreeBSD. Now there is some FUD for ya. -- Yours in Christ, Joseph A Nagy Jr Whoever loves instruction loves knowledge, But he who hates correction is stupid. -- Proverbs 12:1 Emails are not formal business letters, whatever businesses may want. Original content CopyFree (F) under the OWL http://owl.apotheon.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: Newbie question about freebsd-update: single user mode is not needed anymore?
Well, I understand your concern. I've been using the freebsd-update method since several years now and mostly remotely. I've never encounter a problem. I haven't recompiled everything many times as I didn't really found a tangible advantage in this method but I've never thought about this. I believe some developer around here can provide you a neat explanation about that (which is going to be interesting to know). Strictly about your concern I believe whatever way you use for your upgrade you CANNOT be 100% sure that your upgrade will go smoothly and things like loosing control of your remote box will not happen. Even though jumping from close releases 9.0 = 9.1 is a low risk upgrade, a console access to your remote server (via terminal server/KVM/other) is imperative in these cases to avoid the worst. On Mon, 2012-12-31 at 16:50 +0100, Jose Garcia Juanino wrote: El lunes 31 de diciembre a las 16:27:44 CET, ASV escribió: Hi Jose, with the freebsd-update method you don't need to pass through the make installworld as it's a binary patch/upgrade system. Using freebsd-update upgrade -r 9.1-RELEASE for example allows you to get your system patched directly without recompiling the kernel and the userland but getting binary patches from the repo and applying these directly on your system. Check the following page for a more detailed explanation and be aware that upgrading your ports/packages is required every time you upgrade your kernel to a major version (which would be your case). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Happy new year. Thanks for your response. The freebsd-update upgrade method is: 1- freebsd-update install # will install a new kernel and modules 2- reboot in multi user 3- freebsd-update install # will install new userland 4- reboot in multi user The src upgrade method is: 1- make installkernel # will install a new kernel 2- reboot in single user 3- make installworld # will install a new userland 4- reboot in multiuser I think that the third step is essentially the same in both methods: it will install a new userland. But the second one require to be ran in single user, and the first one does not. Why? My unique concern is that step 2 in freebsd-update method goes smootly: it will boot kernel in 9.1-RELEASE but userland in 9.0-RELEASE. If the system hangs giving up the net or other essential service, I will not be able to reach the computer via ssh. Regards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
just a curiosity about auth.conf
Good afternoon and happy new year to everybody. I'm just curious about auth.conf. According to the detailed release notes (http://www.freebsd.org/releases/9.1R/relnotes-detailed.html): auth.conf(5) has been removed because it was deprecated years ago.[r238481] but according to the man pages online AUTH.CONF(5) of FBSD9.0-RELEASE: auth.conf contains various attributes important to the authentication code, most notably crypt(3) for the time being. This documentation will be updated as the /etc/auth.conf file, which is very new, evolves.. How can something deprecated years ago being new and evolving quickly enough to require further doc updates? Am I missing something? :) ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
--On January 2, 2013 6:45:50 PM +0100 andreas scherrer ascher...@gmail.com wrote: Hi This can be considered a follow up to the message How to keep freebsd-update from trashing custom kernel? sent to this list by Brett Glass on August 13th 2012 (see [1]). Unfortunately there is no solution to the problem in that thread (or I cannot see it). I am running currently running 9.0-RELEASE-p4 and freebsd-update recommends to update to p5. It states: - The following files will be updated as part of updating to 9.0-RELEASE-p5: /boot/kernel/kernel snip - And from experience this is what it will do: replace /boot/kernel/kernel which is my custom kernel with a GENERIC kernel. As it seems that freebsd-update works by comparing a hash of /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ (see [3]). So why is freebsd-update going to overwrite my custom kernel? And how can I prevent it from doing so? Read man (5) freebsd-update.conf. Particularly the COMPONENTS portion that explains how to update world without changing kernel. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-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: Newbie question about freebsd-update: single user mode is not needed anymore?
For some reason my email hasn't apparently been delivered so I'm re-sending it. From: ASV a...@inhio.eu To: Jose Garcia Juanino jjuan...@gmail.com Cc: freebsd-questions@freebsd.org Subject:Re: Newbie question about freebsd-update: single user mode is not needed anymore? Date: Mon, 31 Dec 2012 17:19:19 +0100| Well, I understand your concern. I've been using the freebsd-update method since several years now and mostly remotely. I've never encounter a problem. I haven't recompiled everything many times as I didn't really found a tangible advantage in this method but I've never thought about this. I believe some developer around here can provide you a neat explanation about that (which is going to be interesting to know). Strictly about your concern I believe whatever way you use for your upgrade you CANNOT be 100% sure that your upgrade will go smoothly and things like loosing control of your remote box will not happen. Even though jumping from close releases 9.0 = 9.1 is a low risk upgrade, a console access to your remote server (via terminal server/KVM/other) is imperative in these cases to avoid the worst. On Mon, 2012-12-31 at 16:50 +0100, Jose Garcia Juanino wrote: El lunes 31 de diciembre a las 16:27:44 CET, ASV escribió: Hi Jose, with the freebsd-update method you don't need to pass through the make installworld as it's a binary patch/upgrade system. Using freebsd-update upgrade -r 9.1-RELEASE for example allows you to get your system patched directly without recompiling the kernel and the userland but getting binary patches from the repo and applying these directly on your system. Check the following page for a more detailed explanation and be aware that upgrading your ports/packages is required every time you upgrade your kernel to a major version (which would be your case). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Happy new year. Thanks for your response. The freebsd-update upgrade method is: 1- freebsd-update install # will install a new kernel and modules 2- reboot in multi user 3- freebsd-update install # will install new userland 4- reboot in multi user The src upgrade method is: 1- make installkernel # will install a new kernel 2- reboot in single user 3- make installworld # will install a new userland 4- reboot in multiuser I think that the third step is essentially the same in both methods: it will install a new userland. But the second one require to be ran in single user, and the first one does not. Why? My unique concern is that step 2 in freebsd-update method goes smootly: it will boot kernel in 9.1-RELEASE but userland in 9.0-RELEASE. If the system hangs giving up the net or other essential service, I will not be able to reach the computer via ssh. Regards ___ freebsd-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: Newbie question about freebsd-update: single user mode is not needed anymore?
Hi Jose, with the freebsd-update method you don't need to pass through the make installworld as it's a binary patch/upgrade system. Using freebsd-update upgrade -r 9.1-RELEASE for example allows you to get your system patched directly without recompiling the kernel and the userland but getting binary patches from the repo and applying these directly on your system. Check the following page for a more detailed explanation and be aware that upgrading your ports/packages is required every time you upgrade your kernel to a major version (which would be your case). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html Happy new year. On Mon, 2012-12-31 at 13:13 +0100, Jose Garcia Juanino wrote: Hi, I am planning to upgrade from FreeBSD 9.0-RELEASE to FreeBSD-9.1-RELEASE. With upgrade source method, it is always needed to do the make installworld step in single user mode. But it seems to be that single user is not required with freebsd-update method, in the second freebsd-update install. Someone could explain the reason? Am I misunderstanding something? Can I run the upgrade enterely by mean a ssh connection in a safe way, or will I need a serial console? Best regards, and excuse my poor english. ___ freebsd-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: using /etc/portsnap.conf
On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
The confusion comes from the fact that the original behavior of freebsd-update was NOT to update the kernel binaries if a custom kernel was detected. FYI my /etc/freebsd-update.conf has # Components of the base system which should be kept updated. #Components src world kernel Components src world ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
on 2.1.13 19:15 Paul Schmehl said the following: --On January 2, 2013 6:45:50 PM +0100 andreas scherrer And from experience this is what it will do: replace /boot/kernel/kernel which is my custom kernel with a GENERIC kernel. As it seems that freebsd-update works by comparing a hash of /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ (see [3]). So why is freebsd-update going to overwrite my custom kernel? And how can I prevent it from doing so? Read man (5) freebsd-update.conf. Particularly the COMPONENTS portion that explains how to update world without changing kernel. Thanks for pointing this out. I might change my freebsd-update.conf to not update the kernel. But still I believe this to be more of a kludge than a solution: in my opinion the handbook suggests that a custom kernel should be detected and left alone. But at the same time a GENERIC kernel in /boot/GENERIC should be patched. http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html - However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. - Furthermore if I remove the kernel option from the COMPONENTS in freebsd-update.conf I think I will not get the kernel source patches anymore, right? Which in turn means I have to get them via some other mechanism, no? From the same link as above to the handbook: - Unless the default configuration in /etc/freebsd-update.conf has been changed, freebsd-update will install the updated kernel sources along with the rest of the updates. - I think something does not add up here but I can't get my head around it (yet?). ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
On Wed, Jan 2, 2013 at 11:18 AM, andreas scherrer ascher...@gmail.comwrote: This is no longer true, though it was true at the time that was written... - However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. This is no longer true, though it was true at the time - Furthermore if I remove the kernel option from the COMPONENTS in freebsd-update.conf I think I will not get the kernel source patches anymore, right? Which in turn means I have to get them via some other mechanism, no? No. If you have Components src world you'll get all sources - which you want, presumably, since /usr/src/sys changes are sometimes motivated by security vulnerabilities.. - M ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
--On January 2, 2013 8:18:38 PM +0100 andreas scherrer ascher...@gmail.com wrote: on 2.1.13 19:15 Paul Schmehl said the following: --On January 2, 2013 6:45:50 PM +0100 andreas scherrer And from experience this is what it will do: replace /boot/kernel/kernel which is my custom kernel with a GENERIC kernel. As it seems that freebsd-update works by comparing a hash of /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ (see [3]). So why is freebsd-update going to overwrite my custom kernel? And how can I prevent it from doing so? Read man (5) freebsd-update.conf. Particularly the COMPONENTS portion that explains how to update world without changing kernel. Thanks for pointing this out. I might change my freebsd-update.conf to not update the kernel. But still I believe this to be more of a kludge than a solution: in my opinion the handbook suggests that a custom kernel should be detected and left alone. But at the same time a GENERIC kernel in /boot/GENERIC should be patched. http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html - That needs to be updated. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. - Furthermore if I remove the kernel option from the COMPONENTS in freebsd-update.conf I think I will not get the kernel source patches anymore, right? Which in turn means I have to get them via some other mechanism, no? See UpdateIfUnmodified in the man page. You can specify a regex pattern that prevents the kernel from being modified but still downloads the sources. Or you can simply pull source from svn, which I think would be my preferred method. Once you've made the first pull, you can use svn to pull all the kernel updates subsequent to that first pull and then buildkernel as you normally do. From the same link as above to the handbook: - Unless the default configuration in /etc/freebsd-update.conf has been changed, freebsd-update will install the updated kernel sources along with the rest of the updates. - I think something does not add up here but I can't get my head around it (yet?). The Handbook is out of date. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
--On January 2, 2013 1:46:25 PM -0600 Paul Schmehl pschmehl_li...@tx.rr.com wrote: --On January 2, 2013 8:18:38 PM +0100 andreas scherrer ascher...@gmail.com wrote: on 2.1.13 19:15 Paul Schmehl said the following: --On January 2, 2013 6:45:50 PM +0100 andreas scherrer And from experience this is what it will do: replace /boot/kernel/kernel which is my custom kernel with a GENERIC kernel. As it seems that freebsd-update works by comparing a hash of /boot/kernel/kernel with the GENERIC kernel's hash I checked the md5 and sha1 hash of /boot/kernel/kernel and /boot/GENERIC/kernel. They differ (see [3]). So why is freebsd-update going to overwrite my custom kernel? And how can I prevent it from doing so? Read man (5) freebsd-update.conf. Particularly the COMPONENTS portion that explains how to update world without changing kernel. Thanks for pointing this out. I might change my freebsd-update.conf to not update the kernel. But still I believe this to be more of a kludge than a solution: in my opinion the handbook suggests that a custom kernel should be detected and left alone. But at the same time a GENERIC kernel in /boot/GENERIC should be patched. http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html - That needs to be updated. However, freebsd-update will detect and update the GENERIC kernel in /boot/GENERIC (if it exists), even if it is not the current (running) kernel of the system. - Furthermore if I remove the kernel option from the COMPONENTS in freebsd-update.conf I think I will not get the kernel source patches anymore, right? Which in turn means I have to get them via some other mechanism, no? See UpdateIfUnmodified in the man page. You can specify a regex pattern that prevents the kernel from being modified but still downloads the sources. I wasn't thinking when I wrote this. Freebsd-update pulls *binary* copies of files, so you're not ever going to get the src files to rebuild your kernel from freebsd-update. You need to pull those in using svn. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead. Thomas Jefferson There are some ideas so wrong that only a very intelligent person could believe in them. George Orwell ___ freebsd-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-update patches custom /boot/kernel/kernel which it should not
On 02/01/2013 20:55, Paul Schmehl wrote: I wasn't thinking when I wrote this. Freebsd-update pulls *binary* copies of files, so you're not ever going to get the src files to rebuild your kernel from freebsd-update. You need to pull those in using svn. Not so. Take a look at /etc/freebsd-update.conf -- if you have 'src' listed as one of the Components, freebsd-update will keep your /usr/src up to date. Primarily this is intendend for people that want to do binary updates of userland, but compile their own kernels for particular device support or whatever reason. However there's no reason why you couldn't just use freebsd-update just to grab system sources, and them update by building and installing world. If you want to track a release brance, and you don't intend to do any development work on the sources, then freebsd-update is going to be a lot more efficient for you than SVN. Outside that particular audience, however, svn rules. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: using /etc/portsnap.conf
Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Upgrading from 9.0-STABLE to 9.1-RELEASE with freebsd-update?
I've used STABLE for years, but with csup going away, I don't want to deal with adding extra packages, and keeping them unbroken, just to stay up date. Running freebsd-update doesn't work for people running STABLE, and I'm not sure freebsd-update will work properly anyway if I compile world for myself. What's the best way to switch from running STABLE to running the RELEASE channel? ___ freebsd-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: using /etc/portsnap.conf
On Thu, 03 Jan 2013 00:43:36 +0100, Fbsd8 fb...@a1poweruser.com wrote: Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. Just guessing: Try without the spaces at the beginning of the REFUSE lines? Michael ___ freebsd-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 boot alternate installation?
I have a system that boots 9.0+patches (claims to be 9.1-PRERELEASE but that's a stretch in this case) off an ssd on sata0 - I needed some mfi patches. Now that mfi is working, I have a raid1 pair on the mfi controller, and I've unpacked 9.1-RELEASE onto it using bsdinstall. Now, the crappy PERC5 and the AMI BIOS in my little AMD mobo don't really see eye to eye and I've had a lot of trouble coaxing it to boot from the RAID volume (the RAID card initialises late it seems). I'm happy to keep /boot on the SATA SSD for now. Is there a straightforward way to configure (the menus to) boot from 9.1? I'm happy enough to rename /boot on the SSD and copy over the contents from 9.1 (really the old 9.0+ system is there as insurance for the moment). Is the simplest mechanism to do that and override rootdev in loader.conf? It seems that there are a number of variables with /boot/... paths so its not so easy to switch between (say) /boot90 and /boot91. ___ freebsd-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: using /etc/portsnap.conf
Michael Ross wrote: On Thu, 03 Jan 2013 00:43:36 +0100, Fbsd8 fb...@a1poweruser.com wrote: Walter Hurry wrote: On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? It will use /etc/portsnap.conf by default. No need for -f unless you need to use a different config file. By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. My /ect/portsnap.conf looks like this. # $FreeBSD: src/etc/portsnap.conf,v 1.5.2.1.2.1 2009/10/25 01:10:29 kensmith Exp $ # Default directory where compressed snapshots are stored. # WORKDIR=/var/db/portsnap # Default location of the ports tree # (target for update and extract). # PORTSDIR=/usr/ports # Server or server pool from which to fetch updates. You can change # this to point at a specific server if you want, but in most cases # using a nearby server won't provide a measurable improvement in # performance. SERVERNAME=portsnap.FreeBSD.org # Trusted keyprint. Changing this is a Bad Idea unless you've received # a PGP-signed email from security-offi...@freebsd.org telling you to # change it and explaining why. KEYPRINT=9b5feee6d69f170e3dd0a2c8e469ddbd64f13f978f2f3aede40c98633216c330 # List of INDEX files to build and the DESCRIBE file to use for each #INDEX INDEX-6 DESCRIBE.6 #INDEX INDEX-7 DESCRIBE.7 INDEX INDEX-8 DESCRIBE.8 # Example of ignoring parts of the ports tree. If you know that you # absolutely will not need certain parts of the tree, this will save # some bandwidth and disk space. See the manual page for more details. # # WARNING: Working with an incomplete ports tree is not supported and # can cause problems due to missing dependencies. If you have REFUSE # directives and experience problems, remove them and update your tree # before asking for help on the mailing lists. # REFUSE arabic chinese french german hebrew hungarian japanese REFUSE korean polish portuguese russian ukrainian vietnamese # # The following is complete list of all the port categories . # # REFUSE accessibility archivers astro audio benchmarks biology cad # REFUSE comms converters databases deskutils devel dns editors emulators # REFUSE finance ftp games graphics irc java lang mail math mbone misc # REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print # REFUSE science security shells textproc www # REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers # REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils # REFUSE accessibility archivers astro audio benchmarks biology cad REFUSE comms converters databases deskutils devel dns editors emulators REFUSE finance ftp games graphics irc java lang mail math mbone misc REFUSE multimedia net net-im net-mgmt net-p2p news palm ports-mgmt print REFUSE science security shells textproc www REFUSE x11 x11-clocks x11-drivers x11-fm x11-fonts x11-servers REFUSE x11-themes x11-toolkits x11-wm # REFUSE sysutils This should only populate /usr/ports/sysutils But its not being used because everything is being populated in /usr/ports. I do portsnap fetch followed by portsnap extract What am I doing wrong here? I even tried portsnap extract -f /etc/portsnap.conf with no joy. Just guessing: Try without the spaces at the beginning of the REFUSE lines? Thanks that was it. Sometimes your to close to the trees to see the forest. ___ freebsd-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: using /etc/portsnap.conf
On Wed, 02 Jan 2013 20:06:47 -0500, Fbsd8 wrote: Thanks that was it. Sometimes your to close to the trees to see the forest. But you wouldn't have needed any REFUSE lines if you had followed my suggestion and just extracted the ports you wanted. ___ freebsd-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: using /etc/portsnap.conf
Walter Hurry wrote: On Wed, 02 Jan 2013 20:06:47 -0500, Fbsd8 wrote: Thanks that was it. Sometimes your to close to the trees to see the forest. But you wouldn't have needed any REFUSE lines if you had followed my suggestion and just extracted the ports you wanted. After doing portsnap fetch for the first time followed by portsnap extract mis/ytree will create an /usr/ports directory empty of the files and directories needed for the make command to function. But yes the /usr/ports/misc/ytree port will be there. But having a /etc/portsnap.conf with REFUSE statements for all of the ports categories will populate /usr/port directory with only the files and directories required for the make command to function correctly. In csup this was called the base category which could be selected separately in the same way other ports could be selected separately. But it's good to know that I can duplicate what I was doing with csup now with portsnap to have a ports tree trimmed to only the things required by make and the few major ports that I needed to recompile to change the defaults used in the packaged versions. And to address the dependents question. I used pkg_add -r to install the dependents and the make install compiled without any problems. So thanks for your pointer to portsnap extract mis/ytree. It took some testing to figure out things because the man portsnap is not very clear about what is really happening. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
somewhat OT ... in parts
guys,
it was bill joy and friends who clued me in on how-to use the
vi that he was writing in the late 70's. I've been stuck on that
editor--or VIIM in recent years. Bill's original editor became
COPYRIGHT of UNIX {TM}, and of course you just didnt mess with
the telephone company. I was glad when keith bostic wrote an
exact clone of bill joy's editor. I'm still getting used to vim.
one reason ive stuck with vim-as-vi was of the colors that vim
defaults to. I'v fought the dark/crap/puke brown /search
color that seems to be the default on my linux desktop. it's hard
to see my block cursor when I search for words. und`zo, today I
spend a couple hours tracking down this color feature in vim. was
pleased to find that there was a blue-tone color set. my joints
are complaining so I'll ask if any of you can give me the right
terms to google for. I'd like to find a lighter blue or play
around with the colors. {am assuming that vim is the same across
the linux and berkeley distributions.}
thanks in advance for a few url's.
gary
PS: OH; the offtopic thing. I'm done, or =very= close with my
voice by computer program. It's in C with gtk and AFAICT works
only on linux. ive got a few months of cleaning up before
release 0.51 will be finished. in the FBSD world, this would
fit into the accessibility directory. now, the speech-impaired
who can type will be able to communicate with anyone. VBC requires
espeak and gvim.
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
Twenty-six years of service to the Unix community.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
audio/baresip on FreeBSD 9
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
However, there is no sound.
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
There doesn't seem to be much documentation anywhere on the Internet for
baresip.
My config file (~/.baresip/config) is:
/* Begin ~/.baresip/config */
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device/dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/audio0.0
audio_srate 8000-48000
audio_channels 1-2
#audio_aec_length 128 # [ms]
# Video
video_dev
video_size 352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports 1-2
#rtp_bandwidth 512-1024 # [kbit/s]
rtcp_enable yes
rtcp_muxno
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
module stdio.so
module cons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
module g711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
module avcodec.so
#module vpx.so
# Video source modules
#module avformat.so
#module v4l.so
#module v4l2.so
# Video display modules
#module sdl.so
#module x11.so
# Media NAT modules
#module stun.so
#module turn.so
#module ice.so
# Media encoding modules
#module srtp.so
# Other modules
#module natbd.so
#--
# Module parameters
# Speex codec parameters
speex_quality 7 # 0-10
speex_complexity7 # 0-10
speex_enhancement 0 # 0-1
speex_vbr 0 # Variable Bit Rate 0-1
speex_vad 0 # Voice Activity Detection 0-1
speex_agc_level 8000
# NAT Behavior Discovery
#natbd_server creytiv.com
#natbd_interval 600 # in seconds
/* End ~/.baresip/config */
/* uname -a */
FreeBSD peace 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #4 r244062: Mon Dec
10 17:56:25 CST 2012 root@peace:/usr/obj/usr/src/sys/PEACE i386
Thanks.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Solar Collector Windows - US Air Force Approved
Solar Window Solar Collecter Windows (Interior Mounted) - University Tested and Solar Rejector Windows all in one A 4' X 4' In'Flector window insulator can produce as much heat as a 600 watt electrical heater per sunlight hour and reflect up to 72% of the room heat back into the room! During the summer, our product reduces air infiltration up to 71%, stops solar heat gain up to 65%, and blocks up to 90% of harmful UV rays for such customers as General Motors and numerous Canadian Embassies! We would like you to consider offering your customers truly energy efficient window insulators, roller blinds, vertical blinds, or sliders. At the same time, we would like you to be a supplier, distributor or manufacturer by adding another product line for your customers to consider! We have been tested by two major universities with outstanding results and we are located in the United States, Canada, Mexico, the UK, Ireland, Italy, Pakistan, Hong Kong, Dubai, and Australia! Energy Efficiency Done Right invites you to a webinar with information on chances in manufacturing or being a dealer of In'Flector See Through Radiant Barrier Window and Skylight Insulators. The webinar will take place on Tuesday, January 22nd at 10:00AM (CST) The energy efficiency industry is projected to be a 40 billion dollar industry by the year 2012, and a good portion of those funds should be dedicated to improving the least energy efficient envelope component-the windows. If you need more information please reply to this email. If you want to be a part of this webinar please email back this information- your name, your business, your location, the market you desire to serve, your email and a phone number. This is a true groundfloor chance in a fast growing industry. Thank you for your consideration Unsubscribe by email Inflector Window Insulators 10854 Lake Path Drive San Antonio, TX 78217 ___ freebsd-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: using /etc/portsnap.conf
On Wed, 02 Jan 2013 12:27:41 -0500, Fbsd8 wrote: When issuing the portsnap command will it automatically read the /etc/portsnap.conf file or is the -f option mandatory? Judging from man portsnap, the file will be read automatically at start unless you specify a -f diifferent file. -f conffile Read the configuration from conffile. (default: /etc/portsnap.conf) See man portsnap for reference. -- 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: using /etc/portsnap.conf
On Wed, 2 Jan 2013 18:24:14 + (UTC), Walter Hurry wrote: By the way, in answer to your question in another thread, you don't have to extract the whole tree if you don't want to. Use 'portsnap fetch' the first time around, and then portsnap extract the port you want. See 'man portsnap', and remember to cater for the dependencies. This is correct and works in many many situations. However, there has been a saying which states that only a complete ports tree is guaranteed to work properly; I think this basically refers to the availability of dependencies and turtles all the way down, plus the top level files (such as /usr/ports/Makefile) and the Mk/ and Tools/ subtrees. -- 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: somewhat OT ... in parts
On Wed, 2 Jan 2013 18:53:05 -0800, Gary Kline wrote:
one reason ive stuck with vim-as-vi was of the colors that vim
defaults to. I'v fought the dark/crap/puke brown /search
color that seems to be the default on my linux desktop. it's hard
to see my block cursor when I search for words. und`zo, today I
spend a couple hours tracking down this color feature in vim. was
pleased to find that there was a blue-tone color set. my joints
are complaining so I'll ask if any of you can give me the right
terms to google for. I'd like to find a lighter blue or play
around with the colors. {am assuming that vim is the same across
the linux and berkeley distributions.}
In case you're using gvim (a GUI enclosing for vim) you can
do the following: Load some text or source code, :syntax on,
then in the menu: Edit - Color Scheme, and pin the resulting
menu next to the editor window; click the different schemes
to check if one of the predefined 17 schemes looks usable to
you; when done, unpin the menu. This approach is just for
testing and looking around in the first place, not for
actual permanent use. :-)
PS: OH; the offtopic thing. I'm done, or =very= close with my
voice by computer program. It's in C with gtk and AFAICT works
only on linux. ive got a few months of cleaning up before
release 0.51 will be finished. in the FBSD world, this would
fit into the accessibility directory. now, the speech-impaired
who can type will be able to communicate with anyone. VBC requires
espeak and gvim.
There are both gvim and /usr/ports/audio/espeak in ports, and
Gtk is also in there. What would cause this software to refuse
working on FreeBSD?
--
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: Skype video chat?
El día Thursday, January 03, 2013 a las 08:03:42AM +0200, Ross escribió: Hello. Can you please recommend a webcam and microphone that will work in skype under FreeBSD? Hello, See http://wiki.freebsd.org/WebcamCompat matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | - No proprietary attachments phone: +49-170-4527211 | - Respect for open standards ___ freebsd-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: audio/baresip on FreeBSD 9
Hi,
El día Wednesday, January 02, 2013 a las 08:19:11PM -0800, Joseph Olatt
escribió:
I've been trying to get baresip to work on my FreeBSD 9.x laptop and
haven't had much success. I register successfully to callcentric.com and
it appears that I can connect and there is a stream of data coming
through based on the status display:
[0:00:08] audio=0/0 (bit/s) []
The display shows zero audio data!
However, there is no sound.
Have you tried the local audio loop with pressing the single letter 'a'?
Is anybody on the list successfully using baresip? If so, could they
please provide some pointers on how to get sound?
I'm attaching my config file which works fine; in your config file it
looks stange to me:
# Audio
audio_dev /dev/audio0.0
do you have such a device file '/dev/audio0.0'?
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
moduleg711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
#module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
you have no audio driver loaded, try 'oss.so'
Once you get the local loop working you could contact me off-list for my
SIP and try to call me.
HIH
matthias
--
Sent from my FreeBSD netbook
Matthias Apitz | - No system with backdoors like Apple/Android
E-mail: g...@unixarea.de | - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | - No proprietary attachments
phone: +49-170-4527211 | - Respect for open standards
#
# baresip configuration
#
#--
# Core
poll_method poll# poll, select, epoll ..
# Input
input_device/dev/event0
input_port
# SIP
sip_trans_bsize 128
#sip_listen 127.0.0.1:5050
# Audio
audio_dev /dev/dsp
audio_srate 8000-48000
audio_channels 1-2
#audio_aec_length 128 # [ms]
# Video
video_dev /dev/video0
video_size 352x288
video_bitrate 384000
video_fps 25
#video_selfview window # {window,pip}
# AVT - Audio/Video Transport
rtp_tos 184
#rtp_ports 1-2
rtp_ports 1024-1030
#rtp_bandwidth 512-1024 # [kbit/s]
rtcp_enable yes
rtcp_muxno
jitter_buffer_delay 5-10# frames
# Network
#dns_server 10.0.0.1:53
#--
# Modules
module_path /usr/local/lib/baresip/modules
# UI Modules
module stdio.so
module cons.so
#module evdev.so
# Audio codec Modules (in order)
#module g7221.so
#module g722.so
module g711.so
#module gsm.so
#module l16.so
#module speex.so
#module celt.so
#module bv32.so
# Audio filter Modules (in order)
# NOTE: AEC should be before Preproc
#module sndfile.so
#module speex_aec.so
#module speex_pp.so
#module speex_resamp.so
#module plc.so
# Audio driver Modules
module oss.so
#module alsa.so
#module portaudio.so
#module gst.so
# Video codec Modules (in order)
module avcodec.so
#module vpx.so
# Video source modules
module v4l2.so
#module avformat.so
#module v4l.so
# Video display modules
module x11.so
# modulesdl.so
# Media NAT modules
module stun.so
module turn.so
module ice.so
# Media encoding modules
#module srtp.so
# Other modules
#module natbd.so
#--
# Module parameters
# Speex codec parameters
speex_quality 7 # 0-10
speex_complexity7 # 0-10
speex_enhancement 0 # 0-1
speex_vbr 0 # Variable Bit Rate 0-1
speex_vad 0 # Voice Activity Detection 0-1
speex_agc_level 8000
#
