Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 9/30/2013 11:23 AM, David Demelier wrote: Nice, but how does it handle if a Makefile contains a love target? The easter egg only appears if the target isn't defined. ___ 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: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
Devin, I just want to say that I really liked the reference. I was teaching myself loader/forth and working on a version of it for my own amusement when I saw the commit. Please do continue to make these silly things in the future. I actually run FreeBSD in production and my boss loved it so much we actually have an official change-order ticket to preconfigure all of our production 9.2 systems to show the logo. A guy I work with slated a hack to show it at the login prompt as well. :) As for any of you who objected seriously: it's a joke, a tribute to one of the better cult action movies, and a nice bit of pre-release fun. While there are some Linux distros like RHEL where you can pay someone to listen to your pointless complaints, Devin doesn't get a cent to put up with your whingy little snit. In short, stuff it. ___ 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: zfs_enable vs zfs_load in loader.conf (but neither works)
On 9/8/2013 7:52 PM, J David wrote: On Sun, Sep 8, 2013 at 10:22 PM, Darren Pilgrim wrote: Did you build and install new boot blocks? Yes. Oddly, setting: zfs set mountpoint=legacy data/root (plus the appropriate fstab entry) You can use zfs.root.mountfrom="zfs:data/root" in /boot/loader.conf instead of an fstab entry. Mountpoint=legacy is required either way. instead of zfs set mountpoint=/ data/root This only applies to Solaris, IIRC. seems to produce a bootable system, although it absolutely should not be necessary to do things that way anymore. I ran into that problem as well. The instructions for root-on-zfs for 9.x (at least as of 9.1) are wrong--you need to use the 8.x-style instructions with mountpoint=legacy for / and, for fresh installs, leaving the pool imported and copying over /boot/zfs/zpool.cache. ___ 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: zfs_enable vs zfs_load in loader.conf (but neither works)
On 9/8/2013 6:02 PM, J David wrote: Trying to mount root from zfs:data/root []… Mounting from zfs:data/root failed with error 2: unknown file system. Did you build and install new boot blocks? ___ 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: Building RELENG_9 (or RELENG_9_*) on a small machine?
On 2013-03-01 10:50, Ian Smith wrote: At 256MB - the minimum earlier that completed installation without disabling CTL - swap often sat at ~14MB but blew out to around 165MB building those huge llvm libraries - cc1plus 332M, 173M resident was one top I snipped, but I can't say I caught the biggest. I had top running throughout a build and saw cc1plus reach 460 MB with 171MB resident, at that point CPU was down to about 4% and the system was hammering swap. As a testament to FreeBSD's robustness, I could still log in via ssh, start screened shells, and generally conduct admin tasks while cc1plus beat the crap out of my VM. Even start and stop other services. Then I added 128MB (to 384MB) and repeated the first buildworld (incl. clang) expecting huge savings as it'd only touched swap to about 12MB a time or two, mostly having 100MB+ of free memory .. wow, down to 7h02m! For 9.x, I changed my notes to "256 MB to run, 768 MB to build". For 8.x, the numbers were 192 MB to run, 512 MB to build. Here at least, building llvm libs and clang doubles buildworld time! and extends /usr/obj from 675MB to 1GB. I'll be doing `make buildkernel buildworld` ET and size comparisons between RELENG_8_3 and RELENG_9_1 when I test out my buildbox. I'd like to gather memory usage metrics as well, if someone knows some tricks for that. My current approach is somewhat crude. :) If there's interest I'll follow up with the results here. ___ 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: Building RELENG_9 (or RELENG_9_*) on a small machine?
On 2013-02-28 06:43, Ryan Stone wrote: It's possible with a caveat: in my experience both the object tree and the source tree have to have *exactly* the same path on the build host and the destination. You can't (for example) build with MAKEOBJDIRPREFIX set to something, then copy src to /usr/src and obj to /usr/obj on the destination and have installworld work. Why couldn't I just also specify MAKEOBJDIRPREFIX on the destination machine? ___ 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: Building RELENG_9 (or RELENG_9_*) on a small machine?
On 2013-02-27 18:23, Adrian Chadd wrote: Hm, have you disabled that CAM target layer stuff at boot? It's likely tying up some RAM. Disabling CTL let cc1plus get is resident size up to 167 MB, but that still wasn't enough. Building clang is simply too memory intensive. :/ To the buildbox! ___ 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"
Building RELENG_9 (or RELENG_9_*) on a small machine?
So I have this VM which only has 256 MB of memory and 9.1-R installed. I want to update it to RELENG_9, but buildworld swaps so bad it grinds nearly to a halt. Even make -j1 -B runs into very heavy swapping. So two questions: 1. Is there anything I can do to set a limit on how much memory the compiler uses? 2. If I crossbuild for this machine, can I get away with doing buildworld on a buildbox, ship the obj tree, and do installworld and mergemaster on the VM? It's been a few enternities since I did a cross build and back then it was crossbuilding releases. ___ 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: ICH9 ethernet part (82566) woes
Daniel O'Connor wrote: On Fri, 21 Sep 2007, Jack Vogel wrote: What you will be able to do shortly is download the new driver from Intel, version 6.6.6 (LOL, really :) Heh, I look forward to testing Satan's own ethernet driver.. :) I hear it's kind of a beast. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: BIND 9.3.1 - How to get rid of AAAA querys?
Andreas Pettersson wrote: Mark Andrews wrote: Why don't you go the other way and get yourself IPv6 connectivity. You do realise that you will require it to reach many sites in about 3 years time as they will be IPv6 only For almost 10 years I've heard discussions about the successor to IPv4, but from my point of view (may differ from others..) not much has happened. Of course, I can imagine that when the wheel starts rolling for real things might change quickly. 3 years may prove to be correct, but are there any clear signs pointing in this direction? The proponents of IPv6 have claimed growing real-world deployment for the last several years. There is yet no significant commercial deployment--the real world still runs on IPv4. The mitigating factors are IPv4 address space pressure and global routing problems. Every time enough people start crying about too little IPv4 address space left, IANA reassigns more reserved space into the allocation pool and those fussing grow quiet. As for global routing, it can be summed as: it ain't broken enough, yet. It's going to be years before there is a real, sustained pressure to migrate significant portions of the commercial internet into IPv6 space and years more for enough key-player migration to drag the rest of the commercial world with it. The academic and research portions of the internet are not the driving force. Convince MSN, AOL, Yahoo, Comcast, $BIG_NATIONAL_ISP, etc. to deploy IPv6 and we'll get wide-spread global IPv6 deployment overnight. I'll put it this way: When my Linksys WRT54G supports IPv6 on both sides of the router, IPv6 will have reached commercial viability. Until then, it's a research exercise. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: large RAID volume partition strategy
Vivek Khera wrote: On Aug 17, 2007, at 10:44 PM, Ivan Voras wrote: fdisk and bsdlabels both have a limit: because of the way they store the data about the disk space they span, they can't store values that reference space > 2 TB. In particular, every partition must start at an offset <= 2 TB, and cannot be larger than 2 TB. Oh... one more note: if I don't use fdisk or paritions, I *can* newfs the raw drive much bigger than 2Tb. I just don't want to do that for a production box. :-) Or you can use GPT, which uses 64-bit data structures and thus has an 8 ZB limit. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
3ware cards [Was: Re: A little story of failed raid5 (3ware 8000 series)]
Gary Palmer wrote: Darren Pilgrim wrote: Tom Judge wrote: If you use the 3dm2 management interface you can schedule verify and rebuild tasks to run on a regular basis. I think that 7500 series controllers can do this, 9500 and 9550's definitely can. >> Actually it's all 7/8/9xxx series cards. The 9xxx series cards also do auto-verify so there's no need to schedule the task. Sorry, I do not believe that is the case. I have a 8506-4LP and if I click on Management -> Scheduling in the 3dm web interface it says (0x0C:0x0017): Scheduling is not supported on this controller model However you might be able to cheat using the tw_cli port to run the schedules out of cron rather than native on the card I was talking about the verify task, though I now realize that wasn't clear. Some of the older cards do only support tw_sched. The ability to perform data verification and media scans has been present since the 7xxx series. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A little story of failed raid5 (3ware 8000 series)
Tom Judge wrote: Tom Samplonius wrote: The real solution is RAID scrubbing: a low level background process that reads every sector of every disk. All of the real RAID systems do this (usually scheduled weekly, or every other week). Most 3ware RAID card don't have this feature. So rather than not using RAID5 or RAID6 again, you should just not use 3ware anymore. If you use the 3dm2 management interface you can schedule verify and rebuild tasks to run on a regular basis. I think that 7500 series controllers can do this, 9500 and 9550's definitely can. Actually it's all 7/8/9xxx series cards. The 9xxx series cards also do auto-verify so there's no need to schedule the task. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A little story of failed raid5 (3ware 8000 series)
Artem Kuchin wrote: Darren Pilgrim wrote: Artem Kuchin wrote: That exactly was i was talking about. I don't acess to individual disks behind raid unit, so, i cannot doit. I don't know it controller VERIFY command does it right. If it doesm then i shoudl put it into a cron job and do it on weekly basis. Also, it would halpfull it i could get access to number of left reserved sector for remapping. Any idea about these two for 3ware controllers? Also, someone should mention, that while using raid MUST do verifies often. The 3dm2 software (sysutils/3dm port) can dump the SMART data from individual disks. It can also schedule verify and self-test tasks and identify individual drives by blinking the activity light for the drive. ___ Problems are: 1) how to parse this dump of data? Actually smartctl (part of smartmontools) can read the SMART data through a 3ware controller. 2) No scheduling is available on 7000,8000 on 4 port models Use tw_sched then. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A little story of failed raid5 (3ware 8000 series)
Artem Kuchin wrote: That exactly was i was talking about. I don't acess to individual disks behind raid unit, so, i cannot doit. I don't know it controller VERIFY command does it right. If it doesm then i shoudl put it into a cron job and do it on weekly basis. Also, it would halpfull it i could get access to number of left reserved sector for remapping. Any idea about these two for 3ware controllers? Also, someone should mention, that while using raid MUST do verifies often. The 3dm2 software (sysutils/3dm port) can dump the SMART data from individual disks. It can also schedule verify and self-test tasks and identify individual drives by blinking the activity light for the drive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: getting garbage faster using FreeBSD?
Clayton Milos wrote: We use a device called a degausser. It creates a very strong varying magnetic field that totally wipes out everything on a tape. We've put a few hard drives on it to test it out. it TOTALLY wipes out everything on the drive include the bios sectors rendering the drive totally unusable. We can't even get it back after that. Class I or Class II? -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommendations for a serial port card you can actually BUY?
Henrik Brix Andersen wrote: On Thu, Oct 05, 2006 at 05:04:41PM -0400, Bob Johnson wrote: I have used USB-to-serial converters with no problem. All the control signals (at least the ones my applications need) seem to work correctly. I don't remember any brands or models off hand, I bought what was cheap as I needed them and they all worked. "Cheap" means under $20 delivered (for one port). Speaking of USB-to-serial converters... anybody know which chipset Moxa's UPort 1610-16 [1] and similar products are based on? Anybody know if they work with FreeBSD? Considering that their vendor ID (0x110a) isn't found anywhere in the FreeBSD source, I'd say they aren't supported. Their tech support contact form does list FreeBSD 4.x and 5.x, however, so they may provide their own drivers. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recommendations for a serial port card you can actually BUY?
Karl Denninger wrote: I wasn't aware that the USB to Serial converters would work - I can try them, but there are a lot of those out there that don't work right even under Windows - expecting them to under FreeBSD might be asking too much. A local vendor sells a generic adaptor[1] that uses the Prolific Tech PL-2303HX chip supported by uplcom(4). I use them for APC Smart-UPS and MGE Evolution (both utalk and SHUT) with NUT and the terminal end of serial console connections. The funny thing is that they work better in FreeBSD--Windows' serial device auto-detection is convinced my servers are Wacom tablets. The Windows bug is worked around by connecting the adaptor first, then connecting the adaptor to the serial device after Windows has finished its plug-and-play spasm. 1: http://store.pchcables.com/usbtorsseca.html -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ARRRRGH! Guys, who's breaking -STABLE's GMIRROR code?!
Karl Denninger wrote: I don't think its too much to ask that before something is MFC'd back to -STABLE from -CURRENT that it be tested for the most common functionality (that is, does it work at all?) In this case all that someone had to do was boot the system and then detach and reattach a mirror component - the most basic of functionality - to detect that the patch was bad. That obviously wasn't done in this instance. I understand that finding corner cases and expecting exhaustive testing is unreasonable from a free project - even in a -RELEASE we don't get that. But this wasn't a corner case - it was a situation where absolutely zero testing was performed before the MFC was sent back to the source tree. So when can the FreeBSD Foundation expect your donation of computers for the purpose of GEOM testing? -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 16M RAM enough for FreeBSD 6.1?
Torfinn Ingolfsen wrote: Hello, I have an old laptop, a Compaq Armada 1580DMT, with 16M RAM, 2GB hd, floppy and CD-rom. It doesn't have built in networking, neither wired nor wireless. It does have PC card slots. It has had FreeBSD 4.9-release installed a long time, and was recently upgraded to 4.11-release from CD, sucessfully. However, I would like better pccard support, ie. 32 bit cardbus and wireless network cards, so I would like to install 6.1-release (or -stable) on it. However, when I try the 6.1-release CD (CD1), it boots as far as loading the kernel, botting the kernel, and then reboots again?? Try turning off all power management and plug-and-play support in the BIOS and booting FreeBSD without ACPI. Try combinations of these three things. Often older hardware has really broken APM/ACPI support that makes FreeBSD do odd things. Failing that, you may need to build a custom kernel with just the minimum required to get yourself to a shell prompt. You can build a new kernel with cardbus, usb and other extras after you get FreeBSD installed. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: suggestions for SATA RAID cards
Andreas Klemm wrote: On Wed, Aug 23, 2006 at 09:23:00AM +0100, Steven Hartland wrote: The Areca cards I can recommend. Highpoint 1820a is surprisingly good Many many years ago I bought a HighPoint HPT366 ATA66 controller. Thought its a good deal because it was cheap. Thought, an ATA interface can't be that complicated anymore so that its safe to buy a cheap product. Turned out that I was very wrong with my theorie. I ran into timeout problems, that couldn't be fixed. After days and nights of troubleshooting and testing I didn't get it to work reliably. I replaced it by buying a more expensive Promise controller. Since then I had zero problems. Since that time I lost trust in HighPoint products. The 366 was an exception, mostly. It was a borked piece of hardware in a "new generation" of ATA controllers at a time when IIRC FreeBSD was on the leading edge of major overhaul of ATA support. Modern HighPoint controllers are decent for the price. I wouldn't put one in a server, though. My servers use 3ware and Dell cards. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fail to install the driver of the on-board LAN Card
Johnie Wong wrote: Dear All, I am the user of FreeBSD 6.1. Recently, i buy a new server for my company which is a Intel Core 2 Duo E6300 (1.86GHz) with Intel D946GZIS mainboard, 2GB Consair DDR2 Ram, 3Ware 9500S-4LP, and 4X Seagate 250GB SATA II Harddrive. But when i install the on-board LAN card driver by activating the default fxp option, it is invisible. That board is really new, so I would guess you have a new network controller with a PCI ID FreeBSD doesn't know about yet. It's a pretty common occurrence, especially with Intel NICs. Post the complete output of `pciconf -lv` (preferrably as an attached text file) and someone will see if this is the case. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't appear in sysctl. Gotta love namespace collisions. -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MySQL and default memory limits (mysqld: Out of memory)
Mathieu Arnold wrote: +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : > | I read somewhere that FreeBSD by default | limits process size to 512MB, however the variables used to tune it do | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more | memory? If you're using a i386, the max process memory size limit is at 512M, you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. That OID doesn't seem to exist: > uname -pr 6.0-RELEASE-p1 i386 > sysctl -N kern | grep max kern.maxvnodes kern.maxproc kern.maxfiles kern.argmax kern.maxfilesperproc kern.maxprocperuid kern.ipc.maxsockbuf kern.ipc.somaxconn kern.ipc.max_linkhdr kern.ipc.max_protohdr kern.ipc.max_hdr kern.ipc.max_datalen kern.ipc.maxpipekva kern.ipc.msgmax kern.ipc.shmmax kern.ipc.maxsockets kern.iov_max kern.kq_calloutmax kern.maxusers kern.threads.max_threads_per_proc kern.threads.max_groups_per_proc kern.threads.max_threads_hits kern.smp.maxcpus -- Darren Pilgrim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: How can I know which files a proccess is accessing?
Eduardo Meyer wrote: Hello, I need to know which files under /var a proccess (httpd here) is acessing. It is not logs because I have a different partition for logs. gstat tells me that slice ad0s1h (my /var) is 100% frequently, and in fact with fstat I can see a number of httpd proccesses running accesing that. But fstat only shows me inodes and the mount point. I need to know which files the proccesses are acessing. find(1) can match inodes. A quick example: > fstat | grep 'httpd.*/var ' | awk '{print $6}' | xargs -n 1 sudo find -x /var -inum | sort -u /var/log/httpd-error.log /var/run/accept.lock.# /var/tmp/apr8530d5 /var/tmp/aprF2Zs0e -- Darren Pilgrim ___ 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.1-PRERELEASE (April 5, 2006) randomly rebooting on Dell Poweredge 650
Matt Watson wrote: The subject line pretty much says it all, I have a Dell Poweredge 650 box running 6.1-PRERELEASE which was cvsup'd on April 5, 2006. The box has now twice rebooted on its own for no aparant reason. <...> [Log indicates no errors, spontaneous reboot.] <...> This machine previously had Linux installed on the box and did not display the same problems, so I'm going on the assumption that its not a hardware failure. Aside from the reboots the box has been preforming extermely well. If anybody can provide some insights or suggestions I'd greatly appreciate it. Check your BIOS settings for a hardware watchdog timer. I had this problem on some brand-new servers (same class of hardware as yours) and disabling the timer stopped the reboots. Intel 6300ESB, if anyone's interested. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: downgrade question
Chris H. wrote: Greetings all, I inadvertently put the wrong tag in my cvsup script and ended up with 5.5-PRERELEASE instead of 5.4. If I just change the tag to default release=cvs tag=RELENG_5_4 will it prune and/ or overwrite my src tree accordingly? Yes, cvsup is fully capable of reverting collections to older versions. Actually, cvsup doesn't really care which is older or newer, it just compares your files to what's on the server, then makes any modifications necessary to make your files match the server's files. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA RAID: Adaptec 1420SA, Promise TX4300?
Daniel O'Connor wrote: On Monday 03 April 2006 04:39, George Hartzell wrote: With raid systems that use proprietary metadata I'd need to find a similar controller to hook them up to. Actually no.. If you are using a cheap RAID like Promise TX2 or just about any onboard IDE/SATA RAID that FreeBSD supports the array can be used on ANY system. (Except for booting) More concisely, is this because said cheap RAID controllers all use the ataraid framework and therefore the metadata stored on disk is inherently understood by FreeBSD? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
How to make sshd not log invalid user login attempts?
In 4.x, I can make sshd not log this noise by using the Deny/Allow Users/Groups options. In 6.x, the same configuration doesn't stop the logging, so my logs get overrun with thousands of "Failed password for invalid user" messages. What do I need to do to make sshd not log this information? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: How can i get CIFS-Support in my kernel?
From: Roger Grosswiler > > i would like to get CIFS-Support instead of SMB. How can i > get this into my kernel?? SMB is CIFS. CIFS is the product of Microsoft's "embraced and extended" implementation of the standard SMB protocol. Due to imcomplete and expired IETF drafts and licensing issues, there is no real CIFS standard from which to write an implementation. There isn't even real documentation of the differences between the standard SMB and Microsoft's CIFS. The smbfs support in FreeBSD is good enough to work in most cases. If you need something directly developed toward a high degree of interoperability with Windows, there are ports from the Samba project which may provide a more complete implementation. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: powerd effectiveness
I guess I should chime in here: 1.6GHz Pentium M notebook. Everything enabled: ACPI, USB, wireless, bluetooth. powerd_flags="-i 100 -r 25" The backlight is on continuously in FreeBSD. Lag is hard to notice, since it takes <100 ms to make the 100->1600 MHz step, but I can see brief lag if the machine is completely idle and I do something to eat the CPU that provides an immediate visual indicator of churn rate, like run an animation. Battery life: FreeBSD, powerd running: 4.5-5 hours FreeBSD, powerd not running: ~2 hours For comparison: Windows XP, aggressive power-saving: ~3 hours As for heat, the surface hot spots all stay significantly cooler with powerd running. I don't have working system health stats in FreeBSD, so quantitative heat reports aren't possible. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Unable to set device characteristics with devd
From: Kevin Oberman > > I've been trying to use devd for a number of things, but have > not gotten > far. > > One issue is when I attach an ATAPI disk: > attach 100 { > device-name "acd0"; > action "/bin/chmod 666 /dev/$device-name"; > } > > I have similar statements for my second hard drive (ad2s2). > > By using the -D option I see the device attach, but the chmod returns > an error indicating that /dev/acd0 does not exist. I get > similar results for other devices. > > Is there a delay between the attach event and the creation of the /dev > entry? Am I missing something here? Maybe I should use devfs for this. The normal tools (chmod, chown, etc.) don't work on devfs. You need to create devfs rules to change permissions, ownership, etc. on device nodes. See devfs.rules(5) and devfs.conf(5). ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Few questions.
Its Azfar <[EMAIL PROTECTED]> wrote: > > I want to move my servers on freebsd from linux and I > need few information regarding freebsd > compatibilities. > > 1. What is the current status of freebsd compatibility > with Java. Multiple versions of Sun's JDK is available in the java/ directory of the Ports Collection. The FreeBSD Java Project, which is responsible for porting Java to FreeBSD can be found at http://www.freebsd.org/java/. > 2. What is the current status of freebsd compatibility > with MySQL. MySQL runs very well on FreeBSD. Multiple MySQL server and client versions are available in databases/ directory of the Ports Collection. There is no authoritative site for MySQL on FreeBSD to my knowledge, but installation is very straight forward. > 3. What is the current status of freebsd compatibility > with SMP and Threading. SMP with FreeBSD is extremely stable with both 5.x and 6.x. Both schedulers are good choices in the latest 5.x and 6.x, but I would recommend using the 4BSD scheduler over the ULE scheduler in a production environment. There is an implementation of LinuxThreads available for FreeBSD. You can get it by installing the devel/linuxthreads port. The MySQL ports have options to let you build them with linuxthreads support. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: usbd.conf
usbd is deprecated. Please use devd. From: Petr Holub > > I've found that usbd on 6.0-RELEASE doesn't react on detach > event properly: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: application to check cpu / system temp?
From: Mike Tancsa [mailto:[EMAIL PROTECTED] > At 07:59 PM 14/10/2005, Darren Pilgrim wrote: > > >I wouldn't trust any of these. It's been a few years since > any of them have > >given me complete or even correct values on current > hardware. I can provide > >examples on current hardware running RELENG_5 and -CURRENT, > if anyone is > >interested. > > They certainly dont work on *all* boards, so YMMV. However, the > various VIAs, ICH4,5,6s, they work for me. The two machines I have on hand, an i915-based notebook (dell) and an E7525-based server (Supermicro), both produce bad output. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: application to check cpu / system temp?
From: Mike Tancsa > At 04:54 PM 14/10/2005, Jayton Garnett wrote: > > > >Are there any apps/utilities to check the cpu and system temperature? > > Yes, check in /usr/ports > xmbmon > lmmon > healthd I wouldn't trust any of these. It's been a few years since any of them have given me complete or even correct values on current hardware. I can provide examples on current hardware running RELENG_5 and -CURRENT, if anyone is interested. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6300ESB watch-dog timer/apic support?
I have a system with a Supermicro X6DAL-G main-board on which I'm running RELENG_5_4. The following are from the output of `pciconf -vl`: [EMAIL PROTECTED]:29:4:class=0x088000 card=0x668015d9 chip=0x25ab8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '6300ESB Watchdog Timer' class= base peripheral [EMAIL PROTECTED]:29:5:class=0x080020 card=0x chip=0x25ac8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '6300ESB APIC1' class= base peripheral subclass = interrupt controller I haven't had much luck finding out how to attach to these. Is there support at all? Perhaps in -CURRENT? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Audigy LS and Netgear WG311 drivers
From: Brandon Beamer > > I'm running FreeBSD 5.4. I have a Soundblaster Audigy LS and > a Netgear WG311 v3 wireless PCI card. The ath driver does not > recognize the Netgear card The WG311v3 doesn't use an Atheros chipset. You, like many others, are confused by companies like Netgear who, throughout the course of a specific model number's life, will use entirely different devices. The original WG311 (unmarked, but effectively "v1") used the Atheros 5212, which is supported by the ath driver. The WG311v3 uses the Prism GT which isn't supported. There was a third-party driver[1] for the Prism 54 family of wireless chips, but it appears to have mysteriously vanished, even from the Internet Archive, which says the pages were archived, but not indexed. You may find some leads through the Linux Prism 54 driver homepage[2]. Presently your only options are either the ndis Windows driver wrapper or using a different network card. [1] http://green.homeunix.org/~green/prism54-driver/pff/ [2] http://www.prism54.org/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Sysinstall automatic filesystem size generation.
From: Julian H. Stacey > "Steven Hartland" wrote: > > data. In addition to that I dont have to sit though 1 hour worth of > > offline checks when it crashes for what ever reason which I do on our > > FreeBSD boxes. > > [Apologies if I missed something, coming in late on thread, but ...] > > FreeBSD-4 does fsck on dirty filesystems before going multi > user: You wait. > FreeBSD-5.* & 6.0-BETA3 : fsck runs in background after boot: > No waiting. A dirty volume can cause some fairly severe problems if it's used before the background fsck completes repairs. I'd rather delay restart than face even more damage when something else dies because the volume was mounted dirty. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Sysinstall automatic filesystem size generation.
From: C. Michailidis > [sysinstall FS sizing defaults] > > <...> Isn't it safe to make some of the default sizes a > wee bit larger? That is, a 256mb /tmp and /var doesn't seem > "appropriate" if you have one of these massive modern disk > drives. For christ's sake, I'd gladly give up a GB or two of > /usr so I could build openoffice without needing to consider > that I may need an extra few megabytes in /var at the time of > the system install. > <...> > > Wouldn't it be smart to remove the hardcoded default sizes > altogether and dynamically generate them according to a > reasonable function? Probably, but a template for something like this isn't simple unless it's created as part of a general profile-based installer that would inform sysinstall of the machine's purpose in life. For example, a "workstation or Windows replacement" would need several extra GB in /usr whereas a server would get away with a much smaller /usr, but need those extra file-systems for logs, spools and other data. There are, however, some basic constants: If /usr, /var and /home are on another file-system, / doesn't need to be more than 150-200 MB. There just isn't that much in the root file-system. Assuming the default log retention and no spooling, /var will likely never grow past 50MB. Adding a mail, web, db or log server or increasing log retention will go well past that mark, but then such servers should have subordinate file-systems to handle the extra data. What comes with the OS will take less than 300MB in /usr. /usr/src and /usr/obj eat around 500 MB each. /usr/local eats around 1 GB for most servers and 3 GB on a desktop. /usr/X11R6 is empty if X isn't installed, the base Xorg server package is a few hundred MB and a desktop can need several GB. /usr/ports should have 1-2 GB just for distfiles on a desktop built from ports and 3 GB for work if you're building something huge, like KDE. I size /usr/ports to 6 GB on my desktop machines. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: IRQ conflict between twa0 and skc0
From: Brandon Fosdick [mailto:[EMAIL PROTECTED] > > Darren Pilgrim wrote: > > Try switching slots with the RAID and video cards. It's silly, but > > then so is PCI interrupt routing. > > Unbelievable. Who ever wrote the PCI spec should have been shot. I believe the IEEE was involved. :) > I switched the cards and now the network card is sharing an > interrupt with the video card, but neither seems to mind. > More importantly it isn't sharing with the raid card and they > all appear to be happy. IRQ sharing is a known issue with many RAID cards and even some gigabit ethernet cards. It seems to correlate to cards that push the performance limit of the bus. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: IRQ conflict between twa0 and skc0
From: Brandon Fosdick > Mike Jakubik wrote: > > > > The easiest thing would probably be to disable the onboard > > sk card, and put in an em (intel gigabit card). The marvell > > chipset and driver is known to be problematic. > > I had thought of that, but the motherboard only has 2 > non-express PCI slots and they're both currently filled by > the video card and the raid card. I could take the video card > out, but then I wouldn't be able to see what I was doing. Try switching slots with the RAID and video cards. It's silly, but then so is PCI interrupt routing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Building kernel, -mno-3dnow and stuff.
From: Viatcheslav Fedorov > > cc -O -pipe -march=pentiumpro -march=athlon-tbird > -I/<...cut...> -mno-mmx -mno-3dnow -mno-sse -mno-sse2 These are disabled because they cause problems when used in the kernel. > my ``/etc/make.conf'' file: > - > CPUTYPE=athlon-tbird > CFLAGS= -O -pipe -march=pentiumpro > COPTFLAGS= -O -fomit-frame-pointer -march=pentiumpro -pipe > - You should not put -march in your FLAGS variables. CPUTYPE determines the correct architecture- and processor-specific compiler flags. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ndis with Intel 2915 wireless, getting "NDIS ERROR" messagesand deattach on boot
> From: Darren Pilgrim > From: Carl Gustavsson <[EMAIL PROTECTED]> > > > > Have you tested the iwi-driver? > > See: http://damien.bergamini.free.fr/ipw/iwi-freebsd.html > > I haven't yet. Reading that page has brought up another questions. On the > page it says 5-STABLE doesn't support WPA. My wireless network uses WPA. > Is this still the case? I know -stable is -stable, but WPA something of a > show-stopper, if you ask me. > > Fortunately, my neighborhood is a well-covered sea of open "linksys" and > "NETGEAR" APs in default configuration with to test the driver. I'm using driver version 1.3.4 and firmware version 2.2. The driver appears to attach just fine: iwi0: mem 0xdfcfd000-0xdfcfdfff irq 5 at device 3.0 on pci3 iwi0: Ethernet address: 00:0e:35:f6:d6:5c iwi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps iwi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps However, when I attempt to associate and get an IP address, I get "iwi0: fatal error" when running dhclient. Setting debug.iwi=10 and debug.ieee80211=10, I get the following debug output when I run the firmware download and dhclient commands: # iwicontrol iwi0 -d /root/if_iwi/firmware-2.2 -m bss Firmware cached: boot 6464, ucode 16326, main 166952 # dhclient iwi0 INTR!0x0100 INTR!0x0100 Setting MAC address to 00:0e:35:f6:d6:5c TX!CMD!11!6 INTR!0x0800 Configuring adapter TX!CMD!6!20 INTR!0x0800 Setting power mode to 0 TX!CMD!17!4 INTR!0x0800 Setting RTS threshold to 2312 TX!CMD!15!4 INTR!0x0800 Setting .11bg supported rates (12) TX!CMD!22!16 INTR!0x0800 Setting .11a supported rates (8) TX!CMD!22!16 INTR!0x0800 Setting initialization vector to 693451133 TX!CMD!34!4 INTR!0x0800 Enabling adapter TX!CMD!2!0 INTR!0x0800 ieee80211_next_scan: chan 56->60 Start scanning TX!CMD!20!60 INTR!0x0800 INTR!0x0002 Notification (20) INTR!0x0002 Scan channel (36) INTR!0x0002 Scan channel (40) INTR!0x0002 Scan channel (44) INTR!0x0002 Scan channel (48) INTR!0x0002 RX!DATA!68!52!58 ieee80211_recv_mgmt: new probe response on chan 52 (bss chan 52) "191" from 00:0c:db:81:5e:a8 ieee80211_recv_mgmt: caps 0x401 bintval 100 erp 0x0 ieee80211_recv_mgmt: country info 55 53 20 24 04 11 34 04 17 95 05 1e INTR!0x0002 Notification (25) Scan channel (52) INTR!0x0002 RX!DATA!68!56!50 ieee80211_recv_mgmt: new probe response on chan 56 (bss chan 56) "191" from 00:0c:db:81:5e:4a ieee80211_recv_mgmt: caps 0x401 bintval 100 erp 0x0 ieee80211_recv_mgmt: country info 55 53 20 24 04 11 34 04 17 95 05 1e INTR!0x0002 Notification (25) Scan channel (56) INTR!0x0002 Scan channel (60) INTR!0x0002 Scan channel (64) INTR!0x0002 Scan channel (149) INTR!0x0002 Scan channel (153) INTR!0x0002 Scan channel (157) INTR!0x4000 iwi0: fatal error At which point dhclient stalls for several seconds before switching to its background mode. `ifconfig iwi0` then shows "status: no carrier" and no IP address assignment. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: ndis with Intel 2915 wireless, getting "NDIS ERROR" messages and deattach on boot
From: Carl Gustavsson <[EMAIL PROTECTED]> > > Have you tested the iwi-driver? > See: http://damien.bergamini.free.fr/ipw/iwi-freebsd.html I haven't yet. Reading that page has brought up another questions. On the page it says 5-STABLE doesn't support WPA. My wireless network uses WPA. Is this still the case? I know -stable is -stable, but WPA something of a show-stopper, if you ask me. Fortunately, my neighborhood is a well-covered sea of open "linksys" and "NETGEAR" APs in default configuration with to test the driver. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ndis with Intel 2915 wireless, getting "NDIS ERROR" messages and deattach on boot
I'm trying to get my wireless NIC working using the ndis driver, but during boot I get an attach, a stream of what appear to be errors, followed by "device_attach: ndis0 attach returned 6". The basic specs for the configuration are: FreeBSD src: RELENG_5 as of 2005/04/30, about 4pm PDT (-0700) Machine: Dell Inspiron 6000 NIC: Intel PRO/Wireless 2915ABG miniPCI (Dell PCI ID) NDIS drivers: Windows 2000 (NDIS 5.0), driver file is "w29n50.sys" Windows XP (NDIS 5.1), driver file is "w29n51.sys" I could not find non-NT drivers for this NIC. Both drivers produce the following output during boot: ndis0: mem 0xdfcfd000-0xdfcfdfff irq 5 at device 3.0 on pci3 ndis0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xdfcfd000 ndis0: [MPSAFE] ndis0: NDIS API version: ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x2fb ndis0: NDIS ERROR: c00013a7 (unknown error) ndis0: NDIS NUMERRORS: 2 ndis0: argptr: 0x4e4f4c41 ndis0: argptr: 0x191 ndis0: NDIS ERROR: c000138d (unknown error) ndis0: NDIS NUMERRORS: 0 ndis0: init handler failed device_attach: ndis0 attach returned 6 Subsequent boots appear to produce identical data. The dmesg outputs for each driver and the driver files themselves are available upon request. Is this fixed in -current? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Grabbing hold of logged out but active tty
> From: Oren Baum > > I'm running 4.10 and was wondering if there's a trick to > regaining control of another tty session that is still > running (under ps) but I (the user) have been logged out. > This happens to me on occasion when I'm running some programs > in the background and am logged out by the shell. Kill the background processes in question. The tty will be returned to the pool automatically. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 3ware raid
> Hello > > I was wandering if anybody out there has had any success using 3ware > 7506-8 cards with Freebsd 4.10. I was previously using a Promise > controller SX6000, and was having problems with this card. This is something of a FAQ. There's a long list of people using 3ware 6/7/8xxx series cards in FreeBSD 4.x boxes with great success. AFAIK that extends to 5.x as well. The Promise ATA RAID cards just plain suck, IMO. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: How do I change so pcm1 is pcm0 and vice versa?
> From: Jesper Wallin > > Now, I got 2 soundcards, my build-in via82c686 and my > soundblaster live! (emu10k1) .. > Both are compiled into the kernel and I want my soundblaster > live! to be pcm0) and my > via82c686 to be pcm1.. by default, my soundblaster live! is > pcm1 and I can't figure out > how to change this.. Anyone has a clue how to do this? Have only snd_emu10k1 loaded at boot and use an rc script to load snd_via82c686 once the machine goes multi-user. It would be a good idea to do this with both drivers loaded as modules, rather than with the emu10k1 driver compiled in. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4-STABLE and 3Ware 9000 series controllers
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Jason Thomson > Sent: Tuesday, September 21, 2004 9:38 AM > To: [EMAIL PROTECTED] > Subject: Re: 4-STABLE and 3Ware 9000 series controllers > > > We have a one machine with a 9500S-4 controller in RAID 10 > configuration. > > Performance in RAID10 configuration is subjectively no > different to the > 7506-4 in RAID10. (Both cards seem excellent with similar disks - WD > 200GB / 8MB cache drives). We haven't done any systematic testing. > > AFAIK the real advantage for the 9000 series cards is for > RAID5 arrays. > > A few caveats: > > 1. The firmware is included in the driver. The driver will > update the > card's firmware if the driver has more recent firmware than the card. > The firmware that came with the 4-STABLE driver at the beginning of > August was quite old; we had to kldload a more recent driver from the > 3ware website in order to complete the install. > > 2. We haven't been able to get 3dm2 working on this machine. (But the > CLI does work). We haven't spent a huge amount of time on it yet - but > do want to get it working to remotely monitor the array / generate > alerts. I'm not surprised, the version for FreeBSD is a very poor port from a Linux version that uses Linux-style file placement and init scripts. It's sickening to read through. But then this is from the same people whose single "BSD guy" got confused when I asked what value for CPUTYPE was used when compiling the twe module and tw_cli software. Does anyone have a rewritten installer script and/or an rc.subr-style startup script for 3dm2? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Moving from 4.7-STABLE to 5.0
Kevin Oberman wrote: Date: Wed, 08 Jan 2003 15:53:05 -0800 From: Darren Pilgrim <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] Andriy Podanenko wrote: make buildworld make buildkernel reboot with boot -s mergemaster -p make installkernel make installworld reboot mergemaster mergemaster -p make buildworld make kernel KERN_CONF=YOURCONF reboot w/ -s make installworld mergemaster reboot This gets covered over and over and over. And it's usually wrong. The correct command to build a new kernel is make kernel KERNCONF=YOURCONF (or put KERNCONF=YOURCONF into /etc/make.conf and just "make kernel") You're right, I somehow missed that one when I proof read the email. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: FTP installation from the floppies through ADSL modem with PPPoEor PPTP protocol.
Andrew wrote: On Fri, 20 Dec 2002, Asker wrote: The modem can be configured to use PPPoE or PPTP protocol for making the connection with my Internet Servise Provider. Well if the modem does PPPoE itself (and preusmably NAT) then you need no speical support from the OS. From its poitn of view you are just conencted via ethernet. If you need the machine to do PPPoE, ppp supports PPPoE. For this to work, though, you need netgraph, which isn't in GENERIC. You will need to make a custom kernel and build your own set of custom floppies. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: If you shop on the internet, please read this,,, then forward.
Eric wrote: Thank you for reading this. I have been unemployed since mid April, 2002, and things don't look good. I am currently on extended unemployment and it runs out the last of December. You can help me and it won't cost you anything extra. If you use my Home Page to get to the stores you want to shop. I will receive a commission. It cost you nothing to use my site, just go there first, and use the links on it to go to the stores you see there. I have stores like K-Mart, KB toys, Amazon.com, Toys R Us (Part of Amazom.com), Warner Brothers, and on and on. The list grows almost every day. Thanks again for reading this, and please forward this to everyone you know. The more people that see this, the better my chances of paying my bills till I find another job. Thank you, No, thank you. I was bored, so I forwarded a copy of this to the provider of your webpage. BTW, did you know hypervine's ToS states that you may not use their service for commerical purposes without their written permission? Happy Holidays! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: make world considered harmful
Matthew Whelan wrote: > 24/07/2002 14:59:42, Jamie Bowden <[EMAIL PROTECTED]> wrote: > [re-insert from Brian's post] > >:Personally, I think it would be better to remove it; for those who dislike > >:typing and don't mind endangering their system, it would be better to have > >:instead a > >: > >:make universe > > Maybe 'make bravenewworld'? Is there a reason against changing the world target to just be an alias for "make buildworld && make kernel && make installworld && mergemaster"? Forgive me if I'm asking something already answered I haven't been able to follow this entire thread. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message