Re: virtual console 'snapshot'?
Peter Pentchev <[EMAIL PROTECTED]> writes: > Is there anything like Linux's /dev/vcs* in FreeBSD? That is, some way > to obtain the complete view of a virtual console - characters, attributes, > everything? The snoop device gives deltas, but never the complete > picture, unless the program running on that console decides to redraw > the whole thing. It shouldn't be difficult to implement, unless you want the snapshot to be consistent per-session - in which case you need to store a copy of the vty buffer at the moment the device is opened, which I don't think is possible in FreeBSD. Apart from that, the only ugliness is the need to fondle syscons' privates. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message <[EMAIL PROTECTED]>you write: }> In message <[EMAIL PROTECTED]>you write: }> }> }Mostly I guess I'd really like it to simply save *all* of the DHCP }> }response in the environment. Just "dhcp.xxx" where xxx is the parameter }> }value would probably do it, or we can argue about names for everything if }> }there aren't established names already. }> } }> what's in a name ;-) }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. } ok, so now i can setenv(dhc.xxx, val). I would very much like to make them available as sysctl dhcp.xxx, the only problem, is that the sysctl interface is prety much static, so has anybody lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them into the mid ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
Danny Braniss ([EMAIL PROTECTED]) wrote: > ok, so now i can setenv(dhc.xxx, val). > > I would very much like to make them available as sysctl dhcp.xxx, the only > problem, is that the sysctl interface is prety much static, so has anybody > lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them > into the mid ... It is dynamic in -current. -- Paul Saab Technical Yahoo [EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED] Do You .. uhh .. Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
In message <[EMAIL PROTECTED]>you write:
}Danny Braniss ([EMAIL PROTECTED]) wrote:
}> ok, so now i can setenv(dhc.xxx, val).
}>
}> I would very much like to make them available as sysctl dhcp.xxx, the only
}> problem, is that the sysctl interface is prety much static, so has anybody
}> lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them
}> into the mid ...
}
}It is dynamic in -current.
}
so now i have to get current to compile :-)
btw, i asked this before, and got answers that were not to the point.
i would very much like to be able and compile to /usr/obj, and install
not on /, but say ${dest}/ ...
danny
}--
}Paul Saab
}Technical Yahoo
}[EMAIL PROTECTED] - [EMAIL PROTECTED] - [EMAIL PROTECTED]
}Do You .. uhh .. Yahoo!?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
Danny Braniss ([EMAIL PROTECTED]) wrote:
> In message <[EMAIL PROTECTED]>you write:
> }Danny Braniss ([EMAIL PROTECTED]) wrote:
> }> ok, so now i can setenv(dhc.xxx, val).
> }>
> }> I would very much like to make them available as sysctl dhcp.xxx, the only
> }> problem, is that the sysctl interface is prety much static, so has anybody
> }> lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them
> }> into the mid ...
> }
> }It is dynamic in -current.
> }
> btw, i asked this before, and got answers that were not to the point.
> i would very much like to be able and compile to /usr/obj, and install
> not on /, but say ${dest}/ ...
make DESTDIR=/path installworld
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Sysinstall HTTP Proxy install information...
Just in case someone has more time than I do to look at this, I've been playing with sysinstall, most notably installation through an HTTP proxy. I've found what I believe to be two distinct bugs. The first is when you try to set one of the pre-fab choices, such as installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears that the request sent to the web proxy does not include the "i386" part of the path. I tried to trace it down, and found in ftp.c that it should be being added. Strange, but... The second I experience when hand-entering the URL and proxy information. It appears in this case, it tries to download the .inf file, correctly (ie - bin.inf), and it claims it parses it. However, something odd seems to happen, and sysinstall does not realize that it is supposed to be receiving chunks, and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". This is after an hour or so of looking (the most time I could get in over the weekend with 3 kids). It looks like it should be an easy fix for someone who has time to get familiar with how sysinstall works (which is where most of my hour went). Anyhow, as mentioned, this is a pointer for anyone who may have more free time than I. -Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Multipath routing in 4.x?
I searched the archives and found a few references to patches for 2.x for multipath routing. I'd like not to have to go that far back. How did something as useful as this to anyone using freebsd as a router not make it into release 3 and 4? Is there any work going on to add it? Thanks! --- David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Can't work out which disk we are booting from
Hi I apologize for ask this in the hackers list, but I have looked in the history mail list in the FreeBSD web site and I haven't found nothing similar. I can't start to install FreeBSD 4.0 or FreeBSD 3.8. It says: "Can't work which disk we are booting from." I have a IBM PC 300GL, with Pentiun II (333Mhz), Ram 64Mb and a H.D. IDE of 3228Mb. When I start to install FreeBSD 2.5 all run fine, and the installation is finished without problems. Can I do? Thanks for your help. The following are the complete messages: BTX loader 1.00 BTX version is 101 Console: internal video/keyboard BIOS drive A: is disk0 BIOS drive C: is disk1 BIOS 639kB/64501kB available memory FreeBSD/i386 bootstrap loader Revision 0.7 Can't work out which disk we are booting from. Guessed BIOS device 0x8b no found by probes, defaulting to disk0: Booting [kernel] can't load 'kernel' +-+ | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554| | | 3451565, 2176251 ext. 16 | | Opus Ingenieria | Fax : +57 1 3458343 | | Calle 61 # 5-44 Piso 3 | E-mail: [EMAIL PROTECTED]| | Santafe de Bogota D.C.,Colombia | [EMAIL PROTECTED] | +-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
atomic operations
I found the atomic_* functions in , but noticed that they have no return value. What I need is a function that increments/decrements the given value *and* returns the new value in an atomic operation. I suppose this is possible, yes? How would one modify the assembly to make this work? Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: dhcp boot was: Re: diskless workstation
> }> what's in a name ;-) > }> the dhcp.xxx stuff is easy, the problem is that the DHCP options are not > }> enough, so im trying to look into defining a FBSDclass ala PXEClient, and > }> supplying stuff like usr-ip/usr-path swap-ip/swap-path or whatever. > } > > ok, so now i can setenv(dhc.xxx, val). > > I would very much like to make them available as sysctl dhcp.xxx, the only > problem, is that the sysctl interface is prety much static, so has anybody > lookeed into making it 'dynamic'?, ie: malloc'ing structs and linking them > into the mid ... If you are setting stuff in the loader environment, you can get it back after the system has booted with 'kenv'. -- ... 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] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Can't work out which disk we are booting from
Booting from CDROM is not (yet) supported on these systems. You will have to boot from floppy disk (you can install from CDROM OK). > I apologize for ask this in the hackers list, but I have looked in the > history mail list in the FreeBSD web site and I haven't found nothing > similar. > > I can't start to install FreeBSD 4.0 or FreeBSD 3.8. > > It says: "Can't work which disk we are booting from." > > I have a IBM PC 300GL, with Pentiun II (333Mhz), Ram 64Mb and a H.D. IDE > of 3228Mb. > > When I start to install FreeBSD 2.5 all run fine, and the installation > is finished without problems. > > Can I do? > > Thanks for your help. > > The following are the complete messages: > > BTX loader 1.00 BTX version is 101 > Console: internal video/keyboard > BIOS drive A: is disk0 > BIOS drive C: is disk1 > BIOS 639kB/64501kB available memory > > FreeBSD/i386 bootstrap loader Revision 0.7 > Can't work out which disk we are booting from. > Guessed BIOS device 0x8b no found by probes, defaulting to disk0: > Booting [kernel] > can't load 'kernel' > > +-+ > | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554| > || 3451565, 2176251 ext. 16 | > | Opus Ingenieria | Fax : +57 1 3458343 | > | Calle 61 # 5-44 Piso 3 | E-mail: [EMAIL PROTECTED]| > | Santafe de Bogota D.C.,Colombia |[EMAIL PROTECTED] | > +-+ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" 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] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall HTTP Proxy install information...
In article <[EMAIL PROTECTED]> you wrote: > Just in case someone has more time than I do to look at this, I've been playing > with sysinstall, most notably installation through an HTTP proxy. [...] > The first is when you try to set one of the pre-fab choices, such as > installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears that > the request sent to the web proxy does not include the "i386" part of the Correct. The method by which the directory on the FTP server is found has been changed in ftp.c some time ago. Since installing via proxy relied on this, it is now broken. A patch is in PR bin/21449 > The second I experience when hand-entering the URL and proxy information. It > appears in this case, it tries to download the .inf file, correctly (ie - > bin.inf), and it claims it parses it. However, something odd seems to happen, > and sysinstall does not realize that it is supposed to be receiving chunks, > and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". Hm, I don't see this here - it correctly fetches all chunks of the desired distribution. IIRC, the installation falls back to "distribution.tgz" if it couldn't get "distribution.inf". I'll take another look at it. Bye, Philipp -- http://www.uni-karlsruhe.de/~un1i/ (,.) \\\00 ) \= ) cc_|\_,^ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall HTTP Proxy install information...
> Correct. The method by which the directory on the FTP server is found > has been changed in ftp.c some time ago. Since installing via proxy > relied on this, it is now broken. > > A patch is in PR bin/21449 Thanks! A lot of "cooks" have been in sysinstall lately and the upshot of it is that nobody really fully knows that code any more, including me. :) I'll review the patch and commit it. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Sysinstall HTTP Proxy install information...
> In article <[EMAIL PROTECTED]> you wrote: > > Just in case someone has more time than I do to look at this, I've been pl aying > > with sysinstall, most notably installation through an HTTP proxy. > [...] > > The first is when you try to set one of the pre-fab choices, such as > > installing from ftp.freebsd.org, or releng4.freebsd.org, etc. It appears t hat > > the request sent to the web proxy does not include the "i386" part of the > > Correct. The method by which the directory on the FTP server is found > has been changed in ftp.c some time ago. Since installing via proxy > relied on this, it is now broken. > > A patch is in PR bin/21449 > Ok. Well, if 4.1.1 hasn't been cut yet, Jordan should probably grab this patch and commit. > > The second I experience when hand-entering the URL and proxy information. It > > appears in this case, it tries to download the .inf file, correctly (ie - > > bin.inf), and it claims it parses it. However, something odd seems to happ en, > > and sysinstall does not realize that it is supposed to be receiving chunks , > > and asks for "bin.tgz", rather than "bin.aa, bin.ab, etc...". > > Hm, I don't see this here - it correctly fetches all chunks of the > desired distribution. IIRC, the installation falls back to > "distribution.tgz" if it couldn't get "distribution.inf". I'll take > another look at it. This would be good. The debug screen had shown that it had fetched bin.inf, and had "parsed" it. Looking at my web proxy log, it had requested bin.inf, and the URL was correct, so I'm guessing it either a.) got it, parsed it, and something didn't go right, or, the web server sent it, and it didn't do the right thing with it. I appreciate the effort to look at this. I'd love to do more, but at the moment, I'm cramming in an hour here and there. -Brian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Can't work out which disk we are booting from
Hi Mike Of course, I tried with both CD-ROM and floppy, but the problem is the same. Thanks. Mike Smith wrote: > > Booting from CDROM is not (yet) supported on these systems. You will > have to boot from floppy disk (you can install from CDROM OK). > +-+ | YONNY CARDENAS B. | Tels: +57 1 3451543, 3451554| | | 3451565, 2176251 ext. 16 | | Opus Ingenieria | Fax : +57 1 3458343 | | Calle 61 # 5-44 Piso 3 | E-mail: [EMAIL PROTECTED]| | Santafe de Bogota D.C.,Colombia | [EMAIL PROTECTED] | +-+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: atomic operations
Kevin Mills <[EMAIL PROTECTED]> wrote:
>I found the atomic_* functions in , but noticed that they
>have no return value. What I need is a function that increments/decrements
>the given value *and* returns the new value in an atomic operation. I
>suppose this is possible, yes? How would one modify the assembly to make
>this work?
Atomic decrement, in the Intel style:
long atomic_decrement(volatile long* address)
{
asm {
mov ecx, [address]
mov eax, -1
lock xadd [ecx], eax
dec eax
}
/* Return value in EAX */
}
An untested conversion into the GNU/AT&T style:
long atomic_decrement(volatile long* address)
{
asm("movl 8(%ebp),%ecx");
asm("movl $-1, %eax");
asm("lock xaddl %eax,(%ecx)");
asm("decl %eax");
/* Return value in %eax */
}
Deriving increment is straightforward.
I haven't looked at the GNU inline assembler notation for indicating
register usage. I'd be curious to see what is should look like.
Jan Mikkelsen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
What's the difference between the ncr0 and sym0 drivers?
Is one preferable? Thanks, Joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: putting FreeBSD in an extended partition
On Sat, 23 Sep 2000, Zhiui Zhang wrote: > > I am wondering whether there is a good reason for not putting FreeBSD in a > DOS extended partition. Good luck booting it. Doug White| FreeBSD: The Power to Serve [EMAIL PROTECTED] | www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What's the difference between the ncr0 and sym0 drivers?
In message <[EMAIL PROTECTED]> Joe McGuckin writes: : Is one preferable? sym is generally preferable to ncr. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: What's the difference between the ncr0 and sym0 drivers?
sym is actively maintained, ncr isn't really. On Mon, 25 Sep 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Joe McGuckin writes: > : Is one preferable? > > sym is generally preferable to ncr. > > Warner > > > 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
