Re: ACPI and SC_PIXEL_MODE problems in 6-stable
Hi, On 12/24/05, iwant4x4jeep <[EMAIL PROTECTED]> wrote: > I'm upgrade my FreeBSD5.4 system to 6.0-STABLE. Now ACPI suspend-to-ram > (sleepstate #3) don't work ( before upgrade all works fine) > > Processor - Pentium 4 2.4Ghz > Mother Board - ASUS P4PE > > # dmesg | grep -i acpi > ACPI APIC Table: > > Features=0xbfebfbff MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22 > acpi0: Power Button (fixed) > pci_link0: irq 5 on acpi0 > pci_link1: irq 9 on acpi0 > pci_link2: irq 9 on acpi0 > pci_link3: irq 9 on acpi0 > pci_link4: irq 10 on acpi0 > pci_link5: on acpi0 > pci_link6: on acpi0 > pci_link7: irq 11 on acpi0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 > cpu0: on acpi0 > acpi_throttle0: on cpu0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pcib2: at device 30.0 on pci0 > pci2: on pcib2 > fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on > ac > pi0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > > When I (as usually before) enter in console 'acpiconf -s 3' (Really I use > sudo, so type 'sudo acpiconf -s 3', computer suspends, but don't resume after > power on. > > I have problem with hi-ressolution modes in console ( Using pathes from > DragonFlyBSD project, which is allready included with freebsd since 6.0). > I'm enabled VESA and SC_PIXEL_MODE options in kernel, when I enter > 'vidcontrol -i mode' - all modes(what i need) displays, but if I use > vidcontrol MODE_279 (for example), monitor enter 1024x768 mode, but I can't > see anything. > First time I think that I do something wrong (Don't load needed fonts for > example), but when I try it on another computer- I can't believe my eyes.. > It was real 1024x768 in FreeBSD Console !!! Are you sure that your configuration cacn support MODE_279? Will other modes work? Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI and SC_PIXEL_MODE problems in 6-stable
I'm upgrade my FreeBSD5.4 system to 6.0-STABLE. Now ACPI suspend-to-ram (sleepstate #3) don't work ( before upgrade all works fine) Processor - Pentium 4 2.4Ghz Mother Board - ASUS P4PE # dmesg | grep -i acpi ACPI APIC Table: Features=0xbfebfbff acpi0: on motherboard acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22 acpi0: Power Button (fixed) pci_link0: irq 5 on acpi0 pci_link1: irq 9 on acpi0 pci_link2: irq 9 on acpi0 pci_link3: irq 9 on acpi0 pci_link4: irq 10 on acpi0 pci_link5: on acpi0 pci_link6: on acpi0 pci_link7: irq 11 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on pci0 pci2: on pcib2 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on ac pi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 When I (as usually before) enter in console 'acpiconf -s 3' (Really I use sudo, so type 'sudo acpiconf -s 3', computer suspends, but don't resume after power on. I have problem with hi-ressolution modes in console ( Using pathes from DragonFlyBSD project, which is allready included with freebsd since 6.0). I'm enabled VESA and SC_PIXEL_MODE options in kernel, when I enter 'vidcontrol -i mode' - all modes(what i need) displays, but if I use vidcontrol MODE_279 (for example), monitor enter 1024x768 mode, but I can't see anything. First time I think that I do something wrong (Don't load needed fonts for example), but when I try it on another computer- I can't believe my eyes.. It was real 1024x768 in FreeBSD Console !!! P.S. I am not think that you'll help me, but I tried... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sys/compat/linux/linux_socket.c - log() message without trailing \n
hello, I got such entry mailed to me in last periodic run: obsolete pre-RFC2553 sockaddr_in6 rejectedarplookup 62.21.28.103 failed: host is not on local network I've grepped through sys/compat/linux/linux_socket.c and looks like there should be an \n on line 157. regards, -- Stanisław Halik, http://tehran.lain.pl pgppQmNyeD6n6.pgp Description: PGP signature
Re: StorageWorks
Wilko Bulte wrote: On Sat, Dec 24, 2005 at 02:13:38AM +0300, Anton Nikiforov wrote.. Dear ALL! I have a Intel XEON based server and Compaq StorageWorks FC adapter with FC disk subsystem. I did not found any info about drivers available in FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?). Could you please help? is there any solution to make this three parts (server, FC adapter and disk subsystem) to work under FreeBSD? *What* Compaq StorageWorks adapter? There are lots of different adapters, both from own Compaq production as well as QLogic and Emulex OEM origin. Only the Qlogics have a driver in FreeBSD, isp(4). It is now working under windows and Device manager saying only the following: Compaq Storage Works 64/66 Fibre host Bus adapter Tomorrow i'll try to open my HP box and see what is on the board. Best regards, Anton smime.p7s Description: S/MIME Cryptographic Signature
Re: StorageWorks
On Sat, Dec 24, 2005 at 02:13:38AM +0300, Anton Nikiforov wrote.. > Dear ALL! > I have a Intel XEON based server and Compaq StorageWorks FC adapter with > FC disk subsystem. > I did not found any info about drivers available in > FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?). > > Could you please help? is there any solution to make this three parts > (server, FC adapter and disk subsystem) to work under FreeBSD? *What* Compaq StorageWorks adapter? There are lots of different adapters, both from own Compaq production as well as QLogic and Emulex OEM origin. Only the Qlogics have a driver in FreeBSD, isp(4). -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OpenSSH does not honour WITHOUT_KERBEROS
Building OpenSSH (as part of buildworld) from a RELENG_6 tree (RELENG_5 works fine from memory) results in binaries linked against the Kerberos libraries, even when NO_KERBEROS is set in make.conf. Although these libraries exist in the host environment, they do not in the target environment (because it is being built with NO_KERBEROS set). -- Alastair D'Silvamob: 0423 762 819 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
On Friday 23 December 2005 20:26, James Tanis wrote: > What reason is that? A reverse-lookup is no longer really a valid way > of filtering out the undesireable unless your lucky enough to be > dealing only with those who have the knowledge and ability to control > those entries. Most residential ips either have no reverse-lookup or I guess you are wrong you can fake your IP and you can fake your hostname, but exactly for security reasons, since we believe that beeing a a network admin is not because of luck but knowledge, and we also believe that this person has a certain responsibility and so he will probably not set up false dns reverse data. so when I check your IP and hostname you send me and when this do not match the reverse info I get I can suppose you do not have good intentions or you do not have the knowledge to set your network up. Both cases may not be welcome on my network and you get kicked out. Like you see here the decision is the owner's one who can or not enter his home. so reverse dns is a absolute valid check - what never was so important as today since each newborn already knows how to fake IP's and when your residential Ip provider do not has a correct reverse DNS get yourself a more serious one anyway, you are mixing things up since you do not need a valid reverse dns to configure your sshd, the server admin can disable this lookup or use the local host file - or you may like the "clever way" and forget to set or delete your resolv.conf João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
StorageWorks
Dear ALL! I have a Intel XEON based server and Compaq StorageWorks FC adapter with FC disk subsystem. I did not found any info about drivers available in FreeBSD-5.4-RELEASE-p8 (maybe vendor developed drivers/utilities?). Could you please help? is there any solution to make this three parts (server, FC adapter and disk subsystem) to work under FreeBSD? Best regards, Anton smime.p7s Description: S/MIME Cryptographic Signature
Making a data DVD with 4.10 and dvd+rw-format
Did you try with growisofs -dvd-compat -Z /dev/cd0*a* -J -R ? I had the same problem but , i tried with this device (cd0_a)_ and it worked. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdboot troubles; 6.0 kernel hanging
On Thu, Dec 22, 2005 at 10:55:58PM +0100, Juergen Lock wrote: > On Wed, Dec 21, 2005 at 11:15:30PM +0100, Juergen Lock wrote: > > I have this box that apparently no longer likes FreeBSD's cdboot, > > it prints something about BOOT/LOADER and then just reboots. > > Any ideas how to debug something like that? The box already has > > FreeBSD installed (5.3 with some patches), and i tried copying the > > 6.0 kernel from disc1 and loading it manually at the loader prompt. > > It hangs after printing (boot -v): > > GEOM: new disk ad0 > > GEOM: new disk ad4 > > > > ad0 is on oboard pata (the board is a via kt400), ad4 is a single disk > > on a Promise Fasttrack tx2200 sata controller. I guess i could try > > to build a 6.0 kernel with ddb, but what would i be looking for then > > to find out why its hanging? [...] Nevermind, 6.0 boots now... (pilot error :) Leaving only the problem of the rebooting cdboot... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
What reason is that? A reverse-lookup is no longer really a valid way of filtering out the undesireable unless your lucky enough to be dealing only with those who have the knowledge and ability to control those entries. Most residential ips either have no reverse-lookup or it's set to some long painful textual conglomeration devised by the isp (although at the isp I work at we will set it per some users requests..). Anyway, to make a long story short, you end up locking out or at the very least delaying (for up to several minutes) the very people who use it. I can definately see the sysadmin side of it though were its used perhaps to remotely access a data center from a satellite location -- you don't much want or care that a residential ip has problems connecting to the server. It just definately doesn't seem to me a "last resort" option, at the drop of a hat someone can change their hostname to match their reverse dns and back again -- setting up a good packet filter to filter out all but the desired ip ranges seems a much more reliable method. On 23 Dec 2005 09:30:56 -0500, Lowell Gilbert <[EMAIL PROTECTED]> wrote: > Marian Hettwer <[EMAIL PROTECTED]> writes: > > > Hej there, > > > > Kobi Shmueli wrote: > > > Try checking /etc/resolv.conf on oboe first, adding a static entry to > > > /etc/hosts of the remote ip/host should speed dns checks as well. > > > You can also run ssh in verbose mode (ssh -v oboe) or/and run sshd in > > > debug > > > mode (sshd -d). > > > > > alternativly to check out wether it's dns related, you use set the > > Option "UseDNS no" in your sshd_config, so sshd won't try a reverse > > dns lookup. > > Give it a shoot. Usually ssh timeouts are related to DNS... > > That should be a last resort; the hostname checks are there for a > reason... > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- James Tanis [EMAIL PROTECTED] http://pycoder.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: problems with groff in FreeBSD 6.0 buildworld
On Friday 23 December 2005 20:54, Telegin Gennady wrote: > /usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/ >src/preproc/grn/main.cpp:692: error: expected primary-expression before > '<'token > /usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/ >src/preproc/grn/main.cpp:694: error: expected primary-expression before '>' > token > Can you paste line 690-700. This looks like a cvs merge conflict to me. -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
problems with groff in FreeBSD 6.0 buildworld
I have heads up my source tree to RELENG_6, and for the `make
buildworld` I have got a compile error, last message of which is that:
c++ -O2 -fno-strict-aliasing -pipe -O -pipe -DHAVE_CONFIG_H
-I/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/include
-I/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../src/include
-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-rtti -fno-exceptions
-c
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp:
In function `void savebounds(double,double)':
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp:692:
error: expected primary-expression before '<'token
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp:693:
error: expected primary-expression before ';' token
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp:694:
error: expected primary-expression before '>' token
/usr/src/gnu/usr.bin/groff/src/preproc/grn/../../../../../../contrib/groff/src/preproc/grn/main.cpp:695:
error: expected primary-expression before ';' token
*** Error code 1
Stop in /usr/src/gnu/usr.bin/groff/src/preproc/grn.
I was trying change CFLAGS, COPTFLAGS in /etc/make.conf to `+= -0
-pipe`, or comment it, but the result were not changed. Here
the /etc/make.conf, which I use now:
CFLAGS += -O -pipe
COPTFLAGS += -O -pipe
NO_PROFILE=
COMPAT3x=YES
COMPAT4x=YES
BSDPORTMK?= ${PORTSDIR}/devel/portmk/Mk/bsd.port.mk
BSDPORTSUBDIRMK?= ${PORTSDIR}/devel/portmk/Mk/bsd.port.subdir.mk
PERL_VER=5.8.7
PERL_VERSION=5.8.7
My current system is FreeBSD 5.4.
In what a problem?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
James Tanis wrote: For whatever reason, I have had a similar problem which was solved by entering the machines that you are logging in from into the hosts file. I'm guessing it attempts a reverse lookup and your (as well as my) dns/hostname does not match its reverse lookup entry. On 12/23/05, Michael A. Koerber <[EMAIL PROTECTED]> wrote: All, I have three machines that have had 5.4 and 6.0 installed. Two of the three machines have very well behaved "ssh". However, the machine (laptop) named OBOE does not. Specifically "ssh oboe" will (most of the time) hang for around one minute before asking for a prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other machines) a password is requested within a couple seconds. (I said most of the time, since on occasion I can reboot OBOE and ssh will work just fine...hmmm.) I have looked through the /var/log files for clues and skimmed "man ssh" for time out related stuff, but no luck. Where should I start looking for clues? All machines have had clean installs from "newfs'd" drive under both 5.4 and 6.0 so I'm sure no left over configs are getting propagated. -- - Dr Michael A. Koerber x3250 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- James Tanis [EMAIL PROTECTED] http://pycoder.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" Try disabling sendmail. I don't remember exactly how I came up with this solution but I remember sendmail was the problem. This might work for you as well. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Fri, 23 Dec 2005 19:28:19 +0100
Florent Thoumie <[EMAIL PROTECTED]> wrote:
> On Friday 23 December 2005 18:52, Ion-Mihai Tetcu wrote:
> > On Fri, 23 Dec 2005 15:38:15 +0100
> >
> > Florent Thoumie <[EMAIL PROTECTED]> wrote:
> > > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote:
> > > > I'm not sure this is the way to go, but ...
> > > >
> > > > Can someone put a document on what is the desired model? I
> > > > think we have too much little pieces of disperse notes about
> > > > this.
> > > >
> > > > Also, some working notes about ports and RELENG_4/RELENG_5 src
> > > > issues will be of interest.
> > > >
> > > > Hope this can be tweak in time for 6.1 (Jan).
> > >
> > > Convert your old script to rcNG scripts and use
> > > USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains
> > > meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all
> > > your rcNG scripts. bsd.port.mk should do the rest.
> >
> > You should actually convert your old script to a ``rc.d'' script,
> > that's how they are called now.
>
> rcNG was the word for "using rc.subr". From the beginning
> these rc.subr-powered scripts have been using the rcorder preamble
> and have always been rc.d script actually. Since we're talking about
> the same thing, I'm not sure words are really important.
Well, I was corrected by dougb@
For me a rc.d script is one that on:
1. has the right keywords, ... (ie. is rcNG)
2. has the right extension depending if it must be sourced or not
(on a a system which has local_startup scripts in the base rcorder -
HEAD and 6-STABLE for now).
> > Also, if your script is rc.d compatible you should use:
> > USE_RC_SUBR=script (without .sh)
> > For now it doesn't matter because bsd.port.mk install all
> > USE_RC_SUBR scripts with .sh extension, but see below
>
> Using the .sh extension prevents from conflicts in ${WRKDIR}
This is indeed a problem; perhaps we should hack bsd.port.mk to avoid
this.
> and you know what kind of file it is in ${FILESDIR}. Anyway, what is
This is easy to fix, no ?
> the difference between adding .sh suffix in some cases and removing
> it in some cases ?
If you are asking what is the difference between how it is/will be treated by
rc.subr the answer is in the quote from Brooks which you removed.
An interesting discussion is in
http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/90070 and a solution is
tested (http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/90150).
I think naming a script without .sh make it easy to see it's rc.d ready.
--
IOnut - Unregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
BOFH excuse #386:
The Internet is being scanned for viruses
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Release schedule for 2006
On Thu, Dec 22, 2005 at 01:10:19PM -0800, Jo Rhett wrote: > I and many others have offered to work on this. The core team has > repeatedly stated that they won't integrate the efforts Please provide hard evidence for this assertion. Merely repeating it will not be sufficiently convincing. I would like to see _specific_ references (email or other documentation) that that is _exactly_ what core, or anyone else, has said. I cannot recall any such thing on any of the mailing lists that I have monitored for the past several years. Without that, my high degree of skepticism about this claim will remain. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 18:52, Ion-Mihai Tetcu wrote:
> On Fri, 23 Dec 2005 15:38:15 +0100
>
> Florent Thoumie <[EMAIL PROTECTED]> wrote:
> > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote:
> > > I'm not sure this is the way to go, but ...
> > >
> > > Can someone put a document on what is the desired model? I think we
> > > have too much little pieces of disperse notes about this.
> > >
> > > Also, some working notes about ports and RELENG_4/RELENG_5 src
> > > issues will be of interest.
> > >
> > > Hope this can be tweak in time for 6.1 (Jan).
> >
> > Convert your old script to rcNG scripts and use USE_RC_SUBR=
> > script.sh. Ensure that the rcorder preamble contains meaningful
> > keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts.
> > bsd.port.mk should do the rest.
>
> You should actually convert your old script to a ``rc.d'' script,
> that's how they are called now.
rcNG was the word for "using rc.subr". From the beginning these
rc.subr-powered scripts have been using the rcorder preamble and have
always been rc.d script actually. Since we're talking about the same
thing,
I'm not sure words are really important.
> Also, if your script is rc.d compatible you should use:
> USE_RC_SUBR=script (without .sh)
> For now it doesn't matter because bsd.port.mk install all USE_RC_SUBR
> scripts with .sh extension, but see below
Using the .sh extension prevents from conflicts in ${WRKDIR} and you
know
what kind of file it is in ${FILESDIR}. Anyway, what is the difference
between adding .sh suffix in some cases and removing it in some cases ?
--
Florent Thoumie
[EMAIL PROTECTED]
FreeBSD Committer
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Fri, 23 Dec 2005 15:38:15 +0100 Florent Thoumie <[EMAIL PROTECTED]> wrote: > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: > > > I'm not sure this is the way to go, but ... > > > > Can someone put a document on what is the desired model? I think we > > have too much little pieces of disperse notes about this. > > > > Also, some working notes about ports and RELENG_4/RELENG_5 src > > issues will be of interest. > > > > Hope this can be tweak in time for 6.1 (Jan). > > Convert your old script to rcNG scripts and use USE_RC_SUBR= > script.sh. Ensure that the rcorder preamble contains meaningful > keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. > bsd.port.mk should do the rest. You should actually convert your old script to a ``rc.d'' script, that's how they are called now. Also, if your script is rc.d compatible you should use: USE_RC_SUBR=script (without .sh) For now it doesn't matter because bsd.port.mk install all USE_RC_SUBR scripts with .sh extension, but see below On Thu, 22 Dec 2005 10:52:27 -0800 Brooks Davis <[EMAIL PROTECTED]> wrote: [ ... ] > > Does this mean that we will remove the .sh extension on port rc.d > > startup scripts? Because a) it's been only running .sh scripts for > > quite a while, and b) it's really nice and easy to disable scripts > > by moving them to .old or another extension.. > > Yes. You should be able to disable any correctly written rc.d script > by setting the variable listed by running "
Re: SSH login takes very long time...sometimes
For whatever reason, I have had a similar problem which was solved by entering the machines that you are logging in from into the hosts file. I'm guessing it attempts a reverse lookup and your (as well as my) dns/hostname does not match its reverse lookup entry. On 12/23/05, Michael A. Koerber <[EMAIL PROTECTED]> wrote: > All, > > I have three machines that have had 5.4 and 6.0 installed. Two of the > three machines have very > well behaved "ssh". However, the machine (laptop) named OBOE does not. > > Specifically "ssh oboe" will (most of the time) hang for around one minute > before asking for a > prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other > machines) a password is > requested within a couple seconds. (I said most of the time, since on > occasion I can reboot OBOE > and ssh will work just fine...hmmm.) > > I have looked through the /var/log files for clues and skimmed "man ssh" > for time out related > stuff, but no luck. > > Where should I start looking for clues? > > All machines have had clean installs from "newfs'd" drive under both 5.4 > and 6.0 so I'm sure no > left over configs are getting propagated. > -- > - > Dr Michael A. Koerber > x3250 > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- James Tanis [EMAIL PROTECTED] http://pycoder.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: troubles compiling latest RELENG_6
Tofik Suleymanov wrote: After cvsuping latest RELENG_6: make buildworld ( executes fine) make buildkernel (gives an error - look below) cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/net80211/ieee80211_ioctl.c /usr/src/sys/net80211/ieee80211_ioctl.c: In function `ieee80211_ioctl_get80211': /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: `IEEE80211_IOC_MCAST_RATE' undeclared (first use in this function) /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: (Each undeclared identifier is reported only once /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: for each function it appears in.) /usr/src/sys/net80211/ieee80211_ioctl.c:1484: error: structure has no member named `ic_mcast_rate' /usr/src/sys/net80211/ieee80211_ioctl.c: In function `ieee80211_ioctl_set80211': /usr/src/sys/net80211/ieee80211_ioctl.c:2375: error: `IEEE80211_IOC_MCAST_RATE' undeclared (first use in this function) /usr/src/sys/net80211/ieee80211_ioctl.c:2376: error: structure has no member named `ic_mcast_rate' *** Error code 1 Your tree/build area must be out of sync; rev 1.10.2.3 to ieee80211_ioctl.h defines IEEE80211_IOC_MCAST_RATE. Sam ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates..
Essentially, you want a CVS (or equivalent tool) for the system administrator. This could be a project management tool for OS binary or source releases and updates. The CVS concept would be able to manage the synchronization with current source as it does now, and could include binary. Then you need: 1a. A place to store specifications for each system configuration 1b. A place to specify each port, options and flags required, per system 1c. Delivery/timing/synchronization parameters for each system or group of systems. 2. A flag in each independent component to indicate binary replacement or source recompile. 3. A flag for each component indicating backward compatibility or not. 4. A way to synchronize non-backward compatible upgrades 5. Port like compile code to bin upgrade and/or build new binaries 6. A way to indicate component upgrades that cause cascade(s) of upgrades/recompiles, and which those are. It appears that many of the components to build such a system exist in partial or full form. The problem I have in going deeper is that my understanding of many parts of FreeBSD is not very deep, so I can't tell if my proposal is a valid starting point. Comments? BillN Poul-Henning wrote: It's what people are used to, but it is not what they want. It would be much better to invest time in developing a configuration management system that allows the system administrators of FreeBSD installations to do their job more effectively than to spend time giving them the tool they know inwards and outwards is not an effective way to do their job. The assignment is simple, and with creative thinking maybe the solution is also: Bring to system administration what source code version control brought to programming. Merry Xmas, Poul-Henning ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
On Fri, 23 Dec 2005 21:10:19 +0530 Joseph Koshy <[EMAIL PROTECTED]> wrote: > www.infrastructures.org > www.isconf.org and perhaps also http://www.cfengine.org/ and probably others. IMHO, FreeBSD is a good os, with good options on configuration and management. It is not a systems management tool / system, and (IMHO) it shoildn't try to be that either. Let those who need it build the necessary tools to do large scale FreeBSD administration and maintenance. If the tool is good, it will be used. So far, I have read only a lot of bikeshedding. -- Regards, Torfinn Ingolfsen, Norway ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Booting from ZIP 750 ...
IIRC ATAPI Zip drives appear as "ATAPI Floppy Device" to the kernel, you should be able to boot off of them but it might be a bit weird. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Viernes, 23 de Diciembre de 2005 16:17, Florent Thoumie escribió: > On Friday 23 December 2005 16:12, Jose M Rodriguez wrote: > > El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: > > > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: > > > > I'm not sure this is the way to go, but ... > > > > > > > > - some kinda of style for ports/system rc scripts > > ? In the way of style(9). > > > - some docs about keywords and stage support > > It's quite simple enough but yar wrote an article about it : > > http://people.freebsd.org/~yar/rcng/article.html > > I thought it already made it to the doc tree. > I think this is about the rc framework. But not about the hard details: Also, if we now support rcorder for localpkg, we're implemening, at last, a two stage boot process ( we can't read the local rc scripts at the very beginning of the boot process). > > - some kinda of timeline model > > There's one. > Commit, MFC, fix broken ports. Sorry, it's boot process timeline, not working timeline. We need a good reference for good tagging of rc scripts. -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: indefinite wait buffer: Does this indicate hardware issue?
Xin> Hi Hi. On 19 Dec 2005 14:32:31 -0600, Douglas K. Rand <[EMAIL PROTECTED]> wrote: Doug> Tracing command swapper pid 0 tid 0 td 0xc0698e20 Doug> sched_switch(c0698e20,0,1) at sched_switch+0x14b Doug> mi_switch(1,0) at mi_switch+0x1ba Doug> scheduler(0,81ec00,81e000,0,c042f5d5) at scheduler+0x262 Doug> mi_startup() at mi_startup+0x96 Doug> begin() at begin+0x2c Xin> Which scheduler are you using? SCHED_4BSD. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
phk> Bring to system administration what source code phk> version control brought to programming. www.infrastructures.org www.isconf.org -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 16:12, Jose M Rodriguez wrote: > El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: > > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: > > > I'm not sure this is the way to go, but ... > > > > > > Can someone put a document on what is the desired model? I think > > > we have too much little pieces of disperse notes about this. > > > > > > Also, some working notes about ports and RELENG_4/RELENG_5 src > > > issues will be of interest. > > > > > > Hope this can be tweak in time for 6.1 (Jan). > > > > Convert your old script to rcNG scripts and use USE_RC_SUBR= > > script.sh. Ensure that the rcorder preamble contains meaningful > > keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. > > bsd.port.mk should do the rest. > > Some time working with binary oriented software systems have teach me > that simple changes may become harder when size and numbers grow up. I > think this may be even harder with a non-binary oriented system like > ports. > > But this doesn't solve the real problem. We've lost a reference model > about rc and the interaction with the base system and ports. > > - some kinda of style for ports/system rc scripts ? > - some docs about keywords and stage support It's quite simple enough but yar wrote an article about it : http://people.freebsd.org/~yar/rcng/article.html I thought it already made it to the doc tree. > - some kinda of timeline model There's one. Commit, MFC, fix broken ports. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer pgp1HMFMmWWyU.pgp Description: PGP signature
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Viernes, 23 de Diciembre de 2005 15:38, Florent Thoumie escribió: > On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: > > I'm not sure this is the way to go, but ... > > > > Can someone put a document on what is the desired model? I think > > we have too much little pieces of disperse notes about this. > > > > Also, some working notes about ports and RELENG_4/RELENG_5 src > > issues will be of interest. > > > > Hope this can be tweak in time for 6.1 (Jan). > > Convert your old script to rcNG scripts and use USE_RC_SUBR= > script.sh. Ensure that the rcorder preamble contains meaningful > keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. > bsd.port.mk should do the rest. Some time working with binary oriented software systems have teach me that simple changes may become harder when size and numbers grow up. I think this may be even harder with a non-binary oriented system like ports. But this doesn't solve the real problem. We've lost a reference model about rc and the interaction with the base system and ports. - some kinda of style for ports/system rc scripts - some docs about keywords and stage support - some kinda of timeline model ... I think that this is more or less out there, but not in a strict document that may guide for the change to FreeBSD-6.1 -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
troubles compiling latest RELENG_6
After cvsuping latest RELENG_6: make buildworld ( executes fine) make buildkernel (gives an error - look below) cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/net80211/ieee80211_ioctl.c /usr/src/sys/net80211/ieee80211_ioctl.c: In function `ieee80211_ioctl_get80211': /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: `IEEE80211_IOC_MCAST_RATE' undeclared (first use in this function) /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: (Each undeclared identifier is reported only once /usr/src/sys/net80211/ieee80211_ioctl.c:1483: error: for each function it appears in.) /usr/src/sys/net80211/ieee80211_ioctl.c:1484: error: structure has no member named `ic_mcast_rate' /usr/src/sys/net80211/ieee80211_ioctl.c: In function `ieee80211_ioctl_set80211': /usr/src/sys/net80211/ieee80211_ioctl.c:2375: error: `IEEE80211_IOC_MCAST_RATE' undeclared (first use in this function) /usr/src/sys/net80211/ieee80211_ioctl.c:2376: error: structure has no member named `ic_mcast_rate' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. paranoia# Any suggestions or ideas ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
On Friday 23 December 2005 15:19, Jose M Rodriguez wrote: > I'm not sure this is the way to go, but ... > > Can someone put a document on what is the desired model? I think we > have too much little pieces of disperse notes about this. > > Also, some working notes about ports and RELENG_4/RELENG_5 src issues > will be of interest. > > Hope this can be tweak in time for 6.1 (Jan). Convert your old script to rcNG scripts and use USE_RC_SUBR= script.sh. Ensure that the rcorder preamble contains meaningful keywords (PROVIDES, REQUIRES, BEFORE, ...) for all your rcNG scripts. bsd.port.mk should do the rest. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer pgpiY2qd3eeZG.pgp Description: PGP signature
Re: SSH login takes very long time...sometimes
Marian Hettwer <[EMAIL PROTECTED]> writes: > Hej there, > > Kobi Shmueli wrote: > > Try checking /etc/resolv.conf on oboe first, adding a static entry to > > /etc/hosts of the remote ip/host should speed dns checks as well. > > You can also run ssh in verbose mode (ssh -v oboe) or/and run sshd in debug > > mode (sshd -d). > > > alternativly to check out wether it's dns related, you use set the > Option "UseDNS no" in your sshd_config, so sshd won't try a reverse > dns lookup. > Give it a shoot. Usually ssh timeouts are related to DNS... That should be a last resort; the hostname checks are there for a reason... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: MFC of local_startup changes to rc.d complete
El Miércoles, 21 de Diciembre de 2005 09:23, Doug Barton escribió: > Howdy, > > As has been discussed for a couple weeks now, I have MFC'ed to > RELENG_6 the changes in /etc/rc* that bring new-style boot scripts > from the local_startup directories (by default /usr/local/etc/rc.d > and /usr/X11R6/etc/rc.d) into the base rcorder. For old style scripts > (those that don't use rc.subr) there should be no changes. They will > still run out of /etc/rc.d/localpkg. For those scripts that have been > converted to use rc.subr, they will still be run the same way that > they are now. The difference is that they will be added to the base > rcorder list, and run in that spot instead of in localpkg. To get an > idea of the current list (minus any local scripts) in RELENG_6, see > http://people.freebsd.org/~dougb/rcorder-6.all > > In an ideal world, there should be no problems related to running the > scripts in a different order. However, it is anticipated that there > may be a brief period while scripts for whom the ordering is > significant are adjusted. These are extremely easy changes to make, > and do not otherwise affect the functionality of the packages in any > way. If you run into one of these problems, please report it to the > port's maintainer, and [EMAIL PROTECTED] ASAP. In almost all > cases however the scripts will run close enough to their old position > as not to make any difference, since currently localpkg is fairly > late in the order. > > This change is being made so that port authors and users can take > advantage of the greater control these features will give them. Some > authors have already stepped forward and added new functionality to > their ports that take advantage of these features. If anyone has > questions about the changes, or what they offer you, feel free to ask > on [EMAIL PROTECTED] You can also find more information in > rc(8) on an updated system. > > > Happy Holidays, > > Doug > I'm not sure this is the way to go, but ... Can someone put a document on what is the desired model? I think we have too much little pieces of disperse notes about this. Also, some working notes about ports and RELENG_4/RELENG_5 src issues will be of interest. Hope this can be tweak in time for 6.1 (Jan). -- josemi -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfilter upgrade issue
On Friday 23 December 2005 14:51, Koen Martens wrote: > Melvyn Sopacua wrote: > >On Friday 23 December 2005 11:12, Koen Martens wrote: > >>Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. > >>The ipfilter implementation in the 6-STABLE kernel errs on the commands > >>sent by the 5.4 ipf binary. This can be an issue when you are upgrading > >>remotely without serial console and you have IPFILTER_DEFAULT_BLOCK > >>enabled: after rebooting in the 6-STABLE kernel no firewall rules will > >>be loaded and you cannot access the box anymore to make installworld.. > > > >Just wondering - is COMPAT5X in the kernel? > > Well, COMPAT_FREEBSD5 is.. Sounds like a note for UPDATING then :) -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
Hej there, Kobi Shmueli wrote: Try checking /etc/resolv.conf on oboe first, adding a static entry to /etc/hosts of the remote ip/host should speed dns checks as well. You can also run ssh in verbose mode (ssh -v oboe) or/and run sshd in debug mode (sshd -d). alternativly to check out wether it's dns related, you use set the Option "UseDNS no" in your sshd_config, so sshd won't try a reverse dns lookup. Give it a shoot. Usually ssh timeouts are related to DNS... HTH, Marian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfilter upgrade issue
Melvyn Sopacua wrote: On Friday 23 December 2005 11:12, Koen Martens wrote: Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. The ipfilter implementation in the 6-STABLE kernel errs on the commands sent by the 5.4 ipf binary. This can be an issue when you are upgrading remotely without serial console and you have IPFILTER_DEFAULT_BLOCK enabled: after rebooting in the 6-STABLE kernel no firewall rules will be loaded and you cannot access the box anymore to make installworld.. Just wondering - is COMPAT5X in the kernel? Well, COMPAT_FREEBSD5 is.. Koen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i915drm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dawnshade wrote: > On Friday 23 December 2005 08:11, Gianmarco Giovannelli wrote: > >>At 08.10 22/12/2005, dawnshade wrote: >> >On Thursday 22 December 2005 04:22, Gianmarco Giovannelli wrote: >> >> It seems to me that also Oliver has the same bug (0M) on his 915GM >> >> Any other with with centrino based 915 card can confirm this ? >> > >> >for me works fine: >> > >> >dmesg |grep -E 'drm|agp' >> >agp0: port 0xe000-0xe007 mem >> >0xd000-0xd007,0xa000-0xafff,0xd008-0xd00b irq 5 >> > at device 2.0 on pci0 >> >agp0: detected 7932k stolen memory >> >agp0: aperture size is 256M >> >drmsub0: : (child of agp_i810.c) on agp0 >> >info: [drm] AGP at 0xd000 0MB >> >info: [drm] Initialized i915 1.2.0 20041217 >> >>Uhm... you have the same 0M of me :-) >>Have you tried glxgears ? >>What are your results ? > > > glxinfo: > > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > server glx vendor string: SGI > > >> >try to upgrade port dri to dri-devel >> >I have the same situation - glxinfo shows that dri disabled, after >>portupgrade >> >-f -o graphics/dri-devel dri glxgears shown 1128.200 FPS (was ~300 and ~600 >> >w/o dri) >> >>Oops I don't remember about this. >>Can you please told me which versions (dri-devel, xorg) do you have >>(because I am running dri-devel !!! :-) ? > > > pkg_info |grep dri > dri-6.2.20050719,1 DRI OpenGL drivers snapshot > linux_dri-4.4.0 Binary Linux DRI libraries for 3D hardware acceleration of > > pkg_info |grep xorg > xorg-6.8.2 X.Org distribution metaport > xorg-clients-6.8.2 X client programs and related files from X.Org > xorg-documents-6.8.2 Documentation of X11 protocol and libraries from X.Org > xorg-fonts-100dpi-6.8.2 X.Org 100dpi bitmap fonts > xorg-fonts-75dpi-6.8.2 X.Org 75dpi bitmap fonts > xorg-fonts-cyrillic-6.8.2 X.Org Cyrillic bitmap fonts > xorg-fonts-encodings-6.8.2 X.Org font encoding files > xorg-fonts-miscbitmaps-6.8.2 X.Org miscellaneous bitmap fonts > xorg-fonts-truetype-6.8.2 X.Org TrueType fonts > xorg-fonts-type1-6.8.2 X.Org Type1 fonts > xorg-fontserver-6.8.2 X font server from X.Org > xorg-libraries-6.8.2 X11 libraries and headers from X.Org > xorg-manpages-6.8.2 X.Org library manual pages > xorg-nestserver-6.8.2 Nesting X server from X.Org > xorg-printserver-6.8.2_2 X Print server from X.Org > xorg-server-6.8.99.16_1 X.Org X server development snapshot and related > programs > xorg-vfbserver-6.8.2 X virtual framebuffer server from X.Org > > So the combination of dri-devel and xorg-6.8.99.16_1 works fine. For me the latest xorg-snap (903) does not work. Anyway here is a path for the vanilla xorg 6.8.2, it works: http://apocalyptech.com/linux/nc6120/xorg-6.8.2-i810.patch Best, Laci - -- László Károly <[EMAIL PROTECTED]> Department of Altaic StudiesEgyetem str. 2. University of Szeged H-6722 Szeged, Hungary PGP/GnuPG key: 1024D/869D81C5 Fingerprint: 1E61 3205 8F5A 87E7 1269 3396 1C63 F9FF 869D 81C5 Encrypted e-mail preferred. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDrABuHGP5/4adgcURAkBpAJ9wjYqt9QCnTCAJTssO9H6argIM2ACfSKjd xR1Y/REFY5Be0O7bLE2+EJI= =iRsr -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfilter upgrade issue
On Friday 23 December 2005 11:12, Koen Martens wrote: > Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. > The ipfilter implementation in the 6-STABLE kernel errs on the commands > sent by the 5.4 ipf binary. This can be an issue when you are upgrading > remotely without serial console and you have IPFILTER_DEFAULT_BLOCK > enabled: after rebooting in the 6-STABLE kernel no firewall rules will > be loaded and you cannot access the box anymore to make installworld.. Just wondering - is COMPAT5X in the kernel? -- Melvyn Sopacua [EMAIL PROTECTED] FreeBSD 6.0-STABLE Qt: 3.3.5 KDE: 3.4.3 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
Michael A. Koerber wrote: > I have three machines that have had 5.4 and 6.0 installed. Two of the three machines have very > well behaved "ssh". However, the machine (laptop) named OBOE does not. > > Specifically "ssh oboe" will (most of the time) hang for around one minute before asking for a > prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other machines) a password is > requested within a couple seconds. (I said most of the time, since on occasion I can reboot OBOE > and ssh will work just fine...hmmm.) > > I have looked through the /var/log files for clues and skimmed "man ssh" for time out related > stuff, but no luck. > > Where should I start looking for clues? Try checking /etc/resolv.conf on oboe first, adding a static entry to /etc/hosts of the remote ip/host should speed dns checks as well. You can also run ssh in verbose mode (ssh -v oboe) or/and run sshd in debug mode (sshd -d). -Kobi. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
Michael A. Koerber wrote: All, I have three machines that have had 5.4 and 6.0 installed. Two of the three machines have very well behaved "ssh". However, the machine (laptop) named OBOE does not. Specifically "ssh oboe" will (most of the time) hang for around one minute before asking for a prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other machines) a password is requested within a couple seconds. (I said most of the time, since on occasion I can reboot OBOE and ssh will work just fine...hmmm.) I have looked through the /var/log files for clues and skimmed "man ssh" for time out related stuff, but no luck. Where should I start looking for clues? All machines have had clean installs from "newfs'd" drive under both 5.4 and 6.0 so I'm sure no left over configs are getting propagated. Check your DNS (or reverse DNS really) on the laptop (OBOE). Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology Anything that works is better than anything that doesn't. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SSH login takes very long time...sometimes
On 12/23/05, Michael A. Koerber <[EMAIL PROTECTED]> wrote: > All, > > I have three machines that have had 5.4 and 6.0 installed. Two of the > three machines have very > well behaved "ssh". However, the machine (laptop) named OBOE does not. > > Specifically "ssh oboe" will (most of the time) hang for around one minute > before asking for a > prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other > machines) a password is > requested within a couple seconds. (I said most of the time, since on > occasion I can reboot OBOE > and ssh will work just fine...hmmm.) > > I have looked through the /var/log files for clues and skimmed "man ssh" > for time out related > stuff, but no luck. > > Where should I start looking for clues? > Most probably it's a reverse dns issue. You can either check your dns/hosts setup or tcpdump the traffic when you try to login a machine. -- Joao Barros ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
SSH login takes very long time...sometimes
All, I have three machines that have had 5.4 and 6.0 installed. Two of the three machines have very well behaved "ssh". However, the machine (laptop) named OBOE does not. Specifically "ssh oboe" will (most of the time) hang for around one minute before asking for a prompt. However, if I'm logged into OBOE and "ssh BSD" (one of the other machines) a password is requested within a couple seconds. (I said most of the time, since on occasion I can reboot OBOE and ssh will work just fine...hmmm.) I have looked through the /var/log files for clues and skimmed "man ssh" for time out related stuff, but no luck. Where should I start looking for clues? All machines have had clean installs from "newfs'd" drive under both 5.4 and 6.0 so I'm sure no left over configs are getting propagated. -- - Dr Michael A. Koerber x3250 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Booting from ZIP 750 ...
On Fri, 23 Dec 2005 21:34, Stefan Juhl wrote: > Is anybody able to boot FreeBSD 5.x-STABLE from a ATAPI ZIP 750 .? > > I tried to, but it didn't work. "it didn't work" is a pretty useless error message. What happened? Is your BIOS set to boot off that device? Can it boot from it? Have you tried another OS on it? If it looks like a hard disk I would think it *should* work as long as the partition FreeBSD is installed onto is set to be bootable. How did you partition and label the disk? I've booted FreeBSD from a Jazz drive but it was a long time ago (and on SCSI ISTR) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpUu8Aeoa6EX.pgp Description: PGP signature
Booting from ZIP 750 ...
Hi! Is anybody able to boot FreeBSD 5.x-STABLE from a ATAPI ZIP 750 .? I tried to, but it didn't work. I mounted the ZIP from a running 5.X-STABLE and made the normal release procedure (installworld / installkernel .). I also gave bootcfg a try. But nothing helped. Or is there no way of booting a FreeBSD 5.X-STABLE from ZIP? Yours Stefan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Please clean out your */etc/rc.d directories
On Thu, 22 Dec 2005 10:52:27 -0800
Brooks Davis <[EMAIL PROTECTED]> wrote:
> > Also, how will this effect cups which installs a .sample file? and
> > any other port that does this?
>
> .sample files should go away. If for some reason a script must
> be modified to be useful, the sample version should go under
> ${PREFIX}/share.
I haven open (and badly written) PR for converting cups' rc script to be
rc.d compatible. Today / tomorrow I'll submit a new patch (after
TinderFoxy finishes building my ports so I can test the modifications I
make).
--
IOnut - Unregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
I'm not sure, try calling the Internet's head office -- it's in the book
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
I have consistently ignored all emails in this thread because the use of the word "demand" in the Subject. Whenever people use words like "demand" or "somebody should" in FreeBSD contexts, it indicates cluelessness to me. Cluelessness about how the project works and cluenessness about how things happen in the project and a touch of insensibility to the developers how seldom are paid to listen to such drivel. The precense if "binary updates" in the subject also indicated to me that we had to do with people who didn't really know what they were talking about nor indeed the implications of attempting to do what they demanded. Now that I've read the tread anyway I can to my chagrin see that I was right. In my opinion, and I readily admit that since I only have 20+ years of experience managing UNIX computers I may be totally wrong, binary updates is not what we really want. It's what people are used to, but it is not what they want. It would be much better to invest time in developing a configuration management system that allows the system administrators of FreeBSD installations to do their job more effectively than to spend time giving them the tool they know inwards and outwards is not an effective way to do their job. The assignment is simple, and with creative thinking maybe the solution is also: Bring to system administration what source code version control brought to programming. Merry Xmas, Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006)
Brian Candler wrote: > I think the real concern here is: for how long after RELEASE_X_Y are binary > patches for it made available? I build FreeBSD Update patches for all the branches supported by the FreeBSD Security Team. To answer a couple of other questions: FreeBSD Update is something which I _personally_ support; it isn't supported by the _project_, because at the moment there isn't anyone else who could take over running it if I get hit by a bus. Re the long list of requests people have made (starting with "amd64 support" and "make this officially supported by the project"), I'll get to those as soon as I have time. Sadly, I have a pesky thing called "a full time job" and my FreeBSD time has been occupied with portsnap lately. Colin Percival ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
On Fri, 23 Dec 2005 19:26, Matthew D. Fuller wrote:
> > the Internet? I was planning to use NFS/TCP secured by IPSec
> > transport mode, but anything less complicated would be greatly
> > appreciated ;-)
>
> This is one of the situations where r{dist,sync}'ing out the binaries
> makes more sense than NFS mounting and running installworld (which
> would be awful awful slow, above and beyond security and convenience
> issues).
I guess one problem is that is replicating installworld's behaviour can be
difficult as it does more than just install files sometimes.
--
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
-- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
pgpJLWYEOBSRc.pgp
Description: PGP signature
ipfilter upgrade issue
Hi All, Just a smallish issue with ipfilter and upgrading from 5.4 to 6-STABLE. The ipfilter implementation in the 6-STABLE kernel errs on the commands sent by the 5.4 ipf binary. This can be an issue when you are upgrading remotely without serial console and you have IPFILTER_DEFAULT_BLOCK enabled: after rebooting in the 6-STABLE kernel no firewall rules will be loaded and you cannot access the box anymore to make installworld.. Best, Koen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006)
On Thu, Dec 22, 2005 at 09:08:13PM -0600, Matthew D. Fuller wrote: > > No, you're missing the point. More core OS upgrades means less > > incremental patches (which are easier to apply than a full update). > > Right. I don't understand how B follows A here. > > These patches come from where? Security advisories, mailing list > discussions, and eating too much beef right before bed and waking up > at 2am with brilliant ideas? Why would there be less of them, just > because RELENG_X_Y_RELEASE tags are laid down more often? I think the real concern here is: for how long after RELEASE_X_Y are binary patches for it made available? If the policy is "every RELEASE_X_Y has binary patches available for Z months after its release", then clearly it doesn't matter how many RELEASE_X_Y's are made in this period. If the policy is "binary patches are made available for the last N releases", then the availability lifetime of binary patches is (N * release interval). As long as N is made sufficiently large, then it's not a problem. There is a risk that reducing the interval between releases does not cause a corresponding increase in N, thus forcing people to perform full updates to a new release more often. > > Huh? That's backwards. If we can't schedule the downtime for a > > full operating system upgrade (which takes far longer than it > > should) then the system won't get upgraded. > > Having done full OS upgrades a number of times, I can't remember the > last time it took more than 5 or 10 minutes ... > For small groups of servers, I NFS mount > installworlds, and for larger groups, I rdist out binaries. But it > always comes from source. That's good for you and a certain clan of highly experienced FreeBSD system administrators. However I believe that there's a far larger pool of people for whom binary installs and upgrades makes much more sense. At one end of the spectrum are those bailing out from Linux, and the other end are people who want an audit trail for every binary back to a 3rd-party release medium. (I started off in the first group, but now fall into the second) Regards, Brian. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
On Fri, Dec 23, 2005 at 09:51:15AM +0100 I heard the voice of
Patrick M. Hausen, and lo! it spake thus:
>
> Any suggestions for an alternative to NFS if your 'client' servers
> are located "all over the world" and you want to installworld across
> the Internet? I was planning to use NFS/TCP secured by IPSec
> transport mode, but anything less complicated would be greatly
> appreciated ;-)
This is one of the situations where r{dist,sync}'ing out the binaries
makes more sense than NFS mounting and running installworld (which
would be awful awful slow, above and beyond security and convenience
issues).
--
Matthew Fuller (MF4839) | [EMAIL PROTECTED]
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 )
Hi, Folks! > On your central PC.. > buildworld once. > builkernel once for each of the different kernels you are using. > > On each 'client' PC.. > NFS mount /usr/src and /usr/obj > installkernel > reboot > installworld Any suggestions for an alternative to NFS if your 'client' servers are located "all over the world" and you want to installworld across the Internet? I was planning to use NFS/TCP secured by IPSec transport mode, but anything less complicated would be greatly appreciated ;-) Anyone using ggated/ggatec for that purpose? Thanks, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: lsof on 6.0
> On Thursday 22 December 2005 16:27, Danny Braniss wrote: > > > > > > Do you have a mount which is a symlink? > > > > > > > > no, but many nfs. > > > > minbari> mount > > > > 132.65.16.100:/d/6 on / (nfs) > > > Breakpoint 1 at 0x402779: file dmnt.c, line 159. > > (gdb) run > > Starting program: > > /home/pobj/r+d/ports/sysutils/lsof/work/lsof_4.77A.freebsd/ls of > > lsof: WARNING: access /root/.lsof_shuttle-3: No such file or directory > > lsof: WARNING: can't open /root/.lsof_shuttle-3: Read-only file system > > > > Breakpoint 1, dev2udev (c=0xe) at dmnt.c:159 > > 159 if (ln != dn) > > (gdb) print sr > > $1 = -1 > > (gdb) print ln > > $2 = 0x525140 "132.65.16.100:/d/8" > > (gdb) print dn > > $3 = 0x525140 "132.65.16.100:/d/8" > > As I figured, statsafely (which wraps around stat(2)) returns -1 on your nfs > mount, therefore ss never gets set. I've got no idea what the "user device > random seed" is needed for, so I suggest you file a pr with the above info. > > Additionally, you can try the following patch to see why exactly the stat(2) > call fails: > --- dmnt.c.orig Mon Oct 3 15:22:52 2005 > +++ dmnt.c Thu Dec 22 16:51:23 2005 > @@ -163,6 +163,9 @@ > dn = (char *)NULL; > if (sr) > continue; > + else > + (void)fprintf(stderr, "%s: cannot stat %s: %s\n", Pn, ln, > strerror(errno)); > + > ss = 1; > s = (u_int)sb.st_ino ^ (u_int)sb.st_rdev; > break; > well, your patch has problems, but at least it pointed in the direction :-) / (root) is nfs mounted. the problem is in process_node(va) in dnode.c, that sets vtag to VT_UFS instead of VT_NFS because vtbuf is "ufs" after a call to kread((KA_T)v->v_tag... so, can someone with some more knowledge in vnodes follow this? I suspect the problem is in the kernel ... danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
