Re: restart a script in etc/rc.d
On Mon, Mar 2, 2009 at 4:10 PM, Glen Barber glen.j.bar...@gmail.com wrote:
On Mon, Mar 2, 2009 at 2:25 PM, Oliver Lehmann lehm...@ans-netz.de wrote:
Hi Doug,
Doug Barton wrote:
Also, the assignment of pidfile should really come after the defaults are
set.
If you do all that and it still doesn't work, send a diff of your two rc.d
scripts to the list.
PROVIDE is in both cases utility (probably a generic unchanged default)
- I've changed it to utility2 for bacula-fd2 with no changes. Here the diff:
r...@nudel rc.d diff -u bacula-fd*
--- bacula-fd 2009-02-15 23:25:03.0 +0100
+++ bacula-fd2 2009-03-02 20:22:40.0 +0100
@@ -16,16 +16,16 @@
. /etc/rc.subr
-name=bacula_fd
+name=bacula_fd2
rcvar=${name}_enable
command=/usr/local/sbin/bacula-fd
I didn't see anyone else mention this -- did you change 'bacula-fd' to
'bacula-fd2'?
Actually... That may not work (although, you could create a symlink,
but I doubt that'll help). Ignore my noise.
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: restart a script in etc/rc.d
On Mon, Mar 2, 2009 at 2:25 PM, Oliver Lehmann lehm...@ans-netz.de wrote:
Hi Doug,
Doug Barton wrote:
Also, the assignment of pidfile should really come after the defaults are
set.
If you do all that and it still doesn't work, send a diff of your two rc.d
scripts to the list.
PROVIDE is in both cases utility (probably a generic unchanged default)
- I've changed it to utility2 for bacula-fd2 with no changes. Here the diff:
r...@nudel rc.d diff -u bacula-fd*
--- bacula-fd 2009-02-15 23:25:03.0 +0100
+++ bacula-fd2 2009-03-02 20:22:40.0 +0100
@@ -16,16 +16,16 @@
. /etc/rc.subr
-name=bacula_fd
+name=bacula_fd2
rcvar=${name}_enable
command=/usr/local/sbin/bacula-fd
I didn't see anyone else mention this -- did you change 'bacula-fd' to
'bacula-fd2'?
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: magic disappearing coredumps
On Fri, Apr 24, 2009 at 11:21 AM, Horst Günther Burkhardt III ho...@sxemacs.org wrote: I'm trying to debug a piece of software. It dumps a core file which mysteriously vanishes. it's not in the program directory, nor my $HOME, nor /var/crash nor /var/core ... Deliberately crashing /bin/sh also results in a core file which turns up nowhere on my filesystem. Crossposting to -stable and -ppc because i'm uncertain whether this is a ppc issue or a bsd issue or simple operator incompetence. I apologise if the answer is something that was a google away. Do you disable coredumps in /boot/loader.conf? The following would enable them: kern.coredump=1 -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How do i fix the broken FTP structure of freebsd 7.0?
On Sun, Apr 26, 2009 at 4:42 AM, wac waldoalvare...@yahoo.com wrote: vantline# pkg_add -r dkimproxy-1.1 Error: FTP Unable to get ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7 .0-release/Latest/dkimproxy-1.1.tbz: File unavailable (e.g., file not found, no access) pkg_add: unable to fetch 'ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages- 7.0-release/Latest/dkimproxy-1.1.tbz' by URL vantline# ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ packages 10/23/2006 12:00:00 AM packages-5-stable 4/4/2008 12:00:00 AM packages-6-stable 4/18/2009 6:16:00 PM packages-6.4-release 11/21/2008 1:33:00 PM packages-7-stable 4/18/2009 10:06:00 PM packages-7.1-release 12/22/2008 11:30:00 PM packages-7.2-release 4/21/2009 5:18:00 PM packages-8-current 4/16/2009 2:38:00 PM packages-current 2/9/2008 12:00:00 AM packages-stable 3/1/2008 12:00:00 AM packages-7.0-release is completely missing. Is there a way to fix this? How? What should I put in PACKAGESITE? You could build from ports. Regarding PACKAGESITE, see the handbook. http://www.freebsd.org/doc/en/books/handbook/packages-using.html Upgrading is unfortunately not an option for me. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How do i fix the broken FTP structure of freebsd 7.0?
On Sun, Apr 26, 2009 at 7:40 PM, wac waldoalvare...@yahoo.com wrote: Thanks Glen but doing that in a remote computer is askin for trouble and I can't step to the risk of having that computer trashed (fixing it would cost almost as much as renting a new one). Anyway in the forums somebody gave me this: Doing what in a remote machine is asking for trouble? SSH will not be affected. ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/i386/7.0-RELEASE/packages/All The problem now is that the package I need is way too old. Let's see if i can work out to fix that. Problem is it uses perl and perl is used by another package the hosting company installed that depends on it. And that I really have 0 experience with it so reinstalling a new one means downtime. I'll try to modify dkimproxy and see what happens. So far the newer version installed with warnings but doesn't even start. If you need stability (production ready), you (as the maintainer of the machine) are obligated to some extent to keep it both, up to date and stable. Note: I use stable in quotes to not be confused with -STABLE. AFAIK, 7.0-REL was EOL'd (or is scheduled to be). Ports are generally guaranteed to be installable on the latest -RELEASE version (in this case, 7.1-RELEASE). Anything prior to that is not a guarantee. Packages (as I am sure you are aware) are only built one time -- when X.X-RELEASE is released. There is no guarantee on compatibility after that point. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Building 7.2-STABLE from 7.2-RELEASE
Hi, Andrew On Sun, May 24, 2009 at 12:43 PM, Andrew Klaus andrewkl...@gmail.com wrote: I'm trying to build a 7.2-STABLE buildworld right after I do a fresh install of 7.2-RELEASE. The kernel compiles (and boots) properly, without issue, however when I try to do a buildworld, I get the following error: objcopy -S -O binary zfsboot.out zfsboot.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/zfsboot/../btx/btx/btx -l zfsboot.ldr -o zfsboot.ld -P 1 zfsboot.bin btxld: zfsboot.ldr: Invalid argument *** Error code 2 Stop in /usr/src/sys/boot/i386/zfsboot. *** Error code 1 I know they introduced some new zfsboot stuff into the -Stable branch - could that have anything to do with it? Absolutely. Bernhard Schmidt just reported a patch that was seemingly successful a few emails back. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel KERNCONF=GENERIC fails
Hi, Christian On Tue, May 26, 2009 at 10:35 AM, Christian Walther cptsa...@gmail.com wrote: 2009/5/26 Christian Walther cptsa...@gmail.com: Hi, I wanted to update my system to FreeBSD 7.2, so after updating my sources I started a make buildkernel. After a while, it fails with the following message: /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_register_source': /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 4 of 'intr_event_create' makes pointer from integer without a cast /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 7 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c:136: warning: passing argument 8 of 'intr_event_create' from incompatible pointer type /usr/src/sys/i386/i386/intr_machdep.c: In function 'intr_execute_handlers': /usr/src/sys/i386/i386/intr_machdep.c:261: warning: implicit declaration of function 'intr_event_handle' /usr/src/sys/i386/i386/intr_machdep.c:261: warning: nested extern declaration of 'intr_event_handle' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Oh yes, but I shouldn't hit the send button before finishing the mail. ;-) Anyway there isn't much information left to share, I found nothing in UPDATING. Trying to build with a clean source tree instead. Has anybody an idea of what's happening here? Out of curiosity, how long ago did you update your sources? Also, did you change the GENERIC kernel config? (If so, please include that.) I haven't seen a tinderbox email about -STABLE failing since the 24th, which was a different problem than what you are seeing, anyway. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel KERNCONF=GENERIC fails
Christian, On Tue, May 26, 2009 at 2:42 PM, Christian Walther cptsa...@gmail.com wrote: No, I create my own kernel configuration by copying GENERIC. Well, for some strange reason the same happened again: I did # mv /usr/src /usr/src.old # csup /root/stable-supfile # cd /usr/src # make buildkernel KERNCONF=GENERIC and it fails with exactly the same the error: [snip] Maybe it's a problem with *default host=cvsup.de.FreeBSD.org I changed my stable-supfile to use cvsup.freebsd.org instead, and I'm updating right now. Either there has just been an update commited, or the servers aren't in sync, because I see many Edits, Checkouts and even Deletions. I'm actually curious what happens with: 'make buildworld' without KERNCONF=GENERIC (which is implied anyway, if not stated explicitly). -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.0-RELEASE-p12 and php5-gd
On Tue, May 26, 2009 at 7:09 PM, free...@box201.com wrote: I've been trying to build /usr/ports/graphics/php5-gd [snip] Everything built smoothly. I just can't build the php5-gd port now. Has anyone else had this problem? What is the error? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: I've borked my ZFS system upgrading to -STABLE
On Wed, May 27, 2009 at 12:49 PM, Steve Bertrand st...@ibctech.ca wrote: Hey all, In short, I've got a system with /boot on a USB thumb drive that I boot from, which then mounts root and the rest of the system from a 4-disk ZFS storage pool. However, during the upgrade, something didn't go quite right, and now when I boot, I end up with: /libexec/ld-elf.so.1: Shared object libc.so.7 not found required by sh ...at the Enter full path of shell or RETURN for /bin/sh# prompt. Hitting return repeats the cycle. Rebooting to the old kernel does not help, as it was the installworld that failed. I've seen this before. My situation was different, as I had just installed the machine, finished a 'co' on the source tree and rebuilt world/kernel. Since there was nothing, production-wise, on the machine, I thought nothing of it and reinstalled. Had there been data on the machine, I would have dug deeper. I can boot the box using alternate media, but I can't figure out the procedure to mount the ZFS pool into the filesystem. Can you boot into single-user mode from the USB device? This box is a running-backup box, so I'm not overly concerned about the data, but I would like to learn how to properly get to the data if this situation arises in the future. Can someone provide some pointers on how to do this without destroying the pool? Unfortunately, I haven't played with ZFS (because of lack of hardware to run it on)... My reason for the post was to suggest single-user mode, if you haven't already tried. Also, to stop the repeated reboot, you could use /rescue/sh in place of /bin/sh (hopefully). -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: make buildkernel KERNCONF=GENERIC fails
On Tue, May 26, 2009 at 4:15 PM, Rick C. Petty rick-freebsd2...@kiwi-computer.com wrote: You should always do a buildworld before doing a buildkernel, as the toolchain which builds the kernel might have changed. Also KERNCONF=GENERIC is implied. Rick, I thought the toolchain didn't change until an installworld was done (and possibly a reboot). -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: latest stable version of FreeBSD?
On Wed, Jun 3, 2009 at 11:24 PM, AES allnetgr...@yahoo.com wrote: Where can I download the latest stable version of FreeBSD? http://www.freebsd.org/where.html http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ -- Glen Barber http://www.dev-urandom.com http://www.linkedin.com/in/glenjbarber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Kernel Debugging Options
Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options KDB options KDB_UNATTENDED options DDB and 'sysctl debug.debugger_on_panic' shows: debug.debugger_on_panic: 0 However, after a panic loading the vboxdrv.ko module, the machine did not reboot automatically after reboot. Here are my questions: 1) Would enabling DDB in the kernel prevent an automatic reboot after a panic? 2) Does the debugger wait for XX seconds of console inactivity before rebooting? I was under the impression from the handbook that the machine would instantly reboot and after dumping the crash to vmcore0. Is this assumption incorrect? Thanks in advance for any input. -- Glen Barber http://www.dev-urandom.com http://www.linkedin.com/in/glenjbarber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel Debugging Options
On Sat, Jun 6, 2009 at 9:16 AM, Glen Barberglen.j.bar...@gmail.com wrote: Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options KDB options KDB_UNATTENDED options DDB and 'sysctl debug.debugger_on_panic' shows: debug.debugger_on_panic: 0 However, after a panic loading the vboxdrv.ko module, the machine did not reboot automatically after reboot. I meant automatically after panic. It's early, and I am apparently unable to type a coherent thought... Here are my questions: 1) Would enabling DDB in the kernel prevent an automatic reboot after a panic? 2) Does the debugger wait for XX seconds of console inactivity before rebooting? I was under the impression from the handbook that the machine would instantly reboot and after dumping the crash to vmcore0. Is this assumption incorrect? Thanks in advance for any input. Also, if this is helpful, the userland / kernel are from two days ago, r193481: FreeBSD orion 7.2-STABLE FreeBSD 7.2-STABLE #0 r193481: Fri Jun 5 01:55:06 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386 -- Glen Barber http://www.dev-urandom.com http://www.linkedin.com/in/glenjbarber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel Debugging Options
On Sat, Jun 6, 2009 at 9:20 AM, Glen Barberglen.j.bar...@gmail.com wrote: Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options KDB options KDB_UNATTENDED options DDB and 'sysctl debug.debugger_on_panic' shows: debug.debugger_on_panic: 0 However, after a panic loading the vboxdrv.ko module, the machine did not reboot automatically after reboot. I meant automatically after panic. It's early, and I am apparently unable to type a coherent thought... Here are my questions: 1) Would enabling DDB in the kernel prevent an automatic reboot after a panic? 2) Does the debugger wait for XX seconds of console inactivity before rebooting? I was under the impression from the handbook that the machine would instantly reboot and after dumping the crash to vmcore0. Is this assumption incorrect? Thanks in advance for any input. Also, if this is helpful, the userland / kernel are from two days ago, r193481: FreeBSD orion 7.2-STABLE FreeBSD 7.2-STABLE #0 r193481: Fri Jun 5 01:55:06 EDT 2009 r...@orion:/usr/obj/usr/src/sys/ORION i386 Sorry for the noise... Disabling DDB from the kernel corrected the reboot issue. Unless I am misunderstanding how it is worded, it is unclear from the HTML docs that DDB overrides KDB_UNATTENDED. If I am misunderstanding, I apologize, but I'm more curious if I am experiencing unusual behavior with DDB enabled. -- Glen Barber http://www.dev-urandom.com http://www.linkedin.com/in/glenjbarber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Adding multiipul virtual domains?
On Mon, Jun 22, 2009 at 5:46 PM, ALLnetgroupallnetgr...@yahoo.com wrote: I have 3 virtual domains I need to add to FreeBSD 7.2-RELEASE server using Terminal or Webmin preferably Terminal. Virtual domains for what? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Adding multiipul virtual domains?
On Mon, Jun 22, 2009 at 6:23 PM, ALLnetgroupallnetgr...@yahoo.com wrote: For 3 domain names I just recieved. Please don't just reply to me, because the rest of the list doesn't see your response. Your question is extremely vague. What are you trying to do? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Value of $? lost in the beginning of a function.
2009/7/19 Romain Tartière rom...@blogreen.org:
Hi!
Simple test case:
8--
#!/bin/sh
foo()
{
echo \$?=$? \$1=$1
}
false
foo $?
8--
% sh foo.sh
$?=0 $1=1
% zsh foo.sh
$?=1 $1=1
% bash foo.sh
$?=1 $1=1
As you can see, the value of $? is « lost » when FreeBSD sh enters a
function. Is this supposed to behave this way?
Hi.
I'm no expert at shell scripting, but my first presumption is that
since you have '#!/bin/sh' at the beginning of the script, it is
creating a new subshell, and overwriting the value. What happens if
you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ?
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Value of $? lost in the beginning of a function.
2009/7/19 Romain Tartière rom...@blogreen.org: Hi Glen, On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote: % sh foo.sh % zsh foo.sh % bash foo.sh What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ? This is not related to my problem since I am not running the script using ./foo.sh but directly using the proper shell. sh just behaves differently, that looks odd so I would like to know if it is a bug in sh or if there is no specification for this and the behaviour depends of the implementation of each shell, in which case I have to tweak the script I am porting to avoid this construct (passing $? as an argument for example). Romain My understanding was this: If you specify 'sh foo.sh' at the shell, the script will be run in a /bin/sh shell, _unless_ you override the shell _in_ the script. Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh foo.sh' containing '#!/bin/sh' would execute using zsh. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Shell execution ( [was] Re: Value of $? lost in the beginning of a function.)
Possibly off-topic... 2009/7/19 Glen Barber glen.j.bar...@gmail.com: 2009/7/19 Romain Tartière rom...@blogreen.org: Hi Glen, On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote: % sh foo.sh % zsh foo.sh % bash foo.sh What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ? This is not related to my problem since I am not running the script using ./foo.sh but directly using the proper shell. sh just behaves differently, that looks odd so I would like to know if it is a bug in sh or if there is no specification for this and the behaviour depends of the implementation of each shell, in which case I have to tweak the script I am porting to avoid this construct (passing $? as an argument for example). Romain My understanding was this: If you specify 'sh foo.sh' at the shell, the script will be run in a /bin/sh shell, _unless_ you override the shell _in_ the script. Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh foo.sh' containing '#!/bin/sh' would execute using zsh. I meant to say in the last line: '#!/bin/sh' would override the 'zsh' shell. Can someone enlighten me if I am wrong about this? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Shell execution ( [was] Re: Value of $? lost in the beginning of a function.)
On Sun, Jul 19, 2009 at 9:02 PM, Mark Andrewsma...@isc.org wrote: In message 4ad871310907191717g1ed90be7y92250f2addc38...@mail.gmail.com, Glen Barber writes: Possibly off-topic... 2009/7/19 Glen Barber glen.j.bar...@gmail.com: 2009/7/19 Romain Tarti=E8re rom...@blogreen.org: Hi Glen, On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote: % sh foo.sh % zsh foo.sh % bash foo.sh What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ? This is not related to my problem since I am not running the script using ./foo.sh but directly using the proper shell. =A0sh just behaves differently, that looks odd so I would like to know if it is a bug in sh or if there is no specification for this and the behaviour depends of the implementation of each shell, in which case I have to tweak the script I am porting to avoid this construct (passing $? as an argument for example). Romain My understanding was this: If you specify 'sh foo.sh' at the shell, the script will be run in a /bin/sh shell, _unless_ you override the shell _in_ the script. Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh foo.sh' containing '#!/bin/sh' would execute using zsh. I meant to say in the last line: '#!/bin/sh' would override the 'zsh' shel= l. Can someone enlighten me if I am wrong about this? #! is used to define the interpretor when the file is exec'd. perl, AFAIK, is the only interpretor that will look at what is after the #! and modify it's behaviour. All other a interpretors (shells) treat #! as a comment. Some shells used to examine the executable about to be called and looked for #! and invoke the correct interpretor. This was how #! was supported before kernels has support for #!. It was all done in userland. Hi, Mark. You've given me enough information to point me in the right direction on digging further into this. Thanks, and I appreciate the response! -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Shell execution ( [was] Re: Value of $? lost in the beginning of a function.)
Hi, Lowell On Mon, Jul 20, 2009 at 7:02 AM, Lowell Gilbertfreebsd-stable-lo...@be-well.ilk.org wrote: Glen Barber glen.j.bar...@gmail.com writes: Possibly off-topic... 2009/7/19 Glen Barber glen.j.bar...@gmail.com: 2009/7/19 Romain Tartière rom...@blogreen.org: Hi Glen, On Sun, Jul 19, 2009 at 04:32:28PM -0400, Glen Barber wrote: % sh foo.sh % zsh foo.sh % bash foo.sh What happens if you replace '#!/bin/sh' with '#!/usr/local/bin/zsh' ? This is not related to my problem since I am not running the script using ./foo.sh but directly using the proper shell. sh just behaves differently, that looks odd so I would like to know if it is a bug in sh or if there is no specification for this and the behaviour depends of the implementation of each shell, in which case I have to tweak the script I am porting to avoid this construct (passing $? as an argument for example). Romain My understanding was this: If you specify 'sh foo.sh' at the shell, the script will be run in a /bin/sh shell, _unless_ you override the shell _in_ the script. Ie, 'sh foo.sh' containing '#!/bin/sh' being redundant, but 'zsh foo.sh' containing '#!/bin/sh' would execute using zsh. I meant to say in the last line: '#!/bin/sh' would override the 'zsh' shell. Can someone enlighten me if I am wrong about this? The person to whom you were responding had it closer. The shell specified in the #! first line is only consulted if you run it as ./foo.sh. Otherwise, it's input to the shell that you started, and the line is only a comment. I suppose that makes sense, but what if the script location is in the user's $PATH? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Shell execution ( [was] Re: Value of $? lost in the beginning of a function.)
On Mon, Jul 20, 2009 at 1:56 PM, Lowell Gilbertfreebsd-stable-lo...@be-well.ilk.org wrote: Glen Barber glen.j.bar...@gmail.com writes: The shell specified in the #! first line is only consulted if you run it as ./foo.sh. Otherwise, it's input to the shell that you started, and the line is only a comment. I suppose that makes sense, but what if the script location is in the user's $PATH? That would be the same as ./foo.sh. The distinction is between whether the file is treated as an executable or as input to a script. You might find the manual page for execve(2) useful for more detail on how the former case is handled. Aha! Yes, I will have a look. Thanks for the point in the right direction. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Shell execution ( [was] Re: Value of $? lost in the beginning of a function.)
On Mon, Jul 20, 2009 at 3:12 PM, Doug Bartondo...@freebsd.org wrote:
Glen Barber wrote:
Possibly off-topic...
It's very off topic for -stable. If you want to follow up on this,
please do so in -hackers.
I meant to say in the last line: '#!/bin/sh' would override the 'zsh'
shell.
Can someone enlighten me if I am wrong about this?
It's trivial to create an example to test it yourself, don't ask when
you can do. :)
#!/bin/foo
echo yes
$ ./foo
bash: ./foo: /bin/foo: bad interpreter: No such file or directory
$ sh foo
yes
$ bash foo
yes
Now it's your turn. :)
Hi, Doug.
The test I was going to run was:
-
#!/bin/sh
echo $SHELL
-
which I would execute from $PATH and from 'sh/csh/zsh foo.sh', but I
haven't had much time to play around with it. I plan on having time
later today after ${JOB}.
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Going to BSD 8 from RELENG_7
Hi, Dan On Thu, Aug 13, 2009 at 9:12 PM, Dan Allendanalle...@airwired.net wrote: I cvsup and build RELENG_7 many times a week. This has served me well (except for the ZFS boot problem I had that went in and was backed out) for quite a while. I like to track a STABLE release. When BSD 7 went to 7.1 and to 7.2, it all just happened automatically with the way I do things. By BSD, I hope you mean FreeBSD. I think BSD is still at version 4.4. :-) Now I am interested on one of my BSD machines to try 8.0. I need to change my cvsup target from RELENG_7 to CURRENT I believe. Is that true? When will STABLE become 8.0? 8.0 is still in -BETA2. 8.0-STABLE will be after -BETA3, and the release candidates. If you want 8.0-STABLE, you do not want CURRENT, you want RELENG_8. HTH. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: today portsnap aren't portsnapping
Hi, On Sun, Aug 23, 2009 at 8:28 AM, barbarabarbara.xxx1...@libero.it wrote: Sorry, it's not the first time I notice that, but I don't know where is the better place to report it. Any advise about that will be appreciated. It seems that there aren't new port snapshot on the servers. Can someone else confirm that? For example a new version of Makefile for multimedia/vlc has been committed more than 7 hours ago, but I'm still not getting the new one. Thanks What mirror are you using by default? orion# portsnap fetch update Looking up portsnap.FreeBSD.org mirrors... 3 mirrors found. Fetching snapshot tag from portsnap1.FreeBSD.org... done. Fetching snapshot metadata... done. Updating from Thu Aug 20 09:52:10 EDT 2009 to Sat Aug 22 19:06:01 EDT 2009. Fetching 4 metadata patches... done. Applying metadata patches... done. Fetching 0 metadata files... done. Fetching 2996 patches.10203040506070809010011012013014015016017018019020021022023024025026027028029030031032033034035036037038039040041042043044045046047048049050051052053054055056057058059060061062063064065066067068069070071072073074075076077078079080081082083084085086087088089090091092093094095096097098099010001010102010301040105010601070108010901100111011201130114011501160117011801190120012101220123012401250126012701280129013001310132013301340135013601370138013901400141014201430144014501460147014801490150015101520153015401550156015701580159016001610162016301640165016601670168016901700171017201730174017501760177017801790180018101820183018401850186018701880189019001910192019301940195019601970198019902000201020202030204020502060207020802090210021102120213021402150216021702180219022002210222022302240225022602270228022902300231023202330234023502360237023802390240024102420243024402450246024702480249025002510252025302540255025602570258025902600261026202630264026502660267026802690270027102720273027402750276027702780279028002810282028302840285028602870288028902900291029202930294029502960297029802990... done. Applying patches... -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: today portsnap aren't portsnapping
On Sun, Aug 23, 2009 at 8:39 AM, barbarabarbara.xxx1...@libero.it wrote: I've tried with portsnap[1-3].freebsd.org mirrors. Can you check with: grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile I'm getting: DISTVERSION= 1.0.0 but the last version committed 7h26m ago has 1.0.1 Yes, I have the updated version for that port. orion# grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile DISTVERSION=1.0.1 -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: today portsnap aren't portsnapping
On Sun, Aug 23, 2009 at 8:52 AM, barbarabarbara.xxx1...@libero.it wrote: On Sun, Aug 23, 2009 at 8:39 AM, barbarabarbara.xxx1...@libero.it wrote: I've tried with portsnap[1-3].freebsd.org mirrors. Can you check with: grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile I'm getting: DISTVERSION= 1.0.0 but the last version committed 7h26m ago has 1.0.1 Yes, I have the updated version for that port. orion# grep ^DISTVERSION /usr/ports/multimedia/vlc/Makefile DISTVERSION= 1.0.1 I've tried again and it worked. That's strange. I've also got the latest audio/gnome-media, committed more than 12h ago. Very odd. How many patches did it apply altogether? -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Rearrange entries in GENERIC KERNCONF?
Hello I was considering submitting a patch to rearrange some USB devices in the GENERIC kernel config. I wanted to get some feedback / comments before I submit a PR. What I was going to propose is moving rum(4), ural(4), uath(4) and zyd(4) into a separate USB section, similar to 'USB Serial devices' and 'USB Ethernet'. A diff of the i386 GENERIC is attached, and comments appreciated. -- Glen Barber --- GENERIC.orig2009-10-02 21:35:36.0 -0400 +++ GENERIC 2009-10-03 13:40:01.0 -0400 @@ -301,10 +301,6 @@ device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse -device rum # Ralink Technology RT2501USB wireless NICs -device ural# Ralink Technology RT2500USB wireless NICs -device uath# Atheros AR5523 wireless NICs -device zyd # ZyDAS zb1211/zb1211b wireless NICs device urio# Diamond Rio 500 MP3 player # USB Serial devices device u3g # USB-based 3G modems (Option, Huawei, Sierra) @@ -324,6 +320,11 @@ device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet device udav# Davicom DM9601E USB +# USB Wireless +device rum # Ralink Technology RT2501USB wireless NICs +device ural# Ralink Technology RT2500USB wireless NICs +device uath# Atheros AR5523 wireless NICs +device zyd # ZyDAS zb1211/zb1211b wireless NICs # FireWire support device firewire# FireWire bus code ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: NDIS broken?
Hi On Wed, Oct 7, 2009 at 7:51 PM, Jeff Dowsley jeff.dows...@mac.com wrote: Folks Just upgraded from 7.2 to 8.0RC1 Under 7.2, I was using an ndis wrapper to provide a Windows network driver for an old Linksys PCMIA card (non-ath). Worked beautifully as per the Handbook under 7.2. Sadly, under 8.0RC1, the process to generate the wrapper appears to work OK, but when I attempt to set any of the card's parameters, ifconfig returns I/O errors. For example: ifconfig ndis0 up (back to prompt without errors, but then... ifconfig ndis0 inet 192.168.1.105 netmask 255.255.255.0 ifconfig: ioctl (SIOCAIFADDR): Invalid argument or ifconfig ndis0 ssid chcs ifconfig: SIOCS80211: Invalid argument Have a look at the 20080420 entry in /usr/src/UPDATING for 8.X. You have to change ndis to wlan with an additional change in rc.conf. HTH. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[panic] Finally got a crash report
Howdy, Since I got this laptop, I've been having some issues I could not track. Usually the system will completely lock up, no keyboard, mouse, etc, leaving me with no way to break to the debugger, forcing me to power off completely. Something changed recently, and although the machine locked up again, I was able to get a crash report[1]. The kernel config the crash report mentions is available as well[2]. I can usually trigger it with excessive disk IO, but this time I was editing a file in Vim. Any thoughts? [1] - http://freebsd.dev-urandom.com/ports/20091025.core.txt [2] - http://freebsd.dev-urandom.com/ports/PEGASUS -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Nikon Coolpix
On Sunday 23 December 2007 02:54:35 pm Michael Butler wrote: -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Nikon Coolpix
My apologies for the blank post. Apparently, I became a bit trigger happy while setting up Kmail for mailing lists. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What would be the appropriate value for kern.maxfiles
On Tue, Nov 18, 2008 at 6:05 PM, Ramesh Ayyagari [EMAIL PROTECTED] wrote: Hello All, I have my client system running FreeBSD 6.3-RELEASE-p1 with 4 GB of RAM. This morning i have the following errors popping up on the console log - postfix/qmgr[94057]: fatal: socket: Too many open files Googling for this error, I found this is someway related to the kernel parameter kern.maxflies and increasing this value can have errors go away. The present value of this parameter is 24000. I also found this also depends of the RAM we have on the system. what would the appropriate value for kern.maxfiles for a system having 2GB RAM, a system having 4 GB and a system having 16GB of RAM. Please help The Xorg meta-package recommends 'kern.maxfiles=25000' for a desktop system. This is a situation where it really depends on what you're using your system for. HTH -- Glen Barber 570.328.0318 If you have any trouble sounding condescending, find a Unix user to show you how it's done. --Scott Adams ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What would be the appropriate value for kern.maxfiles
On Wed, Nov 19, 2008 at 3:51 PM, Ramesh Ayyagari [EMAIL PROTECTED] wrote: my server primarily runs postfix experiencing very huge inflow of mails 6 per hour. There are some other services that the servers runs like caching DNS etc but postfix being the primary application running on it. Ram 1.) Please don't top-post. 2.) I gave you an example. You obviously know what your server is doing, so you need to adjust the tunable accordingly. You can always set the number too high, then slim it down from there after testing to see what meets your requirements. -- Glen Barber If you have any trouble sounding condescending, find a Unix user to show you how it's done. --Scott Adams ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing FreeBSD 7.0
On Tue, Dec 23, 2008 at 1:30 PM, Jack Raats j...@jarasoft.net wrote: Hi, At this moment I have problems installing FreeBSD 6.4 and FreeBSD 7.0. After booting from CD the system I get the menu. I have tried all possible options. The system starts checking all hardware but freezes after finding the CD-ROM drives printing the GEOM_LABLE (on FB 7.0, not 6.4) (acd0) The hardware is a Targa Visonary 2700XP, AMD 2700+ CPU, mem 1 GB Can anyone help me. I never had this problems before on other systems. Have you tried disabling DMA or ACPI? hw.ata.ata_dma=0 -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Kernel Trap during installworld caused unrecoverable system
Hi folks. I was unfortunate enough to encounter a kernel trap in single user mode yesterday when upgrading from 7.1-RC1 to -RC2 using the typical build/install world. I'm still not sure what caused the trap, as the system was rebooting when I saw the screen. As one would expect, this led to an irrecoverable system; the system would automatically drop me into single user mode, as it could only mount the root directory; /bin/sh and /bin/csh would not work (had to use /restore/csh for the minimal digging I actually could do). So, now to the question. Given I could not mount anything other than /, would there have been any way for me to gather debugging information on what caused this failure? (FWIW, I am certain it is not a hardware failure.) Regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Kernel Trap during installworld caused unrecoverable system
On Fri, Dec 26, 2008 at 12:34 PM, Kris Kennaway k...@freebsd.org wrote: Glen Barber wrote: Hi folks. I was unfortunate enough to encounter a kernel trap in single user mode yesterday when upgrading from 7.1-RC1 to -RC2 using the typical build/install world. I'm still not sure what caused the trap, as the system was rebooting when I saw the screen. As one would expect, this led to an irrecoverable system; the system would automatically drop me into single user mode, as it could only mount the root directory; /bin/sh and /bin/csh would not work (had to use /restore/csh for the minimal digging I actually could do). So, now to the question. Given I could not mount anything other than /, would there have been any way for me to gather debugging information on what caused this failure? (FWIW, I am certain it is not a hardware failure.) You can proceed recovering the system using the tools in /rescue, and once you have shared libraries working again, run savecore to save the crashdump (assuming one was made). Hi, Kris. I'll do some digging later today. I appreciate your response. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-update to 6.4-RELEASE doesn't work
On Sun, Dec 28, 2008 at 6:50 AM, Thomas Krause freebsd-sta...@chef-ingenieur.de wrote: Dear list, I cannot upgrade my 6.3-RELEASE-p7/i386 to 6.4-RELEASE with freebsd-update. I have run: # freebsd-update upgrade -r 6.4-RELEASE Is there any output from this? and then # freebsd-update install No updates are available to install. Run '/usr/sbin/freebsd-update fetch' first. any ideas? You could try `freebsd-update -r 6.4-RELEASE-p6 upgrade'. -- Glen Barber Tell me and I forget. Teach me and I remember. Involve me and I learn. - Benjamin Franklin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-update to 6.4-RELEASE doesn't work
On Sun, Dec 28, 2008 at 9:26 AM, SDH Admin ad...@stardothosting.com wrote: any ideas? Try cvsup-without-gui your source tree, make buildworld, then try freebsd-update again. If he does a buildworld, he won't *need* to do freebsd-update... -- Glen Barber Tell me and I forget. Teach me and I remember. Involve me and I learn. - Benjamin Franklin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.1-RC2 Available...
On Sun, Dec 28, 2008 at 10:18 AM, Martin na...@web.de wrote: Am Thu, 25 Dec 2008 09:37:55 -0500 schrieb Ken Smith kensm...@cse.buffalo.edu: FreeBSD 7.1-RC2 is now available, the second of the Release Candidates. Unless an as yet undiscovered show-stopper comes along the release itself will be anywhere from a week to two weeks from now. Hi, the RC2 livefs CD still does not boot on my P2-350 machine. It works on my laptop though. Did something essential change after BETA2 in the boot sector? I can still boot a 8.0-CURRENT (december snapshot) livefs CD on this old box. With RC1 and RC2 I only get Booting CD-ROM... failure. from my BIOS (Asus board P2B). Any ideas? 1.) Try disabling ACPI 2.) Try hw.ata.ata_dma=0 at the boot prompt. -- Glen Barber Tell me and I forget. Teach me and I remember. Involve me and I learn. - Benjamin Franklin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.1-RC2 Available...
On Sun, Dec 28, 2008 at 10:25 AM, Glen Barber glen.j.bar...@gmail.com wrote: On Sun, Dec 28, 2008 at 10:18 AM, Martin na...@web.de wrote: Am Thu, 25 Dec 2008 09:37:55 -0500 schrieb Ken Smith kensm...@cse.buffalo.edu: FreeBSD 7.1-RC2 is now available, the second of the Release Candidates. Unless an as yet undiscovered show-stopper comes along the release itself will be anywhere from a week to two weeks from now. Hi, the RC2 livefs CD still does not boot on my P2-350 machine. It works on my laptop though. Did something essential change after BETA2 in the boot sector? I can still boot a 8.0-CURRENT (december snapshot) livefs CD on this old box. With RC1 and RC2 I only get Booting CD-ROM... failure. from my BIOS (Asus board P2B). Any ideas? Sorry for replying to myself.. I misread the post initially. Are you sure the CDs are good burns? Test them in a different machine if possible. -- Glen Barber Tell me and I forget. Teach me and I remember. Involve me and I learn. - Benjamin Franklin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: lenovo t400 does not start 7.1
On Tue, Jan 13, 2009 at 1:57 PM, Harald Servat redcr...@gmail.com wrote: Hello, I downloaded FreeBSD 7.1 (DVD iso image) for amd64 architecture (with correct SHA256 checksum), but I'm unable to start the system (Lenovo T400). Could you test the disc on a different machine to verify a good burn? [snip] -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH problem
On Mon, Jan 26, 2009 at 6:10 PM, SDH Support ad...@stardothosting.com wrote: Hi All, I can use scp to move files from a linux to my Freebsd machine. But, when I try to use WinSCP under windows, it always failed. WinSCP errors: Network error: Connection refused. Both scp sftp fail if using WinSCP. Any clues for this? Tcpdump on both boxes. -w to a file and analyze w/ ipsumdump. I don't think he'll be able to tcpdump on the windows box. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SSH problem
On Mon, Jan 26, 2009 at 6:44 PM, SDH Support ad...@stardothosting.com wrote: I don't think he'll be able to tcpdump on the windows box. There are tcpdump equivalents such as wireshark and windump. Yeah, I was replied to off-list with that information. I stand corrected, and apologize. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
iwn(4) 5100 - Estimation for MFC of r198429?
Hi, I've been using the iwn(4) driver contributed by Bernhard Schmidt with my Intel 5100 AGN card on 8-STABLE since he announced the availability. It was committed to -CURRENT as of r198429. There is no mention of MFC in the commit log. Are there plans to MFC this driver to 8-STABLE for a wider testing base? Cheers, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iwn(4) 5100 - Estimation for MFC of r198429?
On Wed, Dec 2, 2009 at 12:24 PM, Roland Smith rsm...@xs4all.nl wrote: On Tue, Dec 01, 2009 at 07:39:37PM -0500, Glen Barber wrote: Hi, I've been using the iwn(4) driver contributed by Bernhard Schmidt with my Intel 5100 AGN card on 8-STABLE since he announced the availability. It was committed to -CURRENT as of r198429. There is no mention of MFC in the commit log. Are there plans to MFC this driver to 8-STABLE for a wider testing base? Hear, hear. I've got a 5100 AGN in a laptop. I'd like to test it as well, without switching to -CURRENT. If I just got the files mentioned in the commit* and add/replace them in my source tree, it looks like it should work. Or am I missing something? That should be sufficient. Roland * http://svn.freebsd.org/viewvc/base?view=revisionrevision=198429 -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Jails in FreeBSD 8
Hi On Mon, Dec 14, 2009 at 9:54 AM, Peter Fraser petros.fra...@gmail.com wrote: Hi All I installed FBSD 8 and got some jails up using the instructions in the handbook. My question is this. Do you still have to use the alias IP address on the host that you want the jail to have? Example: I want my jail to have ip address 192.168.2.5 I put these entries in rc.conf on the host #Jail Config jail_enable=YES jail_set_hostname_allow=NO jail_list=www jail_www_hostname=www.mydomain.com jail_www_ip=192.168.2.5 jail_www_rootdir=/usr/home/jails/www jail_www_devfs_enable=YES Do I also need this entry below? ifconfig_vr0_alias0=inet 192.168.2.5 netmask 255.255.255.0 No. Alternatively, you can add the following line to rc.conf: jail_www_interface=vr0 That will bind the jail (with the specified IP) to that interface. /etc/defaults/rc.conf has a good listing of all jail(8) options. Regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 7:41 AM, Jamie Griffin j...@koderize.com wrote: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ Sign me up for a me too. The last message from that list in my mailbox is the (overly drawn out) Root Exploit thread. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Create socket files
Hi Peter On Tue, Dec 22, 2009 at 8:34 PM, Peter Fraser petros.fra...@gmail.com wrote: Hi All I wonder if anyone could help me with this problem. I followed the instructions in the handbook to create some jails. It makes part of the filesystem readonly which is good. This sounds like you used the service jail approach [1]. Correct me if I am wrong. Problem is though that I tried installing syslog-ng in one of the jails and when I tried to start it, I got this error Error binding socket; addr='AF_UNIX(/var/run/log)', error='Permission denied (13)' Error initializing source driver; source='src', id='src#0' Error initializing message pipeline; /usr/local/etc/rc.d/syslog-ng: WARNING: failed to start syslog_ng I think it's trying to create the socket files /var/run/log and /var/run/logpriv but can't. Is there anyway for me to create them manually? It has been some time since I used that method to create jails; the areas that have burned me in particular were symlinking /usr/local/bin/perl to /usr/bin/perl and similarly for the security/ca_root_nss port. Re-reading the doc, /var should be made read/write as it is part of the jail skeleton filesystem, from which you create the moving parts of your jail, so to speak. Did you create /var read-only? Regards, [1] - http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails-application.html -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: su password prompt ti stdout instead of /dev/tty
Hi, Cyrille Lefevre wrote: Hi, su password prompt is displayed to *stdout* instead of */dev/tty*. # su user $ su root -c date /tmp/date 21 (nothing displayed) $ cat /tmp/date Password:su: Sorry $ uname -a FreeBSD freebsd8.my.domain 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I suppose this is a getpass() problem ? I cannot reproduce this. In fact, su root -c date /tmp/date hangs waiting for input. orion % su root -c date /tmp/date ^C su: Sorry orion % less /tmp/date Password: orion % Also, you appear to be running an unpatched version of FreeBSD 8.0, subject to the rtld exploit (among a few others). I'd suggest upgrading. For what it's worth: orion % uname -a FreeBSD orion 8.0-STABLE FreeBSD 8.0-STABLE #20 r202187: Wed Jan 13 11:51:15 EST 2010 r...@orion:/usr/obj/usr/src/sys/ORION amd64 Regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
sshd logging with key-only authentication
Hi,
I've been seeing quite a bit of ssh bruteforce attacks which appear to
be dictionary-based. That's fine; I have proper measures in place, such
as key-only access, bruteforce tables for PF, and so on; though some of
the attacks are delaying login attempts, bypassing the bruteforce rules,
but that isn't the reason for this post.
What caught my interest is if I attempt to log in from a machine where I
do not have my key or an incorrect key, I see nothing logged in auth.log
about a failed login attempt. If I attempt with an invalid username, as
expected, I see 'Invalid user ${USER} from ${IP}.'
I'm more concerned with ssh login failures with valid user names.
Looking at crypto/openssh/auth.c, allowed_user() returns true if the
user is not in DenyUsers or DenyGroups, exists in AllowUsers or
AllowGroups (if it is not empty), and has an executable shell. I'm no C
hacker, but superficially it looks like it can never meet a condition
where the user is valid but the key is invalid to trigger a log entry.
Is this a bug in openssh, or have I overlooked something in my
configuration?
Regards,
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sshd logging with key-only authentication
On 7/8/10 10:24 PM, David Adam wrote:
On Thu, 8 Jul 2010, Glen Barber wrote:
I've been seeing quite a bit of ssh bruteforce attacks which appear to be
dictionary-based. That's fine; I have proper measures in place, such as
key-only access, bruteforce tables for PF, and so on; though some of the
attacks are delaying login attempts, bypassing the bruteforce rules, but that
isn't the reason for this post.
What caught my interest is if I attempt to log in from a machine where I do
not have my key or an incorrect key, I see nothing logged in auth.log about a
failed login attempt. If I attempt with an invalid username, as expected, I
see 'Invalid user ${USER} from ${IP}.'
I'm more concerned with ssh login failures with valid user names. Looking at
crypto/openssh/auth.c, allowed_user() returns true if the user is not in
DenyUsers or DenyGroups, exists in AllowUsers or AllowGroups (if it is not
empty), and has an executable shell. I'm no C hacker, but superficially it
looks like it can never meet a condition where the user is valid but the key
is invalid to trigger a log entry.
Is this a bug in openssh, or have I overlooked something in my configuration?
With LogLevel VERBOSE, you should get entries like
sshd[88595]: Failed publickey for root from 130.95.13.18 port 41256 ssh2
Is that what you're after?
Sort of, but do I really need to set verbose logging to find that valid
users are used in SSH attacks? root is an obvious target, which in my
scenario is not allowed. I'm concerned about more specific, allowed users.
Regards,
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: sshd logging with key-only authentication
On 7/8/10 11:13 PM, David Adam wrote:
On Thu, 8 Jul 2010, Glen Barber wrote:
On 7/8/10 10:24 PM, David Adam wrote:
On Thu, 8 Jul 2010, Glen Barber wrote:
What caught my interest is if I attempt to log in from a machine
where I do not have my key or an incorrect key, I see nothing logged
in auth.log about a failed login attempt. If I attempt with an
invalid username, as expected, I see 'Invalid user ${USER} from
${IP}.'
I'm more concerned with ssh login failures with valid user names.
Looking at crypto/openssh/auth.c, allowed_user() returns true if the
user is not in DenyUsers or DenyGroups, exists in AllowUsers or
AllowGroups (if it is not empty), and has an executable shell. I'm
no C hacker, but superficially it looks like it can never meet a
condition where the user is valid but the key is invalid to trigger
a log entry.
Is this a bug in openssh, or have I overlooked something in my
configuration?
With LogLevel VERBOSE, you should get entries like
sshd[88595]: Failed publickey for root from 130.95.13.18 port 41256 ssh2
Is that what you're after?
Sort of, but do I really need to set verbose logging to find that valid users
are used in SSH attacks? root is an obvious target, which in my scenario is
not allowed. I'm concerned about more specific, allowed users.
It's just an example I pulled out of the logs. You won't get that message
for users listed in DenyUsers, although you will get spaff if the denied
user attempts password authentication.
Right. Though, password authentication is not allowed, which brings me
back to my original point.
To me, verbose SSH logging doesn't seem like too big a burden,
It does to me, especially if, by default, sshd does not log failed
logins from valid users. I believe *that* should be default.
particularly if coupled with tools like sshit/sshdeny or logwatch. I
encourage you to experiment; you could even try patching sshd to emit the
relevant log lines at a lower debug level if you want.
I am fully aware of these utilities. They don't address the real
problem, however. Logwatch, in this scenario, is useless unless verbose
logging is enabled for sshd, which I believe should not be necessary.
Regards,
--
Glen Barber
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
panic in tmpfs_valloc_vp() in 8-STABLE r217160
Hi, I know tmpfs(5) is experimental on FreeBSD, but it seems to be enabled for ports-mgmt/tinderbox-devel, which probably not too coincidentally had just started a build before the machine panic'd. uname: FreeBSD orion 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #8 r217160: Sat Jan 8 14:17:44 EST 2011 gbarber@orion:/usr/obj/usr/src/sys/ORION amd64 I was able to get a shot of the console, which didn't give much output: http://www.glenbarber.us/img/panic.jpg Unfortunately, the machine hung on dumping RAM, in spite of 'dumpdev=/dev/mirror/swap' in rc.conf, so it seems I might be out of luck with getting a full crash report. I have dmesg from the last boot available here: http://www.glenbarber.us/stuff/dmesg.txt The machine runs a full ZFS setup, with a custom kernel; KERNCONF is available here: http://www.glenbarber.us/stuff/kernconf.txt Any advice on how I can help provide further information would be appreciated. Best regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic in tmpfs_valloc_vp() in 8-STABLE r217160
On 2/1/11 7:56 PM, Jeremy Chadwick wrote: Any advice on how I can help provide further information would be appreciated. At this time do not mix tmpfs with ZFS: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2011-01/msg00344.html Thanks for the info. Cheers, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: panic in tmpfs_valloc_vp() in 8-STABLE r217160
On 2/2/11 12:27 PM, Jaakko Heinonen wrote: On 2011-02-01, Glen Barber wrote: FreeBSD orion 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #8 r217160: Sat Jan 8 14:17:44 EST 2011 gbarber@orion:/usr/obj/usr/src/sys/ORION amd64 See this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=122038 Thanks, I'll check it out. -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Building your own FreeBSD USB memstick image
On 6/17/11 10:01 PM, Glen Barber wrote: Hey, On 6/17/11 9:22 PM, Jeremy Chadwick wrote: CC'ing Ken, Nathan, and Martin since they all have some insight to this procedure. Given the recent MFC of graid(8) to RELENG_8, I'd like to make my own FreeBSD USB memstick image but with the latest RELENG_8 kernel/world. For the USB memstick, I've found src/release/scripts/make-memstick.sh, but there's no real explanation as to what /path/to/directory should be, and that's probably because I'm not familiar with the build a base system infrastructure. /path/to/directory should be the 'R/' directory from the 'make release' process, a subdirectory of the CHROOTDIR target. Oops, my mistake. There's more to the hierarchy that I neglected. '/path/to/directory' in my case is '/usr/release/R/cdrom/disc1/8-STABLE', where '/usr/release' is CHROOTDIR. Again, I'd be happy to be proven wrong, or inaccurate. Regards, -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Building your own FreeBSD USB memstick image
Hey, On 6/17/11 9:22 PM, Jeremy Chadwick wrote: CC'ing Ken, Nathan, and Martin since they all have some insight to this procedure. Given the recent MFC of graid(8) to RELENG_8, I'd like to make my own FreeBSD USB memstick image but with the latest RELENG_8 kernel/world. For the USB memstick, I've found src/release/scripts/make-memstick.sh, but there's no real explanation as to what /path/to/directory should be, and that's probably because I'm not familiar with the build a base system infrastructure. /path/to/directory should be the 'R/' directory from the 'make release' process, a subdirectory of the CHROOTDIR target. Is the procedure for creating new FreeBSD memstick images documented anywhere? I'd be happy to be proven wrong, but I don't think so. The release process for 9.x builds the memstick by default, so I'm not sure it's worth updating the 7.x/8.x documentation for this. Regards, -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8 Stable won't boot into zfs with underlying geli layer amd64
On 6/23/11 8:47 AM, Sebastian Anding wrote: Hi, i tried to switch to 8.0 stable. I checkout the src-all with cvsup 3 days ago. What branch did you switch from, and what tag do you have in your supfile for the -stable branch? The tag for the latest -stable branch should be RELENG_8 . After make buildworld, make buildkernel and make installkernel, I booted into the new system. But now I'm not asked for the geli passphrases. That results in the kernel not beeing able to mount the root vfs. The keyboard (USB) is not responding anymore and so I'm not able to set parameters after the root fs went missing, or produce a dmesg. I guess that the discs are not detected anymore. My setup can be seen in the attached files. There are one freebsd-swap and one freebsd-zfs gpart partition on each disc. The gpart partitions freebsd-zfs are encrypted with geli. I attach the dmesg of the Generic 8.2 release kernel too. I'm not familiar with mixing GELI with ZFS, but I have a few questions to try to clarify exactly what you did because of ZFS pool compatibility. You mentioned 8.0-STABLE above, but you mention 8.2-RELEASE for dmesg. If you did in fact switch from 8.2-RELEASE to 8.0-STABLE, you downgraded your system. Depending on what ZFS version you were using (v15 was the default in 8.2-RELEASE), the zpool may not be usable by older ZFS versions (the default in 8.0-STABLE was v13 when it was branched from HEAD). Regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Status of support for 4KB disk sectors
suffering in performance? Probably. Why do I not care? Because the level of annoyance is extremely high -- remember, all of this has to be done from within the installer environment (referring to Emergency Shell), which on FreeBSD lacks an incredible amount of usability, and is even worse to deal with when doing a remote install via PXE/serial. Fixit is the only decent environment. Given that floppies are more or less gone, I don't understand why the Fixit environment doesn't replace the Emergency Shell. /rant Not that it necessarily helps in a PXE environment, but a memstick of 9-CURRENT has helped me recover minor oops situations a few times over the past few months. What are these floppies you speak of, again? :) Regards, -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: How to update like Debian
Hi, On 9/29/11 1:45 PM, Denny Schierz wrote: # freebsd-update fetch Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. Fetching public key from update3.FreeBSD.org... failed. No mirrors remaining, giving up. There was also no solution for this problem. I think it has something to do with the release I run: 8.2-STABLE FreeBSD 8.2-STABLE #0: Thu Jul 7 13:20:14 CEST 2011 This is indeed correct. freebsd-update(8) does not provide binary updates for the -STABLE branches (outside of -RC release candidates occasionally). Regards, Glen -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: question on netstat statistics.
Hi, Jeremy Chadwick wrote: [...] I don't particularly care what the man page says, I just know what works. :-) If there is something in the man page that is not precise, I personally am interested in any inconsistencies with reality so they can be fixed. Even given your detailed explanation, I'm still not 100% clear on what, if anything, is incorrect in the manual. Regards, Glen -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project pgpmEoto4GCuk.pgp Description: PGP signature
Re: question on netstat statistics.
On Mon, Nov 14, 2011 at 05:46:02PM -0800, Jeremy Chadwick wrote: On Mon, Nov 14, 2011 at 07:56:07PM -0500, Glen Barber wrote: Jeremy Chadwick wrote: [...] I don't particularly care what the man page says, I just know what works. :-) If there is something in the man page that is not precise, I personally am interested in any inconsistencies with reality so they can be fixed. Even given your detailed explanation, I'm still not 100% clear on what, if anything, is incorrect in the manual. FWIW, neither am I. The OP seems to be basing his argument syntaxes based on what's in the man page, so if something is vague, confusing, or inaccurate, he will need to state clearly what it is that's an anomaly. My comment was more along the lines of: if it's wrong in the man page, I'm really not that concerned (e.g. file a PR and be done with it). I'm still trying to work out exactly what it is the OP wants statistics-wise on a per-interface basis. I'm left thinking he wants netstat -s output per-interface, but that's not going to happen. Got it, thanks for clarifying. I (mis)read your statement as the manual is wrong, but here's the correct explanation. Thanks. Glen -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project pgpqMh4djnPmN.pgp Description: PGP signature
Re: question on netstat statistics.
Hi Vincent, On Tue, Nov 15, 2011 at 04:25:18PM +, Vincent Hoffman wrote: On 15/11/2011 00:56, Glen Barber wrote: Hi, Jeremy Chadwick wrote: [...] I don't particularly care what the man page says, I just know what works. :-) If there is something in the man page that is not precise, I personally am interested in any inconsistencies with reality so they can be fixed. Even given your detailed explanation, I'm still not 100% clear on what, if anything, is incorrect in the manual. Hi Glen, Filed as as misc/162587, sorry i did start using category docs and class docs, but I timed out the original web form and forgot to change from defaults while copying and pasting to the new page. Serves me right for using the web form. Thanks for pointing me to the PR. I've assigned it to myself, and will look into this. Glen -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project pgpL4DZTOvhxn.pgp Description: PGP signature
Re: Possible to build 9-stable kernel on 8.2?
Hi, On Tue, Nov 15, 2011 at 11:45:02AM -0800, Chuck Tuffli wrote: Is it possible to do a buildkernel of 9-stable (r227536) on a stock 8.2 system? Most of it seems to work, but the linker fails towards the end with ... MAKE=make sh /usr/home/ctuffli/dev/releng_9/src/sys/conf/newvers.sh GENERIC /usr/local/bin/svnversion cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/home/ctuffli/dev/releng_9/src/sys -I/usr/home/ctuffli/dev/releng_9/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug ld:/usr/home/ctuffli/dev/releng_9/src/sys/conf/ldscript.amd64:9: syntax error *** Error code 1 Stop in /usr/home/ctuffli/dev/releng_9/obj/usr/home/ctuffli/dev/releng_9/src/sys/GENERIC. *** Error code 1 Stop in /usr/home/ctuffli/dev/releng_9/src. *** Error code 1 Stop in /usr/home/ctuffli/dev/releng_9/src. You'll need to do 'buildworld' first. Regards, Glen -- Glen Barber ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Looks like a bug (or odd intended practice) in cron not honoring the PATH variable.
Hi, On Sat, Jan 28, 2012 at 04:45:01PM -0800, Eric Bullen wrote: Hi All, I'm running the following: FreeBSD x 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:46:30 UTC 2012 r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 I couldn't figure out why SOME of root's cronjobs weren't running, and others were. Here's my test crontab for root: # PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/user/local/bin Looks to me like '/user/local/bin' is more likely the problem. It should be '/usr/local/bin' (note the lack of 'e'). Regards, Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Reducing the need to compile a custom kernel
On Fri, Feb 10, 2012 at 02:56:04PM +0100, Alexander Leidinger wrote: The question is, is this enough? Or asked differently, why are you compiling a custom kernel in a production environment (so I rule out debug options zhich are not enabled in GENERIC)? Are there options which you add which you can not add as a module (SW_WATCHDOG comes to my mind)? If yes, which ones and how important are they for you? For me, the two big ones are IPSEC (which, as I understand it, we cannot ship with GENERIC due to export laws), and KDB_UNATTENDED. The latter may be a sysctl tunable, I never bothered to look. Regards, Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_8 still identifies itself as 8.3-PRERELEASE
Hi,
On Sun, Apr 22, 2012 at 10:59:02PM +0100, Adrian Wontroba wrote:
A RELENG_8 system built this morning still identifies itself as
8.3-PRERELEASE.
Any chance of this becoming 8.3-STABLE soon? While this is entirely
cosmetic, it does cause me issues at $JOB.
If this is a problem for you at $JOB, the attached patch will fix the
version output until the change is made in the official sources.
Glen
Index: sys/conf/newvers.sh
===
--- sys/conf/newvers.sh (revision 234589)
+++ sys/conf/newvers.sh (working copy)
@@ -32,7 +32,7 @@
TYPE=FreeBSD
REVISION=8.3
-BRANCH=PRERELEASE
+BRANCH=STABLE
if [ X${BRANCH_OVERRIDE} != X ]; then
BRANCH=${BRANCH_OVERRIDE}
fi
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Reject Action For SPF
On Thu, May 03, 2012 at 04:30:53PM -, Prabhpal S. Mavi wrote: Dear Friends, i have setup SPF alright, postfix is performing check as well (results below), but even if there is no SPF record exist for a domain, message is still accepted. how can i set the reject action, if no SPF available. Why would you want to reject mail from legitimite senders that do not have SPF records published? Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Fri, Jun 01, 2012 at 11:14:10PM -0400, David Magda wrote: ZFS is for storing file systems on locally connected block devices. Gluster is a network file system where data can be distributed over many nodes. Pardon my ignorance to not knowing what gluster is, but is this conceptually similar to HAST? Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Fri, Jun 01, 2012 at 09:19:15PM -0700, Freddie Cash wrote: Pardon my ignorance to not knowing what gluster is, but is this conceptually similar to HAST? Similar in concept, but different layers in the storage stack. HAST sits between the physical disks and the filesystem, replicating data between two systems. So, disks -- HAST -- ZFS. Got it, thanks. However, HAST is not specifically ZFS. (Just pointing it out.) Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Documenting 'make config' options
On Wed, Jun 06, 2012 at 02:14:46PM -0700, Doug Barton wrote: On 06/06/2012 11:59, Dave Hayes wrote: I'm describing more of a use case here, not attempting to specify an implementation. If a user invokes 'make', a window is presented to them with various options. It's probably very common that this is met with an initial reaction of what the hell do these do?, even from the most seasoned of admins (presuming they are unfamiliar with the software they have been asked to install). I claim it would be an improvement to have that information at the fingertips of the make invoker. What manner of providing this information would meet your needs? IMHO, something informing what THAT is in devel/subversion option MOD_DONTDOTHAT would be nice. :) Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: less and vi fail on file whose name begins with +
On Mon, Jul 16, 2012 at 01:03:30AM -0400, Thomas Mueller wrote: I notice in my latest build of FreeBSD 9.0-STABLE (#11), a problem with less and vi with files whose name begins with +. These files occur in /var/db/pkg/(pkg-name)/ For instance, if I cd /var/db/pkg/png-1.4.8 and type less +DESC I get Missing filename (less --help for help) but if I type the filename with full path, or even less ./+DESC it works OK less(1) is expecting '+' to be followed by additional arguments. If you use 'less -- +DESC', for example, it should work fine. Same with vi(1). Regards, Glen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: Quoth Ken Smith kensm...@buffalo.edu: The latter. If you are not using FreeBSD-Update to handle the updates of a machine you'll need to update your source tree using SVN for release branches (releng/*) from now on. Updates of the CVS repository will continue for the existing stable/* and head for now. I don't think anything has been decided on when that will stop. Two questions: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. Glen pgpZLNLT1eFGX.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 12:18:39AM -0400, Garrett Wollman wrote: In article 20120825041357.gd1...@glenbarber.us, g...@freebsd.org writes: On Sat, Aug 25, 2012 at 04:55:48AM +0100, Ben Morrow wrote: 1. Is is sensible|supported to use freebsd-update to update just the src component, followed by a normal buildworld/buildkernel to update the rest of the system? I would much prefer to avoid having to use svn, especially given that it isn't in the base system. No. freebsd-update(8) is a binary system updater. It does not touch your source tree. It works just fine for that, actually -- PROVIDED that you installed the source tree the same way (from original installation media or with a previous freebsd-update invocation). He asked followed by buildworld/buildkernel. This implies customization, as did the second question. I don't know what it will do if you've modified the sources. On the machines where I do this, I don't touch the sources. I do. It will overwrite them. Glen pgp78RtHs0SGK.pgp Description: PGP signature
Re: FreeBSD 9.1-RC1 Available...
On Sat, Aug 25, 2012 at 04:04:07PM +0200, Alexandre wrote: No. freebsd-update(8) is a binary system updater. It does not touch your source tree. Freebsd-update tool installs binary updates for -RELEASE branch only (base system + GENERIC kernel). By default, /usr/src is synced. So you can upgrade your system and GENERIC kernel, then rebuild manually your custom kernel if you got one. This is described in the Handbook at the page FreeBSD update. You do not have to SVN or CSUP your /usr/src sources tree after used freebsd-update tool. You're right, my mistake. I meant to remove that last sentence after realizing this. Sorry for the confusion. Glen pgpQHzHIOKP3w.pgp Description: PGP signature
FreeBSD 10-CURRENT and 9-STABLE snapshots
Hi, A number of FreeBSD users have displayed interest in the availability and testing of -STABLE and -CURRENT snapshot releases. I have been working on generating snapshots regularly, and now would like to announce their availability for those interested in testing. Please note, as always with the -STABLE and -CURRENT branches, these snapshots are not intended for production systems. The snapshots available are: - 10.0-CURRENT amd64 - 10.0-CURRENT i386 - 9.1-PRERELEASE amd64 - 9.1-PRERELEASE i386 Note that the 9.1-PRERELEASE snapshots are the stable/9 branch, not what will eventually be 9.1-RELEASE. I do not yet have snapshots for the 8-STABLE branch, but am working on the magic to make that happen as well. There are also no bootonly ISOs, since the necessary distribution sets are not available on the FreeBSD FTP servers, so I cannot direct the installer to a different location very easily. The URL for the snapshots is: https://snapshots.glenbarber.us/Latest/ The SHA256 of the xz(1)-compressed install medium follows, and is also included in a plain-text file on the site. FreeBSD-10.0-CURRENT-amd64-memstick.xz = 8779f5925cb903c64d647392f6af825d5e74019d6d13222045d69091b03a81ff FreeBSD-10.0-CURRENT-amd64-release.iso.xz = cc3934c947563c23f92ba1cd8ca7ded3999dfbc050e2b2647c294e442f267040 FreeBSD-10.0-CURRENT-i386-memstick.xz = 9eb7ff8e28c0c524d2794828acb601b9b7079c1d00017e3bf84b974ff4412e42 FreeBSD-10.0-CURRENT-i386-release.iso.xz = 0d1334fea13e16cb0d06a3f3c3fb7b0e1223baf06a06a889a6cffa6981348ae5 FreeBSD-9.1-PRERELEASE-amd64-memstick.xz = f5f1e7acbaaac6eb61c5194199eb6ef090af242efc9808dc1af5caeee126e15e FreeBSD-9.1-PRERELEASE-amd64-release.iso.xz = 0cfa5b258428741e0345b29eed241188d5944fcb15a70b079d39d56195f0 FreeBSD-9.1-PRERELEASE-i386-memstick.xz = 4e98ffe63b186b0e26f22c3ddfb0582019bf352d1ea39da2757817c809872b67 FreeBSD-9.1-PRERELEASE-i386-release.iso.xz = 0bce6f2a9626705484ff7cac18623f714e289ef6ddc0b6199d78eba37ded2ca4 The Latest directory on the site will always point to the latest batch of snapshots, which right now my goal is to regenerate every few days (I do not have a definitive timeframe in mind yet). I hope these are useful to the FreeBSD community. Feedback on this is welcome, as always. Cheers, Glen PS: Please report any issues regarding downloading to me directly. pgpXSdNJRWeLz.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Fri, Oct 05, 2012 at 09:56:39PM +0800, Mike Manilone wrote: A number of FreeBSD users have displayed interest in the availability and testing of -STABLE and -CURRENT snapshot releases. Good idea! :-) Could it be used in freebsd-update? Currently, no. The freebsd-update(8) utility is something I have been meaning to look into. Glen pgpWPNYGozWSO.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Fri, Oct 05, 2012 at 04:29:45PM +0200, Miroslav Lachman wrote: It would be nice to have them hosted on FreeBSD.org site as official source. I agree 100%. Unofficial snapshots can be downloaded from https://pub.allbsd.org/FreeBSD-snapshots/ for a long time (bootonly.iso too) I am not sure how the bootonly.iso for -CURRENT and -STABLE can point to a non-FreeBSD FTP site without patching the source prior to the release build. If there is a clean way to do this without modifying the src/ tree prior to the build phase, I am happy to also provide bootonly.iso images and the necessary hierarchy for the various distribution sets. Glen pgpdXSzDncWIb.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Wed, Oct 10, 2012 at 07:04:22PM +0200, Claude Buisson wrote: And for the record, they are NOT official snapshots. I know, but: - there are no more official snapshots on freebsd.org This is a problem, and for what it is worth (and as Mark mentioned in a previous reply), the end goal is official snapshots. - anybody enquiring about it on the lists is directed to allbsd.org For clarification purposes, my goal is _not_ to compete with allbsd.org (in case anyone sees it that way), but to provide an alternative location for snapshots. - the recently created snapshots.glenbarber.us is much more limited May I ask what it is that is limiting? If there is some limitation, I certainly will do what I can to address it. Right now, the limitations I am already aware of are: - Lack of varying ranges of dates of snapshots to download. This is really due to lack of space on the machine these snapshots are hosted to hold much more than 3 days of snapshots. - Lack of snapshots for the stable/8 branch. I'm working on this, and differences (infrastructurally) in how the release builds work between stable/9 and stable/8 are trickier than I originally anticipated to work around. I have local patches to the release build script in -CURRENT that I have been testing to make legacy release builds do the right thing, and have had some success with my changes, but I am not yet comfortable committing them just yet. Having said that, I will not upload snapshot images that I am not sure are okay to use. As mentioned in my original email, I certainly do welcome feedback. I certainly will do what I can to address any issues and/or limitations. Glen pgpy0wfjbpUnS.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 12:47:32AM +0100, Bruce Cran wrote: On 11/10/2012 00:40, Glen Barber wrote: This is a problem, and for what it is worth (and as Mark mentioned in a previous reply), the end goal is official snapshots. I think a lot of people will be wondering what's special about _your_ snapshots that they'll become official The answer is simple. Nothing. We're all on the same team here. why not just make pub.allbsd.org the official source? Because offloading official snapshots to third-party sites (any third-party site) rather than doing the work ourselves is the wrong solution. Glen pgpfZJbFUXGVm.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 02:02:40AM +0200, Michael Ross wrote: - I had to install a complete VCS I have no (other) need of, Unfortunate, but not hugely significant (Just a bit of disk space). I think it is rather significant: FWIW, you can compile the svn binary elsewhere, statically linked, and save the dependency problem by copying the resulting binary around. I do this on many machines, and even have a static svn binary in /root/bin as a fallback in case things blow up badly and I cannot access /usr/local. (I also do the same thing with the pkgng pkg-static binary...) Glen pgp5uu6hcqIM4.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 02:28:05AM +0200, Claude Buisson wrote: - the recently created snapshots.glenbarber.us is much more limited May I ask what it is that is limiting? If there is some limitation, I certainly will do what I can to address it. Right now, the limitations I am already aware of are: [...] You said it, I have nothing to add. Thank you for clarifying. Hopefully within the next few days, I'll have the stable/8 snapshot building issue fixed.[1] The space issue, right now, is a bit out of my control at the moment. [1] For reference on why the stable/8 snapshots are a problem for me, I am building all snapshots on a single 64-bit machine. The normal magic used by the release build script on -CURRENT does not work out-of-box because additional make(1) flags are required and/or incompatible with the flags for the stable/9 and head/ branches. As mentioned in my original email, I certainly do welcome feedback. I certainly will do what I can to address any issues and/or limitations. Do not misinterpret my mail: I really think that your work is useful. No misinterpretation at all. I appreciate the feedback. Glen pgpMrkXA43TS5.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 02:34:56AM +0200, Claude Buisson wrote: FWIW, you can compile the svn binary elsewhere, statically linked, and save the dependency problem by copying the resulting binary around. Lucky people who have an elsewhere. And the static binary is as much bloated than the dynamic ones. Compare it with this poor csup, which gave great services for a small price. Agreed on all counts. For what it is worth, my response was really geared with the mindset of having a cluster of machines to administer, where having the extra (sometimes unnecessary) dependencies of svn are not ideal and/or can conflict with other software. As mentioned in today's earlier announcement for 9.1-RC2, however, CVS backporting from SVN will continue to be done for the stable/9 branch. Hopefully that buys some time for svnup to become reality. Glen pgp5qBGIEgJBQ.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 12:42:21PM +0200, Claude Buisson wrote: I understood that. At a time I have been in that situation, but to be there I had to sell the use of FreeBSD at my $WORK, and started with a single machine and limited ressources. So the existence of a cluster even for people doing real production work with FreeBSD is not a given. Fair enough point. As mentioned in today's earlier announcement for 9.1-RC2, however, CVS backporting from SVN will continue to be done for the stable/9 branch. One of the starting point of this thread have been that according to cvsweb, there does not seem to have been any update of releng7, releng8, and releng9 at least since October 5 or 6, which is confirmed by cvsup1.fr.freebsd.org (I have just done the test for releng8). So something is not working somewhere, and someone may ask do somebody care about it ? Sorry to have started so long a thread. I asked essentially the same questions about cvs/csup/mirrors, etc more than a year ago without real answer.. Sorry if your original email about the mirror went overlooked or unanswered. Can you please file a PR about cvsup1.fr ? There are two immediate issues regarding that: 1.) I (personally) do not have a way to check on the status of that machine's syncing; 2.) Some machines within the FreeBSD.org infrastructure are being moved around/upgraded/duct-taped, etc. So, while thus far it has been minimal, user-facing issues may have occurred. So, until all of the moving things around is done, a PR will be the best way to ensure your report does not further go unanswered. Glen pgpivJevD6Pwk.pgp Description: PGP signature
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Thu, Oct 11, 2012 at 02:43:07PM +0200, Claude Buisson wrote: I do not see a real interest of filling a PR for cvsup1.fr. I have just done the same test with the same result with cvsup5.de and cvsup10.us. www.mavetju.org/unix/freebsd-mirrors/ have all cvsup mirrors in red, and IIRC someone wrote on hubs@ that the current test for mirrors was flawed because it tried at a now inexistent file. And someone else wrote that the project does not want anymore mirrors which are not under its direct control. I will do what I can to look into this. It is clear that there have been a problem at least with lists.freebsd.org, but what astonishes me is the fact that in our glorious 21th century, nobody thought to inform people on the mailing lists, or on the home page of www.freebsd.org (no, I do not want to be on Twitter or FaceBook for that kind of information). I absolutely understand, and appreciate your input about this. I am sorry that you feel people within the Project do not care. But, I assure you, that is not the case. I cannot speak for anyone but myself in the Project, but as someone who has direct access to make such a chanage to the FreeBSD.org website, I apologize for the lack of announcement. You are right - there should have been some sort of Some services may be disrupted for a bit, or similar there. I am sorry this was not done. Thank you for taking the pain of reading my emails. Thank you for taking the time to outline your concerns. Glen pgptkkFCcgn6r.pgp Description: PGP signature
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: Am Fri, 19 Oct 2012 11:32:49 -0700 schrieb Adrian Chadd adr...@freebsd.org: Guys/girls/etc, I do suggest that someone actually spends some time coming up with a table of what the current state is, what we could do, what would happen if we did that. Right now there's a lot of possibilities (new drive, drive with windows, drive with linux, drive with linux/windows, drive with legacy freebsd MBR, etc) and as an outsider trying to figure out what is actually the right sounding behaviour, it's difficult for me to sit down and digest all these emails that chip away at a bit of the problem at a time. So if you'd like to see this fixed, I really do suggest that one of you dumps some time into coming up with a basic table like I said above, work with others who can correct/flesh out the various options to take into account, and then we can come up with a real solution. Then 9.1 can go out the door. If I select the entire disk for FreeBSD, I think it's a reasonable assumption that the MBR should replaced, too. Please don't make people install FreeBSD 9.0 first on disks with non-FreeBSD MRRs and then upgrade to 9.1. Can you outline for me in detail what you did when you partitioned your drive during the installation? I have seen your specific issue exactly once, and reliably reproducing the problem has not been successful so far. BTW, what was on the drive before you did the install, if anything? Glen pgpgqmYglawAJ.pgp Description: PGP signature
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Sat, Oct 20, 2012 at 02:06:03AM +0200, Rainer Duffner wrote: Am Fri, 19 Oct 2012 17:11:30 -0400 schrieb Glen Barber g...@freebsd.org: On Fri, Oct 19, 2012 at 10:38:41PM +0200, Rainer Duffner wrote: If I select the entire disk for FreeBSD, I think it's a reasonable assumption that the MBR should replaced, too. Please don't make people install FreeBSD 9.0 first on disks with non-FreeBSD MRRs and then upgrade to 9.1. Can you outline for me in detail what you did when you partitioned your drive during the installation? I chose entire disk, then deleted all partitions-suggestions except the first one and created my own partitioning scheme. (/, swap, var, usr, maybe /var/log and /home, too) Ok, this is similar to my case. I have seen your specific issue exactly once, and reliably reproducing the problem has not been successful so far. BTW, what was on the drive before you did the install, if anything? It had a version of Solaris. Maybe Opensolaris. I don't know exactly. And I don't know if it had zfsroot or not. I created a HW-RAID1 with the HP P400 controller on it. The drives were previously used in another server. Ok, as long as they were not new drives. Thank you. I tried to install 9.1RC2 twice on these disks and it always went back to the grub-prompt after reboot. Then I installed 9.0 and it's running now. The grub prompt for (Open)Solaris? Or do you use grub on FreeBSD? I _think_ at this point, you've hit the same problem I hit, the only difference is that in my case, 9.1-PRERELEASE was installed twice, because the paritions were not ideal. So, my guess is if you were to boot the install cd and select 'Live CD' or 'Shell' from the first menu option, and wrote the GPT bootcode to da0p1 (assuming da0 is the drive) and reboot, it would have booted fine. In my case, the disk originally had an older FreeBSD install, so had an existing MBR. The odd thing though is that the system was bootable before the second installation. Glen pgpHsNFOoxOFQ.pgp Description: PGP signature
Re: 9.1 and intel graphics
On Sat, Oct 20, 2012 at 06:14:08AM +0200, Zoran Kolic wrote: Yesterday I have gotten lenovo e320 laptop, with core i3 2350 and HD3000 integrated. Gonna wait few days till 9.1 release. I never used anything aside intel on my old laptop. Kostik Belousov made a port of kms and I found patches from june and jule on the net. What should I do after 9.1 install in this case? I assume kms is in xorg. Do I have to find and install some driver from intel? Do I need to change xorg.conf after configure flag, that will make conf file? The i915kms driver is in the 9-STABLE branch, I am not 100% certain if it is what will be 9.1-RELEASE. Finally, what happens when I leave x and want to go back to console mode? Currently, you cannot go back to console once i915kms is loaded. I tried out live RC2 from usb stick. Few acpi errors, intel 1000 wifi found. After some time sysctl hw.acpi gave me the cpu temperature of 50C. Fan was on. Probably temp gonna go down when I add powerd and cx_lowest to rc.conf on hdd. Is it normal temp for this cpu? Yes. Glen pgpT4jLjdJF4M.pgp Description: PGP signature
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Sat, Oct 20, 2012 at 07:04:02PM +0200, Rainer Duffner wrote: Am Fri, 19 Oct 2012 20:14:01 -0400 schrieb Glen Barber g...@freebsd.org: The grub prompt for (Open)Solaris? Or do you use grub on FreeBSD? I thought it was a linux grub (the Firmware-Update DVD is linux-based and I thought it had gone postal. But I came to realize that it was the Solaris grub. We only use FreeBSD on servers and it's always the only OS on the disks. Ok, thank you. I did not want to assume anything here. I _think_ at this point, you've hit the same problem I hit, the only difference is that in my case, 9.1-PRERELEASE was installed twice, because the paritions were not ideal. So, my guess is if you were to boot the install cd and select 'Live CD' or 'Shell' from the first menu option, and wrote the GPT bootcode to da0p1 (assuming da0 is the drive) and reboot, it would have booted fine. I don't think this is what a user is expecting from an OS installation routine It's a bug. Oh, I agree. For what it is worth, when I ran into this, I just merely thought I did something wrong during the install, so writing the gptboot code to the drive was my quick fix. I originally didn't bother reproducing it, until about an hour later when I saw this thread start. The frustrating part now is I have had zero luck reproducing the problem... Glen pgphxMV76cJHy.pgp Description: PGP signature
Re: 9.1-RC2 - could it be that the installer does not write the MBR?
On Fri, Oct 19, 2012 at 10:21:54PM -0600, Warren Block wrote: I don't know if this is the problem, but it is worth pointing out that graid(8) is now included in GENERIC. Leftover hardware RAID metadata could make for unexpected results. For example, http://forums.freebsd.org/showthread.php?t=35168 Definitely worth noting. GEOM_MIRROR can do this too, iirc. In my case, however, the target installation disk was not previously part of any RAID configuration, software or otherwise. Glen pgp8wbcOjFYRp.pgp Description: PGP signature
Re: make release fails on find
On Tue, Oct 30, 2012 at 04:58:52PM +0100, Andreas Nilsson wrote: I'm trying to build some images for 9-stable ( r242349 ) and 9.1-RC3, but using the release tools doesn't really work. 9.1-RC3 fails with: ... cd /tank/cvs/9.1/src/libexec/rtld-elf; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 -C -b -fschg -S ld-elf32.so.1 /tmp/newdist/lib32/libexec /tmp/newdist/lib32/usr/libexec/ld-elf32.so.1 - /libexec/ld-elf32.so.1 cd /tank/cvs/9.1/src/usr.bin/ldd; PROG=ldd32 MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU=i686 mmx sse sse2 LD=ld -m elf_i386_fbsd -Y P,/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 AS=as --32 MAKEOBJDIRPREFIX=/usr/obj/lib32 _SHLIBDIRPREFIX=/usr/obj/tank/cvs/9.1/src/lib32 VERSION=FreeBSD 9.1-PRERELEASE amd64 901501 PATH=/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/legacy/usr/games:/usr/obj/tank/cvs/9.1/src/tmp/usr/sbin:/usr/obj/tank/cvs/9.1/src/tmp/usr/bin:/usr/obj/tank/cvs/9.1/src/tmp/usr/games:/tmp/install.SgiYOaRS CC=cc -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 CXX=c++ -m32 -march=core2 -DCOMPAT_32BIT -isystem /usr/obj/tank/cvs/9.1/src/lib32/usr/include/ -L/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 -B/usr/obj/tank/cvs/9.1/src/lib32/usr/lib32 LIBDIR=/usr/lib32 SHLIBDIR=/usr/lib32 make -DNO_CPU_CFLAGS -DCOMPAT_32BIT -DWITHOUT_BIND -DWITHOUT_MAN -DWITHOUT_INFO -DWITHOUT_HTML -DNO_CTF -DNO_LINT -ECC -ECXX -EAS -ELD -DNO_INCS distribute cd /tank/cvs/9.1/src/usr.bin/ldd; make install -DNO_SUBDIR DESTDIR=/tmp/newdist/lib32 SHARED=copies install -s -o root -g wheel -m 555 ldd32 /tmp/newdist/lib32/usr/bin find //tmp/newdist/doc -empty -delete find //tmp/newdist/games -empty -delete find: -delete: //tmp/newdist/games: relative path potentially not safe *** [distributeworld] Error code 1 Stop in /tank/cvs/9.1/src. *** [distributeworld] Error code 1 Are you defining WITH*_GAMES in src.conf or make.conf? If this looks like what I think it looks like, I fixed this a few months ago. And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. I have seen many reports on this, and cannot reproduce it. How exactly are you running the release build? What specific make(1) targets are you using, and what is your make.conf/src.conf contents? Glen pgp1qPZ1OYPTB.pgp Description: PGP signature
Re: make release fails on find
On Tue, Oct 30, 2012 at 05:32:20PM +0100, Andreas Nilsson wrote: Are you defining WITH*_GAMES in src.conf or make.conf? If this looks like what I think it looks like, I fixed this a few months ago. Used same command for building both, see below. And yes, WITHOUT_GAMES is set in src.conf And 9-stable ends up recursing when generating tarballs. The sources have already been added to a tarball. The tarballs themselfs are also included. I have seen many reports on this, and cannot reproduce it. How exactly are you running the release build? What specific make(1) targets are you using, and what is your make.conf/src.conf contents? Glen I did the following steps: zfs create tank/cvs/9 zfs create tank/cvs/9/src zfs create tank/cvs/9.1 zfs create tank/cvs/9.1/src cd /tank/cvs/9/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9 . cd /tank/cvs/9.1/src ; sudo svn co http://svn0.us-east.freebsd.org/base/releng/9.1 . cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf buildworld buildkernel -sj16 cd /tank/cvs/9/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom cd /tank/cvs/9.1/src ; sudo make SRCCONF=/relng/files/src.conf -C release cdrom /relng/files/src.conf contains: $ cat /relng/files/src.conf WITHOUT_X11=true WITHOUT_BLUETOOTH=true WITHOUT_CLANG=true WITHOUT_ATM=true WITHOUT_CTM=true WITHOUT_CDDL=true WITHOUT_DICT=true WITHOUT_HTML=true WITHOUT_IPFILTER=true WITHOUT_IPX=true WITHOUT_IPX_SUPPORT=true WITHOUT_LOCALES=true WITHOUT_LPR=true WITHOUT_NCP=true WITHOUT_NIS=true WITHOUT_OBJC=true WITHOUT_RCMDS=true WITHOUT_RCS=true WITHOUT_SENDMAIL=true WITHOUT_SSP=true WITHOUT_ZFS=true WITHOUT_BIND_DNSSEC=true WITHOUT_GAMES=true WITHOUT_IPX=true WITHOUT_NIS=true WITHOUT_PF=true WITHOUT_SENDMAIL=true WITHOUT_WIRELESS=true make.conf contains: $ cat /etc/make.conf CPUTYPE?=core2 CFLAGS=-pipe -O2 BUILD_JOBS=8 WITHOUT_SENDMAIL=true WITHOUT_X11=true DISTDIR=/tank/distfiles WRKDIRPREFIX?=/tmp/ports PACKAGES?=/tmp/ports/packages # WITH_KMS=yes WITH_NEW_XORG=yes # added by use.perl 2012-10-15 17:24:41 PERL_VERSION=5.14.2 I don't really see any reason this should not work. However, I have not tested with sudo. Maybe that is the piece of the puzzle I am missing... Glen pgpkeDSe8cbhC.pgp Description: PGP signature
Re: make release fails on find
On Wed, Oct 31, 2012 at 12:11:22AM +0100, Andreas Nilsson wrote: interesting idea, would be pretty bad if sudo caused that. Indeed, but sudo only keeps certain environment variables, so it's not entirely unexpected if this is the case. I gave it run without direct sudo call ( ie sudo bash, then make ... ) and no go. Doing just su - and cd'ing to proper dir and the make ... is still not working. Overnight I'll try to build world and kernel without src.conf ( ie SRCCONF=/dev/null ) and same for make release. I'll posts results in the morning. Best regards Andreas Just a quick update; running a new buildworld+buildkernel and then make release from su - does not work :( You've said 'does not work' twice. Can you elaborate more? What specifically isn't working? Same behavior as before, or...? Glen pgpGFWkI2sv3Y.pgp Description: PGP signature
Re: make release fails on find
On Wed, Oct 31, 2012 at 01:08:13AM +0100, Andreas Nilsson wrote: On Wed, Oct 31, 2012 at 12:14 AM, Glen Barber g...@freebsd.org wrote: On Wed, Oct 31, 2012 at 12:11:22AM +0100, Andreas Nilsson wrote: interesting idea, would be pretty bad if sudo caused that. Indeed, but sudo only keeps certain environment variables, so it's not entirely unexpected if this is the case. I gave it run without direct sudo call ( ie sudo bash, then make ... ) and no go. Doing just su - and cd'ing to proper dir and the make ... is still not working. Overnight I'll try to build world and kernel without src.conf ( ie SRCCONF=/dev/null ) and same for make release. I'll posts results in the morning. Best regards Andreas Just a quick update; running a new buildworld+buildkernel and then make release from su - does not work :( You've said 'does not work' twice. Can you elaborate more? What specifically isn't working? Same behavior as before, or...? Glen Oops, my bad. Yes exact same behavior; make -C release cdrom fails with ... find //tank/cvs/9.1/src/release/dist/doc -empty -delete find //tank/cvs/9.1/src/release/dist/games -empty -delete find: -delete: //tank/cvs/9.1/src/release/dist/games: relative path potentially not safe *** [distributeworld] Error code 1 on 9.1-RC3. I can try with 9-stable as well (tomorrow). Ok, thanks. I do not want to assume anything more at this point. I am still waiting for my build machine to finish a few queued things. Once it frees up, I will roll a release using sudo (just for my own sanity), and without sudo, with your src.conf and make.conf. Anyway, thanks for all of the details you have provided. It is all helpful, and hopefully this will finally be tracked down. Glen pgpCDfFa5wvv4.pgp Description: PGP signature
Re: make release fails on find
On Tue, Oct 30, 2012 at 08:11:15PM -0400, Glen Barber wrote: Oops, my bad. Yes exact same behavior; make -C release cdrom fails with ... find //tank/cvs/9.1/src/release/dist/doc -empty -delete find //tank/cvs/9.1/src/release/dist/games -empty -delete find: -delete: //tank/cvs/9.1/src/release/dist/games: relative path potentially not safe *** [distributeworld] Error code 1 on 9.1-RC3. I can try with 9-stable as well (tomorrow). Ok, thanks. I do not want to assume anything more at this point. I am still waiting for my build machine to finish a few queued things. Once it frees up, I will roll a release using sudo (just for my own sanity), and without sudo, with your src.conf and make.conf. Anyway, thanks for all of the details you have provided. It is all helpful, and hopefully this will finally be tracked down. Ugh... Ok, so this is my fault. I do not remember why, specifically, but the change in question was not merged to the releng/9.1 branch. Please try the following, in the top-level directory of your releng/9.1 source checkout: svn merge -c240077 ^/head/Makefile.inc1 Makefile.inc1 It worked for me fine. Unfortunately, it is far too late in the release cycle for that change to make it into 9.1-RELEASE. Unfortunately, this does not have anything to do with the recursing in the usr/src tarball. Please let me know if you continue to see that happen, as this is the _single_ most reported issue that I have had zero luck reproducing... Thanks. Glen PS: Sorry about being the cause of your release build failure... pgpt3EepG3RGa.pgp Description: PGP signature
Re: make release fails on find
On Tue, Oct 30, 2012 at 11:07:24PM -0400, Glen Barber wrote: I do not remember why, specifically, but the change in question was not merged to the releng/9.1 branch. Please try the following, in the top-level directory of your releng/9.1 source checkout: svn merge -c240077 ^/head/Makefile.inc1 Makefile.inc1 It worked for me fine. Unfortunately, it is far too late in the release cycle for that change to make it into 9.1-RELEASE. To be clear, I mean the release build worked. Unfortunately, this does not have anything to do with the recursing in the usr/src tarball. Please let me know if you continue to see that happen, as this is the _single_ most reported issue that I have had zero luck reproducing... And, look at that. I'm finally able to reproduce this recursion problem. Looks that that, too, was fixed in head, but not merged. So, please also do: svn merge -c241451 ^/head/release release At that point, things _should_ work as you expect. Please let me know how this works out for you. Glen pgpnGQJisRpYK.pgp Description: PGP signature
Re: make release fails on find
On Tue, Oct 30, 2012 at 11:19:12PM -0400, Glen Barber wrote: So, please also do: svn merge -c241451 ^/head/release release You'll want to merge one more revision: svn merge -c241596 ^/head/release release Same as before - I _think_ this should work. :-) Glen pgpQRYOYHWRns.pgp Description: PGP signature
Re: make release fails on find
On Wed, Oct 31, 2012 at 02:07:56PM +0100, Andreas Nilsson wrote: First, late me state status more clearly: solved :) Big thanks for fixing it. Glad to help. To answer one of your previous questions, I've already merged this to stable/9. On a side note, how has re-team not run into this? No, the releases are built within a chroot, and this issue is specific to a few edge-cases outside of that environment. Glen pgpGlkk4SQM1i.pgp Description: PGP signature
