FreeBSD Quarterly Status Report - Fourth Quarter 2021
FreeBSD Quarterly Status Report 4th Quarter 2021 This report covers FreeBSD related projects for the period between October and December. It is the fourth of four planned reports for 2021, and contains 19 entries. Highlights include faster boot times, more LLDB work, a base OpenSSH update, and more wireless development. Yours, Pau Amma, Daniel Ebdrup, John-Mark Gurney, and Joe Mingrone ━━━ Table of Contents • FreeBSD Team Reports □ FreeBSD Foundation □ Ports Collection □ Documentation Engineering Team □ FreeBSD Website Revamp - WebApps working group • Projects □ Enable ASLR by default for 64-bit executables □ Boot Performance Improvements □ LLDB Debugger Improvements □ NXP LS1028A/1027A SoC support □ sched_getcpu(2), membarrier(2), and rseq(2) syscalls □ Base System OpenSSH Update □ VDSO on amd64 • Kernel □ The AVX bug on amd64 □ ENA FreeBSD Driver Update □ Intel Wireless driver support □ Kernel Crypto changes to support WireGuard • Ports □ KDE on FreeBSD □ FreeBSD Office Team • Third-Party Projects □ helloSystem □ Containers & FreeBSD: Pot, Potluck & Potman ━━━ FreeBSD Team Reports Entries from the various official and semi-official teams, as found in the Administration Page. FreeBSD Foundation Links: FreeBSD Foundation URL: https://www.FreeBSDFoundation.org Technology Roadmap URL: https://FreeBSDFoundation.org/blog/technology-roadmap/ Donate URL: https://www.FreeBSDFoundation.org/donate/ Foundation Partnership Program URL: https://www.FreeBSDFoundation.org/ FreeBSD-foundation-partnership-program FreeBSD Journal URL: https://www.FreeBSDFoundation.org/journal/ Foundation News and Events URL: https://www.FreeBSDFoundation.org/ news-and-events/ Contact: Deb Goodkin The FreeBSD Foundation is a 501(c)(3) non-profit organization dedicated to supporting and promoting the FreeBSD Project and community worldwide. Donations from individuals and corporations are used to fund and manage software development projects, conferences, and developer summits. We also provide travel grants to FreeBSD contributors, purchase and support hardware to improve and maintain FreeBSD infrastructure, and provide resources to improve security, quality assurance, and release engineering efforts. We publish marketing material to promote, educate, and advocate for the FreeBSD Project, facilitate collaboration between commercial vendors and FreeBSD developers, and finally, represent the FreeBSD Project in executing contracts, license agreements, and other legal arrangements that require a recognized legal entity. Here are some highlights of what we did to help FreeBSD last quarter: Fundraising Efforts We did it! We met our 2021 fundraising goal by raising $1,281,437!! On behalf of the Foundation, I want to thank you for your financial support last year, that will help us continue and increase our support for FreeBSD in 2022. In addition, folks are already sending us their 2022 contributions, which is incredibly heartwarming! We’ll start updating the fundraising meter for 2022 by the end of January. In this Quarterly Status report you’ll read about many of the areas we funded in Q4 to improve FreeBSD and advocate for the Project (the two main areas we spend money on). Check out reports on the externally funded projects like LLDB support, Raid-Z Expansion, WireGuard, and wifi, as well as, internally supported work like improved security, tier-1 architecture support, and providing online opportunities to connect and educate the community. If you want to help us continue our efforts, please consider making a donation towards our 2022 fundraising campaign! https://www.FreeBSDFoundation.org/donate/. We also have a Partnership Program for larger commercial donors. You can read about it at https://www.FreeBSDFoundation.org/ FreeBSD-foundation-partnership-program/. OS Improvements During the fourth quarter, Foundation staff and grant recipients committed 472 src tree changes, 98 ports tree changes, and 11 doc tree changes. This represents 41%, 41%, and 13% of src, ports, and doc commits identifying a sponsor. You can read about Foundation-sponsored projects in individual quarterly report entries: • The AVX bug on amd64 • Crypto changes for WireGurard • Intel Wireless driver support • LLDB Debugger Improvements • Base System OpenSSH Update • sched_getcpu(2), membarrier(2), and rseq(2) syscalls • VDSO on amd64 Here is a small sample of other base system improvements from Foundation developers this quarter that do not have separate report entries. kern.proc.pathname canonical hard link Some programs adjust their behavior depending on which name was used for execution. For these programs, it is often important to have a consistent name
Re: pkg: Cannot open /dev/null:No such file or directory
Thank you! I only added the mount line, but it seemed to work. On 2019-06-11 14:52, Johannes Lundberg wrote: > Hi > > This is probably overkill but I've attached a diff that show my patches > to image.sh. It's just a hack so far to make it do what I want and not > meant as general purpose. Use the changes you need for your application. > > Changes (only meant to work for building usb images on amd64 and i386) > > - mount devfs so pkg will work properly > - add "install packages from official repo" option so you won't have to > build your own packages for each jail > - downloaded packages from official repo is cached locally to avoid > excessive downloads > - hack for i386 so packages are installed properly > - increase swap space to allow for kernel core dumps (for usb image) > - execute post-install script "overlay.sh" in the jail if provided in > the overlay folder > > Bapt: Maybe you'll find some of these changes useful? :) > > /Johannes > > On 6/11/19 8:52 AM, jbwli...@hilltopgroup.com wrote: >> I'm having the same issue with poudriere image; could you please let >> me know what you did to fix it? I'm assuming the image.sh you're >> referring to is /usr/local/share/poudriere/image.sh, but I'm not sure >> where the change would need to be made. >> >> Thanks in advance, >> Joseph >> >> >> On 2019-06-04 13:02, Johannes Lundberg wrote: >>> On 6/3/19 10:44 PM, Baptiste Daroussin wrote: >>>> On Tue, Jun 04, 2019 at 07:32:16AM +0200, O. Hartmann wrote: >>>>> Hello List, >>>>> >>>>> lately I ran into a serious problem installing packages in a nanoBSD >>>>> environment, in which the package repository server is "remotely" >>>>> on site. The >>>>> issue as documented below occurs on both 12-STABLE r348529 and >>>>> CURRENT r348600 >>>>> and must have been introduced shortly, since the last known good >>>>> installation >>>>> with the environment of ours was on 21st May 2019. >>>>> >>>>> As far as I know,, the package installation is performed via >>>>> "chroot'ed" >>>>> environment and somehow /dev/null is out of a sudden not accessible >>>>> anymore >>>>> while pkg tries to delegate some output to /dev/null. >>>>> >>>>> What happened here? >>>>> >>>>> Kind regards and thanks in advance, >>>>> >>>>> oh >>>>> >>>>> [...] >>>>> All repositories are up to date. >>>>> The following 10 package(s) will be affected (of 0 checked): >>>>> >>>>> New packages to be INSTALLED: >>>>> python3: 3_3 [zeit4] >>>>> sudo: 1.8.27_1 [zeit4] >>>>> devcpu-data: 1.22 [zeit4] >>>>> python36: 3.6.8_2 [zeit4] >>>>> readline: 8.0.0 [zeit4] >>>>> indexinfo: 0.3.1 [zeit4] >>>>> libffi: 3.2.1_3 [zeit4] >>>>> gettext-runtime: 0.19.8.1_2 [zeit4] >>>>> openldap-sasl-client: 2.4.47 [zeit4] >>>>> cyrus-sasl: 2.1.27 [zeit4] >>>>> >>>>> Number of packages to be installed: 10 >>>>> >>>> What is new is that pkg is using /dev/null as input when running >>>> script? this is >>>> new since pkg 1.11 . Somehow this does not seems to be avaalaible in >>>> your >>>> environement. >>> Hi >>> >>> Same things applies to poudriere-image. I had to add a mount devfs >>> command to the image.sh script. >>> >>>> Best regards, >>>> Bapt >>> ___ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Lenovo BIOS boot fix
Warren Block wbl...@wonkity.com writes: Please, whoever has one of these systems, find a contact address for Lenovo. It should be on every one of these messages, and we should be encouraging every affected user to contact Lenovo support. I can post it in the forums, also. gethuman.com lists customerfeedb...@lenovo.com as a contact email. http://www.headquartersinfo.com/lenovo-headquarters-information/ One this page is a list of the Lenovo Headquarters Executive Team. Most of them have Twitter accounts. Some public tweets to them might have a strong impact. If you're providing feedback and you don't agree with Lenovo's practice of preventing you from installing your own wireless card, please mention that as well. There is also a petition: https://www.change.org/p/lenovo-release-an-unencumbered-version-of-the-bios. Joseph signature.asc Description: PGP signature
Re: CD Access in 9.x and -CURRENT
On 12/30/2011 08:13, Tijl Coosemans wrote: On Thursday 29 December 2011 12:52:39 Claude Buisson wrote: On 12/29/2011 07:41, Garrett Cooper wrote: On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinsonj...@freebsd.org wrote: I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the issue of cdda:// access. I can confirm this issues, but don't know enough about driver access to fix this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and mplayer and audactiy also display issues running as non-root. Under 9.0-RC3 r228843, I get these errors on boot with no disc present in /dev/cd0 at all. (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass1:ahcich2:0:0:0): CAM status: ATA Status Error (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 These ports are fairly popular, but the problems may not lie exclusively with their assumptions about FreeBSD. I am running 10.0 on another machine specifically to test changes under src/sys/cam. I am worried that with the actual 9.0-RELEASE on the horizon, users will find show stopping problems using their disc drives. Try having users merge r228808 and r228847. If that works, then I would press re@ produce another RC that fixes this. Thanks, -Garrett PS This is coming from a user that was annoyed by this gap with the ATA_CAM code. As the submitter of ports/162190, I would firstly ask: Is the problem corrected by r228808 and r228847 in 10.0-CURRENT ? If not merging to 9.0 is useless. If yes I could test. There are 3 methods to access audio CDs. - if your drive is connected to your sound card you can use the drive's built-in audio support (if present). (used by cdcontrol) - read raw audio data via the CAM layer. (used by cdparanoia) - read raw audio data via the cd(4) driver. (used by vlc, libcdio?) The first two should work. The last one has now been fixed in CURRENT, but programs using that method also seem to use CDRIOCSETBLOCKSIZE ioctl that cd doesn't implement. The driver already knows the correct block size though, so it seems safe to ignore the error. With the attached patch vlc works for me. You sir, are a godsend. Tested this on 10.0-CURRENT and it worked. Now to get some form of this into VLC 1.2.0. It's likely too late to get the MFC needed, so possibly errata. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: CD Access in 9.x and -CURRENT
On 12/29/2011 01:41, Garrett Cooper wrote: On Wed, Dec 28, 2011 at 9:56 PM, Joseph S. Atkinsonj...@freebsd.org wrote: I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the issue of cdda:// access. I can confirm this issues, but don't know enough about driver access to fix this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and mplayer and audactiy also display issues running as non-root. Under 9.0-RC3 r228843, I get these errors on boot with no disc present in /dev/cd0 at all. (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass1:ahcich2:0:0:0): CAM status: ATA Status Error (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 These ports are fairly popular, but the problems may not lie exclusively with their assumptions about FreeBSD. I am running 10.0 on another machine specifically to test changes under src/sys/cam. I am worried that with the actual 9.0-RELEASE on the horizon, users will find show stopping problems using their disc drives. Try having users merge r228808 and r228847. If that works, then I would press re@ produce another RC that fixes this. Thanks, -Garrett My desktop is 10.0-CURRENT r228926. I am running 9.0-RC3 on my laptop. I mention RC3 because the problem there is about to become a RELEASE problem. Neither machine can read CDs. I also cannot eject CDs on the laptop after the failed attempts to read it because it doesn't seem to stop trying to read it. PS This is coming from a user that was annoyed by this gap with the ATA_CAM code. If pre-RELEASE is any indication, this is going to flood GNATS. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
CD Access in 9.x and -CURRENT
I am the maintainer of VLC, I have an outstanding PR (ports/162190) on the issue of cdda:// access. I can confirm this issues, but don't know enough about driver access to fix this myself. Doug Barton reports that cdcontrol(1) doesn't work for him, and mplayer and audactiy also display issues running as non-root. Under 9.0-RC3 r228843, I get these errors on boot with no disc present in /dev/cd0 at all. (pass1:ahcich2:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 01 00 (pass1:ahcich2:0:0:0): CAM status: ATA Status Error (pass1:ahcich2:0:0:0): ATA status: 51 (DRDY SERV ERR), error: 04 (ABRT ) (pass1:ahcich2:0:0:0): RES: 51 04 01 14 eb 40 00 00 00 01 00 These ports are fairly popular, but the problems may not lie exclusively with their assumptions about FreeBSD. I am running 10.0 on another machine specifically to test changes under src/sys/cam. I am worried that with the actual 9.0-RELEASE on the horizon, users will find show stopping problems using their disc drives. -- Joseph S. Atkinson Paellax Technology Group http://www.paellax.com/ -- Sent from my FreeBSD/GNOME laptop 'pazuzu'. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [review request] New config.5 manual page
placed on the value should be similar/identical. Any differences in the
way the value is treated should be well documented (or fixed). As we
move into larger memory systems our current limitations need to be either
removed or increased.
Yes, you are right. It doesn't make sense to restrict the value of maxusers
at configuration time, when the kernel can be configured to use larger values
at boot time.
I think it makes sense to remove the maximum bound on a statically
configured 'maxusers' value. The lower bound could be retained
as a sanity check.
Something like this?
Index: mkoptions.c
===
RCS file: /cvs/FreeBSD/src/usr.sbin/config/mkoptions.c,v
retrieving revision 1.30
diff -u -r1.30 mkoptions.c
--- mkoptions.c 15 Feb 2003 02:26:13 - 1.30
+++ mkoptions.c 5 Jul 2003 04:42:44 -
@@ -52,11 +52,7 @@
#include config.h
#include y.tab.h
-static struct users {
- int u_default;
- int u_min;
- int u_max;
-} users= { 8, 2, 512 };
+#define U_MIN 2
static char *lower(char *);
static void read_options(void);
@@ -79,13 +75,10 @@
SLIST_INSERT_HEAD(opt, op, op_next);
}
- if (maxusers == 0) {
- /* printf(maxusers not specified; will auto-size\n); */
- } else if (maxusers users.u_min) {
- printf(minimum of %d maxusers assumed\n, users.u_min);
- maxusers = users.u_min;
- } else if (maxusers users.u_max)
- printf(warning: maxusers %d (%d)\n, users.u_max, maxusers);
+ if (maxusers maxusers U_MIN) {
+ printf(minimum of %d maxusers assumed\n, U_MIN);
+ maxusers = U_MIN;
+ }
/* Fake MAXUSERS as an option. */
op = (struct opt *)malloc(sizeof(*op));
--
Joseph Koshy [EMAIL PROTECTED]
Developer, The FreeBSD Project http://people.freebsd.org/~jkoshy/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
[review request] New config.5 manual page
The attached manual page documents the syntax for the kernel configuration files as understood by the config(8) program in 5-CURRENT. This syntax has diverged from the syntax understood by the original 4.4BSD config(8) program, and it is perhaps time for a new manual page. This manual entry is to be added to section 5 (file formats) of the FreeBSD manual. Could you please review and send in your comments? Joseph Koshy [EMAIL PROTECTED] Developer, The FreeBSD Project http://people.freebsd.org/~jkoshy/ .\ Copyright (c) 2003 Joseph Koshy .\ .\ Redistribution and use in source and binary forms, with or without .\ modification, are permitted provided that the following conditions .\ are met: .\ 1. Redistributions of source code must retain the above copyright .\notice, this list of conditions and the following disclaimer. .\ 2. Redistributions in binary form must reproduce the above copyright .\notice, this list of conditions and the following disclaimer in the .\documentation and/or other materials provided with the distribution. .\ .\ THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND .\ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE .\ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE .\ ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\ SUCH DAMAGE. .\ .\ $FreeBSD: src/share/man/man5/quota.user.5,v 1.3 2002/12/12 17:25:57 ru Exp $ .\ .Dd June 03, 2003 .Dt CONFIG 5 .Os .Sh NAME .Nm config .Nd kernel configuration file format .Sh DESCRIPTION A kernel configuration file specifies the configuration of a .Fx kernel. It is processed by .Xr config 8 to create a build environment where a kernel may be built using .Xr make 1 . .Sh LEXICAL STRUCTURE A kernel configuration file comprises a sequence of specification directives. .Pp A specification directive starts with a keyword at the beginning of the line and is followed by additional parameters. .Pp A specification directive may be terminated by a semicolon .Ql \; or by a newline. Long input lines may be broken into shorter lines by starting the second and subsequent lines with a white space character. .Pp Case is significant, .Ql machine and .Ql MACHINE are different tokens. .Pp A double quote character .Ql \\*q starts a quoted string. All characters up to the next quote character form the value of the quoted string. A .Ql \\*q character may be inserted into a quoted string by using the sequence .Ql \e\*q . .Pp Number are specified using .Li C Ns No -style syntax. .Pp A .Ql # character starts a comment; all characters from the .Ql # character till end of line are ignored. .Pp Whitespace between tokens is ignored, except inside quoted strings. Whitespace following a comment line is ignored. .Sh CONFIGURATION DIRECTIVES Kernel configuration directives may appear in any order in a kernel configuration file. Directives are processed in order of appearance with subsequent directive lines overriding the effect of prior ones. .Pp The list of keywords and their meanings are as follows: .Bl -tag -width makeoptions .\ CPU .It Cm cpu Ar cputype Specify the CPU this kernel will run on. There can be more than one .Li cpu directives in a configuration file. The allowed list of cpu names is architecture specific and is defined in the file .Pa sys/conf/options. Ns Ar arch . .\ DEVICE .It Cm device Ar name Op count Configures device .Ar name for inclusion into the kernel image. If .Ar count is specified, the device is configured for .Ar count instances. The list of valid device names is architecture specific and are defined in the files .Pa sys/conf/files and .Pa sys/conf/files. Ns Ar arch . .\ ENV .It Cm env Ar filename Specifies a filename containing a kernel environment definition. The kernel normally uses an environment prepared for it at boot time by .Xr loader 8 . This directive makes the kernel ignore the boot environment and use the compiled in environment instead. .Pp This directive is useful for setting kernel tunables in embedded environments that do not start from .Xr loader 8 . .\ HINTS .It Cm hints Ar filename Specifies a file to load a static device configuration specification from. From .Fx 5.0 onwards, the kernel picks up the device configuration at boot time (see .Xr device.hints 5 Ns ). This directive configures the kernel to use the static device configuration listed in .Ar filename. .Ar filename
RE: Server locking hard -- A LOT!!!
Trying turning polling on in the kernel on the ethernet NIC you are using. SOunds like an interrupt issue. Set to 1000 to 3000 depending on how responsive you need it to be joseph On Wed, 2003-02-05 at 13:22, Muhannad Asfour wrote: On Wed, 2003-02-05 at 08:20, Robert Covell wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Muhannad Asfour Sent: Tuesday, February 04, 2003 9:25 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Server locking hard -- A LOT!!! Hello. I've recently faced a rather odd issue that I've never seen before. I bought a new server (specs below), and I loaded it up with FreeBSD 5.0-RELEASE (I know, I know, not for a production environment, but this is a personal server). Now, whenever I get about 30 simultaneous connections, the box just locks hard. I tested all the hardware components (CPU, Memory, HD, NIC, etc.) and even bought new ones just to make sure and all end up with the same result. I can never keep a decent uptime (never went past 2 days so far). As soon as I get a mediocre http load (30 simul. connections), the box just locks hard. I built a debug kernel, I tried everything imaginable, and I have not found a solution whatsoever. Everyone seems to be stumped by this. I tried FreeBSD 4.7-RELEASE, 4.7-STABLE, 5.0-RELEASE and 5.0-CURRENT on this box. All give me the same result. I checked everywhere for relevant logs to explain what is occuring, but had no such luck. This is truly the million dollar question for me right now, because I have no idea why it would lock under such a petty load. I'm not sure what to do to fix this issue, I've tried many different areas for support and haven't come up with anything as I stated earlier. I'm not overclocking or anything if that's what you're wondering. If anyone could assist me in any way shape or form to get this working, I would appreciate it very very much. Also, if you e-mail back, I'm not subscribed to the lists, so could you please CC it to me. In the past 4 hours, it has locked hard about 3 times because of a 28-34 connection load. Machine Specs: Single Pentium IV 2.4 GHz processor ASUS P4S533 motherboard 512MB DDR333 RAM (will be 1GB next week) 120GB Maxtor 7200rpm (ATA133) HDD 40GB Maxtor 7200 rpm (ATA66) HDD Floppy Disk Drive ATI Rage 128 (32 meg) AGP 4x graphics adapter 52x LG CD-ROM drive 3Com 3C905C-TX NIC Currently running FreeBSD 5.0-CURRENT as of Sunday Feb. 2, 13:02:05 EST 2003. Thank you very much To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message I have seen things like this that are not software related at all but due to a faulty power supply. Did you replace that when you went out and bought new hardware? You might want to try and take off your CD-ROM and or the secondary HD. This will cut back on your power usage and might be a good test. If it still does it, get a new power supply that has enough juice. Sincerely, Robert T. Covell President / Owner Rolet Internet Services, LLC Web: www.rolet.com Email: [EMAIL PROTECTED] Phone: 816.471.1095 Fax: 816.471.3447 24x7: 816.210.7145 Well, I took off the CD-ROM drive, so now it's just the two HDs and a floppy drive. We'll see if it was a power supply issue after all. Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: problem with X
Try a make build world and see if that version of libc_r works. It should fix the problem. joseph On Mon, 2003-01-27 at 13:07, Alexander Pohoyda wrote: Charlie ROOT [EMAIL PROTECTED] writes: root, nor a regular user. Is this a font path problem? No, it is not. /usr/libexec/ld-elf.so.1: /usr/lib/libc_r.so.5: Undefined symbol __thr_jtable This is a problem. Version numbers are OK, though. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: first snag with 5.0 - XFree86 4 (fwd)
Recompile and install the with X*4-Server from /usr/ports/x11-servers. Your X server was built on a RC kernel base not the RELEASE the /dev/io mappings are slightly different. The following is the offending line in your snippet Build Operating System: FreeBSD 5.0-RC i386 [ELF] It should say Build Operating System: FreeBSD 5.0-RELEASE i386 [ELF] It will then work and make sure you do a make buildworld if you upgraded to make sure all your libs are also RELEASE not RC :)oseph On Tue, 2003-01-21 at 10:41, fingers wrote: hi it's been suggested that i send this to current@. Please let me know what info you'd like to carry on debugging this. Regards --Rob -- Forwarded message -- Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST) From: fingers [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: first snag with 5.0 - XFree86 4 howdie built X 4 from source or using package I'm getting: snip XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-RC i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Jan 21 11:15:10 2003 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 Fatal server error: xf86EnableIO: Failed to open /dev/io for extended I/O /snip when trying something like XFree86 -config. I trolled xfree86.org, found 1 hit but don't see any response to it. fresh install of 5.0-RELEASE using Riva 128. Was previously working on 5.0-CURRENT (build of about 2 weeks ago). /dev/io seems to exist. wrapper is installed. xf86cfg gives same error. any ideas? pnpinfo gives me can't get i/o privelege which doesn't seem right. have tried 'hint.acpi.0.disabled=1' with same results. I'd think it was XFree86 specific initially if it wasn't for the pnpinfo error. any suggestions appreciated. Regards --Rob To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Simple way to build boot disks?
Hi Marc...:) Just build your kernel and do a make release... just takes a little time then run the script /usr/src/release/i386/mkisoimages.sh --- READ the info about this in the shell script so you build what you want and you can even set up drives to be mounted ... YOU can build a bootable CD with your custom kernel... Then burn this iso image file to a CD and it will boot your kernel... everytime... joseph On Wed, 2003-01-22 at 12:36, Marc G. Fournier wrote: G'day ... I'm having a bugger of a time getting my laptop with a third-party ethernet adapter installed with 5.0, since it won't properly configure the adapter ... what I'd like to do is build a custom boot kernel, that gets rid of everything but what I require for that laptop, so that the onboard doesn't conflict with the 3rd party one ... all I can find so far on how to do this is to go through the whole 'make release' procedure ... is there an easier way of doing this that I'm not finding? thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: make release.9 fails ... ?
Hi Marc, It Should be dhclient-script.sh (a bug in the release builder?) then it works... :) Joseph On Wed, 2003-01-22 at 19:06, Marc G. Fournier wrote: Evening ... I found the release man page this evening, after more searching, and understand from it that a simple: cd /usr/src make buildworld cd release make floppies Should give me what I need ... But, when I try, the release.9 stage gives: atelier# make release.9 rm -rf /R/stage/mfsfd mkdir /R/stage/mfsfd cd /R/stage/mfsfd mkdir -p etc/defaults dev mnt stand/etc/defaults stand/help ( cd /R/stage/mfsfd for dir in bin sbin ; do ln -sf /stand $dir; done ) cp /R/stage/trees/base/sbin/dhclient-script /R/stage/mfsfd/stand cp: /R/stage/trees/base/sbin/dhclient-script: No such file or directory *** Error code 1 Known bug, or is there another step that I need to run first? Thanks ... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: aout support not working on todays -current
Hi Bob, Go into your kernel of choice and build it with the following: options COMPAT_AOUT now to enable AOUT binaries from the kernel loader. Make and Install and reboot the about new kerenl and aout will now work for you. :) joseph AOUT binaries... elf is the all around executable format for most loadable binaries.. On Tue, 2003-01-21 at 08:36, Bob Willcox wrote: I cvsup'd and built and installed a new -current system and kernel this morning and immediately noticed that my setiathome processes no longer ran. It appears that aout support is no longer working in -current. Note that I do have the COMPAT_AOUT option set in my kernel config file (it is the same config file that I used to build with about a week ago and that kernel runs aout files just fine). Anybody have any clues as to what happened? Thanks, Bob To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
NVida Ideas may help.
Hi Becuase of the memory access model with debuging on I found that a interrupt stack overflow in the kernel seems to occur from the interaction with interrupts and the memory on the nVida card. I have not nailed it down yet to which interrupts, but without debugging it reduces it an thus the freezing of the box. But in 3D mode the card is doing alot of the work and is notifing the X system and the kernel through interupts. Seems this overwrites the kernel and cause the Frozen deseret effect, without the desert. Maybe we need to have a kernel parameter for the agp based cards for increasing the interrupt stack size or the like. I watched it on one of our hardware developement PC's I have with a hardware debug card in it and shows that the cards blows up the kernel from video memory DMA transfer interrupts to/from X. regards, Please check what happens on IRQ 11 on PCI2 (on my Intel based debug machines) Joseph Altea, CEO ImerXion,LLC [EMAIL PROTECTED] On Wed, 2002-12-25 at 15:57, David Holm wrote: On Thursday 26 December 2002 00:51, Cliff L. Biffle wrote: I've managed to reproduce a very similar situation using RC1. Does your kernel have various debugging features in place? If so...try turning them /off/. I kid you not. On the RC1 box here the nVidia drivers were very unstable doing 3D until the kernel was recompiled without debugging. (Chris, the owner of the machine, wanted to do it for 'performance' reasons -- getting the graphics working was an unexpected boon.) I can get you the kernel config, or make it available to the list if anyone's interested in this fleeting heisenbug. -Cliff L. Biffle Yes, I've turned off all the debugging stuff. I've also removed Load dri from XF86Config etc. Please post your kernel conf, maybe I can see where they differ (if they do). //David Holm To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: The great perl script rewite - progress report
On Wed, 31 Jul 2002, Mark Murray wrote: # /usr/sbin/adduser Mike Makonnen [EMAIL PROTECTED] - redo - * # /usr/sbin/rmuser Mike Makonnen [EMAIL PROTECTED] - redo - * There are several PRs out on these that Mike might want to look at. bin/4357 bin/33881 (bin/24953, misc/40802) bin/7324 bin/16480 bin/22860 bin/24742 docs/35732 (issue w/ adduser(8) man page), i386/38481 (small typo) -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Building php mod and cgi
Is their a way to build the port mod_php4 as the module version for apache and the cgi for command line options. I currently have mod_php+apache13+mysql+gd working perfect but I now have the need to run php from the command prompt with mysql gd. What is the best way to go about this. thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Why isn't PAM_smb available for FreeBSD?
On Fri, 15 Feb 2002, Hiten Pandya wrote: # hi all, # # I was wondering, after seeing that Linux has pam_smb, why can't # FreeBSD have it too. I can get the pam_smb compiling under FreeBSD, # from http://www.samba.org, so I was wondering why it isn't in our # CVS tree. This probably belongs to -questions more than -current. At any rate, we do have one in the ports collection: security/pam_smb -Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ~/.login_conf disabling exact reasons wanted
On Sat, Sep 22, 2001 at 03:17:52PM +0400, Andrey A. Chernov wrote: Only me class can be defined in ~/.login_conf, anything else ignored there. And me class picked up only when permissions are set to user mode, at the end of setusercontext(). And copyright and welcome are not overwriteable from me class in any case. I was able to overwrite the settings for the `default' class, which happens to be my login class, and was able to get master.passwd to print... This was 4.x though, not CURRENT, so maybe this is something that wasn't affected in CURRENT, and that's what you're referring to, or something. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
On Mon, Aug 27, 2001 at 09:34:06AM -0700, John Baldwin wrote: Just to get this out in the public: I for one think 5.x has enough changes in it and would like for KSE to be postponed to 6.0-current and 6.0-release. I I definitely agree about this, 5.x is going to be enough of a major change as it is, and confusing _everything_ with even more big changes can't do any good in the short term, and would probably make KSE (and other things) a big hassle to the point of where they wouldn't be of any use until 6.x anyway. But that's just my opinion, and I'm sure I'll get smacked for it. /joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Headsup! KSE Nay-sayers speak up!
On Tue, Aug 28, 2001 at 09:55:13AM -0700, Julian Elischer wrote: Joseph Mallett wrote: On Mon, Aug 27, 2001 at 09:34:06AM -0700, John Baldwin wrote: Just to get this out in the public: I for one think 5.x has enough changes in it and would like for KSE to be postponed to 6.0-current and 6.0-release. I I definitely agree about this, 5.x is going to be enough of a major change as it is, and confusing _everything_ with even more big changes can't do any good in the short term, and would probably make KSE (and other things) a big hassle to the point of where they wouldn't be of any use until 6.x anyway. But that's just my opinion, and I'm sure I'll get smacked for it. /joseph *smack* Note that I wasn't really posting this comment this late in the thread, but my MTA decided to queue it for an obscenely long time. Sorry. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: bash in /usr/local/bin?
On Mon, Aug 13, 2001 at 07:23:26PM -0500, Jim Bryant wrote: DOD/DFAS, as well as DOD/DISA. I find it amazing that the CIA has a more lax policy than DFAS and DISA. The only person I've ever talked to from the CIA was in charge of network security to some degree, and according to him they can't even use FreeBSD, OpenBSD, or NetBSD internally. Everything must come from a central vendor and be supported by a real company, not by mailing lists. I'd call that less lax. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Tail-call reference (was: CPUTYPE warning)
tl == Terry Lambert wrote: tl FWIW: tail-call optimization is when I have a function tl that, as it's last thing (perhaps after reordering by tl the compiler, as well) calls another function, such tl that the return value of the other function is its tl return value. See also: Debunking the ``Expensive Procedure Call'' Myth or, Procedure Call Implementations Considered Harmful or, LAMDBA: The Ultimate GOTO By Guy Lewis Steele, Jr. AI memo 443, October 1977, 23 pages ftp://publications.ai.mit.edu/ai-publications/0-499/AIM-443.ps Regards, Koshy [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: convert libgmp to a port?
On Sun, 17 Jun 2001, Giorgos Keramidas wrote: If we do need some of the functionality of libgmp in the base-system, then we really should import some newer version of libgmp, instead of trying to make our own new library. I dont really like reinventing wheels :) Unless you are the one charged with doing the work, you shouldn't complain about the circumstances of the job. If someone wants to implement something which already exists with a good reason for doing so, let them. It can't hurt. Honestly, the odds that you would end up doing this, are NULL. Giving concise reasons as to why it doesn't need replaced would be nice, rather than why not bring in more vendor code. -- [ Joseph Mallett[EMAIL PROTECTED] ] [ http://srcsys.org ] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ FreeBSD, NetBSD, xMach User; (Obj)C(++) Coder ] [ http://xMach.org ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Date for a working -current?
I'm in the processing of bring a 5-current system of Oct 2000 vintage more upto-date. The kernel built around May 23rd 2001, has been quite unstable, with numerous warning on lock order reversals, and alas, frequent panics, mostly on account of processes sleeping while holding mutexes. Its been a while since -current was like this :). My priority is to build a reasonably upto-date userland. So, my question is: what is a known good date that I can upgrade the machine to? Regards, Koshy [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: vm_mtx
Those who dial will know its meaning: 6545666,555,666,654555654 On Tue, 24 Apr 2001, Julian Elischer wrote: Poul-Henning Kamp wrote: I'm sure you are fully aware of the implications of the strategically placed supposed in your own sentence. I have never heard anybody get Mach code multithreaded yet. Mach has successfully run in multiprocessor multithreadded systems since 1991. Yep. Distributed processing, too. -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 --- X_.---._/ v To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- [ Joseph Mallett jmallett@[newgold.net|xmrg.com|xMach.org] ] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ Proud Open/Free/Net/4.4BSD User; C Programmer; Mad ] [ www.xMach.org ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Suscribe
suscribe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Majordomo Problem
After installing the majordomo port I get the following message: May 31 04:04:26 n669 sendmail[66642]: EAA66641: SYSERR(root): hash "Alias1": missing map file /usr/local/majordomo/aliases.majordomo.db: No such file or directory a newaliases begets this: freebsd:/etc# newaliases /etc/aliases: 41 aliases, longest 56 bytes, 784 bytes total hash map "Alias1": unsafe map file /usr/local/majordomo/aliases.majordomo.db: Permission denied WARNING: cannot open alias database /usr/local/majordomo/aliases.majordomo Cannot create database for alias file /usr/local/majordomo/aliases.majordomo But, believe you me, the /usr/local/majordomo/aliases.majordomo *is* present, and I am running as root. thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
MajorCool
Does anyone know the default password for majorcool if you install the FreeBSD port? thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xl driver
After my latest cvsup/make world, I have this happening at boot: Sep 3 13:24:26 manatee /kernel: xl0: 3Com 3c900-COMBO Etherlink XL port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 Sep 3 13:24:26 manatee /kernel: xl0: Ethernet address: 00:60:97:58:92:e5 Sep 3 13:24:26 manatee /kernel: xl0: selecting 10baseT transceiver, half duplex Sep 3 13:24:26 manatee /kernel: xl1: 3Com 3c900-COMBO Etherlink XL port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 Sep 3 13:24:26 manatee /kernel: xl1: couldn't map ports/memory Sep 3 13:24:26 manatee /kernel: device_probe_and_attach: xl1 attach returned 6 I only have one ethernet card, so I'm confused why it's trying to set up two. Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl built twice?
While doing a make world, I noticed that perl is built early on. When I came back later, I saw perl being built again along with all the other gnu.usr.bin stuff. Was I tripping or did perl really get built twice? Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mouse madness under X
This is a problem I've had starting with the last couple of builds. If I switch from X to a virtual console, then back again, *sometimes* the mouse cursor will be stuck on the right hand side of the screen. I can move it up and down, but not side to side. The way to cure the problem is to go back to the console, wait a few seconds, then come back into X. The problem goes away. At first I thought this was a problem with my wm, but I tried a different one and got the same result. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic at shutdown
I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic at shutdown
And Bill Fumerola spoke:
On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote:
I just built a new world/kernel yesterday, and now I get a panic when I shut
down. I ran gdb on the dump:
..
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2998272
initial pcb at 25b1c0
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
type 'bt', this tells us just about as much as if you said
"it crashed".
though, by the panic message, this seems to be a known bug..
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
Sorry :)
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2998272
initial pcb at 25b1c0
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc014bd28 in poweroff_wait (junk=0xc02010a0, howto=1)
at ../../kern/kern_shutdown.c:553
#2 0xc0146af0 in lockmgr (lkp=0xc0c50a00, flags=6, interlkp=0xc87108ac,
p=0xc7d4be00) at ../../kern/kern_lock.c:382
#3 0xc01779ab in vop_stdunlock (ap=0xc7d51e48) at ../../kern/vfs_default.c:255
#4 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e48)
at ../../ufs/ufs/ufs_vnops.c:2301
#5 0xc01b1bab in ufs_inactive (ap=0xc7d51e78) at vnode_if.h:865
#6 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e78)
at ../../ufs/ufs/ufs_vnops.c:2301
#7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794
#8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700,
p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955
#9 0xc017c605 in sync (p=0xc026d5e0, uap=0x0) at ../../kern/vfs_syscalls.c:551
#10 0xc014b777 in boot (howto=0) at ../../kern/kern_shutdown.c:225
#11 0xc014b578 in reboot (p=0xc7d4be00, uap=0xc7d51f80)
at ../../kern/kern_shutdown.c:146
#12 0xc01ecd21 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -942333996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at ../../i386/i386/trap.c:1128
#13 0xc01e1ab5 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
On Thu, Jun 29, 2000 at 12:39:46PM -0700, Doug Barton wrote: On Thu, 29 Jun 2000, gnu not unix wrote: Hi. My vote is for root's shell to be /bin/sh if anyone's counting. This will never happen. This position was made clear in th erecent tcsh debate. Speaking of csh and tcsh, I noticed that /bin/csh is hard linked to /bin/tcsh, yet when I invoke tcsh, I get a different prompt than when I invoke csh. I find this rather odd. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GENERIC from today does not detect system console on my box
Chris Costello wrote:
On Friday, June 16, 2000, Peter Wemm wrote:
Err.. how did you run it? 'perl MYKERNEL'? If you run 'perl MYKERNEL'
it will generate nothing because I was kinda lame and didn't know how to do
argument parsing. :-]
Couldn't have hurt to ask.
while (defined($ARGV[0])) {
# ... parse ...
shift;
}
It'd work as perl script.pl arg1 arg2 ... or as ./script.pl
arg1 arg2 ... (if +x).
How about that and as a stdin pipe as well if no args are specified?
while () {
# parse
# ...
}
does this. It is a simple construct, but magical and generally
does what you want. You can even modify the @ARGV array in the middle of
the loop and have it work correctly. Perl is filled with these programming
shortcuts, thus its beauty and strength.
Joe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
odd error in bioscall.s
I have this problem while building a kernel from sources cvsup'ed
today:
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL
-include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s
{standard input}: Assembler messages:
{standard input}:774: Error: operands given don't match any known 386 instruction
{standard input}:839: Error: operands given don't match any known 386 instruction
*** Error code 1
Stop in /usr/src/sys/compile/MANATEE.
The file bioscall.s has only 163 lines. Where is it getting 774 and
839?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Motif is now Open Source 8)
On Tue, 16 May 2000, Sheldon Hearn wrote: On Mon, 15 May 2000 23:08:23 -0400, Donn Miller wrote: Check it out at: http://www.opengroup.org/openmotif/ Yes, that is great news! I tried compiling it, but I had trouble with lib/Xm/Scale.c. It wanted to include langinfo.h, which FreeBSD doesn't have. I've integrated NetBSD's langinfo and nl_types support into FreeBSD. I can send you patches if you haven't managed to work around this yet? That's interesting. I compiled it without problems. Why would it look for langinfo.h on one machine and not another? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syslogd_flags in /etc/defaults/rc.conf
Nick Johnson wrote:
I'm curious to see if anyone is like-minded with me that syslogd_flags in
/etc/defaults/rc.conf should be "-ss" instead of "". I reasoned that it
should be, considering:
1. Most people don't direct syslogs at other machines in my experience.
While I am one of those people that does redirect syslogs to other
machines, I agree with your change.
2. Someone could conceivably DOS a machine by directing tons of crap at
port 121, which is also noted in the BUGS section of the syslogd
manpage.
3. Syslogd runs as root, and while it is a mature piece of code, I think
it preferable to minimize the number of root applications listening
on sockets.
Nick
--
Joseph Scott
[EMAIL PROTECTED]
Office Of Water Programs - CSU Sacramento
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
In contrast, I've been using -Os -march=pentium during the last three months for buildworld and the kernel. Never had problems whatsoever. Perhaps this is a bit off topic, but can the pentium optimisations be used for AMD K6 processors? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
single user mode problem
This has been going on for awhile, and I've looked everywhere for a solution. When I boot single user, the / filesystem gets mounted on wd0s4a even though /dev does not even have such an entry nor does /etc/fstab, since these have all been updated. This is not really such a problem until I try to exit from single user mode. Then, it tries to remount / on ad0s4a and can't find it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I try to exit from single user
mode. Then, it tries to remount / on ad0s4a and can't find it.
Dear Joseph,
as I have recently written, I met an analogous problem while upgrading
to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
order to (somehow) make installworld. Well, I did NOT care about it
and I went ahead ruthlessly ...
By the way, I made another kernel at the end of the process ("by the
book"). I suppose (?) this cleared the problem. In fact, I was able to
boot with no weird messages: all my filesystems were correctly
identified as adNsM (e.g. ad1s2a, ad1s2e ...)
Hi Salvo,
I did read your recent post on this. For me, however, the problem
persists even with a new kernel. I've looked through all the boot and
init files for some clue as to where it's getting the idea that / is on
wd0s4a but I can't find anything ):-(.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b noneswapsw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdos ro,noauto 0 0 proc/proc procfs rw 0 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
On Fri, 10 Mar 2000, Walter Brameld wrote: On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright wrote: Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b noneswapsw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdos ro,noauto 0 0 proc/proc procfs rw 0 0 Shouldn't all those "4"s be "1"s ? No, because I'm using the 4th slice for FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, 7 Mar 2000, William Woods wrote: Good god, I am saying that the files to merger dont existthere is nothing to merge... This is the eror I get when trying to run ssdd /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... That's because it's not under /etc until *after* you've run mergemaster. Right now it's sitting in /var/tmp/tmproot/etc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 6 Mar 2000, R Joseph Wright wrote: On Mon, 6 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? I just re-cvsupped today with crypto and rebuilt. Everything went as smooth as summer butter. I'm really impressed with how quickly and cleanly you developers are able to make things happen. I've only been observing for a short time but it is very interesting. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, Mar 07, 2000 at 12:02:38PM +, FreeBSD mailing list wrote: You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. When you have more experience helping people on a frequent basis, perhaps you will revise this statement. Try helping folks out every day on IRC for 2 or 3 years and tell me what you think THEN. Alternative: answer every question asked on freebsd-questions for same period. You'll see the point once you accomplish this. There is absolutely no reason why you can't submit the help, with suggestion toward ones perception of "the Right Way" to do it, rather than beat the issue to death with superior posturing. There is absolutely no reason why people should lift a finger to help somebody else when said question/inquiry has been documented somewhere on the web or in the manpages, or someplace else. You're right. However, there is no reason to lift a finger to not help someone either. If you don't want to help, simply don't. You save everyone energy. Being a jerk isn't going to keep people from posting elementary questions, that's a fact. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
single user weirdness
A strange thing has happened while booting into single user mode. My / filesystem was mounted on wd0s4a even though I have updated /dev and /etc/fstab to use ad0s4a. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
no openssh after build
I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 6 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? Why, that's a very good question. Why, no, I don't have them installed. :) It wasn't really clear to me, actually. From my tracking of the discussions, which can be very muddy and hard to follow, I thought that openssh was automagically installed but was not really an *active* thing unless the rsaref port was also installed. Thanks for your reply. Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: XFree 3.3.6 authentication failed?
On Fri, Feb 25, 2000 at 03:06:55PM -0800, Joel Ray Holveck wrote: [Followups to -current] I am running monday's current, Mesa-glx for Riva, XFree 3.3.6 and KDE 1.1.2. All from monday's ports tree. Well, I think I can't say I am running this system, for I am getting the following message whenever I try startx: Authentication failed - cannot start X server. Perhaps you do not have console ownership? _X11TransSocketUNIXConnect: Can't connect: errno = 2 seems that you have built XFree with PAM support. Just rebuild without PAM -- it's broken. Could you give me a few more details about the brokenness? It's also in -STABLE. Basically, PAM was built without a crypt library linked in. When new is built with PAM support, it tries to access crypt in PAM. Then, it blows up. Build without PAM, or cvsup latest sources for the patch. It was mentioned in the mailing lists I think back in December? -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 2000 www.anime-expo.org/ # FreeBSD: The Power to Serve www.freebsd.org #The Ultimate Online Speed-Shop www.racesearch.com / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: openssl in -current
On Mon, Feb 21, 2000 at 01:28:34AM -0700, Warner Losh wrote: One thing to keep in mind is that on Sept 8, 2000 the patent for RSA expires and this whole mess goes away. Or at least devolves into the usual crypto export mess rather than the crypto export plus rsa patent law plus rsaref license jumping. So, to double-check here.. it would be illegal to build an openssl based mod_ssl-in-Apache or ApacheSSL Apache to use as the ssl-enabled webserver for an E-commerce company? -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 2000 www.anime-expo.org/ # FreeBSD: The Power to Serve www.freebsd.org #The Ultimate Online Speed-Shop www.racesearch.com / To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: things I noticed w/ 4.0
Sorry for the late reply on this. Ok, cvsup'ed and loaded the most up-to-date bios for my motherboard. (That was tale of woe, but I'll hold off on that telling). Joseph Jacobson wrote: Kernel option VESA fails (see dmesg below). Is this a problem with my graphics card? Are you, by any chance, both compiling in VESA _and_ loading it with loader? VESA is compiled into the kernel. I don't have a /boot/loader.conf file. Is there any other way for the VESA module to be loaded at boot, before /etc/rc runs? Also, none of the vidcontrol VESA modes work for me. (All this isn't a big deal, but the error message is weird). Kernel option PNPBIOS causes the mouse to stop working. A pointer is visible at boot (w/ moused) until the mouse is moved, then it disappears forever. Maybe I'm misunderstanding what PNPBIOS does Weird. Are you sure your BIOS is set to PnP OS = No? My bios has settings "PnP OS", "Use ICU" (run-time software utility), and "Use Setup" (you specify what IRQs and DMAs are available to PnP). I get the above behavior with all three of these settings, (although I believe "Use Setup" is the correct one). I even tried removing my one ISA card (which I don't use anyway, so I can live without PNPBIOS). 'halt -p' still doesn't turn my computer off :). Haven't tested any other functionality of apm though. I usually disable apm in the bios since it makes turning the system power off w/ the button on the case a problem under FreeBSD. Any ideas? Yep. Try turning apm in BIOS on. :-) I didn't express myself very well in the above paragraph. :) Here is the behavior exhibited by my box with apm. When apm is enabled in the bios, and 'apm -e enable' is run, 'halt -p' causes the system to reboot. 'zzz' causes the system to hang (unresponsive to keyboard and mouse input). (I didn't try all permutations of my apm bios settings with 'zzz' to see if I can work around the hang, but I don't think that's the cause). Pushing my power button during the hang state caused the system to reboot. Also, when apm is enabled, after a regular 'halt' or 'shutdown', pushing the power button causes the machine to reset, not turn off. None of this is stopping me from useful work w/ FreeBSD 4.0. --Joe Pertinent parts of dmesg follow: FreeBSD 4.0-CURRENT #1: Thu Mar 2 09:27:11 EST 2000 root@home:/usr/src/sys/compile/new ... Preloaded elf kernel "kernel" at 0xc0341000. Intel Pentium detected, installing workaround for F00F bug module_register_init: MOD_LOAD (vesa, c0246c6c, 0) error 6 md0: Malloc disk ... chip1: Intel 82371AB Power management controller port 0xff40-0xff4f at device 7.3 on pci0 ... pci0: Number Nine model 493d graphics accelerator at 18.0 irq 11 ... psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Am I doing this right?
On Sun, 27 Feb 2000, Steve Kaczkowski wrote: I'm trying to upgrade a 3.4 Release box to the latest Release tree, but running into a few problems, I'm betting someone here can help me! :) I cvsup'd the the latest Release and all went well (no complaints), here's my supfile: *default host=cvsup3.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. The expression "tag=." will get you the latest 4.0-CURRENT sources. If you want to track -STABLE, that should be changed to "tag=RELENG_3". *default delete use-rel-suffix src-all cvs-crypto Nothing too strange there so I'm assuming that's ok. I then remove the /usr/obj directory do the 'make buildworld' which churns for a while (Only a P166) All seems fine with the build, now here is where I run into some issues. I've found some conflicting infomation as to what the next step is. One source says that I should recompile my kernel, reboot into single user and do a 'make installworld'. Makes sense but I can't recompile my kernel, I get errors like: config GENERIC config: line 20: Unknown machine type config: line 20: syntax error config: line 21: syntax error config: line 22: syntax error ... Specify machine type, e.g. ``machine vax'' Etc,etc,etc,etc... It doesn't know ANY x86 CPU, funny enough it doesn't complain if I stick in 'machine vax'. This is happening because under 4.0, you no longer need quotes around options, for example if you have cpu "I586_CPU" it would be changed to cpu I586_CPU Now if I do the 'make buildworld' then drop directly to single users and attempt the 'make installworld' it'll go for a bit and then finally error out with: install-info --quiet --defsection="Programming development tools." --defentry="* libcom_err: (com_err).A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Not quite sure what to check, I've done this probably 10 times now and it seems to do the same thing each time... Any hints? Upgrading to 4.0 from 3.x is a little bit more complicated than simply doing "make buildworld make installworld". The file /usr/src/UPDATING will tell you how to do it under the heading "COMMON ITEMS". Also, note that 4.0 has not yet been released and is still under development, meaning be prepared to have flames in your mailbox should you ask any questions that are "stupid". You should also subscribe to freebsd-current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Am I doing this right?
Also, note that 4.0 has not yet been released and is still under development, meaning be prepared to have flames in your mailbox should you ask any questions that are "stupid". You should also subscribe to freebsd-current. Whoa there, I thought I was replying to -questions. I didn't make myself look stupid, did I? =) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm and /dev/dsp
In 4.0, the pcm sound driver works with my es1371 chipset soundcard for playing cds. But I cannot play mp3s. When I use mpg123, I get the error message "can't open /dev/dsp!" This is an improvement over 3.4, however, where I could not get pcm to work at all. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm and /dev/dsp
On Wed, 23 Feb 2000, Brooks Davis wrote: On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote: In 4.0, the pcm sound driver works with my es1371 chipset soundcard for playing cds. But I cannot play mp3s. When I use mpg123, I get the error message "can't open /dev/dsp!" This is an improvement over 3.4, however, where I could not get pcm to work at all. The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a "MAKEDEV snd0" after upgrading. My es1371 is working great streaming mp3s off of my.mp3.com using xmms. Beautiful. Thank you :) What about for isa cards? Which one is used for them now? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm and /dev/dsp
On Wed, 23 Feb 2000, Brooks Davis wrote: On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: Beautiful. Thank you :) What about for isa cards? Which one is used for them now? I gave my only ISA sound card to Camran so I can't say for sure, but if you hardware the probe address the card ends up at that number and I think PnP cards would end up at pcm0 by default. However, Nick gave the more correct answer in that you should check dmesg and /dev/sndstat. I actually do not have an isa sound card, I was merely curious because in 3.x, pcm0 was reserved for isa cards and pcm1 was used for pci. Is it now set up so that it doesn't matter whether the card is isa or pci, you just use pcm0? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ABIT BP6, UDMA-66 and wdc AC310200
It seems Arun Sharma wrote: Do you have the prober 80pin cable ?? if so please provide a verbose boot... Thanks, that fixed the problem. Has anyone benchmarked the driver ? A very unscientific benchmark that I ran didn't seem to produce much of a difference between UDMA33 and UDMA66. In both cases, I got roughly 13 MB/s. There are almost no mesureable difference between UDMA33 and UDMA66, all mesurements I've done (and have read about) sees little if no difference, in fact some drives can be faster under UDMA33 even if they support the higher rate too. # dd if=/dev/ad4s2 of=/dev/null bs=40960k count=10 10+0 records in 10+0 records out 419430400 bytes transferred in 30.797045 secs (13619177 bytes/sec) Thats probably close to what your drive can pull of the platters... I get 22-23MB/sec off an IBM DPTA drive here with 1% cpu usage, so the driver is not the problem.. Look at your drive specs. I have one drive (Maxtor) with specs that say ~34MB to/from media and 66MB to/from interface (bus). Another piece of the puzzle is the amount of drive cache buffer. Again, I've seen between 512KB and 2MB. Mileage will vary... [It's the old 'burst rate of X' where the following 378 conditions must be met to reach the burst level...] I have a config with 7 disks online, giving me a raw throughput of ~100MB/s sustained, that is about the limit of what can be done over the PCI bus... -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Joseph Thomas E/Mail: [EMAIL PROTECTED] Network Computing Services, Inc. [EMAIL PROTECTED] 1200 Washington Ave So. Tel: +1 612 337 3558 Minneapolis, MN 55415-1227 FAX: +1 612 337 3400 An elephant is a mouse with an operating system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade from 3.4 to 4.0...
On Tue, 22 Feb 2000, Alfred Perlstein wrote: * William Woods [EMAIL PROTECTED] [000222 21:27] wrote: I did read that document, and honestly, it dident make a lot of sence and it seemed to have some conflicting instructions.which is why I am asking here. It looks pretty concise to me, perhaps you can explain the confusion so that we may fix it so as to help other users? It seems like it contains good information for those who have been on the track for awhile, while being a bit cryptic for people new to the process. Since this is a development version, I suppose that's to be expected. I followed the instructions that someone else posted on -questions: make buildworld make buildkernel make installkernel Then reboot in single user mode make -DNOINFO installworld make buildkernel make installkernel (again) make installworld This worked for me perfectly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade from 3.4 to 4.0...
On Tue, 22 Feb 2000, William Woods wrote: On 23-Feb-00 R Joseph Wright wrote: make buildworld make buildkernel make installkernel Then reboot in single user mode make -DNOINFO installworld make buildkernel make installkernel (again) make installworld This worked for me perfectly. Hmmm.the only question I have regarding this is does it handle the new devices corectly? It did, although I did eventually remake them. I did: mv /dev /dev.old mkdir /dev cp /usr/src/etc/MAKE* /dev sh MAKEDEV all I also had to make the partition entries for my IDE drive: sh MAKEDEV ad0s4a Then I edited /etc/fstab to reflect the new devices --Very Important! Of course I also ran mergemaster to update the /etc directory. That's it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
devices under 4.0
I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would like to know how to change over the devices. I created the new devices by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running it, but it didn't create any ata* devices such as is shown in the kernel config file. It did make devices ada1, ada2, ada3, and ada4, which would correspond to the four slices on my disk, but if there are no freebsd partitions shown, such as ada4a, etc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Real Producer and FreeBSD
To clarify ... Real Producer is the program that performs the encoding of Real Audio streams. I would prefer to run it under FreeBSD but am having problems related to its willingness to play with libc6 and glibstdc++2.8. I was hoping to check my setup with someone else attempting to do or having done the same. Daniel C. Sobral wrote: Joseph T. Klein wrote: Has anyone gotten real producer to run under FreeBSD, or am I to resort to Linux? Whatever is you are calling a producer (in my vocabulary, it is a resource generation agent), if there is one that runs on Linux, why not use it under FreeBSD? -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Given infinite time, 100 monkeys could type out the complete works of Shakespeare. Win 98 source code? Eight monkeys, five minutes. -- j...@titania.net [arin-jk70] Various predictions have fiber links arriving on our doorsteps in 25 or 30 years. Special Report: Local Loop Access, February 1999 Network Magazine To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Real Producer and FreeBSD
Has anyone gotten real producer to run under FreeBSD, or am I to resort to Linux? -- j...@titania.net [arin-jk70] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: net.inet.tcp.always_keepalive on as default ?
Poul-Henning Kamp writes: Mind you, this is only a problem because FreeBSD is to bloddy stable: I logged into a customers server a few days a go, it had been up for over a year, and had accumulated tons of ftpds from If this customer is using wu-ftpd, it's very possible that you saw daemons blocked inside of accept() for PASV data connections. We used to see the same behavior here wrt. ftpds hanging around and it was almost always the case that the socket was in the LISTEN state. The code (ftpd.c:dataconn()) was changed to time out the data connection establishment using select() before calling accept(). If the client doesn't connect within 15 minutes, we log the event and the daemon exits. A diff against our code wouldn't be helpful, since we've added our own ugly warts to it (but I'll do so if you want it). If this is indeed the same problem you're seeing, tcp keepalives won't help. I haven't looked at the FreeBSD ftpd code to see if the accept is timed out somehow to prevent this (possibly inadvertent) DOS attack. -- Sudish Joseph MindSpring Enterprises To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Handbook DocBook cutover complete
On Mon, Mar 29, 1999 at 06:34:27AM -0500, Brian Feldman wrote: Doc is a nice format, but it's not hypertext. Check out ports/palm/pilot_makedoc TealDoc's version supports graphics and links. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Seeing NFS saturation 'loop' when installworld'ing to NFS / and /usr
On Thu, Feb 11, 1999 at 10:24:51AM +0100, D. Rock wrote: Anyone with /usr/obj NFS mounted should have the same problems. I've just updated my firewall machine using NFSv3 hardmounted /usr/obj over a 10BaseT connection (slow!). Did a make installworld, and kernel rebuild over it last night with the latest cvsup.. NFS server was running 3.1-beta (2/10), and NFS client (firewall) was running 3.0-current (1/10). No problems at all.. I will try the termcap database test tonight.. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
GUI for cdrecord
does anybody know of a decent GUI for cdrecord that works on -current? XCDRoast is pretty hardcoded for linux. -- Jim Joseph Email: j...@phoenix.net The rule is, jam to-morrow and jam yesterday, but never jam today. -- Lewis Carroll To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: windowmaker
I will happily take the patches and test it on -current :) -Jim On Thu, 14 Jan 1999, Brian Handy wrote: Anyone running the new windowmaker (0.50.2) on current? Any problems, advice, pitfalls? The windowmaker port is out of date (0.20.3). I'm running it on -STABLE...no -current box here. I've sent the patches to my committer guy, but he doesn't seem to be in right now. (Maybe I'll submit a PR here in a minute so someone else can grab it and have a go at it.) Regards, Brian -- Jim Joseph Email: j...@phoenix.net Be free and open and breezy! Enjoy! Things won't get any better so get used to it. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Which sound card now?
Is the SB PCI 128 supported yet in -current. I new a new sound card and I really would like a 'real' Sound balster. On Fri, 15 Jan 1999, Satoshi Asami wrote: * From: br...@worldcontrol.com * So I am now mostly back the square 1. I'm still using an old GUS MAX, * which at the whim of FreeBSD-core may suddenly stop working. Just one point -- the axing of voxware was *not* approved by FreeBSD-core, and that's why it has been brought back. Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Jim Joseph Email: j...@phoenix.net Be free and open and breezy! Enjoy! Things won't get any better so get used to it. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Forward all spam to u...@ftc.gov
On Wed, Jan 13, 1999 at 07:36:35PM -0600, Jim Bryant wrote: This announcement is located on the Federal Trade Commission's complaint form page http://www.ftc.gov/ftc/complaint.htm I've been using the address for over half a year.. Nada for response nor spam reduction. So I just tightened up my procmail filters instead.. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ #Anime Expo 1998 www.anime-expo.org/ # Redline Games www.redlinegames.com/ # Cal-Animage Epsilon www.best.com/~nugundam/epsilon/ # EX: The Online World of Anime Manga www.ex.org/ / To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
