is firewall support built into the -current kernel or does it need to be
compiled in?
--karl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
hi,
I used gcc3.1 from ports to compile jdk1.3.1-p7 hotspot, I got problem
in compiing /usr/src/lib/libc_r/uthread/pthread_private.h :
--
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:213
#1 0xc02297ba in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:345
#2 0xc022996d in panic () at /usr/src/sys/kern/kern_shutdown.c:493
#3 0xc025db3b in bwrite (bp=0xcd233954) at /usr/src/sys/kern/vfs_bio.c:797
#4 0xc025ee8d in vfs_
On Sun, 28 Jul 2002, Gavin Atkinson wrote:
> hi,
>
> FreeBSD epsilon.ury.york.ac.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Jul 26
>13:32:52 BST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EPSILON i386
>
> Had this panic twice with current -current on an uniprocessor machine and
> kerne
I've located the source of my printing problems: It's the kernel.
I was able to boot into my orig 5.0-DP1 kernel, I redid the printer
config using apsfilter and I can print w/o problems to my hearts
content.
If I boot into my new kernel (source installed last monday nite) and
attempt to print i
Rob wrote:
> There was either a glitch at Verio's mta or possibly on Linux-Netscape
> in -current. I sent one message and it never went through. Sorry for
> the spam. It was an error message- get it?
In the future, you might want to consider using the "unsubscribe"
documented in both the messa
There was either a glitch at Verio's mta or possibly on Linux-Netscape in -current. I
sent one message and it never went through. Sorry for the spam. It was an error
message- get it?
Rob.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the me
hi,
FreeBSD epsilon.ury.york.ac.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Jul 26
13:32:52 BST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EPSILON i386
Had this panic twice with current -current on an uniprocessor machine and
kernel. Dumps still don't work... Both occurances, i had an ssh
On 27-Jul-2002 Terry Lambert wrote:
> Peter Wemm wrote:
>> > So, given that the install from a CDROM boots from a floppy
>> > image that's faked up by the CDROM drive BIOS, and the image
>> > doesn't include the full boot loader, how exactly is it that
>> > the partial boot loader code acts like
Peter Wemm wrote:
> > So, given that the install from a CDROM boots from a floppy
> > image that's faked up by the CDROM drive BIOS, and the image
> > doesn't include the full boot loader, how exactly is it that
> > the partial boot loader code acts like the full bootloader
> > code for accessing
On Sat, Jul 27, 2002 at 05:15:08PM -0400, John Baldwin wrote:
>
> Knowing the actual panic message would help. :)
My bad. I was loading the wrong version of a kernel module (ipfw).
-Arun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of th
On 27-Jul-2002 Arun Sharma wrote:
> This is with the GENERIC kernel. Known problem ? How can I get a
> -current kernel that boots to multiuser so that I can tinker around with
> it ? Are there any magic config files that suppress these panics ?
>
> db> trace
> _mtx_lock_flags(7069307e,0,c03ff2e0
On 25-Jul-2002 Terry Lambert wrote:
> "M. Warner Losh" wrote:
>> : Think "CDROM install".
>>
>> Dude, what crack are you smoking? How many times to we have to tell
>> you. We have a boot loader that knows how to read the kernel from the
>> cdrom or scsi or whatever. IT is a tiny increment to
This is with the GENERIC kernel. Known problem ? How can I get a
-current kernel that boots to multiuser so that I can tinker around with
it ? Are there any magic config files that suppress these panics ?
db> trace
_mtx_lock_flags(7069307e,0,c03ff2e0,530) at _mtx_lock_flags+0x3e
securelevel_ge(bf
Terry Lambert wrote:
> "M. Warner Losh" wrote:
> > I've noticed that some of the older cam drivers are about all that is
> > in the way of making CAM truly loadable. By that I mean having a
> > kernel with all supported devices that aren't loadable forces CAM to
> > be in the kernel because some
Here's the salient section of my printcap made up by apsfilter; what
should I edit here??
# APS1_BEGIN:printer1
# - don't delete start label for apsfilter printer1
# - no other printer defines between BEGIN and END LABEL
lp|ljet2p;r=600x600;q=high;c=gray;p=letter;m=auto:\
:lp=/dev/lpt0:\
Terry Lambert wrote:
> "M. Warner Losh" wrote:
> > : Think "CDROM install".
> >
> > Dude, what crack are you smoking? How many times to we have to tell
> > you. We have a boot loader that knows how to read the kernel from the
> > cdrom or scsi or whatever. IT is a tiny increment to also load
>
On Sat, 2002-07-27 at 09:25, karl agee wrote to recap:
>
> >
> > system: FreeBSD enterprise.workgroup 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Jul
>23 16:07:44 PDT 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NEWKERNEL i386
> >
> > trying to print to a post script laser printer which works
On 27-Jul-2002 Steven G. Kargl wrote:
> Can someone close PR bin/37795? I am the originator
> of the PR, and it no longer applies to current version
> xinstall.
Closed. Note that several people (including myself) actually
want -d -C to not be an error. Still, the PR should be
closed.
--
Jo
Can someone close PR bin/37795? I am the originator
of the PR, and it no longer applies to current version
xinstall.
--
Steve
http://troutmask.apl.washington.edu/~kargl/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> That's not what I was asking for. He mentionned he had a kernel from
> the 25th that was working and I wanted the version of subr_mbuf.c that
> he had used to build _that_ kernel.
Oh, sorry. IIRC then (for me) everything worked just fine with r1.22.
Marc
To Unsubscribe: send mail to [EM
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, Jul 27, 2002 at 07:27:11PM +0200, Marc Recht wrote:
> > > I started getting unexpected lockups during mozilla sessions after
> > > remaking world & kernel on the evening of July 25. The screen
> > > would freeze completely, followed a few seconds later by a
> > > spontaneous reboot.
> >
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
QUIT
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > I started getting unexpected lockups during mozilla sessions after
> > remaking world & kernel on the evening of July 25. The screen
> > would freeze completely, followed a few seconds later by a
> > spontaneous reboot.
> >
> > After this happened twice I deleted the new kernel and went back
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> --
> >>> Kernel build for LINT started on Fri Jul 26 23:27:37 PDT 2002
> --
> ===> LINT
> /local0/scratch/des/src/sys/i386/conf/
On Sat, Jul 27, 2002 at 02:15:15PM +0200, Marc Recht wrote:
> With -current of today the system resets (without syncing discs) when mozilla
> is started. This happens everytime when mozilla is started. Other X apps
> like Sylpheed or mplayer seem to work correctly. zero copy sockets are not
> tur
Bosko Milekic wrote:
> On Fri, Jul 26, 2002 at 08:18:27PM -0700, walt wrote:
>
.
.
.
>>Seems to implicate kernel code committed on July 25, sometime after
>>about 1430 GMT.
> For the kernel that works, what version of src/sys/kern/subr_mbuf.c did
> you build it from?...
My source tree has been
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> --
> >>> Kernel build for GENERIC started on Sat Jul 27 11:45:42 GMT 2002
> --
> ===> GENERIC
> /usr/home/des/tinderbox/sparc64/
On Fri, Jul 26, 2002 at 08:18:27PM -0700, walt wrote:
> A small observation which I hope will be useful:
>
> I started getting unexpected lockups during mozilla sessions after
> remaking world & kernel on the evening of July 25. The screen
> would freeze completely, followed a few seconds later
Quoting karl agee <[EMAIL PROTECTED]>:
|
| Excuse my newbie ignorance, but, how to do print a file bypassing lpr
| and apsfilter
How about
# cat file_to_print.ps > /dev/lpt0
or
# cp file_to_pring.ps /dev/lpt0
ed
-
http://wor
With -current of today the system resets (without syncing discs) when mozilla
is started. This happens everytime when mozilla is started. Other X apps
like Sylpheed or mplayer seem to work correctly. zero copy sockets are not
turned on and it didn't happen with -current as of a week ago.
To Unsu
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On Sat, 2002-07-27 at 00:21, David Wolfskill wrote:
> >From: karl agee <[EMAIL PROTECTED]>
> >Date: 26 Jul 2002 20:44:24 -0700
>
> >> If this is a networked printer, then you'll probably want to
> >> use lpr but skip apsfilter.
>
> >Excuse my newbie ignorance, but, how to do print a file bypassi
karl agee wrote:
> Ok, I tried rebooting to my old orig kernel (5.0-DP1) to see if it
> helped my printing issue. well, this happened when I rebooted:
>
> Panic: Malloc type lacks magic
>
> Debugger ("panic")
>
> stopped at Debugger+0x40 xorl%eax, %eax
>
> ?
You need to wave
63 matches
Mail list logo
