On Mon, Nov 15, 1999 at 05:44:12PM -0800, David Greenman wrote:
I agree that we need to get rid of 'e' and any other options that allow
reading another process's environment.
I think it would be sufficient, to allow only root to use the 'e' option.
There is no need to get rid of it
On Thu, 18 Nov 1999, Andreas Klemm wrote:
On Mon, Nov 15, 1999 at 05:44:12PM -0800, David Greenman wrote:
I agree that we need to get rid of 'e' and any other options that allow
reading another process's environment.
I think it would be sufficient, to allow only root to use the 'e'
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../intl
-DLOCALEDIR=\/usr/local/share/locale\ -g -O2 -c makeinfo.c
makeinfo.c: In function `xrealloc':
makeinfo.c:1205: parse error before `void'
makeinfo.c:1209: `exit_value' undeclared (first use this function)
makeinfo.c:1209: (Each undeclared
On Fri, 15 Jan 1999 ea...@phc.igs.net wrote:
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../lib -I../intl
-DLOCALEDIR=\/usr/local/share/locale\ -g -O2 -c makeinfo.c
makeinfo.c: In function `xrealloc':
makeinfo.c:1205: parse error before `void'
makeinfo.c:1209: `exit_value' undeclared (first use
I have found that the mixer has the volume controls for the synth
and cd devices swapped. Strangely, this swap does not affect the
recording source selection (mixer =rec cd properly sets the CD as
recording device).
I have tested this using mixer(8), xmmix and kmix, so the problem
resides in the
On Thu, 14 Jan 1999, Brian Somers wrote:
: But this isn't necessarily a good idea as it may attract a pile of
: ``why the hell did you break my configuration for no good reason''
: messages.
:
: Anyone with any strong opinions on this ?
:
: Of course it's not guaranteed that libalias will
Hello,
I'm using ctm-cvs for synchronizing my CVS-Tree.
But sometimes I get MD5 checksum errors when apllying the ctm's.
To resynchronize my ctm's with the CVS-Tree i have to use cvsup at
ctm.freebsd.org with the option strictrcs. Many files have to
be retransmitted and many fixup's appear.
Is
I have similar experiences. I sometimes do a make release with an NFS
mounted chroot environment. My latest successful build is dated from
Dec 21. All of the later builds (starting Jan 6th) failed. The error
seems to be very deterministic though. I have at least a lot of garbage
in
Actually the good news is that the problems I see with the XFree86-contrib
port are absolutely reproducible. To be sure I set the test case up on a
different set of machines than the pair at home on which I first noticed
it.
I'll dig a little more this weekend and perhaps I can correlate my
On Wed, Jan 13, 1999 at 05:26:40PM -0500, Brian Feldman wrote:
...
How could it be memory when it's written to disk, extracted, then after a
nearly
full build read again? Why would it extract completely the first time with no
errors?
I had this exact same problem when evaluating pentium
I will happily take the patches and test it on -current :)
-Jim
On Thu, 14 Jan 1999, Brian Handy wrote:
Anyone running the new windowmaker (0.50.2) on current? Any problems,
advice, pitfalls? The windowmaker port is out of date (0.20.3).
I'm running it on -STABLE...no -current box
Is the SB PCI 128 supported yet in -current. I new a new sound card and I
really would like a 'real' Sound balster.
On Fri, 15 Jan 1999, Satoshi Asami wrote:
* From: br...@worldcontrol.com
* So I am now mostly back the square 1. I'm still using an old GUS MAX,
* which at the whim of
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are pressed.
Solution? Putting the command kldunload splash_bmp before
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are pressed.
Solution? Putting the command kldunload splash_bmp
Am I still safe to do the equivalent of a 'remote' install world? - I have 2 x
3.0 boxes, one which is fresh 3.0-RELEASE, the other which is 3.0-CURRENT...
If I take the /usr/src /usr/obj directories from sucsessful 'buildworld' on
the -current machine can I run an 'installworld' on the -release
With this commit, I'm trialling a simple method for providing tuning
hints for otherwise statically-set parameters from the bootloader.
You can now say:
set kern.ipc.nmbclusters=
to effectively set NMBCLUSTERS to .
I've looked at other approaches, particularly a hook in the
I love it. Haven't tried it, but the concept is great, and on the
assumption it works, will make things even easier...
Keep 'em coming. :)
On Fri, 15 Jan 1999, Mike Smith wrote:
With this commit, I'm trialling a simple method for providing tuning
hints for otherwise statically-set
It would be kind of cool if when managing a remote system if /kernel
failed to boot, then on the next boot, the loader will fire up
/kernel.old, or a /kernel.somethingorother.
Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and
have at least some assurance that I'll
It would be kind of cool if when managing a remote system if /kernel
failed to boot, then on the next boot, the loader will fire up
/kernel.old, or a /kernel.somethingorother.
Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and
have at least some assurance that I'll
Hi All!
I recently installed FreeBSD 3.0-RELEASE from ftp.freebsd.org and
Apache/1.3.2 (Server version: Apache/1.3.2 (Unix). Server built: Oct 14
1998 23:19:52) from
ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/packages/www/apache-1.3.2.tgz .
After running 'pkg_add apache-1.3.2.tgz' I
I must have missed this on the list, but I caught a sig11 on
sysinstall from 3.0.0-19990106-SNAP. DEBUG on VTY2 reports:
DEBUG: diskPartitionWrite: Examining 1 devices
DEBUG: bootalloc: can't stat /boot/boot1
DEBUG: bootalloc: can't stat /boot/boot2
DEBUG: Signal 11 caught! That's bad!
Ideas?
I must have missed this on the list, but I caught a sig11 on
sysinstall from 3.0.0-19990106-SNAP. DEBUG on VTY2 reports:
DEBUG: diskPartitionWrite: Examining 1 devices
DEBUG: bootalloc: can't stat /boot/boot1
DEBUG: bootalloc: can't stat /boot/boot2
DEBUG: Signal 11 caught! That's bad!
FYI, when I rcp (actually, rsync) a certain makefile (ppp -alias), I
get lots of these, and it never completes:
Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored
Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored
Warning: CCP: deflink: Unexpected ResetAck (id 51)
I got this message after getting the newest source from cvsup today
(15.01.1999, about 14 h GMT). I compiled the sources then installed
everything and compiled a new kernel. So, the kernel stops after
recognition of the NIC when accessing the first SCSI adaptor of two
(first Adaptec AHA2940UW,
That particular feature could also be done with once-persistence
as in: On next reboot load this file...
In message 199901151746.jaa01...@dingo.cdrom.com, Mike Smith writes:
It would be kind of cool if when managing a remote system if /kernel
failed to boot, then on the next boot, the
That particular feature could also be done with once-persistence
as in: On next reboot load this file...
Sure. The problem is just implementing any persistence at all.
Consider that we support the following backing-stores for the kernel:
- UFS on local disk
- (V)FAT(32)
- NFS
- TFTP
Poul-Henning Kamp wrote:
Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and
have at least some assurance that I'll eventually be able to get back to a
kernel I could use.
Hmmm... This does rely on the 'stuffed-kernel' eventually cleanly rebooting
the machine, we don't
Hi,
My src tree is current as of 2:00 EST (35 minutes ago), and I'm
seeing the following failure:
cp dl_dlopen.xs DynaLoader.xs
/usr/obj/usr/src/tmp/usr/bin/miniperl
-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib
-I/usr/obj/usr/src/gnu/usr.bin/perl/perl/lib
Hello!
First of all I appologize if any of these problems have been addressed on the
-current list, I am not subscribed, and at the moment don't have much
time to carefully browse through the archive of the -current.
However, after a quick glance I didn't find it reported.
All this is related to
After a cvsup and make world this AM, I get
.: Out of file descriptors
then I am thrown into single user, and the booting
process stops.
Can someone advise me what is causing this, and what I have to
do to eliminate the problem?
Thanks in advance!
Tom
To Unsubscribe: send mail to
On Fri, 15 Jan 1999, Zach Heilig wrote:
On Wed, Jan 13, 1999 at 05:26:40PM -0500, Brian Feldman wrote:
...
How could it be memory when it's written to disk, extracted, then after a
nearly
full build read again? Why would it extract completely the first time with
no
errors?
I had
On Fri, 15 Jan 1999, Mike Smith wrote:
That particular feature could also be done with once-persistence
as in: On next reboot load this file...
Sure. The problem is just implementing any persistence at all.
Consider that we support the following backing-stores for the kernel:
-
On Fri, 15 Jan 1999, Mike Smith wrote:
Obviously we can't write to CDROMs, but a persistence mechanism needs
to work with each of these others. I've been leaning towards a very
simple solution using a small, preallocated file which we just
overwrite. It's not beautiful, but it's
On Fri, 15 Jan 1999, Mike Smith wrote:
On Fri, 15 Jan 1999, Mike Smith wrote:
Obviously we can't write to CDROMs, but a persistence mechanism needs
to work with each of these others. I've been leaning towards a very
simple solution using a small, preallocated file which we just
On Fri, Jan 15, 1999 at 02:51:01PM -0500, Brian Feldman wrote:
Good to know I am looking in the right place.
I switched my timings from Turbo to Normal (I have 2 EDO/2 FP), and now it
seems to past tests, but I think I did see a few bytes get corrupted in an
image
in netscape... ah well, so
I've been thinking about this same thing, and I thought that relatively
static fallback list of environments plus an (persistant) index to tell
you what you've tried so far might work. I was considering stealing a
byte from the RTC CMOS to hold the state between reboots.
louie
To Unsubscribe:
I recently purchased an optical drive for doing backups. After doing a
backup, I naturally flipped the switch to write protect.
At a later point, I needed to restore some files from the backup, and
so, stuck the disk back in, and mounted it.
When I was done, the disk wouldn't unmount. When I
It needs to be a general solution, and see above, again, for the things
it needs to be able to do.
So for FFS, it could be stored in the superblock, label, or one of the other
structures that aren't actually inodes, right? For FAT, couldn't it be stored
in
either the FAT or the volume
On 15 Jan 1999, Cory Kempf wrote:
I recently purchased an optical drive for doing backups. After doing a
backup, I naturally flipped the switch to write protect.
At a later point, I needed to restore some files from the backup, and
so, stuck the disk back in, and mounted it.
When I
According to Boris Staeblow:
Is it possible that there are slight differences between the
CTM's and the real world ?
There should not be.
Is CTM a little neglient when the diffs are generated?
I cannot say anything else than it has been working for me for several
years and the few times it
On Fri, 15 Jan 1999, Karl Pielorz wrote:
Am I still safe to do the equivalent of a 'remote' install world? - I have 2 x
3.0 boxes, one which is fresh 3.0-RELEASE, the other which is 3.0-CURRENT...
If I take the /usr/src /usr/obj directories from sucsessful 'buildworld' on
the -current
On Fri, 15 Jan 1999, Igor Shulgin wrote:
What I have done wrong?
Is it possible to run Apache 1.3.x on FreeBSD 3.0 ?
Yes but you need to install a more recent port or package. The
conversion to ELF tripped up a few things like Apache that didn't
know about ELF FreeBSD systems. That is all
Zach Heilig z...@uffdaonline.net wrote:
Except simm checkers don't always catch errors, so if the simm passes,
there still is no guarantee (but simm checkers do weed out obvious
duds quicker than trying in a system). Unfortunately, there is no
conclusive test [that I know about] to prove a simm
On Wed, Jan 13, 1999 at 07:36:35PM -0600, Jim Bryant wrote:
This announcement is located on the Federal Trade Commission's
complaint form page http://www.ftc.gov/ftc/complaint.htm
I've been using the address for over half a year.. Nada for response
nor spam reduction.
So I just tightened up
I'm trying to adapt a working 2.2.6 diskless booting arrangement to 3.0,
for both clients and the server. The client machines load the kernel just
fine, then I see
NFS ROOT: 10.0.0.1:/export/boot/fs
which is correct, but the process stops there. It doesn't get any
further. I'm not sure if the
On Fri, 15 Jan 1999, Satoshi Asami wrote:
* From: as...@freebsd.org (Satoshi Asami)
*
* * From: Chris Timmons skyn...@opus.cts.cwu.edu
*
* * make: don't know how to make Makefiles. Stop
*
* I've seen similar things, but they went away when I reduced the load
* (other
On Fri, 15 Jan 1999, Boris Staeblow wrote:
Hello,
I'm using ctm-cvs for synchronizing my CVS-Tree.
But sometimes I get MD5 checksum errors when apllying the ctm's.
To resynchronize my ctm's with the CVS-Tree i have to use cvsup at
ctm.freebsd.org with the option strictrcs. Many files have
I've got a crash in ufs_lookup, and I'm trying to assess responsibility. I
use SoftUpdates on all drives and _MAY_ have some bad RAM. This crash was
during a make -j4 -DNOCLEAN world, and maybe it may be due to SoftUpdates not
completely having finished the dir, but I'm thinking it could've
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are pressed.
Solution? Putting the command kldunload splash_bmp before
Вы писали:
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are pressed.
Solution? Putting the command kldunload
On Sat, 16 Jan 1999, Eugeny Kuzakov wrote:
?? ??:
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are
It seems that if the splash screen image is not cleared (ie: press any
key) before xdm starts up then once logged in the user is unable to
switch to a vitual terminal (ie: ctrl-alt-f1 etc), and it just beeps
when those keys are pressed.
Solution? Putting the command kldunload splash_bmp
Hello!
After cvsuped my source tree, i try to compile
a new kernel, c following:
# config -r MY_KERNEL
# cd ../../compile/MY_KERNEL
# make depend
# make
cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes
I have found several people using IDE disks on newer Award BIOSes have trouble
getting the boot-time probes and installation routines to recognize the correct
disk geometry.
If anyone is running 3.0 (or 2.2.x) on a machine with Award BIOS using IDE
drives with LBA turned off in the kernel
On Fri, 15 Jan 1999, Brian Feldman wrote:
Solution? Putting the command kldunload splash_bmp before the line that
loads xdm seems to work. Is this a bug or just the way things are?
My current has not this bug. All works Ok.
xdm starts by init (ttys).
Do you have in rc.conf a screen
Just wondering if there is an updated timeline for 3.0.1 release ?
---Mike
**
Mike Tancsa, Network Admin* m...@sentex.net
Sentex Communications Corp, * http://www.sentex.net/mike
Cambridge, Ontario
Jaye Mathisen writes:
It would be kind of cool if when managing a remote system if /kernel
failed to boot, then on the next boot, the loader will fire up
/kernel.old, or a /kernel.somethingorother.
Sort of a kernel-clean flag. Then 300 miles away, I can try stuff, and
have at least some
I'm pretty sure this is not softupdates related. It could either be bad RAM
or a bad disk block, there is no way entryoffsetinblock could be 21209,
the block size is only 8192. And you need over 2000 files to fill the
directory to i_offset == 37593, assuming an average file name length of
10
I was thinking about the DIAGNOSTICS replacement macros and
had a random thought...
Suppose you're sitting in front of a ddb (or better yet gdb) prompt
because your kernel has just crashed due to who knows what reason.
What do you do to debug this? You start looking at variables,
memory, etc for
Archie Cobbs writes:
Jaye Mathisen writes:
It would be kind of cool if when managing a remote system if /kernel
failed to boot, then on the next boot, the loader will fire up
/kernel.old, or a /kernel.somethingorother.
Sort of a kernel-clean flag. Then 300 miles away, I can try stuff,
On Fri, Jan 15, 1999 at 09:12:07PM -0800, Archie Cobbs wrote:
I was thinking about the DIAGNOSTICS replacement macros and
had a random thought...
Suppose you're sitting in front of a ddb (or better yet gdb) prompt
because your kernel has just crashed due to who knows what reason.
What do
If libalias changes to libnat, I'd prefer to just change the ppp flag
to -nat, update the ppp version to 2.1 and update
You would change it, and you'd only document -nat, but you'd still
preserve -alias as a synonym for it (for at least a year or so)
because otherwise:
But this isn't
I cvsupped a couple of times, even blew away the entire
contrib/texinfo and gnu/usr.bin/texinfo in the middle but I still get
this
===
=== makeinfo
cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\/usr/share/local\
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo
* From: as...@freebsd.org (Satoshi Asami)
*
* * From: Chris Timmons skyn...@opus.cts.cwu.edu
*
* * make: don't know how to make Makefiles. Stop
*
* I've seen similar things, but they went away when I reduced the load
* (other compilations in my case) on the server. How busy is your
:Forgot to mention, this happens with a read-only NFS tree too. I was
:running builds on the client with a shared /usr/ports and WRKDIRPREFIX
:pointing to a local directory, and the build will topple over in the
:middle unable to find a Makefile on the server or something.
:
:That is the problem
silver% cat /usr/src/gnu/usr.bin/texinfo/makeinfo/Makefile
# $Id: Makefile,v 1.8 1999/01/14 20:00:46 markm Exp $
(snip)
CFLAGS+= -DLOCALEDIR=\/usr/share/local\
^
this should be 'locale'...
Seigo TANIMURA |M1, Nakagawa Lab, Dept of
* ===
* === makeinfo
* cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\/usr/share/local\
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo
Some weeks or days ago my GUS MAX (non-PnP) became a relic when Voxware
was axed from FreeBSD.
Eventhough, Voxware was reinstated, I diligently went about finding
a Luigi-Approved sound card.
After weeks of research I came to the conclusion that the
'Aopen AW 37 Pro' was the card of choice.
I
* From: br...@worldcontrol.com
* So I am now mostly back the square 1. I'm still using an old GUS MAX,
* which at the whim of FreeBSD-core may suddenly stop working.
Just one point -- the axing of voxware was *not* approved by
FreeBSD-core, and that's why it has been brought back.
Satoshi
I'll third that.
Eddie.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Hi,
On Fri, 15 Jan 1999, Bjoern Fischer wrote:
On Thu, Jan 14, 1999 at 08:03:46PM -0800, Chris Timmons wrote:
I have duplicated on two pairs of machines a case whereby you have two
-current machines as of ~20:00 UTC 1999/Jan/14 which cannot interoperate
via NFS without corruption.
On Fri, 15 Jan 1999, Nicolas Souchu wrote:
Hi there,
Currently, the ZIP+ probe is intrusive and sends char to the printer if
no ZIP+ is connected.
Here is a patch that corrects the problem for my printer, but I haven't
any ZIP+ :)
So, please check the ZIP+ is still detected.
With
Eventhough, Voxware was reinstated, I diligently went about finding
a Luigi-Approved sound card.
After weeks of research I came to the conclusion that the
'Aopen AW 37 Pro' was the card of choice.
...
And I have no idea what modern card will be reasonably well supported
under pcm0.
I
And I have no idea what modern card will be reasonably well supported
under pcm0.
Does anyone have any suggestions?
Followup: Dru Nelson was so kind to post me the details of his
research on this subject and told me the following:
I just went to Central Computer www.centralcomputer.com.
74 matches
Mail list logo
