:Hi !
:
:Since one or two weeks my system panics shortly before completely
:going down. Services like squid and inn take a little longer than
:usual to finish, I hear much disk activity.
:
:This happens usually if the system ran a day or so.
:
:What can I do to help ? Compile Kernel with debug inf
Sorry I'm jumping into this in the middle.
* Oliver Fromme wrote:
* >In releases/snapshots they're called "axp" and "x86", while in
* >ports they're called "alpha" and "i386".
I'm not sure where this "axp/x86" thing is coming from, but we are
using "alpha" and "i386" in ports (and /usr/src/sy
I wrote:
> I'm off now to play now with rootdev and boot_askname.
Well, if I let the standard boot process occur, then I stop the loader and
set rootdev=disk3s1a: I can get the kernel running in single user mode
but mount refuses to remount / as rw. It's curious that the message about
changing the
Hi !
Since one or two weeks my system panics shortly before completely
going down. Services like squid and inn take a little longer than
usual to finish, I hear much disk activity.
This happens usually if the system ran a day or so.
What can I do to help ? Compile Kernel with debug infos ?
BTW,
Oliver Fromme wrote:
>In releases/snapshots they're called "axp" and "x86", while in
>ports they're called "alpha" and "i386".
I agree that having two different names is confusing.
DEC (or Compaq) literature seems to use both Alpha and AXP - I'm not
sure that either is an especially better choic
Doug Rabson writes:
> > Might it be a good idea to choose a consistent naming scheme for the
> > modules? I'd think so because it would help blind loading at the boot
> > prompt. If you choose names it the following format:
> >
> > type_name
> > saver_warp
> > saver_daemon
> >
> > the modules of
On Wed, 20 Jan 1999, Daniel C. Sobral wrote:
> John Saunders wrote:
> > I have had no success in booting -current with the new loader. I can boot
> > the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> > However if I enter either 1:wd(1,a)/boot/loader (the default) or
> > 1:wd(2
Sorry for replying to my own mail...
In list.freebsd-current I wrote:
> I'm wondering whether it might be a good idea to rename the
> directories "current" and "releng22" on {current,releng22}
> .freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as
> they are named on ftp.freebsd.org.
I
Hi,
Please excuse me if this is the wrong place to ask this kind
of things...
I'm wondering whether it might be a good idea to rename the
directories "current" and "releng22" on {current,releng22}
.freebsd.org to "FreeBSD-current" and "FreeBSD-stable", as
they are named on ftp.freebsd.org.
That
Aaron D. Gifford wrote:
> I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
> unsuccessfully. It used to die in perl, then that was fixed, but for
> the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386.
> Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully
FYI. That had no affect for me at all. I was able to pass the kernel the
rootdev by:
boot -rootdev kernel
but then I had a problem when it came time to mount root as read/write. It
mounted read-only successfully and then bailed because it couldn't remount
as read/write. num_ide_disks=
:Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world
:just fine. Try starting with an empty /usr/obj.
:
:You can pretty much glean from reading -current whether or not most people
:are building it or if it is broken. -questions is more for general
:freebsd issues.
:
:-Ch
Hmmm, I zapped my /usr/obj clean around 1100PST 19/Jan/1999 and made world
just fine. Try starting with an empty /usr/obj.
You can pretty much glean from reading -current whether or not most people
are building it or if it is broken. -questions is more for general
freebsd issues.
-Chris
On
John Saunders wrote:
>
> I have had no success in booting -current with the new loader. I can boot
> the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
> However if I enter either 1:wd(1,a)/boot/loader (the default) or
> 1:wd(2,a)/boot/loader I get the loader started but the kern
Terry Lambert wrote:
>Put another way:
>
> default:A seat belt for you, but not the passenger
> sync: A seat belt for you and your passenger
Terry forgot to mention that you also have to come to a dead stop every
10 feet and check that the wheel bolts are all tight :-
> Hey gang:
>
> Somebody mentioned the other day that UFS async isn't entirely async, and
> that directories are (always) sync. Is that true?
No.
The default is sync metadata and async user data, with the assumption
that the user will have taken a CS 203 class and know about two stage
commit fo
> The only solution I have is bypass the loader all-together, but I really
> wanted a splash screen :( Or possibly use config to make my second disk
> appear as wd1 instead of wd2 (not tried yet because I consider it an ugly
> hack).
Try "set num_ide_disks=-1" in the loader.
--
\\ Sometimes yo
Hi,
I have had no success in booting -current with the new loader. I can boot
the kernel directly by entering 1:wd(2,a)/kernel at the boot prompt.
However if I enter either 1:wd(1,a)/boot/loader (the default) or
1:wd(2,a)/boot/loader I get the loader started but the kernel won't boot.
The the se
I'm still trying to upgrade from 3.0-RELEASE to 3.0-CURRENT
unsuccessfully. It used to die in perl, then that was fixed, but for
the past 2 days, it has been dying in /usr/src/sys/boot/i386/libi386.
Is this a known problem? Yes, I'm a CURRENT newbie, but hopefully only
until the split to 3.1 whe
Just in case anyone's been losing sleep over this, it was pilot error!
bde@ pointed out the problem, and cron confirmed it :-/
> Hi,
>
> Something weird is happening in -current. I installed world, a
> kernel and bootblocks on Jan 6 - I can't say for sure that it wasn't
> happening before this
Actually, about half a dozen. Lots More if you include LS-120 drives in the
list... But, the main point I'm driving at is to still be able to build
bootable CDs without too much playing...
-Brian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the
Mike Smith wrote:
> > Mike Smith wrote:
> >
> > > > This sounds like booting/installing from CD-ROM is currently
> > > > impossible as well ???
> > >
> > > That's correct. We're looking at having to move to a harddisk
> > > emulation mode to get this back on track.
> >
> > Would a 2.88M virtual
> Mike Smith wrote:
>
> > > This sounds like booting/installing from CD-ROM is currently
> > > impossible as well ???
> >
> > That's correct. We're looking at having to move to a harddisk
> > emulation mode to get this back on track.
>
> Would a 2.88M virtual floppy for the CD-ROM boot image be
On Tue, 19 Jan 1999, Jeroen C. van Gelderen wrote:
> Hi,
>
> Might it be a good idea to choose a consistent naming scheme for the
> modules? I'd think so because it would help blind loading at the boot
> prompt. If you choose names it the following format:
>
> type_name
> saver_warp
> saver_daem
On Tue, 19 Jan 1999, Peter Wemm wrote:
> Doug Rabson wrote:
> > On Tue, 19 Jan 1999, Julian Elischer wrote:
> >
> > >
> > > If I load a module A
> > > then try load a module B that requires a function in A
> > > it fails because it cannot find the symbol..
> > > is this a known problem?
> > >
>
Hi,
dirp = opendir("/cdrom");
direntp = readdir(dirp);
results in
direntp->d_type == DT_UNKNOWN
for every kind of directoryentry, even if it is a directory or file.
The man page didn't say it didn't work with CDs, so I assume it should
work ( ;) ).
current from "Sun Jan 17",
Bye,
Alexander.
Hi,
Installing the latest 3.0-SNAP, I just discovered that I cannot run
the netscape binaries anymore. It stops claiming not to find
/usr/libexec/ld.so, but obviously it would not find a.out libraries
neither. :)
Maybe we need a compat22 distribution before 3.1 release.
On Tue, 12 Jan 1999, Bruce Evans wrote:
> >Does softupdates give any gain over async?
> >I have /usr/src and /usr/obj both mounted async, noatime, and it does
> >seem to be rather nicely fast over default mountops.
>
> Async isn't fully async in FreeBSD (some directory operations are still
> syn
Satoshi Asami writes:
However, if I try to mount it from B read-only while A is mounting
it read-write, it succeeds. This looks dangerous, as A writing data
onto the disk could cause B's cache to go stale without B knowing
it.
Just about as dangerous al letting A mount it read-onl
>> I recently installed 3.0-RELEASE on existing 2.1.0-RELEASE.
>> After that one program does not run any more.
>
>You probably did not update the contents of /etc, as one must by hand.
>This would not create the a.out search paths properly and leads to this
>exact error.
By the way, file /etc/rc.
I think the 2.88MB suggestion was an alternative to going to a 'Hard Drive'
type solution for bootable CDROMs (from a jkh post earlier). Since most
bioses support 2.88MB floppies (regardless of if the hardware exists on the
person's machine), wouldn't it be possible to have the 'boot.flp' for a
> Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation
> I've read states that this should be supportable on machines that understand
> 2.88MB floppies Or, have we outgrown that already?
How many systems have you seen with 2.88MB floppy drives?
--
\\ Sometimes you'r
On Tue, Jan 19, 1999 at 02:06:13PM +0200, Jeremy Lea wrote:
> On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote:
> > Gimp (CVS) compiled with
> > CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486
> > -pipe -lpthread"
>
> Hmm, if you're using the libpth
On Tue, 19 Jan 1999, Chan Yiu Wah wrote:
> Hello,
>
> I just finished the compilation of the whole system with ctm source upto
> src-cur.3712 and found the keyboard freezed after system boot up. I would
> like to know the usage of atkbdc device which I think is the cause of the
> keyboard freeze
On Mon, Jan 18, 1999 at 06:27:18PM -0800, br...@worldcontrol.com wrote:
> I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current
> (1/17/1998) with
>
> CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
> COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK
>
> and linuxthreads po
Wouldn't it be possible to use a 2.88MB boot image? Most of the documentation
I've read states that this should be supportable on machines that understand
2.88MB floppies Or, have we outgrown that already?
-Brian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe free
On Tue, Jan 19, 1999 at 01:01:34PM +0200, Sheldon Hearn wrote:
[...]
> > But there's still something wrong: When shutting down the server
> > it still sometimes panics in vinvalbuf() complaining 'bout dirty
> > pages.
>
> I'm not sure this has anything to do with NFS. I got this after last
> night
Mike Smith wrote:
> > This sounds like booting/installing from CD-ROM is currently
> > impossible as well ???
>
> That's correct. We're looking at having to move to a harddisk
> emulation mode to get this back on track.
Would a 2.88M virtual floppy for the CD-ROM boot image be a quick fix, or is
> >but that doesn't happen any-
> >more. Instead, it uses the current one (i.e. if I'm on ttyv3
> >and start X, it uses ttyv3). Is this intentional, or is it a
> >bug?
Oops... I'm very sorry for the confusion... it was all my
fault. There were as many gettys configured in in /etc/ttys
as
In , Joss
Roots wrote:
> Hi there,
> Some ports are complaining during early configuration
> phase using configure that c++ compiler is unable to
> produce excutables, and the options are -O -pipe
> is there anything I am missing here, as this is the
> first time I hear this complain, please help
This patch seems to fix my NFS problems. I started a make release yesterday
and it is still running (It's a slow machine). No problems so far.
The chroot dir is NFSv2/UDP mounted.
Thanks,
Daniel
Luoqi Chen schrieb:
>
> The check is correct and should be there, the B_CACHE bit was cleared becaus
Sorry for self reply.
Patch isn't good enougth:-) becouse linker_file_unload()
deallocates lf structure's memory... so lf->userrefs-- may cause
page fault or whatever else. (I wonder how that didn't happened)
Look at this one:
*** kern_linker.c.orig Mon Jan 18 17:22:39 1999
--- kern_linker.c
Hi,
On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote:
> Gimp (CVS) compiled with
> CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486
> -pipe -lpthread"
Hmm, if you're using the libpthread from lt.tar.com, and you installed it
according to the instruct
Hi,
Might it be a good idea to choose a consistent naming scheme for the
modules? I'd think so because it would help blind loading at the boot
prompt. If you choose names it the following format:
type_name
saver_warp
saver_daemon
the modules of one type will sort together in a directory listing.
Imagine:
I'm trying to unload KLD module, it is busy:
# kldunload -n ntfs
kldunload: can't unload file: Device busy
After this point i'll never get module unloaded becouse
kldunload() in sys/kern/kern_linker.c has already decremeted
lf->userrefs. I'll get only this messages:
# kldunload -n ntf
I have committed another syscons update.
Because one new file has been added to the source tree, and one file
has changed location, I have to ask you to run config() before you
compile the kernel next time, and "make clean depend all" in your
kernel compile directory. No need to update the kernel
Berend de Boer wrote:
> >> - update to the new bootblocks (done)
> >> - move to ELF kernel
>
> > Installing the Jan 12th snapshopt gives you all of this already, and
> > no a.out cruft anywhere in sight.
>
> Warning: make world doesn't upgrade the bootblocks as I just detected. I
> tried disklabe
Doug Rabson wrote:
> On Tue, 19 Jan 1999, Julian Elischer wrote:
>
> >
> > If I load a module A
> > then try load a module B that requires a function in A
> > it fails because it cannot find the symbol..
> > is this a known problem?
> >
> > (A real bummer if so)
>
> The module B needs to have A
On Tue, 19 Jan 1999 11:38:50 +0100, Bjoern Fischer wrote:
> But there's still something wrong: When shutting down the server
> it still sometimes panics in vinvalbuf() complaining 'bout dirty
> pages.
I'm not sure this has anything to do with NFS. I got this after last
night's fresh world and k
>> - update to the new bootblocks (done)
>> - move to ELF kernel
> Installing the Jan 12th snapshopt gives you all of this already, and
> no a.out cruft anywhere in sight.
Warning: make world doesn't upgrade the bootblocks as I just detected. I
tried disklabel -B before but it complained that the
On Mon, Jan 18, 1999 at 10:05:50AM -0500, Luoqi Chen wrote:
> The check is correct and should be there, the B_CACHE bit was cleared because
> I made a mistake when setting the valid bit in the vm page.
[...]
> Note the calculation of ev, the original code was a round-up and I changed it
> to round-
Brian Feldman suggested:
> Try compiling with debugging info, get a coredump, and debug with the binary
> that has the full debugging symbols.
Gimp (CVS) compiled with
CFLAGS="-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe
-lpthread"
Brian Litzinger wrote:
>>Everything
On Tue, 19 Jan 1999, Julian Elischer wrote:
>
> If I load a module A
> then try load a module B that requires a function in A
> it fails because it cannot find the symbol..
> is this a known problem?
>
> (A real bummer if so)
The module B needs to have A as a dependancy. Use KMODDEPS to do thi
"Kenneth D. Merry" wrote:
>
> > At the moment, looking in LINT, it looks like aic still isn't
> > supported. Is that true? Does anyone know whether it will be?
>
> It's true that it isn't supported yet. We are planning on supporting it.
> Brian Beattie is the one working on it, you should probab
I tried `make aout-to-elf' last sunday (17th Jan). Make died
in src/gnu/usr.bin/texinfo/doc
The Makefile started the elf binary `../makeinfo/makeinfo'
But the elf linker was not yet ready ...
--
Wolfram Schneider http://freebsd.org/~w/
To Unsubscribe: send mail to majord...@freebsd.org
with "
hi,
I tried to upgrade my system (FreeBSD-3.0 december)
with 3.0.0-19990112.
I'm using 2 scsi drivers for FreeBSD
SCSIID 1 for my work system
SCSIID 2 for my test system
I'm always installing a new version on my test drive (SCSIID 2)
with the (SCSIID 1) drive disconnected. the I reconnect my
Mike Smith writes :
>
> Installing the Jan 12th snapshopt gives you all of this already, and no
> a.out cruft anywhere in sight.
After a bit of thought - I think I will take this advice.
Blowing the achine I have installed away is quicker than
trying to juggle some of the recent changes!
geoff.
Hi there,
Some ports are complaining during early configuration
phase using configure that c++ compiler is unable to
produce excutables, and the options are -O -pipe
is there anything I am missing here, as this is the
first time I hear this complain, please help.
thanks
- MAY THE FORCE BE WITH YOU
> Hi,
>
> I'm in the process of setting up a new FreeBSD-current
> box, starting with 3.0 Release, and moving to current.
> One question I have, is whether to go to the ELF kernel
> before I recompile the world with current source.
>
>
> My plan is as follows:
> - Load 3.0-RELEASE (done)
> -
Hi,
I'm in the process of setting up a new FreeBSD-current
box, starting with 3.0 Release, and moving to current.
One question I have, is whether to go to the ELF kernel
before I recompile the world with current source.
My plan is as follows:
- Load 3.0-RELEASE (done)
- archive and delete all
> I'd love to see the aic supported, mostly for my notebook. However,
> no one seems to have a confluance of time, information and talent to
> write the driver, or even port the other one in all its gory.
If CAMed aic driver is available, SlimSCSI support is very
easy. First of all, we need CAMed
If I load a module A
then try load a module B that requires a function in A
it fails because it cannot find the symbol..
is this a known problem?
(A real bummer if so)
julian
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Hello,
I just finished the compilation of the whole system with ctm source upto
src-cur.3712 and found the keyboard freezed after system boot up. I would
like to know the usage of atkbdc device which I think is the cause of the
keyboard freeze. Any idea ?
cheers
Clarence
To Unsubscribe: send
I've been taking the last few days off, but I intend to get to
this this week and fix whatever's broken. Don't panic. :)
> On Mon, Jan 18, 1999 at 09:52:26PM -0800, Mike Smith wrote:
> > > Hi ! Bad news, make release still produces non bootable floppies.
> > > I cvsupped yesterday evening at 8pm
64 matches
Mail list logo
