At 10:12 AM 3/17/00 -0500, Will Andrews wrote:
>On Fri, Mar 17, 2000 at 10:00:44AM -0500, Kelly Yancey wrote:
> > This is all beginning to smell a lot like a FTP install.
>
>Exactly. Only thing is, an FTP install requires a usable internet
>connection on intended box, which is not always availab
At 09:46 AM 3/17/00 -0500, Will Andrews wrote:
>On Wed, Mar 15, 2000 at 11:59:29AM -0600, Jeffrey J. Mountin wrote:
> > However, if you consider the size of the file and the possibility of
> > corruption, then it should be archived with gzip and forget the
> compression
>
At 11:01 PM 3/15/00 -0500, Donn Miller wrote:
>Sounds like one of those nasty gcc optimization bugs. I generally
>build my kernel and world with -mpentium -O3 -pipe, and I haven't seen
>any bugs at all. I build everything with these flags without
>problems. The only problems I've see, as mentio
At 01:42 PM 3/16/00 +0100, Christian Weisgerber wrote:
>David O'Brien <[EMAIL PROTECTED]> wrote:
>
> > What??? 'pentiumpro' code isn't going to be very optimized for a Pentium
> > (if it even runs at all).
>
>According to the gcc(1) man page, -mpentiumpro is synonymous to
>-mcpu=pentiumpro, which
At 11:09 PM 3/15/00 +0100, Oliver Fromme wrote:
>That's true. Most of the files in the ISO images are already
>compressed, so trying to gzip it saves only a few percent.
>
>Also take into account that many people are downloading and
>recoding the images on Windows boxes, which don't have gzip
>by
Well now...
Successfully did a buildworld with -O -pipe -march=pentiumpro, installworld
was good, remade /dev and built a generic kernel. Config'd my local kernel
and within the first few lines of 'make depend' it bombed:
> gdb -k kernel.debug vmcore.0
GNU gdb 4.18
Copyright 1998 Free Softwa
At 05:53 AM 3/15/00 -0800, Alfred Perlstein wrote:
>* Kai Voigt <[EMAIL PROTECTED]> [000315 05:47] wrote:
> > Matt Heckaman wrote:
> > > It's been my experience that gzipping an ISO (or other compression tools)
> > > do not make enough different to justify the time it takes to both
> compress
> >
At 12:48 PM 3/15/00 -0500, Donn Miller wrote:
>I've noticed various compile-time optimization bugs as well. For
>example, I tried building Qt with -mpentium -O3 -pipe, and somewhere
>during the build, I get "Internal compiler error." Falling back to
>the stock optimization levels of -O2 fixed t
At 05:30 PM 3/12/00 -0600, Jeffrey J. Mountin wrote:
>At 06:04 PM 3/12/00 -0500, Brian Dean wrote:
>>Hi,
>>
>>I am building a release and am getting a failure during the doc phase
>>due to a port problem, (/usr/ports/www/w3m to be exact). This port is
>>built dur
At 06:04 PM 3/12/00 -0500, Brian Dean wrote:
>Hi,
>
>I am building a release and am getting a failure during the doc phase
>due to a port problem, (/usr/ports/www/w3m to be exact). This port is
>built during make release, and it builds a program called 'mktable',
>which core dumps, causing the wh
At 05:43 AM 3/11/00 -0800, David O'Brien wrote:
>On Fri, Mar 10, 2000 at 07:45:33PM -0600, Jeffrey J. Mountin wrote:
> >
> > Hopefully that "yet" will be "never" so one can boot sans keyboard and
> > later hook one up if need be.
>
>For me it
At 09:19 PM 3/10/00 -0600, Ryan Thompson wrote:
>Me as well...For at least a decade. I used to do it manually all the
>time, but had occasional glitches with funny scan codes and indicator
>statuses. With a mid-range priced switch, though, I have had no problems
>whatsoever.
The only glitches I
At 05:54 PM 3/10/00 -0800, Mike Smith wrote:
>Since you can't safely hot-plug the PC keyboard, that wouldn't be very
>smart. The only way to auto-detect the use of a serial console is to
>look for a keyboard; if one isn't plugged in, there's no local console,
>end of story.
Can't safely? Why th
At 12:23 PM 3/10/00 -0800, Jordan K. Hubbard wrote:
> > 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
At 05:06 PM 3/10/00 -0800, Mike Smith wrote:
>Note also that the probe-for-keyboard feature is only used on the
>installation media; it's not the default for system behaviour (yet).
Hopefully that "yet" will be "never" so one can boot sans keyboard and
later hook one up if need be.
Jeff Mounti
At 05:35 PM 3/8/00 +, Kris Kennaway wrote:
>On Wed, 8 Mar 2000, Jeffrey J. Mountin wrote:
>
> > What I did not check is removing RSAref after a buildworld and checking for
> > breakage, but that smacks of shooting one's self in the foot.
>
>That should just r
At 09:26 AM 3/8/00 -0800, Jordan K. Hubbard wrote:
>> 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.
At 07:39 AM 3/8/00 -0800, Jordan K. Hubbard wrote:
>> 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
CC's trimmed...
At 07:42 AM 3/8/00 -0500, Jim Bloom wrote:
>In either case, the answer is that you do not need to install the rsaref
>port before any builds. It is only a runtime dependency now.
>
>Jim Bloom
>[EMAIL PROTECTED]
>
>Walter Brameld wrote:
>>
>> > Do you still need to install the rs
At 12:24 PM 3/3/00 -0500, Andrew Gallatin wrote:
>
>I'm just wondering -- when is RC3 expected? ? A lot has happened
>since the 2/14 snap..
Try the 2/28 snap, unless another has been made within the day.
Doubtful.
At lot is still happening, so the 3/10 release will be changed.
Jeff Mountin -
At 03:14 AM 3/3/00 -0800, Devin Butterfield wrote:
>Sheldon Hearn wrote:
>>
>> Hi folks,
>>
>> Shouldn't I be able to show the current tuneables for a given filesystem?
>>
>> # tunefs -p /usr
>> tunefs: cannot work on read-write mounted file system
>>
>> This is on a recent CURRENT.
>
>AFAIK,
At 01:30 PM 2/28/00 -0800, Kris Kennaway wrote:
>On Mon, 28 Feb 2000, Chris Timmons wrote:
>
>>
>> I tried starting sshd via the rc.conf infrastructure after another
>> buildworld/installworld this morning and still see the:
>>
>> sshd[166]: fatal: rsa_private_decrypt() failed
>>
>> error.
Have a few issues...
(pardon the laundry list :)
Background:
Fresh install of RC2 (4.0-2214-CURRENT).
Fresh meaning remove slices, create, yada...
After install, tweak some minor things while building an SMP kernel,
install pdksh and less from ports, and install CVSup.
Update source, check
At 10:07 AM 2/26/00 +1300, Dan Langille wrote:
>On 25 Feb 00, at 22:03, O. Hartmann wrote:
>
>> One of our two servers will not perform "buildworld"! Well, kernel stuff
>> should be on the newest track, I cvsup-dated them both today.
>>
>> After a short while making dependencies it stops with the
At 04:33 PM 2/24/00 -0800, Kris Kennaway wrote:
>On Thu, 24 Feb 2000, Jeffrey J. Mountin wrote:
>
>> So when is this event scheduled to end, so we can go for a test drive?
>>
>> 57^H^H61 commits to -current and counting...
>
>The last message to show up in the ser
At 12:58 AM 2/25/00 +0200, Mark Murray wrote:
>Gimme a break, I'm getting there! :-)
So when is this event scheduled to end, so we can go for a test drive?
57^H^H61 commits to -current and counting...
Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve
At 02:51 PM 2/24/00 -0800, David O'Brien wrote:
>On Wed, Feb 23, 2000 at 02:27:31PM +0800, User URANIA wrote:
>> I also set these flags at my /etc/make.conf
>> CFLAGS= -mpentiumpro -O6 -pipe -funroll-loops -fexpensive-optimizations
>> COPTFLAGS= -mpentiumpro -O6 -pipe -funroll-loops
>
>-O6 (an
At 01:59 PM 2/24/00 -0800, Alfred Perlstein wrote:
>* Dan Langille <[EMAIL PROTECTED]> [000224 13:45] wrote:
>> I'm guessing this is related to jkh's mention of OpenSSH coming into
>> the tree, but I'm posting it anyway. Just in case it helps. my cvsup is
>> less then 4 hours old.
>>
>> ===>
At 10:15 PM 2/21/00 -0800, Jordan K. Hubbard wrote:
>> > 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 te
At 08:37 PM 2/21/00 -0800, Doug Barton wrote:
> Hrrmm... so you did a clean install from floppies, etc. and the installed
>version of /etc/group didn't have a $FreeBSD tag? I'm a little confused by
>your account.
Yes, a clean install.
No, the sysinstall version of /etc/group did not have t
Nothing major
Finished a build, installed, and mergemaster points out that the $FreeBSD
line is missing from the /etc/group binary install. Only a touch
irritating. 'Twas the case with RC1 as well, but when I merged the temp
and original version it lumped the ID with a comment and the wheel
At 10:17 PM 2/19/00 -0800, Kris Kennaway wrote:
>This doesn't help. The RSA source not being there isn't the problem, the
>problem is that there are two different binary versions depending on how
>you build it (with rsaref or not). Source code builds aren't a problem,
>they already work fine, it's
At 10:36 AM 2/18/00 -0800, Jordan K. Hubbard wrote:
>I will also say here and now that even I use the Standard installation
>since I don't like having to remember all the canonical steps in setting
>up a "stock" system and if anybody should remember them, it should be
>me - I've probably installed
At 09:50 PM 2/18/00 -0800, R Joseph Wright wrote:
>I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would
>like to know how to change over the devices. I created the new devices
>by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running
>it, but it didn't create an
CVSup -current as of Wed Feb 16 04:11:01 CST...
Figured I'd try a build/install from source before wiping it all for the
latest RC:
===> gnu/usr.bin/binutils/doc
install-info --quiet --defsection="Programming & development tools."
--defentry="* As: (as).
The GNU assembler." as.info /usr
At 10:15 PM 2/10/00 -0800, John Polstra wrote:
>In article <[EMAIL PROTECTED]>,
>Jeffrey J. Mountin <[EMAIL PROTECTED]> wrote:
>>
>> In the context of CVSup server connections it would not be. Have to
>> chuckle when I hear someone doing CVSup for ports-all
At 05:55 PM 2/10/00 -0800, Matthew Dillon wrote:
>:Sounds good, but again how will the CVSup file for ports and CVSup itself
>:deal with this. Either a "refuse" file would need to be created and then
>:populated or there would need to be other changes. Not sure Mr Wraith or
>:the CVS maintainers
At 11:45 AM 2/10/00 -0800, Matthew Dillon wrote:
>
>:> contain.
>:
>:Here's what we can do. We keep all the "major" subdirectories in
>:place, such as audio, devel, etc. BUT, instead of branching out into
>:separate subdirectories, we can just put everything into the
>:Makefile. For example, h
At 09:58 PM 2/9/00 +0100, Kai Voigt wrote:
>Hello,
>
>I'm just doing a cvsup update of my system and -as many times before- I
>realize that /usr/ports/ takes a lot of time and also disk space to sync.
>
># du -sk /usr/ports
>71118 /usr/ports
Is that just source or with some distfiles and /work
At 10:57 AM 10/1/99 +0930, Greg Lehey wrote:
>You're not typical. But you *can* grow concatenated plexes. You just
>can't expand UFS to use the space. That's not a Vinum issue, but
>somebody's working on it.
Yes, I realized that and donned a pointy hat.
Root (/) and OS specific files are of i
At 10:19 AM 10/1/99 +0930, Greg Lehey wrote:
>This is -CURRENT. Expect work in progress. From the commit log:
>
>> replaceobject: Add preliminary code. This is not yet complete.
>>
>> Add keyword 'hotspare'.
Yessir. Read -current, track commits, eat my veggies, get a bit of sun
every other we
At 09:44 AM 10/1/99 +1000, Peter Jeremy wrote:
>I was thinking of some `production' code (written by a sister company)
>that I used to provide customer support for. It would regularly core
>dump (but was automatically restarted). After a few years they did
>manage to fix the core dump, but that
At 12:59 PM 9/28/99 +1000, Peter Jeremy wrote:
>On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
>> Good software shouldn't panic.
>I wish _I_ could convince some people of this :-(.
It can be difficult to consider what a user can do and tends to bloat the
code a bit. Frustrates my i
At 03:14 PM 9/28/99 +0930, Greg Lehey wrote:
>> And the preferred method is...
>> a) /dev/da0
>> b) /dev/da0s1
>> c) /dev/da0s1e
>> (-current and -stable I hope :)
>
>(b) or (c). (a) isn't a slice. Note that it won't take slice c,
>either.
Thanks for the clarification. Was recalling a past dic
At 08:41 AM 9/28/99 +0930, Greg Lehey wrote:
>It has changed (again).
And the preferred method is...
a) /dev/da0
b) /dev/da0s1
c) /dev/da0s1e
(-current and -stable I hope :)
>> Not to surprising that it paniced with what appeared to be a
>> "dedicated" disk (ie da0e).
>
>It's surprising. Good s
At 01:05 PM 9/27/99 -0400, Brad Chisholm wrote:
>Well, I believe I discovered the source of my problem. It turns out that
>I did not have the correct devices configured in /dev for the component
>drives. I had da[0-3]e, but not da[0-3]s1e. The documentation seemed to
>indicate that the da?s1?
46 matches
Mail list logo