Re: diskless booting
On Tue, Apr 23, 2002 at 08:32:51PM +0300, Danny Braniss wrote:
On Tue, Apr 23, 2002 at 12:19:58PM -0400, Robert Watson wrote:
diskless_root_readonly=NO # Make it YES for readonly
good.
diskless_etc_localmd=NO # Make it YES to have the
# diskless environment md-mount and replicate /etc from /conf
Seems the if [ -d ] tests in rc.diskless are OK already. If we add
this knob, then a knob should also be added for the source of the files
rather than assuming /conf/etc or /conf/{client}/etc. In other words
either really engineer this to make diskless properly configurable, or
have the minimal number of knobs, etc.
nice, but impractical, because of the chicken and egg problem, or in other
words, the load/over-write of rc.conf[.local] happens a bit later ...
Please explain farther what is impractical and where the chicken-and-egg
problem is. I rc.diskless1 already has:
if [ -d /conf/default/etc ]; then
..snip..
if [ -d /conf/${i}/etc ]; then
in rc.diskless1 is where the decision is made about /etc, /tmp, /var.
the mount is done some lines before the test.
i guess a first run could be made, before the actual mount:
...
echo Interface ${bootp_ifc} IP-Address ${bootp_ipa} Broadcast ${bootp_ipbca}
for i in ${bootp_ipbca} ${bootp_ipa} ${hostname} ; do
if [ -d /conf/${i}/etc ]; then
if [ -r /conf/${i}/etc/rc.conf ]; then
. /etc/defaults/rc.conf
...
IMHO, the solution is a bit of klduge :-), and sort of breaks the KISS
principle.
danny
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting
Robert Watson wrote: This would provide full compatibility with the current model for those that want it (and I think it's more people than you think) at the same time as changing the system to provide easy support for the environment you're looking for. If the default settings are changing, it should be a 5.0 feature not a 4.x feature. FWIW, I thought this was a new feature, since diskless/dataless has never really worked for me, without a lot of local hacking to make it work. the first time around this was a real problem for me, starting off with FreeBSD and also doing the diskless stuff, now some time later (hum, about 2 years?), i tried it from scratch with 5.0 - it took me almost no time! adding the local mods took more time since i was (not very successfuly) recording the changes i was doing :-( btw, i did not have to do no 'lot of local hacking' to get it working: newfs /c/2; cd /c/2; dump 0f - / | restore rf - (brute force to get most of the local environment :-) make installworld DESTDIR=/c/2 and i could start booting 5.0 danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting
Robert Watson wrote: I have't really used the diskless environment with 4.x, but use it extensively in my test/development environments for 5.0. Stateless workstations are great when it comes to file system debugging, especially since newfs is orders of magnitude faster than fsck :-). THat is what I primarily use them for, as well. -- Terry true, true, it's nice to be able to fix bugs on a running system, and trying it out on a diskless/dataless! but im also deploying servers dataless, it makes upgrading them less problematic. danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting
On Mon, 22 Apr 2002, David O'Brien wrote: +if [ -z `hostname -s` ]; then +hostname=`kenv dhcp.host-name` +hostname $hostname +echo Hostname is $hostname +fi If you wanted to match the style for most of the rc* files, and avoid an unecessary call to 'test,' you could do: case `hostname -s` in '') foo ;; esac Not a big deal, but I thought I'd mention it. :) Doug done, and thanks, danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Tue, Apr 23, 2002 at 09:40:11PM -0700, David Schultz [EMAIL PROTECTED] wrote: Userspace processes will allocate memory from UVA space and can grow over 1GB of size if needed by swapping. You can certainly have more than one over-1GB process going on at the same time, but swapping will constrain your performance. It isn't a performance constraint. 32-bit architectures have 32-bit pointers, so in the absence of segmentation tricks, a virtual address space can only contain 2^32 = 4G locations. If the kernel gets 3 GB of that, the maximum amount of memory that any individual user process can use is 1 GB. If you had, say, 4 GB of physical memory, a single user process could not use it all. Swap increases the total amount of memory that *all* processes can allocate by pushing some of the pages out of RAM and onto the disk, but it doesn't increase the total amount of memory that a single process can address. Thank you, Terry and David, now I grasp how it should work (I hope). I really miss some education, but that's life. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
what if/diskless booting
at stage 1, the diskless host sends out a bootp/dhcp request, the dhcpd servers sends back some packets, and pxeloader gets tftp'ed. i modified libstand/bootp.c to place all the tags - that dhcp provides - in the kernel environmet, so that they can be used later - eg in rc.diskless1. what if: we place the rc.conf[.local] there? in the dhcpd.conf: option rc-conf 132.65.16.100:/d/4/etc/rc.conf and so - automagicaly - `kenv rc.conf.diskless_root_readonly` or kenv | grep rc.conf | sed 's/rc.conf.//' rc.conf i'll work now on the 'automagicaly' part :-) danny To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic: clist reservation botch
On Tue, 23 Apr 2002, Robert Watson wrote: This was from the TrustedBSD MAC branch, but it's not clear to me that this relates to the MAC patches. Have't seen this before; this box is a pxe-booted NFS-mounted system. Kernel and userland may be out of sync, but all modules should be in sync. System is on a serial console. This panic was last reported for a USB modem in -RELENG_4.x. I think it is just a missing spltty() in usb there. Configuring syscons: blanktimepanic: clist reservation botch cpuid = 1; lapic.id = 0100 Debugger(panic) Stopped at Debugger+0x41: xorl%eax,%eax db trace Debugger(c03de45a) at Debugger+0x41 panic(c03e429f,c0445620,c8e3f200,c8e3f200,c982ab08) at panic+0xd8 cblock_free_cblocks(b,c8e3f200,c982ab28,c0274fd8,c8e3f200) at cblock_free_cblocks+0x29 clist_free_cblocks(c8e3f200,c8e3f238,c8e3f21c,c8e3f200,3) at clist_free_cblocks+0x20 ttyclose(c8e3f200,c8e3f200,1,c98315a0,c939ca48) at ttyclose+0x44 ttyclose(c8e3f200,c8e3f200,1,c98315a0,c939ca48) at ttyclose+0x44 scclose(c049a518,1,2000,c939ca48,c049a518) at scclose+0xd6 spec_close(c982ab94,c982aba8,c02995ec,c982ab94,c93ab03c) at spec_close+0x11a spec_vnoperate(c982ab94,c93ab03c,c93ab03c,c0417ee0,c98315a0) at spec_vnoperate+0x15 vn_close(c98315a0,1,c3f76a00,c939ca48,c982ac08) at vn_close+0x40 vn_closefile(c93ab03c,c939ca48,c93ab03c,c939ca48,0) at vn_closefile+0x1f fdrop_locked(c93ab03c,c939ca48,c049cc00,0,c03daa33) at fdrop_locked+0x12c fdrop(c93ab03c,c939ca48,1,c984b974,8) at fdrop+0x26 closef(c93ab03c,c939ca48) at closef+0xa0 fdfree(c939ca48,c982ad20,c939ca48,c982ad20,c939c948) at fdfree+0x80 exit1(c939ca48,0,c0441740,0,c03db00e) at exit1+0x2af sys_exit(c939ca48,c982ad20,2813c3f8,2805173c,0) at sys_exit+0x2a syscall(2f,2f,2f,0,2805173c) at syscall+0x223 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (1, FreeBSD ELF, sys_exit), eip = 0x280bb48b, esp = 0xbfbffd5c, ebp = 0xbfbffd88 --- The most important part of the trace is missing here. The panic is in clock_alloc(), which isn't in the trace. In -current, there is only the Giant lock to lock clist allocation. I can't see anywhere where it is missing (exit(2) is not MPSAFE, so Giant should be held in most of the above. Similarly for read(2) and write(2). The upper layer of tty interrupt handlers are not MPSAFE, so Giant should be held in them too. It is also important that free(9) doesn't block or otherwise release Giant. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
David Schultz wrote: Thus spake Terry Lambert [EMAIL PROTECTED]: Writing a useful (non-fluff) technical book, optimistically, takes 2080 hours ... or 40 hours per week for 52 weeks... a man year. By the time you are done, the book is a year out of date, and even if you worked really hard and kept it up to date (e.g. you had 4 authors and spent only 6 months of wall time on the book), the shelf life on the book is still pretty short. Although it would be unreasonable to comprehensively document the kernel internals and expect the details to remain valid for a year, there is a great deal of lasting information that could be conveyed. For example, Kirk's 4.[34]BSD books cover obsolete systems, and yet much of what they say applies equally well to recent versions of FreeBSD. These are general OS architecture books by a noted authority on OS architecture. That's a barrier to entry for other authors, as the intrinsic value in the information is not constrained to the direct subject of the work. 8-). Kirk is supposedly working on a similar book for FreeBSD, release date indeterminate. In any case, this doesn't resolve the issue of Where do I go to do XXX to version YYY, without having to learn everything there is to know about YYY?. It's true that the specific question ``How do I change my KVA size?'' might have different answers at different times, but I doubt that the ideas behind an answer have all been invented in the last few months. Even things like PAE, used by the Linux 2.4 kernel, remind me of how DOS dealt with the 1 MB memory limit. The PAE is the thing that Peter was reportedly working on in order to break the 4G barrier on machines capable of accessing up to 16G of RAM using bank selection. I didn't mention it by name, since the general principle is also applicable to the Alpha, which has a current limit of 2G because of DMA barrier and other constraints. While it's true that the ideas behind the answer remain the same... the ideas behind the answer are already published in the books I've already referenced in the context of this thread. If people were content to discover implementation details based on a working knowledge of general principles, then this thread would never have occurred in the first place. It's my opinion that people are wanting to do more in depth things to the operating system, and that there is a latency barrier in the way of them doing this. My participation in this discussion, and in particular, with regard to the publication of thorough and useful documentation, has really been around this point. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Locking down a socket, milestone 1
I am now working on locking down a socket. (I have heard that Jeffrey Hsu is also doing that, but I have never seen his patch. Has anyone seen that?) My first milestone patch is now available at: http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz The works I have done so far are: - Determine the lock required to protect each of the members in struct socket. - Add mutexes to each of the sockbufs in a socket as BSD/OS does. - Lock down so_count, so_options, so_linger and so_state. - Add a global mutex socq_lock to protect the connection queues of a listening socket. Lock socq_lock to lock two sockets at once, followed by enqueuing or dequeuing a socket, or moving a socket across queues. socq_lock is not an sx lock because we usually have to lock two sockets to modify them. - Add a global sx sigio_lock to protect the pointer to the sigio object of a socket. This is to avoid lock order reversal caused by locking a process in pgsigio(). This lock should be applicable to a pipe as well. Although there are still lots of works to do, the patch has grown up quite a lot. so_options is the most notorious member in struct socket so far because it is used in almost all of the protocol stacks. I would therefore like to test, fix and merge the patch before it blows up. Comments are welcome. Thanks. -- Seigo Tanimura [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
still ATA problems with promise tx2
hello, i couldnt decide from reading the list if there should or shouldnt be problems with promise ata/100 controller with current. anyway, i have problems with it. i've tried several current versions from the devel snapshot to apr 22nd and all of those fail after installation. in the floppy boot all looks ok, and it installs fine, but when i boot up after the installation it panics every time, looks like at the time the machine is probing for the controller. any ideas? i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) this is a single disk on that controller. no errors during the installation. [this is an attempt to make a fresh installation, all my other current machines are too old to be helpfull] mickey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: still ATA problems with promise tx2
It seems mika ruohotie wrote: hello, i couldnt decide from reading the list if there should or shouldnt be problems with promise ata/100 controller with current. I dont think so... anyway, i have problems with it. i've tried several current versions from the devel snapshot to apr 22nd and all of those fail after installation. in the floppy boot all looks ok, and it installs fine, but when i boot up after the installation it panics every time, looks like at the time the machine is probing for the controller. any ideas? i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) That would be most helpfull, where does it panic, what is the panic message ? -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: new expr(1) behaviour breaks libtool
I have just committed code to expr which will cause it to behave more like the old expr did in the presence of an EXPR_COMPAT environment variable. Ports can then be set up to build with this variable defined until the libtool maintainers fix up their act. Thanks, with this and some patches to the ghostscript-gnu and jade ports, I can now build releases with docs. John -- John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Kenneth Culver writes: OK, I THINK I found what calls the actual kernel syscall handler, and sets it's args first, but I'm not sure: from linux_locore.s NON_GPROF_ENTRY(linux_sigcode) ... Does anyone who actually knows assembly have any ideas? This is the linux sigtramp, or signal trampoline. It is used to wrap a signal handler. Eg, the kernel calls it (by returning to it) when it delivers a signal. It calls the apps signal handler. When the handler returns, it calls the linux sigreturn system call. This has essentially nothing to do with system calls. The system call entry point on x86 is int0x80_syscall, which is labled: /* * Call gate entry for FreeBSD ELF and Linux/NetBSD syscall (int 0x80) .. This then calls syscall2(), which calls the linux prepsyscall. Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Locking down a socket, milestone 1
On 24-Apr-2002 Seigo Tanimura wrote: I am now working on locking down a socket. (I have heard that Jeffrey Hsu is also doing that, but I have never seen his patch. Has anyone seen that?) My first milestone patch is now available at: http://people.FreeBSD.org/~tanimura/patches/socket_milestone1.diff.gz The works I have done so far are: - Determine the lock required to protect each of the members in struct socket. - Add mutexes to each of the sockbufs in a socket as BSD/OS does. - Lock down so_count, so_options, so_linger and so_state. - Add a global mutex socq_lock to protect the connection queues of a listening socket. Lock socq_lock to lock two sockets at once, followed by enqueuing or dequeuing a socket, or moving a socket across queues. socq_lock is not an sx lock because we usually have to lock two sockets to modify them. Do you actually lock two sockets at once or do you lock one at a time while holding socq_lock. If you do lock two at once, what is the defined locking order? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
- Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Christian Flügel [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 4:05 AM Subject: Re: upgrade from 4.5 to current fails On Tue, Apr 23, 2002 at 11:55:37PM +0200, Christian Flügel wrote: Hello Folks. I currently try to upgrade from 4.5 STABLE to CURRENT. I have cvsuped my source and already made buildworld and buildkernel. But installworld failed with Signal 12 while installing chpass. You're attempting to upgrade incorrectly. Follow the directions _precisely_ and this won't happen. If this would work I'd gladly follow the procedure described in updating. make buildworld: works ok. make buildkernel: works ok. copy GENERIC.hints to /boot/device.hints: works ok. make installkernel: stops with error: kldxref not found The suggestion on current was to simply make installworld so that the missing file is installed and then make installkernel but this one wouldn't work either. so the kernel does need a file which is only part of curent but world will only install itself when a current kernel exists. Like the snake biting its own tail. Regards Christian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: what if/diskless booting
On Wed, 24 Apr 2002, Danny Braniss wrote:
i modified libstand/bootp.c to place all the tags - that dhcp provides - in
the kernel
environmet, so that they can be used later - eg in rc.diskless1.
what if:
we place the rc.conf[.local] there?
in the dhcpd.conf:
option rc-conf 132.65.16.100:/d/4/etc/rc.conf
and so - automagicaly -
`kenv rc.conf.diskless_root_readonly`
or
kenv | grep rc.conf | sed 's/rc.conf.//' rc.conf
Note that Luigi has recently committed something similar to create the
sysctl kern.bootp_cookie (see /sys/nfs_client/bootp.c rev 1.36).
I have also been doing the same thing for some time, but the difference in
my version is that I use four separate DHCP options (133,134,135,136 at
present, though this isn't important) and concatenate their together onto
the end of the (MFS copy of) /etc/rc.conf from rc.diskless1.
The reason for using four options is that in the DHCP configuration there
are a number of different scopes in which you can put the option
assignments, all of which are potentially useful for diskless
configuration options.
For example, in our setup we have some things that need to be set
per-subnet (eg. which servers to use), some that need to be per group{} of
machines in the dhcpd.conf (eg. we have one group of 486-class machines
that are pure X-terminals, and another of more powerful machines which are
allowed to run more services locally), and finally there are some options
that need to be set per-machine (eg. which machines need to run lpd
because they have a printer attached). Each scope gets its own DHCP
option, and then they are all concatenated together onto the end of
rc.conf.
Before implementing this scheme, we tried to use the /etc/conf/ipaddr
scheme, but this didn't really scale well. We started with just two
classes of hardware, so had two /etc/conf/{IBM,COMPAQ} directories with
symlinks for each of the machines of that class, but then as the network
expanded we needed per-subnet configuration and the /etc/conf/${ipba}
scheme didn't work as we still needed the per-machine-class configuration
too. Then we started adding local printers and we now had
/etc/conf/{IBM-net10,COMPAQ-net10,IBM-net11,COMPAQ-net11,IBM-net10-printer}
etc and then we got some new hardware that wasn't quite the same...
With the new scheme, everything is configured in just one place and
adding a new machine or a new per-subnet service is easy.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
- Original Message - From: Christian Flügel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 2:17 PM Subject: Re: upgrade from 4.5 to current fails make installkernel: stops with error: kldxref not found OK. I figured this one out for myself. cd usr.sbin/kldxref make depend make make install solved the problem. Maybe this should be put in UPDATING? Regards Christian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: what if/diskless booting
Note that Luigi has recently committed something similar to create the
sysctl kern.bootp_cookie (see /sys/nfs_client/bootp.c rev 1.36).
i will check that out asap.
I have also been doing the same thing for some time, but the difference in
my version is that I use four separate DHCP options (133,134,135,136 at
present, though this isn't important) and concatenate their together onto
the end of the (MFS copy of) /etc/rc.conf from rc.diskless1.
well, not much different from my proposal, which probably means that we are
thinking
somewhat alike :-)
with my scheme, i could concat more than one file, and place all the
name/value pairs
in the environmet.
im trying to solve the chicken and egg problem: there are some (few) things
that have
to be dealt very early - ie. is / RO or RW, etc.
secondly, im also getting bogged down trying to configure clusters/few/single
hosts
with some particularities, and having some kind of central control is
escential so
that i can keep my sanity.
we developed a very sophisticated (in other words complicated) system to
configure
our linux boxes, and it's getting to the point that too much time is spent
debugging
the system each time a new hardare/box appears :-)
the freebsd scheme is much more to my liking, it just needs something more ...
The reason for using four options is that in the DHCP configuration there
are a number of different scopes in which you can put the option
assignments, all of which are potentially useful for diskless
configuration options.
For example, in our setup we have some things that need to be set
per-subnet (eg. which servers to use), some that need to be per group{} of
machines in the dhcpd.conf (eg. we have one group of 486-class machines
that are pure X-terminals, and another of more powerful machines which are
allowed to run more services locally), and finally there are some options
that need to be set per-machine (eg. which machines need to run lpd
because they have a printer attached). Each scope gets its own DHCP
option, and then they are all concatenated together onto the end of
rc.conf.
Before implementing this scheme, we tried to use the /etc/conf/ipaddr
scheme, but this didn't really scale well. We started with just two
classes of hardware, so had two /etc/conf/{IBM,COMPAQ} directories with
symlinks for each of the machines of that class, but then as the network
expanded we needed per-subnet configuration and the /etc/conf/${ipba}
scheme didn't work as we still needed the per-machine-class configuration
too. Then we started adding local printers and we now had
/etc/conf/{IBM-net10,COMPAQ-net10,IBM-net11,COMPAQ-net11,IBM-net10-printer}
etc and then we got some new hardware that wasn't quite the same...
he he, been there too! we get a batch of 50 machines, they are all alike,
great, then
some want to swap localy, fine, then some change the cd to cdr, they add a
different
sound card, etc, etc,
With the new scheme, everything is configured in just one place and
adding a new machine or a new per-subnet service is easy.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Cross-platform releases
Hi! This is just a heads up for anyone interested that I have just started working on a cross-platform make release issue so that make release TARGET_ARCH=alpha on an i386 box would produce a working Alpha release. The next task will be to support cross-branch make releases so that a 4.x box could be used to produce a 5.0 snapshot. Combined together, that would give me an ability to test my 5.0 changes with make release on a fast 2x1GHz box that runs -STABLE. Supporting non-root make releases might be a good idea too. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37622/pgp0.pgp Description: PGP signature
Re: upgrade from 4.5 to current fails
On Wed, Apr 24, 2002 at 02:22:49PM +0200, Christian Flügel wrote: - Original Message - From: Christian Flügel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 2:17 PM Subject: Re: upgrade from 4.5 to current fails make installkernel: stops with error: kldxref not found OK. I figured this one out for myself. cd usr.sbin/kldxref make depend make make install solved the problem. Maybe this should be put in UPDATING? If you start at 4.5 and upgrade to current, then the installkernel should report kldxref/boot/kernel kldxref: No Such File or Directory ***Error code 1(ignored) Note the Error code 1(ignored). See for example, Date: Sat, 30 Mar 2002 20:54:14 -0800 (PST) From: Doug White [EMAIL PROTECTED] To:A.Z. [EMAIL PROTECTED] Cc:[EMAIL PROTECTED] Subject: Re: kldxref problem Message-ID: [EMAIL PROTECTED] In-Reply-To: 001601c1d87f$620474f0$6401a8c0@voodoowixp As Kris stated, follow the documented 4.5 to current upgrade procedure in UPDATING. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote: Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. My recollection is that beyond 5 arguments, a pointer to the remaining ones is passed. (But my recollection may be wrong and I don't wish to subject myself to the source cesspool at the moment) -- brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineeringKF8NH carnegie mellon university [better check the oblivious first -ke6sls] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Brandon S Allbery KF8NH writes: On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote: Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. My recollection is that beyond 5 arguments, a pointer to the remaining ones is passed. (But my recollection may be wrong and I don't wish to subject myself to the source cesspool at the moment) I think that's how it used to work. Apparently, they've changed it recently and they now pass 6 args in registers. Eg, in the linux kernel sources, old_mmap() fetches its args via copy_from_user(), whereas the newer sys_mmap2() doesn't. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
UTF-8 support.
What's going on as far as adding utf-8 based locales? How can I help? Kyle Butt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: still ATA problems with promise tx2
On Wed, Apr 24, 2002 at 02:17:27PM +0200, Søren Schmidt wrote: It seems mika ruohotie wrote: i might be able to provide more information if this sounds like something which shouldnt be happening. (trace, whatever needed) That would be most helpfull, where does it panic, what is the panic message ? panic: bad ivar read request (4) Debugger(panic) Stopped at Debugger+0x40: xorl%eax,%eax db trace Debugger(c03c241c) at Debugger+0x40 panic(c057a399,4,d7bdf070,ce4e0c00,d7c2ce00) at panic+0x70 acpi_read_ivar(ce4e0c00,d7c2bc80,4,c05aebb8) at acpi_read_ivar+0x9b ata_pci_match(d7c2ce00) at ata_pci_match+0x918 ata_pci_probe(d7c2ce00,d7c2ce00,d7c2e780,d7c2ce00,0) at ata_pci_probe+0xd device_probe_child(d7c2e780,d7c2ce00,d7c2ce00,d7c2bc80,d7c2e780) at device_probe_child+0xca device_probe_and_attach(d7c2ce00) at device_peobe_and_attach+0x41 bus_generic_attach(d7c2e780,d7c2e780,d6928280,ce4e0c00,1) at bus_generic_attach+0x16 device_probe_and_attach(d7c2e780) at device_probe_and_attach+0x9a bus_generic_attach(d7c2bc80,d7bd5090,ce4e0c00,d7c2bc80,c05aec90) at bus_generic_attach+0x16 acpi_pcib_attach(d7c2bc80,d7c2bc80,ce4e0c00,ce4e0c00,0) at acpi_pcib_attach+0x1d7 device_probe_and_attach(d7c2bc80) at device_probe_and_attach+0x9a bus_generic_attach(ce4e0c00,ce4e0ba0,ce4e0b80,ce4b23e0,c05aecf8) at bus_generic_attach+0x16 i hope that's enough, had to type that by hand... =) -Søren mickey To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Cross-platform releases
ru This is just a heads up for anyone interested that I have just ru started working on a cross-platform make release issue so that ru make release TARGET_ARCH=alpha on an i386 box would produce a ru working Alpha release. Wonderful! If there are any tasks I can help for you, feel free to email me. My buildboxes are awaiting more jobs to do, but myself is awaiting more spare times to do :-( ru The next task will be to support cross-branch make releases ru so that a 4.x box could be used to produce a 5.0 snapshot. It seems that there are 2 problems; some syscall issue, and md/vn device issue. However, IIRC, the latter problem was already resolved by nyan-san. ru Supporting non-root make releases might be a good idea too. This requires that non-root uses vn/md device... -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
CURRENT panic + patch
Calling freeenv with the pointerm different from one received from
getenv seldom is a good idea :) Indeed, CURRENT panics with the
following stack trace (patch below fixes that):
_mtx_lock_sleep(c08300e4,0,c03644b1,649,c08300e4) at
_mtx_lock_sleep+0x122
_mtx_lock_flags(c08300e4,0,c03644b1,649,c03a7b60) at
_mtx_lock_flags+0x67
uma_zfree_arg(c083,cca34d5f,cca34ef8,cca34d5f,5) at
uma_zfree_arg+0x3e
free(cca34d5f,c03a7b60,c04ddc44,c015d9ce,cca34d5f) at free+0x6c
freeenv(cca34d5f,cca41070,cc3d5100,c04ddc60,c04ddc64) at freeenv+0x1a
acpi_disabled(c0326287) at acpi_disabled+0x96
acpi_ec_probe(ccac1100,ccac1100,cc3d5100,ccac1100,0) at
acpi_ec_probe+0x96
device_probe_child(cc3d5100,ccac1100,ccac1100,cc3d5100,cc3d5100) at
device_probe_child+0xce
device_probe_and_attach(ccac1100) at device_probe_and_attach+0x41
bus_generic_attach(cc3d5100,cc3d5100,c6d83f20,c6d83f00,c6d5a700) at
bus_generic_attach+0x16
acpi_probe_children(cc3d5100) at acpi_probe_children+0x6a
acpi_attach(cc3d5100,cc3d5100,cc3d5a00,cc3d5a00,1) at acpi_attach+0x2bd
device_probe_and_attach(cc3d5100) at device_probe_and_attach+0x9a
bus_generic_attach(cc3d5a00,cca6b090,cc3d5c80,c04ddd5c,c020ad66) at
bus_generic_attach+0x16
nexus_attach(cc3d5a00,cc3d5a00,c037ace4,4e2000,1) at nexus_attach+0xe
device_probe_and_attach(cc3d5a00) at device_probe_and_attach+0x9a
root_bus_configure(cc3d5c80,c03675a0,0,4) at root_bus_configure+0x16
configure(0,4dac00,4da000,0,c0130d3c) at configure+0x22
mi_startup() at mi_startup+0x95
begin() at begin+0x43
Index: acpi.c
===
RCS file: /usr/ncvs/src/sys/dev/acpica/acpi.c,v
retrieving revision 1.60
diff -u -r1.60 acpi.c
--- acpi.c 19 Apr 2002 23:36:38 - 1.60
+++ acpi.c 24 Apr 2002 16:33:24 -
@@ -1590,17 +1590,18 @@
int
acpi_disabled(char *subsys)
{
-char *cp;
+char *cp, *env;
intlen;
-if ((cp = getenv(debug.acpi.disable)) == NULL)
+if ((env = getenv(debug.acpi.disable)) == NULL)
return(0);
-if (!strcmp(cp, all)) {
- freeenv(cp);
+if (!strcmp(env, all)) {
+ freeenv(env);
return(1);
}
/* scan the disable list checking for a match */
+cp = env;
for (;;) {
while ((*cp != 0) isspace(*cp))
cp++;
@@ -1610,12 +1611,12 @@
while ((cp[len] != 0) !isspace(cp[len]))
len++;
if (!strncmp(cp, subsys, len)) {
- freeenv(cp);
+ freeenv(env);
return(1);
}
cp += len;
}
-freeenv(cp);
+freeenv(env);
return(0);
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: CURRENT panic + patch
Alexander Kabaev wrote: Calling freeenv with the pointerm different from one received from getenv seldom is a good idea :) [...] Indeed. Sorry for this yet another freeenv() breakage ; this patch looks good. Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
On 24-Apr-2002 Christian Flügel wrote: - Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Christian Flügel [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 4:05 AM Subject: Re: upgrade from 4.5 to current fails On Tue, Apr 23, 2002 at 11:55:37PM +0200, Christian Flügel wrote: Hello Folks. I currently try to upgrade from 4.5 STABLE to CURRENT. I have cvsuped my source and already made buildworld and buildkernel. But installworld failed with Signal 12 while installing chpass. You're attempting to upgrade incorrectly. Follow the directions _precisely_ and this won't happen. If this would work I'd gladly follow the procedure described in updating. make buildworld: works ok. make buildkernel: works ok. copy GENERIC.hints to /boot/device.hints: works ok. make installkernel: stops with error: kldxref not found This is a bug in installkernel. Bug Peter Wemm [EMAIL PROTECTED] to fix it since he broke it. :) Or find somone else who groks the src/Makefile.inc1 stuff. The real fix is harder and involves fixing the kernel build so that modules stop being a hack and all .ko's are built in the same directory and then kldxref is run at build time as a build tool. I guess the other hack would be to change the makefiles back to ignoring failures from kldxref for now until the bigger problem is fixed. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
sgk Note the Error code 1(ignored). That's right, it's not an actual *error*. However, we have seen such a report so many, many times. We may want to consider changing src/sys/conf/kmod.mk to shut it up. -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: CURRENT panic + patch
Alexander Kabaev wrote: Hint: Now if only someone could commit it ... Done, thanks. Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
panic at shutdown, ums related?
Hi, backtrace from the console, no core dump: panic: Removing other than first element usb_transfer_complete uhci_device_intr_abort usbd_ar_pipe usbd_abort_pipe ums_disable ums_close spec_close ... It seems I may get it at every shutdown, so if there's something I should look at... Bye, Alexander. -- The three Rs of Microsoft support: Retry, Reboot, Reinstall. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Cross-platform releases
On Thu, Apr 25, 2002 at 01:44:04AM +0900, Makoto Matsushita wrote: ru This is just a heads up for anyone interested that I have just ru started working on a cross-platform make release issue so that ru make release TARGET_ARCH=alpha on an i386 box would produce a ru working Alpha release. Wonderful! If there are any tasks I can help for you, feel free to email me. My buildboxes are awaiting more jobs to do, but myself is awaiting more spare times to do :-( A fast -CURRENT box with root access for make release would be highly appreciated. My 500MHz Celeron is too slow for this. ru The next task will be to support cross-branch make releases ru so that a 4.x box could be used to produce a 5.0 snapshot. It seems that there are 2 problems; some syscall issue, and md/vn device issue. However, IIRC, the latter problem was already resolved by nyan-san. There are no syscall issues in my version because I do not do a second installworld. ru Supporting non-root make releases might be a good idea too. This requires that non-root uses vn/md device... I realize that, there are some prerequisites for this too, like setting vfs.usermount=1. More about this later. I estimate that 30% is already done. :-) Time to sleep now. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg37635/pgp0.pgp Description: PGP signature
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Mon, 22 Apr 2002 06:04:34 -0700 Terry Lambert [EMAIL PROTECTED] wrote: TL FreeBSD doesn't currently support bank selection. Peter was TL working on it, last time I heard. Linux supports it, at an TL incredible performance penalty. This inspired an off the wall thought that may be insane. Would it be possible (on a 4Gb system) to address 4Gb of RAM and write a driver to make the rest appear as a device, which could then be used for a preferred or (even neater) first level swap. -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
- Original Message - From: Steve Kargl [EMAIL PROTECTED] To: Christian Flügel [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 5:29 PM Subject: Re: upgrade from 4.5 to current fails If you start at 4.5 and upgrade to current, then the installkernel should report kldxref/boot/kernel kldxref: No Such File or Directory ***Error code 1(ignored) Note the Error code 1(ignored). ^^^ I am sure that I am not the only one who is confused by this error message. I overread the (ignored) part of the message and assumend that it was a genuine error. Nothing about this is mentioned in either UPDATING or README and it has cost me about one day to get things straight again. A quick note in UPDATING about this could have saved me a lot of time and energy. But I still get signal 12 exceptions when trying to installworld. It seems to me that the install process still uses my old kernel and I am not able to load the new one. Could anybody please tell me how to achieve this? Regards Christian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Errors in qt30 build
I tried building qt-3 today and it errors with the following: gmake[1]: Entering directory `/usr/ports/x11-toolkits/qt30/work/qt-copy-3.0.3/src' g++ -c -pipe -fno-exceptions -I/usr/local/include -Wall -W -g -pthread -D_THREAD_SAFE -fPIC -DQT_SHARED -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT -DQT_NO_NIS -DQT_NO_IMAGEIO_MNG -DQT_NO_IMAGEIO_JPEG -DQT_BUILTIN_GIF_READER=1 -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_MAC -DQT_NO_STYLE_INTERLACE -DQT_NO_STYLE_COMPACT -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/ports/x11-toolkits/qt30/work/qt-copy-3.0.3/include -I/usr/X11R6/include -I.moc/debug-mt/ -I/usr/ports/x11-toolkits/qt30/work/qt-copy-3.0.3/mkspecs/freebsd-g++ -o .obj/debug-mt/qapplication_x11.o kernel/qapplication_x11.cpp In file included from kernel/qinputcontext_p.h:5, from kernel/qapplication_x11.cpp:77: kernel/qt_x11.h:132: X11/extensions/Xinerama.h: No such file or directory In file included from kernel/qt_x11.h:143, from kernel/qinputcontext_p.h:5, from kernel/qapplication_x11.cpp:77: /usr/X11R6/include/X11/Xft/XftFreetype.h:34: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:37: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:41: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:54: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:71: syntax error before `,' gmake[1]: *** [.obj/debug-mt/qapplication_x11.o] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/qt30/work/qt-copy-3.0.3/src' gmake: *** [sub-src] Error 2 *** Error code 2 I'm running -current (monday build). Any suggestions? Beech -- --- Beech Rintoul - SysAdmin - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Sinbad Network Communications \ / - NO HTML/RTF in e-mail | 3101 Penland Parkway #K-38 X - NO Word docs in e-mail | Anchorage, AK 99508-1957 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: UTF-8 support.
On Wed, Apr 24, 2002 at 10:22:54AM -0600, Kyle Butt [EMAIL PROTECTED] wrote: What's going on as far as adding utf-8 based locales? How can I help? There were some widechar support related imports from CITRUS project as I recall, but all the work seems to be stalled at the moment. I guess it's low priority topic in light of SMP/KSE development and upcoming 5.0 release. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
I tried printing out everything in the trapframe in hex and nothing looke remotely right. Ken On 24 Apr 2002, Brandon S Allbery KF8NH wrote: On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote: Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. My recollection is that beyond 5 arguments, a pointer to the remaining ones is passed. (But my recollection may be wrong and I don't wish to subject myself to the source cesspool at the moment) -- brandon s. allbery [os/2][linux][solaris][japh] [EMAIL PROTECTED] system administrator [WAY too many hats][EMAIL PROTECTED] electrical and computer engineeringKF8NH carnegie mellon university [better check the oblivious first -ke6sls] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Brandon S Allbery KF8NH writes: On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote: Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. My recollection is that beyond 5 arguments, a pointer to the remaining ones is passed. (But my recollection may be wrong and I don't wish to subject myself to the source cesspool at the moment) I think that's how it used to work. Apparently, they've changed it recently and they now pass 6 args in registers. Eg, in the linux kernel sources, old_mmap() fetches its args via copy_from_user(), whereas the newer sys_mmap2() doesn't. Drew Yep, according to the docs and source code I looked at in the linux kernel, the sixth arg is in the ebp register. I've looked all over the FreeBSD kernel and the linux emulator for the place that actually sets these, and unfortunately, due to my lack of asm coding knowledge, I can't find anything. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
libc sets it before it enters the kernel. Then on kernel entry we save ebp in the trapframe. So in the case of linux emulation, the glibc that we're using in the linux-ulator isn't setting it properly? I'm using the linux_base-7 port for this, so as far as I can tell, it should work... assuming linux_base-7 is meant to run on a linux-2.4.x kernel (or kernel that's emulating that). I may have screwed up my linux libs somehow or another too... could this be causing the behavior I'm seeing? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
On 24-Apr-2002 Kenneth Culver wrote: libc sets it before it enters the kernel. Then on kernel entry we save ebp in the trapframe. So in the case of linux emulation, the glibc that we're using in the linux-ulator isn't setting it properly? I'm using the linux_base-7 port for this, so as far as I can tell, it should work... assuming linux_base-7 is meant to run on a linux-2.4.x kernel (or kernel that's emulating that). I may have screwed up my linux libs somehow or another too... could this be causing the behavior I'm seeing? Maybe. You could always try finding the mmap2() entry point and dissassembling it to see what it is doing. Ken -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Spin lock (?) problems with MUTEX_PROFILING
Hi all, I am not generating a false alarm, but I compiled a fresh kernel yesterday with the MUTEX_PROFILING option, and it just went haywire just after the FreeBSD copyright messages and the build info: [ Copyright Info ] [ Build Information ] panic: spin lock mutex profiling lock not in order list I had no idea how to debug this, so I am sending it to the -current list and cc'ing a copy to DES. I am also attaching my kernel configuration file for reference purposes. Thanks -- Hiten Pandya http://storm.uk.FreeBSD.org/~hiten Finger [EMAIL PROTECTED] for PGP public key -- 4FB9 C4A9 4925 CF97 9BF3 ADDA 861D 5DBD E4E3 03C3 # -current Kernel Configuration file # Hiten Pandya machine i386 cpu I686_CPU ident CURRENT5 maxusers500 #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. profile 2 makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols options DEVICE_POLLING #Polling support on devices options UFS_DIRHASH #DIRHASH Support for Kernel options COMPAT_LINUX#Linux Compatibility options PERFMON #Performance Monitories options VESA#Large Splash Screen Support options INET#InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options MD_ROOT #MD is a potential root device options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PSEUDOFS#New PROCFS Framework dependancy! options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] #optionsUSERCONFIG #boot -c editor #optionsVISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Debugging for use in -current options DDB #Enable the kernel debugger options INVARIANTS #Enable calls of extra sanity checking options INVARIANT_SUPPORT #Exta sanity checking. options WITNESS #Enable mutex checks to detect. options MUTEX_DEBUG #Debug Mutexes options MUTEX_PROFILING #Mutex Profiling # Miscelleneous Options options REGRESSION #Regression Testing (needed!) options DONTPROBE_1284 #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O device isa device eisa device pci options PCI_ENABLE_IO_MODES # Enable pci resources left off by a lazy BIOS # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash device sc # SysCon Device device npx # Floating Point Device (not to disable!) device apm # Power Managment Support device pmtimer # Suspend/Resume Timer # Serial (COM) ports #device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device (Strong Cryptography!) device loop# Network loopback device ether # Ethernet support device
Re: implementing linux mmap2 syscall
On 24-Apr-2002 Kenneth Culver wrote: Brandon S Allbery KF8NH writes: On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote: Maybe the argument isn't where you expect it to be, but is there. Can you make a test program which calls mmap2 with its 6th arg as something unique like 0xdeadbeef? Then print out (in hex :) the trapframe from the linux prepsyscall routine see if you can find the deadbeef. My recollection is that beyond 5 arguments, a pointer to the remaining ones is passed. (But my recollection may be wrong and I don't wish to subject myself to the source cesspool at the moment) I think that's how it used to work. Apparently, they've changed it recently and they now pass 6 args in registers. Eg, in the linux kernel sources, old_mmap() fetches its args via copy_from_user(), whereas the newer sys_mmap2() doesn't. Drew Yep, according to the docs and source code I looked at in the linux kernel, the sixth arg is in the ebp register. I've looked all over the FreeBSD kernel and the linux emulator for the place that actually sets these, and unfortunately, due to my lack of asm coding knowledge, I can't find anything. libc sets it before it enters the kernel. Then on kernel entry we save ebp in the trapframe. -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
On Wed, Apr 24, 2002 at 05:49:52PM +0200, Christian Flügel wrote: But I still get signal 12 exceptions when trying to installworld. It seems to me that the install process still uses my old kernel and I am not able to load the new one. Could anybody please tell me how to achieve this? You're still actually running your 4.x kernel. This may be an omission in the documentation for upgrading to 5.0: you need to install the new /boot/defaults/ files so that the boot loader will automatically pick up the changed default location of the 5.0 kernel. Kris msg37646/pgp0.pgp Description: PGP signature
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
Steve O'Hara-Smith wrote: On Mon, 22 Apr 2002 06:04:34 -0700 Terry Lambert [EMAIL PROTECTED] wrote: TL FreeBSD doesn't currently support bank selection. Peter was TL working on it, last time I heard. Linux supports it, at an TL incredible performance penalty. This inspired an off the wall thought that may be insane. Would it be possible (on a 4Gb system) to address 4Gb of RAM and write a driver to make the rest appear as a device, which could then be used for a preferred or (even neater) first level swap. Only if you reserved a window for it. Say 1G of KVA, though last I checked the bank selection granularity wasn't fine enough for that. Memory in the window can *never* be a target for DMA, and should *probably* never be used for kernel structures. If you ever programmed graphics on a TI 99/4A, which has a 4k visible window onto screen memory, or programmed code on the Commodore C64 to use the 32K of RAM-under-ROM, or programmed in DOS or CP/M using Overlays, then you'll be familiar with the problem. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
libc sets it before it enters the kernel. Then on kernel entry we save ebp in the trapframe. So in the case of linux emulation, the glibc that we're using in the linux-ulator isn't setting it properly? I'm using the linux_base-7 port for this, so as far as I can tell, it should work... assuming linux_base-7 is meant to run on a linux-2.4.x kernel (or kernel that's emulating that). I may have screwed up my linux libs somehow or another too... could this be causing the behavior I'm seeing? Ken OK, I removed the linux_base packages that I had on here, and made some changes to the linux-ulator (added the arg[5] = tf-tf_ebp, and then re-installed the linux_base-7.1 package, and now things are working... winex is working fine now. :-) I'll clean up my changes to the linux-ulator, and submit them as a pr. Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
libc sets it before it enters the kernel. Then on kernel entry we save ebp in the trapframe. So in the case of linux emulation, the glibc that we're using in the linux-ulator isn't setting it properly? I'm using the linux_base-7 port for this, so as far as I can tell, it should work... assuming linux_base-7 is meant to run on a linux-2.4.x kernel (or kernel that's emulating that). I may have screwed up my linux libs somehow or another too... could this be causing the behavior I'm seeing? Ken OK, I removed the linux_base packages that I had on here, and made some changes to the linux-ulator (added the arg[5] = tf-tf_ebp, and then re-installed the linux_base-7.1 package, and now things are working... winex is working fine now. :-) I'll clean up my changes to the linux-ulator, and submit them as a pr. I'm actually still not seeing a match between what's in truss, and what's in my printed-out args, but it seems to be working anyway... Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
I'm actually still not seeing a match between what's in truss, and what's in my printed-out args, but it seems to be working anyway... Argh, it's not working again... It was working on an install of ms office, but it won't work on some old windows game.. (winex) and it's still not setting the last arg (or register properly): truss output: linux_mmap2(0x6543,0x10,0x3,0x11,0x9,0x6) = 1698889728 (0x6543) notice that the last arg is 0x6, that's the page offset... what the kernel prints for the same call: mmap2(0x6543, 1048576, 3, 0x0011, 9, 0) notice that they both have all the same values until you get to the last one... at which point the value is wrong... Apparently this only causes problems on some windows programs that one may try to execute, and not on others... So, where can I force this to get set? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
Makoto Matsushita wrote: sgk Note the Error code 1(ignored). That's right, it's not an actual *error*. However, we have seen such a report so many, many times. We may want to consider changing src/sys/conf/kmod.mk to shut it up. Or deleting klxref entirely. If it's ignorable, then the system can function fine without it. If the system can't function fine without it, well, then it's not ignorable. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: panic at shutdown, ums related?
Peter Wemm wrote: USB is pretty hosed. :-( For a while, removing the mouse didn't get detected and you had to kill moused manually. Then the removal event happened. A new moused would start but it was impossible to kill -9 the old moused. If you remove the mouse again, it instantly panics the box. I've not seen what is happening as I've always been in X at the time. :-/ USB hates Mieces to pieces. I've taken to using NetGear based KVM switches, which is not really an option if the problem is with a laptop and/or docking port (sorry), but might be an OK way to deal with peripheral sharing on a desktop, until USB gets fixed. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Here's where it happens:
sys/i386/linux/linux_sysvec.c
static void
linux_prepsyscall(struct trapframe *tf, int *args, u_int *code, caddr_t *params)
{
args[0] = tf-tf_ebx;
args[1] = tf-tf_ecx;
args[2] = tf-tf_edx;
args[3] = tf-tf_esi;
args[4] = tf-tf_edi;
*params = NULL; /* no copyin */
}
You probably want to add:
args[5] = tf-tf_ebp;
so that it ends up in the syscallargs struct.
Yeah, I did that... it still doesn't work, tf_ebp isn't getting set... So
I'm thinking that either I have a glibc that's too old, or something else
is wrong...
For FreeBSD syscalls, we copy this from the top of stack for the number of
32 bit words specified in the syscall table in i386/trap.c:
if (params (i = narg * sizeof(int))
(error = copyin(params, (caddr_t)args, (u_int)i))) {
(narg comes from the syscall table).
OK, that gives me an idea...
Ken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
RCS file: /home/ncvs/src/sys/i386/linux/linux_sysvec.c,v retrieving revision 1.99 diff -u -2 -r1.99 linux_sysvec.c --- linux_sysvec.c 4 Apr 2002 17:49:46 - 1.99 +++ linux_sysvec.c 24 Apr 2002 23:57:23 - @@ -711,4 +711,5 @@ args[3] = tf-tf_esi; args[4] = tf-tf_edi; + args[5] = tf-tf_ebp; *params = NULL; /* no copyin */ } Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message yeah, I did that already, and have been running with that since yesterday :-P still not working right though... I think it has something to do with that nargs thing... I'm checking that out now... Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Kenneth Culver wrote:
Brandon S Allbery KF8NH writes:
On Wed, 2002-04-24 at 10:41, Andrew Gallatin wrote:
Maybe the argument isn't where you expect it to be, but is there.
Can you make a test program which calls mmap2 with its 6th arg as
something unique like 0xdeadbeef? Then print out (in hex :) the trapf
rame
from the linux prepsyscall routine see if you can find the deadbeef.
My recollection is that beyond 5 arguments, a pointer to the remaining
ones is passed. (But my recollection may be wrong and I don't wish to
subject myself to the source cesspool at the moment)
I think that's how it used to work. Apparently, they've changed it
recently and they now pass 6 args in registers. Eg, in the linux
kernel sources, old_mmap() fetches its args via copy_from_user(),
whereas the newer sys_mmap2() doesn't.
Drew
Yep, according to the docs and source code I looked at in the linux
kernel, the sixth arg is in the ebp register. I've looked all over the
FreeBSD kernel and the linux emulator for the place that actually sets
these, and unfortunately, due to my lack of asm coding knowledge, I can't
find anything.
Here's where it happens:
sys/i386/linux/linux_sysvec.c
static void
linux_prepsyscall(struct trapframe *tf, int *args, u_int *code, caddr_t *params)
{
args[0] = tf-tf_ebx;
args[1] = tf-tf_ecx;
args[2] = tf-tf_edx;
args[3] = tf-tf_esi;
args[4] = tf-tf_edi;
*params = NULL; /* no copyin */
}
You probably want to add:
args[5] = tf-tf_ebp;
so that it ends up in the syscallargs struct.
For FreeBSD syscalls, we copy this from the top of stack for the number of
32 bit words specified in the syscall table in i386/trap.c:
if (params (i = narg * sizeof(int))
(error = copyin(params, (caddr_t)args, (u_int)i))) {
(narg comes from the syscall table).
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Cross-platform releases
ru A fast -CURRENT box with root access for make release would be ru highly appreciated. My 500MHz Celeron is too slow for this. snapshots.jp.FreeBSD.org and associate build machines are all P3-500Mhz, not so fast like Celeron 500Mhz... ru There are no syscall issues in my version because I do not do a ru second installworld. Ah, I see, and we cannot do second installworld since it installs 'target' arch's binary :-) ru I estimate that 30% is already done. :-) Great, keep on :-) -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / disklessbooting
In message: [EMAIL PROTECTED] David O'Brien [EMAIL PROTECTED] writes: : The very original solution was to mount NFS / RW. The move to : /conf/default/etc was someone's special needs leaking into the FreeBSD : repository. If you want to special case, things be my guest -- add an : elif test; but leave RW NFS mounted / alone. / should only be mounted RO IFF root_rw_mount is not empty aand doesn't match [Nn][Oo]. We already have a variable for dealing with that. /etc/rc.diskless* shouldn't, as obrien points out, assume a specific setting. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / disklessbooting
In message: [EMAIL PROTECTED] David O'Brien [EMAIL PROTECTED] writes: : On Tue, Apr 23, 2002 at 12:19:58PM -0400, Robert Watson wrote: : diskless_root_readonly=NO # Make it YES for readonly : : good. What's wrong with the current root_rw_mount knob? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: 005e01c1eb13$cce043c0$594bfea9@bender
[EMAIL PROTECTED] (Christian Flügel) writes:
: - Original Message -
: From: Eric Brunner-Williams in Portland Maine [EMAIL PROTECTED]
: To: Christian Flügel [EMAIL PROTECTED]
: Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
: Sent: Tuesday, April 23, 2002 11:55 PM
: Subject: Re: upgrade from 4.5 to current fails
:
:
: Yeah. I picked those up too -- the signal 12 @ the install phase of
: chfoo.
: I also got another shell failure when doing the depend phase of the kernel
: build, but since I don't care what is in vers.c, and I don't care about
: the
: chfoo set of utilities, I cheerfully continued.
:
: It is strange that nothing is mentioned in either UPDATING or README about
: these problems.
That's because if you were following the instructions in UPDATING:
To upgrade from 4.x-stable to current
-
make buildworld
make buildkernel KERNCONF=YOUR_KERNEL_HERE
cp src/sys/${MACHINE_ARCH}/conf/GENERIC.hints /boot/device.hints [2]
make installkernel KERNCONF=YOUR_KERNEL_HERE
reboot in single user [3]
mergemaster -p [5]
make installworld
mergemaster [4]
[1]
reboot
you wouldn't have these problems. :-)
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: [EMAIL PROTECTED] Makoto Matsushita [EMAIL PROTECTED] writes: : : sgk Note the Error code 1(ignored). : : That's right, it's not an actual *error*. : : However, we have seen such a report so many, many times. We may want : to consider changing src/sys/conf/kmod.mk to shut it up. Something like the following maybe: Index: kmod.mk === RCS file: /cache/ncvs/src/sys/conf/kmod.mk,v retrieving revision 1.117 diff -u -r1.117 kmod.mk --- kmod.mk 22 Apr 2002 15:53:04 - 1.117 +++ kmod.mk 25 Apr 2002 01:56:43 - @@ -166,6 +166,9 @@ .endif .endif +.if !exists(/usr/sbin/kldxref) +NO_XREF=yes +.endif .if !target(all-man) all-man: _SUBDIR To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: 001e01c1eba7$ad27ff70$594bfea9@bender [EMAIL PROTECTED] (Christian Flügel) writes: : - Original Message - : From: Steve Kargl [EMAIL PROTECTED] : To: Christian Flügel [EMAIL PROTECTED] : Cc: [EMAIL PROTECTED] : Sent: Wednesday, April 24, 2002 5:29 PM : Subject: Re: upgrade from 4.5 to current fails : : : If you start at 4.5 and upgrade to current, then the : installkernel should report : :kldxref/boot/kernel :kldxref: No Such File or Directory : :***Error code 1(ignored) : : Note the Error code 1(ignored). : ^^^ : : I am sure that I am not the only one who is confused by this error message. : I overread the (ignored) part of the message and assumend that it was a : genuine error. Nothing about this is mentioned in either UPDATING or README : and it has cost me about one day to get things straight again. A quick note : in UPDATING about this could have saved me a lot of time and energy. : : But I still get signal 12 exceptions when trying to installworld. : It seems to me that the install process still uses my old kernel and I am : not able to load the new one. Could anybody please tell me how to achieve : this? Did you reboot with the new kernel into single user mode first? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: [EMAIL PROTECTED] Kris Kennaway [EMAIL PROTECTED] writes: : On Wed, Apr 24, 2002 at 05:49:52PM +0200, Christian Flügel wrote: : : But I still get signal 12 exceptions when trying to installworld. : It seems to me that the install process still uses my old kernel and I am : not able to load the new one. Could anybody please tell me how to achieve : this? : : You're still actually running your 4.x kernel. This may be an : omission in the documentation for upgrading to 5.0: you need to : install the new /boot/defaults/ files so that the boot loader will : automatically pick up the changed default location of the 5.0 kernel. Are you sure you need to do that by hand? When I upgraded my laptop I didn't need to do that. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: implementing linux mmap2 syscall
Alright, so I got tired of trying to figure out if glibc is doing something wierd or wrong so I downloaded the source for it, and I'm looking at it now... (for version 2.2.2 which is what we have on FreeBSD's linux_base-7) and here's what I'm seeing: pushl %ebp pushl %ebx pushl %esi pushl %edi movl OFFLO(%esp), %edx movl OFFHI(%esp), %ecx testl $0xfff, %edx jne L(einval) shrdl $12, %ecx, %edx /* mmap2 takes the offset in pages. */ shrl $12, %ecx jne L(einval) movl %edx, %ebp So above I'm seeing the offset arg get into register %ebp, which is what we expect... movl ADDR(%esp), %ebx movl LEN(%esp), %ecx movl PROT(%esp), %edx movl FLAGS(%esp), %esi movl FD(%esp), %edi Then I'm seeing all the other args getting put into the registers they belong in... (which matches up with our linux_prepsyscall() function) movl $SYS_ify(mmap2), %eax /* System call number in %eax. */ /* Do the system call trap. */ L(do_syscall): int $0x80 Now I'm seeing the int 0x80 trap /* Restore registers. */ popl %edi popl %esi popl %ebx popl %ebp So, as far as I can tell, this version of glibc is doing the Right Thing, and the ebp register is getting messed up somewhere along the line in either the assembly code that handles the 0x80 trap in FreeBSD, or in syscall2 (I think it's probably the asm that handles the 0x80 trap)... Can anyone confirm this? Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: 004d01c1eb8a$bfadfef0$594bfea9@bender [EMAIL PROTECTED] (Christian Flügel) writes: : solved the problem. Maybe this should be put in UPDATING? I've added a note to the effect that you can safely ignore this warning. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 5.0 Developer Preview #1 Now Available / diskless booting
Danny, What do you think about doing a little more polishing and rolling a new set of patches taking this /etc/rc.conf option into account? Your kernel env dhcp variables are really good. I know that many do want to do what you are doing (large scale RO /); but up until now /etc/rc.diskless* has not been well engineered. On Wed, Apr 24, 2002 at 07:44:20PM -0600, M. Warner Losh wrote: : The very original solution was to mount NFS / RW. The move to : /conf/default/etc was someone's special needs leaking into the FreeBSD : repository. If you want to special case, things be my guest -- add an : elif test; but leave RW NFS mounted / alone. / should only be mounted RO IFF root_rw_mount is not empty aand doesn't match [Nn][Oo]. We already have a variable for dealing with that. /etc/rc.diskless* shouldn't, as obrien points out, assume a specific setting. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
On Wed, Apr 24, 2002 at 07:58:42PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] Kris Kennaway [EMAIL PROTECTED] writes: : On Wed, Apr 24, 2002 at 05:49:52PM +0200, Christian Flügel wrote: : : But I still get signal 12 exceptions when trying to installworld. : It seems to me that the install process still uses my old kernel and I am : not able to load the new one. Could anybody please tell me how to achieve : this? : : You're still actually running your 4.x kernel. This may be an : omission in the documentation for upgrading to 5.0: you need to : install the new /boot/defaults/ files so that the boot loader will : automatically pick up the changed default location of the 5.0 kernel. Are you sure you need to do that by hand? When I upgraded my laptop I didn't need to do that. Does installkernel do this already? Otherwise I can't see how the updated loader.conf gets into /boot/defaults by this point in the instructions. Kris msg37671/pgp0.pgp Description: PGP signature
Re: upgrade from 4.5 to current fails
Oh, wait, I see the chicken and egg that you are talking about... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
In message: [EMAIL PROTECTED]
Kris Kennaway [EMAIL PROTECTED] writes:
: On Wed, Apr 24, 2002 at 07:58:42PM -0600, M. Warner Losh wrote:
: In message: [EMAIL PROTECTED]
: Kris Kennaway [EMAIL PROTECTED] writes:
: : On Wed, Apr 24, 2002 at 05:49:52PM +0200, Christian Flügel wrote:
: :
: : But I still get signal 12 exceptions when trying to installworld.
: : It seems to me that the install process still uses my old kernel and I am
: : not able to load the new one. Could anybody please tell me how to achieve
: : this?
: :
: : You're still actually running your 4.x kernel. This may be an
: : omission in the documentation for upgrading to 5.0: you need to
: : install the new /boot/defaults/ files so that the boot loader will
: : automatically pick up the changed default location of the 5.0 kernel.
:
: Are you sure you need to do that by hand? When I upgraded my laptop I
: didn't need to do that.
:
: Does installkernel do this already? Otherwise I can't see how the
: updated loader.conf gets into /boot/defaults by this point in the
: instructions.
No. But installworld does in sys/boot/${ARCH}/Makefile seems to do
so.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: upgrade from 4.5 to current fails
- Original Message - From: Kris Kennaway [EMAIL PROTECTED] To: Christian Flügel [EMAIL PROTECTED] Cc: Steve Kargl [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, April 25, 2002 1:20 AM Subject: Re: upgrade from 4.5 to current fails You're still actually running your 4.x kernel. This may be an omission in the documentation for upgrading to 5.0: you need to install the new /boot/defaults/ files so that the boot loader will automatically pick up the changed default location of the 5.0 kernel. Thanks now everything is working fine. Regards Christian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: FreeBSD 4.5-STABLE not easily scalable to large servers ... ?
On Wed, 24 Apr 2002 16:38:08 -0700 Terry Lambert [EMAIL PROTECTED] wrote: TL Only if you reserved a window for it. Say 1G of KVA, though last I was thinking more like 1M, or even a few K, it sounds like that's not possible. TL I checked the bank selection granularity wasn't fine enough for That would be a problem. TL If you ever programmed graphics on a TI 99/4A, which has a 4k TL visible window onto screen memory, or programmed code on the I've done a number of similar things (Newbrain, Lynx, bank switched CP/M ...). -- C:WIN | Directable Mirrors The computer obeys and wins.|A Better Way To Focus The Sun You lose and Bill collects. | licenses available - see: | http://www.sohara.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Errors in qt30 build
On Wed, Apr 24, 2002 at 10:58:39AM -0800, Beech Rintoul wrote: from kernel/qapplication_x11.cpp:77: /usr/X11R6/include/X11/Xft/XftFreetype.h:34: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:37: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:41: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:54: syntax error before `;' /usr/X11R6/include/X11/Xft/XftFreetype.h:71: syntax error before `,' gmake[1]: *** [.obj/debug-mt/qapplication_x11.o] Error 1 gmake[1]: Leaving directory `/usr/ports/x11-toolkits/qt30/work/qt-copy-3.0.3/src' gmake: *** [sub-src] Error 2 *** Error code 2 I had same problem, but after rebuilding freetype2 all looks good, except that gcc hangs with internal compiler error while building arts port -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
