On Feb 13, 2012, at 9:09 AM, Niclas Zeising wrote:
The ML ate the attachments. Either attach them as text/plain or post
them online somewhere.
Well, Brandon Falk actually appears to have nailed the root cause. I followed
older instructions on http://wiki.freebsd.org/BuildingFreeBSDWithClang
I've noticed that it's been broken for about a week as a result of:
--- /usr/src/lib/libc/../../include/rpc/rpcb_clnt.h.orig2012-02-12
22:42:29.0 -0800
+++ /usr/src/lib/libc/../../include/rpc/rpcb_clnt.h 2012-02-12
22:41:27.0 -0800
@@ -66,7 +66,7 @@
On Feb 13, 2012, at 5:59 AM, Dimitry Andric wrote:
I build it very regularly, and there are several buildbots that also
build it continously (though they currently don't spam the mailing
lists). For me, and the buildbots, head builds just fine with clang,
though. What was the exact error
Erm, can I ask what this thread POSSIBLY has to do with
freebsd-current? Do people even care about posting on-topic things to
the correct mailing lists anymore? At best, this is and always was
freebsd-chat material. Thank you.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Hopefully sysinstall will be smarter about writing these overrides
than it is about writing the "USA_RESIDENT=NO" override to /etc/make.conf.
It doesn't do that anymore.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
OK. We have no enough time. I'll commit it.
Jordan, can I MFC this?
Only if you're really really sure it won't break something else.
I must confess that the way this one has turned up with no independant
confirmation makes me very nervous. :-(
- Jordan
To Unsubscribe: send mail to [EMAIL
cd /usr/src; make -f Makefile.inc1 hierarchy
cd /usr/src/etc;make distrib-dirs
mtree -deLU -f /usr/src/etc/mtree/BSD.root.dist -p /
mtree: illegal option -- L
usage: mtree [-cdeinrUux] [-f spec] [-K key] [-k key] [-p path] [-s seed]
[-X excludes]
*** Error code 1
To
Long time back i sent request to the list and asked about including this
driver into the source tree. i still did not receive any reply. Some people
seems to be using this driver for Ethernet tunneling (with VTUN software).
Somebody even requested for OpenBSD port. So it would be really nice
Yes he did. Talk to various committers and you'll see that many have
ideas where files should live. There have been long threads on this
issue that got nowhere. The reason things are in such a messy state is
when something new is brought in, or is changed suffiently much for a
repo copy
If I somehow cc'd the mailing list on this then I made a mistake which
I don't usually make. These messages, when I'm watching the headers
correctly, are always sent privately.
- Jordan
On Monday, 26 June 2000 at 15:43:47 -0700, Jordan K. Hubbard wrote:
SUBSCRIBE [EMAIL PROTECTED
Yeah, I will say that pkg_info could get a lot more featureful
than it is now without "exceeding its mandate." It would have
been better than a profusion of tools.
- Jordan
On Mon, 26 Jun 2000 00:57:00 MST, Jeremy Lea wrote:
I've placed the source for a new command, pkg_which, on
SUBSCRIBE [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
If you're receiving this message, it's because you just sent a
"subscribe" message erroneously to one of our mailing lists, resulting
in thousands (and,
I think it should *definitely* be in the base system. :)
On Sun, 18 Jun 2000, Brandon D. Valentine wrote:
Out of curiosity, are there any plans to commit the smbfs stuff? It is
really useful and I'd love to see it in the base system.
Yes, I'm get much more responses about smbfs
Everyone talks about using bitkeeper but none of the people who
recommend it have ever actually tried to use it for anything.
Before such recommendations will bear weight, this needs to
change. :)
- Jordan
[EMAIL PROTECTED] said:
:- "CVS branches suck" is the reason I belive.
He seems to have put a new style GENERIC file (thus one that has no
hints = port irq etc information for ISA stuff) through the perl script.
You might try the script on an old style GENERIC to get the hints..
That was indeed my problem - sorry for the false alarm, folks!
I grabbed the
I tried booting a kernel this morning, just to see Peter's new
"lean-n-mean" kernel config format in action, and I turned my
workstation into a headless server in the process. :-)
Most notably, these former entries were now missing from my dmesg
output when I logged in remotely and poked around:
Did you ran the Perl skript to create the hints file and
then change your KERNEL config like this?
Yep! The Perl script generates no output and my kernel config file
matches the requirements perfectly. Though, if you'll read the
subject line again, you'll see I used GENERIC for my test
IMHO, the hints are a machine property, not a per-kernel property. Setting
up a /boot/device.hints is (IMHO) a one-time task that never needs to be
done more than once, and (again IMHO) the 'make install' had damn well
better not mess with.
But what if one does not exist? Wouldn't it be a
Err.. how did you run it? 'perl MYKERNEL'? If you run 'perl MYKERNEL'
it will generate nothing because I was kinda lame and didn't know how to do
argument parsing. :-]
Yep, I ran it exactly as you specified in your "HEADS UP" message
to -current. It generates no output for either GENERIC
Jonathan Hanna wrote:
Yes, recently on 4.0-stable, though provoked by unplugging and
replugging in the mouse. It did not recover. This I thought
sounded like a PR on the mouse being dead after a wakeup
from sleep mode.
Come to think of it, I do use a KVM switch, but this usually
Nope!
May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
I've seen it for the last few weeks and can only think that something
must be stomping on the psm driver now (or the driver is missing
interrupts for reasons of its own). Anyone else seeing this?
Do you, by any
options PSM_HOOKRESUME
options PSM_RESETAFTERSUSPEND
They compile and boot fine. I'll let you know in a day or two if this
stops the crazy mouse syndrome. For what it's worth, I've seen this
both before and after a suspend/resume.
I doubt that this will help me since the PS/2 mouse in
Unless your mouse died of old age. The PS/2 mouse I had been using for
quite some time started to behave exactly like yours at some point last
year. I avoided replacing it for a long time, since I couldn't find another
mouse with a long enough cord.
I tried several other mice. It's a
I don't know if the mouse problems are related or not, did anyone have
jumpy-mouse problems before the SMP cleanup was committed? (i.e. in
kernels then two weeks old for 4.0, and four weeks old for 5.0).
I did not have jumpy-mouse problems on my SMP system (probably should
have
No, I don't mean rodents who've nibbled on chocolate-covered expresso
beans, I mean PS/2 mice which fall victim to this new problem:
May 19 00:50:45 zippy /kernel: psmintr: out of sync (00c0 != ).
I've seen it for the last few weeks and can only think that something
must be stomping on the
I haven't seen this message, but I _have_ been seeing an off-and-on problem
where my PS/2 (Logitech Firstmouse) mouse will go insane. Just moving it
causes clicks, wild pointer motion, all sorts of stuff. I usually have to
FWIW, those are all the symptoms of this problem too. The mouse
But I'm suddenly confused what you're actually talking about
here: OpenSSH, OpenSSL, or RSAREF.
OpenSSH has never included crypto code, but it's useless without OpenSSL
which quite certainly does. OpenSSH no longer requires RSAREF to operate
(if you've got clients/servers willing to do DSA
Err, well it still requires openssl, which I think is firmly rooted in the
crypto distribution as long as we have one.
Is it? I thought the RSAref code being pluggable gave it some
protection, or is merely "pluggability" also classified as crypto?
I do recall someone saying something to that
Maybe the comitters ought to take an idea from many software companies and
contribute $5 to the beer fund every time they break the build. Have it
all come due at the next BSDcon to fund a committer beer bash. :-)
I'd go along with that. What do the other committers think?
I think
In trying to build "make release" today, I discovered that the
"vn" driver is required now to build the boot floppies.
You make it sound like a new thing - the release process has required
the vn device for years.
I would suggest that this driver be added to "GENERIC". For
It's already
* No longer a dependency on RSA (and therefore rsaref for US folks): SSH2
can handle DSA keys which have no patent or usage restrictions. This means
we could now enable SSH2 out of the box in a crypto installation, with no
post-installation configuration requirements. We now have a truly free
I have a suggestion for pkg_delete: Very often when I'm deleting a package
(such as kde, after testing the port) I want to delete that package, and
all it's dependancies; instead of going around looking for the
dependancies, I think it would be a nice idea to add an option to
pkg_delete to
Does anyone know if this has been brought up with the folks at
Sleepycat to see if we could get a modification/clarification of this
point, so that as long as FreeBSD satisfies the necessary
requirements that this point of the license doesn't then recurse upon
people who might be
wishlist
Not sure if this is a silly question or not, but could the kernel somehow
view a specific dir on a ext2fs disk as the freebsd root and boot a
freebsd system from it? Also being able to access the stuff below the
I think there's a more general need to have a loader variable which
What sort of fallback behaviour would you want in case of error here?
Just let chroot() either succeed or fail. It's own "fallback behavior"
in such a case should prove adequate. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of
And if I put up, will you (the organization) use it? It's certainly too much
work to prove the obvious. I don't have to convince myself of anything.
The only value accrues if it gets used.
Erm, haven't we been here with you before? I can even replay the
script from heart:
1. Richard comes
Gee, is that perhaps because FreeBSD keeps breaking the ABI to modules
so every vendor that has ever tried to use them has been bitten by the
fact that they have to maintain N version for each branch of FreeBSD???
Can you list some specific examples? I'm not trying to be a wise-ass,
I'm
So you guys (core) choose -- do you want 4.x to reap the benefits of
further SMP development or not?
I've read all the feedback on this thread and now feel that it would
be worthwhile to simply bring the SMP changes in on Wednesday. As others
have pointed out, we don't have enough 3rd
Are there any 3rd party NIC klds yet?
NTMK.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/
src/usr.bin/netstat/ipx.c
cc -O -pipe -Wall -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/
src/usr.bin/netstat/route.c
/usr/src/usr.bin/netstat/route.c: In function `p_tree':
In general I agree with the concept but I think .0 releases have to
have a bit more flexibility, and that 4.0 in particular (due to the
rules change made for the BSDI merger) has to be even more flexible.
And this is something I can render an opinion on right away: I
Really, then you have a short memory. Why don't we ask Jordan for a
clarification.
How about if you let me review the patches in question and I'll render
a decision.
If you, Matt, could put the SMP and linux stuff into -current first
and then give me a day or so to check it out, I'll
Does this mean that the burdon of proof of patent problems shifts from
those doing the software to those who think there's a problem?
That's the way things generally work, yes. :)
does that mean things can go ahead with the integration of the
firewire drivers that are out there? It sounds
IMHO, it's not such a bad idea. freebsd-current _is_ the place to
report problems with -current, why can't the report be produced by a
daemon?
Becuase it's chunky and regular enough that I don't see why we
also can't just create a new notification service for it.
Think a bit bigger-picture
I have a machine which isn't doing much right now, so I have decided
to set it up as an automatic "FreeBSD Build checker".
Welcome to the current.freebsd.org game. :)
Once per day the machine cvsups, checks out a virgin source tree,
tries to build GENERIC, GENERIC98, LINT and world. If
But does this also check the kernels ? It was my understanding that
it only did world/release ?
It only does the world/release (and it's the chrooted make release
"world build" which is reported on, not the host system's BTW) but
could easily add a kernel build just for the benefit of the
We argue about this a lot. Nobody has, as yet, ever done the work to
make "bindist" a meta-package which depends (perhaps selectively) on
sub-packages like groff, sendmail, gcc, et al. to achieve the required
state of "bundling by default but not by requirement" in FreeBSD.
This is despite the
For the latest 4.0-STABLE snapshots:
ftp://releng4.freebsd.org/pub/FreeBSD
For the latest 5.0-CURRENT snapshots:
ftp://current.freebsd.org/pub/FreeBSD
I don't run mirrors of these machines so please don't ask where you
can get the bits closer/faster/cheaper/etc. If you want to mirror
Try again, the DNS wasn't updated yet.
"Jordan K. Hubbard" wrote:
For the latest 4.0-STABLE snapshots:
ftp://releng4.freebsd.org/pub/FreeBSD
Unfortunately does not work ...
root[amb]@pinta# nslookup releng4.freebsd.org. who.cdrom.com
Server: who.cdrom.co
It is down right now. It will be back soon. Thanks for asking
so loudly.
Why is this machine (current.freebsd.org) always rejecting guest privileges
and why won't ANYBODY answer the question?
Thanks in advance,
Tom Veldhouse
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
Just out of curiosity, why is there an "AGAIN" in the subject line,
since this is the first email I've gotten on the subject?
Sorry, the first queries about this probably didn't go directly to you
since it was only yesterday that I actually bothered to go track down
the specific commit which
Sounds perfectly reasonable to me. I'd be happy if someone else wants
to look at this, or I can look at it on the 10th when I get back from
Australia. This would mean there's a src/secure/usr.sbin/tcpdump that
builds with crypto and src/usr.sbin/tcpdump that builds without?
Correct! Both
There *were* several problems with the .ifdefs in the tcpdump makefile
which I fixed prior to 4.0, and I thought I had fixed the problem of
tcpdump in the bin distribution being linked against libcrypto (this was
broken in the initial 4.0 Release but fixed when jkh rereleased it). If I
You moved tcpdump into the crypto distribution with revision 1.25 of
its Makefile. I am still scratching my head and trying to figure out
why, however, since most people expect tcpdump to be in the bin
distribution where it's always been. Did you have some really good
reason for this which
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf
-mno-fp-regs -Wa,-mev56 ../../alpha/alpha/clock.c
I did and created malloc.conf as documented there. And things were
fine after that. Wouldn't it be better if the build process created
a default /etc/malloc.conf ?
It's purely an optional file; one doesn't need to be installed by
default in order for things to behave as expected. Consider it
Speaking of which, why is /home/ncvs on beast not pointing to
the current CVS repository? I got bit by the same error after
doing (what I thought) was a correct `cvs update' on beast.
Sorry, "my bad"; the alpha releases were falling over on some sort of
NFS bogon (and cvs checkouts using
Hmph, it seems sysinstall (and thus make release) is broken in -current:
I don't know what version of sysinstall you're using, but it builds just
fine for me under -current. I saw some other kvetching about kget
being broken and just tried building it last night. Observe:
root@zippy- make
Urk, sorry guys, I've been cvsupping the repo faithfully but evidently not
cvs updating my tree as faithfully. :-)
I'll find and fix it.
- Jordan
On 24-Mar-00 Jordan K. Hubbard wrote:
Hmph, it seems sysinstall (and thus make release) is broken in -current:
I don't know what version
kern-144.flp
root-144.flp
boot-288.flp
Winner! Much better than my personal favorite of bigbooty.flp. :-)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Good idea, terrible name. Can't you guys some up with something better? :)
On Tue, Mar 21, 2000 at 04:32:35PM -0800, Doug White wrote:
I would be in favor of renaming the boot.flp to something obviously
different, like 288boot.flp, to untrain us 2.x heads that got used to the
Great
In my 4.0 cvsupped from 3/20 /etc/rc.firewall says this:
# Suck in the configuration variables.
if [ -r /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
elif [ -r /etc/rc.conf ]; then
. /etc/rc.conf
fi
which would be fine, but
I think I'm just going to go to the 3.4 bits; I don't have a definitive
XFree86 distribution for 4.0 and I don't think I'm going to get one in
time to make a difference.
- Jordan
It looks like the X11 associated with the snapshots on current.freebsd.org
is still broken:
I was actually talking about FreeBSD 4.0, not XFree86 4.0. :)
On Tue, 14 Mar 2000, Jordan K. Hubbard wrote:
I think I'm just going to go to the 3.4 bits; I don't have a definitive
XFree86 distribution for 4.0 and I don't think I'm going to get one in
time to make a difference
IMO (and I suggested this the other day), we should make the crypto
collection mandatory, and have sysinstall ask a question about whether to
point the libcrypt symlinks at libscrypt or libdescrypt (libdescrypt is
I'm still waiting for your diffs which do this. :)
- Jordan
To Unsubscribe:
Well yeah, that's fun to say, but my days have been literally completely
full with getting other things ready for 4.0.
And you think mine haven't been? :) My point is simply that I'm going
to need a lot more than rough suggestions at this point if people want
to help. I don't have time to go
That was fixed days ago - get a more recent snap. :)
Hi.
I'm testing 2307-SNAP and I found that USA_RESIDENT is set to YES
even if I installed from CD-ROMs with crypto distribution compiled
from international crypto sources.
How about adding something like following patch to
I installed a -current snap from internat.freebsd.org that was built
with crypto source from internat. I answered yes when sysinstall asked
me if I want the crypto stuff, but then found that it marked me as an
USA_RESIDENT=YES in /etc/make.conf and it also asked me later if I
want to install
Good point, I forgot the link. Fixed!
- Jordan
Says, it can't chdir into the 4.0-2307-CURRENT directory.
It does work from current.FreeBSD.org. Looking on ftp.freebsd.org
I do not see a link under /pub/FreeBSD/releases/i386/ ? that maybe
the missing link ?
--
Regards, Ulf.
The other possibility would be to fix the wine port so it calls
dllockinit() to set up locking. I don't know for sure how hard that
would be, but it's probably a feasible solution.
To be honest, I'd be the most comfortable with this solution but also
trust John's skills with the linker
OK!
You have my OK to change the option, but you'll need Jordans
OK to commit it.
Poul-Henning
In message [EMAIL PROTECTED], Warner Losh writes:
Given that OpenBSD had the -e flag to fdisk first, and that it means
edit there and that disklabel -e means edit, I'd like to apply the
Hi:
I did an install of 4.0-RC3 last night and found the following:
1:Unable to transfer the local distribution from
ftp://current.freebsd.org/pub/FreeBSD/Snapshots/i386
Because it's not there. I listed the URLs I listed *very
specifically* and that is the ONLY location you can
I got the install floppies from the ftp directory that you listed. When the
install came to a point where it asked for the ftp site to get the
distribution, it listed a "primary" site (ftp.freebsd.org, I believe) and
This should work now - it just needed some symlinks to be created.
-
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/
.. just as soon as they finish uploading
I tried an FTP SNAP install this morning, and all the crypto libs from
current were unavailable. I switched over to the debug console, but there
was no additional info. The files seem to be on the ftp site just fine.
Is this a known issue ?
Please try again - I *just* fixed this problem
There were a couple of sysinstall related bogons, one related to
variable toggling in rc.conf and another related to the crypto
distribution (it was still looking in des/). Both of these have been
fixed and rolled into the updated boot floppies as well as the ISO
images, which are still
For just ftp (wizard) or on current (usw2) as well?
These snapshots are only going up on ftp, sorry for the confusion.
The stuff on current is just the daily snapshot stuff and not entirely
equivalent to the URLs I specifically gave out.
- Jordan
To Unsubscribe: send mail to [EMAIL
Urk! Geeze, how did I not notice that. Must have been the hour.
I'm fixing this now, sorry guys.
- Jordan
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
I have upgraded a machine to the latest -current snapshot (it
was running a -current from the end of January before). Every-
thing went fine, except for one thing: ssh didn't work anymore.
It used to work fine before.
You really need to read the -current mailing list if you're going to
run
I keep asking myself this question; a default sysinstall package would
give us the same end result.
I'm building with NO_OPENSSL and NO_OPENSSH and have still gotten hit with
breakage.
Would you guys quit spreading FUD and start actually giving us some
DETAILS on this alleged breakage?
Good god, I am saying that the files to merger dont existthere is nothing
to merge...
You need to be reading -current or stop running it. The issue with
/etc/ssh/sshd_config has been discussed to death.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
You know people, it's quite sad that those with knowledge simply refuse
to answer simple questions without "RTFM" attitudes and indirect (and
What you and others don't seem to understand is that there are also
"minimum responsibilities" that have been established for users of our
, 2 Mar 2000, Jordan K. Hubbard wrote:
Date: Thu, 02 Mar 2000 03:12:09 -0800
From: "Jordan K. Hubbard" [EMAIL PROTECTED]
To: Dmitry Valdov [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: sysinstall mistake
You need to track -current
You need to track -current. I fixed this on:
revision 1.155
date: 2000/02/24 08:28:06; author: jkh; state: Exp; lines: +2 -2
Do USA_RESIDENT properly.
Hi!
Please commit it:
--- release/sysinstall/config.c.old Tue Feb 29 23:56:47 2000
+++ release/sysinstall/config.c Tue
It seems that sysinstall will completely refuse to install unless we
have made a swap partition. Then for some reason it didn't allow
us the option of partitioning our second disk after "committing".
Why force swap? I swear we were going to configure it after the
install. :)
Hmmm. I'm
I'm still here for another hour, dammit. :-)
I'm also going to be reachable for most of that week since Holland
does have Internet connections now, you know. They got it along with
electric lighting and running water at least several years ago. :)
- Jordan
In message [EMAIL PROTECTED], Kevin
OK, I browsed through the source tree to locate something looking
like an RSA package and found /usr/src/crypto/openssl
/usr/src/crypto is just like /usr/src/contrib - you *never* attempt
to build things out of it. That will fail.
What you need is simply the rsaref package. I think
It exists in source form - you just need to build secure/lib/librsaintl
and install it.
Perhaps, but according to the conversation I had with Peter, at least,
it also wants to be in the ports collection and build a package
version of itself. :) Not everyone has source on their box.
- Jordan
installing the rsaref package if you're in the US or the rsaintl
package if you're outside the US. Of course, the rsaintl package
^^^ ^^^
doesn't quite *exist* yet, but that's another story. :-)
librsaintl existed right from
Mark *still* needs to commit the /etc/rc* changes to make sshd generate a
hostkey (I'll do it tonight if he hasn't by then, since we were hoping for
a RC3 tomorrow).
Today.. :) I'll be pretty busy tomorrow preparing for the trip and
have just gone and committing a fix.
- Jordan
To
Hmm. Whats the status of the sysinstall changes we were talking
about? Namely, displaying rsaref on the correct vty during installation,
and teaching it to pick up the RSA packages?
I'm going to do this tonite, before I roll RC#3.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
approved
Test condition is always true which is not supposed.
Please approve this patch.
--- login.c.bak Sun Feb 20 22:52:16 2000
+++ login.c Sun Feb 27 17:35:35 2000
@@ -382,9 +382,9 @@
refused("Home directory not available", "HOMEDIR", 1);
But now, I prefer to use pam_ssh.so with wdm. Wdm doesn't support PAM
session. So, I merged the code from XFree86-3.3.6 of xdm.
Hmmm. I see that /usr/ports/x11/wdm has merged in support for
FreeBSD's login classes, but not PAM. Are you planning to merge these
changes of yours into the port
OK, so now that we've settled this, can we get something into the
startup files? :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
+# Generate SSH host key, if it doesnt exist. Both sshd and ssh need it
+# so we do it unconditionally on sshd_enable.
Are you sure ssh requires a host key? I could have sworn this was
entirely related to sshd and could thus be lumped into the same
"if sshd_enable=YES" clause.
- Jordan
To
No, that would be contrary to the conventions documented in hier(4).
/usr/libexec is for things that are executed by other programs.
Normal persistent daemons such as sshd belong in /usr/sbin. Take a
look at the current contents of those two directories and you'll see
the distinction.
Can we please stop cross-posting this? -current alone is a more than
adequate mailing list.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I just did an install of the Feb 22 snap. The new wording for the anon
ftp section is really screwy. It's been turned around. The old straight
forward "Do you want to enable anon ftp?" was fine.
It's been turned around because people usually just hit return without
reading the dialogs and I
I agree but the wording is a bit weird. Maybe it should read:
"Do you want to enable anon ftp?" but if they just hit return it
defaults to no.
There's no way to make a libdialog yes/no requestor "default to no" or
I'd have done exactly that. C'mon, give me at least minimum credit
for having
Perhaps, but take a look at the installation... it sets it
to USA_RESIDENT="YES" (note WITH quotes).
Fixed, whoops!
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
1 - 100 of 404 matches
Mail list logo
