Re: Could you please fix this ?
On Thu, 3 Dec 2009 01:57:50 +, Leonardo Santagostini
lsantagost...@gmail.com wrote:
Hello everybody,
I was facing one big problem, i have a notebook, which is an Acer
Aspire 5920. If you like i can send to you my messages file.
Which is:
Intel(R) Core(TM)2 Duo CPU T5550 @ 1.83GHz (1833.48-MHz 686-class CPU)
Intel(R) PRO/Wireless 3945ABG
Broadcom NetLink Gigabit Ethernet Controller
2 Gigs RAM
160 Gigs SATA
The point was:
With ACPI disabled, i managed to boot but without WIFI; and with ACPI
enabled, the boot process hanged up all times.
I fixed this adding
if (device_get_unit(dev)==2){
pci_write_config(dev, PCIR_COMMAND, PCIM_CMD_MEMEN | PCIM_CMD_PORTEN,
1);
pci_enable_busmaster(dev);
pci_write_config(dev, PCIR_IOBASEL_1, 0xf0, 1);
pci_write_config(dev, PCIR_MEMBASE_1, 0xf020, 2);
pci_write_config(dev, PCIR_MEMLIMIT_1, 0xf020, 2);
pci_write_config(dev, PCIR_PMBASEL_1, 0xfff1, 2);
}
if (device_get_unit(dev)==3){
pci_write_config(dev, PCIR_COMMAND, PCIM_CMD_MEMEN | PCIM_CMD_PORTEN,
1);
pci_enable_busmaster(dev);
pci_write_config(dev, PCIR_IOBASEL_1, 0xf0, 1);
pci_write_config(dev, PCIR_MEMBASE_1, 0xf030, 2);
pci_write_config(dev, PCIR_MEMLIMIT_1, 0xf030, 2);
pci_write_config(dev, PCIR_PMBASEL_1, 0xfff1, 2);
}
to /usr/src/sys/dev/acpica/acpi_pcib_pci.c running on a 8.0-RELEASE
I was able to fix it by my way but many people cant do it, so, i would
really appreciate if you can add this piece of code.
Hi Leonardo.
Jung-uk Kim has done a lot of ACPI-related work, so he will probably
know if the change is ok to commit to stable/8. I've added him to the
thread, so he can let us know what he thinks of the change. Can you
please post a diff that also shows _where_ the changes have to be
installed in our current version of src/sys/dev/acpica/acpi_pcib_pci.c
for 8.0-RELEASE?
___
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: 8.0-RELEASE completed...
On Sun, 29 Nov 2009 11:30:18 -0800, Gary Kline kl...@thought.org wrote: * There have been a lot of changes in the kernel configuration. If you want a custom kernel, start anew from the 8.0 GENERIC kernel so you don't miss anything. Could somebody who's running a 32biter send a GENERIC from 8.0 so I can diff? You can always grab the latest version of GENERIC for 8.X from: http://svn.freebsd.org/viewvc/base/stable/8/sys/i386/conf/GENERIC Just follow the view link of the latest revision. ___ 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: 8.0-RELEASE and Emacs port
On Thu, 30 Jul 2009 16:42:26 +0900, Byung-Hee HWANG b...@izb.knu.ac.kr wrote: Hello! A few hours ago, Chong Yidong, Emacs maintainer, has been released Emacs 23.1 on gnu.org's mailing lists. Since i use Emacs as default mailer, i really want that FreeBSD Project Release Team to add Emacs 23.1 (Stable Ver.) into FreeBSD 8.0-RELEASE. Because i use only -RELEASE branch as far as i possibly can. Then i can use pkg_add instead of ports, so easily. Thanks in advance ..;; Hi Byung-Hee, AFAIK, The ports are not frozen yet. I think we can make it by updating the port before this weekend. There is a bit of testing to make sure that we can repo-copy the editors/emacs port to editors/emacs22 and check that the new editors/emacs port for 23.1 works fine. I'm working on it, and I will post patches soon-ish :) pgpAJZYPn7zwe.pgp Description: PGP signature
Re: Request for testing - top 3.8b1 in the base system
On Sun, 28 Sep 2008 15:46:20 +1000, Edwin Groothuis [EMAIL PROTECTED] wrote: I have made an update for the top(1) utility in the FreeBSD base system to get it from the 3.5b12 version to the 3.8b1 version. Thank you! :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regression in 7.0BETA2: unionfs and cd9660
On 2007-11-17 22:29, Ivan Voras [EMAIL PROTECTED] wrote: Hi, I'm reporting a regression in recent RELENG_7, it was present (and I've reported it) on BETA2, and I sadly confirm that it's also present in BETA3. The problem is that cd9660 doesn't want to be the underlying layer for unionfs. How to repeat: Boot a system with root on cd9660 (e.g. LiveCD), then create a UFS-based md/mfs, then try to mount it via unionfs over (e.g.) /etc: # ...make a ram-drive / memory file system on /tmp # mount_unionfs /tmp /etc mount_unionfs: /etc: operation not supported by device This worked ok with BETA1 and even -CURRENT versions, and I've located the breaking point somewhere between: #*default date=2007.11.07.00.00.00 # #*default date=2007.11.08.00.00.00 I don't know if the date is local or UTC, [...] FWIW, if these are dates used as -D 'arg' in cvs(1), then they are UTC. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/man/man8/MAKEDEV.8
On 2007-10-30 18:26, Giorgos Keramidas [EMAIL PROTECTED] wrote: There are also a couple of manpages with references to very long URIs, which cannot be wrapped by nroff in a reasonable line-length: ng_netflow.4 bluetooth.device.conf.5 I don't think we can easily fix these, without manually wrapping the URIs, but that may 'break' copy/pasting of the URIs :/ Fixed with a bit of help from our resident groff-guru, Ruslan :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/man/man8/MAKEDEV.8
On 2007-10-29 12:18, Jeremy Chadwick [EMAIL PROTECTED] wrote:
On Mon, Oct 29, 2007 at 03:24:47PM +0200, Giorgos Keramidas wrote:
On 2007-10-28 12:54, Andrew Lankford [EMAIL PROTECTED] wrote:
Thbbt! I'm reading the catman version of MAKEDEV. Wish I could
disable that feature. Oh well. I'll delete it all and rebuild it
again if needed. Thanks!
Ah, that's it then :)
My usual `installworld' steps include this too:
# cd /usr/share/man
# find cat[0-9] \! -type d -exec rm {} +
There's a periodic script (/etc/periodic/weekly/330.catman) which
rebuilds all the catman pages for you. However, it makes an immense
mess of your weekly system mails due to all the manpage/nroff formatting
mistakes. Have a look:
http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html
Very interesting. Maybe we can tweak 330.catman to display the filename
of the manpage which causes each error. Then we could use the periodic
script as an aid to start actually *fixing* the errors :)
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/man/man8/MAKEDEV.8
On 2007-10-30 13:32, Giorgos Keramidas [EMAIL PROTECTED] wrote: http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html Very interesting. Maybe we can tweak 330.catman to display the filename of the manpage which causes each error. Then we could use the periodic script as an aid to start actually *fixing* the errors :) Neat. The base-system manpages which have errors or warnings are just a few of the hundreds we have. I just finished running a slightly modified version of `/etc/periodic/weekly/330.catman', which uses `catman -v' and the list of files with errors (after a bit of manual parsing) is now: % Reformatting manual pages: % /usr/share/man: not writable - will only be able to write to existing cat directories % man directory /usr/share/man % section man1 % format man1/readelf.1.gz - cat1/readelf.1.gz % standard input:151: warning [p 1, 3.8i]: cannot adjust line % standard input:300: warning [p 2, 9.7i, div `an-div', 0.0i]: cannot adjust line % standard input:300: warning [p 2, 9.7i]: cannot adjust line % section man2 % format man2/minherit.2.gz - cat2/minherit.2.gz % mdoc warning: .Fx: Unknown FreeBSD version `2.2.0' (#132) % format man2/sctp_generic_recvmsg.2.gz - cat2/sctp_generic_recvmsg.2.gz % mdoc warning: Empty input line #76 % format man2/sctp_generic_sendmsg.2.gz - cat2/sctp_generic_sendmsg.2.gz % mdoc warning: Empty input line #51 % mdoc warning: Empty input line #88 % format man2/sctp_peeloff.2.gz - cat2/sctp_peeloff.2.gz % mdoc warning: Empty input line #82 % section man3 % format man3/ether_aton.3.gz - cat3/ether_aton.3.gz % mdoc warning: Empty input line #169 % format man3/gss_add_cred.3.gz - cat3/gss_add_cred.3.gz % Not a \-mdoc command: .PP (#89) % format man3/gss_inquire_cred_by_mech.3.gz - cat3/gss_inquire_cred_by_mech.3.gz % mdoc warning: Empty input line #72 % format man3/gss_inquire_mechs_for_name.3.gz - cat3/gss_inquire_mechs_for_name.3.gz % mdoc warning: Empty input line #50 % format man3/gss_seal.3.gz - cat3/gss_seal.3.gz % mdoc warning: A .Bl directive has no matching .El (#146) % format man3/gss_unseal.3.gz - cat3/gss_unseal.3.gz % mdoc warning: A .Bl directive has no matching .El (#159) % format man3/gss_wrap_size_limit.3.gz - cat3/gss_wrap_size_limit.3.gz % mdoc warning: A .Bl directive has no matching .El (#131) % format man3/lwres_gabn.3.gz - cat3/lwres_gabn.3.gz % standard input:45: warning [p 1, 5.2i]: can't break line % format man3/lwres_gnba.3.gz - cat3/lwres_gnba.3.gz % standard input:45: warning [p 1, 5.2i]: can't break line % format man3/lwres_noop.3.gz - cat3/lwres_noop.3.gz % standard input:45: warning [p 1, 5.2i]: can't break line % format man3/valloc.3.gz - cat3/valloc.3.gz % mdoc warning: Extraneous .Ef (#49) % format man3/zlib.3.gz - cat3/zlib.3.gz % standard input:52: warning [p 1, 7.0i]: cannot adjust line % section man4 % format man4/mac.4.gz - cat4/mac.4.gz % mdoc warning: extraneous .El call (#200) % format man4/md.4.gz - cat4/md.4.gz % mdoc warning: Unknown keyword `-ofset' in .Bd macro (#68) % mdoc warning: Unknown keyword `indent' in .Bd macro (#68) % format man4/ng_netflow.4.gz - cat4/ng_netflow.4.gz % standard input:254: warning [p 3, 3.3i]: can't break line % section man5 % format man5/bluetooth.device.conf.5.gz - cat5/bluetooth.device.conf.5.gz % standard input:93: warning [p 1, 7.2i]: can't break line % format man5/quota.group.5.gz - cat5/quota.group.5.gz % mdoc warning: Unknown keyword `-indent' in .Bl macro (#53) % mdoc warning: Unknown keyword `offset' in .Bl macro (#53) % section man8 % format man8/fwcontrol.8.gz - cat8/fwcontrol.8.gz % mdoc warning: Empty input line #179 % format man8/ifmcstat.8.gz - cat8/ifmcstat.8.gz % mdoc warning: A .Bl directive has no matching .El (#82) % section man9 % format man9/uio.9.gz - cat9/uio.9.gz % mdoc warning: A .Bl directive has no matching .El (#129) % link cat9/zpfind.9.gz - cat9/pfind.9.gz These are just the manpages of the base-system. I think I can handle most of them, so I started patching the non-contrib stuff. - Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/man/man8/MAKEDEV.8
On 2007-10-30 14:16, Giorgos Keramidas [EMAIL PROTECTED] wrote: Neat. The base-system manpages which have errors or warnings are just a few of the hundreds we have. I just finished running a slightly modified version of `/etc/periodic/weekly/330.catman', which uses `catman -v' and the list of files with errors (after a bit of manual parsing) is now: % Reformatting manual pages: % /usr/share/man: not writable - will only be able to write to existing cat directories % [...] Hi again Jeremy. The 'trigger' for using 330.catman and catman -v was very useful indeed :) I've fixed the following manpages in CURRENT, and will MFC the changes after a while (given RE approval for RELENG_7): minherit.2, sctp_generic_recvmsg.2, sctp_generic_sendmsg.2, sctp_peeloff.2, ether_aton.3, gss_add_cred.3, gss_inquire_cred_by_mech.3, gss_inquire_mechs_for_name.3, gss_seal.3, gss_unseal.3, gss_wrap_size_limit.3, valloc.3, mac.4, md.4, quota.group.5, fwcontrol.8, ifmcstat.8, uio.9 There are still some errors/warnings in contrib manpages, like: readelf.1(binutils) lwres_gabn.3 (bind) lwres_gnba.3 (bind) lwres_noop.3 (bind) zlib.3 (zlib) I'll ask the respective contrib-code maintainers before making changes here, to avoid taking files off the vendor branch if it's too bad. There are also a couple of manpages with references to very long URIs, which cannot be wrapped by nroff in a reasonable line-length: ng_netflow.4 bluetooth.device.conf.5 I don't think we can easily fix these, without manually wrapping the URIs, but that may 'break' copy/pasting of the URIs :/ - Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/share/man/man8/MAKEDEV.8
On 2007-10-28 12:54, Andrew Lankford [EMAIL PROTECTED] wrote:
Thbbt! I'm reading the catman version of MAKEDEV. Wish I could
disable that feature. Oh well. I'll delete it all and rebuild it
again if needed. Thanks!
Ah, that's it then :)
My usual `installworld' steps include this too:
# cd /usr/share/man
# find cat[0-9] \! -type d -exec rm {} +
This takes care of deleting any `stale' preformatted manpages, so the
next time I ask for a manpage, it's going to be reformatted.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libpcap/tcpdump update
On 2007-10-19 10:48, Max Laier [EMAIL PROTECTED] wrote: Okay. libpcap 0.9.8 and tcpdump 3.9.8 are now imported into HEAD and RELENG_7. Is anyone eager to pull it down to RELENG_6 as well, because I don't have the resources available at the moment. The update was crucial to me in HEAD and RELENG_7 to get a working pflog tcpdump, but RELENG_6 isn't broken for me ... Any takers? If not I might get round to it eventually, but I'd prefer somebody with genuine interest would step up. Hi Max, I can do this. I may need a bit of help with code-style or parts which I am not very familiar with, but if you think you can do a pre-commit review of the RELENG_6 patches (or alternatively help me find another src-committer who can do this), that would be awesome :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enable more than 256 pty's?
On 2007-10-02 15:41, Vlad GALU [EMAIL PROTECTED] wrote: On 10/2/07, Dag-Erling Sm?rgrav [EMAIL PROTECTED] wrote: Vlad GALU [EMAIL PROTECTED] writes: The symptoms were exhibited even with rev. 1.16. I've CC'ed him so he can catch up with the thread. Which symptoms? I can no longer reproduce the hang-on-close bug. Strangely enough, me neither. In his case, allocated pts' wouldn't get deallocated once the sessions ended. There was an old bug, which caused pts consumers to get stuck in devdrn. This has been fixed, AFAICT, a long time ago. At least, I can't reproduce it any more with the usual tests: * Closing xterm windows. * Closing telnet sessions. * Exiting from screen(1) windows. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to enable more than 256 pty's?
On 2007-10-04 18:05, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/4/07, Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2007-10-02 15:41, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/2/07, Dag-Erling Sm?rgrav [EMAIL PROTECTED] wrote:
Vlad GALU [EMAIL PROTECTED] writes:
The symptoms were exhibited even with rev. 1.16. I've CC'ed him so
he can catch up with the thread.
Which symptoms? I can no longer reproduce the hang-on-close bug.
Strangely enough, me neither. In his case, allocated pts' wouldn't
get deallocated once the sessions ended.
There was an old bug, which caused pts consumers to get stuck in
devdrn. This has been fixed, AFAICT, a long time ago. At least, I
can't reproduce it any more with the usual tests:
* Closing xterm windows.
* Closing telnet sessions.
* Exiting from screen(1) windows.
Weird. 3 people on this thread already saw the symptoms :(
It must be a different problem, then. I used to have a local patch
which reverted the devdrn wait in kern_conf.c:destroy_devl() near
the lines:
753 while (dev-si_threadcount != 0) {
754 /* Use unique dummy wait ident */
755 msleep(csw, devmtx, PRIBIO, devdrn, hz / 10);
756 }
but the original problem I was seeing seems to have been fixed.
At least, I can't reproduce it was easily anymore...
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Announce: FreeSBIE-2.0-RELEASE available!
On 2007-01-15 21:21, Matteo Riondato [EMAIL PROTECTED] wrote: FreeSBIE 2.0-RELEASE (codename Clint Eastwood) is based on the fresh FreeBSD 6.2-RELEASE, both in terms of sources and of packages. My goodness! You guys are fast :) Enjoy FreeSBIE and spread FreeBSD! Go Matteo and FreeSBIE team, go... You have my sincerest thanks and gratitude. For one thing, I used FreeSBIE to test laptops in local computer shops, until I found one that I liked. Without FreeSBIE, I would have had to guess (wrongly, most of the time) or use an inferior OS for my tests. Thank you! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: doc/en_US.ISO8859-1/books/handbook/serialcomms chapter.sgml
On 2006-08-24 10:18, Ceri Davies [EMAIL PROTECTED] wrote: On Wed, Aug 23, 2006 at 11:37:19PM +, Giorgos Keramidas wrote: keramida2006-08-23 23:37:19 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/handbook/serialcomms chapter.sgml Log: Expand the section `Setting a Faster Serial Port Speed', to mention ways to set the serial console speed without having to rebuild the boot blocks. Note that for releases before 6.1, though, rebuilding the boot blocks may be the only option. On a related note, is the keyboard multiplexer now good enough for us to ship a /boot.config containing '-P' on the installation images? Not sure. I think I have heard of problems when kbdmux is used with systems that only have a USB keyboard, but I am not sure if this change would affect the same users. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Securelevels and /dev/io documentation inconsistency
On 2006-07-12 15:47, Alexandros Kosiaris [EMAIL PROTECTED] wrote: Hello, I believe i have stumbled upon a documentation inconsistency concerning securelevels and usage of /dev/io From init(8) manpage 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem, /dev/kmem and /dev/io (if your platform has it) may not be opened for writing; kernel modules (see kld(4)) may not be loaded or unloaded. Note the may not be opened for writing. It is correct for /dev/mem and /dev/kmem but incorrect for /dev/io as the following experiment shows: 3:40pm ~ # sysctl kern.securelevel kern.securelevel: 1 [EMAIL PROTECTED] 3:40pm ~ # head /dev/io head: /dev/io: Operation not permitted [EMAIL PROTECTED] 3:40pm ~ # Now the source code in /usr/src/sys/i386/i386/io.c just checks if securelevel is greater that 0 when opening the device and return accordingly. However from io(4) Note that even read-only access will grant the full I/O privileges. Which means that changing the code to check if the device is opened O_RDONLY and then allowing access would be a mistake cancelling the idea of blocking access to the device through usage of the securelevel. I am correct about the above ? Does the documentation need a correction in that place? It looks like it does. Would something like this be satisfactory? 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem and /dev/kmem may not be opened for writing and /dev/io (if your platform has it) may not be opened at all; kernel modules (see kld(4)) may not be loaded or unloaded. Regards, Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Securelevels and /dev/io documentation inconsistency
On 2006-07-12 20:35, Alexandros Kosiaris [EMAIL PROTECTED] wrote: It looks like it does. Would something like this be satisfactory? 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem and /dev/kmem may not be opened for writing and /dev/io (if your platform has it) may not be opened at all; kernel modules (see kld(4)) may not be loaded or unloaded. Regards, Giorgos Yes it would be. Thank you. It should be fixed in HEAD now, with this commit: Revision ChangesPath 1.47 +4 -3 src/share/man/man7/security.7 After a short period (3 days or so), if there are no objections, corrections or other changes by fellow committers, I'll merge the change to RELENG_6 too. Thanks :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cc can't build 32-bit executables on amd64
On 2006-05-01 16:04, Mikhail Teterin [EMAIL PROTECTED] wrote: Can I direct someone's attention to the annoying but easy to fix bug: http://www.freebsd.org/cgi/query-pr.cgi?pr=gnu/96570 There are still a few days left to make sure, FreeBSD-6.1 is shipped with amd64 being able to link 32-bit executables. Release Engineers insist, it must be fixed in current first... cc can build binaries just fine if you also use the -B option: % cc -m32 -B/usr/lib32 ... I know it does because I've used it on my laptop a while ago, running FreeBSD/amd64. It's dead now so I can verify this works in all cases, but it seemed to solve this for me a couple of months ago. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Copying kernel and OS
On 2005-12-08 07:02, Jack Raats [EMAIL PROTECTED] wrote: Is it also possible to scp both directories to the slow machine? Maybe, but why do that? NFS is going to work better :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fails to boot after buildworld
On 2005-11-09 20:53, [EMAIL PROTECTED] wrote: Hey all, I don't know if this is a bug somewhere in the source but my system will not boot after I buildworld FreeBSD 6.0. I get the error: Can't work out which disk to boot from This error occurs right after the loader is booted and before the FreeBSD menu. System of course stalls here and says to press a key to reboot. I used the GENERIC kernel, empty loader.conf, my cvs tag = RELENG_6 and my make.conf has: CPUTYPE?=pentium4 CFLAGS= -O2 -mmmx -msse -msse2 -pipe -funroll-loops -ffast-math CXXFLAGS+= -fconserve-space COPTFLAGS= -O2 -pipe -funroll-loops -ffast-math Try without all those fancy optimizations. There's a very good comment in /usr/share/examples/etc/make.conf' which you may be interested in reading carefully: # CFLAGS controls the compiler settings used when compiling C code. # Note that optimization settings other than -O and -O2 are not recommended # or supported for compiling the world or the kernel - please revert any # nonstandard optimization settings to -O or -O2 before submitting bug # reports without patches to the developers. - Giorgos PS: Please, ignore the automatically forced 'footer' below. It's automatically added by the Exchange server I'm behind and has no relation whatsoever to non-work email I post. - This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, do not forward this email to any other person, delete this e-mail and destroy all copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorized and may be illegal. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.0 Released
6.0-RELEASE is not -CURRENT anymore, so I'm removing -current from the Cc: list. It's not really nice to have a multi-thread spread all over both -stable and -current AFAIK. On 2005-11-04 16:33, Renato Botelho [EMAIL PROTECTED] wrote: On 11/4/05, Scott Long [EMAIL PROTECTED] wrote: It is my great pleasure and privilege to announce the availability of FreeBSD 6.0-RELEASE. This release is the next step in delivering the high performance and enterprise features that have been under development in the FreeBSD 5.x series for that last several years. Some of the many changes since 5.4 include: I'm having some troubles with locale after upgrade to RELENG_6. one example, perl warning me about my locale: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL = en_US.ISO8859-1, LANG = en_US.ISO8859-1 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). Is this the Perl package from the 6.0-RELEASE CD-ROM or a Perl port installed before the upgrade some time? Regards, Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is rcorder working under /usr/local/etc/rc.d?
On 2005-10-15 22:12, Lefteris Tsintjelis [EMAIL PROTECTED] wrote: I am getting all these no provider and rcorder doesn't seem to work properly under /usr/local/etc/rc.d. Services seem to start alphabetically and not in the right order specified. The keywords REQUIRE, PROVIDE, BEFORE and KEYWORD seem to be ignored. Services like SERVERS, NETWORKING, LOGIN, etc, are all provided within /etc/rc.d. rcorder /usr/local/etc/rc.d/* rcorder: requirement `SERVERS' in file `squid.sh' has no providers. rcorder: requirement `NETWORKING' in file `squid.sh' has no providers. rcorder: requirement `DAEMON' in file `snmptrapd.sh' has no providers. [...] These look like stuff that is provided by /etc/rc.d/* scripts. Try including all the scripts in the rcorder command line: % flame:/home/keramida$ rcorder /usr/local/etc/rc.d/* /dev/null % rcorder: file `/usr/local/etc/rc.d/samba.sh' is before unknown provision `DAEMON' % rcorder: requirement `named' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `SERVERS' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `NETWORKING' in file `/usr/local/etc/rc.d/samba.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/perforce.sh.sample' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/mysql.sh' has no providers. % rcorder: requirement `ldconfig' in file `/usr/local/etc/rc.d/000.pkgtools.sh' has no providers. % flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /dev/null % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/newsyslog'. % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/syslogd'. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is rcorder working under /usr/local/etc/rc.d?
On 2005-10-16 00:41, Lefteris Tsintjelis [EMAIL PROTECTED] wrote: Giorgos Keramidas wrote: % flame:/home/keramida$ rcorder /etc/rc.d/* /usr/local/etc/rc.d/* /dev/null % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/newsyslog'. % rcorder: Circular dependency on provision `mountcritremote' in file `/etc/rc.d/syslogd'. Gia sou Giorgo kai pali, Hehehe, geia :) That certainly fixes just about all of the no providers but the start up rcorder problem remains. To be more specific, I specify for a service this: # REQUIRE: mysql This service however still fails to start after MySQL and keeps on starting right before it. Hmm, that's odd. Can I see the dependency lines of the two scripts and the output of rcorder? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: applying the vesa patch to stable for high console resolution
On 2005-06-13 22:06, Ted Mittelstaedt [EMAIL PROTECTED] wrote: http://people.freebsd.org/~delphij/vesa/patchset-highres.20050522 Has this patch beeen applied to CURRENT? So it will be in the next release of FreeBSD? Yes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: limit number of tcp connection for a GID
On 2005-06-05 19:56, Riccardo Giuntoli [EMAIL PROTECTED] wrote: Hi folks, Do you have any idea for limiting the number of tcp ESTABLISHED connections for a GID? ipfw can match connections per uid/gid and it also has limiting capabilities. When combined with dummynet, it can also enforce bandwidth limits. See the ipfw(8) manpage for details. I'm not sure if pf does this already. Even if it doesn't though, it may be possible to write a transparent proxy that limits the connections per uid/gid. The support for transparent proxies in pf is awesome :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On 2005-05-11 13:50, Gavin Atkinson [EMAIL PROTECTED] wrote: Ah, yes! Good thought. This could affect the width of the USERNAME column and push everything too far to the right. If this is the case, I'd probably vote for optionally limiting the length of the username column to, say, 8 columns at most. I would also vote for limiting it to 8 characters. Even with longer usernames, I suspect 8 characters will be enough to identify particular users (and if it's not there is always they UID view). That's an option too. I'm currently trying to get top to display something like this (80 columns are used for text, so use a slightly wider terminal to view this properly: ---+ last pid: 11090; load averages: 1.27, 1.26, 0.86up 0+01:11:11 03:07:43| 71 processes: 3 running, 68 sleeping | CPU states: 11.2% user, 0.0% nice, 77.1% system, 0.8% interrupt, 10.9% idle | Mem: 50M Active, 348M Inact, 70M Wired, 20M Cache, 60M Buf, 6340K Free | Swap: 5000M Total, 5000M Free | | PID USERNAME PRI NICE SIZERES STATETIME WCPU COMMAND/NTHR | 4738 root 1080 1360K 836K RUN 1:28 22.80% find/1 | 638 giorgos-80 13496K 4672K pcmwr1:33 1.03% mpg123/1 | 11062 giorgos960 2428K 1520K RUN 0:00 1.54% top/1 | ---+ This includes at least the following changes (some not visible): + The entire header line is limited to the window width too. + The USERNAME column is hard-limited to 8 characters. + The THR column is displayed as /1 after the COMMAND, like the prstat(1M) command of recent Solaris versions. + The CPU/WCPU columns occupy the same space and can be toggled with the 'C' keyboard command. + When UID numbers are displayed, hitting 'u' will read a UID instead of a username. + When the view is toggled between processes/threads, the NTHR part becomes the thread ID of the particular thread. Hopefully, I'll have these changes running on CURRENT before the weekend. If no strong objections are voiced for any of these changes, I'll test it on CURRENT for a while, then ask for approval of a commit to HEAD and merge it to 5-STABLE after it's been tested enough on CURRENT. - Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On 2005-05-12 13:49, Dominic Marks [EMAIL PROTECTED] wrote: On Thursday 12 May 2005 11:39, you wrote: That's an option too. I'm currently trying to get top to display something like this (80 columns are used for text, so use a slightly wider terminal to view this properly: ---+ last pid: 11090; load averages: 1.27, 1.26, 0.86up 0+01:11:11 03:07:43| 71 processes: 3 running, 68 sleeping | CPU states: 11.2% user, 0.0% nice, 77.1% system, 0.8% interrupt, 10.9% idle | Mem: 50M Active, 348M Inact, 70M Wired, 20M Cache, 60M Buf, 6340K Free | Swap: 5000M Total, 5000M Free | | PID USERNAME PRI NICE SIZERES STATETIME WCPU COMMAND/NTHR | 4738 root 1080 1360K 836K RUN 1:28 22.80% find/1 | 638 giorgos-80 13496K 4672K pcmwr1:33 1.03% mpg123/1 | 11062 giorgos960 2428K 1520K RUN 0:00 1.54% top/1 | ---+ If you don't mind I will share my thoughts on these changes. Thanks :) This includes at least the following changes (some not visible): + The entire header line is limited to the window width too. + The USERNAME column is hard-limited to 8 characters. This makes me a little uneasy. Its a typical idiom, at least at my Business, to have usernames which are of the form 'firstnamelastname', for this reason they can be quite long and often the first 5-8 characters will be frequently repeated, for example the following contrived names: rogermoore - rogermoo rogermoody - rogermoo charlottelane - charlott charlottedaniels - charlott [...] If this behaviour could be turned on and off, I'd be very happy. Hmmm, not a bad idea. You have a good point here. + When the view is toggled between processes/threads, the NTHR part becomes the thread ID of the particular thread. Okay, not really sure what this will look like to me but no need to explain I'll wait until they hit -CURRENT and see for myself. Instead of displaying a single named/7 line, which would mean that there is a named process with 7 threads, in thread mode you would see 7 lines with named/0, named/1, named/2, ... which would be the thread IDs of the distinct threads. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On 2005-05-12 09:33, Scot Hetzel [EMAIL PROTECTED] wrote: On 5/12/05, Tuomo Latto [EMAIL PROTECTED] wrote: Dominic Marks wrote: This includes at least the following changes (some not visible): + The entire header line is limited to the window width too. + The USERNAME column is hard-limited to 8 characters. ... If this behaviour could be turned on and off, I'd be very happy. How about making it a command line parameter? The field size, I mean. How about using the -w flag to increase the size? Similar to the way that ps uses it now (i.e. ps -axwww). Cool tip. Thanks :) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On 2005-05-12 09:43, Jonathan Noack [EMAIL PROTECTED] wrote: On 5/12/2005 8:12 AM, Giorgos Keramidas wrote: On 2005-05-12 13:49, Dominic Marks [EMAIL PROTECTED] wrote: + When the view is toggled between processes/threads, the NTHR part becomes the thread ID of the particular thread. Okay, not really sure what this will look like to me but no need to explain I'll wait until they hit -CURRENT and see for myself. Instead of displaying a single named/7 line, which would mean that there is a named process with 7 threads, in thread mode you would see 7 lines with named/0, named/1, named/2, ... which would be the thread IDs of the distinct threads. What happens if the command is long enough to overrun the screen? Is the thread information truncated and lost? I believe this was the argument for making a separate column for the thread info. By removing the THR column and merging CPU into WCPU we gain a lot of columns, so I'm hoping that it would be ok to trim the command name in favor of the thread count. Before actually having something in the form of a patchfile though it's hard to tell if it's going to be good or not. - Giorgos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The sendmail discussion...
On 2002-03-28 13:34, Nate Williams wrote: (my company demands that all software I write, including in my own free time, is copyright by them) You need to move to California, where this is against the law. Every California company I've worked for has made me ... ...which was signed voluntarily. They either make you, or it's voluntary. It can't be both :-) Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: MAKEDEV 4.4-STABLE still offering problems
Dimitry Andric [EMAIL PROTECTED] wrote: However, the proper solution is to follow the instructions from /etc/defaults/make.conf, which say: # If you experience any problems after setting this flag, please unset # it again before submitting a bug report or attempting to modify code. # It may be that certain types of software will become unstable after being # compiled with processor-specific (or higher - see below) optimization flags. # If in doubt, do not set CPUTYPE or CFLAGS to non-default values. So I'm now in the process of removing CPUTYPE from all FreeBSD boxes I manage, and rebuilding them. :) I did try putting some agressive optimizations to /etc/make.conf once. All kinds of weird problems started popping up, with the most annoying of them all an invalid checksup on all UDP and TCP packets my machine tried to send over dialup interfaces like ppp0 or tun0. Switching to a plain `-O -pipe' setting in make.conf made all of the problems go magically away. That was the last time I used optimizations in buildworld and buildkernel, as far as I remember :) Strange because in the Linux camp they are all madly optimizing, but since I hate unpredictability compared to a loss of speed, the choise is obvious for me thereafter. Just my $0.2 -giorgos PGP signature
Re: The FreeBSD core team needs your help
On Fri, 8 Jun 2001, Donn Miller wrote: Does ReiserFS work with FreeBSD? Nope. ReiserFS is very Linux-specific at the moment. -giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: problem with chflags
On Fri, 1 Jun 2001, Brooks Davis wrote: If we really need to support people who don't know what to do in single user mode, the correct thing is to add instructions to do: fsck -p mount -a after the reboot into single user mode. Yes, that would be marvellous. I know that I need to mount my filesystems after checking them, and I always do: # fsck -p # mount -u -o rw / # mount -a But these steps are not easy to guess, if one reads /usr/src/UPDATING. They are implied, but for someone who is booting in single user mode for his first time, they are also very hard to just come up with :-) -giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Limit on the number of disklabel entries?
On Sun, Jan 21, 2001 at 11:56:44PM +, Josef Karthauser wrote: On Sun, Jan 21, 2001 at 03:33:31PM -0700, Warner Losh wrote: In message [EMAIL PROTECTED] Matt Heckaman writes: : Brand new system, installed 3 days ago, 4.2-RELEASE. Creating the : partition on the newly sliced da1 via sysinstall put it on "e". 'e' is the first slice that sysinstall uses. Since you wanted the whole disk, it gave you the whole disk as 'e'. Nothing magical about it. 'c' being the whole disk *IS* magical. Does 'c' include the disklabel itself, and the boot blocks? Actually in /usr/src/sys/sys/disklabel.h you can see three constants defined. #define LABEL_PART 2/* partition containing label */ #define RAW_PART2/* partition containing whole disk */ #define SWAP_PART 1/* partition normally containing swap */ The code uses LABEL_PART when it wants to access the partition containing the entire disk, together with the disklabel, but as you can see, this is the same as RAW_PART which is defined to `2'. Now, lemme guess... 'a', 'b', 'c'.. '0', '1', '2'.. SWAP_PART is '1' and default swap partition is 'b'. RAW_PART is '2' and the default `entire disk' partition is 'c'. HAHHAHHH. I'm beginning to love this source thing! Absolutely amazing, how clearly ideas and things can jump out on you, if you read a few lines of code :-) Cheers, Giorgos. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: howto: cvs for minimum space freebsd server (Re: Upgrade problem)
On Sun, Nov 26, 2000 at 02:08:22PM +1300, kit wrote: On Sat, Nov 25, 2000 at 06:19:04PM +1100, Jonathan Michaels wrote: i currently run (and have done so fro, er since v2.0.5-release) -release versions. now that the cost of freebsd release cds has gone through the roof for me it might be cheaper fo follow -stable. USD prices are painful in this part of the world :( In my part of the world, too. However, nothing stops me from downloading the 4.2-RELEASE .iso image and burning it on a cdrom disk of my own. This seems to cost a lot less. - giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: REMINDER: 4.2 code freeze starts tomorrow!
On Thu, Nov 02, 2000 at 12:31:19PM +0200, Panagiotis Astithas wrote: In Greece, we also switched from 4am to 3am. I am not sure how this works in Spring though. Off the top of my head, I think that in Spring it's 03:00 - 04:00 am. -- Giorgos Keramidas, keramida @ ceid . upatras . gr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: big trouble - sendmail in todays stable NOT reading sendmail.cw
On Wed, Nov 01, 2000 at 12:25:00PM +1100, Gregory Bond wrote: these domains _really_ are written to /etc/mail/sendmail.cw and they have always worked... Read the HEADS UP in stable a few weeks ago. "sendmail.cw" is now spelled "local-host-names" Of course you can always use the macros of sendmailm.mc to change that, as in: define(`confCW_FILE', `-o /etc/mail/sendmail.cw')dnl But /etc/mail/local-host-names or even /etc/mail/locals are named that new users will find more meaningful. -- Giorgos Keramidas, keramida @ ceid . upatras . gr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Reminder: Just 7 days till 4.2 code freeze!
On Wed, Oct 25, 2000 at 07:20:42PM -0700, Dima Dorfman wrote: On Wed, Oct 25, 2000 at 05:58:38PM -0700, Kris Kennaway wrote: Grr. Brian, how many bug reports does it take for you to do something about this? This should either be fixed or entirely backed out by 4.2-RELEASE. IIRC, the fix was to add a passwd_format capability to login.conf. If that's the case, wouldn't a src/UPDATING entry suffice? If this is not the case, I apologize for the wasted bandwidth. Ahem. I did add this entry to my /etc/login.conf and ran cap_mkdb on my login.conf, then logged off all my terminals and logged in again. It did not solve the 'cannot set password cipher' problem though. As this machine is the name server of our local network, I cannot reboot the machine now, to see if this will fix the problem after the login.conf/cap_mkdb changes, but later this afternoon I will try this too. - giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: All the x11-wm ports b0rken in 4.1.1-STABLE?
On Wed, Oct 25, 2000 at 05:13:12PM -0400, Chris BeHanna wrote: If you had these lines in your supfile: *default release=cvs tag=RELENG_4 *default delete use-rel-suffix then all of that should have been handled already. You'll also need ports-all=. Correct me someone if I'm wrong here, but doesn't ports-all=. render the tag=RELENG_4 meaningless? I mean, why not tag=. in the first place? -- Giorgos Keramidas, keramida @ ceid . upatras . gr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
