Re: ffs_valloc: dup alloc panics with stable/current
On Fri, Dec 08, 2000 at 03:44:28AM +0200, Tomi Vainio - Sun Finland - wrote: > sense = 3 asc = 11 asq = 0 > This is not so bad but 5-30 minutes after this command system will > always panic. Are you surprised? The system is complaining that it's having intermittent difficulty accessing the disk, so it shouldn't be at all surprising that you'd have disk corruption problems as a result. Start by checking your SCSI cabling and termination. Almost all SCSI problems boil down to that eventually. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm0: hwptr went backwards 4128 -> 4116
On Sun, Sep 10, 2000 at 09:49:24PM +0200, Szilveszter Adam wrote: > Since no one this far has reported anything like this, ... http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20731 - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ucontext
On Tue, Mar 21, 2000 at 10:54:32PM -0800, Arun Sharma wrote: > > > Before getting too far here, can we consider some other > > > standard interfaces? > > > #include > > > int getcontext(ucontext_t *ucp); > > > int setcontext(const ucontext_t *ucp); > > > void makecontext(ucontext_t *ucp, (void *func)(), int argc, ...); > > > int swapcontext(ucontext_t *oucp, const ucontext_t *ucp); > > > http://www.opengroup.org/onlinepubs/007908799/xsh/ucontext.h.html [ ... ] > Is anyone working on this ? Porting JDKs to FreeBSD would be a lot easier > if these routines are implemented. If it helps at all, these are (approxmiately :-) implemented in the svr4 emulator. I'm not sure that svr4_setcontext() is doing entirely the right thing, and there are some holes related to signal mask handling (which might be related to the "entirely the right thing" bit), but it's a start. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
On Thu, Mar 16, 2000 at 03:37:22PM -0800, Kris Kennaway wrote: > On Fri, 17 Mar 2000, Mark Newton wrote: > > > > in there. I've got all the other posix functions, though. Are > > > you using Linuxthreads? > > > > Everyone is using Linuxthreads now; it's the default. > > I didn't think so - it's still a port. We *support* linuxthreads out of > the box, but don't install it. I think we're talking about different things. There's a linuxthreads port, yes, but that's something which provides FreeBSD's compile-time environment with libraries which duplicate the Linux threading APIs. There's also the capability for Linux executables to use threads under emulation. That's there "out of the box" by default. The linuxthreads port is only necessary if you want to use "The Linux Way" of doing threads in a piece of software you're building for FreeBSD; It doesn't make much difference to emulation. [ at least, I think that's how it works -- Marcel can ping me if I'm lying :-) ] - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
On Thu, Mar 16, 2000 at 06:29:58PM -0500, Donn Miller wrote: > On Fri, 17 Mar 2000, Mark Newton wrote: > > On Thu, Mar 16, 2000 at 06:01:57PM -0500, Donn Miller wrote: > > > Hmm. Do you get video, though? Also, which plugins did you install? > > > > Yup, I get video; like I said, it's working perfectly. I just took it > > through the stock standard installation (click next -> next -> finish, > > with no other options). > > Ok, fair enough. One last question, though -- are you running XFree86 > 4.0? Nope, not yet. I haven't upgraded X in quite a while; I'm running 3.3.3. > Maybe it's something I'm lacking in my kernel config. I noticed > that I didn't have > options _KPOSIX_VERSION=199309L I do. I also have _KPOSIX_PRIORITY_SCHEDULING. > in there. I've got all the other posix functions, though. Are you using > Linuxthreads? Everyone is using Linuxthreads now; it's the default. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
On Thu, Mar 16, 2000 at 06:01:57PM -0500, Donn Miller wrote: > > I've had it working perfectly with the latest linux_base-6.1 and no > > LD_LIBRARY_PATH setting. Hasn't crashed once so far, which is rather > > unusual for products from RealNetworks! > > Hmm. Do you get video, though? Also, which plugins did you install? Yup, I get video; like I said, it's working perfectly. I just took it through the stock standard installation (click next -> next -> finish, with no other options). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RealPlayer 7
On Thu, Mar 16, 2000 at 05:35:43PM -0500, Donn Miller wrote:
> Anyone get this beast to work on -current? The audio works, but the video
> doesn't work at all. I have COMPAT_LINUX in my kernel, and RealPlayer 5.0
> works pretty well.
I've had it working perfectly with the latest linux_base-6.1 and no
LD_LIBRARY_PATH setting. Hasn't crashed once so far, which is rather
unusual for products from RealNetworks!
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Sun, Jan 30, 2000 at 02:12:45PM +1030, Greg Lehey wrote: > On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: > > Just imagine, too bad its not an 8086 or a 286 prolly take a month or so. > > I did a make world on my PDP-11 yesterday. It took less than a day. ... to parse the Makefile :-) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Solved(?): crash with ffs_softdep.c 1.52
On Mon, Jan 17, 2000 at 10:01:13PM -0800, Alex Zepeda wrote: > > Could you please explain why you need to smash a finger in a door in order > > to get a back trace?? > > The ferret was unavailable. :) Which, of course, begs the question: If you *did* have a ferret, would have have slammed it in the door, or stuck your finger in it? [ enquiring minds 'n' all that... :-) ] - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
On Wed, Jan 12, 2000 at 10:08:17AM -0800, Glendon Gross wrote: > Are there any tricks to enabling Awe64 support? I initially removed my > Awe64 card from my first FreeBSD machine to avoid interrupt conflicts, and > now I would like to try to integrate it back again. Would you mind > sending me your /sys/i386/conf/GENERIC or correct kernel build file? > Thanks! --Glen Gross The relevent bit from my kernel config is: device pcm0 :-) Way back in the dim dark ages I used to use a boot.config command which set it to "os" configuration mode and explicity configured IRQ, DRQ's and port numbers to the same values I was using in my old "controller sbc0" configuration line, but I don't need to do that anymore. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: why is my current so .... stable?
On Wed, Jan 12, 2000 at 08:29:44AM -0500, Tom Embt wrote: > >This would be great, but I wonder from what source we could take reliable > >data about -current's stability. > > How 'bout some sort of client program that is run via the rc.d and > rc.shutdown scripts? One of the more annoying aspects of IRIX in its default config is that whenever you do a halt or reboot it'd pop up a menu to ask why. That information, together with crash dump info and other data about system failures, can be funnelled into a mail filter which records historical reliability data; That data can (optionally) be sent back to SGI too. We could provide something like this, but (a) if it's on by default it'll suck rocks, and (b) if it's off by default nobody will bother turning it on. Hey ho! - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm
"Cameron Grant" <[EMAIL PROTECTED]> writes: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. SB AWE64 (ISA) works fine for most things, but audio is *very* scratchy and up to five seconds behind the action in Quake-II (these problems didn't exist with the old snd0 controller). Linux RealPlayer, mpg123, and just about everything else I've tried it with are happy, though. -current from Jan 9, dmesg is: sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,5 on isa0 sbc0: setting card to irq 9, drq 0, 5 pcm0: on sbc0 /dev/sndstat says: newton@atdot> cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 11 2000 09:18:06 Installed devices: pcm0: at io 0x220 irq 9 drq 0:5 (1/1 channels duplex) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 code freeze scheduled for Jan 15th
On Thu, Jan 06, 2000 at 04:27:27PM -0800, fifi - the hamster - asami wrote: > dear mr. hubbard, > please do not insult hamsters. it doesn't work that way for hamsters > either. we are fully aware of our surroundings and plan our lives > accordingly. in fact, satoshi is out picking oranges now so i have > full access to his computer. (ooohh nude hamster pics) http://www.realhamster.com - mark :-) -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problem building XFree86 (pre-3.3.6) on a recent Freebsd 4.0-current
On Wed, Jan 05, 2000 at 09:15:07PM -0800, David O'Brien wrote: > Correct. The change is due to philosophical changes by the GCC > development team. GCC 2.95.2's cpp built from cccp.c is now a pure > preprocessor and knows much less about the world than it previously did. > In 2.95.2 there is now an additional cpp that is build using gcc.c and is > a driver for the cccp.c cpp. I dare you to try saying that again with a mouth full of peanuts! - mark :-) -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unwanted Vinum partition fsck'ing when booting
On Wed, Jan 05, 2000 at 11:44:44PM +0100, Thierry Herbelot wrote: > On my SMP box, I've set up a striped Vinum partition. Not wanting to > mount it each time I boot, I've included a "placeholder" in fstab to get > it known, but without it getting mounted at boot-up. Uh huh -- But you've specified a non-zero fsck pass number in the fstab entry. Change this: > /dev/vinum/initial /files1 ufs rw,noauto 2 2 to this: /dev/vinum/initial /files1 ufs rw,noauto 2 0 - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error messages while loading the kernel
On Wed, Jan 05, 2000 at 05:49:44PM -0500, Robert C. Noland III wrote: > I have seen that as well... It seems to be caused by svr4_enable="YES" > in rc.conf. or rather the specified module. FWIW, this was fixed in rev 1.10 of svr4_sysvec.c - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, Dec 19, 1999 at 11:28:29PM -0500, Bill Fumerola wrote: > On Sun, 19 Dec 1999, Alex Zepeda wrote: > > Hmm. It happened again. This time I was playing around with the vmware > > stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think > > this is the way to go, not bloating *our* procfs), and eventually when run > > panic'd the system. I just rebooted it (nearly a day later), and fsck > > cleaned it and printed some info, but then mount refused to mount it. A > > simple reboot from the comandline seems to have worked. Hmmm indeed. > > Ditto. mount was telling me my fs wasn't clean, but after I rebooted > it was fine and it didn't fsck that second time. I saw that too; I worked out it was because I hadn't done the MAKEDEV after upgrading to a -current without blkdevs (so it's surprising it worked at all). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )
On Thu, Dec 16, 1999 at 01:22:46AM -0500, Donn Miller wrote: > runlevels, OpenBSD does not or goes with an entirely different > system), them would it be fair to consider FreeBSD "BSD"? The > advantage here is that FreeBSD would mature into it's own type of > UNIX with a BSD heritage. Can we please not have this thread again? Anyone who is interested in following up on anything whatsoever to do with SysV runlevels should first familiarize themselves with the numerous problems they have which have been hashed out on the lists several times over the last 12 months (hint: to to the mail archive search engine at www.freebsd.org and search for "runlevel"). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, Dec 15, 1999 at 10:21:40PM +0100, Wilko Bulte wrote: > >"flourocarbons" > > fluorocarbons aka CFK. There is a relation with computing: Seymour used > them to keep his machines thermally sound. Call it "cfc" -- "The tool you want to use when you want to keep FreeBSD cool." :-) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, Dec 15, 1999 at 10:41:56AM +0100, Thomas Runge wrote: > This all sounds like a decision, whether we want to be a desktop > or a server-only system. I don't agree at all -- I think that's another divsion which is orthogonal to the current discussion. Why can't we be a server OS with a decent installation tool? > For mainly server-oriented, the "install source to update" or > console-based setups are quite enough, because the system will > most probably administraded by people, that know, what they are > doing. But is it reasonable to say, "You can't play at all if you don't fit that description"? (Especially since the NT server camp seems to think you can administer a system with zero knowledge of anything; The requirement that they suddenly need to become familiar with how to deal with large archives of source code isn't going to help us get a foot in those doors). - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem with sbc driver and/or newpcm
On Wed, Dec 15, 1999 at 03:09:10AM -0600, Jeremy L. Stock wrote: > The sbc driver seems to correctly detect my soundcard for the first time > since the introduction of newpcm but I don't actually get sound out of it. Just a quick check: Can you type "mixer" at a shell prompt and check whether the reason you're getting no sound is because the master volume level defaults to 0? - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )
On Wed, Dec 15, 1999 at 01:39:28AM +, Brian Somers wrote: > [.] > > On a related subject: don't you think it's high time to end up this > > madness with MAKEDEV being a shell script, and reimplement it in C? Today, > [.] > *cough*DEVFS*cough* Gesunteit. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Tue, Dec 14, 1999 at 05:37:09PM -0600, Ryan Thompson wrote: > Daniel, here, sees the X install as being "user-friendly". Is the text > based install not? Let's not get too fixated on the visual aspect of installing the OS: That's just a sideline (an important one, but a sideline nonetheless). There's a whole swag of structural details which the current sysinstall fails miserably in. For example, has anyone noticed how virtually every OS on the market except the *BSD's build up their distributions in the same file format and with the same package database machinations as their third-party add-on packages? If I'm on a Solaris box, or an IRIX box, or a SCO box, or a Redhat box, or essentially anything else except BSD I install the base operating system using the same tools I'd use for any other software. This provides enormous benefits. Worried about bloat? Define what you mean by "Base system install" at the actual time that you're installing the system. Don't need a nameserver? Don't install it. Don't need lpd? Don't install it. Do you need Fortran? Fine, install it, even though it isn't part of the default installation set (h, I'm gonna get flamed for that :-) Upgrades are another issue: At the moment, patching parts of the base system is utterly hopeless. Consider what happens whenever there's a security advisory: We release a source-code patch to CERT, and say to everyone, "Install the patch if you have the sources installed, but if you don't have the sources you're going to have to upgrade the entire god-damned operating system!" And once someone has upgraded by patching the source code, they suddenly have a "base distribution" which is subtly different from what would have been described as the "base distribution" the day before they patched it, so future bug reports become a shot-in-the-dark type of problem. Wouldn't it be easier to say, "pkgpatch named-8.8.2p2857" (or something - I've pulled that example out of my butt) and have it md5 the files it's about to replace to make sure that you have the faulty version it's attempting to upgrade, back up the old files, install a new binary, and patch the sources if they happen to be installed, AND RECORD THE FACT THAT THIS HAS BEEN DONE IN THE PACKAGE DATABASE? And if you don't like the patch? Back it out. This is something other OS's find trivial: To continue the example of patching named, every other UNIX I can think of has named in a stand-alone package as part of the base install. If you want to upgrade it, you install a more recent version of the package, and the fact that you've done it gets recorded in a "this has been patched" section of the package database. Note that I haven't mentioned user-interfaces once in the discussion above: The problems with sysinstall have very little to do with user interfaces. > To take this a step further, why not keep (or keep something similar to) > the current sysinstall, but have an option to fetch, install, configure > and run X and another GUI installer distribution, then start the X server > and continue the installation process from there? This discussion is orthogonal to the one we're actually happening, which is about the structural problems in sysinstall which has lead Jordan to place the "this has a limited lifespan" comment in the sources. You can do what you're proposing whether we end up with a new installer or not. Anyway, don't think about user-interfaces -- They're the easy bit. Re-read Jordan's (very lucid) message on the topic from a few hours ago and think about the problems described therein and the solutions that have been proposed; you can slot your favourite user interface (even one that looks the same as the one we're using now!) into that picture later once the background issues have been dealt with. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, Dec 15, 1999 at 07:47:00AM +1100, Peter Jeremy wrote: > On 1999-Dec-14 18:36:04 +1100, Donn Miller <[EMAIL PROTECTED]> wrote: > >As far as the successor to sysinstall goes, I think it would be > >nice to have both a console version and an X version, with some X > >tookit such as Lesstif or Qt, or Tcl/Tk. > > I know Jordan mentioned Qt before his over-enthusiastic hand-waving > made him over-balance, but Lesstif and Qt (or anything else related to > X11) have a number of serious problems. That's ok; He also said it could be back-ended by TurboVision, with the decision of which GUI to use based on whether you had a $DISPLAY environment variable set. > Given the primary mission of sysinstall is to load FreeBSD, I'd > go so far as to say that developing an X version would be wasting > valuable developer resources (IMHO, of course). Long-term, do we want the installer to be a program whose primary mission is to load FreeBSD, or would we prefer a generic framework which provides the situation where loading FreeBSD doesn't differ markedly from loading (and configuring!) any particular package or subsystem after the initial installation event? I think I'll pick the latter. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
"make world" broken on a 3 month old system
I'm trying to "make world" on a system last built on Sep 29th; it's failing like so: ===> f77doc /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -B install; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH /usr/obj/usr/src/gnu/lib/libgcc/GRTAGS /usr/obj/usr/src/gnu/lib/libgcc/GSYMS /usr/obj/usr/src/gnu/lib/libgcc/GTAGS echo '#include '> config.h echo '#include ' >> config.h echo '#include "gansidecl.h"' > tconfig.h echo '#include "i386/xm-i386.h"'>> tconfig.h echo '#include "i386/i386.h"' > tm.h echo '#include "i386/att.h"'>> tm.h echo '#include "svr4.h"'>> tm.h echo '#include ' >> tm.h echo '#include "i386/freebsd.h"'>> tm.h echo '#include "i386/perform.h"'>> tm.h cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o /usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c *** Signal 12 Stop in /usr/src/gnu/lib/libgcc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Should I be expecting this? :-) - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel 810?
On Mon, Dec 06, 1999 at 07:52:20PM -0500, Garrett Wollman wrote: > < said: > > > As others have stated, Socket370 boards arent all 810/810c...my 4.0-Current > > The important issue to me is: will FreeBSD work on an 810 motherboard? > The reason I care is because I need the form-factor (a 1U-high > server); if I am to use some alternate motherboard, I'll need to be > certain in advance that it will fit in a MicroATX opening. For what it's worth, we've been buying 1U servers pre-configured (and pre-installed with FreeBSD) from Telenet Systems, http://www.tesys.com. US$1199 for the entry-level model. - mark -- Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: removing enigma(1)
On Wed, Dec 01, 1999 at 04:36:12PM -0500, James Howard wrote:
> > Renaming?
> > [15:25:53] mortis:~
> > (ttyp9):{838}% ll -i `which crypt` `which enigma`
> > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt*
> > 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/enigma*
>
> Why is that a hard link instead of a symbolic link?
Hard links are faster, require no disk space, and don't consume any
extra inodes.
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: removing enigma(1)
On Wed, Dec 01, 1999 at 03:26:34PM -0600, Matthew D. Fuller wrote:
> On Wed, Dec 01, 1999 at 04:09:11PM -0500, a little birdie told me
> that Bakul Shah remarked
> > Enigma is just a format converter at this point and should be
> > left around (after renaming it crypt -- which is how it is
> > known on all Unix versions older than 10 years). Some of us
>
> Renaming?
> [15:25:53] mortis:~
> (ttyp9):{838}% ll -i `which crypt` `which enigma`
> 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/crypt*
> 23155 -r-xr-xr-x 2 root wheel 4980 Oct 29 13:47 /usr/bin/enigma*
Ok, so the verdict is that enigma isn't contributing to bloat in
any measurable way whatsoever, because it's merely a hard link to
"crypt", a utility which has long been a useful part of UNIX and
which is required so that people can decrypt their old files (without
needing to spend an hour or so on a brute-force keysearch :-)
- mark
--
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current will enter feature freeze on December 15th!
David Schwartz wrote: > Jordan Hubbard wrote: > > With any luck, we'll have 4.0 out in time to catch the last of the new > > millennium celebrations (or riots, depending on who you listen to :). > > The last of the new millennium celebrations are still more than a year > away. Yup, and with any luck we'll have 4.0 out before then :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: nexus_setup_intr: NULL irq resource!
Peter Jeremy wrote: > Since your patch effectively turns isa_setup_intr() into a nop for > this case, a better patch would seem to be to skip the call to > BUS_SETUP_INTR() (and presumably bus_alloc_resource()) at the end > of sioattach() when you're attaching a slave SIO port. Absolutely true. :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: nexus_setup_intr: NULL irq resource!
Peter Jeremy wrote:
> I'm trying to enable a generic ISA multiport SIO card in -current from
> just before the signal changes and get presented with the above panic
> when the first SIO port on the card is attached.
Well... the first port that doesn't mention an IRQ.
I discussed this with Bruce last month; The following patch seemed
to work-around, even though it's a stupid hack which shouldn't be
committed.
The problem is that the BUS_SETUP_INTR() method for ISA seems to
absolutely require the specification of an IRQ, even though IRQ
specification is absolutely prohibited for non-master ports in
AST-compatible multi-port sio cards. Gah.
I'm not completely sure that this patch does the right thing (in
terms of allowing the slave serial ports to work correctly) anyway:
I haven't stress-tested it, I was more interested in getting the
machine involved to be able to boot. More investigation is required.
- mark
*** /tmp/co/src/sys/i386/isa/isa.c Wed Sep 1 16:04:24 1999
--- isa.c Wed Oct 6 23:00:26 1999
***
*** 137,142
--- 137,152
isa_setup_intr(device_t bus, device_t child, struct resource *r, int flags,
void (*ihand)(void *), void *arg, void **cookiep)
{
+ if (r == NULL) {
+ /*
+* handle the case for multiport sio cards, where
+* the kernel config file mentions lots of sio ports
+* but only provides the irq on the master port -- other
+* ports panic in nexus_setup_intr() without this
+*/
+ return 0;
+ }
+
return (BUS_SETUP_INTR(device_get_parent(bus), child, r, flags,
ihand, arg, cookiep));
}
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Solaris Binaries on FreeBSD
Bill A. K. wrote: > Are you the author of this emulation? I'm the maintainer and the guy who ported it to FreeBSD. It's very heavily derived from code originally authored by Christos Zoulas for NetBSD. > I was wondering because Sun is now > shipping Solaris 7.0, will this work? Yup. - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Solaris Binaries on FreeBSD
Bill A. K. wrote:
> I was wondering if we can run Solaris Binaries on our great OS? I've
> heard that OpenBSD can do it. If FreeBSD will, what do I need to do this?
Grab a copy of the Solaris/x86 libraries from Sun (they'll ship you a
CD set for $10 which includes SPARC and x86 binaries). Then look
at http://www.freebsd.org/~newton/freebsd-svr4/ to see how to make it
work.
Note that the module sources on the web page have not been tested with
3.x for a very long time. You really ought to be running -current to
expect this to work.
- mark
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: duplicate filenames under Linux emulation
Alex wrote: > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c > 444964 -rw-r--r-- 1 ak users 102042 Oct 17 20:23 > bxutils-c.c For what it's worth, I have this bug in the to-do list for the SVR4 emulator too. It's caused by the fact that dirent structures for BSD and SysVR4 are of different sizes, so svr4_getdents() (and svr4_getdents64(), its 64-bit counterpart) fetches a buffer full of BSD dirent structures from disk (usually more than the number which have actually been requested) with VOP_READDIR(), rewrites them into another buffer full of svr4_dirent structures, and returns the contents of the second buffer to userspace. Next time getdents() is called the emulated version continues from where it left off in the first buffer until it has been exhaused, at which point it issues another VOP_READDIR() call to refresh it. It looks like the duplicates are the entries which appear on the boundaries of the buffer first buffer (i.e.: the last directory entry in a buffer will be re-read into the beginning of the buffer when VOP_READDIR() is called again). I haven't had time to examine it in detail, but I suspect that incrementing an offset parameter for VOP_READDIR() aio request will fix this bug. If it does, let me know and I'll fold the result into svr4_getdents() as well :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Err - scratch that. Braino
Ignore that last message (for reasons which are too damaging to go into in any great depth :-) - mark To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
4.0-CURRENT on Pentium 200
I have a P200 running -current (from about a week ago) which announces that Pentium Pro MTRR support is enabled at boot time. Is this something I should expect given that the machine isn't running a Pentium Pro? :-) - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: A record?
Mark Murray wrote: > > 7:46PM up 375 days, 20:09, 2 users, load averages: 0.00, 0.01, 0.00 > > FreeBSD xx.xxx.xxx 2.2.6-STABLE FreeBSD 2.2.6-STABLE #0: Tue May 5 >15:51:34 SAST 1998 [EMAIL PROTECTED]:/usr/src/sys/compile/XXX i38 > 6 > > This box was used as a shell server for more than a year; it was > hardened for shell use, and served us admirably. We recently (with > some sadness) closed down the shell service, but the actual box > will live in some other (staff-serving) incarnation. A similar box which I rebooted (for an upgrade from 2.2.5 to 3.2) about a fortnight ago: 3:38PM up 471 days, 5:59, 1 user, load averages: 0.00, 0.02, 0.00 ... and, before this thread gets completely out of control, I direct posters to http://uptime.viper.net.au (warning: if you're easily offended, don't bother). - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: svr4 module broken after VM86 change
Kazutaka YOKOTA wrote: > The svr4 module is broken after the following change to svr4_machdep.c > rev 1.5. > -- > revision 1.5 > date: 1999/06/01 18:20:23; author: jlemon; state: Exp; lines: +0 -4 > Unifdef VM86. > Reviewed by:silence on on -current > -- Ah, that would be a mistake: I haven't completed the VM86 stuff yet (it has been among the lower of my priorities). Sorry, I didn't see your mesage on -current asking about it. I'l back the change out, anyway. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
IRQ sharing with newbus
I've blown the dust off an old ISA multiport serial card. In the old days, I used to make it work with BSD by including "options COM_MULTIPORT" and using the following config file directives: device sio2at isa? port 0x280 tty flags 0x0201 irq 5 vector siointr device sio3at isa? port 0x288 tty flags 0x0201 device sio4at isa? port 0x290 tty flags 0x0201 device sio5at isa? port 0x298 tty flags 0x0201 device sio6at isa? port 0x2a0 tty flags 0x0201 device sio7at isa? port 0x2a8 tty flags 0x0201 device sio8at isa? port 0x2b0 tty flags 0x0201 device sio9at isa? port 0x2b8 tty flags 0x0201 Under newbus, of course, things look slightly different, so I tried this: device sio2at isa? port 0x280 flags 0x0201 irq 5 device sio3at isa? port 0x288 flags 0x0201 device sio4at isa? port 0x290 flags 0x0201 [ ... ] device sio9at isa? port 0x2b8 flags 0x0201 Natch: "panic: NULL irq resource!" from nexus_setup_intr() in sys/i386/i386/nexus.c while probing sio3 (and I know that sio2 is probing successfully - see below). Assuming (from the panic message) that it wants an IRQ, I've tried this: device sio2at isa? port 0x280 flags 0x0201 irq 5 conflicts device sio3at isa? port 0x288 flags 0x0201 irq 5 conflicts [ ... ] device sio9at isa? port 0x2b8 flags 0x0201 irq 5 conflicts Same bat-panic, same bat-probe. If I boot -c and disable sio3-thru-sio9, the kernel successfully probes and boots, but the "slave" ports on the serial card will, of course, never be seen. (This is how I know it's the sio3 probe that's causing the panic). I'm guessing the reason for this is that an IRQ that has been "eaten" by a device under the newbus architecture is made unavailable for subsequent devices, so the "irq 5" hint on sio3-thru-sio9 is ignored, and there are no alternatives the device can try instead. So, guys -- What is the officially blessed way of sharing IRQs under newbus? - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1620-2223 - Fax: +61-8-82231777 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
NFS diskless on -current
I tried to upgrade my diskless router this afternoon to -current as
cvsupped last night.
I can't make it boot, though.
The configuration it has been using since it was last rebuilt
from Feb 24's -current (and which has been working for longer than
I care to remember) is:
- /etc/bootptab features:
yeahwhatever:\
:ha=21409773:\
:ip=YYY.YYY.YYY.YYY:\
:sm=255.255.255.240:\
:ht=ether:\
:sa=XXX.XXX.XXX.XXX:
- /tftpboot/freebsd.YYY.YYY.YYY.YYY specifies:
hostname yeahwhatever
netmask 255.255.255.240
rootfs XXX.XXX.XXX.XXX:/export/root/dotat
swapfs XXX.XXX.XXX.XXX:/export/swap/dotat
swapsize 20480
- kernel config mentions NFS_ROOT and NFS.
- kernel built with KERNFORMAT=aout ('cos loader is too stupid to
do NFS just now).
It now panics with "Can't mount root" when I boot it. And yes, I have
updated the kernel config for new-bus.
I noticed the BOOTP stuff in LINT, but that's been there for a while and
I've never needed to use it before. I turned it on anyway just to see
what happens, but tcpdump doesn't show it sending any bootp requests.
I'm obviously missing something really stupid. Would anyone care to
educate me about changes to diskless booting with NFS root filesystems
since February 24?
- mark
Mark Newton Email: new...@internode.com.au (W)
Network Engineer Email: new...@atdot.dotat.org (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/pci pcisupport.c
Mikael Karpberg wrote: > That would be so lovely, with a DEVFS too: > Plug your Cool card into your pcmcia slot, and get the message on > the sytem console that an unknown pcmcia card called "Cool", made > by CoolMakers, Inc. Damn... not even a generic driver wanted this card. > Pull the card out and go for the web: > # ftp ftp.a.cool.thing.com > ftp> get cool.tgz > --> Downloading file. Pah. kldload http://www.cool.com/drivers/freebsd/cool.ko Perhaps kld modules should have some kind of signature verification to support such a thing. That'd be so great. The FreeBSD installation floppy could delay most device probes until after you've set up networking (so you'd need some network drivers on the floppy) then grab all the latest versions of the other drivers it wants to complete the install from www.freebsd.org... - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
cvsup.au.freebsd.org
Does anyone know what has happened to cvsup.au.freebsd.org? - mark To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Alex wrote: > The question is how badly did I screw things up by running fsck? > (I think with -p it doesn't actually salvage anything, just checks the > disk). > Worth a reboot? Definitely: -p *does* salvage things. Boot to single user and run fsck manually to make sure everything's ok. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: file disappeared?
Alex wrote: > > > pcayk:~/tmp$ rm bigcdimage.iso > > > pcayk:~/tmp$ df -k . > > > Filesystem 1K-blocks UsedAvail Capacity Mounted on > > > /dev/wd0s1f7621844 69756693642899%/usr > > > How on earth did that happen?!!! > > > > Are you running soft updates? It takes ~30s for changes to take effect if > > you are. I noticed this myself last week. > > I believe not - doesn't that involve adding a "SOFTUPDATES" option to the > kernel? I don't have that in my kernel; therefore, disc access should be > synchronous by default, right? And it had definitely been longer than 30s > before I decided to run fsck (or before the first run completed). Ok, something has the file open then - storage is not freed until the last reference to the file disappears. This is so that you can rm a file on a multitasking system without making processes that might be using the file at the time fall over and die (for a similar effect, try "rm /var/log/messages" -- You'll note that storage for the file isn't freed until you kill syslogd; in fact, if you generage log messages the file will "grow" and consume more space even though it doesn't have a directory entry. An application might have the file open; Alternatively, since it's a disk image which I presume you've been testing, you could have it attached to a vn device; if that's the case, something like "vnconfig -u /dev/vn0" will detach it, close the last reference to the file, and free the associated storage. Finally, it's possible that there was a hard link to the file. Given that fsck bitched about it being an unref'ed file that's probably unlikely, but the fact stil remains that hardlinks are a legitimate reason for storage to remain allocated after you've deleted something: Once again, the file isn't really deleted until the last reference to it disappears. > Perhaps someone with an in-depth knowledge of ufs can tell me what really > happened (and what exactly did fsck do to my drive, just to make things > worse.) No need for an in-depth knowledge of UFS; this is standard UNIX behaviour, regardless of the underlying filesystem. - mark Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: solid NFS patch #6 avail for -current - need testers
Matthew Dillon wrote: > This patch is for CURRENT ONLY. Do not apply to -3.x unless you like > seeing computer equipment melt! Wow. I makes NFS access *that* fast?! - mark :-) ---- Mark Newton Email: new...@internode.com.au (W) Network Engineer Email: new...@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
HEADS UP: struct proc changing
While everyone is hob-nobbing at USENIX I thought I'd take the opportunity to make a gratuitous change to the proc structure. I'll be adding a pointer to the end of it which can be used by emulators for storing process-related emulator-specific information. It'll initially be used for storing information related to signal context state in the SysVR4 emulator, but there's no reason other emulators can't use it to hook into state data they need to store on a process-by-process base. I'll commit it tomorrow; You'll need to rebuild libkvm and any statically linked binaries which are linked against libkvm (or just do a make world). Cheers, - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
*1 routines in /sys/kern
We currently have routines like fork1() and killpg1() in /sys/kern/* to implement generic functionality for actions with more than one "front-end". NetBSD has done something similar for signals, so that emulators with non-BSD signal semantics can implement their way of doing things as an emulator-specific front-end without polluting the rest of the kernel. The SysVR4 emulator started using that stuff fairly heavily in NetBSD from November last year. I haven't merged those changes into the FreeBSD version because, well, the *1 routines aren't there yet. I wanted to get a bit of discussion going before ploughing ahead with making the change because I'm uneasy about kernel-wide changes simply to support an emulator (unstaticizing a function here and there is one thing, completely altering the implementation architecture of something that already works is something else entirely). If I split sigaction(), sigsuspend(), sigpending(), sigprocmask() and sigaltstack() into front-end and back-end pieces a-la NetBSD so that emulator-specific signal semantics can be imposed without totally duplicating those routines inside the emulator (like I did with sendit() and recvit() for socket I/O), will anyone complain? - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: SysVR4 emulator
Warner Losh wrote: > In message <199901300636.raa20...@atdot.dotat.org> Mark Newton writes: > : It's early days yet, folks -- You'll probably have trouble getting 100% > : functionality out of most things (specifically, poll() on a socket doesn't > : look like it works at the moment, so Netscape doesn't work (among other > : things)). Patches will be appreciated. > > Any idea if wabi works yet? Pretty much guaranteed that it won't: I've wrapped all the LDT-manipulation stuff in #ifdef(NOTYET) for the time being (I've been more interested in getting it ported than working at the differences between NetBSD and FreeBSD LDT handling. Doing signal context was bad enough (and I'm not sure that I've done that right either)). Perhaps an enteprising contributor can put that on a TO-DO list somewhere :-) - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
SysVR4 emulator
I've just committed the FreeBSD svr4 emulator, which has been built by adapting the stirling work of Christos Zoulas from the NetBSD project to FreeBSD. I hope I haven't left anything out or broken the world, but I'm sure I'll hear about it if I have :-) To use it: 1. Add "pseudo-device streams" to your kernel config file and rebuild, reboot. 2. Build and install the svr4 module in /sys/modules/svr4 3. Type "svr4" to start it up. 4. Grab compat_sol26.tar.gz or compat_svr4.tar.gz from http://www.freebsd.org/~newton/freebsd-svr4 and install them in /compat/svr4 5. Run "sh SVR4_MAKEDEV all" in /compat/svr4/dev 6. Mount a Solaris/x86 CD-ROM on /cdrom 7. Brand any executables you want to run 8. See if they work. It's early days yet, folks -- You'll probably have trouble getting 100% functionality out of most things (specifically, poll() on a socket doesn't look like it works at the moment, so Netscape doesn't work (among other things)). Patches will be appreciated. I'll be putting the compat_*.tar.gz archives into /usr/share/examples with a README file RSN (I haven't written a Makefile for them yet, though, hence the delay). Regards, - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: btokup() macro in sys/malloc.h
John Polstra wrote: > On 28-Jan-99 John Birrell wrote: > > John Polstra wrote: > >> > >> Hear ye, hear ye! Be it here noted and archived for all eternity that > >> on January 27, 1999 Pacific Time, John Polstra was, for one fleeting > >> moment, purer than Bruce! :-) > > > >OK, so now we have to shoot you too. Oh well, so be it > > > >Are there any others who would like to join these purists? Come on, > >we have bullets for you all... > > Bah! You might be able to hit Bruce over there in oz. But to hit me, > you'd need an ICBM. Give me purity or give me death! Bwahahahahah! That's ok -- We'll give you death. We have your ICBM address: > John Polstra j...@polstra.com > John D. Polstra & Co., Inc.Seattle, Washington USA Come to think of it, that might solve a few other problems too. Linus Torvalds may want world domination, but I think our way has the potential to be quicker... - mark :-) I tried an internal modem, new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
LDT changes to support SysVR4 emulator
Ok, people, heads up -- I'm about to commit a patch to /sys/i386 which changes the way FreeBSD uses the x86 LDT. Specifically, I'm moving LUDATA_SEL from LDT entry 4 to 5 (Why 5? Why not?) and re-using entry 4 as a call gate for SysV system calls made by library stubs from Solaris 2.6 and higher. I've been running with these mods for about a month now with no problems at all (there are no userland implications AFAICT). Nevertheless, I'm going to leave this in for a couple of days before committing the rest of the emulator to give interested parties a chance to bitch at me :-) Cheers, - mark I tried an internal modem,new...@atdot.dotat.org but it hurt when I walked. Mark Newton - Voice: +61-4-1958-3414 - Fax: +61-8-83034403 - To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: vga driver and signal
Amancio Hasty wrote:
> Not sure that this is as elegant as what you are suggesting , can
> the kernel schedule a user level routine to be executed when an interrupt
> occurs? I guess on Windoze land this is called a driver call-back.
Under UNIX it's called a signal handler :-)
- mark
----
Mark Newton Email: [EMAIL PROTECTED] (W)
Network Engineer Email: [EMAIL PROTECTED] (H)
Internode Systems Pty Ltd Desk: +61-8-82232999
"Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
