Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
kern.securelevel: -1 and the permessions on /bin and / is the correct :[ 2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]: On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote: My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Could be caused by some filesystem mount options you've got set, maybe incorrect permissions on /bin (no execute bit?), or possibly a secure runlevel setting (which I believe was the cause of your last issue you reported here). -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
I do chflags noschg /bin and its work :) 2007/6/15, ExTaZyTi [EMAIL PROTECTED]: kern.securelevel: -1 and the permessions on /bin and / is the correct :[ 2007/6/15, Jeremy Chadwick [EMAIL PROTECTED]: On Fri, Jun 15, 2007 at 12:07:40AM +0300, ExTaZyTi wrote: My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Could be caused by some filesystem mount options you've got set, maybe incorrect permissions on /bin (no execute bit?), or possibly a secure runlevel setting (which I believe was the cause of your last issue you reported here). -- | Jeremy Chadwickjdc at parodius.com| | Parodius Networking http://www.parodius.com/| | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pf(4) + fetch(1) + http://ftp.gnu.org
On Friday 15 June 2007, Vlad GURDIGA wrote: On 15/06/07, Chuck Swiger [EMAIL PROTECTED] wrote: On Jun 14, 2007, at 2:24 PM, Vlad GURDIGA wrote: Presumably you want to make sure that fetch(1) is using: FTP_PASSIVE_MODEIf set to anything but `no', forces the FTP code to use passive mode. Just in case, I have checked my environment and FTP_PASSIVE_MODE is set to yes. I'm saying just in case because the downloads were from http://ftp.gnu.org;, not from ftp://ftp.gnu.org;, I mean the HTTP protocol was used, not FTP. Hrm, missed that part, or perhaps just ran with the ftp.gnu.org hostname implying FTP access. :-) I might watch out for the no-df entry to your scrub line, as it is probably breaking PMTUd: I thought about it too and ran a test with that line commented out, but it did not help. Try to enable logging in pf and see if it's dropping anything. Also just to be sure try removing the scrubbing to see if it makes any difference. -- Best Regards, Iulian Margarintescu http://www.erata.net [EMAIL PROTECTED] (spamassassin pf spamd all said it's OK to make it public ;-) ) Key ID: 0x03176E5CEDEFF7AB I prefer plain text email pgpf68IiIeOLB.pgp Description: PGP signature
Re: Problem with installworld in FreeBSD 6.2-RELEASE-p5
ExTaZyTi wrote: Hi, My problem is with the installing new world in my system, this is the error === bin (install) === bin/cat (install) install -s -o root -g wheel -m 555 cat /bin strip: /bin/sthZDAzl: Operation not permitted install: wait: Operation not permitted *** Error code 70 Stop in /usr/src/bin/cat. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. If someone can help me. Thanks in advance. It could be caused /tmp is mounted with noexec, or by securelevel settings. Miroslav Lachman ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
question about gtar and --newer
man gtar states: --newer dateOnly store files with creation time newer than date. Is it totally wrong and gtar really uses inode change time (like tar) or gtar does no take inode change time into account at all? -- Regards, Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) signature.asc Description: OpenPGP digital signature
Upgrading to amd64 requires recompilation of ports?
I was just wondering if one were to upgrade a FreeBSD installation from i386 to amd64, would it require a complete recompilation of all the ports? (I already know that it does require a recompilation of world and the kernel). Thanks. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading to amd64 requires recompilation of ports?
On Sat, Jun 16, 2007 at 03:38:29AM +0200, Ivan Voras wrote: Indigo 23 wrote: the ports? (I already know that it does require a recompilation of world and the kernel). AFAIK nobody has succeeded in this (i.e. upgrading i386 to amd64 via buildkernel/world) on-line far enough to tell the tale. You might be the first :) Nah, I've done it several times. Yes, you will want to recompile all ports. While they may mostly work, some things (e.g. threaded applications) will currently fail, and if you ever want to build any new ports on that systemthey'll be very unhappy trying to link together 32-bit and 64-bit objects. Kris pgpqWCRoZu9Co.pgp Description: PGP signature
