Syscalls.master broken on -CURRENT?
During the compilation of usr.bin/truss this error stops world: syscalls.master: line 55: syscall number out of sync at 7 line is: struct rusage * rusage ) ; } wait4 wait_args int The error is actually produced by the execution of '/usr/src/sys/kern/makesyscalls.sh syscalls.master' I see that syscalls.master and related files were changed on June 13. What I don't understand is why this same error breaks world on one of my -CURRENT machines but not on the other machine. If I execute the shellscript by hand on either machine the error message is the same. Strange. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Syscalls.master broken on -CURRENT?
During the compilation of usr.bin/truss this error stops world: syscalls.master: line 55: syscall number out of sync at 7 line is: struct rusage * rusage ) ; } wait4 wait_args int The error is actually produced by the execution of '/usr/src/sys/kern/makesyscalls.sh syscalls.master' What I don't understand is why this same error breaks world on one of my -CURRENT machines but not on the other machine... Try this: # cd /usr/src/usr.bin/truss # make clean # make I think you will see the error appear. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Entschuldigen Sie bitte die Störung!
Entschuldigen Sie bitte die Störung! Mir ist etwas zu Ohren gekommen. Eine relativ aussergewöhnliche Gerüchteküche, aus der man mir ein schwerverdauliches Süppchen vorgesetzt hat, ist der Grund meiner Mail. Unappetitlich ist gar kein Ausdruck! Ist es möglich auf funktechnischem Wege(in welchen Frequenzbereichen?) jemanden zu beeinflussen oder zu manipulieren? Oder sogar zu schikanieren und terrorisieren? Unter dem Motto:Einen am Sender?Nich ganz alleine? Kleine Mannim Ohr?Falsche Wellenlänge?Bohnen in den Ohren? Auf den Zahn gefühlt(Amalgam)?Mal unverbindlich reinhören? Der Pullacher Wanzentanz? Ist das Spinnerei?Das geht doch gar nicht,oder? Und wenn wie sieht das ethisch moralisch aus? Zur technischen Seite der Sache gibt es zwar Berichte und Webseiten: Totalitaer,de - Die Waffe gegen die Kritik http://www.fosar-bludorf.com/Tempelhof/ http://jya.com/haarp.htm http://www.zeitenschrift.at/magazin/zs_24_15/1_mikrowaffen.htm http://www.bse-plus.de/d/doc/lbrief/lbmincontr.htm http://home.nexgo.de/kraven/bigb/big3.html http://w3.nrl.navy.mil/projects/haarp/index.html http://cryptome.org/ http://www.parascope.com/ds/mkultra0.htm http://www.trufax.org/menu/mind.html http://www.trufax.org/menu/elect.html http://mindcontrolforum.com/ http://www.trufax.org/menu/elect.html usw. usw. usw. ,aber,das kann doch nicht sein,das soetwas gemacht wird,oder? Eine Menschenrechtsverletzung sonder gleichen!?! Ist es möglich,durch Präparation,der Ohren und im Zusammenspiel mit eventuell vorhandenem Zahnersatz? Mit relativ einfacher Funktechnik?? In diesem Land?Hier und heute??? Unter welchen Motiven? Wo ist eigentlich die Abteilung 5 des BND und des Verfassungsschutzes? Kann es sein,daß es Leute gibt,die dem BND/Verfassungsschutz,auf funktechnischem Wege permanent einen Situationsbericht abliefern,ohne es selbst zu merken,im Kindesalter machbar gemacht?? Werden durch solche inoffiziellen Mitarbeiter,beim BND und Verfassungsschutz,nach Stasimanier, Informationen von und über,rein theoretisch, jeden Bundesbürger,gesammelt? Gibt es dann noch ein Recht auf Privatsphere? Wer kontrolliert eigentlich den BND,MAD und Verfassungsschutz auf Unterwanderung??? In der Mail geht es mir eigentlich um die Frage,ob es kriminellen Elementen, aus dem Motiv der Bereicherung,oder Gruppierungen aus ideologischen Motiven, möglich ist ,sich Wissen und Technik anzueignen,die zu anderen Zeiten, aus anderen Motiven(Westfernsehen?),entwickelt wurde. Und stellt der technische Wissensstand, der der Allgemeinheit bekannt ist wirklich das Ende der Fahnenstange dar? Ist es denn nicht kriminellen Elementen genauso möglich, ich sage das jetzt mal verharmlost und verniedlichend, einzelne Personen oder Gruppen mit relativ einfachen Mitteln, aus welchen Motiven auch immer, auszuspionieren? Und stellt diese Ausspioniererei nicht einen erheblichen Eingriff in die Privatsphäre dar? Ist es möglich einzelne Personen oder Gruppen, eine Akzeptans einer gewissen Öffentlichkeit(suggeriert?), die z.B. mit Hilfe von Internetseiten,wie zum Beispiel dem Prangergeschaffen werden könnte, mal vorausgestzt,zu terroriesieren und oder zu schikanieren, und das in aller (suggerierten)Öffentlichkeit?Haben die Leute die da am Pranger, oder auf irgendeiner anderen Seite verunglimpft,oder gar Verleumdet werden, eigentlich eine Chance zur Gegenöffentlichkeit?Ist das nicht Rufmord? Vor einigen Jahren bin ich per Zufall auf die Seite Der Pranger gestoßen, damals lief das noch nicht unter dem Deckmantel der Partnervermittlung. Können sich einzelne Personen,oder Interessengemeinschaften, aus reinem Selbstzweck,solcher Seiten bedienen, um unter dem Deckmantel einer fragwürdigen Zivilkourage, durch anzetteln irgendwelcher Hetzkampagnen,eigene, ganz persöhnliche Interessen durchsetzen? Können solche Seiten zur Koordination von kriminellen machenschaften dienen? Die Frage,ist es Möglichkeit oder Unmöglichkeit,technisch und gesellschaftlich, einzelne Personen,oder auch Gruppierungen,aus einer kriminellen/ideologischen Energei heraus,zu manipulieren oder zu beeinflussen,terrorisieren oder zu schickanieren,und zwar gezielt. Zielgruppenmanipulation durch Massenmedien sind alltägliche Manipulation, der mansich,mehr oder weniger,entziehen kann. Wird das Recht auf Privatsphäre,schleichend,tiefenpsychologisch, durch Sendungen,wie,zum Beispiel Big brother,untergraben? Sollte bei einem der Angemailten ein gewisser Wissensstand zum Thema vorhanden sein, wäre ich über Hinweise zum Thema froh. Auf der Suche nach Antworten auf meine Fragen maile ich verschiedene Adressen aus dem Internet an, und hoffe aufkonstruktive Antworten und Kritiken. Über einen Besuch auf der Seite http://hometown.aol.de/reinerhohn38259/homepage/index.html würde ich mich freuen. Sollten Sie von mir mehrfach angeschrieben worden sein,so bitte ich Sie,mir dies zu entschuldigen, das war nicht beabsichtigt. Der Grund für meine Anonymität ist die Tatsache, daß bei derlei Fragenstellerei, verständlicherweise,schnell der Ruf nach der
RE: Syscalls.master broken on -CURRENT?
On Sat, 15 Jun 2002, walt wrote: During the compilation of usr.bin/truss this error stops world: syscalls.master: line 55: syscall number out of sync at 7 line is: struct rusage * rusage ) ; } wait4 wait_args int The error is actually produced by the execution of '/usr/src/sys/kern/makesyscalls.sh syscalls.master' What I don't understand is why this same error breaks world on one of my -CURRENT machines but not on the other machine... Try this: # cd /usr/src/usr.bin/truss # make clean # make I think you will see the error appear. s/appear/disappear/? It basically looks like the generated include files aren't in sync, but it's not something I can reproduce locally. Lots of make cleaning and make includes should clear this up. If it doesn't, let me know, and I'll do more chasing. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
HEADS UP: prefix(8) and gifconfig(8) are obsoleted.
Hi,
I committed to don't install prefix(8) and gifconfig(8). ifconfig(8)
has the facilities provided by these commands. Please use
ifconfig(8).
gifconfig - ifconfig tunnel/deletetunnel
prefix- ifconfig eui64
I'll do cvs remove after a mean time.
I have no plan to MFC this due to backward compatibility issue.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
[EMAIL PROTECTED] [EMAIL PROTECTED] ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Fri, 14 Jun 2002, Danny Braniss wrote: in amd, # REQUIRE: rpcbind mountall ypbind nfsclient ** since i don't use yp, how can i override this? or in other words, can REQUIRE be configurable too? This isn't a hard requirement for starting, but instead a hint for ordering the startup of the system. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Sat, 15 Jun 2002, Greg 'groggy' Lehey wrote: Hmm, appears to be Luke Mewburn's NetBSD stuff, which I know. Shouldn't there be an Obtained From: NetBSD in the commit messages? Heh, sorry about that. I thought taking if off the NETBSD vendor branch was enough of a hint. It appears that I should have been much more specific with my commit message. My apologies on that. Are you (or is anybody) doing something about keeping as close as possible to being in sync with NetBSD? If I am correct (Mike will correct me if I'm wrong), we are caught up with NetBSD with this commit. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Fri, 14 Jun 2002, Terry Lambert wrote: Mike Makonnen wrote: Danny Braniss [EMAIL PROTECTED] wrote: in amd, # REQUIRE: rpcbind mountall ypbind nfsclient ** since i don't use yp, how can i override this? or in other words, can REQUIRE be configurable too? The REQUIRE line doesn't mean it will be started. It just means that ypbind comes before amd in the boot process. Ick. What should be used instead of REQUIRE to mean that it will be started? I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? I don't like this design decision either. I have a couple of ideas on how to get rid of rcorder completely and bring the dependency checking into the script itself (complete with the notion of hard and soft dependencies). I was thinking of coming up with a way to make dynamic dependency registration and coming up with a reverse and forward dependency tree so if you stop nfsd, it would make a call to mountd to see if there was anything still using nfsd. If there weren't any more dependencies, it would then stop mountd (that could be a bit risky though, depending on the completeness of the dependency tree). -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More X breakage in XFree86-4-Servers ...
Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src. *** Error code 1 I'm getting this as well. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
alpha tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/alpha/obj/tmp/des/src/alpha/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Sat Jun 15 12:09:51 PDT 2002 -- === GENERIC config: Error: device mpt is unknown FYI: static unit limits for pci are set: NPCI=1 FYI: static unit limits for ppp are set: NPPP=1 FYI: static unit limits for atkbdc are set: NATKBDC=1 FYI: static unit limits for sc are set: NSC=1 *** Error code 1 Stop in /tmp/des/src. *** Error code 1 Stop in /tmp/des/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote: I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? Why the need to distingish? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
Bruce Evans wrote: This is a bug in bsd.kern.mk. -ffreestanding never belonged there, since it is also needed for modules and perhaps for boot programs and libstand. Module makefiles still include bsd.kern.mk, but Makefiles for boot programs have regressed. Your x86 box must be out of date. x86 has gcc-3 and adds -ffreestanding unconditionally, so -ffreestanding is added twice for all arches. I have been using the following fix since this bug was committed. What exactly does this do, besides implying -fno-builtin? The documentation says and implies main has no special requirements... Neither the kernel nor modules have a main, so the only thing that's relevent here is the -fno-builtin, right? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
Terry Lambert wrote: What exactly does this do, besides implying -fno-builtin? The documentation says and implies main has no special requirements... Neither the kernel nor modules have a main, so the only thing that's relevent here is the -fno-builtin, right? IIRC, -ffreestanding prevented GCC3 from being stupid optimizations like changing occurences of printf(constant string\n) to puts(constant string), which failed for kernel builds since we don't have puts() in the kernel... Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
David O'Brien wrote: On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote: I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? Why the need to distingish? Otherwise circular dependencies. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ESS sound card support on laptop
I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote: I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org Does it not work with the maestro driver? Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
Maxime Henrion wrote: Terry Lambert wrote: What exactly does this do, besides implying -fno-builtin? The documentation says and implies main has no special requirements... Neither the kernel nor modules have a main, so the only thing that's relevent here is the -fno-builtin, right? IIRC, -ffreestanding prevented GCC3 from being stupid optimizations like changing occurences of printf(constant string\n) to puts(constant string), which failed for kernel builds since we don't have puts() in the kernel... That is an incredibly *fugly* optimization. It assumes that I use libc, unless I have -ffreestanding, and it assumes my implementation of printf vs. puts. It sounds like -ffreestanding -fbuiltin should be the default for everything but the kernel, which should not have -fbuiltin... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 01:52:16PM -0600, Scott Long wrote: On Sat, Jun 15, 2002 at 02:52:33PM -0500, David W. Chapman Jr. wrote: I have the following sound card on my laptop, does anyone know how hard it would be to add this card to the pcm driver. none2@pci0:14:0:class=0x040100 card=0x2550107b chip=0x1978125d rev=0x10 hdr=0x00 vendor = 'ESS Technology' device = 'ES1978 Maestro-2E Audiodrive, ES1970 Canyon3D' class= multimedia subclass = audio Does it not work with the maestro driver? It does. Mark -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
On Sat, 15 Jun 2002 12:49:29 -0700, Maxime Henrion [EMAIL PROTECTED] said: IIRC, -ffreestanding prevented GCC3 from being stupid optimizations like `-ffreestanding' tells the compiler that it is to operate as a free-standing implementation (in the words of the C standard); i.e., that there is no Standard C Library, and the compiler may not assume that a function which has the same name as a Standard Library function has the same semantics. -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : pcm0: unable to map register space : device_probe_and_attach: pcm0 attach returned 6 FreeBSD should, but isn't, assign resources to PCI devices. In the past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : pcm0: unable to map register space : device_probe_and_attach: pcm0 attach returned 6 FreeBSD should, but isn't, assign resources to PCI devices. In the past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) So if you have a machine without any MS software installed, and have thereby denied the opportunity for MS to migrate this functionality into the OS, how does it get migrated? -- TErry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
past, the BIOS has done this, but MS has migrated this functionality into the OS. That's why you see a lot of these sorts of failures with various kludges in the FreeBSD tree. That's part of what I was talking about in the developers conference when I said we needed to make PCI work again :-) Wel I look forward to this if it fixes my sound and linksys card :) -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] Terry Lambert [EMAIL PROTECTED] writes: : M. Warner Losh wrote: : In message: [EMAIL PROTECTED] : David W. Chapman Jr. [EMAIL PROTECTED] writes: : : pcm0: ESS Technology Maestro-2E irq 5 at device 14.0 on pci0 : : pcm0: unable to map register space : : device_probe_and_attach: pcm0 attach returned 6 : : FreeBSD should, but isn't, assign resources to PCI devices. In the : past, the BIOS has done this, but MS has migrated this functionality : into the OS. That's why you see a lot of these sorts of failures with : various kludges in the FreeBSD tree. That's part of what I was : talking about in the developers conference when I said we needed to : make PCI work again :-) : : So if you have a machine without any MS software installed, and : have thereby denied the opportunity for MS to migrate this : functionality into the OS, how does it get migrated? We write it. It isn't in the BIOS anymore. Usually with ACPI. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
We write it. It isn't in the BIOS anymore. Usually with ACPI. Now that msmith left, do we have any acpi gurus? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Sat, 15 Jun 2002 12:49:52 -0700 Terry Lambert [EMAIL PROTECTED] wrote: David O'Brien wrote: On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote: I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? Why the need to distingish? Otherwise circular dependencies. That's what rcorder(8) is there for. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
Mike Makonnen wrote: On Sat, 15 Jun 2002 12:49:52 -0700 Terry Lambert [EMAIL PROTECTED] wrote: David O'Brien wrote: On Fri, Jun 14, 2002 at 03:30:19PM -0700, Terry Lambert wrote: I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? Why the need to distingish? Otherwise circular dependencies. That's what rcorder(8) is there for. It's not that simple. The most obvious example is the need to use DNS in order to look up syslog hosts, and whether you start syslogd before you start DNS, if DNS needs to syslog errors. Since the DNS information is only used by syslogd when actual logging to a remote host takes place, it should be possible to say that syslog has a soft dependency on DNS, and DNS has a hard dependency on syslog. Similar arguments can be made about sendmail, but the example is less obvious, since it involves local configuration, and the mailing of things like cron job output. In fact, any daemon you run will import N services and export M services. The natural rendesvous is actually on the dependency on a particular service, as opposed to dependency on a psrticular set of code implementing a service (e.g. it's a seperate program in DJBDNS to export TCP based DNS services and/or DNSXFR services, and there are many programs that can export HTTP services on port 80 or SMTP services on port 25 or POP3 services on port 110). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
M. Warner Losh wrote: : FreeBSD should, but isn't, assign resources to PCI devices. In the : past, the BIOS has done this, but MS has migrated this functionality : into the OS. That's why you see a lot of these sorts of failures with : various kludges in the FreeBSD tree. That's part of what I was : talking about in the developers conference when I said we needed to : make PCI work again :-) : : So if you have a machine without any MS software installed, and : have thereby denied the opportunity for MS to migrate this : functionality into the OS, how does it get migrated? We write it. It isn't in the BIOS anymore. Usually with ACPI. That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. I'm not sure I understand if you're referring to me. I haven't blamed MS or even mentioned MS. If I understand warner correctly, it can be solved by working on ACPI. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : We write it. It isn't in the BIOS anymore. Usually with ACPI. : Now that msmith left, do we have any acpi gurus? There are many japanese that are expert at this. I had plans on taking up at least some familiarity with the ACPI code because it directly impacts a usable cardbus subsystem. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
In message: [EMAIL PROTECTED] Terry Lambert [EMAIL PROTECTED] writes: : That was kind of my point to David: blaming MS doesn't make FreeBSD : work. At some point, you have to accept that the problem is yours, : rather than being caused by some outside agency. Actually, it was caused by MS moving the BIOS resource assignment into the OS. We have had forever to deal and just haven't. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ESS sound card support on laptop
On Sat, Jun 15, 2002 at 05:07:53PM -0600, M. Warner Losh wrote: In message: [EMAIL PROTECTED] David W. Chapman Jr. [EMAIL PROTECTED] writes: : We write it. It isn't in the BIOS anymore. Usually with ACPI. : Now that msmith left, do we have any acpi gurus? There are many japanese that are expert at this. I had plans on taking up at least some familiarity with the ACPI code because it directly impacts a usable cardbus subsystem. The rumor I heard is that their english isn't that good so that I might not be able to communicate with them, english being the only language I know. I would be glad to contact them if this isn't the case, but Im not sure exactly who they are. -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More X breakage in XFree86-4-Servers ...
On Sat, Jun 15, 2002 at 01:39:08PM -0500, David W. Chapman Jr. wrote: Please submit a full bug report, with preprocessed source if appropriate. See URL:http://www.gnu.org/software/gcc/bugs.html for instructions. *** Error code 1 Stop in /usr/local/ports/usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/GL/mesa/src. *** Error code 1 I'm getting this as well. Has anyone actually submitted a bug report to GCC yet? Kris msg39666/pgp0.pgp Description: PGP signature
Re: ESS sound card support on laptop
David W. Chapman Jr. wrote: That was kind of my point to David: blaming MS doesn't make FreeBSD work. At some point, you have to accept that the problem is yours, rather than being caused by some outside agency. I'm not sure I understand if you're referring to me. I haven't blamed MS or even mentioned MS. If I understand warner correctly, it can be solved by working on ACPI. It was a point to you, but the statement was Warner's. It was your reaction that I was reacting to... 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: More X breakage in XFree86-4-Servers ...
Has anyone actually submitted a bug report to GCC yet? I don't believe so. I'm not sure exactly what is broken or the circumstances that cause the problem. My lack of c knowledge is preventing me from saying much more than X-Servers won't build. Would you be willing to help me figure out what is going on so I can file a proper report or were you offering to file it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: prefix(8) and gifconfig(8) are obsoleted.
On Sun, Jun 16, 2002 at 03:14:17AM +0900, Hajimu UMEMOTO wrote: I committed to don't install prefix(8) and gifconfig(8). ifconfig(8) has the facilities provided by these commands. Please use ifconfig(8). gifconfig - ifconfig tunnel/deletetunnel prefix- ifconfig eui64 I'll do cvs remove after a mean time. I have no plan to MFC this due to backward compatibility issue. After RELENG_4 is unfrozen, it would probably be a good idea to modify these utilities to warn of their obsolesence when run to try and get people to switch now. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg39669/pgp0.pgp Description: PGP signature
Re: HEADS UP: rc.d is in the tree
On Saturday, 15 June 2002 at 11:30:08 -0700, Gordon Tetlow wrote: On Fri, 14 Jun 2002, Terry Lambert wrote: Mike Makonnen wrote: Danny Braniss [EMAIL PROTECTED] wrote: in amd, # REQUIRE: rpcbind mountall ypbind nfsclient ** since i don't use yp, how can i override this? or in other words, can REQUIRE be configurable too? The REQUIRE line doesn't mean it will be started. It just means that ypbind comes before amd in the boot process. Ick. What should be used instead of REQUIRE to mean that it will be started? I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? I don't like this design decision either. I have a couple of ideas on how to get rid of rcorder completely and bring the dependency checking into the script itself (complete with the notion of hard and soft dependencies). Are you talking with lukem about this? It would be nice to stay as compatible as possible. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
From: [EMAIL PROTECTED] (Terry Lambert) Date: Sat 15 Jun, 2002 Subject: Re: duplicate -ffreestanding in kernel build That is an incredibly *fugly* optimization. It assumes that I use libc, unless I have -ffreestanding, and it assumes my implementation of printf vs. puts. It means you can't futz with the implementation of the standard library in a standard way. :-) Cheers, Mark. -- Mark Valentine, Thuvia Labs [EMAIL PROTECTED] http://www.thuvia.co.uk Tigers will do ANYTHING for a tuna fish sandwich. Mark Valentine uses We're kind of stupid that way. *munch* *munch*and endorses FreeBSD -- http://www.calvinandhobbes.com http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Zsh dumps core after cap_get_proc() removal
Hello Robert Watson, After removal of cap_get_proc() and friends from libc, zsh from the ports started to dump core: $ zsh [1] 7477 Bad system call (core dumped) zsh $ $ gdb /usr/local/bin/zsh zsh.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... Core was generated by `zsh'. Program terminated with signal 12, Bad system call. Reading symbols from /usr/local/lib/zsh/libzsh-4.0.4.so... (no debugging symbols found)...done. Reading symbols from /usr/lib/libncurses.so.5...(no debugging symbols found)...done. Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libc.so.5...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x28172333 in __sys___cap_get_proc () from /usr/lib/libc.so.5 (gdb) where #0 0x28172333 in __sys___cap_get_proc () from /usr/lib/libc.so.5 #1 0x2816003e in cap_get_proc () from /usr/lib/libc.so.5 #2 0x280ca331 in privasserted () from /usr/local/lib/zsh/libzsh-4.0.4.so #3 0x28080099 in evalcond () from /usr/local/lib/zsh/libzsh-4.0.4.so #4 0x2807e5d7 in bin_test () from /usr/local/lib/zsh/libzsh-4.0.4.so #5 0x280754ea in execbuiltin () from /usr/local/lib/zsh/libzsh-4.0.4.so #6 0x28085236 in execsubst () from /usr/local/lib/zsh/libzsh-4.0.4.so #7 0x280828b9 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #8 0x28081fa3 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #9 0x28081a33 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #10 0x2809f269 in execif () from /usr/local/lib/zsh/libzsh-4.0.4.so #11 0x28085049 in execsubst () from /usr/local/lib/zsh/libzsh-4.0.4.so #12 0x280828b9 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #13 0x28081fa3 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #14 0x28081a33 in execlist () from /usr/local/lib/zsh/libzsh-4.0.4.so #15 0x280817b6 in execode () from /usr/local/lib/zsh/libzsh-4.0.4.so #16 0x28093f68 in loop () from /usr/local/lib/zsh/libzsh-4.0.4.so #17 0x28095c24 in source () from /usr/local/lib/zsh/libzsh-4.0.4.so #18 0x28095e55 in sourcehome () from /usr/local/lib/zsh/libzsh-4.0.4.so #19 0x280958ff in run_init_scripts () from /usr/local/lib/zsh/libzsh-4.0.4.so #20 0x2809663d in zsh_main () from /usr/local/lib/zsh/libzsh-4.0.4.so #21 0x804854f in exit () #22 0x8048495 in exit () (gdb) $ I had to manually disable HAVE_CAP_GET_PROC in config.h for zsh. Can't we have some kind of HEADS-UP or version-bump for this matter. Thank you, Haro =-- _ _Munehiro (haro) Matsuda -|- /_\ |_|_| Business Incubation Dept., Kubota Corp. /|\ |_| |_|_| 1-3 Nihonbashi-Muromachi 3-Chome Chuo-ku Tokyo 103-8310, Japan Tel: +81-3-3245-3318 Fax: +81-3-3245-3315 Email: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
On Sat, 15 Jun 2002, Terry Lambert wrote: Maxime Henrion wrote: Terry Lambert wrote: What exactly does this do, besides implying -fno-builtin? The documentation says and implies main has no special requirements... Neither the kernel nor modules have a main, so the only thing that's relevent here is the -fno-builtin, right? IIRC, -ffreestanding prevented GCC3 from being stupid optimizations like ^^ smart changing occurences of printf(constant string\n) to puts(constant string), which failed for kernel builds since we don't have puts() in the kernel... That is an incredibly *fugly* optimization. It assumes that I use libc, unless I have -ffreestanding, and it assumes my implementation of printf vs. puts. This is a routine optimization. It assumes that you use a C compiler (printf and even libc might not exist, since they might be builtins). A non-routine optimization might involve building hardware to run the application and emitting the 1 bit instruction to turn the hardware on. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[PATCH] sed is broken in -CURRENT
After the recent round of -i fixes to sed, certain ports will no longer
make configure (gaim being a prime example). The problem is that
mf_fgets() is unnecessarily overwriting sp-len. The attached patch
corrects the problem while still allowing -i to work on multiple files.
As a ports committer, I can't do anything but let you guys (and gals)
know. Thanks.
Joe
diff -u -r1.23 main.c
--- usr.bin/sed/main.c 2002/06/14 02:20:05 1.23
+++ usr.bin/sed/main.c 2002/06/16 04:38:31
-315,7 +315,8
firstfile = 1;
}
- sp-len = 0;
+ if (lastline)
+ sp-len = 0;
for (;;) {
if (f != NULL (c = getc(f)) != EOF) {
(void)ungetc(c, f);
signature.asc
Description: This is a digitally signed message part
Re: duplicate -ffreestanding in kernel build
Bruce Evans wrote: printf( const string); - pusts( const string); That is an incredibly *fugly* optimization. It assumes that I use libc, unless I have -ffreestanding, and it assumes my implementation of printf vs. puts. This is a routine optimization. It assumes that you use a C compiler (printf and even libc might not exist, since they might be builtins). A non-routine optimization might involve building hardware to run the application and emitting the 1 bit instruction to turn the hardware on. It's routine to assume that I'm going to use libc?!? I understand the -fnobuiltins thing... particularly if the compiler generates code that makes a function call, instead of generating the code inline, and saving the call/return (kind of makes you want -fnobuiltins by default, though, since I'm smarter than the compiler writers is a common base assumption). I *really* don't understand them making assumptions about the instrumentation that I may or may not have put between myself and the libc implementations of functions, though. Historically, for code portability, I used to carry around my own printf(), and I didn't even have a puts(); this optimization would *really* break things. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ problems
Wesley Morgan wrote: I cleaned up my /usr/lib and /usr/include file of stale headers/libs left after the libstdc++ upgrade (maybe this should be in src/UPDATING??), and now any port that uses C++ autoconf fails to configure... checking if STL implementation is SGI like... no checking if STL implementation is HP like... no configure: error: no known STL type found - did you forget to install libstdc++-devel ? However, the configure script WILL succeed if I manually run configure with the same options (grabbed from ps). Weird... Anyone have some thoughts on this? It's a little annoying :) I just hit the same problem while trying to compile KDE stuff. In my case it stems from bsd.kde.mk adding -I/usr/include to CPPFLAGS, causing gcc to change its include search order. Lacking further insight, I don't know the proper fix there, but I got around it by simply removing -I/usr/include from bsd.kde.mk. Regards, -- Michael Nottebrock The circumstance ends uglily in the cruel result. - Babelfish msg39676/pgp0.pgp Description: PGP signature
i386 tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/i386/obj/local0/scratch/tinderbox/src/i386/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Sat Jun 15 22:24:23 PDT 2002 -- === cm === coff === drm === drm/gamma In file included from @/dev/drm/drm_fops.h:43, from /local0/scratch/tinderbox/src/sys/dev/drm/gamma_drv.c:107: @/sys/signalvar.h:245: conflicting types for `psignal' @/../include/signal.h:88: previous declaration of `psignal' @/sys/signalvar.h:245: warning: redundant redeclaration of `psignal' in same scope @/../include/signal.h:88: warning: previous declaration of `psignal' *** Error code 1 Stop in /local0/scratch/tinderbox/src/sys/modules/drm/gamma. *** Error code 1 Stop in /local0/scratch/tinderbox/src/sys/modules/drm. *** Error code 1 Stop in /local0/scratch/tinderbox/src/sys/modules. *** Error code 1 Stop in /local0/scratch/tinderbox/obj/local0/scratch/tinderbox/src/sys/GENERIC. *** Error code 1 Stop in /local0/scratch/tinderbox/src. *** Error code 1 Stop in /local0/scratch/tinderbox/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Fri, 14 Jun 2002 15:30:19 -0700 Terry Lambert [EMAIL PROTECTED] wrote: Ick. What should be used instead of REQUIRE to mean that it will be started? I.e. if REQUIRE describes soft dependency ordering, what describes hard dependency ordering? Correct, the REQUIRE line only describes the dependency ordering. To start it you twiddle the appropriate rc.conf knob. Cheers, Mike Makonnen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 'sh' core dumps with signal 4 and another problems...
On Sat, Jun 15, 2002 at 11:45:42AM +0600, Vladimir G. Drobyshevsky wrote: 2. When I try to build kernel with bktr (or just to build custom kernel) 'sh' is core dumps. This not enough information to track down any problem. Please give an example of how to cause the problem, a backtrace from gdb, or at least the signal number (there are ~9 signals that cause core dumps). Tim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Sat, 15 Jun 2002 10:44:31 +0930 Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 13 June 2002 at 15:37:55 -0700, Gordon Tetlow wrote: I've imported the excellent work by Mike Makonnen into the tree. Can you summarize what the differences are? o Instead of a few monolithic scripts in /etc there are many task oriented scripts in /etc/rc.d o Dynamic ordering of boot scripts performed at boot o Ability to run a daemon in a jailed environment as a non-privileged user o common subroutines to make scripts shorter and easier to maintain o If necessary, service specific knobs in /etc/rc.conf.d/ Basically, the scripts /etc/rc* scripts have been broken down into individual scripts, each one doing one specific task**. In addition the dependency ordering of the scripts is performed at boot time, so if you have local scripts that you want executed at boot time, it's just a matter of writing up the script, defining what services it should follow (i.e- after local disks have been mounted), and then putting it in /etc/rc.d/. There's a file: /etc/rc.subr, which is intended to make your scripts as short as possible. It contains common subroutines that are useful in writing scripts. Here's a quick introduction: #!/bin/sh # . /etc/rc.subr # PROVIDE: fooservice # REQUIRE: barservice mountcritlocal # KEYWORD: FreeBSD name=foo rcvar=`set_rcvar` command=/usr/bin/foo required_files=/etc/foo.conf load_rc_config $name run_rc_command $1 Given this script, the routines in rc.subr will do the following: o check rc.conf and /etc/rc.conf.d/foo to make sure 'foo_enable' is set. o pull in the correct path to the command if 'foo_command' is specified, and make sure it is executable o check that the required file /etc/foo.conf exists o pull in any command line options specified in the 'foo_flags' variable o if the appropriate variables are defined, start foo in a jail as a non-privileged user. o tell you whether foo is already started o tell you what pid foo is using o let you start foo o let you stop all instances of foo o and some more that I can't think of right now IMO the functionality you get for just those 11 lines is well worth the small effort required in readjusting to this new scheme. If what you want to do requires a little more customization, then you can also define custom start/stop/etc... routines that will be executed instead of the default one. Having said that, there is remarkably little to adjust to. Baring any bugs in the scripts, switching on rcng should not break anything. I have tried to include temporary compatibility shims to ensure that. I had intended to remove them before 5.0-RELEASE, but they should probably be marked as deprecated and instead removed in 6.0-RELEASE. Cheers, Mike Makonnen ** Most scripts do one specific task, but there are exceptions. It is acceptable to do more than one task if they are closely related: for example: /etc/rc.d/sendmail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re[2]: 'sh' core dumps with signal 4 and another problems...
Saturday, June 15, 2002, 1:13:34 PM, you wrote: TJR On Sat, Jun 15, 2002 at 11:45:42AM +0600, Vladimir G. Drobyshevsky wrote: 2. When I try to build kernel with bktr (or just to build custom kernel) 'sh' is core dumps. TJR This not enough information to track down any problem. Please give an TJR example of how to cause the problem, a backtrace from gdb, or at least TJR the signal number (there are ~9 signals that cause core dumps). Hmm... The signals is the number 4 (as explaned in the Subject) and sometimes number 11. This problem is showed after I build GENERIC kernel without DEBUG=-g, ddb and another debug stuff. Now I have downloaded 5.0-CURRENT-20020615-JPSNAP and wanna try to install it. I will send information about this problem in that snapshot. But I am disturbed much more with a problem with CVS... Vl. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Saturday, 15 June 2002 at 0:34:36 -0700, Mike Makonnen wrote: On Sat, 15 Jun 2002 10:44:31 +0930 Greg 'groggy' Lehey [EMAIL PROTECTED] wrote: On Thursday, 13 June 2002 at 15:37:55 -0700, Gordon Tetlow wrote: I've imported the excellent work by Mike Makonnen into the tree. Can you summarize what the differences are? o Instead of a few monolithic scripts in /etc there are many task oriented scripts in /etc/rc.d o Dynamic ordering of boot scripts performed at boot o Ability to run a daemon in a jailed environment as a non-privileged user o common subroutines to make scripts shorter and easier to maintain o If necessary, service specific knobs in /etc/rc.conf.d/ Hmm, appears to be Luke Mewburn's NetBSD stuff, which I know. Shouldn't there be an Obtained From: NetBSD in the commit messages? Are you (or is anybody) doing something about keeping as close as possible to being in sync with NetBSD? Basically, the scripts /etc/rc* scripts have been broken down into individual scripts, each one doing one specific task**. In addition the dependency ordering of the scripts is performed at boot time, so if you have local scripts that you want executed at boot time, it's just a matter of writing up the script, defining what services it should follow (i.e- after local disks have been mounted), and then putting it in /etc/rc.d/. There's a file: /etc/rc.subr, which is intended to make your scripts as short as possible. It contains common subroutines that are useful in writing scripts. Here's a quick introduction: #!/bin/sh # . /etc/rc.subr # PROVIDE: fooservice # REQUIRE: barservice mountcritlocal # KEYWORD: FreeBSD name=foo rcvar=`set_rcvar` command=/usr/bin/foo required_files=/etc/foo.conf load_rc_config $name run_rc_command $1 Given this script, the routines in rc.subr will do the following: o check rc.conf and /etc/rc.conf.d/foo to make sure 'foo_enable' is set. o pull in the correct path to the command if 'foo_command' is specified, and make sure it is executable o check that the required file /etc/foo.conf exists o pull in any command line options specified in the 'foo_flags' variable o if the appropriate variables are defined, start foo in a jail as a non-privileged user. o tell you whether foo is already started o tell you what pid foo is using o let you start foo o let you stop all instances of foo o and some more that I can't think of right now IMO the functionality you get for just those 11 lines is well worth the small effort required in readjusting to this new scheme. If what you want to do requires a little more customization, then you can also define custom start/stop/etc... routines that will be executed instead of the default one. Having said that, there is remarkably little to adjust to. Baring any bugs in the scripts, switching on rcng should not break anything. I have tried to include temporary compatibility shims to ensure that. I had intended to remove them before 5.0-RELEASE, but they should probably be marked as deprecated and instead removed in 6.0-RELEASE. Cheers, Mike Makonnen ** Most scripts do one specific task, but there are exceptions. It is acceptable to do more than one task if they are closely related: for example: /etc/rc.d/sendmail -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 'sh' core dumps with signal 4 and another problems...
Hi! Do you enable softupdate? I have had core dump right after booting and about to login: prompt. I disabled all softupdates, and now it works fine so far. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
On Sat, 15 Jun 2002 17:53:03 +0930
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Saturday, 15 June 2002 at 0:34:36 -0700, Mike Makonnen wrote:
On Sat, 15 Jun 2002 10:44:31 +0930
Greg 'groggy' Lehey [EMAIL PROTECTED] wrote:
On Thursday, 13 June 2002 at 15:37:55 -0700, Gordon Tetlow wrote:
I've imported the excellent work by Mike Makonnen into the tree.
Can you summarize what the differences are?
o Instead of a few monolithic scripts in /etc there are many task oriented
scripts in /etc/rc.d
o Dynamic ordering of boot scripts performed at boot
o Ability to run a daemon in a jailed environment as a non-privileged user
o common subroutines to make scripts shorter and easier to maintain
o If necessary, service specific knobs in /etc/rc.conf.d/
Hmm, appears to be Luke Mewburn's NetBSD stuff, which I know.
Shouldn't there be an Obtained From: NetBSD in the commit messages?
Yes, it is a port of NetBSD's rc sytem as mentioned here:
http://home.pacbell.net/makonnen/rcng.html .
Oversight on Gordon's part I'm sure.
Are you (or is anybody) doing something about keeping as close as
possible to being in sync with NetBSD?
Yeah, when I get some time I'm going to try and get rid of those
case `${CMD_OSTYPE}` clauses together with Luke. David O'Brien said
a while back that he and some others were willing to make sure they stayed
in sync. That's the only reason I made the effort to set it up so that it would
be somewhat easy to do.
Cheers,
Mike Makonnen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Have random panic somewhere near console driver on fresh current
On Fri, 14 Jun 2002, Vladimir B.Grebenschikov wrote: System: FreeBSD vbook.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Jun 5 17:36:46 MSD 2002 [EMAIL PROTECTED]:/usr/local/src/sys/i386/compile/VBOOK i386 gdm runned from /etc/ttys by init gnome environment xconsole runned both by gdm on login screen and by gnome-session after login FreeBSD's support for xconsole never worked right, and using it is normally fatal in -current. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: duplicate -ffreestanding in kernel build
On Fri, 14 Jun 2002, Maxime Henrion wrote:
I recently noticed that we are adding the -ffreestanding flag twice for
kernel builds. It's added once if GCC3 is defined in
/usr/share/mk/bsd.kern.mk and another time inconditionally in
/sys/conf/kern.pre.mk. As a result, I have -ffreestanding once on my
x86 box still running with GCC 2.95 and I have it twice on my sparc box
running GCC 3.
This is a bug in bsd.kern.mk. -ffreestanding never belonged there, since
it is also needed for modules and perhaps for boot programs and libstand.
Module makefiles still include bsd.kern.mk, but Makefiles for boot
programs have regressed.
Your x86 box must be out of date. x86 has gcc-3 and adds -ffreestanding
unconditionally, so -ffreestanding is added twice for all arches. I have
been using the following fix since this bug was committed.
%%%
Index: kern.pre.mk
===
RCS file: /home/ncvs/src/sys/conf/kern.pre.mk,v
retrieving revision 1.12
diff -u -2 -r1.12 kern.pre.mk
--- kern.pre.mk 12 May 2002 15:51:38 - 1.12
+++ kern.pre.mk 13 May 2002 06:12:03 -
@@ -39,5 +36,10 @@
.endif
-COPTS= ${INCLUDES} ${IDENT} -D_KERNEL -ffreestanding -include opt_global.h
+# XXX _KERNEL is bogusly placed. It should be in bsd.kern.mk so that it
+# affects both kernels and modules. Perhaps many more things should be
+# there.
+COPTS= ${INCLUDES} ${IDENT} -D_KERNEL -include opt_global.h
+# XXX aargh, no -fno-common is bogusly placed placed too. It is not even
+# in COPTs like all other options.
CFLAGS=${COPTFLAGS} ${CWARNFLAGS} ${DEBUG} ${COPTS} -fno-common
%%%
One of these should be removed, but I'm not sure which
one yet. Keeping it in kern.pre.mk has the advantage that it will work
even if someone is using a staled bsd.kern.mk.
bsd.kern.mk is misplaced. It should be in sys/conf and renamed to not
emphasize kern. It still needs to be separate from kern.pre.mk to keep
general sys things separe from pure kernel things.
Also, I wonder if it
should be conditional on GCC3 being defined since we were adding it
inconditionally there.
We fixed this. -fformat-extension is now broken (turned off)
unconditionally. I have been using the following fix since the need for
this bug went away:
%%%
Index: bsd.kern.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.kern.mk,v
retrieving revision 1.26
diff -u -2 -r1.26 bsd.kern.mk
--- bsd.kern.mk 24 May 2002 01:02:45 - 1.26
+++ bsd.kern.mk 24 May 2002 15:01:28 -
@@ -7,9 +7,7 @@
# most of the remaining warnings. Warnings introduced with -Wall will
# also pop up, but are easier to fix.
-#
-# XXX FIXME - revert to -fformat-extensions when we've re-added it
CWARNFLAGS?= -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes \
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \
- -Wno-format -ansi
+ -fformat-extensions -ansi
#
# The following flags are next up for working on:
%%%
Anyway, it was a mistake to use -ffreestanding for gcc-3. It was
equally applicable to all versions of gcc that support it. gcc-2 just
happened not to need it.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: HEADS UP: rc.d is in the tree
Greg 'groggy' Lehey wrote: Hmm, appears to be Luke Mewburn's NetBSD stuff, which I know. Shouldn't there be an Obtained From: NetBSD in the commit messages? Are you (or is anybody) doing something about keeping as close as possible to being in sync with NetBSD? This project has been discussed numerous times on -arch. All of your questions should be answered there. -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Entschuldigen Sie bitte die Störung!
Entschuldigen Sie bitte die Störung! Mir ist etwas zu Ohren gekommen. Eine relativ aussergewöhnliche Gerüchteküche, aus der man mir ein schwerverdauliches Süppchen vorgesetzt hat, ist der Grund meiner Mail. Unappetitlich ist gar kein Ausdruck! Ist es möglich auf funktechnischem Wege(in welchen Frequenzbereichen?) jemanden zu beeinflussen oder zu manipulieren? Oder sogar zu schikanieren und terrorisieren? Unter dem Motto:Einen am Sender?Nich ganz alleine? Kleine Mannim Ohr?Falsche Wellenlänge?Bohnen in den Ohren? Auf den Zahn gefühlt(Amalgam)?Mal unverbindlich reinhören? Der Pullacher Wanzentanz? Ist das Spinnerei?Das geht doch gar nicht,oder? Und wenn wie sieht das ethisch moralisch aus? Zur technischen Seite der Sache gibt es zwar Berichte und Webseiten: Totalitaer,de - Die Waffe gegen die Kritik http://www.fosar-bludorf.com/Tempelhof/ http://jya.com/haarp.htm http://www.zeitenschrift.at/magazin/zs_24_15/1_mikrowaffen.htm http://www.bse-plus.de/d/doc/lbrief/lbmincontr.htm http://home.nexgo.de/kraven/bigb/big3.html http://w3.nrl.navy.mil/projects/haarp/index.html http://cryptome.org/ http://www.parascope.com/ds/mkultra0.htm http://www.trufax.org/menu/mind.html http://www.trufax.org/menu/elect.html http://mindcontrolforum.com/ http://www.trufax.org/menu/elect.html usw. usw. usw. ,aber,das kann doch nicht sein,das soetwas gemacht wird,oder? Eine Menschenrechtsverletzung sonder gleichen!?! Ist es möglich,durch Präparation,der Ohren und im Zusammenspiel mit eventuell vorhandenem Zahnersatz? Mit relativ einfacher Funktechnik?? In diesem Land?Hier und heute??? Unter welchen Motiven? Wo ist eigentlich die Abteilung 5 des BND und des Verfassungsschutzes? Kann es sein,daß es Leute gibt,die dem BND/Verfassungsschutz,auf funktechnischem Wege permanent einen Situationsbericht abliefern,ohne es selbst zu merken,im Kindesalter machbar gemacht?? Werden durch solche inoffiziellen Mitarbeiter,beim BND und Verfassungsschutz,nach Stasimanier, Informationen von und über,rein theoretisch, jeden Bundesbürger,gesammelt? Gibt es dann noch ein Recht auf Privatsphere? Wer kontrolliert eigentlich den BND,MAD und Verfassungsschutz auf Unterwanderung??? In der Mail geht es mir eigentlich um die Frage,ob es kriminellen Elementen, aus dem Motiv der Bereicherung,oder Gruppierungen aus ideologischen Motiven, möglich ist ,sich Wissen und Technik anzueignen,die zu anderen Zeiten, aus anderen Motiven(Westfernsehen?),entwickelt wurde. Und stellt der technische Wissensstand, der der Allgemeinheit bekannt ist wirklich das Ende der Fahnenstange dar? Ist es denn nicht kriminellen Elementen genauso möglich, ich sage das jetzt mal verharmlost und verniedlichend, einzelne Personen oder Gruppen mit relativ einfachen Mitteln, aus welchen Motiven auch immer, auszuspionieren? Und stellt diese Ausspioniererei nicht einen erheblichen Eingriff in die Privatsphäre dar? Ist es möglich einzelne Personen oder Gruppen, eine Akzeptans einer gewissen Öffentlichkeit(suggeriert?), die z.B. mit Hilfe von Internetseiten,wie zum Beispiel dem Prangergeschaffen werden könnte, mal vorausgestzt,zu terroriesieren und oder zu schikanieren, und das in aller (suggerierten)Öffentlichkeit?Haben die Leute die da am Pranger, oder auf irgendeiner anderen Seite verunglimpft,oder gar Verleumdet werden, eigentlich eine Chance zur Gegenöffentlichkeit?Ist das nicht Rufmord? Vor einigen Jahren bin ich per Zufall auf die Seite Der Pranger gestoßen, damals lief das noch nicht unter dem Deckmantel der Partnervermittlung. Können sich einzelne Personen,oder Interessengemeinschaften, aus reinem Selbstzweck,solcher Seiten bedienen, um unter dem Deckmantel einer fragwürdigen Zivilkourage, durch anzetteln irgendwelcher Hetzkampagnen,eigene, ganz persöhnliche Interessen durchsetzen? Können solche Seiten zur Koordination von kriminellen machenschaften dienen? Die Frage,ist es Möglichkeit oder Unmöglichkeit,technisch und gesellschaftlich, einzelne Personen,oder auch Gruppierungen,aus einer kriminellen/ideologischen Energei heraus,zu manipulieren oder zu beeinflussen,terrorisieren oder zu schickanieren,und zwar gezielt. Zielgruppenmanipulation durch Massenmedien sind alltägliche Manipulation, der mansich,mehr oder weniger,entziehen kann. Wird das Recht auf Privatsphäre,schleichend,tiefenpsychologisch, durch Sendungen,wie,zum Beispiel Big brother,untergraben? Sollte bei einem der Angemailten ein gewisser Wissensstand zum Thema vorhanden sein, wäre ich über Hinweise zum Thema froh. Auf der Suche nach Antworten auf meine Fragen maile ich verschiedene Adressen aus dem Internet an, und hoffe aufkonstruktive Antworten und Kritiken. Über einen Besuch auf der Seite http://hometown.aol.de/reinerhohn38259/homepage/index.html würde ich mich freuen. Sollten Sie von mir mehrfach angeschrieben worden sein,so bitte ich Sie,mir dies zu entschuldigen, das war nicht beabsichtigt. Der Grund für meine Anonymität ist die Tatsache, daß bei derlei Fragenstellerei, verständlicherweise,schnell der Ruf nach der
