Join Afroconnections Today!
Instructions for removal is at the bottom of this message.If you have any questions regarding this e-mail, please send them to emailto:[EMAIL PROTECTED]If you hit reply , you will automatically be removed from this list.Dear Friend,We are AfroConnections.com - leaders in providing African Americans with the best way to meet each other for the purposes of friendship, dating or joint activities.Come and join tens of thousands of members who have already connected.To get started "Today" and receive 3 FREE email contacts go to http://www.afroconnections.comBest RegardsYour Fri! ! ends at AfroConnections.com(A member of SocialPlus.com network)PS. Do not forget to tell a friend about us. Click here http://www.afroconnections.com/recommend.aspPPS. For more information, please contact us at mailto:[EMAIL PROTECTED]This email sent by http://www.EmailFactory.comThe Web-Based Precision Opt-In Email Marketing Solution.To UNSUBSCRIBE from this mailing list:Reply to this message with the w! ! ord 'unsubscribe' as the subject ORTo UNSUBSCRIBE from this mailing list, go to:http://UNSUBSCRIBE.EmailFactory.com/handler/default.cfm?action=optout&func=removeMe&idAddress=L5062566403%2E2910
Re: CURRENT is freezing again ...
On Thu, Nov 16, 2000 at 10:27:39PM +0100, Soren Schmidt scribbled: | It seems John Baldwin wrote: | > | > 1) What revision of sys/kern/kern_synch.c do you have? I fixed several things | > yesterday, and the latest version is 1.108. | | 1.108 | | > 2) If you do have the latest version, have you compiled a kernel with WITNESS, | > INVARIANTS, and INVARIANT_SUPPORT to see how it runs? | | Have those in too... | | It still cant compile a kernel, it hangs itself in ~30 secs, no messages, | no hints, no nothing, the machine just locks up solid as usual.. | | Mind you the same machines run 4.2 and PRE_SMPNG without a hitch... | | > Also, I have noticed that occasionally on my SMP boxes the console seems to | > lose itself. By lose itself, I mean that all output stops, and it doesn't | > process any input. If I hit Ctrl-Alt-Backspace to break into the debugger, it | > suddenly catches up and processes all pending events before dropping into teh | > debugger, but hangs again when I continue from ddb. However, the rest of hte | > machine works fine during this time. I can ssh in, build kernels, reboot, etc. | > without any problem. | | It has been like this almost since the SMPNG stuff vent in, at least on all my | -current machines... I had those problems too a while ago on a UP p3-650 laptop. Finally I just newfs'ed the machine and installed the 20001028 snapshot, then cvsupp'ed to 20001122. The laptop now works well. What I saw was processes forking and forking again until the machine runs out of memory and swap. I think it may be some old libraries left over from upgrades and make world. -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
strange behaviour of mkioctls in kdump/truss
Hi, Since I've moved to -CURRENT a few weeks ago [I'm fairly new to FreeBSD] I had build problems with kdump and truss. The problem I report here are as far as I can judge them, sorry for any errors or inconsistencies. I've tried to find something about an earlier bug report but could not find any. The problem consisted of the definition for TELNO_MAX not defined or included in /usr/include/machine/i4b_rbch_ioctl.h. The definition for this is in /usr/include/machine/i4b_ioctl.h. By coincidence the building of kdump/truss succeeds, due to the fact that mkioctl uses find(1) for the retreiving of the include files. And because i4b_ioctl.h is alphabetical in front of i4b_rbch_ioctl.h it will be included before i4b_rbch_ioctl.h and therefor the value for TELNO_MAX is already defined on the moment i4b_rbch_ioctl.h is included. Due to some reason I don't know yet [please enlighten me on this] i4b_rbch_ioctl.h appeared before i4b_ioctl.h in _my_ ioctl.c! [Although like I told find(1) uses alphabetical order ?!?!] This happened still after various builds and cleans, etc. But after I have touched the files a bit [e.g. editing them for testing] they do also appear in the right order for me now. So in my case make buildworld stopped on this error because it did not know the value of TELNO_MAX, which is correct as far as it goes for the compiler part. Anyway, like I said earlier, due to some luck it went well for a long time. [that is why nobody reported it before probably, otherwise shoot me] The solution to this seems to be simple: #include in i4b_rbch_ioctl.h Don't hesitate to ask me anything more (that I forgot). Regards, Mark -- Mark Santcroos RIPE Network Coordination Centre PGP KeyID: 1024/0x3DCBEB8D PGP Fingerprint: BB1E D037 F29D 4B40 0B26 F152 795F FCAB 3DCB EB8D To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
It seems John Baldwin wrote: > > 1) What revision of sys/kern/kern_synch.c do you have? I fixed several things > yesterday, and the latest version is 1.108. 1.108 > 2) If you do have the latest version, have you compiled a kernel with WITNESS, > INVARIANTS, and INVARIANT_SUPPORT to see how it runs? Have those in too... It still cant compile a kernel, it hangs itself in ~30 secs, no messages, no hints, no nothing, the machine just locks up solid as usual.. Mind you the same machines run 4.2 and PRE_SMPNG without a hitch... > Also, I have noticed that occasionally on my SMP boxes the console seems to > lose itself. By lose itself, I mean that all output stops, and it doesn't > process any input. If I hit Ctrl-Alt-Backspace to break into the debugger, it > suddenly catches up and processes all pending events before dropping into teh > debugger, but hangs again when I continue from ddb. However, the rest of hte > machine works fine during this time. I can ssh in, build kernels, reboot, etc. > without any problem. It has been like this almost since the SMPNG stuff vent in, at least on all my -current machines... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /tmp
Leif Neland wrote: > > Something keeps changing permissions on /tmp to 755, which causes pine to > claim the mailbox is in use by another process. > This change has occurred a couple of times lately, but I haven't found a > pattern. > When I reset the perms to 777, pine works normal again. > What is the proper perms on /tmp? > > Leif > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message I ran into the same thing a lot on our main intranet server (Solaris 7).. what it ended up being was pretty simple. I used to compile most of my stuff in /tmp (now I do it in ~/compiling), and sometimes do the bad thing (relative paths.. enough said) of extracting stuff as root in /tmp. Some tarfiles would then extract into . and reset the permissions of . - for instance, McAfee for UNIX virus updates. The permissions would get reset to 755. And of course, I'd get tons of user complaints that things were messing up for them (for instance, uw-imap). Just wanted to share one possible explanation.. this sure had us fooled for a few weeks. -- #-# name> thomas r. strombergwork> [EMAIL PROTECTED] pos> senior systems administrator home> [EMAIL PROTECTED] corp> research triangle commerce (icc.net) web> http://chaotical.ly/ #-# earth has a lot of things other folks might want, like the whole planet -- william s. burroughs To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: CURRENT is freezing again ...
On 16-Nov-00 Valentin Chopov wrote: > Hi, > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > 10 min after boot... > > Thanks, > > Val Two questions: 1) What revision of sys/kern/kern_synch.c do you have? I fixed several things yesterday, and the latest version is 1.108. 2) If you do have the latest version, have you compiled a kernel with WITNESS, INVARIANTS, and INVARIANT_SUPPORT to see how it runs? Also, I have noticed that occasionally on my SMP boxes the console seems to lose itself. By lose itself, I mean that all output stops, and it doesn't process any input. If I hit Ctrl-Alt-Backspace to break into the debugger, it suddenly catches up and processes all pending events before dropping into teh debugger, but hangs again when I continue from ddb. However, the rest of hte machine works fine during this time. I can ssh in, build kernels, reboot, etc. without any problem. -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
"Andresen,Jason R." wrote: > Garrett Wollman wrote: > > > > < said: > > > > > I have a similar problem -- every time I make world, perms on /var/mail > > > get set to 775. Mutt considers my mailbox read-only until I change it > > > to 1777. > > > > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail > > is insecure, but was necessary in the mists of ancient past, before > > UNIX learned to do file locking. Unless your mail spool is shared > > over NFS (don't do that), locking is reliable and .lock files should > > never be used or relied upon. > > Not the FreeBSD's file locking works anyway. > Here's the results from a test of the below program: You test case is incorrect. Following quote from flock(2) explains why: [...] NOTES Locks are on files, not file descriptors. That is, file descriptors du- plicated through dup(2) or fork(2) do not result in multiple instances of a lock, but rather multiple references to a single lock. If a process holding a lock on a file forks and the child explicitly unlocks the file, the parent will lose its lock. [...] -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
Mike Meyer wrote: > > Andresen,Jason R. <[EMAIL PROTECTED]> types: > > Garrett Wollman wrote: > > > > > > < said: > > > > > > > I have a similar problem -- every time I make world, perms on /var/mail > > > > get set to 775. Mutt considers my mailbox read-only until I change it > > > > to 1777. > > > > > > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail > > > is insecure, but was necessary in the mists of ancient past, before > > > UNIX learned to do file locking. Unless your mail spool is shared > > > over NFS (don't do that), locking is reliable and .lock files should > > > never be used or relied upon. > > > > Not the FreeBSD's file locking works anyway. > > Here's the results from a test of the below program: > > I can see at least two problems with the test program. > > 1) You're locking a shared descriptor. Possibly that should work, but >it's not a case I normally see. Moving the open after the fork >makes this behave better. Actually, it does work in Irix. I'll try that under FreeBSD. That seems to have fixed the problem under FreeBSD, although it might be a good idea to mention somewhere in the manpage that shared file descriptors are handled differently than they are in other OSes (Irix for instance). This is the kind of caveat that is likely to catch the unsuspecting developer. > 2) You're depending on a synchronization between the two process, but >not doing anything to insure it. The correct test is not that the >last message was the child string, but that the last two messages >are the same. Yeah, I tossed this program together last year when someone said they couldn't get file locking to work under FreeBSD, I wanted to see if it was working at all. The only "syncronization" is that the processes wait for a second before writing, which in my case was enough (unloaded PII 400s with no disk activity can get a write out in less than 1 second). -- _ __ ___ ___ __ / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED] / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those /_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
* Steven E. Ames <[EMAIL PROTECTED]> [001116 09:27] wrote: > It seems to only do it SMP... the same machine built with a non-SMP > kernel (same source code) runs just fine for extended periods. John just checked in some code last night that may address your problems. I would try a new kernel, and perhaps some collabaration with John to debug these problems rather than just complaining about the situation. I see at least two experianced developers in the CC list, there's no reason for these poor bug reports. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
> It seems Boris Popov wrote: > > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > > 10 min after boot... > > > > > > You mean "is still freezing" right ? > > > > > > Current has been like this for longer than I care to think about, it > > > seems those in charge doesn't take these problems seriously (enough)... > > > > I think info about where/how it freezing would be more helpful. > > No idea, the system just freezes, no drob to DDB no remote gdb no > nothing, so its really hard to tell where... > As to how, just boot current on a fairly fast machine, make a kernel > and it'll hang in minutes if not less, or just leave it alone and > it will hang in 10-30 mins... I have the same problem on a dual PII 400mhz. I haven't tried to remove the SMP support, but I have not too much time to cvsup and to make anything else. I'll try to boot the GENERIC (damn !%&!& , I always repeat to myself that is a good habits to compile the GENERIC too after updates... but I never do... :-( ) -- Regards... Gianmarco "Unix expert since yesterday" http://www.giovannelli.it To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
Andresen,Jason R. <[EMAIL PROTECTED]> types:
> Garrett Wollman wrote:
> >
> > < said:
> >
> > > I have a similar problem -- every time I make world, perms on /var/mail
> > > get set to 775. Mutt considers my mailbox read-only until I change it
> > > to 1777.
> >
> > It is misconfigured (or perhaps just broken). 1777 mode for /var/mail
> > is insecure, but was necessary in the mists of ancient past, before
> > UNIX learned to do file locking. Unless your mail spool is shared
> > over NFS (don't do that), locking is reliable and .lock files should
> > never be used or relied upon.
>
> Not the FreeBSD's file locking works anyway.
> Here's the results from a test of the below program:
I can see at least two problems with the test program.
1) You're locking a shared descriptor. Possibly that should work, but
it's not a case I normally see. Moving the open after the fork
makes this behave better.
2) You're depending on a synchronization between the two process, but
not doing anything to insure it. The correct test is not that the
last message was the child string, but that the last two messages
are the same.
Actually, my first test was to change this to "lock, prompt, write,
unlock, exit", then run it in two windows. The first process pauses -
with the file locked - and the second hangs until the user responds to
the prompt.
(81 ~/bin/src): uname -a
> FreeBSD escaflowne.el.hazard 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Sat
> Oct 14 18:59:16 EDT 2000
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ESCAFLOWNE i386
> (82 ~/bin/src): ./testflock
> flock(2) is implemented, but not functional.
>
> And another test:
> %kenshin (1 ~): uname -a
> IRIX kenshin 6.5 01221642 IP20
> %kenshin (2 ~): ./testflock
> flock(2) is fully functional.
>
> I hope I'm doing something wrong here, and that flock really does work
> on FreeBSD.
>
> #include
> #include
> #include
> #include
> #include
> #include
>
> #define TMPFILENAME "/tmp/testflock.out"
> #define MESSLEN 8
> #define CHILDSTR "Child \n"
> #define PARENTSTR "Parent\n"
>
> int main( int argc, char** argv)
> {
> char message[MESSLEN];
> int pid;
> int fd;
> int foo;
>
> fd = open(TMPFILENAME, O_WRONLY | O_CREAT, 0644);
>
> pid = fork();
>
> if ( pid == 0 )
> {
> strcpy(message, CHILDSTR);
> sleep(1);
> }
> else
> strcpy(message, PARENTSTR);
>
>
> flock(fd, LOCK_EX);
>
> lseek(fd, 0, SEEK_END);
> write(fd, message, MESSLEN - 1);
>
> sleep(2);
>
> lseek(fd, 0, SEEK_END);
> write(fd, message, MESSLEN - 1);
>
> flock(fd, LOCK_UN);
>
> close(fd);
>
> if ( pid != 0 )
> {
> wait(&foo);
>
> /* Test the file, see if flock works */
> fd = open(TMPFILENAME, O_RDONLY);
>
> read(fd, (void*)message, MESSLEN - 1); /* Discard first
> */
> read(fd, (void*)message, MESSLEN - 1);
>
> if (! strcmp(message, CHILDSTR))
> printf("flock(2) is implemented, but not
> functional.\n");
> else
> printf("flock(2) is fully functional.\n");
>
> close(fd);
> }
>
> return 0;
> }
>
>
> --
>_ __ ___ ___ __
> / \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED]
> / /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those
> /_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation.
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
It seems to only do it SMP... the same machine built with a non-SMP kernel (same source code) runs just fine for extended periods. -Steve - Original Message - From: "Soren Schmidt" <[EMAIL PROTECTED]> To: "Boris Popov" <[EMAIL PROTECTED]> Cc: "Valentin Chopov" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, November 16, 2000 12:17 PM Subject: Re: CURRENT is freezing again ... > It seems Boris Popov wrote: > > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > > 10 min after boot... > > > > > > You mean "is still freezing" right ? > > > > > > Current has been like this for longer than I care to think about, it > > > seems those in charge doesn't take these problems seriously (enough)... > > > > I think info about where/how it freezing would be more helpful. > > No idea, the system just freezes, no drob to DDB no remote gdb no > nothing, so its really hard to tell where... > As to how, just boot current on a fairly fast machine, make a kernel > and it'll hang in minutes if not less, or just leave it alone and > it will hang in 10-30 mins... > > -Søren > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
It seems Boris Popov wrote: > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > > 10 min after boot... > > > > You mean "is still freezing" right ? > > > > Current has been like this for longer than I care to think about, it > > seems those in charge doesn't take these problems seriously (enough)... > > I think info about where/how it freezing would be more helpful. No idea, the system just freezes, no drob to DDB no remote gdb no nothing, so its really hard to tell where... As to how, just boot current on a fairly fast machine, make a kernel and it'll hang in minutes if not less, or just leave it alone and it will hang in 10-30 mins... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
Garrett Wollman wrote:
>
> < said:
>
> > I have a similar problem -- every time I make world, perms on /var/mail
> > get set to 775. Mutt considers my mailbox read-only until I change it
> > to 1777.
>
> It is misconfigured (or perhaps just broken). 1777 mode for /var/mail
> is insecure, but was necessary in the mists of ancient past, before
> UNIX learned to do file locking. Unless your mail spool is shared
> over NFS (don't do that), locking is reliable and .lock files should
> never be used or relied upon.
Not the FreeBSD's file locking works anyway.
Here's the results from a test of the below program:
(81 ~/bin/src): uname -a
FreeBSD escaflowne.el.hazard 4.1.1-STABLE FreeBSD 4.1.1-STABLE #0: Sat
Oct 14 18:59:16 EDT 2000
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ESCAFLOWNE i386
(82 ~/bin/src): ./testflock
flock(2) is implemented, but not functional.
And another test:
%kenshin (1 ~): uname -a
IRIX kenshin 6.5 01221642 IP20
%kenshin (2 ~): ./testflock
flock(2) is fully functional.
I hope I'm doing something wrong here, and that flock really does work
on FreeBSD.
#include
#include
#include
#include
#include
#include
#define TMPFILENAME "/tmp/testflock.out"
#define MESSLEN 8
#define CHILDSTR "Child \n"
#define PARENTSTR "Parent\n"
int main( int argc, char** argv)
{
char message[MESSLEN];
int pid;
int fd;
int foo;
fd = open(TMPFILENAME, O_WRONLY | O_CREAT, 0644);
pid = fork();
if ( pid == 0 )
{
strcpy(message, CHILDSTR);
sleep(1);
}
else
strcpy(message, PARENTSTR);
flock(fd, LOCK_EX);
lseek(fd, 0, SEEK_END);
write(fd, message, MESSLEN - 1);
sleep(2);
lseek(fd, 0, SEEK_END);
write(fd, message, MESSLEN - 1);
flock(fd, LOCK_UN);
close(fd);
if ( pid != 0 )
{
wait(&foo);
/* Test the file, see if flock works */
fd = open(TMPFILENAME, O_RDONLY);
read(fd, (void*)message, MESSLEN - 1); /* Discard first
*/
read(fd, (void*)message, MESSLEN - 1);
if (! strcmp(message, CHILDSTR))
printf("flock(2) is implemented, but not
functional.\n");
else
printf("flock(2) is fully functional.\n");
close(fd);
}
return 0;
}
--
_ __ ___ ___ __
/ \/ \ | ||_ _|| _ \|___| | Jason Andresen -- [EMAIL PROTECTED]
/ /\/\ \ | | | | | |/ /|_|_ | Views expressed may not reflect those
/_/\_\|_| |_| |_|\_\|___| | of the Mitre Corporation.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
On Thu, 16 Nov 2000, Soren Schmidt wrote: > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > > 10 min after boot... > > You mean "is still freezing" right ? > > Current has been like this for longer than I care to think about, it > seems those in charge doesn't take these problems seriously (enough)... I think info about where/how it freezing would be more helpful. > I've started doing development on -stable instead, it goes nowhere > on -current - works fine for me even with my new evil hacks :) -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /var/mail
< said: > I have a similar problem -- every time I make world, perms on /var/mail > get set to 775. Mutt considers my mailbox read-only until I change it > to 1777. It is misconfigured (or perhaps just broken). 1777 mode for /var/mail is insecure, but was necessary in the mists of ancient past, before UNIX learned to do file locking. Unless your mail spool is shared over NFS (don't do that), locking is reliable and .lock files should never be used or relied upon. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CURRENT is freezing again ...
It seems Valentin Chopov wrote: > Hi, > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in > 10 min after boot... You mean "is still freezing" right ? Current has been like this for longer than I care to think about, it seems those in charge doesn't take these problems seriously (enough)... I've started doing development on -stable instead, it goes nowhere on -current -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Proper permissons on /tmp
On Thu, Nov 16, 2000 at 06:54:23AM +0100, Leif Neland wrote: > Something keeps changing permissions on /tmp to 755, which causes pine to > claim the mailbox is in use by another process. I have a similar problem -- every time I make world, perms on /var/mail get set to 775. Mutt considers my mailbox read-only until I change it to 1777. Is there a supported way to locally override BSD.var.dist, or do I need to install mutt setgid mail, or what? -- Ben 220 go.ahead.make.my.day ESMTP Postfix To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CURRENT is freezing again ...
Hi, After last cvsup my machine (Dual PIII, SMP kernel) is freezing again in 10 min after boot... Thanks, Val To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unable to build world
The last time i built -current world was using 4.1-STABLE, about uhm 2:nd or 3:rd november. This is the first time i tried building world since the upgrade. / Joel.L a.k.a Nevyn -- #FreeBSD.se, #unix.se On Wed, 15 Nov 2000, David O'Brien wrote: > On Wed, Nov 15, 2000 at 09:20:06PM +, Joel Lindau wrote: > > When i try to build my -current world cvsupped today ( 15 nov ) i get the > > following errors: > > When was the last time up built world? I'd like to know if this has > anything to do with the Binutils upgrade, or if is something you would > have experienced if you had tried to build world yesterday > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: clock/apm broken in CURRENT ?
According to Warner Losh: > to your config file. Fixes it for me. Tell people on #bsdcode about > this. Darn, I thought I remembered this one, sorry for being stupid. Works now. /me blames it on the flu -- Ollivier ROBERT -=- Eurocontrol EEC/ITM -=- [EMAIL PROTECTED] FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Thu Aug 10 17:36:11 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
$B%a!<%k%"%I%l%9HNGd!JG/Fb8BDj!K$N$*CN(B$B$i$;(B
$BFMA3$N%a!<%k!"?=$7Lu$"$j$^$;$s!#8fITMW$N>l9g$O:o=|$7$F$/$@$5$$!#(B == $B!|!|!|%@%$%l%/%H%a!<%kMQ!!%a!<%k%"%I%l%94|4V8BDjHNGd$N$*CN$i$;!|!|!|(B == $B%a!<%k%"%I%l%9%G!<%?$rG/Fb8BDj$G!"3J0BHNGd$$$?$7$^$9!#(B $BEve$2$^$9!#(B -- $B!|%G!<%?%?%$%W!J#A!K!!!J0B2A$GBgNL$K;EF~$l$?$$J}$O!"$3$N#A%?%$%W$r!*!K(B -- $B#1K|7o!!(B 2,000$B1_!JC12A(B0.20$B1_!K(B $B!!#1#0K|7o!!(B 5,000$B1_!JC12A(B0.05$B1_!K(B $B!!#2#5K|7o!!(B10,000$B1_!JC12A(B0.04$B1_!K(B $B!!#5#0K|7o!!(B15,000$B1_!JC12A(B0.03$B1_!K(B $B#1#0#0K|7o!!(B20,000$B1_!JC12A(B0.02$B1_!K(B $B#3#0#0K|7o!!(B30,000$B1_!JC12A(B0.01$B1_!K(B -- $B!|%G!<%?%?%$%W!J#B!K!!!J%8%c%s%kJL$K8!:w!&Cj=P$7$?%a!<%k%"%I%l%9$G$9!K(B -- $B#1K|7o!!(B 8,000$B1_!JC12A(B0.80$B1_!K(B $B#3K|7o!!(B21,000$B1_!JC12A(B0.70$B1_!K(B $B!!#1#0K|7o!!(B60,000$B1_!JC12A(B0.60$B1_!K(B $B!!#1#5K|7o!!(B75,000$B1_!JC12A(B0.50$B1_!K(B $B!!#2#0K|7o!!(B80,000$B1_!JC12A(B0.40$B1_!K(B $B>e5-$NNA6b$O!J#A!K!J#B!K%?%$%W6&$K$9$Y$F!">CHq@G9~$_$N2A3J$G$9!#(B $B5$C$?>l9g$K$O!"#5#5K|7o$r$*5RMM$X$*EO$7$7$F$$$^$9!#(B -- $B!|%a!<%k%"%I%l%9%G!<%?$N$*0zEO$7J}K!!J#3l9g!"F~6b3NG'8e#3;~4V0JFb$KAw?.(B $B!!$7$F$*$j$^$9!#:GB.$G!"?69~8e#3#0J,$GAw?.$$$?$7$^$9!#(B $B#2!%6d9T8}:B$K$*?69~3NG'8e!"$4;XDj$N=;=j$X(B CD-ROM $B$^$?$O(B FD $B$rM9Aw!#(B $B!JJLES!"AwNA(B1,000$B1_$r?=$7&IJE~Ce;~$KBpG[JX6He5-$N$h$&$KJ]B8$5$l$F$$$^$9!#(B $BDL>o$O#C#S#V7A<0$N%U%!%$%k$K$F$4Ds6!$5$;$F$$$?$@$-$^$9$,!"$b$7$*5RMMB&(B $B$KITET9g$,$"$k>l9g$O!"B>$N%U%!%$%k7A<0$K$F$4Ds6!$9$k$3$H$b2DG=$G$4$6$$(B $B$^$9$N$G(B [EMAIL PROTECTED] $B$^$G!"$*Ld$$9g$o$;$/$@$5$$!#(B -- $B!|%a!<%k%"%I%l%9%G!<%?$NFbMF$K$D$$$F(B -- $BEvo$K?7A/$G$9!*$^$?!"7HBSEEOC$d#P#H#S$N%a!<%k(B $B%"%I%l%9$O4^$^$l$F$*$j$^$;$s!#Ds6!$9$k%a!<%k%"%I%l%9$OF|K\9qFb$G$N;HMQ(B $B$rL\E*$H$7$?%G!<%?$G$9!#(B $B"(%G!<%?$NCf$K$O#1%u7n0JFb$K%W%m%P%$%@$NJQ99$d2rLsEy$K$h$jFO$+$J$/$J$C(B $B$F$$$k%"%I%l%9$b?t!s$O4^$^$l$F$$$k2DG=@-$,$"$k$3$H$r$4N;>5$/$@$5$$!#(B -- $B!|$49XF~J}K!(B -- $B2<5-;v9`$r5-:\$N>e(B [EMAIL PROTECTED] $B$^$G%a!<%k$K$FAw?.$7(B $B$F$/$@$5$$!#(B $B#1!%$*L>A0(B $B!J?69~;~$NL>A0$HF10l$K$J$k$h$&$K$7$F$/$@$5$$!#%O%s%I%k%M!<%`$G$b9=(B $B!!$$$^$;$s!K(B $B#2!%O"Mm@h%a!<%k%"%I%l%9(B $B$4CmJ8D:$$$F$+$i!"FbMF$N3NG'%a!<%k$r$3$NO"Mm@h$KAw?.$$$?$7$^$9!#(B $B$=$N;~$K?69~@h$N6d9TL>!"8}:BHV9fEy$b0l=o$K$4O"Mm:9$7>e$2$^$9!#(B $B#3!%$*0zEO$7J}K!!J%a!<%k$G!"M9Aw$G!"Be6b0z49$G!K(B $BFC$K!"$*5RMMB&$G$4;XDj$NL5$$>l9g$O!">e5-!VO"Mm@h%a!<%k%"%I%l%9!W$X(B $B%a!<%k$K$F%G!<%?$rAw?.$5$;$F$$$?$@$-$^$9!#(B $B#4!%9XF~7o?t!J#1!$#1#0!$#2#5!$#5#0!$#1#0#0!$#3#0#0!KK|7o(B $B>e5-0J30$N7o?t$G$b!J#7#5K|7oEy!K>5$j$^$9$N$G!"$*?=$7IU$1$/$@$5$$!#(B $B#5!%9XF~%G!<%?%?%$%W!J#A$O!V%N!<%8%c%s%k!W#B$O!V%8%c%s%kJL!W%G!<%?$G$9!K(B $B!!!J#A!K%?%$%W(B $B#A%?%$%W$ONw2AHG$N%a!<%k%"%I%l%9$G$9!J0B$$$+$i8E$+$C$?$j!"H?1~$,0-(B $B$$$H$$$&$3$H$O$"$j$^$;$s!*!K0B$/$FBt;3M_$7$$J}$O!"$3$A$i$r$I$&$>!*(B $BNA6b$O!">e5-$N!J#A!K%?%$%WNA6bI=$r$4Mw$/$@$5$$!#(B $B!!!J#B!K%?%$%W(B $B#B%?%$%W$O$*5RMM$K$h$j!"%8%c%s%k$r;XDj$7$F$$$?$@$-$^$9!#(B $BNc$($P!V/!9;~4V$N$+$+$k$3$H$,$4$6$$$^$9!#CmJ8;~(B $B$K!"8!:wJ}K!$H$"$o$;$F!"$*Ld$$9g$o$;$/$@$5$$!#(B $BNA6b$O!">e5-$N!J#B!K%?%$%WNA6bI=$r$4Mw$/$@$5$$(B -- $B!|:G8e$K(B -- $BF|K\$G$b%$%s%?!<%M%C%H$NGzH/E*$JIa5Z$K$h$j0l?M$G$R$H$D$N%a!<%k%"%I%l%9(B $B$r;}$D;~Be$K$J$C$F$-$^$7$?!#%$%s%?!<%M%C%H$rMxMQ$7$?%@%$%l%/%H%a!<%k$O(B $B0B$/!"Aa$/!"3Ne$O>e$,$k!*!W$,EE;R%a!<%k$r(B $BMxMQ$7$?;~$N!"%@%$%l%/%H%a!<%k8z2L$G$9!#(B $BEve$2D:$$$?$*5RMM$+$i$N5;=QE*$J$4AjCL$b>5$C$F$*$j$^$9!#(B $B!JEz$($i$l$kHO0O$G$9$,!KBgNL$N%@%$%l%/%H%a!<%k$r<+F0Aw?.$9$k%=%U%H$d8z(B $B2LE*$J#D#M$NAw?.J}K!!"$^$?%a!<%k%"%I%l%9$N%U%!%$%k$r;XDj$N7A<0$KJQ49$9(B $B$k%5!<%S%9$d!"%Q%=%3%sD6=i?4pJsDs6!4k6H$+$i$N0MMj$K$h$j%j%&%s%8%g%s(BCorp.$B$,G[?.$7$F$*$j(B $B$^$9!#(B == $B!!%$%s%?!<%M%C%H4XO"4k6H$r%5%]!<%H$9$kAm9g#I#T4k6H(B $B%j%&%s%8%g%s(BCorp. --
RE: vmwareport does not work
Hi ... I'll give my worth of what the messages actually mean .. > i get > > kldload: can't load /usr/local/lib/vmware/lib/modules/vmmon_up.ko: File > exists This means the vmmon_up is already loaded - do a kldstat > sysctl: unknown oid 'net.link.ether.bridge_refresh' Seems like you do not have bridging compiled into the kernel ?? > kldload: can't load if_tap.ko: File exists This also axists already - same as vmmon_up above > ifconfig: ioctl (SIOCAIFADDR): File exists The ifconfig fails because it has already been done on bootup with the vmnet device - that's why the error "File exists" > > what' s wrong then ? > There doesn't seem to be anything wrong ... except that bridging isn't on (I think), but depending on how you use vmware networking it is not a show stopper. Reinier ### # # # R.N. Bezuidenhout NetSeq Firewall # # [EMAIL PROTECTED] http://www.nanoteq.co.za# # # ### -- Date: 16-Nov-00 Time: 11:21:04 This message was sent by XFMail -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Does floppies work with 384MByte RAM ?
On Wed, Nov 15, 2000 at 10:38:29PM -0500, Louis A. Mamakos wrote: > > I've got a Dell dual-Pentium-III XEON system at work that I was running > -current on. Some time ago (didn't notice when exactly, sigh) when > building new kernels, I started getting > > isa_dmainit(foo, bar) failed > For me it is a ASUS P2B-DS with 512M RAM. I see the same isa_dmainit failed with full ram utilized. With MAXMEM set to MAXMEM="(464*1024)" it is working under current. With 480M it is failing. I looked through the sources and found that contigousmalloc can't find a page of physical ram under the 16M margin. But I am not vm wizzard enough, to understand what the difference is with MAXMEM set to some lower value than the real amount of memory. Regards, Frank -- ~/.signature not found: wellknown error 42 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
