Chuck Robey wrote:
>
> > If you are running -stable
>
> This is the -current list, and I'm running current. I don't have the
> file "userconfig_script" nor /kernel.config.
Just to be on the safe side... :-)
> > OTOH, you might solve your problem just by adding the following two
> > lines to /b
> BTW, do you plan to include egcs' g77 as well?
Current, the g77 driver is built. But the f771 isn't. From previous
talk, I've gotten the impression g77 should be a port vs. in the base
system. I'm Ok either way -- I leave the decision to the lists and Core.
--
-- David(obr...@nuxi.com
> The pnp line is a "userconfig" type of information. It must, then,
> be put on a file to be loaded with "-t userconfig_script" flag. But,
> as I said, I have little familiarity with userconfig stuff. I think
> it is the commands you would type if you booted -c and entered the
> commands manually
"Jordan K. Hubbard" wrote:
>
> > The pnp line is a "userconfig" type of information. It must, then,
> > be put on a file to be loaded with "-t userconfig_script" flag. But,
> > as I said, I have little familiarity with userconfig stuff. I think
> > it is the commands you would type if you booted -
Hi!
I was wondering why 4.0-Current still uses gcc 2.7.x instead of gcc 2.8.1,
which is available in the ports. gcc 2.8.x supports 586/686 optimization
and much more, whereas 2.7.x will compile for 486 processors. Are there
any compatibility problems involved when replacing 2.7.x by 2.8.x? If not,
> I was wondering why 4.0-Current still uses gcc 2.7.x instead of gcc 2.8.1,
Review the freebsd-current mail archives (http://www.freebsd.org/ ->
support).
Short answer -- it is being worked on. We don't jump into the newest fad
technology. gcc281 and egcs needed to be proven to be stable and u
Hi folks,
I have a proposal regarding the OBJLINK option; let's drop it.
Currently, OBJLINK breaks world when NOAOUT is undefined -- that is, for
the legacy build. This is because making the objlink target for aout
libraries blows away the existing objlinks that have already been
created for bu
On Sun, 14 Mar 1999 16:33:29 +0200, Sheldon Hearn wrote:
> I have a proposal regarding the OBJLINK option; let's drop it.
Perhaps I should have fleshed out the "how" more. I focused mostly on
the "why".
I'm suggesting that:
1) PR misc/8071 be examined.
2) People acknowledge that this isn't he
David O'Brien wrote:
> > BTW, do you plan to include egcs' g77 as well?
>
> Current, the g77 driver is built. But the f771 isn't. From previous
> talk, I've gotten the impression g77 should be a port vs. in the base
> system. I'm Ok either way -- I leave the decision to the lists and Core.
>
In message <65294.921422...@axl.noc.iafrica.com>, Sheldon Hearn writes:
>
>Hi folks,
>
>I have a proposal regarding the OBJLINK option; let's drop it.
I concur. Lets try to reduce the amount of Makefile-hair for once.
--
Poul-Henning Kamp FreeBSD coreteam member
p...@freebsd.org
Hi folks,
As mentioned in PR misc/5207, /usr/share/examples/etc/README says that
the directory contains virgin copies of the files installed into /etc .
This isn't true, of course.
I've attached to the PR diffs that would cause /usr/share/examples/etc
to be populated correctly. I've tested the c
Sheldon Hearn wrote:
> Diffs to do just this are attached to PR misc/8071. I've tested the
> diffs through a buildworld+installworld, but would appreciated feedback
> on a release build.
Nuke the festering slag :-) (Or gimme fresh patches and I'll do it!)
M
--
Mark Murray
Join the anti-SPAM movem
I hate to roll up old threads, but it seems like nothing has come out of
the Postfix vs. sendmail debate on this list.
We don't even have a Postfix port. Has anybody created a port or should I
go ahead and have a look at it?
Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz
Medinet d.o.o., L
Blaz Zupan wrote:
> I hate to roll up old threads, but it seems like nothing has come out of
> the Postfix vs. sendmail debate on this list.
>
> We don't even have a Postfix port. Has anybody created a port or should I
> go ahead and have a look at it?
I would be very pleased to see a Postfix por
On Sun, 14 Mar 1999, Jeroen C. van Gelderen wrote:
> Blaz Zupan wrote:
> > I hate to roll up old threads, but it seems like nothing has come out of
> > the Postfix vs. sendmail debate on this list.
> >
> > We don't even have a Postfix port. Has anybody created a port or should I
> > go ahead and
> I hate to roll up old threads, but it seems like nothing has come out of
> the Postfix vs. sendmail debate on this list.
> We don't even have a Postfix port. Has anybody created a port or should I
> go ahead and have a look at it?
Postfix is working great for me. I replaced sendmail on a "light
I had a very weird problem with the new parallel port device that caused
this to occur. It turned out to be speculative probing by the parallel
device causing the system to go unstable.
Try disabling the new parallel port device(s)/controllers and see if you
can boot again.
For those of you using the VN device as a loadable module, please be aware
that the new VN device has been committed to -4.x and cannot yet be
used as a loadable module.
Be sure that you are not improperly using the stale loadable module for
VN under -4.x that might still resid
Exceptions are made for people who really know what they are doing, verses
only think that they know what they are doing :-)
* Do not use any loadable modules, compile the needed modules into the
kernel directly. To double check, run 'kldstat' after booting the
system and
When I boot up my -current box, I hit 'c' to get to the boot prompt. Then
I do "boot -c", and then "vi" to configure my kernel. But any changes I
make via userconfig aren't saved for when the next time I boot.
Is it a problem with the boot loader, or do I have to type some commands
to save my co
The answer depends on exactly how current you are...
With -current from a few days ago, I would have said:
Make sure you have a /boot/loader.rc file that contains at least
these lines:
load /kernel
load -t /boot.config
Then, make sure /boot.config contains all the stuff that you would
normally
And to supplement this- please try and isolate problems to areas of likely
failure. In particular, SCSI driver related problems go to
freebsd-s...@freebsd.org- they're read and responded to quicker there than
freebsd-hackers or freebsd-current. Thanks.
To Unsubscribe: send mail to majord...@
On Sun, 14 Mar 1999, Matthew Dillon wrote:
> Exceptions are made for people who really know what they are doing, verses
> only think that they know what they are doing :-)
>
> * Do not use any loadable modules, compile the needed modules into the
> kernel directly. To double
A pity. This would mean g77 gets a fair chance to once again become quite
obsolete. Of course, it's not all that important 'far as servers are
concerned, but as I'm in high energy physics - I should say so far all my
colegues I know used FORTRAN rather than C/C++. Well, that still doesn't
make us a
>I have a proposal regarding the OBJLINK option; let's drop it.
No, it is quite useful for actually working with the objects (it saves
some `make whereobj's...).
>Currently, OBJLINK breaks world when NOAOUT is undefined -- that is, for
>the legacy build. This is because making the objlink target
Matthew Dillon wrote:
> - error = acquire(lkp, extflags,
> - LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE);
> + if (p->p_flag & P_DEADLKTREAT) {
> + error = acquire(
This is broken: p may be NULL, it i
Donald J . Maddox wrote:
> The answer depends on exactly how current you are...
>
> With -current from a few days ago, I would have said:
>
> Make sure you have a /boot/loader.rc file that contains at least
> these lines:
>
> load /kernel
> load -t /boot.config
>
> Then, make sure /boot.config
Yeah, you're right on all counts, of course...
I've answered this question so many times in
the last 10 days that I'm starting to go on
autopilot :-/
Robert Nordier wrote:
>
> Donald J . Maddox wrote:
>
> > The answer depends on exactly how current you are...
> >
> > With -current from a few day
On Fri, Mar 12, 1999 at 03:17:10PM -0800, Jordan K. Hubbard wrote:
> This is done by make release in the chroot area.
Ah. So it is.
> > 2. Make sure /usr/doc/ is up to date (or wherever you store a
>
> This will have no effect on the chroot area - it's checked out
> by make release. :)
>
>
[ redirected to ports ]
According to Blaz Zupan:
> We don't even have a Postfix port. Has anybody created a port or should I
> go ahead and have a look at it?
Please wait a few days if you insist on a port, Wietse will release a new
version with quite a number of new features. In any case, a Post
>> BTW, do you plan to include egcs' g77 as well?
>Current, the g77 driver is built. But the f771 isn't. From previous
>talk, I've gotten the impression g77 should be a port vs. in the base
>system. I'm Ok either way -- I leave the decision to the lists and Core.
>- --
>- -- David(obr...@n
On Sun, 14 Mar 1999, Blaz Zupan wrote:
> We don't even have a Postfix port. Has anybody created a port or should I
> go ahead and have a look at it?
FWIW, I installed Postfix on an experimental box here (since it's
still in 'Beta'). I've been happy with its performance, although I've
not really
> Please wait a few days if you insist on a port, Wietse will release a new
> version with quite a number of new features. In any case, a Postfix port
> will not be very difficult to do.
Actually, I already had a go at it. A first version of the port can be
downloaded from ftp://ftp.si.freebsd.org
:>
:> * Do not use any loadable modules, compile the needed modules into the
:> kernel directly. To double check, run 'kldstat' after booting the
:> system and make sure that only the kernel is listed.
:
:This does not mean that modules are thought to be broken, just that it
:obsc
:Matthew Dillon wrote:
:> -error = acquire(lkp, extflags,
:> -LK_HAVE_EXCL | LK_WANT_EXCL | LK_WANT_UPGRADE);
:> +if (p->p_flag & P_DEADLKTREAT) {
:> +error = acquire(
:
:This is broken: p may be NULL, i
35 matches
Mail list logo
