> Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm
> not very impressed. I was expecting some bugs but not like that...
I don't see a problem with FreeBSD 4.0 so much as a problem with
someone jumping beyond their abilities. :)
Please, go back to 3.2-STABLE. 4.0-CURRENT i
Luckycasino.com now blocked by spam filters. Sorry, as always, for
the interruption.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Weird! Fixed.
> Permissions in
> ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386
> are:
>
> drwx-- 19 root 0 1024 Jul 8 12:38
> 4.0-19990708-CURRENT
> drwx-- 19 root 0 1024 Jul 9 12:37
> 4.0-19990709-CURRENT
>
> Val
> __
> Q: I want to use this cool piece of software that's in the FreeBSD
> ports system. But I can't build it on my 3.x-stable system.
>
> Why not?
A. Likely because someone running only on a -current box last committed
a change to the port which broke it with 3.x. Please submit a bug
This is most odd - I will go investigate this. Absolutely nothing has
changed with the build scripts recently which is what makes this
so weird..
- Jordan
> Something broke with the -current snapshots generation on
> current.freebsd.org, probably a few days ago. The permissions
> aren't set ap
Already done.. :)
> Hi,
>
> The permissions of new -current snapshots on
> current.freebsd.org are still broken. :-(
>
> If everything else fails, I'd suggest to set
> up a cronjob to fix the permissions, until the
> cause of the problem is found. Putting up
> snapshots without letting us dow
> I was wondering what to attribute this better performance to. Could
> this be due to the new network driver / newbus integration?
The CVS metadata was removed, reducing the inode count per port significantly.
This results in faster extraction time and hence "faster" downloads, assuming
that ex
It sounds like ppp is simply exiting immediately. I'll turn debugging
on and give it a shot myself; perhaps somebody broke something.
- Jordan
> I should have also stated that I tried all the other "F" keys also.
> The only vty that is available/active is vty1 for debugging. Every other
> F-key
> Mkisofs is good for creating an ISO 9660 file systems. Wormcontrol and
> dd are a good combination for writing them.
This would be true if the worm driver wasn't actually dead. You
should at least check on these things before publically recommending
obsolete mechanisms. :)
In the world of CAM
All of this would be true if your personal definition of "emulator"
were the prevailing one, but that is unfortunately just not the
case. :)
When the average computing public thinks of an "emulator", they think
of something like MAME or the SNES emulator. Even the more
compute-minded folks tend
> So can we have the manufacture and model of your cd-recorder ? 8)
Yes, it's a "Smart and Friendly" (gah!) "Rocket Recorder" - it does
8X CDR, 6X CDRW and 24X CD. I like it. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the messa
> Wormcontrol uses WORM ioctls, handled by both of the ATAPI drivers.
Utterly irrelevant, not that you seem to let it stop you.
> But ATA and wcd are both not CAM. dd works just fine. You can solve data
See above. dd's unsuitableness for writing CDs has nothing whatsoever
to do with CAM.
> Yo
Others have pretty much already listed my preferences:
"Linux compatibility"
"Linux ABI support"
"Linux binary compatibility"
or any of the other obvious permutations thereof...
- Jordan
> Okay, I will bite.
>
> What would you call the linux emulator to convey the proper
> meaning to the suit
In my case, you should always assume SCSI unless expressly indicated
otherwise. I hate ATAPI devices, no insult to Soren's fine work
intended. :)
- Jordan
>
> I take it that the absence of the interface means your cd-recoder uses scsi.
>
> Tnks A Lot!
>
>
> > > So can we have the manufactur
I kinda like the idea of a top-level compat category; it will keep the
top level uncluttered when sysv and iBCS compatibility start requiring
their own knobs, and if you put linux at the top level this will later
be used as justification for putting all the other "compat" stuff up
there too. I th
Sigh.. OK, whatever Brian, it's clear that I can't communicate
with you and any future correspondence between us will be by
way of your mentor, Mike Smith. You had I have had our last
public exchange since you're now in my killfile.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
I agree with this as well.
> > "Linux compatibility"
> > "Linux ABI support"
> > "Linux binary compatibility"
>
> The suggested "linux mode", has a nice non-technical simple ring to it.
> If we called it this, the non-educated might not come away with the wrong
> idea. Management(tm) may not un
> I gather the reason for using the X trick *and* the quotes is because there
> might be some whitespace in there, too.
Actually, that's mostly just historical legacy. When the quotes, it's
safe even if the expansion is empty or contains whitespace. I got
kinda annoyed with this last night and
> The X also protected test from the case where the expansion included a
> string like "-x", although with most modern implementations of test (or
> shells with test as a builtin) this is no longer a problem.
And certainly not in any of these cases. :)
> I agree with some of your changes
> For the immediate future, it looks like it will -- it seems as though
> we don't have the man power to make the necessary changes to sysinstall
> to support "installing the docs as packages", so I'm going to fix up
> src/release/Makefile as necessary to cope with the new directory structure.
I
> As of a few days ago, ppp(8) supports the -nat flag (as well as
> the -alias flag for backwards compatibility), however, it's not
> clear that we really want to go the whole hog and change the
> library name & interface too.
I've been on both sides of this issue, to be sure, but I have to sa
> XFree86 3.9.xxx was cvsup on December 24th I am sorry but this is
> sufficient information to reproduce the problem.
Not if you actually want the problem solved. There's this thing
called "making it easy on the people you're demanding things of" in
order that they might have some chance of
Sending out an attachment of that size to a public mailing list was
hardly necessary, and the increasing stridency of your posts leading
up to this only serve to indicate that you may be heading in the truly
wrong direction with all this and seriously need to rethink your
strategy before you do so
Everything that sysinstall does WRT devs is abstracted by libdisk.
> On Fri, Dec 31, 1999 at 03:15:02PM -0500, Chuck Robey wrote:
> > On Fri, 31 Dec 1999, Wilko Bulte wrote:
> >
> > > > > Why are "certain" devices wildly different than all other ones? I've
> > > > > never encountered that kind
Dear friends,
I know that many of you may feel slightly let-down by the fact that
nothing truly significant seems to have happened during our transition
to the year 2000, a good many button-clicks on www.cnn.com having gone
for naught as the hour approached and receded, nothing following yet
more
And given that we've already slipped from December 15th, I think you
can treat this as a pretty hard deadline, to be further slipped only
grudgingly and in response to clear and dire need.
10 days, folks! Make 'em count.. :)
The code freeze will last for 15 days, during which time the 4.0
snaps
> My question is not how much time the developers are being given -- the
> *real* question is how much time the developers will give.
Thank you for saying this. If developers were constant-output
devices, we wouldn't need code freezes to motivate them into moving at
all. :-)
- Jordan
To Unsub
> There are many people who use freebsd in the real world that have been counti
ng
> on 4.0 including support for ipsec and ipv6, ipsec more importantly. We would
> be willing to wait an additional couple of months for this functionality, ple
Sadly, you've picked a particular bit of technology th
If I stick an audio CD in my SCSI (rebadged Toshiba) CDRW drive
and try to read data off of it, I get the following behavior:
root@zippy-> dd if=/dev/rcd0c bs=2k of=/dev/null
dd: /dev/rcd0c: Invalid argument
0+0 records in
0+0 records out
(cd0:ahc0:0:4:0): READ(10). CDB: 28 0 0 0 0 0 0 0 4 0
(c
It's a feature freeze, sorry. I still expect the loose-ends that are
in place as of that date to be tied up afterwards.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
[Moved to just -current; this doesn't need to keep getting cross-posted]
> It's not like were moving from v4 to v6. Were just asking that it
> be included in the OS. It should be available to researchers using
> 4.0-RELEASE. That's all im saying. There is no reason to ask for resources
> or anyth
> Hmm! Better hold the 4.0 Code Freeze until this sorts out!
No, just better sort it out more quickly than usual. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Get IPv6 into the tree. Now. Thank you.
Start helping and stop asking. Now. Thank you.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> You mean an Adaptec controller, right?
Yes, I guess Adaptec did buy those guys.
> Try tosha or cdda2wav and report back on whether or not it works. dd has
> never been a supported way to read audio tracks, for the reasons outlined
> above. It may be possible in some situations, but it was pr
> I think what is actually going on is that it doesn't like the 0x82 density
> code that most other drives use. So that's what the first error message
> likely tells us. (the density is given in the mode select parameter list,
> thus the invalid field)
>
> The second error message likely means
Also, I can now add that cdda2wav does work (hurrah), but it does yelp
that it can't read the CD TOC.
Of course, the mystery is that tosha no longer works yet was not
changed, nor was the ripit script I call tosha from, so something on
our side of the fence also moved with respect to this drive.
> In addition to trying cdda2wav, here's something else you can try in your
> tosharc:
>
> "SAF" "" "" 0x28 1 0x82 0 10 0
>
> or:
>
> "SAF" "" "" 0x28 0 0x00 0 10 0
Yep, tried both - no go.
The first produces:
(pass0:ahc0:0:4:0): MODE SELECT(06). CDB: 15 10
> I'm reading this thread, and no, I have no idea. :-)
> To be honest, I've never heard about an "SAF" drive.
It's a "Smart and Friendly CD-R8020", also sold as the "CD Rocket
Recorder" here in the U.S. It does 20X reads, 8X writes and 4X
re-writes. And no, I don't usually waste my CDR heads o
> Doesn't this statement make the entire thread about IPv6 + PC-Card support
> entirely moot? Feature freezes don't mean we can't improve those two areas,
> right? Right? :-)
PC-card, perhaps, but I think IPv6 still needs "improvement" far less
that it needs significant integration. :)
- Jordan
I think you'd do far better to stop bitching and simply start helping.
The people I've heard yell the very loudest in this discussion are
also the people who:
a) Have not helped Yoshinobu Inoue to any great extent during his
calls for patch testing.
b) Have not volunteered to help with the i
Can we please end this discussion? End it now.
It's of no importance to me or, I venture to say, the postmaster
whether or not someone wishes to use an alias in these mailing lists
and it's certainly not a topic which follows the charter for the
FreeBSD-current mailing list. In fact, the only c
> Not yet, but it should. If someone can help me out here it would be
> greatly appreciated.
"Setting it in sysinstall" is easy. Deciding where and how to set it
in response to questions at certain stages of the installations(s)
is more the sticking point.
- Jordan
To Unsubscribe: send mail t
> Jordan, I believe this change should go into 4.0-RELEASE rather than
> happening afterwards so that we have a minimal number of people
> (hopefully none) using TUNSLMODE. TUNSLMODE was never MFC'd.
Do it. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd
> I'm sure this is a silly question, but then why does usw3 appear to _be_ a
> mirror? Why have usw3 at all?
It's NOT a mirror and I really wish people would stop jumping to
conclusions with tenuous data because it's really very simple and not
like anyone is currently speculating:
1. There is
> 1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone
> into the options menu and selected "DHCP"; when I picked my network
> interface it looked for and found a DHCP server and popped up the
> network configuration box with most of the fields filled in (including
> domain name
> IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't
> setup to provide hostnames to the requrestor.
Seems they're set up incorrectly then. You can't be a good "network
citizen" these days without a resolvable hostname that also matches
your primary IP address or, among othe
> OR we can make a [binary] port of it. This would not be hard to do.
> Let me know if you prefer this approach.
I think the easiest and most POLA-friendly approach would be to add
them [back] to Xbin.tgz.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
> Why not check to see what the hostname is after dhclient is run and then
> stick that name in the network setup dialog box. If the user does edit
> the hostname themselves, then you can flag that event.
That would work in that one specific case with that specific dhcp server.
Now change the dh
> Personally I'd prefer to just fix the DHCP client so that it correctly
> sets the hostname as obtained from the server...
Yeah David, sheesh! ;)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
===> libexec/getNAME
cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge
tNAME.c
cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o
gzip -cn /usr/src/libexec/getNAME/getNAME.1 > getNAME.1.gz
===> libexec/getty
cc -O -pipe -I/usr/obj/usr/src/i386/
> That's not correct; your DHCP configuration should reflect the hostname.
>
> Sysinstall doesn't fill in the hostname field because the crunched binary
> is missing the hostname(1) command. If we were to add that, it's just
> possible that we'd get hostnames working too.
Actually, that's not
approved
> Hi,
>
> would it be ok to commit the following patch to
> /usr/src/sys/boot/i386/loader/Makefile so that we can build
> a smaller loader without Forth support, which is still useful
> to boot a picobsd kernel ?
>
> cheers
> luigi
>
> rizzo# diff -ubwr Makefile.40RC Make
Having passive mode on by default *across the board* is truly the
right thing to do in this day in age and there's no reason not to
default to it now. We've received too many tech support emails (and
phone calls) from people with firewalls who were confused with the
previous default.
- Jordan
>I have rebuilt sysinstall inside the 0207-SNAP area and can
> recreate the problem by simply running sysinstall as root and
> running an installation to /install. Also, previously, I was
> using a cdrom as the media, I am now using ftp.
Thanks for your debugging work so far. I just got back
Thanks for these - they're all known problems with the release
candidate which I'm working on correcting now. Many of these problems
stem from the fact that I don't have an "official" XFree86 release for
4.0 and I just threw my own together here with less than optimal
results. :-)
- Jordan
> He
Unless the docs people can actually make the doc tools build
again and successfully format the docs under -current. :)
Sorry for what sounds like a threat of sorts, but I've been building
the -current snapshots with NODOC=YES for months now because that
aspect of release building just hasn't work
It's being fixed as we speak; I know the problem now. :)
- Jordan
> Today The Hermit Hacker wrote:
>
> > Up until this afternoon, when I lost an IDE drive, I've been using CVSup'd
> > sources and ports, so haven't fllowed the threads too closely dealing with
> > 4.0RC, so this is probably alrea
Well, I'd first be very interested to know if anyone has even seen
this work. :)
I have seen regrettably little feedback about it so far.
- Jordan
> * David E. Cross <[EMAIL PROTECTED]> [000211 16:50] wrote:
> > I realize that we are all very busy and the coming 4.0-RELEASE has also
> > compoun
> I can understand part of the reason for this... 4.0-RELEASE is right
> arround the corner, and people are focusing on delivering a stable product,
> not introducing alpha code into the system at the last second. the current
> rpc.lockd is a known value, placing a "maybe" version into the stream
> I have been having some problems gettign Mozilla to start up under
> FreeBSD-4.0-CURRENT .. and the comments given in the Bugzilla forum
> all seem to blaim my problems to having a gcc 2.9.5.2 compiler and an (old)
> 2.9.1 assembler.
That's odd, I have M13 working just great here under -current
> Are there any plan to distribute USA_RESIDENT=NO version of
> des binary distribution?
I have no current plans to build such a thing and am USA_RESIDENT
myself so it would be a questionable thing from a legal standpoint, I
think. I can hardly wait until September when the RSA patent expires! :
They've simply been renamed - it's no biggie. I have some patches
in my inbox for adding the new acd devices, I just haven't gotten to
them yet since it's still easy enough to edit them in the "unknown"
category if one really needs to.
- Jordan
> Hi all
>
> I've been trying out FreeBSD 4.0-200
> 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 havin
> +# 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
> So do I. Unfortunately our hands are tied - the version of FreeBSD
> distributed in the US must not contain these because they are patented
> technologies and not available for unrestricted use. Unfortunately this is
> also the same version distributed worldwide on FreeBSD CDs, install
At this
> It already does this if you get your crypto from internat. US mirror sites
> only carry the neutered (no-RSA) version, but internat carries RSA and
> builds it conditional on USA_RESIDENT.
And why don't the USA sites have the RSAREF version? I'm still not
sure I understand the compartmentaliza
> > openssl becomes a "distribution" like the DES bits are. Depending on
> > external packages is actually something I'm trying to wean sysinstall
> > away from because the dependency is a PITA and the creation of the
> > packages collection is not automated in the same way that distribution
> >
Haha, so much for that issue then. :)
> "David O'Brien" wrote:
> > On Wed, Feb 16, 2000 at 09:04:44AM +0200, Sheldon Hearn wrote:
> > > > What about making FTP_INTERNAL_LS the default for 4.0?
> > >
> > > I'm very much in favour of this,
> >
> > Agreed. Do you want to bug JKH, or should I? ;
Primary:
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2214-CURRENT/
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/4.0-2214-CURRENT/install-i386.iso
[bootable ISO installation image]
Alternate:
ftp://current.freebsd.org/pub/FreeBSD/snapshots/i386/4.0-2214-CURRENT
> "Install" button and things proceeded to install with no hitches--however, i
t
> seemed that randomly (because I couldn't pick out any pattern to it) the
> screen would flash back to the "FreeBSD Configuration Menu" as it cycled
> through new packages to install. The gray dialog that shows w
> it makes sense to slice it that way. Also, as far as teaching new users how
> to install it, I _always_ show them the custom route. While this may sound
> harsh, its used to familarize them with all of sub-components, and
I really kinda wish you'd point them to Novice^H^H^H^H^HStandard
instea
> Perhaps the release notes, or hardware file need to note you really do need
> more than 8M ?
The CD boxes all say 16MB and the release notes/hardware guide don't
say anything at all about this. :)
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in t
> I am currently having a problem installing linux_base, both the port and the
> package on -current. I used to lurk to discover these problems by browsing
> the mailing list, but they are down. :-(
>
> I just cvsupped and rebuilt the world today and it still fails. Here are the
> messages:
Yes,
> Building with rsaref can't be the default case, because it's restrictively
> licensed and not legal for some people to use.
It's trying to figure out who "some" people are and how to address the
needs of people who don't fit that category that I'm still having a
hard time with here. If I have
Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out
at this point. The situation with RSA makes this far more problematic
than I think anyone first thought, and I've seen a lot of breakage so
far for what appears to be comparatively little gain over what we had
before with the
> Kris Kennaway wrote:
> >
> > On Sat, 19 Feb 2000, Victor Salaman wrote:
> >
> > > I personally think that it's braindead to add openssl to the system
> > > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to
> > > have
>
> Pardon me for coming late to the party, but what was
> Having _a_ general-purpose cryptography toolkit in the base system allows
> us to add in all sorts of cool things to FreeBSD (https support for fetch,
> openssh, random cryptographic enhancements elsewhere). OpenSSL just
> happens to be the only decent freely-available (BSDL) toolkit.
And I sti
> How does OpenBSD do it? Cant we do what they do?
1. They're in Canada
2. What they do appears to be kind of icky, e.g. it requires more
"hand work" than I think the average FreeBSD user would be willing
to accept (or the average developer would be willing to see in the
tree in such a
> Don't remove OpenSSL from the three... put the whole thing there, the whole
> openssl distro in the tree. The problem with the patent is not that you
> CAN'T get the software, the problem is that you can't build with it and use
> it. But nobody said that you can't have it in the system. It's up
> Well, you're the release engineer of course..but I don't think the
> problems are insurmountable. Sysinstall could be made to install the
> correct package after asking the user the right questions (if they choose
> to install crypto):
Again, I simply do not wish to depend on any more packages
> Given that we can't import rsaref into FreeBSD and we can't depend on it
> as a port, that about rules out any options for installing from
> sysinstall. The remaining possibility is what we have now, namely manual
> installation of the package post-installation, which is documented in the
> hand
> On Sun, 20 Feb 2000, Jordan K. Hubbard wrote:
>
> > Well, I guess I'll be less frantic about this when I see the ports
> > infrastructure working properly with this - having openssh fail
> > came as a rude shock. :)
>
> See Jim Bloom's patch of earli
> How does OpenBSD deal with it? Why is it so easy for them?
It isn't. Go look for yourself.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Sat, Feb 19, 2000 at 08:34:42PM -0800, Jordan K. Hubbard wrote:
> >
> > 1. They're in Canada
>
> What does that buy them? They have the same restrictions on rsaref since
> it originated from the USA.
I don't believe they're under the same legal
> The /compat symlink should just die. compat bits should not be on the
> root partition, so why are we pretending? /usr/compat should be the only
> supported place. Peroid.
You miss the point entirely. Compat bits aren't intended for the root
partition, they're intended for wherever you happ
> Jordan, please approve this patch.
>
> It seems not good to have FTP_PASSIVE_MODE On as default while ftp program
> itself have it Off by default. Lets either change ftp program defaults to
> Passive On or login.conf defaults to Passive Off. I prefer second variant:
Um, the point of turning FT
> 0. RSA situation
> [ a very nice point-for-point analysis of the situation elided ]
Christian,
Thank you for this summary; it helps a lot to have all the relevant
information presented in one place like this. Now we can begin
cutting to the heart of this matter, which I'll do in the form of
e
OK, I've dinked around with this some more and I think I might have at
least a partial solution to this whole mess (it still doesn't make
openssl actually useful to us, it just makes it less annoying :).
First, apply the following patch:
Index: Makefile
==
> And how exactly are you going to tell /usr/bin/login, /usr/bin/chpass,
> /usr/local/bin/wu-ftpd, etc., where to find that file? Remember, if
> it's ports that read the setup file, it can be moved around anywhere
> by changing PREFIX -- but for files that are read by the system, it is
If it's P
> When is the estimated release of the FreeBSD-current 4.0?
First week of March.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
root@zippy-> cc -fPIC -c stub.c
root@zippy-> ld -shared -o stub.so stub.o
root@zippy-> cc -static test.c -o test stub.so
root@zippy-> ./test
ELF interpreter /usr/lib/libc.so.1 not found
Abort trap
root@zippy-> cc -static test.c -o test stub.o
root@zippy-> ./test
Now in the client, calling doit()
> > Yes, a clean install.
> > No, the sysinstall version of /etc/group did not have the tag.
>
> Ok, that's bad. I'm cc'ing Jordan so he can look into it. Thanks for th
e
> report. These are the little things that really need to be tested.
I'm not sure I understand this - sysinstall doesn
> As a workaround for a static binary, you should be able to use
> -Xlinker -Bstatic
> instead of
> -static
Actually, it appears that just -Xlinker is necessary; it works
fine in conjunction with -static. Thanks for this most helpful
tip! I can see a *lot* of scenarios where I'll be using
-
Since it came down to making openssl actually useful for something or
taking it out of the tree, we accelerated progress somewhat on the
openssh integration work. This is using the rsarefglue stubs I've
been talking about for the last couple of days to "abstract" rsaref
away so we don't have any
> 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
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 por
1 - 100 of 454 matches
Mail list logo
