Re: make fetchindex in /usr/ports failing with Authentication error
Nevermind. I found an email that I had received last month that explained that I had to make install ca_root_nss. Did that and all is well with make fetchindex now. Bob On Mon, Mar 23, 2020 at 03:57:30PM -0500, Bob Willcox wrote: > I just updated my /usr/ports on my 13.0-current system and after that > completed I tried to > run 'make fetchindex' and got a continuous stream of these errors written to > the display: > > fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error > Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt > Authority X3 > 34370576384:error:1416F086:SSL > routines:tls_process_server_certificate:certificate verify > failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: > > Anyone have any idea what I have wrong or am missing? This was previously > working on this > system (and make fetchindex works on my 12.1 systems ok). > > Thanks, > Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
make fetchindex in /usr/ports failing with Authentication error
I just updated my /usr/ports on my 13.0-current system and after that completed I tried to run 'make fetchindex' and got a continuous stream of these errors written to the display: fetch: https://www.FreeBSD.org/ports/INDEX-13.bz2: Authentication error Certificate verification failed for /C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3 34370576384:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: Anyone have any idea what I have wrong or am missing? This was previously working on this system (and make fetchindex works on my 12.1 systems ok). Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Build failed compiling ittnotify_static.pico
My 13.0-current system (just updated about 2 hours ago) that is failing with this error when trying to do a 'make makeworld' --- ittnotify_static.pico --- cc -target x86_64-unknown-freebsd13.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -fpic -DPIC -O2 -pipe -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/usr/src/lib/libomp -I/usr/src/contrib/llvm-project/openmp/runtime/src -I/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify -ffunction-sections -fdata-sections -g -MD -MF.depend.ittnotify_static.pico -MTittnotify_static.pico -std=gnu99 -Wno-format-zero-length -fstack-protector-strong -Wno-atomic-alignment -Wsystem-headers -Werror -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments-c /usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittno tify_static.c -o ittnotify_static.pico cc: error: no such file or directory: '/usr/src/contrib/llvm-project/openmp/runtime/src/thirdparty/ittnotify/ittnotify_static.c' cc: error: no input files *** [ittnotify_static.pico] Error code 1 Anyone else seeing this? Any suggestions for a fix? Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 11:11:53AM +0100, Michael Gmelin wrote: > > > On Thu, 12 Mar 2020 10:31:40 +0100 > Alexander Leidinger wrote: > > > Hi, > > > > This command sets the keyboard layout. You are supposed to set the > > keyboard layout which matches the physical layout of the hardware. > > This hadn't changed, it's a fundamental part of X11 since I know it > > (X11 6.5) and even before... > > [snip] > > Exactly. I just personally prefer to use setxkbmap, as all my setups are > single user (one unprivileged user per machine that runs X, no shared > machines) and customization happens in $HOME that way. Makes it a > bit easier to setup a new machine (no digging in Xorg configs) and > reading ~/.xinitrc basically tells me all about my current config. > > Plus, setxkbmap makes it easy to experiment, as it's applies changes > while X is running, even if one makes the those changes permanently in > an xorg config file later. And the resulting command is just one line > (in my case as short as "setxkbmap -model pc105 -layout de"), makes it > easier to support people. > > Another useful application of the command is for debugging: > "setxkbmap -query" will tell you what's currently configured (regardless > how that configuration was done), e.g., > > On a machine running xorg 1.18: > > # setxkbmap -query > rules: base > model: pc105 > layout: de > > On a machine running xorg 1.20: > rules: evdev > model: pc105 > layout: de > > In both cases the same setxkbmap command was used in ~/.xinitrc to set > model and layout. Rules were taken from Xorg's default config, which > changed to evdev in 1.20. I ran "setxkbmap -query" on my home workstation that hasn't had X updated on it yet and this is what I got: rules: base model: pc105 layout: us So presumably that was the default setting from when I installed the system last April. I plan to run this again after I update xorg on this system, but not too sure when I'll get to that. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 04:53:32PM +0100, Michael Gmelin wrote: > > > On Thu, 12 Mar 2020 10:36:42 -0500 > Bob Willcox wrote: > > > On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > > > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > > > > > > SNIP SNAP > > > > >> It might fix the ???Down key opens application launcher??? > > > > >> problem by applying the correct keymap (you have to select the > > > > >> correct one, ???de??? probably won???t cut it for you). At > > > > >> least it did with xfce, where it was important to run it > > > > >> before the wm starts - you could also try running it > > > > >> afterwards to see if it makes a difference. > > > > > > > > > > I don't know about that problem. What I'm experiencing is the > > > > > Alt-up,down,left,right keys don't work as they used to in my > > > > > ctwm window manager. They used to move the current window to > > > > > the closest boundry in the direction indicated by the key that > > > > > is also pressed (while holding the Alt key down). Also, > > > > > Alt-shift-up,down,left,right would expand the window in the > > > > > direction indicated by the key. These actions seem to do > > > > > nothing now. > > > > > > > > I don???t know much about ctwm, but why don???t you give it a > > > > shot? > > > > > > I plan to sometime today when I get into the office. But since it's > > > my work system and I am dependent on it to do my job, I've just > > > been a little hesitant. > > > > Ok, I added this to my ~/.xinitrc file: > > > > setxkbmap -model pc105 -layout us > > > > and my ctwm window adjustment hot keys are working again. :) > > > > I do wonder why it was deemed ok to change the default behavior for > > the key mappings? Couldn't the default mappings have remained the > > same with change to evdev? This change certainly violated the > > "principle of least surprise" for me. > > > > > > I think the change was unavoidable, but it could've been communicated > better. Then again, time and resources are limited and I'm quite > grateful the graphics team finally made that necessary push forward. > > I'm curious how people set their keyboard layout in the past though, > is it possible that the defaults just worked for US users? I always had > to set it explicitly (setxkbmap or in Xorg.conf), so I was never really > affected by this change. > > -m > > p.s. What does "setxkbmap -query" show if you start X without setting > the keymap in .xinitrc? I'll have to try that when I get home tonight on one of my other systems as I really can't afford to take the time to restart X on this system now...got to get some work done. :) Bob > > -- > Michael Gmelin -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Thu, Mar 12, 2020 at 07:24:42AM -0500, Bob Willcox wrote: > On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > > >> > > >> > > >>>> On 11. Mar 2020, at 22:58, Bob Willcox wrote: > > >>> > > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > > >>>> ??? > > >>>>>> On 11. Mar 2020, at 10:29, Mark Martinec > > >>>>>> wrote: > > >>>>> ??? > > >>>>>> > > >>>>>>> I just updated my laptop from source, and somewhere along the way > > >>>>>>> the key-codes Xorg sees changed. > > >>>>>> Indeed. This doesn't just affect -CURRENT: it happened to me on > > >>>>>> -STABLE last week, so I'm copying that list too. > > >>>>> > > >>>>> And a "Down" key now opens and closes a KDE "Application Launcher", > > >>>>> alternatively with its original function (which makes editing a > > >>>>> frustration). > > >>>>> > > >>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > >>>>> > > >>>>> > > >>>> > > >>>> This *might* help you: > > >>>> > > >>>> https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > >>>> > > >>>> (Short version: run setxkbmap in ~/.xinitrc, e.g., > > >>>> setxkbmap -model pc105 -layout de) > > >>> > > >>> Will running that command return my key mappings back to what they use > > >>> to be? > > >>> > > >> > > >> It might fix the ???Down key opens application launcher??? problem by > > >> applying the correct keymap (you have to select the correct one, > > >> ???de??? probably won???t cut it for you). At least it did with xfce, > > >> where it was important to run it before the wm starts - you could also > > >> try running it afterwards to see if it makes a difference. > > > > > > I don't know about that problem. What I'm experiencing is the > > > Alt-up,down,left,right keys > > > don't work as they used to in my ctwm window manager. They used to move > > > the current window > > > to the closest boundry in the direction indicated by the key that is also > > > pressed (while > > > holding the Alt key down). Also, Alt-shift-up,down,left,right would > > > expand the window in > > > the direction indicated by the key. These actions seem to do nothing now. > > > > > > > I don???t know much about ctwm, but why don???t you give it a shot? > > I plan to sometime today when I get into the office. But since it's my work > system and I > am dependent on it to do my job, I've just been a little hesitant. Ok, I added this to my ~/.xinitrc file: setxkbmap -model pc105 -layout us and my ctwm window adjustment hot keys are working again. :) I do wonder why it was deemed ok to change the default behavior for the key mappings? Couldn't the default mappings have remained the same with change to evdev? This change certainly violated the "principle of least surprise" for me. > > Bob > > -- > Bob Willcox| It's possible that the whole purpose of your life is to > b...@immure.com | serve as a warning to others. > Austin, TX | -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 11:46:49PM +0100, Michael Gmelin wrote: > > > > On 11. Mar 2020, at 23:25, Bob Willcox wrote: > > > > ???On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > >> > >> > >>>> On 11. Mar 2020, at 22:58, Bob Willcox wrote: > >>> > >>> ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > >>>> ??? > >>>>>> On 11. Mar 2020, at 10:29, Mark Martinec > >>>>>> wrote: > >>>>> ??? > >>>>>> > >>>>>>> I just updated my laptop from source, and somewhere along the way > >>>>>>> the key-codes Xorg sees changed. > >>>>>> Indeed. This doesn't just affect -CURRENT: it happened to me on > >>>>>> -STABLE last week, so I'm copying that list too. > >>>>> > >>>>> And a "Down" key now opens and closes a KDE "Application Launcher", > >>>>> alternatively with its original function (which makes editing a > >>>>> frustration). > >>>>> > >>>>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > >>>>> > >>>>> > >>>> > >>>> This *might* help you: > >>>> > >>>> https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > >>>> > >>>> (Short version: run setxkbmap in ~/.xinitrc, e.g., > >>>> setxkbmap -model pc105 -layout de) > >>> > >>> Will running that command return my key mappings back to what they use to > >>> be? > >>> > >> > >> It might fix the ???Down key opens application launcher??? problem by > >> applying the correct keymap (you have to select the correct one, ???de??? > >> probably won???t cut it for you). At least it did with xfce, where it was > >> important to run it before the wm starts - you could also try running it > >> afterwards to see if it makes a difference. > > > > I don't know about that problem. What I'm experiencing is the > > Alt-up,down,left,right keys > > don't work as they used to in my ctwm window manager. They used to move the > > current window > > to the closest boundry in the direction indicated by the key that is also > > pressed (while > > holding the Alt key down). Also, Alt-shift-up,down,left,right would expand > > the window in > > the direction indicated by the key. These actions seem to do nothing now. > > > > I don???t know much about ctwm, but why don???t you give it a shot? I plan to sometime today when I get into the office. But since it's my work system and I am dependent on it to do my job, I've just been a little hesitant. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 11:04:18PM +0100, Michael Gmelin wrote: > > > > On 11. Mar 2020, at 22:58, Bob Willcox wrote: > > > > ???On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > >> ??? > >>>> On 11. Mar 2020, at 10:29, Mark Martinec > >>>> wrote: > >>> ??? > >>>> > >>>>> I just updated my laptop from source, and somewhere along the way > >>>>> the key-codes Xorg sees changed. > >>>> Indeed. This doesn't just affect -CURRENT: it happened to me on > >>>> -STABLE last week, so I'm copying that list too. > >>> > >>> And a "Down" key now opens and closes a KDE "Application Launcher", > >>> alternatively with its original function (which makes editing a > >>> frustration). > >>> > >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > >>> > >>> > >> > >> This *might* help you: > >> > >> https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > >> > >> (Short version: run setxkbmap in ~/.xinitrc, e.g., > >> setxkbmap -model pc105 -layout de) > > > > Will running that command return my key mappings back to what they use to > > be? > > > > It might fix the ???Down key opens application launcher??? problem by > applying the correct keymap (you have to select the correct one, ???de??? > probably won???t cut it for you). At least it did with xfce, where it was > important to run it before the wm starts - you could also try running it > afterwards to see if it makes a difference. I don't know about that problem. What I'm experiencing is the Alt-up,down,left,right keys don't work as they used to in my ctwm window manager. They used to move the current window to the closest boundry in the direction indicated by the key that is also pressed (while holding the Alt key down). Also, Alt-shift-up,down,left,right would expand the window in the direction indicated by the key. These actions seem to do nothing now. Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: New Xorg - different key-codes
On Wed, Mar 11, 2020 at 02:48:56PM +0100, Michael Gmelin wrote: > ??? > >> On 11. Mar 2020, at 10:29, Mark Martinec > >> wrote: > > ??? > >> > >>> I just updated my laptop from source, and somewhere along the way > >>> the key-codes Xorg sees changed. > >> Indeed. This doesn't just affect -CURRENT: it happened to me on > >> -STABLE last week, so I'm copying that list too. > > > > And a "Down" key now opens and closes a KDE "Application Launcher", > > alternatively with its original function (which makes editing a > > frustration). > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244354 > > > > > > This *might* help you: > > https://lists.freebsd.org/pipermail/freebsd-x11/2020-February/025046.html > > (Short version: run setxkbmap in ~/.xinitrc, e.g., > setxkbmap -model pc105 -layout de) Will running that command return my key mappings back to what they use to be? -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Mon, Mar 09, 2020 at 08:35:58AM -0700, Cy Schubert wrote: > On March 9, 2020 7:49:34 AM PDT, Ed Maste wrote: > >On Sun, 8 Mar 2020 at 13:23, Bob Willcox wrote: > >> > >> Thanks for the tip! That worked for me. I guess from reading the > >documentation > >> I didn't pick up on staying with the symlinks and simply changing > >host to net. > > > >Glad it's working for you! Is there anything else that you found > >tricky or surprising in migrating? Perhaps we could produce a > >quick-reference transition guide. > >___ > >freebsd-current@freebsd.org mailing list > >https://lists.freebsd.org/mailman/listinfo/freebsd-current > >To unsubscribe, send any mail to > >"freebsd-current-unsubscr...@freebsd.org" > > /net and indirect maps should be simple conversations. Direct maps may or may > not be easy. Autofs doesn't support nested direct maps like amd does. You may > need to mount elsewhere or use /net with symlinks. > > We do have a port as well. The port will be retired after a reasonable amount > of time to allow people to convert. Amd upstream has told me he no longer > supports amd. His advice is to use autofs. Yes, and I considered installing the amd port but that just seemed like I'd be postponing the inevitable. Since I had a simple use case of just using symlinks to about four of my remote filesystems, switching from using the /host symlink to the /net symlink was pretty easy. -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Mon, Mar 09, 2020 at 10:49:34AM -0400, Ed Maste wrote: > On Sun, 8 Mar 2020 at 13:23, Bob Willcox wrote: > > > > Thanks for the tip! That worked for me. I guess from reading the > > documentation > > I didn't pick up on staying with the symlinks and simply changing host to > > net. > > Glad it's working for you! Is there anything else that you found > tricky or surprising in migrating? Perhaps we could produce a > quick-reference transition guide. Not sure, perhaps it was just my unfamiliarity with the features of autofs, but when I tried setting up a map file I was unable to get it to work as it never mounted the filesystem. I tried following the example in the auto_master man page in the "INDIRECT VERSUS DIRECT MAPS" section and created a auto_fsmount file with this in it: /work -intr,nfsv4 10.1.132.8:/stor/work and added this to the auto_master file: /- auto_fsmount Created the /work directory but couldn't get it to actually mount the filesystem. Removing all of those changes and creating this symlink instead: lrwxr-xr-x 1 root wheel19 Mar 8 12:19 work -> net/vader/stor/work worked and it automatically mounted the filesystem on my first access: vader:/stor/work 30T 19G 30T 0%/net/vader/stor/work So perhaps documenting how to migrate drom amd to autofs, retaining the same operational characteristics would be a help for those of us coming from that environment. Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Tue, Feb 04, 2020 at 08:15:05AM -0800, David Wolfskill wrote:
> On Tue, Feb 04, 2020 at 09:46:50AM -0600, Bob Willcox wrote:
> > ...
> > > Amd is not build by default now and will be removed from base. But you
> > > can continue using it by installing sysutils/am-utils from port.
> >
> > Thanks for the tip. I will likely go ahead and install the am-utils port as
> > from looking
> > at the setup and features of autofs it is way more complex and does more
> > than I need or
> > want. I've been using amd for decades now and it does exactly what I need
> > w/o any special
> > setup or configuration required. :)
> >
>
> I had also used amd from back when I still used a SPARCStation 5 as my
> home NFS (& yp) server, but switched with little fuss to autofs --
> primarily by using symlinks into /net/${host}/..., which works (for my
> purposes) just as well with either (amd or autofs).
>
> Peace,
> david
Thanks for the tip! That worked for me. I guess from reading the documentation
I didn't pick up on staying with the symlinks and simply changing host to net.
Thanks!
Bob
> --
> David H. Wolfskillda...@catwhisker.org
> "The Senate has abdicated its constitutional duty during the impeachment
> trial of President Donald Trump." -- Alan S. Frumin, parliamentarian
> emeritus of the US Senate
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--
Bob Willcox| It's possible that the whole purpose of your life is to
b...@immure.com | serve as a warning to others.
Austin, TX |
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Mon, Feb 03, 2020 at 03:28:29PM -0800, Conrad Meyer wrote: > Yep, amd is deprecated for 13.0: > https://svnweb.freebsd.org/base?view=revision=354902 , > https://svnweb.freebsd.org/base?view=revision=354997 . Ok, I've spent a couple of hours trying to get autofs to do the simple task of mounting my file server's nfs filesystems. With amd in the past all I needed to do was to create symlinks like this in /: lrwxr-xr-x 1 root wheel20 Apr 22 2019 work -> host/vader/stor/work Been doing that for years and it did exactly what I needed. I see that autofs adds lots of features (which I don't need) but the added complexity that comes with the added features (and the seemingly obscure documentation) has really made this much more difficult to understand. So, can someone help me understand how I would achieve the above result with autofs? Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Tue, Feb 04, 2020 at 08:15:05AM -0800, David Wolfskill wrote:
> On Tue, Feb 04, 2020 at 09:46:50AM -0600, Bob Willcox wrote:
> > ...
> > > Amd is not build by default now and will be removed from base. But you
> > > can continue using it by installing sysutils/am-utils from port.
> >
> > Thanks for the tip. I will likely go ahead and install the am-utils port as
> > from looking
> > at the setup and features of autofs it is way more complex and does more
> > than I need or
> > want. I've been using amd for decades now and it does exactly what I need
> > w/o any special
> > setup or configuration required. :)
> >
>
> I had also used amd from back when I still used a SPARCStation 5 as my
> home NFS (& yp) server, but switched with little fuss to autofs --
> primarily by using symlinks into /net/${host}/..., which works (for my
> purposes) just as well with either (amd or autofs).
I will likely look into autofs again at some point when I get a bit more time.
Right now
my goal was to get this system up and running so using something I'm familiar
with
expidites that.
Bob
>
> Peace,
> david
> --
> David H. Wolfskillda...@catwhisker.org
> "The Senate has abdicated its constitutional duty during the impeachment
> trial of President Donald Trump." -- Alan S. Frumin, parliamentarian
> emeritus of the US Senate
>
> See http://www.catwhisker.org/~david/publickey.gpg for my public key.
--
Bob Willcox| It's possible that the whole purpose of your life is to
b...@immure.com | serve as a warning to others.
Austin, TX |
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Is amd automount still supported in 13.0 or not?
On Tue, Feb 04, 2020 at 08:54:35AM +0900, Yasuhiro KIMURA wrote: > From: Bob Willcox > Subject: Is amd automount still supported in 13.0 or not? > Date: Mon, 3 Feb 2020 17:23:33 -0600 > > > I've recently installed a 13.0 snapshot on one of my system to get some > > experience with it > > and am having trouble trying to setup the amd automount program. In fact, I > > can't find amd > > on this system. Has amd been removed and all we have for automatically > > mounting > > filesystems autofs? > > Amd is not build by default now and will be removed from base. But you > can continue using it by installing sysutils/am-utils from port. Thanks for the tip. I will likely go ahead and install the am-utils port as from looking at the setup and features of autofs it is way more complex and does more than I need or want. I've been using amd for decades now and it does exactly what I need w/o any special setup or configuration required. :) I do wonder though, are there plans to remove it from ports? I hope not. I find autofs to be way overkill for my needs. Bob > > --- > Yasuhiro KIMURA > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Is amd automount still supported in 13.0 or not?
Hi All, I've recently installed a 13.0 snapshot on one of my system to get some experience with it and am having trouble trying to setup the amd automount program. In fact, I can't find amd on this system. Has amd been removed and all we have for automatically mounting filesystems autofs? Thanks, Bob -- Bob Willcox| It's possible that the whole purpose of your life is to b...@immure.com | serve as a warning to others. Austin, TX | ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 03:14:39PM -0700, Ngie Cooper wrote: > > > On Aug 11, 2017, at 12:34, Bob Willcox <b...@immure.com> wrote: > > > >> On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: > >> On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > >>>>> On Aug 11, 2017, at 10:36, Bob Willcox <b...@immure.com> wrote: > >>>>> > >>>>> When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > >>>>> modules were built: > >>>>> > >>>>> ipfw.ko > >>>>> ipfw_nat.ko > >>>>> ipfw_nat64.ko > >>>>> ipfw_nptv6.ko > >>>>> ng_ipfw.ko > >>>>> > >>>>> and only this ipfw module was built: > >>>>> > >>>>> ng_ipfw.ko > >>>>> > >>>>> However, the verson of /etc/rc.d/ipfw that I'm running (from the > >>>>> freebsd-base-graphics branch) is failing to load ipfw so my firewall > >>>>> isn't > >>>>> starting. > >>>>> > >>>>> So, what am I missing? Is it possible that the freebsd-base-graphics > >>>>> branch > >>>>> that I'm running has an old or improper version of /etc/rc.d/ipfw? > >> > >> [...] > >> > >>> include GENERIC_DRM > >> > >> GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are > >> built. In particular, ipfw*.ko does not get built. You'll need to either > >> remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make > >> kernel builds somewhat slower), or add > >> > >> makeoptionsMODULES_OVERRIDE+= ipfw ... > >> > >> to your custom config. > > Or add "MODULES_OVERRIDE+= ipfw..." to your src.conf. > Cheers, > -Ngie Well, I added the 'makeoptions MODULES_OVERRIDE+= ipfw' to my kernel config and rebuilt my kernel and it did build ipfw.ko as expected. I haven't installed this new kernel yet since I am not at a good point here at work to do that right now...but will when I get a chance. Thanks all for the help. -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: > On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > > > > On Aug 11, 2017, at 10:36, Bob Willcox <b...@immure.com> wrote: > > > > > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > > > modules were built: > > > > > > > > ipfw.ko > > > > ipfw_nat.ko > > > > ipfw_nat64.ko > > > > ipfw_nptv6.ko > > > > ng_ipfw.ko > > > > > > > > and only this ipfw module was built: > > > > > > > > ng_ipfw.ko > > > > > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > > > freebsd-base-graphics branch) is failing to load ipfw so my firewall > > > > isn't > > > > starting. > > > > > > > > So, what am I missing? Is it possible that the freebsd-base-graphics > > > > branch > > > > that I'm running has an old or improper version of /etc/rc.d/ipfw? > > [...] > > > include GENERIC_DRM > > GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are > built. In particular, ipfw*.ko does not get built. You'll need to either > remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make > kernel builds somewhat slower), or add > > makeoptions MODULES_OVERRIDE+= ipfw ... > > to your custom config. > > > > > ident TAVION_DRM > > > > nooptions INVARIANTS > > nooptions INVARIANT_SUPPORT > > nooptions DEBUG_MEMGUARD > > nooptions DEBUG_REDZONE > > nooptions WITNESS > > nooptions WITNESS_ALL > > nooptions WITNESS_SKIPSPIN > > > > options TMPFS Ok, thanks for that. I'll give that a try, but probably not till next time I am ready to update this system (I use it for my day job and updating it is a pain since I need to run the drm-next mods/branch). -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ipfw kernel module not being built
On Fri, Aug 11, 2017 at 12:55:14PM -0600, Ngie Cooper wrote: > > > On Aug 11, 2017, at 10:36, Bob Willcox <b...@immure.com> wrote: > > > > When I rebuild my kernel on Jun 13th none of the previous ipfw kernel > > modules were built: > > > > ipfw.ko > > ipfw_nat.ko > > ipfw_nat64.ko > > ipfw_nptv6.ko > > ng_ipfw.ko > > > > and only this ipfw module was built: > > > > ng_ipfw.ko > > > > However, the verson of /etc/rc.d/ipfw that I'm running (from the > > freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > > starting. > > > > So, what am I missing? Is it possible that the freebsd-base-graphics branch > > that I'm running has an old or improper version of /etc/rc.d/ipfw? > > Hi Bob, > Can you please provide your make.conf, src.conf, and KERNCONF? > Thank you! > -Ngie Sure. BTW, I cd'd into /usr/freebsd-base-graphics/sys/modules (my drm-next src is in /usr/freebsd-base-graphics), ran make, then copied the ipfw/ipfw.ko file to /boot/kernel and was able to start ipfw after that. * make.conf * KERNCONF= TAVION ALWAYS_CHECK_MAKE= yes BATCH= yes DEFAULT_VERSIONS+= linux=c6 DEFAULT_VERSIONS+= ssl=openssl COMPAT4X= yes COMPAT5X= yes COMPAT6X= yes COMPAT7X= yes COMPAT8X= yes COMPAT9X= yes * src.conf * -- doesn't exit * KERNCONF * # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the config(5) manual page, # and/or the handbook section on Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD$ include GENERIC_DRM ident TAVION_DRM nooptions INVARIANTS nooptions INVARIANT_SUPPORT nooptions DEBUG_MEMGUARD nooptions DEBUG_REDZONE nooptions WITNESS nooptions WITNESS_ALL nooptions WITNESS_SKIPSPIN options TMPFS -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ipfw kernel module not being built
When I rebuild my kernel on Jun 13th none of the previous ipfw kernel modules were built: ipfw.ko ipfw_nat.ko ipfw_nat64.ko ipfw_nptv6.ko ng_ipfw.ko and only this ipfw module was built: ng_ipfw.ko However, the verson of /etc/rc.d/ipfw that I'm running (from the freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't starting. So, what am I missing? Is it possible that the freebsd-base-graphics branch that I'm running has an old or improper version of /etc/rc.d/ipfw? -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: mount -t tmpfs tmpfs fails
On Sat, Jun 17, 2017 at 04:10:53PM -0700, Bryan Drewery wrote: > On 6/14/2017 12:14 PM, Bob Willcox wrote: > > I was attempting to run 'synth status' on my 12-current (drm-next) system > > and I got this error: > > > > root@tavion:0 /> synth status > > Querying system about current package installations. > > Stand by, comparing installed packages against the ports tree. > > > > raised REPLICANT.SCENARIO_UNEXPECTED : /sbin/mount -t tmpfs tmpfs > > /usr/obj/synth-live/SL09 => failed with code 1 > > > > So then I attempted just to do a mount of tmpfs command and got this: > > > > root@tavion:0 /> mount -t tmpfs x /tmp/xxx > > mount: x: Operation not supported by device > > I'm betting 'kldload tmpfs' fixes it. > > > > > synth used to work on this system prior to my recent upgrade to the latest > > drm-next branch (cloned from github and build from source). > > > > root@tavion:1 /> uname -a > > FreeBSD tavion.austin.ibm.com 12.0-CURRENT FreeBSD 12.0-CURRENT #1 > > da5f90154f1(drm-next): Tue Jun 13 16:58:52 CDT 2017 > > b...@tavion.austin.ibm.com:/usr/obj/usr/freebsd-base-graphics/sys/TAVION > > amd64 > > > > Any suggestions on what I should be looking for (or fixing)? > > > > Thanks, > > Bob > > If I could have loaded tmpfs it would have. But the tmpfs.ko module was not being built so it couldn't be loaded. I wound up cding into /usr/src/sys/modules/tmpfs and running make and make install to build and install it. After that kldload tmpfs did work. For some reason it isn't getting built on the system. Not when the kernel or world are built. Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: mount -t tmpfs tmpfs fails
On Wed, Jun 14, 2017 at 02:14:45PM -0500, Bob Willcox wrote: > I was attempting to run 'synth status' on my 12-current (drm-next) system > and I got this error: > > root@tavion:0 /> synth status > Querying system about current package installations. > Stand by, comparing installed packages against the ports tree. > > raised REPLICANT.SCENARIO_UNEXPECTED : /sbin/mount -t tmpfs tmpfs > /usr/obj/synth-live/SL09 => failed with code 1 > > So then I attempted just to do a mount of tmpfs command and got this: > > root@tavion:0 /> mount -t tmpfs x /tmp/xxx > mount: x: Operation not supported by device > > synth used to work on this system prior to my recent upgrade to the latest > drm-next branch (cloned from github and build from source). > > root@tavion:1 /> uname -a > FreeBSD tavion.austin.ibm.com 12.0-CURRENT FreeBSD 12.0-CURRENT #1 > da5f90154f1(drm-next): Tue Jun 13 16:58:52 CDT 2017 > b...@tavion.austin.ibm.com:/usr/obj/usr/freebsd-base-graphics/sys/TAVION > amd64 > > Any suggestions on what I should be looking for (or fixing)? > > Thanks, > Bob Ok, I finally figured out that my previous kernel must have had the tmpfs (and nullfs, it was a problem also with synth) built into the kernel, probably by default. Further, the tmpfs.ko and nullfs.ko modules weren't built and installed. I wound up building and installing both tmpfs and nullfs manually (cding to their respective src direcdories and running make; make install) to get synth to run. My only question remaining now is was the removal of the building and installing of these modules a fairly recent change in 12.0, or is something in my system hosed up? Thanks, Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
mount -t tmpfs tmpfs fails
I was attempting to run 'synth status' on my 12-current (drm-next) system and I got this error: root@tavion:0 /> synth status Querying system about current package installations. Stand by, comparing installed packages against the ports tree. raised REPLICANT.SCENARIO_UNEXPECTED : /sbin/mount -t tmpfs tmpfs /usr/obj/synth-live/SL09 => failed with code 1 So then I attempted just to do a mount of tmpfs command and got this: root@tavion:0 /> mount -t tmpfs x /tmp/xxx mount: x: Operation not supported by device synth used to work on this system prior to my recent upgrade to the latest drm-next branch (cloned from github and build from source). root@tavion:1 /> uname -a FreeBSD tavion.austin.ibm.com 12.0-CURRENT FreeBSD 12.0-CURRENT #1 da5f90154f1(drm-next): Tue Jun 13 16:58:52 CDT 2017 b...@tavion.austin.ibm.com:/usr/obj/usr/freebsd-base-graphics/sys/TAVION amd64 Any suggestions on what I should be looking for (or fixing)? Thanks, Bob -- Bob Willcox| Lawsuit, n.: A machine which you go into as a pig and b...@immure.com |come out as a sausage. Austin, TX |-- Ambrose Bierce ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: gfx-next update: drm-4.8-rc2 tagged in drm-next
Thanks Doug! This should be a big help as I was clueless as to where to begin. The URL for instructions appears to cover what I need. Bob On Tue, Sep 20, 2016 at 07:07:15PM +, Doug Kirk wrote: > Hi Bob, > > To start, you'll want to build and install the kernel from the "drm-next" > branch at https://github.com/FreeBSDDesktop/freebsd-base-graphics . > Instructions in the FreeBSD handbook for building/installing. > > Then, the instructions at ( > https://github.com/FreeBSDDesktop/freebsd-base-graphics/wiki#installing-required-userland-components) > will tell you how to get the updated X server installed. > > One thing to note that's not really stated anywhere is that you need to > load the i915kms driver in rc.conf, not from the boot loader, as it's not > ready for boot-time loading yet (last I worked with it, last month). > Boot-time loading results in a panic. > > The only other problem I faced was a missing/changed function in a shared > library that `pkg` relies on. Using `pkg-static` to install packages worked > around that. > > Cheers! > -doug > > On Tue, Sep 20, 2016 at 11:58 AM Bob Willcox <b...@immure.com> wrote: > > > On Tue, Aug 16, 2016 at 12:12:44AM -0700, Matthew Macy wrote: > > > As of this moment sys/dev/drm in the drm-next tree is sync with > > https://github.com/torvalds/linux drivers/gpu/drm (albeit only for the > > subset of drivers that FreeBSD supports - i915, radeon, and amdgpu). I > > feel this is a bit of a milestone as it means that it is possible that in > > the future graphics support on FreeBSD could proceed in lockstep with Linux. > > > > > > In addition I have IFCed both drm-next-4.6 and drm-next to HEAD as of > > today. > > > > > > Once I'm done working on Kaby Lake support I intend to get radeon and > > amdgpu to the point where they work as well as i915. Following that we'll > > need to spend some time resolving general correctness issues. > > > > > > -M > > > > > > ___ > > > freebsd-...@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" > > > > I just picked up a Skylake i5 NUC (NUC6i5SYH) and was looking for help on > > what > > I need to do to tryout the driver support for Skylake on it. > > > > Currently I have FreeBSD-current (as of a couple of days ago) running on > > it. > > I've read through most of the emails here discussing drm-next support but > > I'm > > not at all clear on where to start? What do I need to do/get? > > > > Any help would be greatly appreciated. > > > > Thanks, > > Bob > > > > > > -- > > Bob Willcox| In real love you want the other person's good. In > > b...@immure.com | romantic love you want the other person. > > Austin, TX | -- Margaret Anderson > > ___ > > freebsd-...@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" > > -- Bob Willcox| In real love you want the other person's good. In b...@immure.com | romantic love you want the other person. Austin, TX | -- Margaret Anderson ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: gfx-next update: drm-4.8-rc2 tagged in drm-next
On Tue, Aug 16, 2016 at 12:12:44AM -0700, Matthew Macy wrote: > As of this moment sys/dev/drm in the drm-next tree is sync with > https://github.com/torvalds/linux drivers/gpu/drm (albeit only for the subset > of drivers that FreeBSD supports - i915, radeon, and amdgpu). I feel this is > a bit of a milestone as it means that it is possible that in the future > graphics support on FreeBSD could proceed in lockstep with Linux. > > In addition I have IFCed both drm-next-4.6 and drm-next to HEAD as of today. > > Once I'm done working on Kaby Lake support I intend to get radeon and amdgpu > to the point where they work as well as i915. Following that we'll need to > spend some time resolving general correctness issues. > > -M > > ___ > freebsd-...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscr...@freebsd.org" I just picked up a Skylake i5 NUC (NUC6i5SYH) and was looking for help on what I need to do to tryout the driver support for Skylake on it. Currently I have FreeBSD-current (as of a couple of days ago) running on it. I've read through most of the emails here discussing drm-next support but I'm not at all clear on where to start? What do I need to do/get? Any help would be greatly appreciated. Thanks, Bob -- Bob Willcox| In real love you want the other person's good. In b...@immure.com | romantic love you want the other person. Austin, TX | -- Margaret Anderson ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: Can anyone tell me where PORTS_MODULES is documented? I don't find it in the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I thing) wrote it. This is a very beneficial tool. It really needs to be well documented. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com I found it in the make.conf(5) man page. I will say, however, that the description is fairly skimpy and I wouldn't have really known how to use it to solve my nvidia driver problem w/o the help of folks here. A more complete description, preferably with a few examples, would really help to understand how it is actually used. Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: Hi, The nvidia-driver package needs to be recompiled with the latest FreeBSD-current sources, because of changes in the callout subsystem. If this is not possible, we can temporarily add the _callout_stop_safe symbol to the kernel for some transition time. ... While I'm running i386 (vs. amd64), I have not encountered the cited issue. Given the above, I suspect that the fact that I have the line: PORTS_MODULES=x11/nvidia-driver in /etc/src.conf has a fair amount of (positive) influence on that. (I track stable/10 head -- on different slices -- daily on my laptop.) Peace, david Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my /etc/src.conf file and rebuilding the kernel fixed it! Learn something new every day! :) Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
CURRENT breaks loading of nvidia.so
Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 Thanks, Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 40% slowdown with dynamic /bin/sh
On Tue, Dec 02, 2003 at 01:43:16PM -0800, Tim Kientzle wrote: Daniel C. Sobral wrote: Now, my machines usually get by themselves, but all *I* do on them is sh(1) intensive, so I'll probably be using the static root option when it comes time to upgrade them to 5.x. The static root option exists for people with special requirements: * Use a lot of shell scripts * Have very high performance requirements for those scripts * Does not use LDAP, NIS, or other networked directory services (I want to move NIS out of libc. Its privileged position relative to LDAP and other services is rather dated.) What impact, if any, will this have on those of us that use NIS and still want a statically linked root? I have been using NIS for years and see no compelling reason to switch to LDAP (i.e., NIS satisfies my needs, is configured, and working). Bob -- Bob Willcox First Law of Procrastination: [EMAIL PROTECTED] Procrastination shortens the job and places the Austin, TX responsibility for its termination on someone else (i.e., the authority who imposed the deadline). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: /bin and /sbin are now dynamically linked
On Fri, Nov 28, 2003 at 10:01:05PM +0100, Michael Nottebrock wrote: Content-Description: signed data On Friday 28 November 2003 21:03, Tim Kientzle wrote: David O'Brien wrote: On Wed, Nov 26, 2003 at 10:37:48AM -0800, Tim Kientzle wrote: and [/usr/bin/ftp] doesn't support HTTP. $ /usr/bin/ftp http://www.theregister.co.uk/content/6/32524.html Requesting http://www.theregister.co.uk/content/6/32524.html 100% |*| 22559 35.32 KB/s 00:00 ETA 22559 bytes retrieved in 00:00 (35.28 KB/s) Wow! Learn something new every day around here. Well, it's a rather new ftp(1), this feature came with lukemftp replacing the former ftp. I believe Microsoft Windows still ships the old ftp client thought. The version of ftp in 4.9-R also supports this feature and is documented in the man page. :-) In fact, it looks like it was added my Mike Smith back in June of 1997 (source was Luke Mewburn/NetBSD). Bob -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -- Bob Willcox First Law of Procrastination: [EMAIL PROTECTED] Procrastination shortens the job and places the Austin, TX responsibility for its termination on someone else (i.e., the authority who imposed the deadline). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: panic: pmap_enter: pte vanished, va: 0xbfbff000
On Sat, Oct 04, 2003 at 06:12:03PM +0200, Christian Brueffer wrote:
Hi,
just got this panic on my smp box. Sources are from October 2nd, around
9pm CEST. A dump is available for further debugging.
I'm seeing this on one of my systems as well that I just recently updated
(Oct 4th). Mine will run for several hours prior to panicing.
Bob
GNU gdb 5.3 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-portbld-freebsd5.1...
panic: pmap_enter: pte vanished, va: 0xbfbff000
panic messages:
---
panic: pmap_enter: pte vanished, va: 0xbfbff000
cpuid = 1; lapic.id = 0100
boot() called on cpu#1
syncing disks, buffers remaining... 3842 3842 3842 3839 3839 3839 3839 3839 3842
3838 3838 3838 3838 3838 38
38 3838 3838 3838 3838 3838 3838 3838 3838 3838 3838 3838 3838 3838 3838
giving up on 3553 buffers
Uptime: 1d7h23m22s
Dumping 511 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352
368 384 400 416 432 448 4
64 480 496
---
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
240 dumping++;
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc0514fb0 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:372
#2 0xc05153b6 in panic (fmt=0xc06cb072 pmap_enter: pte vanished, va: 0x%x)
at /usr/src/sys/kern/kern_shutdown.c:550
#3 0xc06723dd in pmap_enter (pmap=0xc515fc80, va=3217027072, m=0xc17ce6e0, prot=5
'\005', wired=0)
at /usr/src/sys/i386/i386/pmap.c:1962
#4 0xc062149c in vm_fault (map=0xc515fbd0, vaddr=3217027072, fault_type=1 '\001',
fault_flags=0)
at /usr/src/sys/vm/vm_fault.c:890
#5 0xc0675e39 in trap_pfault (frame=0xdbc8dd48, usermode=1, eva=3217029420)
at /usr/src/sys/i386/i386/trap.c:709
#6 0xc06759d4 in trap (frame=
{tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 76, tf_esi = 134629896, tf_ebp =
-1077937832, tf_isp = -
607593100, tf_ebx = 51, tf_edx = 1, tf_ecx = 19, tf_eax = 0, tf_trapno = 12, tf_err
= 4, tf_eip = 673303409,
tf_cs = 31, tf_eflags = 66118, tf_esp = -1077937876, tf_ss = 47}) at
/usr/src/sys/i386/i386/trap.c:317
- Christian
--
Christian Brueffer[EMAIL PROTECTED] [EMAIL PROTECTED]
GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D
--
Bob WillcoxGive a small boy a hammer and he will find
[EMAIL PROTECTED] that everything he encounters needs pounding.
Austin, TX
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: raidframe
I am successfully using a Mylex DAC1164PVX RAID controller on 5-CURRENT: mlx0: Mylex version 5 RAID interface port 0x2000-0x207f mem 0xf800-0xfbff,0xec91-0xec91007f irq 5 at device 8.0 on pci2 mlx0: controller initialisation in progress... mlx0: initialisation complete. mlx0: DAC1164PVX, 3 channels, firmware 5.08-0-87, 64MB RAM mlxd0: Mylex System Drive on mlx0 mlxd0: 105009MB (215058432 sectors) RAID 5 (online) On Sun, Jun 01, 2003 at 02:51:07PM +0300, Petri Helenius wrote: Is there anyone actually successfully using raidframe and if yes, what kind of hardware? Same question goes for any recent SCSI RAID controllers supported by FreeBSD. I admit not having tried all combinations but it seems that using anything else than simple ahc scsi stuff results in kernel panic with 5.x. Pete ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -- Bob Willcox Patience is a minor form of despair, disguised as virtue. [EMAIL PROTECTED]-- Ambrose Bierce, on qualifiers Austin, TX ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
/dev/mlx* renamed to /dev/mxl* ??
Were the device names for the Mylex devices changed? They used be named /dev/mlx* but now (since cvs updating and rebuilding my system this morning) seem to be named /dev/mxl* Was this a deliberate name change or am I missing something here? Thanks, Bob -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: aout support not working on todays -current
On Wed, Jan 22, 2003 at 11:25:16PM -0800, joseph wrote: Hi Bob, Go into your kernel of choice and build it with the following: options COMPAT_AOUT now to enable AOUT binaries from the kernel loader. Make and Install and reboot the about new kerenl and aout will now work for you. :) joseph I do have this option enabled (see below). I didn't change my kernel config file from last week to this and last week's kernel properly runs aout files and the new one doesn't. Something must have changed in the past week. Bob AOUT binaries... elf is the all around executable format for most loadable binaries.. On Tue, 2003-01-21 at 08:36, Bob Willcox wrote: I cvsup'd and built and installed a new -current system and kernel this morning and immediately noticed that my setiathome processes no longer ran. It appears that aout support is no longer working in -current. Note that I do have the COMPAT_AOUT option set in my kernel config file (it is the same config file that I used to build with about a week ago and that kernel runs aout files just fine). Anybody have any clues as to what happened? Thanks, Bob -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
aout support not working on todays -current
I cvsup'd and built and installed a new -current system and kernel this morning and immediately noticed that my setiathome processes no longer ran. It appears that aout support is no longer working in -current. Note that I do have the COMPAT_AOUT option set in my kernel config file (it is the same config file that I used to build with about a week ago and that kernel runs aout files just fine). Anybody have any clues as to what happened? Thanks, Bob -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: aout support not working on todays -current
On Tue, Jan 21, 2003 at 09:47:20AM -0800, Kris Kennaway wrote: On Tue, Jan 21, 2003 at 12:42:23PM -0500, Mike Makonnen wrote: I believe aout support was removed from the kernel some months ago. It was going to be made a port, but I don't know if that has happened yet. You're confusing two issues. To run a.out binaries you just need COMPAT_AOUT. Well, I have that in my kernel config file so maybe something has broken recently (within the last week)?? Bob To generate new a.out binaries you need an a.out toolchain, which is what someone was going to make a port for, but never did. Kris -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Who broke sort(1) ?
Funny, this argument suddenly reminds me of the Hitch Hikers Guide to the Galexy :-) Bob On Tue, Sep 24, 2002 at 05:01:29PM -0400, Garrett Wollman wrote: On Tue, 24 Sep 2002 13:30:11 -0700, Peter Wemm [EMAIL PROTECTED] said: Oh man, this is going to suck. There are thousands and thousands of third party scripts that use +n syntax. I am most unhappy with this change. :-( The time to complain about it was back in 1992when the old syntax was labeled ``deprecated'' by P1003.2, or in 1999 when the revision cycle was just heating up. Old deprecated features were automatically dropped leading up to the 2001 revision, unless someone could make a case for their retention. That case wasn't made in the case of `sort', and as a result the Standard no longer permits the old syntax. It's not like people didn't have nine years' advance warning to fix their scripts. FreeBSD supported `-k' in 1.0; see http://www.freebsd.org/cgi/cvsweb.cgi/src/gnu/usr.bin/sort/Attic/sort.c?rev=1.1content-type=text/x-cvsweb-markup. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel compile at aic7xxx/aicasm today's current.
I now get a bit further: === aic7xxx === aic7xxx/aicasm make -f /.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm/Makefile MAKESRCPATH=/.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm cleandir make -f /.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm/Makefile MAKESRCPATH=/.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm/../../../dev/aic7xxx/aicasm clean rm -f aicasm_gram.h aicasm_macro_gram.h aicasm_gram.output aicasm_macro_gram.output aicasm aicasm.o aicasm_symbol.o aicasm_gram.o aicasm_macro_gram.o aicasm_scan.o aicasm_macro_scan.o aicasm_scan.c aicasm_macro_scan.c aicasm_gram.c aicasm_gram.h aicasm_macro_gram.c aicasm_macro_gram.h make: don't know how to make cleandepend. Stop *** Error code 2 Stop in /.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm. *** Error code 1 Stop in /.amd_mnt/han/host/usr/src/sys/modules/aic7xxx/aicasm. *** Error code 1 Stop in /.amd_mnt/han/host/usr/src/sys/modules/aic7xxx. *** Error code 1 Stop in /.amd_mnt/han/host/usr/src/sys/modules. *** Error code 1 Stop in /.amd_mnt/han/host/usr/obj/.amd_mnt/han/host/usr/src/sys/GREEDO. *** Error code 1 Stop in /.amd_mnt/han/host/usr/src. *** Error code 1 Stop in /.amd_mnt/han/host/usr/src. On Sat, Aug 31, 2002 at 08:50:33AM -0600, Justin T. Gibbs wrote: Today's current gave me the following error while building a new kernel after a successful make world. cd /usr/src/sys/modules ; MAKEOBJDIRPREFIX=/usr/obj/usr/src/sys/PIII850N/modules KMODDIR=/boot/kernel MACHINE=i386 make cleandir === 3dfx === accf_data === accf_http === agp === aha === aic7xxx === aic7xxx/aicasm make: don't know how to make cleandir. Stop *** Error code 2 Stop in /usr/src/sys/modules/aic7xxx. *** Error code 1 Ooops. I never use the buildkernel target. Try re-cvsup'ing and see if the change I just checked in fixes this for you. -- Justin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Is anyone else having trouble with dump(8) on -current?
On Mon, Aug 12, 2002 at 10:16:56PM +1000, Bruce Evans wrote: [snip] I just saw a reply from the original (?) author of the PR. Apparently dump gets killed by amanda. Does amanda actually kill its children enough to matter? From my experience/use with amanda I know that it _always_ kills the dumps that it starts when doing its estimates at the beginning (often several per file system, one for each dump level it's interested in). I don't think it deliberately kills the dumps when actually dumping the data. :-) [snip] Bob -- Bob WillcoxWe seem to have forgotten the simple truth that [EMAIL PROTECTED] reason is never perfect. Only non-sense attains Austin, TX perfection. -- Poul Henningsen [1894-1967] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
locate.mklocatedb requires perl which may not be installed
Hi,
I just installed a system today using the 5.0-CURRENT-20020621-JPSNAP.iso
CDROM and noticed that when I attempted to run /etc/periodic/weekly/310.locate
so that I could use locate to find some files that it spewed out:
Perl is not installed, try 'pkg_add -r perl'
Rather than simply installing perl (I'll get to that later)
I decided to track down what was calling it. Turns out that
/usr/libexec/locate.mklocatedb was the culprit. I then modified
locate.mklocatedb to use awk rather than perl. Here's the diff:
--- locate.mklocatedb.orig Thu Jun 20 17:07:43 2002
+++ locate.mklocatedb Sat Jun 22 18:09:03 2002
@@ -76,14 +76,15 @@
$code $bigrams $filelist || exit 1
locate -d $filelist / | $bigram | $sort -nr | head -128 |
-perl -ne '/^\s*[0-9]+\s(..)$/ print $1 || exit 1' $bigrams || exit 1
+awk '{if (/^[ ]*[0-9]+[ ]+..$/) {printf(%s,$2)} else {exit 1}}'
+$bigrams
+ || exit 1
locate -d $filelist / | $code $bigrams || exit 1
exit
else
if $sortcmd $sortopt $filelist; then
$bigram $filelist | $sort -nr |
- perl -ne '/^\s*[0-9]+\s(..)$/ print $1 || exit 1' $bigrams
+ awk '{if (/^[ ]*[0-9]+[ ]+..$/) {printf(%s,$2)} else {exit 1}}'
+$bigrams
|| exit 1
$code $bigrams $filelist || exit 1
else
This seems to be working for me. It could likely be improved upon by the
perl and/or awk some expert out there. (I'm actually more familiar with
awk than perl but I wouldn't claim that my awk translation is the most
efficient either.)
--
Bob WillcoxIf practice makes perfect, and nobody's perfect,
[EMAIL PROTECTED] why practice?
Austin, TX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: locate.mklocatedb requires perl which may not be installed
On Sat, Jun 22, 2002 at 05:55:47PM -0700, David O'Brien wrote: On Sat, Jun 22, 2002 at 06:22:27PM -0500, Bob Willcox wrote: Rather than simply installing perl (I'll get to that later) I decided to track down what was calling it. Turns out that /usr/libexec/locate.mklocatedb was the culprit. I then modified locate.mklocatedb to use awk rather than perl. Here's the diff: Thanks, committed. BTW, please take care about how your MUA handles ^I's vs. ' '. :-) Hmm, strange. The first awk line had the ^I's converted to spaces and the second one didn't. Digging into this abit deeper, it seems that my MUA (mutt) probably wasn't to blame afterall. It appears that I must have hosed this up myself while editing the file. :-( Bob -- Bob WillcoxIf practice makes perfect, and nobody's perfect, [EMAIL PROTECTED] why practice? Austin, TX To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: [SUGGESTION] - JFS for FreeBSD
On Tue, Dec 11, 2001 at 06:28:56PM +1030, Greg Lehey wrote: On Monday, 10 December 2001 at 22:45:22 -0800, Terry Lambert wrote: Hiten Pandya wrote: i wanted to ask if there were any _plans_ to port JFS (Journaled File System) to FreeBSD... Not unless you have plans. When I was an IBM employee, they would not change the license, and so it's impossible to ship a CDROM where it's the boot FS, or boxes on which it is the boot FS, and still have it be legal, because of the license conflicts. I fought this for about a year within IBM, before I gave up. Since then, it has become possible for the loader to load modules before booting the kernel. This means that, theoretically, it would be possible to have a JFS root file system. Given the strong opposition to the GPL in some factions of the FreeBSD project, I don't see this happening any time soon, especially since we still don't know if it will buy us anything. It is used on IBM MainFrames and Enterprise servers for high performance and maximum throughput... No, it's not. The Linux JFS is derived from the OS/2 JFS code, not the good AIX JFS code. That's correct, but note that AIX is moving to this code base too, so it's not as if it's second-rate. From what I've seen of the structures, JFS2 is *much* better than JFS1. I haven't compared performance. I happened to be with IBM working on AIX (I was the AIX architecture manager at the time) during the development of the original JFS (for AIX 3.1 on the first RS/6000s). Its design and implementation were largely the result of the efforts of a single person (Al Chang) from IBM research, who was also the primary designer/developer for the VM system for AIX 3.1. Consequently, the JFS code was designed to take advantage of the specific VM implementation (and the underlying RS/6000 VM hardware). This resulted in a rather unportable code base. Additionally, since it was derived from ATT (and BSD) filesystem code, there were some licensing issues. As I recall, these two issues (portability and license) were what lead to the reimplementation for OS/2 (I wasn't involved or even very familiar with that effort though). Bob -- Bob Willcox Boucher's Observation: [EMAIL PROTECTED] He who blows his own horn always plays the music Austin, TX several octaves higher than originally written. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Best way to get a system on current?
Hi All, I am interested in what is the best way to get a test system running current? I have tried both upgrading from 4.4-stable (ran into kernel build problems) and installing from the 5.0-20011011-CURRENT snapshot (install failed to mount the filesystems). I decided that I would query the net-wisdom prior to investigating either of these approached any further, though. BTW, before y'all (note, I live in Texas) beat me up for not reading the freebsd-current mailing list, I would like to point out that I have read it but didn't found anything apparent that addresses this (and that's not to say that it's not there, just that I didn't find it...pointers to any oversight on my part are welcomed). Any suggestions?? Thanks, Bob -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 09:20:35AM -0700, David Wolfskill wrote: Might help if you provided a pointer to the problems you had in the upgrade from -STABLE case. For that matter, a bit more detail on the install failed to mount the filesystems for the install from -CURRENT snapshot case would be of interest, as well. In my case, I just followed the instructions in /usr/src/UPDATING, and it worked (once I fabricated a replacement kernel config file). Unfortunately, the actual specifics on what failed on the upgrade attempt were lost on the attempted snapshot install. However from memory, the problem was that the kernel build failed (the make buildworld was successful). It appeared that the make buildkernel was using header files from the current system, rather than the /usr/src/sys tree, when building, but I'm not certain. Note that, now that I think somemore about it, I may have _not_ have created a new kernel config file. (I usually do, but don't recall doing it this time.) Consequently, I may have been trying to use the 4.4 kernel file that I had for this system. I really wouldn't expect that to work. If that's the case, I can start all over again with this approach (install 4.4 and upgrade). As for the snapshot install, since it's errors were only written to the screen I have to work from memory here as well. I believe the first complaint had to do with the filesystems to be mounted (/mnt/usr, for example) not specified in fstab. Since all of the mounts to /mnt failed, the system fails pretty soon apparently running out of space in /. Thanks, Bob Cheers, david -- David H. Wolfskill[EMAIL PROTECTED] As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product. -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Best way to get a system on current?
On Fri, Oct 12, 2001 at 11:16:18AM -0700, David O'Brien wrote: On Fri, Oct 12, 2001 at 11:15:34AM -0500, Bob Willcox wrote: I am interested in what is the best way to get a test system running current? I have tried both upgrading from 4.4-stable (ran into kernel build problems) It would be nice to see the problems you experienced. One is supose to be able to update from 4.4-stable to 5-CURRENT. Do you still have the error output (and the exact sequence of commands that produced it)? No, unfortunately the output is long gone (lost in the subsequent attempt to install the 5.0-current snapshot). I'm planning on recreating the snapshot install failure (or getting it right this time and having the install work:-). If I still can't install the snapshot, I will resort to installing 4.4 and trying the upgrade again. I do remember that it was in the make buildkernel step that I had the problem (the make buildworld was successful). A compile failed due to what looked like it was using the wrong header files (from /usr/include/sys). If this should recur, I will save the output. Note that I may have used the old 4.4 kernel config file for this though. Next time I plan on using the GENERIC config file. Thanks, Bob -- Bob Willcox Putt's Law: [EMAIL PROTECTED]Technology is dominated by two types of people: Austin, TXThose who understand what they do not manage. Those who manage what they do not understand. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.0 release candidate #3 now available.
On Wed, Mar 08, 2000 at 04:45:39PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. Fit fine on the cdr that I burned (~549MB as I recall). -- Bob Willcox What is wanted is not the will-to-believe, [EMAIL PROTECTED] but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD 4.0 release candidate #3 now available.
On Wed, Mar 08, 2000 at 05:34:02PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Bob Willcox wrote: On Wed, Mar 08, 2000 at 04:45:39PM -0800, Brian Beattie wrote: On Wed, 8 Mar 2000, Jordan K. Hubbard wrote: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/alpha/4.0-2307-CURRENT ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2307-CURRENT With ISO images available from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2307-CURRENT/ I tried to burn this image and it was too big for a standard 74 min CD. Fit fine on the cdr that I burned (~549MB as I recall). The image I got was 655MB, I suspect you grabbed it while it was uploading. Quite possible. I have not yet tried to use it. I notice now that the install-i386.iso file is gone. Oh, well. Looks like I probably have another coaster. :-( Bob 500 'EPRT |1|138.95.12.36|49359|': command not understood. 200 PORT command successful. 150 Opening ASCII mode data connection for 'file list'. total 1297625 -rw-r--r-- 1 root 207 117 Mar 8 23:42 CHECKSUM.MD5 -rw-r--r-- 1 2035 207641435648 Mar 8 22:18 install-alpha.iso -rw-r--r-- 1 2035 207687331328 Mar 8 22:27 install-i386.iso 226 Transfer complete. -- Bob Willcox What is wanted is not the will-to-believe, [EMAIL PROTECTED] but the wish to find out, which is the exact Austin, TX opposite. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error with install, Unable to make device nodes...
On Mon, Dec 20, 1999 at 03:45:01PM -0500, Mike Heffner wrote:
[ sorry if you get this twice, it didn't seem to go through the first time ]
I'm having a problem trying to install the 12/20/99 -current snapshot. When I
finalize all the settings and sysinstall is about to partition/setup the drive I
get the following message:
Unable to make device node of /dev/ad0s1b in /dev!
The creation of filesystems will be aborted.
If I switch to the second virtual terminal it says:
DEBUG: Scanning disk ad0 for root filesystem
DEBUG: Scanning disk ad0 for swap partitions
DEBUG: MakeDev: Unable to lookup user "root".
[ last line repeated several times ]
I am seeing this as well. I am also trying to install the
4.0-19991220-CURRENT snapshot (on an IBM 9G IDE drive). From scanning
the sources it looks like this message (the Unable to lookup user
"root") is being issued from src/lib/libdisk/create_chunk.c because the
getpwnam("root") has failed. I have not investigated it any further
yet, so I don't have any idea why getpwnam() failed.
Bob
--
Bob Willcox Don't tell me that worry doesn't do any good.
[EMAIL PROTECTED] I know better. The things I worry about don't
Austin, TX happen. -- Watchman Examiner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
Yep! The patch seems to have fixed the problem! :-)
Thanks Luoqi!!
Bob
On Mon, May 17, 1999 at 11:42:21PM -0400, Luoqi Chen wrote:
I have been making world each time after cvsupping so I would expect the
mfs kld module to be getting rebuilt and it appears to be up-to-date:
-r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko
Also, both my custom kernel config file and the GENERIC config file
include options MFS so mfs should not be getting loaded, right?
Thanks,
Bob
-lq
--
Bob Willcox The man who follows the crowd will usually get no
b...@luke.pmr.comfurther than the crowd. The man who walks alone is
Austin, TX likely to find himself in places no one has ever
been.-- Alan Ashley-Pitt
Would you try this patch?
Index: kern_conf.c
===
RCS file: /home/ncvs/src/sys/kern/kern_conf.c,v
retrieving revision 1.39
diff -u -r1.39 kern_conf.c
--- kern_conf.c 1999/05/12 13:06:34 1.39
+++ kern_conf.c 1999/05/18 03:27:36
@@ -182,7 +182,7 @@
uintptr_t i = (uintptr_t)x;
#ifdef DEVT_FASCIST
- return(253 - ((i 8) 0xff));
+ return(255 - ((i 8) 0xff));
#else
return((i 8) 0xff);
#endif
@@ -200,7 +200,7 @@
makedev(int x, int y)
{
#ifdef DEVT_FASCIST
-return ((dev_t) (((253 - x) 8) | y));
+return ((dev_t) (((255 - x) 8) | y));
#else
return ((dev_t) ((x 8) | y));
#endif
--
Bob Willcox The man who follows the crowd will usually get no
b...@luke.pmr.comfurther than the crowd. The man who walks alone is
Austin, TX likely to find himself in places no one has ever
been.-- Alan Ashley-Pitt
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
panic: page fault (apparently caused by mount_mfs)
Hi, I have been getting a panic lately with every -current kernel that I have built for the past week or so (-current cvsupped daily). Even the GENERIC kernel panics. It is occuring when the mount for a /tmp mfs filesystem is attempted. If I boot an old kernel from 5/11 or remove the fstab entry for the mfs file system the system boots up okay. My fstab entry for this is: /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 and the panic messages are: Fatal trap 12: pagefault while in kernel mode fault virtual address = 0x9d334e68 fault code = Supervisor read, page not present instruction pointer = 0x8:0xc0185cb0 stack pointer = 0x10:0xc98ad84 frame pointer = 0x10:0xc98adb0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 40 (mount_mfs) interrupt mask = trap number = 12 panic: page fault Any ideas on what may be wrong? Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: I use mfs a lot and have had no trouble whatsoever. I'm using: swap/tmpmfs rw,-s=200 0 Do you suppose that the usage of /dev/da0s1b directly is what's causing some trouble? Don't know, but I will change it and see what happens. Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:03:50PM -0700, Matthew Jacob wrote: I use mfs a lot and have had no trouble whatsoever. I'm using: swap/tmpmfs rw,-s=200 0 Do you suppose that the usage of /dev/da0s1b directly is what's causing some trouble? Unfortunately, changing from /dev/da0s1b to swap didn't help. I also tried it without the nosuid option but it still panics. Bob On Mon, 17 May 1999, Bob Willcox wrote: Hi, I have been getting a panic lately with every -current kernel that I have built for the past week or so (-current cvsupped daily). Even the GENERIC kernel panics. It is occuring when the mount for a /tmp mfs filesystem is attempted. If I boot an old kernel from 5/11 or remove the fstab entry for the mfs file system the system boots up okay. My fstab entry for this is: /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 and the panic messages are: Fatal trap 12: pagefault while in kernel mode fault virtual address = 0x9d334e68 fault code = Supervisor read, page not present instruction pointer = 0x8:0xc0185cb0 stack pointer = 0x10:0xc98ad84 frame pointer = 0x10:0xc98adb0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 40 (mount_mfs) interrupt mask = trap number = 12 panic: page fault Any ideas on what may be wrong? Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 01:47:59PM -0700, Matthew Jacob wrote: I use mfs a lot and have had no trouble whatsoever. I'm using: swap/tmpmfs rw,-s=200 0 Do you suppose that the usage of /dev/da0s1b directly is what's causing some trouble? Unfortunately, changing from /dev/da0s1b to swap didn't help. I also tried it without the nosuid option but it still panics. Hmm. Is MFS a module as Luoqi keeps mentioning? How much real memory do you have? I believe it is in the kernel (the GENERIC kernel includes it as well as my customized kernel config file). This system has 256MB. See- it's been working fine for me! Yep. I am going to try re-checking out all of the current sources and see if that helps. Perhaps something is hosed with my source tree. Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: panic: page fault (apparently caused by mount_mfs)
On Mon, May 17, 1999 at 04:34:50PM -0400, Luoqi Chen wrote: Hi, I have been getting a panic lately with every -current kernel that I have built for the past week or so (-current cvsupped daily). Even the GENERIC kernel panics. It is occuring when the mount for a /tmp mfs filesystem is attempted. If I boot an old kernel from 5/11 or remove the fstab entry for the mfs file system the system boots up okay. My fstab entry for this is: /dev/da0s1b/tmp mfs rw,nosuid,-s=102400 0 0 and the panic messages are: Fatal trap 12: pagefault while in kernel mode fault virtual address = 0x9d334e68 fault code = Supervisor read, page not present instruction pointer = 0x8:0xc0185cb0 stack pointer = 0x10:0xc98ad84 frame pointer = 0x10:0xc98adb0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 40 (mount_mfs) interrupt mask = trap number = 12 panic: page fault Any ideas on what may be wrong? Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt How about recompile mfs kld module and try again? I have been making world each time after cvsupping so I would expect the mfs kld module to be getting rebuilt and it appears to be up-to-date: -r-xr-xr-x 1 root wheel 12778 May 17 13:34 /modules/mfs.ko Also, both my custom kernel config file and the GENERIC config file include options MFS so mfs should not be getting loaded, right? Thanks, Bob -lq -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Substitute for dumps on specification in kernel config file
Is there an alternative way of specifying where system dumps are to go similar to the now obsolete: config kernel root on da0s1 dumps on da0s1b line? I am experiencing a panic on a recently cvsuped -current kernel and need to get a crash dump during boot (prior to dumpon being executed). Thanks, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Further on tape CAM problems
On Fri, Apr 30, 1999 at 12:36:25AM +0200, Wilko Bulte wrote: As Bob Willcox wrote ... On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: As Bob Willcox wrote ... On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: shipping 8200's (this was right at their end-of-life) was: MX: 2680 SV: C034 This is for generic models. OEM models may have different versions due to customizations. And these are not recommended for general use. Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I That is what I've been told by an Exabyte engineer years back. I can only guess that some OEMs need adaptations to the firmware behaviour that are incompatible with what the rest of the world needs (or has standardised on, e.g. in the ANSI SCSI standard). Again, guessing. Well, I can only speak for the IBM OEM'd drives that I have (as a retired IBMer, I've been picking them up at their employee surplus store here in Austin, TX). For these drives the generic firmware works just fine. I can see why Exabyte wouldn't openly recommend the change though. Back in the late 80's, when I was still working for IBM on AIX, I do recall that we did have some customizations in the firmware for the RS/6K AIX systems. In addition to changing the Inquiry command Vendor ID data, I believe there were some functional changes (I don't recall the details). I have always suspected that the functional changes are likely what made the IBM OEM'd drives fail on FreeBSD! The upgraded firmware IBM drives work on both (as Other SCSI Tape Drive). have have precisely these firmware levels in them (2680 C034). Also, Mine works OK with that f/w. Not that I use the 8200 often anymore, I like my DLT4000 much better than the 8200. ;-) I much prefer my Exabyte Mammouth drives as well :-) (But I do seem to get some fun out of playing with the 8200's I get for $10 apiece from the surplus store :-) Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Further on tape CAM problems
On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: Exabyte is not particularly famous for stable firmware. I have quite a number of 8200's here (though I don't really use them much anymore since I now have a Mammoth) that I have installed new firmware in. From an email discussion with an Exabyte tech support person back in '93 (I believe it was), the latest level of firmware in shipping 8200's (this was right at their end-of-life) was: MX: 2680 SV: C034 This is for generic models. OEM models may have different versions due to customizations. At the time he sent me the newest (but not ever installed in shipping products) MX firmware rev 2687 (SV C034 was still the newest) . I have, as a matter of course, upgraded the firmware in all of my 8200's to this 2687/C034 combination with good success. I have both of these ERPOM files handy and would gladly email them to anyone that wants them (you'll need access to an EPROM burner). Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Further on tape CAM problems
On Thu, Apr 29, 1999 at 10:26:36PM +0200, Wilko Bulte wrote: As Bob Willcox wrote ... On Wed, Apr 28, 1999 at 08:45:36PM +0200, Wilko Bulte wrote: Exabyte is not particularly famous for stable firmware. I have quite a number of 8200's here (though I don't really use them much anymore since I now have a Mammoth) that I have installed new firmware in. From an email discussion with an Exabyte tech support person back in '93 (I believe it was), the latest level of firmware in Well, you sent it to me in March 1995 (just found the original email ;-) shipping 8200's (this was right at their end-of-life) was: MX: 2680 SV: C034 This is for generic models. OEM models may have different versions due to customizations. And these are not recommended for general use. Hmm, why is that? The newest of the IBM branded Exabyte 8200's that I have have precisely these firmware levels in them (2680 C034). Also, I have here about 12 or so 8200's that I have changed to the 2687/C034 (most of them were already at C034 for the SV PROM) without problems. Have you checked the switch settings on the MX board? The IBM drives that I have all came with sw8 set to on which, according to the service manual, is for PI Cartridge Type (International). The off position is for P6 Cartridge type (Domestic, I assume means USA). My drives don't work (hang, as I recall) with this switch set to On. For those out there without the benefit of the service manual, here is the description of these switches: --- Switch Off Position(0) On Position(1) --- 1 Run Memory Test On Bypass Memory Test On Power-on reset (65 sec) Power-on reset (8 sec) 2 Parity checking DisabledParity checking enabled 3 Odd or Even byte disconnect Even byte disconnect 4 Report busy status No busy enable 5 Fixed block mode on Variable block mode on power uppower up 6 Normal data operations No disconnect during data transfer 7 Reserved for future use Reserved for future use 8 P6 Cartridge Type PI Cartridge Type (Domestic) (International) I have been setting my switches like so: 1 On 2 On 3 On 4 Off 5 On 6 Off 7 Off 8 Off Notes: Switch 1 is on the left-most side (looking at the card with the edge connector down) and the up position (closest to the top edge of the card) is to On position. Also, all of this applies to level 2 MX cards only. This is all I have ever seen, but I'm sure there are some level 1 cards out there somewhere. According to the service manual the level 1 cards use jumpers rather than switches and though the same functions seem to be there, there not in the same positions. If you happen to have one of these and want to know what their settings are email me. Hope this helps someone, Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: AIC
On Wed, Mar 31, 1999 at 12:28:47PM -0800, Brian Beattie wrote: On Wed, 31 Mar 1999, Warner Losh wrote: The aic driver will likely oneday be ported. However, no one has come forward to do it. It is a highly desirable driver to have (even if Umm, I'm still working on the aic driver. Slowly, but working on it. writing it would be a pain) because the only pccard scsi cards that are out there are aic-6[23]60 based. Not having a pcmcia slot or card, I am not sure about support for this. I have both and would be willing to test it on my laptop. -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: How to add a new bootdevice to the new boot code ???
I have an LS-120 and I'd be happy to test the new boot code with it. Bob -- Bob Willcox The man who follows the crowd will usually get no b...@luke.pmr.comfurther than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been.-- Alan Ashley-Pitt To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
