Re: dual booting -stable & -current
At 8:38 AM +0200 7/21/01, Thierry Herbelot wrote: >David O'Brien wrote: > > You are getting bit by the "root" aliasing code (IIRC this is the > > right way to describe the problem). This makes it impossible to > > install multiple copies of FreeBSD on a single disk w/o hacking > > around the system. :-( > >I do not understand what this problem is : >- I've got one system with two bootable FreeBSD "BIOS" partitions > (the one I already sent info about (these are two -Stable > versions) and both versions have been installed via > /stand/sysinstall How did you do those two installs though? David is not saying that dual-booting does not work. He is saying that the sysinstall step can get in your way, depending on how you try to create the two systems you want to boot between. Once you GET the slices and partitions set up right, then the booting process can easily handle multiple freebsd systems on a single disk. For instance, in the following sequence you should not run into any trouble with sysinstall: first set up a dual-boot system with the first dos-style slice being Windows, and the second one holding freebsd. after running this way for awhile, you decide that you do not need windows any more. So you again boot off the FreeBSD cd, you blow away Windows, and you install a second snapshot of freebsd on the slice which used to be Windows. For both of those freebsd installs, at the time of the install the first slice on the disk which was of type freebsd was also the slice that you wanted root (the '/' partition) of the new installation to be on. So, sysinstall has no trouble with what you want to do. Where you have trouble is if you have two dos-style slices defined, both of type freebsd, and you want sysinstall to install into the second of those two slices. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel module options Was: Re: Fw: help me!!!!
On Fri, 20 Jul 2001, Gordon Tetlow wrote: > Is this documented anywhere? If so, can you toss a pointer? I'd be > interested in learning a little kernel hacking, and I can't imagine this > would be *that* hard to implement. Nm, I was too lazy to check before, but apparently man module has lots of interesting information. Sorry about that. I'll go off into a corner and read now. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Suggestions for sysinstall / disklabel
At 1:43 AM -0400 7/21/01, Garance A Drosihn wrote: >[I'm not sure I made this obvious in my previous message, but these >suggestions were meant for the situation where the user is doing a >single install where they are spraying freebsd slices across multiple >partitions -- as was in the case in the example I gave] I meant "spraying freebsd PARTITIONS across multiple dos-style SLICES". I keep getting those two terms mixed up... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting -stable & -current
David O'Brien wrote: > > On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > You are getting bit by the "root" aliasing code (IIRC this is the right > way to describe the problem). This makes it impossible to install > multiple copies of FreeBSD on a single disk w/o hacking around the > system. :-( I do not understand what this problem is : - I've got one system with two bootable FreeBSD "BIOS" partitions (the one I already sent info about (these are two -Stable versions) and both versions have been installed via /stand/sysinstall - Another system runs with two FreeBSD "BIOS" partitions (used to switch between 3-Stable and 4-Stable) the boot0 boot selector is used to switch between releases - a third (a notebook) has one FreeBSD "BIOS" partition and used to be shared between 4-Stable and -Current (using all 8 FreeBSD partitions in the slice and using the loader to select ad0s4a or ad0s4e for root partition) - In this case, /stand/sysinstall was unable to create all 8 FreeBSD partitions : I had to first install FreeBSD on ad0s3, cut 8 partitions in ad0s4, then reinstall in ad0s4. [SNIP] -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting -stable & -current
At 9:06 PM -0700 7/20/01, David O'Brien wrote: >On Fri, Jul 20, 2001, Wilko Bulte wrote: > > Thing is I want to setup a dual-boot box, running -stable & -current. > > >> What I did is create >> ad0s1 -> 256MB -> holds root for -stable >> ad0s2 -> 256MB -> was supposed to hold root for -current >> ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable >> ad0s4 -> ditto for -current > >You are getting bit by the "root" aliasing code (IIRC this is the >right way to describe the problem). This makes it impossible to >install multiple copies of FreeBSD on a single disk w/o hacking >around the system. :-( While I understand the steps you described, it seems to me we should be able to come up with an easier way to do this. What you described is probably quite straightforward to you, but that's because you're already familiar with all the programs you're referring to, and you've worked with them long enough that it's all second-nature to you. Me, I'm hoping to do the installs I want to do without having to become as much of an expert... :-) I think there should be a way to do this which does not require quite so many steps, and so much flip-flopping between programs. The tactic I described in the other thread was ALMOST easy, if I had just understood a little more of what was going on. And I suspect that with a few changes [somewhere...], we could make that strategy work without having to change the type of slices, or having to run diskedit to rename partitions within the slices we've created. >Now install -current in the normal way. When you enter the slice >editor you will see that all is as you want it. In my situation, I had the 4.3-release CD at home, and a very slow network connection. So, "the normal way" for me to install current is to install 4.3 first, and then use cvsup & buildworld to get to 5. I don't know how normal that would seem to other people, but given that that is how I intended to do it, then I just have this feeling that there should be some easier way to get thru the sysinstall/disklabel issues without becoming an expert with renaming partition types, etc. obviously I need to learn a bit more and do a little more thinking before I can say exactly what that "easier way" is, but I do think it's possible... -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel module options Was: Re: Fw: help me!!!!
On Fri, 20 Jul 2001, Mike Smith wrote: > > 3) Steal an idea from Linux (gasp!), and have module dependencies. ie, > >load ipfw.ko and then before we load up natd, we check to see if > >ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko > >(before loading ipfw.ko), will automagically load ipfw.ko since ipfw is > >needed to get divert running. > > We've had this support for a long time already; module authors just > aren't taking advantage of it. Is this documented anywhere? If so, can you toss a pointer? I'd be interested in learning a little kernel hacking, and I can't imagine this would be *that* hard to implement. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Suggestions for sysinstall / disklabel
At 9:27 PM -0700 7/20/01, David O'Brien wrote:
>On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote:
>> Now, remember that during the boot-up process, the "boot0" code requires
>> that the "partition to boot from" be the first partition in the slice.
>> The "boot1" code assumes that the "partition to boot from" is labelled
>> "partition a". So, that partition which I will want to be "/ for
>> release 5" needs to be both the first partition in the slice, and it
>> needs to be labelled "partition a".
>
>That is not true. You can put `b' at the beginning of the slice (what
>I think you mean by "first partition"), followed by `a' and the result
>boots just fine. [this is for i386 only!, this is not true for the Alpha]
Oh. But that is only an option for the swap partition, not some other
UFS partition? Right? I'm still a little fuzzy on how these parts fit
together. So boot0 just looks for the first UFS partition in the slice
you selected, and assumes it is root?
> > Why does disklabel make it "partition e"? Because it knows that it
>> should use "partition a" for the partition which will be mounted
>> as "/".
>
>You did a lot of extra work to undo this. Just let sysinstall make
>it `e' and do your normal install. Then boot into your 4.3 and run
>disklabel da0s3 (or ad0s3). Go to the `e' and change it to `a' and
>save the label. Edit /etc/fstab and change the da0s3e to da0s3a.
Yeah. Eventually I figured that out. I am not one to casually run
disklabel to change partition names on an already-running system (in
fact, this was the first time I have ever run disklabel directly).
>Or better yet, don't create anything within the da0s3 slice -- leave that
>to when you install -current in that slice. See my other email I just
>sent for instructions around the next problem sysinstall will give you.
I "needed" to create partitions in both slices for stable, due to the
way I wanted to set things up. And I intended to install 4.3, update
to stable, copy the 4.3-specific {/,/var,/usr} to the /x5 equivalent
partitions (if you remember my naming scheme), and then update THAT
to turn it into current. So, I did really want stable to come up with
all of the partitions (both stable and current) that I defined.
> > Anyway, the above is a long-winded justification for the following
>> suggestions:
>> 1) if disklabel has already been told about '/', then it
>> should not try and reserve partition 'a' of OTHER SLICES
>> to also be '/'. The first partition created in those
>> other slices should just be labelled partition 'a'.
>
>I don't want my data partition in say sd0s4 to be `a'. `a' implies
>root. So your suggestion will irritate some.
But if "you" (meaning the "user doing the install") are creating a
data partition in a "second slice", doesn't that pretty much imply
that it can't possibly be root?[note that I don't have a long
history of formatting unix partitions, so it wouldn't surprise me
if I am suggesting things which seem weird to people with a longer
history in bsd's].
[I'm not sure I made this obvious in my previous message, but these
suggestions were meant for the situation where the user is doing a
single install where they are spraying freebsd slices across multiple
partitions -- as was in the case in the example I gave]
In any case, sysinstall already will create 'a' partitions which
are not "root", if you just ask it to create enough of them that
it has run out of letters. Why should I care if it irritates
"some" people if I what to use partition 'a' on a second slice
as /home? It's my disk, it works, it does not break anything.
[or does it?]
> > 2) similarly, if it already has swap space defined, then
> > it should not try to reserve partition 'b' of other
>> slices to be swap. The second partition defined in
>> those other slices should be labelled partition 'b'.
>
>What is wrong with having more than one slice with swap in it?
>Nothing.
Er, yeah. I do agree. I think I forgot some extra sentence in this
suggestion, because I meant that to sound more like an "there should
be a way that a user could tell sysinstall", and not that "sysinstall
should never reserve 'b' for swap". At the time I was writing this
I did mean to allow for swap partitions in multiple slices, although
in my specific case I (personally, on my disk) knew that I only wanted
one swap partition. I wanted disklabel to let me name things "the way
I wanted", instead of "the way it thinks is good for me".
>Of course I don't really know what you mean by "second partition
>defined". Sysinstall orders the location of the [BSD] partitions within
>the slice in the order you create the [BSD] partitions. Sysinstall also
>knows that swap is always `b' and root is always `a'. Sysinstall skips
>`d' because `d' used to mean the entire disk in pre-2.2.6. (`d' would
>behave how others coming from non-PC Unixes would expect `c'
Re: arcnet support for FreeBSD (request for review)
In message <[EMAIL PROTECTED]> Julian Elischer writes: : what is arcnet? Old, pre-ethernet technology. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Suggestions for sysinstall / disklabel
On Thu, Jul 19, 2001 at 05:29:10PM -0400, Garance A Drosihn wrote: > Now, remember that during the boot-up process, the "boot0" code requires > that the "partition to boot from" be the first partition in the slice. > The "boot1" code assumes that the "partition to boot from" is labelled > "partition a". So, that partition which I will want to be "/ for > release 5" needs to be both the first partition in the slice, and it > needs to be labelled "partition a". That is not true. You can put `b' at the beginning of the slice (what I think you mean by "first partition"), followed by `a' and the result boots just fine. [this is for i386 only!, this is not true for the Alpha] > Why does disklabel make it "partition e"? Because it knows that it > should use "partition a" for the partition which will be mounted > as "/". You did a lot of extra work to undo this. Just let sysinstall make it `e' and do your normal install. Then boot into your 4.3 and run disklabel da0s3 (or ad0s3). Go to the `e' and change it to `a' and save the label. Edit /etc/fstab and change the da0s3e to da0s3a. Or better yet, don't create anything within the da0s3 slice -- leave that to when you install -current in that slice. See my other email I just sent for instructions around the next problem sysinstall will give you. > Anyway, the above is a long-winded justification for the following > suggestions: > 1) if disklabel has already been told about '/', then it > should not try and reserve partition 'a' of OTHER SLICES > to also be '/'. The first partition created in those > other slices should just be labelled partition 'a'. I don't want my data partition in say sd0s4 to be `a'. `a' implies root. So your suggestion will irritate some. > 2) similarly, if it already has swap space defined, then > it should not try to reserve partition 'b' of other > slices to be swap. The second partition defined in > those other slices should be labelled partition 'b'. What is wrong with having more than one slice with swap in it? Nothing. Of course I don't really know what you mean by "second partition defined". Sysinstall orders the location of the [BSD] partitions within the slice in the order you create the [BSD] partitions. Sysinstall also knows that swap is always `b' and root is always `a'. Sysinstall skips `d' because `d' used to mean the entire disk in pre-2.2.6. (`d' would behave how others coming from non-PC Unixes would expect `c' to behave) So you'll have to change your wording to be a little more exact for others to follow your proposal. > Thinking about what people said about alpha installs, perhaps the > following is another strategy disklabel could take. On the other > hand, this may cause as many problems as it tries to solve. > > 4) never reserve 'a' or 'b'. Always create partitions in the > order people typed them in, except that WHEN someone says > they want to create '/', THEN both move that partition > to the front of the slice and name it 'a' (renaming other > partitions as needed). NO! Many want to put swap at the "beginning" of the disk as that is the fastest part of the disk. The i386 has no problems booting from a partition that is not located at the beginning of the disk(slice). The problem with the Alpha is people try the same "trick", but it does not work. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting -stable & -current
On Fri, Jul 20, 2001 at 06:32:29PM +0200, Wilko Bulte wrote: > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current You are getting bit by the "root" aliasing code (IIRC this is the right way to describe the problem). This makes it impossible to install multiple copies of FreeBSD on a single disk w/o hacking around the system. :-( The way to do this, is 1st install -stable. Create all four slices in the disk slice editor. In the label editor, do your normal thing, but don't bother doing anything with ad0s2. Continue with install as usual. Boot again from CDROM or floppies and enter the slice editor. Change the partition type of ad0s1 from 165 (FreeBSD FFS) to something else. Write this change to disk and exit from sysinstall. Now install -current in the normal way. When you enter the slice editor you will see that all is as you want it. Make sure you choose easyboot vs. leaving the MBR alone or choosing "standard". You should now be able to create your -current root on ad0s2 and mount the partitions on ad0s3 and ad0s4 (change flag to not newfs them of course). Continue install as usual. Reboot using CDROM or floppies, enter slice editor and set the partition type of ad0s1 back to "165". Write changes, exit, reboot and do your F1 / F2 choice from booteasy. You might be able to optimize the number of times booting from CDROM to change the partition type of ad0s1. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
jmp after setting PE?
Hi, Please forgive me if this seems too easy. "http://people.freebsd.org/~jhb/386htm/s10_03.htm"; says: Immediately after setting the PE flag, the initialization code must flush the processor's instruction prefetch queue by executing a JMP instruction. The 80386 fetches and decodes instructions and addresses before they are used; however, after a change into protected mode, the prefetched instruction information (which pertains to real-address mode) is no longer valid. A JMP forces the processor to discard the invalid information. "/home/src/sys/i386/i386" says: 329 /* Now enable paging */ 330 movlR(_IdlePTD), %eax 331 movl%eax,%cr3 /* load ptd addr into mm 332 movl%cr0,%eax /* get control word */ 333 orl $CR0_PE|CR0_PG,%eax /* enable paging */ 334 movl%eax,%cr0 /* and let's page NOW! * 335 336 #ifdef BDE_DEBUGGER 337 /* 338 * Complete the adjustments for paging so that we can keep tracing throu 339 * initi386() after the low (physical) addresses for the gdt and idt bec 340 * invalid. 341 */ 342 callbdb_commit_paging 343 #endif 344 345 pushl $begin /* jump to high virtuali 346 ret My question is "where is the "jmp" instruction which is supposed to immediately follow the instruction setting PE? Or do I miss anything? Thanks Weiguang PS. I am looking at 4.3 stable. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
On Fri, Jul 20, 2001 at 02:54:11PM -0400, Bill Moran wrote: > > My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy > > and this is why this is happening. Joy. > > I don't know. If it's coming from some eGroup, why is it originating at what > looks like a dialup address, and running through Earthling? > Looks like SPAM to me. It's not coming from eGroups. -- Bill Fumerola / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting -stable & -current
Wilko Bulte <[EMAIL PROTECTED]> types: > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > to go current from there). If you've already got -stable installed on ad0s1, why not mount the -current partitions on your -stable system, and then build and install those on -current? I just did mine that way to begin with, and thus avoided any problems with sysinstall. If you're tight on disk space - though it doesn't look like you are - you can save a bit by using the same swap partition for both systems. http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
MFC FFS dirpref code?
could anyone think about MFC FFS dirpref code? is it still not enough stable in CURRENT? I heard OpenBSD 2.9 has it already. __ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dual booting -stable & -current
At 9:32 PM +0200 7/20/01, Thierry Herbelot wrote: >Wilko Bulte wrote: >> >> I'm probably completely dim today so please bear with me :/ >> Thing is I want to setup a dual-boot box, running -stable & -current. >> This box, a P2/266 has a 30G IDE disk. >> >> What I did is create >> ad0s1 -> 256MB -> holds root for -stable >> ad0s2 -> 256MB -> was supposed to hold root for -current >> ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable >> ad0s4 -> ditto for -current >> >> My recollection is that as long as you keep the root partitions <2 (or 8) GB >> it should be bootable. Hence this somewhat strange slicing. >> >> Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want >> to go current from there). >> > > I'm probably missing something obvious here? Somehow I missed the beginning of this thread. I suspect you're running into the same issue I recently described in a message in the thread on "Suggestions for sysinstall / disklabel" in -hackers. I think I sent it in the last two or three days. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Official America's Cup Jubilee Announcement
WASHINGTON PROMOTIONS INTERNATIONAL HONORED BY THE AMERICA'S CUP JUBILEE 2001 The America's Cup Jubilee Governing Committee in Cowes, United Kingdom has selected Washington Promotions International as the official U.S.A. merchandise licensee for the 150th Anniversary of the America's Cup. Please visit this web site to see the array of clothing, compasses, barometers and other commemorative items. http://wpi2001.com/index2.html Individuals, yacht and sailing clubs, and corporations everywhere, currently have the opportunity to acquire special items with ACJ2001 logo. Additionally, you may also choose to add your own logo to these fine items. This is a once in a lifetime opportunity to celebrate an event of this caliber and prestige. Please post to your newsletter or bulletin board. If you have any questions contact: Vassil C. Yanco (281)292-9810 Office (281)292-9331 Fax E-mail: [EMAIL PROTECTED] Web Site: http://wpi2001.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compaq DL380
> > I need to MFC changes in ida driver, which start backround > > firmware processing on Integrated SmartArray controllers > > (this allows automatic on-line rebuild of failed drives). > > > > I am going to do it in next few days. I understood that I shall > > avoid all changes for interrupt-entropy harvesting. > > > > Is there something more I shall avoid ? > > No, other than the buf/bio changes make the diffs harder to read. If you wanted to try to keep the two unified, there are macros in a few of my drivers that hide these. They're ugly, but they work. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compaq DL380
This sounds great; nothing else I can think of. Compaq are happy about this. 8) > I need to MFC changes in ida driver, which start backround > firmware processing on Integrated SmartArray controllers > (this allows automatic on-line rebuild of failed drives). > > I am going to do it in next few days. I understood that I shall > avoid all changes for interrupt-entropy harvesting. > > Is there something more I shall avoid ? > > Thanks in advance, > Milon > -- > [EMAIL PROTECTED] > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hardware" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: interface cloning MFC
On Sat, Jul 21, 2001 at 12:29:13AM +0100, Brian Somers wrote: > This works nicely on my -stale box. Thanks. > > One niggle though :) It's probably worth changing > ``$FreeBSD: $'' to ``$FreeBSD$'' in your patched version. > Without this, mergemaster assumes that the new version in /usr/src/etc > is the same as the /etc version (same Ids). This caused a problem > here, I fixed the problem and went to prepare a patch for you the > patch file came up empty -- you already had the missing ``create'' in > your patches (of course) :*D I've updated the patch again. I'd run into that problem but didn't think to just unexpand the $FreeBSD$ and then promptly forgot about it. Thanks, Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: interface cloning MFC
> I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. > > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff > > apply with: > > cd /usr/src > mkdir sys/modules/if_gif sys/modules/if_stf > patch < gif-stable.diff > > -- Brooks This works nicely on my -stale box. Thanks. One niggle though :) It's probably worth changing ``$FreeBSD: $'' to ``$FreeBSD$'' in your patched version. Without this, mergemaster assumes that the new version in /usr/src/etc is the same as the /etc version (same Ids). This caused a problem here, I fixed the problem and went to prepare a patch for you the patch file came up empty -- you already had the missing ``create'' in your patches (of course) :*D Cheers. -- 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-hackers" in the body of the message
Re: dual booting -stable & -current
On Fri, Jul 20, 2001 at 09:32:48PM +0200, Thierry Herbelot wrote: > Wilko Bulte wrote: > > > > I'm probably completely dim today so please bear with me :/ > > Thing is I want to setup a dual-boot box, running -stable & -current. > > This box, a P2/266 has a 30G IDE disk. > > > > What I did is create > > ad0s1 -> 256MB -> holds root for -stable > > ad0s2 -> 256MB -> was supposed to hold root for -current > > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > > ad0s4 -> ditto for -current > > > > My recollection is that as long as you keep the root partitions <2 (or 8) GB > > it should be bootable. Hence this somewhat strange slicing. > > > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > > to go current from there). > > > > I'm probably missing something obvious here? > > here's what I have on my (just -Stable for the moment) workstation : > multi# fdisk ad4 > *** Working on device /dev/ad4 *** > parameters extracted from in-core disklabel are: > cylinders=35390 heads=16 sectors/track=63 (1008 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: ... > you may want to use a similar setup (with larger bootable partitions : > my setup was initially one only 2G partition, but I cut it this way, > with a shared swap to be able to dual-boot) But does your system boot from the 'second' FreeBSD installation? > PS : I also had problems with a 40G disk on my oldish P-II/266 : it > would not boot from the large disk (I just added a spare 8G which I boot > from) Hmmm. Wilko [who remembers why all his other systems are SCSI.. ] -- | / o / / _ Arnhem, The Netherlands email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Status of agpgart device
For the i440BX, it should be fully operational and work just exactly like the linux counterpart. You shouldn't need the agpgart tarball, it sohuld work (but only in XFree86 3.3.6). XFree86 4.x uses DRI exclusively. If you want to use that, you should visit dri.sourceforge.net. On Fri, Jul 20, 2001 at 01:26:03AM -0700, Farooq Mela wrote, and it was proclaimed: > Hi, > > Right, I've already got that: > > agp0: mem > 0xf800-0xfbff at device 0.0 on pci0 > > That still doesnt answer my question about the agpgart (AGP > g-something address resolution table, or something similar - needed > for high-performance memory transfers). > > -- Coleman Kane wrote: > > > > 4.3-RELEASE comes with an agp device. Simply add agp_load="YES" to your > > /boot/loader.conf file, or device agp to your kernel config file. It > > only supports certain AGP bridges though, look in /usr/src/sys/pci/agp* > > for more info. > > > > On Thu, Jul 19, 2001 at 04:48:00PM -0700, Farooq Mela wrote, and it was proclaimed: > > > Hi hackers@, > > > > > > What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE > > > with a recent cvsup). Is it working, perhaps using a compatible > > > interface with the linux device the of the same name (I can dream > > > can't I ;-) ? I ask because I recently tried compiling Utah-GLX with > > > AGP acceleration support, and it requires a /dev/agpgart device, but > > > the testgart program errors out when it tries to ioctl the agpgart > > > device. > > > > > > The Utah-GLX website all provides a tarball > > > (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-2619.tar.gz) > > > which includes a FreeBSD agpgart driver (as a KLD), but it fails to > > > compile. I believe it was for the FreeBSD 3.x series, and has tons of > > > compile errors. The documentation for the driver also states the as > > > part of the installation, a /dev/agpgart must be built, yet I already > > > had a /dev/agpgart device. This leads me to believe this driver is a > > > bit antiquated. > > > > > > Any ideas? > > > > > > -- > > > farooq <[EMAIL PROTECTED]> > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > -- > >Part 1.2Type: application/pgp-signature > > farooq <[EMAIL PROTECTED]> > PGP signature
Re: Default retry behaviour for mount_nfs
In message <[EMAIL PROTECTED]>, Terry Lambert writes: >> FWIW, I vote that we rever to the traditional default and require >> -R1 or -b to avoid boot time hangs. The standard behaviour for most >> NFS implementations that I'm aware of would do this. > >I agree; people at work have bitched about this. We have a >FreeBSD NFS server that's flakey. Ok, from the small set of responses so far, it seems that the most acceptable option is to change mount_nfs to behave in the old way where it will retry forever by default even in foreground mode. Below is a proposed patch that does this. It also adds two paragraphs near the start of the manpage which describe the default behaviour and point readers at the relevant options. Comments welcome. >The other thing is that it appears to break amd behaviour. Does amd use mount_nfs(8)? I thought it did the mount syscalls directly. Ian Index: mount_nfs.8 === RCS file: /dump/FreeBSD-CVS/src/sbin/mount_nfs/mount_nfs.8,v retrieving revision 1.27 diff -u -r1.27 mount_nfs.8 --- mount_nfs.8 2001/07/19 21:11:48 1.27 +++ mount_nfs.8 2001/07/20 22:20:35 @@ -71,6 +71,28 @@ .%T "NFS: Network File System Version 3 Protocol Specification" , Appendix I. .Pp +By default, +.Nm +keeps retrying until the mount eventually succeeds. +This behaviour is intended for filesystems listed in +.Xr fstab 5 +that are critical to the boot process. +For non-critical filesystems, the +.Fl R +and +.Fl b +flags provide mechanisms to prevent the boot process from hanging +if the server is unavailable. +.Pp +If the server becomes unresponsive while an NFS filesystem is +mounted, any new or outstanding file operations on that filesystem +will hang uninterruptibly until the server comes back. +To modify this default behaviour, see the +.Fl i +and +.Fl s +flags. +.Pp The options are: .Bl -tag -width indent .It Fl 2 @@ -126,12 +148,8 @@ help, but for normal desktop clients this does not apply.) .It Fl R Set the mount retry count to the specified value. -A retry count of zero means to keep retrying forever. -By default, -.Nm -retries forever on background mounts (see the -.Fl b -option), and otherwise tries just once. +The default is a retry count of zero, which means to keep retrying +forever. There is a 60 second delay between each attempt. .It Fl T Use TCP transport instead of UDP. Index: mount_nfs.c === RCS file: /dump/FreeBSD-CVS/src/sbin/mount_nfs/mount_nfs.c,v retrieving revision 1.45 diff -u -r1.45 mount_nfs.c --- mount_nfs.c 2001/07/19 21:11:48 1.45 +++ mount_nfs.c 2001/07/20 21:37:19 @@ -486,7 +486,8 @@ name = *argv; if (retrycnt == -1) - retrycnt = (opflags & BGRND) ? 0 : 1; + /* The default is to keep retrying forever. */ + retrycnt = 0; if (!getnfsargs(spec, nfsargsp)) exit(1); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: arcnet support for FreeBSD (request for review)
On Thu, 19 Jul 2001, Julian Elischer wrote: > probably no committers had arcnet or could test it.. I have it and tried to test it last time with no success. I'll try and find some time to look at this stuff. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NETBIOS Browsing?
At 2:45 PM -0700 7/20/01, Alexander Langer wrote: >Ouch, I should actually read more carefully what you were asking, >sorry. > >I guess smbfs doesn't help you here (don't know if it actually >browses, but at least it's SMB stuff) Extending smbfs with browsing is exactly what I wish to do. -- Conrad Minshall ... [EMAIL PROTECTED] ... 408 974-2749 Alternative email addresses: [EMAIL PROTECTED] and [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NETBIOS Browsing?
At 2:44 PM -0700 7/20/01, Alexander Langer wrote: >> Does anyone know of any code which would help in browsing a Windows >> "Network Neighbourhood"? Something which would make broadcasts to find all >> the netbios name servers, and then query them to discover more. Code from >> Samba's "nmblookup" would be fine but it is GPL. > >xsmbrowser is a GREAT tools, which is even better than Microsofts >Network Neighbourhood. I use it to browser our LAN with 200+ PCs >and it's very comfortable (and has less bugs than M$' crap) Thank you. I should have mentioned"xsmbrowser". Unfortunately it is GPL and uses Samba (also GPL). ...bcc to the author of xsmbrowser -- Conrad Minshall ... [EMAIL PROTECTED] ... 408 974-2749 Alternative email addresses: [EMAIL PROTECTED] and [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NETBIOS Browsing?
Ouch, I should actually read more carefully what you were asking, sorry. I guess smbfs doesn't help you here (don't know if it actually browses, but at least it's SMB stuff) Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: NETBIOS Browsing?
Thus spake Conrad Minshall ([EMAIL PROTECTED]): > Does anyone know of any code which would help in browsing a Windows > "Network Neighbourhood"? Something which would make broadcasts to find all > the netbios name servers, and then query them to discover more. Code from > Samba's "nmblookup" would be fine but it is GPL. xsmbrowser is a GREAT tools, which is even better than Microsofts Network Neighbourhood. I use it to browser our LAN with 200+ PCs and it's very comfortable (and has less bugs than M$' crap) You can find it in the ports collection. Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
NETBIOS Browsing?
Does anyone know of any code which would help in browsing a Windows "Network Neighbourhood"? Something which would make broadcasts to find all the netbios name servers, and then query them to discover more. Code from Samba's "nmblookup" would be fine but it is GPL. -- Conrad Minshall ... [EMAIL PROTECTED] ... 408 974-2749 Alternative email addresses: [EMAIL PROTECTED] and [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: interface cloning MFC
On Fri, Jul 20, 2001 at 08:37:50PM +0100, Brian Somers wrote: > > A diff is available at: > > > > http://people.freebsd.org/~brooks/patches/gif-stable.diff > > You forgot: > > Index: LINT > === > RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v > retrieving revision 1.749.2.64 > diff -u -r1.749.2.64 LINT > --- LINT 2001/06/29 21:14:24 1.749.2.64 > +++ LINT 2001/07/20 19:35:42 > @@ -509,7 +509,7 @@ > options ETHER_SNAP # enable Ethernet_802.2/SNAP frame > > # for IPv6 > -pseudo-devicegif 4 #IPv6 and IPv4 tunneling > +pseudo-devicegif #IPv6 and IPv4 tunneling > pseudo-devicefaith 1 #for IPv6 and IPv4 translation > pseudo-devicestf #6to4 IPv6 over IPv4 encapsulation Oops, I've updated the diff. I'll be committing the appropriate fix to NOTES shortly, since I forgot that in the first round. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: interface cloning MFC
> I plan to MFC the network interface cloning support and the gif > modularization early next week unless someone has objections. I'd like > to get it in before the code slush and since I'll be leaving for a week > on the 31st, that means sometime early to mid next week to allow for any > bug reports. I don't really expect any problems. Good stuff. > A diff is available at: > > http://people.freebsd.org/~brooks/patches/gif-stable.diff You forgot: Index: LINT === RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v retrieving revision 1.749.2.64 diff -u -r1.749.2.64 LINT --- LINT2001/06/29 21:14:24 1.749.2.64 +++ LINT2001/07/20 19:35:42 @@ -509,7 +509,7 @@ optionsETHER_SNAP # enable Ethernet_802.2/SNAP frame # for IPv6 -pseudo-device gif 4 #IPv6 and IPv4 tunneling +pseudo-device gif #IPv6 and IPv4 tunneling pseudo-device faith 1 #for IPv6 and IPv4 translation pseudo-device stf #6to4 IPv6 over IPv4 encapsulation I'm just rebuilding the world now :) I'll let you know how I get on. Thanks for your work. -- 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-hackers" in the body of the message
Re: dual booting -stable & -current
Wilko Bulte wrote: > > I'm probably completely dim today so please bear with me :/ > Thing is I want to setup a dual-boot box, running -stable & -current. > This box, a P2/266 has a 30G IDE disk. > > What I did is create > ad0s1 -> 256MB -> holds root for -stable > ad0s2 -> 256MB -> was supposed to hold root for -current > ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable > ad0s4 -> ditto for -current > > My recollection is that as long as you keep the root partitions <2 (or 8) GB > it should be bootable. Hence this somewhat strange slicing. > > Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want > to go current from there). > > I'm probably missing something obvious here? here's what I have on my (just -Stable for the moment) workstation : multi# fdisk ad4 *** Working on device /dev/ad4 *** parameters extracted from in-core disklabel are: cylinders=35390 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 2457441 (1199 Meg), flag 0 The data for partition 2 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 4095504, size 31577616 (15418 Meg), flag 0 he data for partition 3 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 2457504, size 1638000 (799 Meg), flag 80 (active) The data for partition 4 is: // main bootable partition multi# disklabel -r ad4s1 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 10240004.2BSD 1024 819216 on / b: 860160 102400 swap shared swap c: 24574410unused0 0 e:40960 9625604.2BSD 1024 819216 on /var f: 1453921 10035204.2BSD 1024 819216 on /usr // alternate bootable partition (will be -Current) multi# disklabel -r ad4s3 #size offsetfstype [fsize bsize bps/cpg] a: 10240004.2BSD 1024 819216 on alternate / c: 16380000unused0 0 e:40960 1024004.2BSD 1024 819216 alt. /var f: 1494640 1433604.2BSD 1024 819216 alt. /usr multi# disklabel -r ad4s2 #size offsetfstype [fsize bsize bps/cpg] c: 315776160unused0 0 e: 3157761604.2BSD0 0 0 shared expanse you may want to use a similar setup (with larger bootable partitions : my setup was initially one only 2G partition, but I cut it this way, with a shared swap to be able to dual-boot) PS : I also had problems with a 40G disk on my oldish P-II/266 : it would not boot from the large disk (I just added a spare 8G which I boot from) -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Compaq DL380
On Fri, Jul 20, 2001 at 09:07:00PM +0200, Milon Papezik wrote: > Hi all, > > I need to MFC changes in ida driver, which start backround > firmware processing on Integrated SmartArray controllers > (this allows automatic on-line rebuild of failed drives). > > I am going to do it in next few days. I understood that I shall > avoid all changes for interrupt-entropy harvesting. > > Is there something more I shall avoid ? No, other than the buf/bio changes make the diffs harder to read. -- Jonathan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
RE: Compaq DL380
Hi all, I need to MFC changes in ida driver, which start backround firmware processing on Integrated SmartArray controllers (this allows automatic on-line rebuild of failed drives). I am going to do it in next few days. I understood that I shall avoid all changes for interrupt-entropy harvesting. Is there something more I shall avoid ? Thanks in advance, Milon -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
interface cloning MFC
I plan to MFC the network interface cloning support and the gif modularization early next week unless someone has objections. I'd like to get it in before the code slush and since I'll be leaving for a week on the 31st, that means sometime early to mid next week to allow for any bug reports. I don't really expect any problems. A diff is available at: http://people.freebsd.org/~brooks/patches/gif-stable.diff apply with: cd /usr/src mkdir sys/modules/if_gif sys/modules/if_stf patch < gif-stable.diff -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
Matthew Jacob wrote: > > My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy > and this is why this is happening. Joy. I don't know. If it's coming from some eGroup, why is it originating at what looks like a dialup address, and running through Earthling? Looks like SPAM to me. -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
My guess, fwiw, is that somebody subscribed freebsd-hackers to some eGroup toy and this is why this is happening. Joy. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
He's saying "Huh?" and presumably 'looking into it'. On Fri, 20 Jul 2001, Bill Moran wrote: > Are you saying that he didn't even send them? > > Matthew Jacob wrote: > > > > No. Peter Pflaum responded when I asked him with a "Quoi???!?!?!?!" > > > > On Fri, 20 Jul 2001, Bill Moran wrote: > > > > > Does anyone have any explanation as to why this is coming through -hackers? > > > > > > > Peter Pflaum wrote: > > > > > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > > > > > BBC News TALKING POINT Globalisation Good or bad > > > > > > > >Name: BBC News >TALKING POINT Globalisation Good or bad.url > > > >BBC News TALKING POINT Globalisation Good or bad.urlType: unspecified >type (application/octet-stream) > > > >Encoding: >quoted-printable > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
Are you saying that he didn't even send them? Matthew Jacob wrote: > > No. Peter Pflaum responded when I asked him with a "Quoi???!?!?!?!" > > On Fri, 20 Jul 2001, Bill Moran wrote: > > > Does anyone have any explanation as to why this is coming through -hackers? > > > > > Peter Pflaum wrote: > > > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > > > BBC News TALKING POINT Globalisation Good or bad > > > > > >Name: BBC News >TALKING POINT Globalisation Good or bad.url > > >BBC News TALKING POINT Globalisation Good or bad.urlType: unspecified >type (application/octet-stream) > > >Encoding: quoted-printable > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
No. Peter Pflaum responded when I asked him with a "Quoi???!?!?!?!" On Fri, 20 Jul 2001, Bill Moran wrote: > Does anyone have any explanation as to why this is coming through -hackers? > > > Peter Pflaum wrote: > > > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > > > BBC News TALKING POINT Globalisation Good or bad > > > >Name: BBC News TALKING >POINT Globalisation Good or bad.url > >BBC News TALKING POINT Globalisation Good or bad.urlType: unspecified type >(application/octet-stream) > >Encoding: quoted-printable > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Pflaum on BBC News TALKING POINT Globalisation Good or bad
Does anyone have any explanation as to why this is coming through -hackers? > Peter Pflaum wrote: > > I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast > > http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm > > BBC News TALKING POINT Globalisation Good or bad > >Name: BBC News TALKING >POINT Globalisation Good or bad.url >BBC News TALKING POINT Globalisation Good or bad.urlType: unspecified type >(application/octet-stream) >Encoding: quoted-printable To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Pflaum on BBC News TALKING POINT Globalisation Good or bad
I will be on this program Sunday at 10 - 11 AM on BBC - it is a webcast http://newsvote.bbc.co.uk/hi/english/talking_point/newsid_1444000/1444930.stm BBC News TALKING POINT Globalisation Good or bad BBC News TALKING POINT Globalisation Good or bad.url
Re: [OT] POLA? (was Re: Default retry behaviour for mount_nfs)
On Fri, 20 Jul 2001, Matthew Jacob wrote: > > I'll leave it up to you all to imagine what 'wtf WTF' is. > We all know it stands for "what's that for?"... :) Laurence Berland http://www.isp.northwestern.edu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Finding something useful - Among the protesters
The protest is a good example of Globalization - "What is happening now hasn't happened since the anti-Vietnam war protests of the 1960s," he told me. "Young people from around the globe are coming together to campaign for economic justice - and our movement is growing." BBC News BUSINESS Among the protesters She says the protests are as much about cultural as economic concerns, and praises the "radical street warriors" for showing the world that you cannot dehumanise people and for "reclaiming our most human desires." It is important to understand the social psychological base for the protest. These people feel left out - big means less individual feeling of participation, of being part of the whole. A global peace corps and person-to-person contacts to help people feel global - part of a larger humanity. There should be ways of redirecting all this energy into productive activity - conflict resolution - social services - projects in the poor world building practical projects - maybe financed by the world bank - a IMF / world bank international youth corps in health, education, economic development would be a good start. BBC News BUSINESS Among the protesters.url
Re: [OT] POLA? (was Re: Default retry behaviour for mount_nfs)
Bill Moran wrote: > > > > > Sometimes the stick of POLA should be broken. > > Off topic, I know, but it's going to bother me. > > What's POLA? Policy Of Least Astonishment -- doing changes in a way which will annoy the least number of users. HTH -Christoph Sold To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: [OT] POLA? (was Re: Default retry behaviour for mount_nfs)
'Principle of Least Astonishment' and something we should import from NetBSD: pilt > uname -a NetBSD pilt 1.5.1_ALPHA NetBSD 1.5.1_ALPHA (PILT) #5: Thu Feb 8 12:01:03 PST 2001 mjacob@pilt:/export/src/NetBSD-1.5/syssrc/sys/arch/i386/compile/PILT i386 pilt > /usr/games/wtf POLA POLA: principle of least astonishment pilt > /usr/games/wtf IIRC IIRC: if I recall correctly I'll leave it up to you all to imagine what 'wtf WTF' is. On Fri, 20 Jul 2001, Bill Moran wrote: > > > > > Sometimes the stick of POLA should be broken. > > Off topic, I know, but it's going to bother me. > > What's POLA? > > -Bill > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
[OT] POLA? (was Re: Default retry behaviour for mount_nfs)
> > > Sometimes the stick of POLA should be broken. Off topic, I know, but it's going to bother me. What's POLA? -Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Default retry behaviour for mount_nfs
Matthew Jacob wrote: > > Hmm, maybe we should implement the notion of "critical_local" and > > "critical_net" filesystems (a la NetBSD). Heck, I don't even need the > > distinction between net and local, just critical would do. All remote, > > critical filesystems would be blocking, and all others not. > > > > Sometimes the stick of POLA should be broken. > > Not if it adds work. I think the non-critical ones are the ones with the "-R1" option set... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
dual booting -stable & -current
I'm probably completely dim today so please bear with me :/ Thing is I want to setup a dual-boot box, running -stable & -current. This box, a P2/266 has a 30G IDE disk. What I did is create ad0s1 -> 256MB -> holds root for -stable ad0s2 -> 256MB -> was supposed to hold root for -current ad0s3 -> roughly 14G holds tmp,var,usr,usr/obj for -stable ad0s4 -> ditto for -current My recollection is that as long as you keep the root partitions <2 (or 8) GB it should be bootable. Hence this somewhat strange slicing. Thing is, 4.3R refuses to install it's root on ad0s2 (4.3 because I want to go current from there). I'm probably missing something obvious here? -- | / o / / _ Arnhem, The Netherlands email: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte "Youth is not a time in life, it is a state of mind" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Default retry behaviour for mount_nfs
> Matthew Jacob wrote: > > > So the question is - should I keep the new behaviour that is probably > > > a better default and will catch out fewer new users but may surprise > > > some experienced users, or should I revert to the traditional > > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > > > > Sorry- let me be clearer: > > > > FWIW, I vote that we rever to the traditional default and require > > -R1 or -b to avoid boot time hangs. The standard behaviour for most > > NFS implementations that I'm aware of would do this. > > I agree; people at work have bitched about this. We have a > FreeBSD NFS server that's flakey. > > The other thing is that it appears to break amd behaviour. > > (I couldn't tell which of the two questions he was voting > in favor of, either, since there is one before the "or" and > one after). That's why I submitted a followup after Ian poked me. It's funny- I tend to think of myself as being totally transparent. Why should I need to explain what I meant then? :-) -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Default retry behaviour for mount_nfs
Matthew Jacob wrote: > > So the question is - should I keep the new behaviour that is probably > > a better default and will catch out fewer new users but may surprise > > some experienced users, or should I revert to the traditional > > default where `-R1' or `-b' are required to avoid boot-time hangs? > > > > Sorry- let me be clearer: > > FWIW, I vote that we rever to the traditional default and require > -R1 or -b to avoid boot time hangs. The standard behaviour for most > NFS implementations that I'm aware of would do this. I agree; people at work have bitched about this. We have a FreeBSD NFS server that's flakey. The other thing is that it appears to break amd behaviour. (I couldn't tell which of the two questions he was voting in favor of, either, since there is one before the "or" and one after). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gigabit card drivers
On Fri, 20 Jul 2001, MJL wrote: > Does 4.3 version support 3com or d-link's gigabit > ethernet card? Yes, I've a system running perfectly with a 3Com 3c985-SX gigabit card. Regards Konrad Konrad HeuerPersonal Bookmarks: Gesellschaft für wissenschaftliche Datenverarbeitung mbH GÖttingen http://www.freebsd.org Am Faßberg, D-37077 GÖttingen http://www.daemonnews.org Deutschland (Germany) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
gigabit card drivers
Does 4.3 version support 3com or d-link's gigabit ethernet card? == WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: flock/pthread bug?
Peter Pentchev wrote: > I don't know if Terry was talking about the sched_yield() syscall, > but if he was, then sched_yield(2) exists, at least in 4.x, and is > documented as POSIX-compliant. No. He needs to yield the system CPU, not the CPU for his particular thread. In the user space threads library scheduler, you will just be yielding to another thread. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kernel malloc
On Fri, Jul 20, 2001 at 10:17:20AM +0100, vishwanath pargaonkar wrote: > Hi, > > can any one please help me with this. i want allocate > a memory in the kernel -a buffer of size 2k to 5k. > can i do it using malloc with second parameter as > M_TEMP and third as M_WAITOK. > > can anybody tell me what M_TEMP means .what is maximum > malloc i can do with M_TEMP? > will the OS allow me to malloc 4k buffer in side > kernel??shd i give M_WAITOK or M_DONTWAIT??? M_TEMP is merely there for statistics gathering. If you're writing a subsystem and plan to malloc() a lot of things for the subsystem you may want to create your own malloc type (see malloc(9)). On another note, remember that if you allocate a 5k buffer with malloc() on x86 where the page size if 4k, that you're not guaranteed to have a physically contiguous backing. > please tell me. > thanx in advance. Regards, -- Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: CNN.com - Sen. Frist backs embryonic stem cell research - July 19, 2001
- Original Message - From: "The Rev. John Liebler" <[EMAIL PROTECTED]> To: "Peter Pflaum" <[EMAIL PROTECTED]> Sent: Thursday, July 19, 2001 10:03 PM Subject: CNN.com - Sen. Frist backs embryonic stem cell research - July 19, 2001 > These seem reasonable enough, don't they? No maybe 8 of the 10 but these rules come from transplants of the spare parts of brain dead people to others that need them. It assumes that all human living matter, protoplasm, bioplasm, ectoplasm, tissue, living tissue macromolecule, bioplast cell, unicellular organism, have a soul, spirit - true of frogs and fish and our poodles ? How about blood donors ? The problems is with No. 2 - we can use them but we can't be involved with derivation -but can use them. The goal here is to produce cells on a large scale that will replace ones that are not working - cloning of cells not people ( putting DNA from the patient into the cells so they fit better ) many cells lines need to exist because these cells reproduce endlessly while adult cells do not. BUT we can agree on this and move on. As soon as there are active treatments for major problems it can't be put back in the bottle. America is not the world and it will spread at the speed of light. I don't know how the drug companies will control cells but they will figure out a way. > > A senior aide to Frist outlined 10 conditions on which his support is based: > -- A ban on the creation of embryos for research purposes > -- A continued funding ban on "derivation," meaning federal dollars could be > spent to research embryos and stem cells only obtained through private > funding > -- A ban on human cloning > -- An increase in government funding for adult stem cell research > -- A restriction on funding for embryonic stem cell research only in the > earliest embryonic stage > -- A rigorous "informed consent" rule modeled on those now in place for > organ donation, giving donors the right to decide whether to put the embryo > up for adoption or to discard the embryo. If the donor chooses to discard > the embryo, he or she must approve the embryo's use for research. > -- A limit on the number of stem cell "lines" taken from each embryo in > order to minimize bio-ethical problems > -- A new public research oversight mechanism that would establish public > research guidelines, including a national research registry > -- An ongoing scientific and ethical review by The Institute of Medicine and > the creation of an independent presidential advisory panel to review the > bio-ethical implications of stem-cell research. The review would also > require the secretary of Health and Human Services to report to Congress > annually on the status on federal grants for stem cell research. > -- Strengthen and harmonize embryonic research restrictions to mirror fetal > tissue research restrictions > > > > > > http://www.cnn.com/2001/ALLPOLITICS/07/18/stem.cell/index.html > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Panel Argues for Changing Social Security
The Bush commission's report said the key date was 2016. That is when payroll tax revenues flowing into Social Security from workers and employers will fall short of benefit payments for the first time. At that point, the system will begin relying in part on interest payments from its vast holdings of government bonds the Social Security trust fund. But the bonds and the interest on them are nothing more than commitments by the government to help pay future benefits out of general tax revenues, meaning that Social Security will begin to impinge on the rest of the budget. http://www.nytimes.com/2001/07/20/politics/20SOCI.html Now if those "trust funds" were invested in other than IOU's from the Government to the Government they could earn more and be real. Individual accounts are much more complex - alternative investments could include foreign bonds which would help the balance of payments - Bank CD would add to domestic savings and lower interest rates , index funds are not the only investment alternative. http://www.wiredbrain.com/public-policy.htm suggests a Federal Assets Management Agency - like other pension funds. If the surplus now coming into the trust funds over the next 10 years were used to create a real reserve fund - several trillion dollars would be in the fund. It would remove the temptation to spend theses funds and have real earning (compound interest) added to them. Panel Argues for Changing Social Security.url
kernel malloc
Hi, can any one please help me with this. i want allocate a memory in the kernel -a buffer of size 2k to 5k. can i do it using malloc with second parameter as M_TEMP and third as M_WAITOK. can anybody tell me what M_TEMP means .what is maximum malloc i can do with M_TEMP? will the OS allow me to malloc 4k buffer in side kernel??shd i give M_WAITOK or M_DONTWAIT??? please tell me. thanx in advance. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Proper way for *config(8) to load corresponding modules
Most *config(8) programs, such as ifconfig(8), mdconfig(8), and ccdconfig(8), attempt to load their corresponding module if it isn't already loaded, or already compiled into the kernel. Looking at these programs, they achieve this task in (primarily) two different ways. The first uses modfind() then kldload() (e.g., see ccdconfig.c r1.19 l174). Others use a combination of kldnext(), modfnext(), and some loops to do this (e.g., see ifconfig.c r1.64 l1911). Is there any difference between these two, and which one is preferred (I'd think the former if there is no difference). It would be nice if they all did the same thing. Once it's determined which method is preferred, I'd like to propose a kldmaybeload(3) routine that takes a module name and loads it if it's not already loaded or compiled in. For now this just factors out some common code, but it may save headaches later if the kld interface is changed so that neither of these methods work without modification (with a kldmaybeload, it'd be sufficient just to modify the library function). Thanks for any insight. Dima Dorfman To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Kernel module options Was: Re: Fw: help me!!!!
> 3) Steal an idea from Linux (gasp!), and have module dependencies. ie, >load ipfw.ko and then before we load up natd, we check to see if >ipdivert.ko is loaded and load it. Alternatively, loading ipdivert.ko >(before loading ipfw.ko), will automagically load ipfw.ko since ipfw is >needed to get divert running. We've had this support for a long time already; module authors just aren't taking advantage of it. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Status of agpgart device
Hi, Right, I've already got that: agp0: mem 0xf800-0xfbff at device 0.0 on pci0 That still doesnt answer my question about the agpgart (AGP g-something address resolution table, or something similar - needed for high-performance memory transfers). -- Coleman Kane wrote: > > 4.3-RELEASE comes with an agp device. Simply add agp_load="YES" to your > /boot/loader.conf file, or device agp to your kernel config file. It > only supports certain AGP bridges though, look in /usr/src/sys/pci/agp* > for more info. > > On Thu, Jul 19, 2001 at 04:48:00PM -0700, Farooq Mela wrote, and it was proclaimed: > > Hi hackers@, > > > > What is the status of the /dev/agpgart device? (I'm running 4.3-STABLE > > with a recent cvsup). Is it working, perhaps using a compatible > > interface with the linux device the of the same name (I can dream > > can't I ;-) ? I ask because I recently tried compiling Utah-GLX with > > AGP acceleration support, and it requires a /dev/agpgart device, but > > the testgart program errors out when it tries to ioctl the agpgart > > device. > > > > The Utah-GLX website all provides a tarball > > (http://utah-glx.sourceforge.net/gart/agpgart-freebsd-2619.tar.gz) > > which includes a FreeBSD agpgart driver (as a KLD), but it fails to > > compile. I believe it was for the FreeBSD 3.x series, and has tons of > > compile errors. The documentation for the driver also states the as > > part of the installation, a /dev/agpgart must be built, yet I already > > had a /dev/agpgart device. This leads me to believe this driver is a > > bit antiquated. > > > > Any ideas? > > > > -- > > farooq <[EMAIL PROTECTED]> > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-hackers" in the body of the message > > > > -- >Part 1.2Type: application/pgp-signature farooq <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
