Re: FreeBSD make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 11/11/11 11:43 AM, Traiano Welcome wrote: Most recent suggestions from Damien Fleuriot: [root@snmp-proxy02 /usr/src]# cat /etc/make.conf SUP_UPDATE= yes SUP=/usr/bin/csup SUPFLAGS= -zgL 2 SUPHOST=cvsup2.za.freebsd.org SUPFILE=/etc/cvsup/stable-supfile PORTSSUPFILE= /etc/cvsup/ports-supfile DOCSUPFILE= /etc/cvsup/doc-supfile ENABLE_SUID_K5SU=YES # added by use.perl 2011-11-09 12:33:48 PERL_VERSION=5.10.1 I see the same compile issue with both variants of my make.conf. To clarify, my suggestion has to do with the way you run your updates. These variables in /etc/make.conf allow you to forgo the manual use of csup [args] , and instead use: cd /usr/src ; make update It is not intended as a fix to your build issues and should have no effect on them whatsoever. ___ freebsd-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 make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 11/11/11 11:53 AM, Polytropon wrote: On Fri, 11 Nov 2011 10:45:15 +, Traiano Welcome wrote: And I don't seem to have a src.conf anywhere on my filesystem ... Hmmm. You'll have to create it yourself (just like /etc/make.conf). See man src.conf for details. I can't see any odd variables in your /etc/make.conf I would suggest trying to update from 8.0 to 8.1 first, instead of 8.0 - 8.2 Please try this and see if you can successfully build the world. If you still can't, try updating from 8.0 to 8.0 (yes, I'm serious). See if you can build the 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 make buildworld fail: cc: Internal error: Killed: 9 (program cc1)
On 2011/11/14 11:25 AM, Damien Fleuriot m...@my.gd wrote: On 11/11/11 11:53 AM, Polytropon wrote: On Fri, 11 Nov 2011 10:45:15 +, Traiano Welcome wrote: And I don't seem to have a src.conf anywhere on my filesystem ... Hmmm. You'll have to create it yourself (just like /etc/make.conf). See man src.conf for details. I can't see any odd variables in your /etc/make.conf Me neither. This is a standard config I've used for hundreds of bsd machines (vms and real tin) so I doubt this has anything to do with ... Of course, source may change, requiring make.conf to change, but I'm spculating here :P I would suggest trying to update from 8.0 to 8.1 first, instead of 8.0 - 8.2 Currently testing this ... Please try this and see if you can successfully build the world. If you still can't, try updating from 8.0 to 8.0 (yes, I'm serious). See if you can build the 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 ___ freebsd-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: poppler-qt-0.16.7
On Monday 14 November 2011, n dhert wrote: Has anything been done to fix this? I don't believe it was already done: nothing changed in /usr/ports/UPDATING, also no instructions for portupgrade yet. I still get # pkg_version -VIL= poppler-qt-0.16.7 ! Comparaison failed # pkgdb -F Stale origin: 'graphics/poppler-qt': perhaps moved or obsoleted. Just pkg_delete poppler-qt-0.16.7 and everything will be fine providing you've updated kdegraphics3. It was a bit more of a problem for me. I'm using portmaster and it refused to continue with the rest of the upgrade until I'd deleted poppler-qt. -- Mike Clarke ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Default Samba port?
From: Robert Simmons rsimmo...@gmail.com To: freebsd-questions@freebsd.org Sent: Sunday, November 13, 2011 10:36 AM Subject: Re: Default Samba port? On Sun, Nov 13, 2011 at 7:37 AM, Peter Harrison four.harris...@googlemail.com wrote: Can anyone advise me the appropriate Samba port to install - the handbook refers to samba34, but I see samba35 and samba36 in in ports. This is for a home server, so I'm not necessarily looking for production standard, but something that just works on RELEASE-8.2 amd64. samba36 is the current stable version. The other two are kept for legacy compatibility. 35 and 34 are the last version in those branches. Don't worry about them. The handbook has not been updated for two major revisions of samba. This is a comment for the others on the list, not directly at you: maybe ports like this should have a directory samba that always points to the most recent stable version. Then the handbook would not need to be updated to reflect version changes like this. It would only need to be updated if the actual instructions change or become outdated? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org I second the motion. Then when you do something like whereis samba, it won't come back empty and force you to search in /usr/ports for the desired port directory. As for the original question, I'd install samba36, which is the latest port. The configuration is still the same as previous releases so go for the latest one. Samba has some security issues but it rocks as a file server for *nix machines. I've used it with great success to allow M$ clients to share files. I do not use it for print services however, only file sharing. ___ freebsd-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: 8.2-RELEASE-p4
It touches the kernel but you need to do make builkernel/make installkernel before uname -a shows 8.2-RELEASE-p4. Regards, Evalyn -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Matthew Seaman Sent: 12 November 2011 02:03 To: Robert Simmons Cc: freebsd-questions@freebsd.org Subject: Re: 8.2-RELEASE-p4 On 11/11/2011 21:03, Robert Simmons wrote: Note that if a security update is just to some userland programs, freebsd-update won't touch the OS kernel, so the reported version number doesn't change even though the update has been applied. In these sort of cases, it's not necessary to reboot, just to restart any long running processes (if any) affected by the update. The security advisory should have more detailed instructions about exactly what to do. (The -p2 to -p3 update was like this, but the -p3 to -p4 update definitely did affect the kernel so a reboot was necessary.) I'm not confident that you are correct here. See above. Either p3-p4 did not touch the kernel, or the OP has a legitimate question. Interesting. I based what I said on the text of the security advisories: http://security.freebsd.org/advisories/FreeBSD-SA-11:04.compress.asc http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc Specifically the 'Corrected:' section near the top. I think it's clear that FreeBSD-SA-11:04.compress (Corrected in 8.2-RELEASE-p3) doesn't involve anything in the kernel but FreeBSD-SA-11:05.unix (Corrected in 8.2-RELEASE-p4) is entirely within the kernel code. Except those advisories aren't telling the whole story. Lets look at r226023 in SVN. That's the revision quoted in the 11.05 advisory. The log for newvers.sh in http://svnweb.freebsd.org/base/releng/8.2/sys/conf/newvers.sh?view=logpathr ev=226023 says that the patches in RELEASE-p4 were not actually the security fix -- rather they fixed a problem revealed by the actual security fix, which was applied simultaneously with the patches in FreeBSD-SA-11:04.compress. 11.05 was committed in two blobs spanning -p3 and -p4. So, the good news is that if you have at least 8.2-RELEASE-p3 then you don't have any (known) security holes. However if you don't have the patches in 8.2-RELEASE-p4 then linux apps run under emulation will crash if they use unix domain sockets. The flash plugin for FireFox being the most prominent example as I recall. Now the updates for -p4 certainly should have touched the kernel, and certainly should have resulted in an updated uname string[*]. There should also be a note about -p4 in /usr/src/UPDATING. Starting to wonder if the -p4 patches are actually available via freebsd-update(8) -- could they have been omitted because it wasn't actually a security fix? Odd that no one would have commented in a whole month if so. Cheers, Matthew [*] strings /boot/kernel/kernel | grep '8\.2-' should give the same results as uname(1): if it's different then the running kernel is not the same as the one on disk... -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW ___ freebsd-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: Default Samba port?
Sorry for top posting - my 'phone makes it awkward. Thanks for the s= uggestion. What default package would be delivered in this way on 8.2-R? -- Peter Harrison _ On 13 Nov 2011 14:39, pete wright nomadlo= g...@gmail.com wrote: On Sun, Nov 13, 2011 at 4:37 AM, Pe= ter Harrison four.harris...@googlemail.com wrote: = Hello list, Can anyone advise me the appropriate Samb= a port to install - the handbook refers to samba34, but I see samba35 and s= amba36 in in ports. This is for a home server, so I'm not necessarily looki= ng for production standard, but something that just works on RELEASE-8.2amd64. your best bet may be to install a prebuilt p= ackage via: pgk_add -r samba that is unless you need som= e non-standard knobs tuned. -pete -- pete wright www.nycbug.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: Default Samba port?
Sorry for top posting - curse you 'phone mail client! OK that's exac= tly what I needed to know. Thanks. -- Peter Harrison _ On 13 Nov= 2011 15:37, Robert Simmons rsimmo...@gmail.com wrote: On Sun, Nov 13, 2011 at 7:37 AM, Peter Harrison four.harrisons= @googlemail.com wrote: Can anyone advise me the appropriate = Samba port to install - the handbook refers to samba34, but I see samba35 a= nd samba36 in in ports. This is for a home server, so I'm not necessarily l= ooking for production standard, but something that just works on RELEASE-= 8.2 amd64. samba36 is the current stable version. The other t= wo are kept for legacy compatibility. 35 and 34 are the last version= in those branches. Don't worry about them. The handbook has not be= en updated for two major revisions of samba. This is a c= omment for the others on the list, not directly at you: maybe ports l= ike this should have a directory samba that always points to the most= recent stable version. Then the handbook would not need to be updat= ed to reflect version changes like this. It would only need to be up= dated if the actual instructions change or become outdated? ___= freebsd-questions@freebs= d.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-= questions To unsubscribe, send any mail to freebsd-questions-unsubsc r...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
AUTO: KVVSN Murthy is out of the office. (returning 11/17/2011)
I am out of the office until 11/17/2011. In my obsence, please coordinate with Mr.KN Rao for my PET related activities. Note: This is an automated response to your message freebsd-questions Digest, Vol 389, Issue 1 sent on 11/14/2011 5:30:42 PM. This is the only notification you will receive while this person is away. Disclaimer This message contains legally privileged and/or confidential information. If you are not the intended recipient(s), or employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to login to my jail from host itself (normal user)
On Sat, Nov 12, 2011 at 9:54 PM, masayoshi rocksta...@y7mail.com wrote: Hi,I am masayoshi. If you have enough time, please answer my question. I must adduser Ayumi as normal user. After adding her in jail, I add her in host. Then I type the following command: Correct me if I'm wrong but I think you are confusing FreeBSD Jails with a Jail Shell. The name FreeBSD Jail is confusing because it's based on advanced chrooting but it's really not intended for jailshailing but rather pseudo-virtualization. Maybe you should look at jailkit or something like that. The other option is to create a FBSD Jail only for her, but again I think this is not the right tool for the job. Jail Shell is what you're looking for. -- Alejandro Imass ___ freebsd-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: 8.2-RELEASE-p4
Do you anticipate the release of an fix/update that will allow systems to be patched to -p4 or later via freebsd-update? -Tom Carpenter On 11/14/2011 05:25 AM, Evalyn wrote: It touches the kernel but you need to do make builkernel/make installkernel before uname -a shows 8.2-RELEASE-p4. Regards, Evalyn -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Matthew Seaman Sent: 12 November 2011 02:03 To: Robert Simmons Cc: freebsd-questions@freebsd.org Subject: Re: 8.2-RELEASE-p4 On 11/11/2011 21:03, Robert Simmons wrote: Note that if a security update is just to some userland programs, freebsd-update won't touch the OS kernel, so the reported version number doesn't change even though the update has been applied. In these sort of cases, it's not necessary to reboot, just to restart any long running processes (if any) affected by the update. The security advisory should have more detailed instructions about exactly what to do. (The -p2 to -p3 update was like this, but the -p3 to -p4 update definitely did affect the kernel so a reboot was necessary.) I'm not confident that you are correct here. See above. Either p3-p4 did not touch the kernel, or the OP has a legitimate question. Interesting. I based what I said on the text of the security advisories: http://security.freebsd.org/advisories/FreeBSD-SA-11:04.compress.asc http://security.freebsd.org/advisories/FreeBSD-SA-11:05.unix.asc Specifically the 'Corrected:' section near the top. I think it's clear that FreeBSD-SA-11:04.compress (Corrected in 8.2-RELEASE-p3) doesn't involve anything in the kernel but FreeBSD-SA-11:05.unix (Corrected in 8.2-RELEASE-p4) is entirely within the kernel code. Except those advisories aren't telling the whole story. Lets look at r226023 in SVN. That's the revision quoted in the 11.05 advisory. The log for newvers.sh in http://svnweb.freebsd.org/base/releng/8.2/sys/conf/newvers.sh?view=logpathr ev=226023 says that the patches in RELEASE-p4 were not actually the security fix -- rather they fixed a problem revealed by the actual security fix, which was applied simultaneously with the patches in FreeBSD-SA-11:04.compress. 11.05 was committed in two blobs spanning -p3 and -p4. So, the good news is that if you have at least 8.2-RELEASE-p3 then you don't have any (known) security holes. However if you don't have the patches in 8.2-RELEASE-p4 then linux apps run under emulation will crash if they use unix domain sockets. The flash plugin for FireFox being the most prominent example as I recall. Now the updates for -p4 certainly should have touched the kernel, and certainly should have resulted in an updated uname string[*]. There should also be a note about -p4 in /usr/src/UPDATING. Starting to wonder if the -p4 patches are actually available via freebsd-update(8) -- could they have been omitted because it wasn't actually a security fix? Odd that no one would have commented in a whole month if so. Cheers, Matthew [*] strings /boot/kernel/kernel | grep '8\.2-' should give the same results as uname(1): if it's different then the running kernel is not the same as the one on disk... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
geli + journal
hi Is it possible to create journaled FS which is crypted with geli? I can create crypted or journaled FS, but it is complicated to me to create both in time, can you help me clue? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Stuck between current and 9 release.
I was running current (before 10) last month, had a health emergency and when I could check the server current was 10. I ereased all sources and switched all my csup files to release and begin building a new world daily with no problems to be sure all was well. ( probably a mistake ). Port upgrades were building fine with portmaster so I just decided to reboot to see if all was well.( Dumb ) it wasn't, (Murphy's Law), the machine won't boot. Rather than a spinning slash (/) a single one and it hangs. I have been looking for an amd 64 version of a release snapshot and haven't found anything close. I have no idea why it doesn't even try to boot. I have tried all the loader options and get nowhere. I could use any suggestions especially since I don't even have a amd64 snapshot other than old ones to do a reinstall especially if there is a problem with the release. Thanks, ed P.S. If this should be on another list please let me know. If there is an AMD RELEASE 9 snap somewhere other than what is in the handbook. Anything would be great. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
9.0-RC1 Perl tests fail
Thanks again for info about disabling 1394 :-) Easy. Now here's a harder one: Installing any version of Perl; I found I can install perl5.8, but my 8.2-RELEASE has a perfectly good Perl5.10. Each of my 9.0 Perl attempts perl5.10, 13 and 14 has Failed tests. Such a vast number of tests with so little info as to which feature my 98 or so failed tests comes from! CPAN shows its latest release as perl5-0.08 ! I suspect the Perl versions I've tried may be uniquely numbered for FreeBSD. Any help? Thanks for any help! Chuck Bacon -- c...@cape.com ABHOR SECRECY -- DEFEND PRIVACY ___ freebsd-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: geli + journal
On Mon, 14 Nov 2011 21:57:28 +0200 Коньков Евгений wrote: hi Is it possible to create journaled FS which is crypted with geli? I can create crypted or journaled FS, but it is complicated to me to create both in time, can you help me clue? You have to encrypt first and then create the gjournal device on the .eli device so you end-up with device that ends in .eli.journal. However, FreeBSD 9 supports journaled soft-updates which is much faster than full data journalling, and it can be enabled on existing filesystems. ___ freebsd-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[2]: geli + journal
R On Mon, 14 Nov 2011 21:57:28 +0200 R Коньков Евгений wrote: hi Is it possible to create journaled FS which is crypted with geli? I can create crypted or journaled FS, but it is complicated to me to create both in time, can you help me clue? R You have to encrypt first and then create the gjournal device on R the .eli device so you end-up with device that ends in .eli.journal. R However, FreeBSD 9 supports journaled soft-updates which is much faster R than full data journalling, and it can be enabled on existing R filesystems. I catch idea, but some question: in this situation .eli.journal journal device will not be encrypted? can you describe how data flow will be? -- С уважением, Коньков mailto:kes-...@yandex.ru ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: apps to display cpu temp
On 11/12/11 18:02, Polytropon wrote: On Sat, 12 Nov 2011 18:19:57 -0800, Edward Martinez wrote: Hi, I have a Pentium 4 and i have been trying to get coretemp and sysctl hw.acpi.thermal.tz0.temperature to display my Cpu temperture , however i have not had any luck using them Are there any other apps perhaps from ports that reports CPU temp? I've been using the port xmbmon for that, in combination with device smbus device iicbus device iicsmb device iicbb device iic in the kernel configuration file - on a Pentium 4 system. I haven't tried the sysctl method, because xmbmon did work out of the box. :-) You can also use mbmon for text output. Here's an example from ~/.xinitrc calling xmbmon: xmbmon -g 150x100+0+897 \ -tmin 20.0 -tmax 70.0 \ -cmtmb CPU -cltmb blue \ -cmtcpu CS -cltcpu cyan \ -cmtcs SYS -cltcs green \ -vmin 2.0 -vmax 3.0 -cmvc V -clvc red Depending on the sensor installation of your particular system, check if the different values do match the hardware. Maybe check from within your CMOS setup for reference values. Thanks!, Even though mbmon is about 10 degrees off from what the BIOS is reporting. I'm still a happycamper. I have a question, is it supposed to be device iichsmb or device iicsmb like you have listed? ___ freebsd-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: geli + journal
On Tue, 15 Nov 2011 00:06:00 +0200 Коньков Евгений wrote: catch idea, but some question: in this situation .eli.journal journal device will not be encrypted? can you describe how data flow will be? The journal is encrypted unless you choose to put it on a separate non-encrypted device. In principle the data is encrypted into the journal, decrypted from the journal and then re-encrypted into its final location. In practice I've found that in file copying between disks, writing uses about twice as much cpu time as reading, so maybe the decryption from the journal can be avoided by caching. ___ freebsd-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: apps to display cpu temp
On Mon, 14 Nov 2011 15:16:49 -0800, Edward Martinez wrote: Thanks!, Even though mbmon is about 10 degrees off from what the BIOS is reporting. I'm still a happycamper. I had a similar observation with my P4 system: CPU temp would always flatline at 60 deg. C. I have a question, is it supposed to be device iichsmb or device iicsmb like you have listed? The example listed is from my kernel configuration of that particular P4 system, where it _worked_ properly. I had inserted device iicsmb as per kernel configuration notes. The OS in question was 7-STABLE. -- 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
