Doesn't ccache work? install the package and put WITh_CCACHE_BUILD=yes
in /etc/make.conf. With a lot of ccache hits i cann build kernel and
world with 4 cores onn a vm in about ab hour.
On 10/27/2024 5:00 PM, Maku Bex wrote:
Hello,
I’m trying to figure out a way to decrease build time of -C
Over the last week or so, stable/13, stable/14 and current have
improved. Finally, I can make it through a build and install with a
password on the root account and a user in the wheel group without
having it fail.
Brian
On 9/9/2023 9:02 AM, John Baldwin wrote:
On 9/2/23 7:11 AM, Dimitry
master/passwd as problems.
If this is is expected behavior for current then no big deal. I just
wasn't sure.
Brian
On 8/30/2023 7:35 PM, Graham Perrin wrote:
On 31/08/2023 03:31, brian whalen wrote:
Understood. I guess I was expecting the update process of etcupdate
-p && make in
On 8/30/2023 7:21 PM, Graham Perrin wrote:
On 31/08/2023 03:00, brian whalen wrote:
… I ran etcupdate resolve accepting the remote option and saw 2 issues.
The root user's password was deleted.
The non root user no longer existed.
Logically, remote does not include things such as your root user's
password.
I have seen this twice. Once when going from 13.2 to current 14.0 alpha1
and then to 15, and a 2nd time when going from 13.2 to 15.
I have a user that is a member of the wheel group.
After I upgraded and ran the post reboot commands in single user mode I
was alerted to merge conflicts. I ran e
root@f15:~ # pkg update
pkg: Warning: Major OS version upgrade detected. Running "pkg bootstrap
-f" recommended
Updating FreeBSD repository catalogue...
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz:
Not Found
repository FreeBSD has no meta file, using default setting
x27;t have a snapshot build).
I also rebuilt 'pkg' to get over the same problem.
Hopefully package building will catch up with this fairly quickly. My
problem was on arm64 so probably a lower priority for getting ports back
on track than amd64.
Cheers,
Brian
On 17/10/18 7:15 pm,
On 28/8/18 11:45 pm, Emmanuel Vadot wrote:
> On Tue, 28 Aug 2018 22:10:18 +1000
> Brian Scott wrote:
>
>> Hi,
>>
>> Just a couple of small observations with 12.0-ALPHA3 from testing on a
>> Raspberry-Pi 3:
>>
>> * The boot loader (I presume the new
blems
yet. I'll keep looking though.
Keep up the good work,
Brian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
.
Anyone headed to the conference that might be able to lend me a hand?
Thanks,
Brian
Brian Kidney, M.Eng., P.Eng.
PGP Fingerprint: B8C9 D174 BABC 7FD8 67D0 DF84 FDEE B338 F248 A893
On 3 Jun 2018, at 2:43, Albert wrote:
Michael,
Good to know you still have plans to work on that eventually. It'
end to migrate from linux on both
> his home server as well as his laptop. He is very happy with the change.
>
> Cheers
> Andreas
>
>
>
> > Cheers,
> > -matt
> > ___
> > freebsd-current@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscr...@freebsd.org"
> >
> ___
> freebsd-hack...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
>
--
Best Wishes,
Brian Kim
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
solves the problem?
Thanks.
On Thu, 02 Sep 2010 11:48:44 +0300 Andriy Gapon wrote:
>
> Brian,
>
> after I upgrade from beginning-of-June kernel to end-of-August one (r211758) I
> get a panic in get_next_dirent which happens during parallel access to FS like
> during buildworl
utput.
Go ahead and load up kernel.debug and the core dump in gdb -k, and show us
the backtrace. Also, do you have any idea about more specific circumstances
that will cause this problem? Thanks!
--
Brian Fundakowski Feldman \'[ FreeBSD ]
Has anyone else tried out the most basic IPv6 test: ndp -I and
then ping6 fe80:: extension>? I was
greeted by recursion on a non-recursive lock. After some sleuthing,
I tried to determine what conditions could be tested for that would
indicate "this must not call the nd6_is_addr_neighbor() call be
Bernd Walter <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
> > Doug White <[EMAIL PROTECTED]> wrote:
> > > The OHCI driver is largely synced with NetBSD so you might see if they
> > > have the same bug.
&
Bernd Walter <[EMAIL PROTECTED]> wrote:
> On Fri, Nov 21, 2003 at 12:35:50PM -0500, Brian F. Feldman wrote:
> > Doug White <[EMAIL PROTECTED]> wrote:
> > > The OHCI driver is largely synced with NetBSD so you might see if they
> > > have the same bug.
&
oblem here -- the fact that
it's an ohci controller, an ohci+ehci controller, or that it's some specific
controller issue...
> On Thu, 20 Nov 2003, Brian F. Feldman wrote:
>
> > Thanks for the patches to try! They unfortunately didn't fix the crash I
> > have, but I fou
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote:
> Thanks for the patches to try! They unfortunately didn't fix the crash I
> have, but I found out why it's occurring.
>
> See ohci.c:1389:
> if (std->td.td_cbp != 0)
>
tell me if you see any hints as
to why the transfers are getting stalled. I should have looked at the
debugging messages long ago, I guess. Thanks!
http://green.homeunix.org/~green/ohci-debugging.txt.gz
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> On Sun, Nov 17, 2002 at 01:18:00PM -0500, Brian F. Feldman wrote:
> >
> > > ohci_alloc_std_chain+0xf5 (calling a DMAADDR() function, I believe)
> > > ohci_device_bulk_start+0x0d
> > > ohci_device_b
, SI_ORDER_ANY);
static void
tunstart(struct ifnet *ifp)
=======
A similar change would likely work for if_ppp.c.
Assuming I am right about this (hah :) a pr would seem to be in order.
Brian
[1] Per this commit:
mdodd 2003/04/14 23
rnet
> card that doesn't use dc) and see if the problem goes away.
>
> Am I correct in believing this is a dc issue? If so, hope the above
> helps in diagnosing the problem. Otherwise... any other pointers?
instruction pointer = 0x8:0xc049d0db
That will tell you exactly
e() calls so that they are always able to
> proceed and clean up buffer space.
This will fix at least some of any deadlocks you may be seeing with md(4) or
similar devices, totally unrelated to hardware.
--
Brian Fundakowski Feldman \'[ F
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote:
> Kirk McKusick <[EMAIL PROTECTED]> wrote:
> > I have been able to reproduce your hang on my system and your suggested
> > fix does prevent it. I am going to run some more buffer starvation-type
> > tests on
ested fix.
Thanks, Kirk; seems everyone who's been able to reproduce it can't do so
anymore when the synchers are disallowed from waiting on runningbufspace
(a couple extra people testing it that haven't spoken up on the list).
--
Brian Fundakowski Feldman
gt; Thanks,
> -Jason
>
Try reading /usr/src/UPDATING (its near the top, but read the whole
thing anyway - it'll be good for you). Also, ipfw and ipfilter are not
the same thing.
Brian
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/m
waitrunningbufspace();
---
> if (curthread->td_proc != bufdaemonproc &&
> curthread->td_proc != updateproc)
> waitrunningbufspace();
2038,2039d2041
<
< static struct proc *bufdaemonproc;
--
Brian Fundakows
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 15 Oct 2003, Terry Lambert wrote:
> Dimitry Andric wrote:
> > On 2003-10-15 at 03:30:54 Brian J. Creasy wrote:
> > > unfortunately, we are not getting any errors. the system just restarts
> > > after i
> which phk checked in 2003/10/12 10:55:45.
__FBSDID("$FreeBSD: src/sys/i386/i386/pmap.c,v 1.447 2003/10/13 03:28:31
alc Exp $");
unfortunately, we are not getting any errors. the system just restarts
after it starts booting the kernel.
- ---
Brian J. Creasy
-BEGIN PGP SIGNATU
x27;t remember when I did mine since I let a friend
> borrow it for a couple of weeks. I hope that someone with more
> knowledge can point where to start looking. It isn't ACPI since it
> still doesn't work when unloaded from the boot loader.
>
> > ---
> > B
thing with the acpi or longrun stuff.
i'm not too proficient with freebsd kernel hacking, so hopefully someone
else will be able to tackle this.
- ---
Brian J. Creasy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE/jIaZWMKWjLymTUYRArVrAJ454d0I3V3GvA+9FkNqpz6EL3y1KQCgt
done
Uptime: 2m21s
ata1-slave: WARNING - FLUSHCACHE recovered from missing interrupt
--
Brian Buchanan, CISSP [EMAIL PROTECTED]
--
FreeBSD - The Power to Serve
Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): NOT READY asc:3a,0
(da0:umass-sim0:0:0:0): Medium not present
(da0:umass-sim0:0:0:0): Unretryable error
Opened disk da0 -&
we _can_
keep on topic somewhere. :)
--
Brian 'you Bastard' Reichert<[EMAIL PROTECTED]>
37 Crystal Ave. #303Daytime number: (603) 434-6842
Derry NH 03038-1713 USA BSD admin/developer at large
___
ee86 4.3.0 is
> just a little outdated.
Is 'DRI-HEAD' a CVS tag?
> --
> Scott M. Likens <[EMAIL PROTECTED]>
--
Brian 'you Bastard' Reichert<[EMAIL PROTECTED]>
37 Crystal Ave. #303Daytime number: (603) 434-684
while, then read a
couple of messages on one of the freebsd mailing lists about
the necessity of rebuilding everything due to a change in proc.h.
After the cvsup, rebuild process, the nvidia driver seems to
work, except for the problems mentioned above.
Brian
set hw.eisa_slots=12 works, it recognizes the controller and drives, then panics. I
think I'll settle for 4.7 on here fow now.
thanks for your help,
Brian
On Fri, Mar 21, 2003 at 06:00:29PM -0500, Matthew Emmerton wrote:
>
> - Original Message -
> From: "Bri
pt correctly lists the floppy and two
drives, including the partition information.
Any suggestions would be greatly appreciated.
thanks,
Brian
--
Brian Kirk
primuul.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
wrapped to fit in 80 cols).
ftp://space.mit.edu/pub/davis/jed/v0.99/jed-B0.99-15.tar.gz";>
I know the proxy is working, as my 4.x boxes still go through it happily.
Anyone have any ideas if something has broken, or whether its pilot error?
-Brian
To Unsubscribe: send ma
= 0x1f, tf_eflags = 0x282, tf_esp = 0xbfbff2ec,
tf_ss = 0x2f}) at ../../../i386/i386/trap.c:960
#15 0xc02cf7dd in Xint0x80_syscall () at {standard input}:139
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''''
s are now working. I have only tried it by setting
> hw.snd.maxautovchans. It does produce a lot of "could sleep with"
> messages though:
Yeah. I found and fixed that a few days ago. It's been around for at least
a month, but for some reason I'm getting a lot of ENODEV error
I was just going through the list of projects at the FreeBSD website. I
didn't see one for the installer. I was curious if anyone was working on
an upgrade/replacement for sysinstall... I know of Jordan's paper on the
subject, et al, but curious if anyone was doing anything more than maintaining
o
ect
> cases).
I haven't tested, since I haven't provoked that specific panic on my
machines, but that does appear that it would indeed fix both issues. Kris,
can you confirm that it makes the machines work properly?
--
Brian Fundakowski Feldman
s with the same vmspace can exit at the same time, and the
vm_refcnt could be 2 the entire time, so neither would perform the current
if (--vm->vm_refcnt == 0) { block.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''&#x
Jake Burkholder <[EMAIL PROTECTED]> wrote:
> Apparently, On Sat, Dec 14, 2002 at 07:37:31PM -0500,
> Brian F. Feldman said words to the effect of;
>
> > John Baldwin <[EMAIL PROTECTED]> wrote:
> > >
> > > On 12-Dec-2002 Kris Kennaway wrote:
&g
x27;s clearly not correct for a process in exit1()
to be swapped out, and the vmspace _needs_ to be decremented in the correct
place or resources are NEVER freed when the race is lost.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> If you're an ohci user can you please test this patch out for inclusion
> in 5.0. I need to know that it doesn't break anything - the reports are
> that it fixes broken ohci :).
For what it's worth, it doesn't fix the umass(4) crashing is
else {
pcount = 0;
}
if (pcount || !only_nonzero) {
if (print_name) printf("%s: ",av[optind]);
printf("%d",pcount);
if (print_sizepages) printf("/%d&q
I just installed RC#0. It appears to be as good as some of the DP versions. I
haven't done much with it yet, but a couple of minor sysinstall issues that
are ugly.
1.) It appears, during install that devfs gets mounted on /dev twice. It
doesn't appear to impact anything, its just an oddity.
2.) D
st them out.
I would like someone to commit this, and let me know when its in. Thanks.
-Brian
PS - I'll be looking at doing a patch for -STABLE, as well, but the USB
code looks very, very different
diff -r sys/dev/usb/umass.c sys/dev/usb.new/umass.c
325a326,330
>
roblem
as the SysV semaphores, where they block the entire process,
allowing the same deadlock situation to occur. Has this flock()
behavior changed in CURRENT?
It seems like this behavior is much more likely to change than
the SysV code.
Thanks!
Brian Smith
To Unsubscribe: send mail to
to your
/boot/loader.conf file:
exec="unset ACPI_LOAD"
Good luck!
-Brian
--
Brian Dean
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
a deadlock situation).
Is this the recommended method of preventing these problems?
(the SysV semaphore is protecting shared memory accessed by
multiple processes).
Thanks for the info... it explains alot!
Brian Smith
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
T?
Thanks!
Brian Smith
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Brian Fundakowski Feldman <[EMAIL PROTECTED]> wrote:
> I can't get more info because crash dumps don't work when this happens, but
> for what it's worth, here's a traceback which shows what happens when I
> attempt to use my da0: Removable Direct Acce
return(ENOATTR);
+ return (error);
}
-if (olen == -1) {
+if (error == ENOATTR) {
/* new, append at end */
p = eae + easize;
easize += ealength;
--
Brian Fundakowski Feldman \&
rsion. Unfortunately, I
cannot get to my broadband connection until Thursday because I am staying
with my wife at the hospital. If noone else sends you one, I will try to
make one for you and mail it then.
- brian
On Tue, 22 Oct 2002, Juli Mallett wrote:
> * De: Soeren Schmidt <[EMAI
attempt to track
it down?
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] <> [EMAIL PROTECTED] \ The Power to Serve! \
Opinions expressed are my own.
Josef Karthauser <[EMAIL PROTECTED]> wrote:
> Does this happen on a current with this patch applied too?
I'm certain I tried this already :(
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
e)
ohci_device_bulk_start+0x0d
ohci_device_bulk_transfer+0x27
usbd_transfer+0xc0
umass_setup_transfer+0x4f
umass_bbb_state
usb_transfer_complete
ohci_softintr
Can anyone confirm if this is normal or I have an exceptional system? I
have two completely unrelated OHCI-based controllers in my system and
neither
epping = 2
Features=0x383fbff
AMD Features=0xc0400000
I'm trying to track it down, though.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\
<> [EMAIL PROTECTED] <> [EMAIL PROTECTED] \
seeing any
> SSE code related problems ? (P III based SMP system here)
Yes, I see the same problems with npxrestore() in sigreturn(), but on my
Athlon it seems to occur with or without SSE. I'm trying to track it down...
--
Brian Fundakowski Feldman \'[
I got a crash today because "xvp" did not have an interlock when the
call was made to vn_lock(LK_INTERLOCK):
407 if (snapdebug)
408 vprint("ffs_snapshot: busy vnode", xvp);
409 if (vn_lock(xvp, LK_EXCLUSIVE | LK_INTERLOCK, td) !=
xpected behavior.
Are you using "dangerously-dedicated" disks? That is, no fdisk-style
partition table? If so, disklabel on ad0 or ad2 itself would be valid. It
doesn't appear you are, in which case a disklabel operation should be
performed on the slice, e.g. disklabel ad2s2
"Brian F. Feldman" <[EMAIL PROTECTED]> wrote:
> German Tischler <[EMAIL PROTECTED]> wrote:
> > Hi.
> >
> > I can panic my current system compiled from sources of yesterday
> > by just starting mozilla or ogg123 if I don't include
&g
"Steven G. Kargl" <[EMAIL PROTECTED]> wrote:
> Brian F. Feldman said:
> > "Steven G. Kargl" <[EMAIL PROTECTED]> wrote:
> > > The source tree was retrieved by cvsup
> > > at 21:47 (PST) on Oct 4.
> > >
> > > This is a no
he problem is that in src/sys/ufs/ffs/
ffs_snapshot.c:ffs_snapshot(),
as the mnt vnode list is traversed none of the vnodes ("xvp") would actually GET
VI_LOCK()ed in the first place, and so the LK_INTERLOCK is bogus in the
vn_lock() call. Kirk would know for sure what to
seeing any
> SSE code related problems ? (P III based SMP system here)
I seem to have the same problem on my currently-UP Athlon system, whether or
not SSE is enabled; I'm trying to track it down...
--
Brian Fundakowski Feldman \'[ FreeBSD ]''&
Well, this has been happening for about a year on my dev box. It's not
gcc 3.1 specific.
I've never gotten around to figuring out why it works on some machines.
On Sat, 29 Jun 2002 19:41:51 -0700, David O'Brien wrote:
> On Sat, Jun 29, 2002 at 11:30:48PM +0100, Brian Som
/lib/libGLU.so: undefined reference to `operator new(unsigned)'
> *** Error code 1
>
> Stop in /usr/ports/x11/XFree86-4-clients/work/xc/programs/glxinfo.
> *** Error code 1
> --
> self-producing in perl :
> $_=q(print"\$_=q($_);eval;");eval;
>
expiration before I get a call
that email is down. I have actually gone out and killed every process
running on the machine that I can (including inetd, syslogd, cron, sshd,
sendmail and inn). The wired memory is never released until I reboot the
machine.
Any ideas (other than going to
recently used by kqueue
I've actually seen this, too; not been able to track it down at all, though.
At the moment, I've checked everywhere obviously M_KQUEUE memory is alloced
and dealloced and have no good leads.
--
Brian Fundakowski Feldman \'[ Fre
/mnt
> >
> > /snip/
> >
> > --
> > Peter Hessler
> > <[EMAIL PROTECTED]>
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the b
structions are incorrect
> This seems exactly backwards.
>
> Warner
Unlike replying to something without including a shred of context,
to half-a-dozen addresses including a mail list,
to which all the other recipients are probably subscribed anyways.
Brian K. Whi
> > Brian Somers <[EMAIL PROTECTED]> writes:
> > > This was fixed an hour or so ago. Phk backed out the daddr_t size
> > > change pending investigation.
> >
> > Does that fix the loader too, or just the kernel?
>
> I'm not sure, I'm ju
> Brian Somers <[EMAIL PROTECTED]> writes:
> > This was fixed an hour or so ago. Phk backed out the daddr_t size
> > change pending investigation.
>
> Does that fix the loader too, or just the kernel?
I'm not sure, I'm just rebuilding now.
Remember, /bo
x27; counts
> > as funny stuff)
This was fixed an hour or so ago. Phk backed out the daddr_t size
change pending investigation.
--
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > Try disabling -pipe when building the compiler. This seems to make
> > things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> > building the kernel with -pipe sometimes produces a kernel that
>
ny case, so it's worth just ignoring in my
opinion. (Witness the address 0.1, where the Ethernet was probably found at
0.0). Sound about right?
--
Brian Fundakowski Feldman \'[ FreeBSD ]'''''&#x
H
> Phone: +41 061 826 93 00: +41 61 826 93 01
> PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
> --
>
--
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
http://www.freebsd-services.com/
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I still
have no idea what causes it - except that some kernels ``just work''
and some don't.
Maybe it depends on the humidity in the room when a kernel is built
or something - and I'm only half joking here !
FWIW ru, /boot/kernel/kernel seems ok now. /boot/kernel.sig/ke
> On Fri, 26 Apr 2002, Brian Somers wrote:
>
> BS>The intent is to discover whether there's a filesystem yet (vn_open()
> BS>will die horribly otherwise).
> BS>
> BS>My use of rootdev is (obviously) flawed. AFAICT, either rootvp
> BS>or rootvnode should
ild a kernel at the moment).
If somebody could test that rootvnode or rootvp are non-NULL after
an NFS-mounted root is set up, I'd thankfully approve the quick
fix... :*)
Cheers.
> Ian
--
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
http://www.freeb
On Tue, Apr 23, 2002 at 01:54:17PM +0200, Poul-Henning Kamp wrote:
> This commit detects a memory overwrite problem in the kernel which
> happens before we ever get into userland for the first time.
Do you know the address being corrupted? If so, try breaking into ddb
early on and set a hardware
> Hello.
>
> > brian 2002/03/30 04:30:11 PST
>
> > Modified files:
> > usr.sbin/ppp Makefile async.c async.h atm.c bundle.c
> > ccp.c ccp.h chap.c chap.h chat.c
> >
(PST/PDT assumed):
>
> 2002-4-7 2:0:0.0
>
> should be:
>
> 2002-4-7 3:0:0.0
>
> Anyone object or have any thoughts? -sc
--
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
http://www.freebsd-services.com/
Don't _EVER_ lose your s
pw = getpwuid (getuid ());
> 540 endpwent ();
> 541 }
> 542 if (pw)
> 543 {
>
> (that's from glib12)
>
> This makes panel,gnome-session, etc all crash on start.
>
>
> -current as of this morning.
>
out nothing, so far, RTFM.
|
|
|
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with "unsubscribe freebsd-stable" in the body of the message
--
Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work)
Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal
ialize the general
modification of the vm_map {} structure itself, just certain kinds of
changes, so is easily a primary reason that the VM system as it stands now
is inherently single-threaded.
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''
browser I know that can handle Java
pages on FreeBSD.
Are there others?
If you mean the FreeBSD-native netscape 4.x; yes, it's perfectly silly to run
*that*.
|
| Ken
|
|
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with "unsubscribe freebsd-hackers" in the body of the message
. Chapman Jr.
> [EMAIL PROTECTED] Raintree Network Services, Inc.
> [EMAIL PROTECTED] FreeBSD Committer
--
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
http://www.freebsd-services.com/
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
shake out
any problems it causes.
> M
> --
> o Mark Murray
> \_
> O.\_Warning: this .sig is umop ap!sdn
--
Brian <[EMAIL PROTECTED]>
<http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour !
l ATA/100 raid
controller with up to 128MB onboard cache and it support Levels 0,1,0+1
and 5. Looks real promising, but I cannot see any support for it in
ata-raid.[ch]. Will the current code support this card? Or are there
plans to add it in the near future?
tia,
- brian
To Unsubscribe: send ma
s several features of the kernel which aren't
currently there to be fully-functionalI don't think there would be any harm
in adding it, though, and saying as much in /etc/defaults/rc.conf :)
--
Brian Fundakowski Feldman \'[ FreeBSD ]''''
ttle ram and it's been a damned fine freebsd box for me. neven
gnome and enlightenment and gimp and netscape et al are fast enough to be
useable, although I did disable gnome and E in favor of icewm just on
general principle.
Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/b
Paul van der Zwan <[EMAIL PROTECTED]> wrote:
> > On 14-Feb-2002 (08:29:50/GMT) Brian Fundakowski Feldman wrote:
> >
> > > Please try this change (already committed to -CURRENT) and let me
> > > know if crashes due to detaching USB devices specifically ha
Please try this change (already committed to -CURRENT) and let me know if
crashes due to detaching USB devices specifically have been eliminated.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/usb.c.diff?r1=1.54&r2=1.55&f=h
--
Brian Fundakowski
On Saturday 02 February 2002 03:57 pm, Juha Saarinen wrote:
> On Sat, 2 Feb 2002, Brian T.Schellenberger wrote:
> > No, it's not, because it still maintains a separation between "system"
> > control (rc.conf) and application control (/var/packges).
> &g
. .
>
> -- Terry
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
--
Brian T. Schellenberger . . . . . . . [EMAIL PROTECTED] (work)
Brian, the man from Babble-On . . . . [EMAIL PROTECTED] (personal)
On Friday 01 February 2002 08:38 pm, Terry Lambert wrote:
> "Brian T.Schellenberger" wrote:
> > - There is not a single point of failure for all progams; it only
> > controls basic system functions and services, it does not control
> > applications, so if it fail
1 - 100 of 954 matches
Mail list logo
