Re: BuildingFreeBSDWithClang (was: Re: (no subject))
On Tue, 22 May 2012 13:04:59 +0200, S.N.Grigoriev serguey-grigor...@yandex.ru wrote: Hi list, I tried to build world and kernel with CLang on my 9-stable amd64 system. The following errors occured: mv -f term.h.new term.h cat /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include/curses.tail curses.h.new mv -f curses.h.new curses.h cc -o make_keys -O2 -pipe -I. -I/usr/obj/lib32/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -Qunused-arguments -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/make_keys.c cc -o make_hash -O2 -pipe -I. -I/usr/obj/lib32/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -Qunused-arguments -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -DMAIN_PROGRAM /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tinfo/comp_hash.c cc: unrecognized option '-Qunused-arguments' cc: unrecognized option '-Qunused-arguments' cc1: error: unrecognized command line option -Wno-empty-body cc1: error: unrecognized command line option -Wno-empty-body cc1: error: unrecognized command line option -Wno-string-plus-int cc1: error: unrecognized command line option -Wno-tautological-compare cc1: error: unrecognized command line option -Wno-parentheses-equality cc1: error: unrecognized command line option -Wno-string-plus-int cc1: error: unrecognized command line option -Wno-tautological-compare cc1: error: unrecognized command line option -Wno-parentheses-equality *** Error code 1 *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error The only statement in my /etc/src.conf is `WITH_CLANG_IS_CC=yes'. Should I use additional configuration options to successfully build the system with CLang? Thanks, Serguey. http://wiki.freebsd.org/BuildingFreeBSDWithClang ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: (no subject)
Hi Thorsten,
On 9 June 2010 18:11, Thorsten Baumeister to...@gmx.net wrote:
Hi everyone!
I have a problem to get my KDE4 Terminal working. I use a German keyboard,
and I am not able to use some special keys. Especially I miss the pipe symbol
('|'), but there are some more like '§', '@', '€'. I compiled KDE on my own
computer running a FreeBSD 8.0-STABLE kernel. All packages are up to date.
Any hints? If I use an SSH connection (PuTTY), everything is fine.
I created a /etc/X11/xorg.conf file using
# X -configure
and added/changed the following section:
Section InputDevice
Identifier Keyboard0
Driver keyboard
Option XkbModel pc105
Option XkbLayout de
Option XkbVariant nodeadkeys
Option XkbOptions terminate:ctrl_alt_bksp
EndSection
The last Option line isn't necessary, but it makes it possible to
terminate the X server by pressing Ctrl+Alt+Backspace, which has been
deactivated in recent default configurations.
If you add the above mentioned Section InputDevice, make sure that
the Section ServerLayout contains a CoreKeyboard entry matching the
given identifier. In my case, Section ServerLayout looks like:
Section ServerLayout
Identifier XFree86 Configured
Screen 0 Screen0 0 0
InputDeviceMouse0 CorePointer
InputDeviceKeyboard0 CoreKeyboard
Option Clone off
EndSection
HTH
Christian Walther
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: (no subject)
On Wed, 30 Sep 2009, Oliver Lehmann wrote: A colleague of mine has the same disks in a new Nvidia Atom 330 system and he told me that he reaches around 70MB/sec write speed with a single large file on a single disk running linux 2.6. I hooked the disk up to my client: FreeBSD 7.2-STABLE #0: Tue Jul 28 12:59:47 CEST 2009 CPU: AMD Athlon(tm) 64 Processor 3500+ (2200.10-MHz K8-class CPU) usable memory = 2138615808 (2039 MB) atapci0: VIA 6420 SATA150 controller port 0xd000-0xd007,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xb800-0xb80f ,0xb400 -0xb4ff irq 20 at device 15.0 on pci0 ad4: 953869MB WDC WD10EADS-00L5B1 01.01A01 at ata2-master SATA150 because the on-board controller is a VIA 6420 I had to set the SATA150 Jumper on the harddisk to have the controller detect the drive. I found I was getting timeouts with this controller and exactly those drives even with the SATA150 jumper connected. In the end I got a PCI Silicon Image 3114 based controller and it worked fine. That said I gave up on the hardware as I couldn't get the motherboard to boot off the CF/IDE adapter so I got an AMD SB700 based board which works well (fingers crossed :) I didn't do any stand alone drive performance tests though. -- 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 signature.asc Description: This is a digitally signed message part.
Re: (no subject)
On Sat, 29 Aug 2009 15:03:51 -0700 (PDT) Richard Mahlerwein mahle...@yahoo.com wrote: I'm at a loss. Google's been of little help, and searching these lists hasn't turned up much either. Does anyone have a further recommendation on what to do, try, test or change? BTW, I'm GENERIC. Do you have any kmod's from ports on that system? Loaded in loader.conf maybe? If so, try to no load them and see what happens. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: (no subject)
--- On Sat, 8/29/09, Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote: Do you have any kmod's from ports on that system? Loaded in loader.conf maybe? If so, try to no load them and see what happens. HTH -- Regards, Torfinn Ingolfsen Addendum: While I found I can do a buildworld while in single user mode without error, I have also notice that, AS I SHUT DOWN from there it gives the same fatal trap 12 error. I hadn't always noticed because if I wait for 15 seconds it reboots anyway. So, in regular mode it fails at boot up. In single-user mode it's usable until I try to shut down. I do not believe I have anything of my doing in loader.conf - it's basically a samba box without much else on it. I'll check it specifically later after the kids are in bed. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: (no subject)
On Tue, Sep 23, 2008 at 11:22:24PM -0500, Mark Linimon wrote: On Wed, Sep 24, 2008 at 09:32:52AM +1000, jonathan michaels wrote: thank you gentle peoples for working out this solution. Unfortunately it has not been 'worked out' with the decision-makers. It has been suggested. Doing s/suggested/agreed to/ is not an automatic process. i am not really good with this whole english/words usage thing, i am sorry that i have caused this grieft, it was not my intention but that seems to be somewhat mute as i managed to fall foul again .. perhaps one day sorry for taking my ... whats teh point.. again, sincere apologies to all concerened, for teh inconvience that i have caused. much kind regards and appreciations jonathan -- powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system === appropriate solution in an inappropriate world === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
Hello Oliver, On 5/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get work a WMP54G Linksys Wireless card. I should work with .ko normal driver (ra.ko or ral.ko don'r remember) but it doesn't. I tried with ndisgen and so on ... In fact all what i found on google don't work more than 2 seconds. The ndisgen is the one who work the best but as soon as you want to ping or transmit data, it cause a kernel crash. It work on all other systèmes (NetBSD, OpenBSD, Linux and so on) I'm not an expert and i'll give up if i'm not helped. Can you please help me ? Thanks a lot, Olivier Check these links, and I think your card would work if you recompiled your kernel with RELENG_6 and not 6.2-RELEASE. http://www.bsdforums.net/forums/showthread.php?t=44385 http://www.bsdforums.net/forums/showthread.php?t=47403page=2pp=15 http://www.mail-archive.com/freebsd-stable@freebsd.org/msg87311.html I hope it helps you out. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
On Thu, May 10, 2007 at 10:03:41AM +0200, [EMAIL PROTECTED] wrote: I'm trying to get work a WMP54G Linksys Wireless card. I should work with .ko normal driver (ra.ko or ral.ko don'r remember) but it doesn't. The problem might be that wireless card manufacturers sometimes switch the chipset on the card without changing the type number. So before you buy a card, you need to know the chipset that is used on the card, so you can check if it is supported. Sometimes you can see it on the packaging, but usually you have to take a look at the card. And it can happen that all the chips are behind a metal shield, in which case you're out of luck. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp3WpNPYPE0O.pgp Description: PGP signature
Re: (no subject)
David Kalliecharan wrote: Hello Everyone! I seem to have run into a snag as I am trying to install FreeBSD Stable or Current (preferrable stable) on a HP Pavilion dv6308ca AMD Turion X2, No avail not even with current (installer lags?) due to the ACPI? Cannot upgrade bios because it is at the highest version. Anyway I was wondering about installing FreeBSD Stable on a Compaq Presario AMD Sempron Processor 3500+ 1.8GHz Laptop (V6317CA) - Future Shop Exclusive Will this go through the same problems as a dv6308ca pavilion? The reason I ask for the compaq presario is that it has a sempron and will hopefully not go through the same problem as a AMD turion X2. Any information will be appreciated! I've got a AMD Sempron 3100+ in a desktop at home with a MSI mainboard and FreeBSD 6.2 installed fine on it with no problems. Haven't done much with it since the install (yet), but the install went smooth as silk. -Proto ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
On 2007-May-04 08:54:11 -0600, David Kalliecharan [EMAIL PROTECTED] wrote: I seem to have run into a snag as I am trying to install FreeBSD Stable or Current (preferrable stable) on a HP Pavilion dv6308ca AMD Turion X2, No avail not even with current (installer lags?) due to the ACPI? Cannot upgrade bios because it is at the highest version. Can you be more specific about what problems you are seeing. Are you trying to install the i386 or amd64 version? Does it work if you disable ACPI? Have a look through PR i386/104678: SMP not working on Turion XP Laptop and see if this helps. Anyway I was wondering about installing FreeBSD Stable on a Compaq Presario AMD Sempron Processor 3500+ 1.8GHz Laptop (V6317CA) - Future Shop Exclusive Will this go through the same problems as a dv6308ca pavilion? Without knowing exactly what problem you are having on the dv6308ca, it's difficult to answer this. Note that, based on my experiences trying to resolve a faulty-on- delivery laptop with HP Support , I would not recommend buying HP at all. -- Peter Jeremy pgpUmDHcj3Xmp.pgp Description: PGP signature
Re: (no subject)
- Original Message - From: Andy Jema [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-stable@freebsd.org Sent: Wednesday, March 22, 2006 6:07 AM Subject: (no subject) Hello! I gave a new try to 6.1-BETA4 on my Blade 150 recently but there are some errors still spitting out during an installation: acd0: TIMEOUT - READ_BIG retrying (1 retry left) Interrupt storm detected on vec1996:; throttling interrupt source acd0: TIMEOUT - READ_BIG retrying (1 retry left) hw.ata.atapi_dma to 0 dmesg: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.6, 512 MB memory installed, Serial #53155393. Ethernet address 0:3:ba:2b:16:41, Host ID: 832b1641. Rebooting with command: boot cdrom Boot device: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f File and args: Perhaps similarly: http://groups.google.com/group/mailing.freebsd.current/browse_frm/thread/4953b4952a84db2d/8498b3cbc5b01ca1#8498b3cbc5b01ca1 Why I think it's related: timeouts and interrupt storm in ata, only since 6.1beta4 or very recently before that (6.0stable-snap011 was fine) only when CPUTYPE is not ix86 In this case the hardware is x86 (athlonxp) so it looks like it's merely changing CPUTYPE that breaks it. Changing cputype from stock to i686 does not break it. athlon-xp is kind of silly and makes little performance difference as far as I can tell for the things I do on that box so i686 is fine, but yours, mine some other recent messages just looks like a pattern to me. Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBxLinux SCO FreeBSD#callahans Satriani Filk! FreeBSD/sparc64 boot block Boot path: /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:f Boot loader: /boot/loader Consoles: Open Firmware console Boot path set to /[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a FreeBSD/sparc64 bootstrap loader, Revision 1.0 ([EMAIL PROTECTED], Thu Mar 16 00:29:29 UTC 2006) bootpath=/[EMAIL PROTECTED],0/[EMAIL PROTECTED]/[EMAIL PROTECTED],0:a Loading /boot/defaults/loader.conf /boot/kernel/kernel data=0x490f08+0x5bbb8 syms=[0x8+0x63960+0x8+0x5396f] / Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/boot/kernel/kernel]... nothing to autoload yet. jumping to kernel entry at 0xc006. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-BETA4 #0: Thu Mar 16 15:20:20 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter tick frequency 65000 Hz quality 1000 real memory = 536870912 (512 MB) avail memory = 506642432 (483 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (650.00 MHz CPU) nexus0: Open Firmware Nexus device pcib0: U2P UPA-PCI bridge on nexus0 pcib0: Hummingbird compatible, impl 0, version 0, ign 0x7c0, bus A pcib0: [FAST] pcib0: [FAST] pcib0: [GIANT-LOCKED] pcib0: [GIANT-LOCKED] pcib0 dvma: DVMA map: 0xc000 to 0xc3ff pci0: OFW PCI bus on pcib0 ebus0: PCI-EBus3 bridge mem 0xf000-0xf0ff,0xf100-0xf17f at device 12.0 on pci0 ebus0: idprom: incomplete ebus0: flashprom addr 0-0xf (no driver attached) eeprom0: EEPROM/clock addr 0x1-0x11fff on ebus0 eeprom0: model mk48t59 eeprom0: hostid 832b1641 isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 gem0: Sun ERI 10/100 Ethernet Adaptor mem 0x40-0x41 at device 12.1 on pci0 miibus0: MII bus on gem0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto gem0: 2kB RX FIFO, 2kB TX FIFO gem0: Ethernet address: 00:03:ba:2b:16:41 fwohci0: Sun PCIO-2 mem 0x42-0x4207ff,0x422000-0x4227ff at device 12.2 on pci0 fwohci0: OHCI version 1.0 (ROM=0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:03:ba:ff:fe:2b:16:41 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: IEEE1394(FireWire) bus on fwohci0 sbp0: SBP-2/SCSI over FireWire on firewire0 fwe0: Ethernet over FireWire on firewire0 if_fwe0: Fake Ethernet address: 02:03:ba:2b:16:41 fwe0: Ethernet address: 02:03:ba:2b:16:41 fwe0: if_start running deferred for Giant fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop = 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) ohci0: Sun PCIO-2 USB controller mem 0x200-0x2007fff at device 12.3 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: Sun PCIO-2 USB controller on ohci0 usb0: USB revision 1.0 uhub0: (0x108e) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pci0: old, non-VGA display device at device 3.0 (no driver attached) pci0: multimedia, audio at
Re: (no subject)
You know, I tried printing it out, but I still can't see the naked lady... Site wrote: Ñ èíñòðóìåíò ìàðêåòèíãà! Ìû ïðèâûêëè ê òîìó, ÷òî ñ àéò, ýòî òî, ÷òî ìû âèäèì, íàáðàâ àäðåñ â Èíòåðíåò Íî ñàéò ìîæåò áûòü ìîùíûì è ìàðêåòèíãà, áîëüøèì ïîìîùíèêîì â âà áèçíåñå. Çà âíåøíîñòüþ ñàé äîñòóïíîé òîëüêî êëèåíòàì, ìîæåò ðàñïîëà ãàòüñÿ áàçà äàííûõ, êóäà ñîá èíôîðìàöèÿ î êëèåíòàõ, áèáëèîòåêà, ê ñîäåðæèò ôîðìû è øàá äîêóìåíòîâ, äëÿ ïîëüçîâàíèÿ âñåìè ì åíåäæåðàìè è ò.ä. Îäíîé èç íîâ ðàçðàáîòîê íàøåé êîìïàíè è, ÿâëÿþòñÿ òàê íàçûâàåìûå ñàéòû. Ò.å., çà âíåøíåé ñòîðîíî ñàéòà, íàõîäèòñÿ ðàáî÷èé ñàéò, êîòîðûé äîñò òîëüêî ðàáîòíèêàì ôèðì Ðóêîâîäèòåë âîçìîæíîñòü â óäàëå ðåæèìå äàæå ïðîâîäèòü â èðòóàëüíûå ïëàíåðêè. Ñàéòû, òàê æå ìîãóò áûòüîáúåäèíåíû ñ eCRM ñèñòåìîé. ×òî îíà äàåò ä áèçíåñà: * Ñîõð öåëîñòíîñòü êëèåíòñê áàçû. + Âåäåíêëèåíòñêîé áàçûôèêñèðóþòñÿ âñå àñïåêòû âçàèìîîòíîøåíèé ñ êëèåíòàìè + Èçáåæêëèåíòñêîé áàçñëó÷àå ïåðåõîäà ìåíåäæåêîíêóðèðóþùóþ êîìïàíèþ. Âåäåíèå êëèåíòîâ óâîëèâøåãîñÿ ìåíåïîðó÷èòü äðóãîìó ñîòðóäíèêó, ïðè÷åì íîâè÷îê ïîëóïîëíûå äàííûå îá èñòîðèè âçàèìîîòíîøåíèé êîìïàíèè ñ ýòèìîæåò ïðîäîëæàòü óñïåøíî ðàáîòàòü ñ íèìè; + Ñîõðàñ òåìè, êòî íêëèåíòîì êîìïàíèè èëïåðåñòàë èì áûòü, ïåðèîäè÷åñêèïðåäëîæåíèå íîâûõ óñëóã èëè áîëåå âûãîäíûõ öåíîâûóñëîâèé. + Ýôôåêâçàèìîäåéñòâèå ìåæäóîòäåëàìè êîìïàíèè. * Ïîâû ýôôåêòèâíîñòè ïðîäàæ. + ×åòêîñòü, ïëàíèðîâàíèå è êîíòðîëü äåéñòâèé ìåíåäæåðà. Èçâåñòíî, ÷òî â êîìïàíèÿõ ÷àñòî òåðÿþòñÿ êîíòàêòû ïîñëå ïåðâè÷íûõ çâîíêîâ ïîêëèåíòîâ . + Óïðîùâðåìåíè, çàòðà÷èâàåìîãî íà ïðîöåññ ïîäñäåëêè * Ïîâû ýôôåêòèâíîñòè ìàðêåòè íãà. + Íà îñíîâå äàíêëèåíòå, ñîáðàííûõ â ðåçóëüòàòå ðàáîòû ñ íèì è ó÷òåííûõ â ñèñòåìå, ìîæí + Ôîðìèðîâàòü ïîðòðåò öåëåâîãî êëèåíòà + Èññëåïðåäëàãàåóñëóãè + Àíàëèçèðîâàòüýôôåêòèâíîñòü ðåêëàìíûõ è ìàðêåòèíãîâûõ àêöèé + Èçó÷àïî êàæðåãèîíó è ò.ï * Îò÷ äåÿòåëüíîñòè. + Âñÿ èíôîðìàöèÿêàêóþ ðàáîòó ìåíåäæåðû ïðîäçà îïðåäåëåííûé ïåðèîä, àâòîìàòè÷åñêè ñîáèðàåòñÿ â ñèñòåìå,ôîðìèðóÿ îò÷åòíîñòü äëÿ ðó + Èñïîëüçóÿ ñèìîæíî ïîëó÷àòü îò÷åòû î òîìïðîãíîçû ïïðîäàæàì, êàêèå ïðè âëå÷åíû êëèåíòû, êàêîâ âêëàä êàæäîãî ìåíåäæåðà ñóììó ïðîäàæ, êàêîâîñîîòíîøåíèå ïëàíèðóåìîé è ôàêòè÷åñêîé äîõîäíîñòè ïî êàæäîé èò.ï. Òî åñòü ìîæíî ïîëó÷èòïî ëþáèíôîðìàöèè, ôèêñèðóåòñÿ â ñèñòó÷åòà îòíîøåíèé ñ êëèåíòàìè Òåëåôîí +7 495 225 30 0 (ìíîãîêàíàëüíûé) q5PPv ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
On Sunday 08 January 2006 02:37 am, Christer Solskogen wrote:
Hi!
I got myself a mainboard with the ICH7 chipset. This chipset is
supported in FreeBSD, but on my board it had a problem. It found
only 2 of my four disks (ad0 and ad2) I tried updating to
6.0-stable (from 6.0-release) but the problem resist.
I found a patch at bsdforums that did indeed work.
Could anyone review this, and commit it, please?
It is generally best to file a PR so this stuff doesn't get lost.
Also check to see if this is in current via cvsweb.freebsd.org, and
if it is emailing the responsible commiter about MFC'ing that change
will give you an authoritative answer on what's up.
Taken from
http://www.bsdforums.org/forums/showthread.php?threadid=37304
--- ata-chipset.c Thu Oct 13 10:07:46 2005
+++ ata-chipset-ich7.c Sun Dec 11 23:25:48 2005
@@ -1845,10 +1845,13 @@
struct ata_channel *ch = device_get_softc(dev);
int mask, timeout;
-/* ICH6 has 4 SATA ports as master/slave on 2 channels so deal
with pairs */
+/* ICH6/7 has 4 SATA ports as master/slave on 2 channels so
deal with pairs */
if (ctlr-chip-chipid == ATA_I82801FB_S1 ||
ctlr-chip-chipid == ATA_I82801FB_R1 ||
- ctlr-chip-chipid == ATA_I82801FB_M) {
+ ctlr-chip-chipid == ATA_I82801FB_M ||
+ ctlr-chip-chipid == ATA_I82801GB_S1 ||
+ ctlr-chip-chipid == ATA_I82801GB_R1 ||
+ ctlr-chip-chipid == ATA_I82801GB_M) {
mask = (0x0005 ch-unit);
}
else {
--
Anish Mistry
pgpAYFioqGAbR.pgp
Description: PGP signature
Re: (no subject)
On Mon, Nov 28, 2005 at 10:40:55PM -0500, Matthew Tomsa wrote: What is the difference between RELEASE versions, STABLE versions, and CURRENT versions? Please see the following: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/version-guide/ mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (no subject)
Matthew Tomsa wrote: What is the difference between RELEASE versions, STABLE versions, and CURRENT versions? I've done some reading but I'm still a bit confused. Thanks. -CURRENT is alpha. -STABLE is supposed to be the leading edge of functionality yet be stable enough for production use; it should be treated as a late beta. In other words, test it before deploying in production, because sometimes, perhaps a day or two per month, -STABLE contains problems or breakage. Every few months, the project makes an effort to stabilize the source tree (including ports and docs), generates a release candidate or two, and then pushes out a RELEASE by tagging the -STABLE branch. A -RELEASE or security branch is intended for production use because it has undergone such testing, and is updated with security patches and critical fixes only after such changes have been tested in -CURRENT or -STABLE. If you don't know what to run, run the security branch (ie, RELENG_5_4). -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
CVS, was: Re: no subject
Denis Holmes wrote: star-one[34](~/Mail)-grep -c '^From ' cvs 3818 star-one[35](~/Mail)-ls -l cvs -rw--- 1 dholmes user 13861315 Mar 14 10:15 cvs In 25 days, that's 150 messages (and over .5 meg) per day. While good information to have, it's practically a full-time job to read all of these; the number of messages rivals the questions list. It also normally tells you what was done (in extremely general terms), not what is still to come and what dependency relationships exist. I learned a lot reading those - after some weeks you'll learn to separate the important from the less important messages ;-) Hint: look at an original message and usually the first two replies only, if the original poster described a problem you might encounter ;-) o Usually one can 'ignore' makeworld broken signal 11 messages. o Important are the HEADS UP ones, and reading the /usr/src/UPDATING. Not to mention the problems of then knowing which changes have hit one's chosen mirror, and whether it happens to be in the middle of receiving a major commit, with commits happening round the clock. It seems to me that pretty much all one can do is pull an update and hope for the best, and repeat until it works. Cvsup twice with about 1-5 minutes in between. If nothing changed, you're usually on the sure side that you didn't cvsup in the middle of a commit. So far this gave me next to no trouble during the last 6-12 months at least. I'm new to tracking -stable and so would gladly welcome corrections and suggestions, but this is the impression I've been getting from the mail discussions. The first impression is of course that there are lots of things that don't work (due to the amount of messages), but usually these are only minor bugs where only some people with matching hardware/combinations have real problems. Apart from that, you can always reboot your latest known working kernel if you so wish (have a look at the handbook, make a copy of the known working kernel - even though the default make installkernel will make a copy of the last kernel - and of the modules-directory). [Dare I mention that updated ports are only officially supported on -stable and -current, implying that one must track an update path in order to use applications since previous versions of dist files can disappear rather quickly?] You can get a DVD-release with _most_ distfiles from FreeBSD Services. Most of the usually needed distfiles / packages are on the standard CD-Sets (a purchase of one of those will also help FreeBSD hint,hint ;-) ). http://www.freebsdmall.com/ The 'Original' http://www.freebsdservices.co.uk/ DVD-Distribution http://www.bsdmall.com/ DN-Distribution Basically Daemonnews- and FreeBSDmall-Distributions are the same. Just curious: How did you manage to get your mail sent without any header-information? Regards, Holger -- Holger Kipp, Dipl.-Math., Systemadministrator | alogis AG Fon: +49 (0)30 / 43 65 8 - 114 | Berliner Strasse 26 Fax: +49 (0)30 / 43 65 8 - 214 | D-13507 Berlin Tegel email: [EMAIL PROTECTED] | http://www.alogis.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
