Re: Problesm w/ 4.0-current & wine
> > Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap; > > all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a > > lot of code derived by me from the NetBSD standalone loader. > > Boot2 is, as you say, correctly identified as the "bootstrap", however you > cannot deny that boot2 is a kernel loader as it can load a pure executable > (a.out kernel or /boot/loader) or an ELF kernel. It's the bootstrap. Yes, it can load kernels, but it is not referred to as the "kernel loader" (that's what the loader is). > > > The BTX loader does have a "prompt" by default and if you interrupt the > > > countdown. The prompt is, of course, Forth :) > > > > The "BTX loader" doesn't have a prompt at all. The kernel loader has a > > prompt, and the prompt is not written in Forth (yet). > > By "BTX loader" I refer to the BTX kernel and system which can bootstrap > a kernel and load modules. There's already a perfectly good piece of code called the "BTX Loader" (btxldr); it's not appropriate to misapply this name to the loader proper. > The prompt isn't OF Forth, I stated that the prompt TAKES Forth; perhaps I > could have said that better. You "meant" that the prompt takes Forth, perhaps. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
I spent sometime just staring at the subject, before reading the message, trying to remember if I had been to any FreeBSD & drinking problems thread... :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
On Mon, 15 Feb 1999, Mike Smith wrote: > > Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is > > the kernel loader, and they're all by Mr. Nordier. > > Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap; > all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a > lot of code derived by me from the NetBSD standalone loader. Boot2 is, as you say, correctly identified as the "bootstrap", however you cannot deny that boot2 is a kernel loader as it can load a pure executable (a.out kernel or /boot/loader) or an ELF kernel. > > > The BTX loader does have a "prompt" by default and if you interrupt the > > countdown. The prompt is, of course, Forth :) > > The "BTX loader" doesn't have a prompt at all. The kernel loader has a > prompt, and the prompt is not written in Forth (yet). By "BTX loader" I refer to the BTX kernel and system which can bootstrap a kernel and load modules. The prompt isn't OF Forth, I stated that the prompt TAKES Forth; perhaps I could have said that better. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ m...@smith.net.au > \\ The race is long, and in the \\ msm...@freebsd.org > \\ end it's only with yourself. \\ msm...@cdrom.com > > > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
> Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is > the kernel loader, and they're all by Mr. Nordier. Wrong again. boot0 is in the MBR, boot1 and boot2 are the bootstrap; all by Robert. The loader, OTOH, uses Robert's BTX code, Ficl, and a lot of code derived by me from the NetBSD standalone loader. > The BTX loader does have a "prompt" by default and if you interrupt the > countdown. The prompt is, of course, Forth :) The "BTX loader" doesn't have a prompt at all. The kernel loader has a prompt, and the prompt is not written in Forth (yet). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
> > That sounds like a bug, but the "boot: " prompt is NOT the new boot loader, > it's the semi-new boot0 (which is quite nice, Mr. Nordier). 'boot:' comes from boot2, actually. > When you actually > yet to BTX, try boot -c. ... and you never get to "BTX", you end up the loader. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
> > > Kris Kennaway wrote: > > > On Mon, 15 Feb 1999, Donn Miller wrote: > > > > > I've got the USER_LDT option in my kernel, and I'm running an `aout' > > > instead of `elf' kernel. > > > > I thought running a.out systems had been deprecated for -current and was no > > longer supported. Since you're running a bleeding-edge codebase anyway, why > > haven't you updated to an ELF kernel? > > Did that. I installed the kernel, updated the new bootblocks with disklabel > -B > /dev/rwd0s2a, echo /boot/loader > /boot.conf. Now, when I enter "-c" at the > "boot: " prompt, it boots with the new boot loader, and never goes into > UserConfig (it continues booting as if I never entered "-c" at the boot > prompt). /boot.conf is completely ignored; it does nothing. You should have nothing in /boot.config or /boot.help (delete them both). Use the 'help' command in the loader, or read any of the dozens of posts I've made on this topic to date. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
On Mon, 15 Feb 1999, Daniel C. Sobral wrote: > Brian Feldman wrote: > > > > That sounds like a bug, but the "boot: " prompt is NOT the new boot loader, > > it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you > > actually > > yet to BTX, try boot -c. > > Terminology errors abound here. I know, because I made many of them > in the past. > > boot0 is the "booteasy" prompt (F?). > BTX is a kernel. "Prompt" doesn't apply here. > The twisting | is boot2. If you type something at this time, you get > boot2 prompt. Unless you type enter, od course. > The later stage is called "loader". > > So, change BTX with loader, and your advice stands. :-) Whoops, I always end up typing the wrong thing :) boot0 is the MBR, boot2 is the kernel loader, and they're all by Mr. Nordier. The BTX loader does have a "prompt" by default and if you interrupt the countdown. The prompt is, of course, Forth :) > > -- > Daniel C. Sobral (8-DCS) > d...@newsguy.com > d...@freebsd.org > > Well, as a computer geek, I have to believe in the binary universe. > > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
At the prompt: set boot_userconfig boot Tom Veldhouse ve...@visi.com -Original Message- From: Donn Miller To: Kris Kennaway Cc: curr...@freebsd.org Date: Monday, February 15, 1999 6:34 AM Subject: Re: Problesm w/ 4.0-current & wine > > >Kris Kennaway wrote: > >> On Mon, 15 Feb 1999, Donn Miller wrote: >> >> > I've got the USER_LDT option in my kernel, and I'm running an `aout' >> > instead of `elf' kernel. >> >> I thought running a.out systems had been deprecated for -current and was no >> longer supported. Since you're running a bleeding-edge codebase anyway, why >> haven't you updated to an ELF kernel? > >Did that. I installed the kernel, updated the new bootblocks with disklabel -B >/dev/rwd0s2a, echo /boot/loader > /boot.conf. Now, when I enter "-c" at the >"boot: " prompt, it boots with the new boot loader, and never goes into >UserConfig (it continues booting as if I never entered "-c" at the boot >prompt). > >Donn > > >To Unsubscribe: send mail to majord...@freebsd.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
Brian Feldman wrote: > > That sounds like a bug, but the "boot: " prompt is NOT the new boot loader, > it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually > yet to BTX, try boot -c. Terminology errors abound here. I know, because I made many of them in the past. boot0 is the "booteasy" prompt (F?). BTX is a kernel. "Prompt" doesn't apply here. The twisting | is boot2. If you type something at this time, you get boot2 prompt. Unless you type enter, od course. The later stage is called "loader". So, change BTX with loader, and your advice stands. :-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
Donn Miller wrote: > > Kris Kennaway wrote: > > > On Mon, 15 Feb 1999, Donn Miller wrote: > > > > > I've got the USER_LDT option in my kernel, and I'm running an `aout' > > > instead of `elf' kernel. > > > > I thought running a.out systems had been deprecated for -current and was no > > longer supported. Since you're running a bleeding-edge codebase anyway, why > > haven't you updated to an ELF kernel? > > Did that. I installed the kernel, updated the new bootblocks with disklabel > -B > /dev/rwd0s2a, echo /boot/loader > /boot.conf. Now, when I enter "-c" at the > "boot: " prompt, it boots with the new boot loader, and never goes into > UserConfig (it continues booting as if I never entered "-c" at the boot > prompt). Sorry for not answering this the first time... I'm having a little trouble typing... :-( At the loader prompt (which you can get at by typing anything at the autoboot message), type boot -c. -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Well, as a computer geek, I have to believe in the binary universe. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
On Mon, 15 Feb 1999, Donn Miller wrote: > > > Kris Kennaway wrote: > > > On Mon, 15 Feb 1999, Donn Miller wrote: > > > > > I've got the USER_LDT option in my kernel, and I'm running an `aout' > > > instead of `elf' kernel. > > > > I thought running a.out systems had been deprecated for -current and was no > > longer supported. Since you're running a bleeding-edge codebase anyway, why > > haven't you updated to an ELF kernel? > > Did that. I installed the kernel, updated the new bootblocks with disklabel > -B > /dev/rwd0s2a, echo /boot/loader > /boot.conf. Now, when I enter "-c" at the > "boot: " prompt, it boots with the new boot loader, and never goes into > UserConfig (it continues booting as if I never entered "-c" at the boot > prompt). That sounds like a bug, but the "boot: " prompt is NOT the new boot loader, it's the semi-new boot0 (which is quite nice, Mr. Nordier). When you actually yet to BTX, try boot -c. > > Donn > > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
Kris Kennaway wrote: > On Mon, 15 Feb 1999, Donn Miller wrote: > > > I've got the USER_LDT option in my kernel, and I'm running an `aout' > > instead of `elf' kernel. > > I thought running a.out systems had been deprecated for -current and was no > longer supported. Since you're running a bleeding-edge codebase anyway, why > haven't you updated to an ELF kernel? Did that. I installed the kernel, updated the new bootblocks with disklabel -B /dev/rwd0s2a, echo /boot/loader > /boot.conf. Now, when I enter "-c" at the "boot: " prompt, it boots with the new boot loader, and never goes into UserConfig (it continues booting as if I never entered "-c" at the boot prompt). Donn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
On Mon, 15 Feb 1999, Donn Miller wrote: > I've got the USER_LDT option in my kernel, and I'm running an `aout' > instead of `elf' kernel. I thought running a.out systems had been deprecated for -current and was no longer supported. Since you're running a bleeding-edge codebase anyway, why haven't you updated to an ELF kernel? Kris - (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Problesm w/ 4.0-current & wine
I'm also using wine(latest from ports) with 4.0-current and it works for me (elf kernel). Donn Miller wrote: > When I try to run wine on FreeBSD 4.0-CURRENT, I get the following > message: > > Feb 15 05:19:56 myname /kernel: Patch manager interface is currently > broken. Sorry > Feb 15 05:19:56 myname /kernel: Patch manager interface is currently > broken. Sorry > wine: can't exec 'demo1.exe': error=0 > wine: no executable file found. > > I've got the USER_LDT option in my kernel, and I'm running an `aout' > instead of `elf' kernel. > > Donn > > To Unsubscribe: send mail to majord...@freebsd.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Problesm w/ 4.0-current & wine
When I try to run wine on FreeBSD 4.0-CURRENT, I get the following message: Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry Feb 15 05:19:56 myname /kernel: Patch manager interface is currently broken. Sorry wine: can't exec 'demo1.exe': error=0 wine: no executable file found. I've got the USER_LDT option in my kernel, and I'm running an `aout' instead of `elf' kernel. Donn To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
