Re: Reminder: FCP-101: pending removal of some 10/100 Ethernet drivers
On Thu, Jan 31, 2019 at 11:43:44PM +, Brooks Davis wrote: > We are currently planning to remove the following less-popular 10/100 > Ethernet drivers in the March/April timeframe: > > ae, bm, cs, de, dme, ed, ep, ex, fe, pcn, sf, sn, tl, tx, txp, vx, wb, xe > > All of these drivers generate warnings in FreeBSD 12 and to the best of > my knowledge, none have cleared the bar specified in the FCP[0]: > > https://github.com/freebsd/fcp/blob/master/fcp-0101.md Hi, The above document states that the support lifetime for FreeBSD 12 is 2023. The expected EOL (but not decided) for 12 is June 30, 2020 however, according to https://www.freebsd.org/security/security.html#sup So, hardware in some of my machines will only be supported until sometime next year. -- Joel ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
On Thu, Oct 04, 2018 at 12:23:17PM -0600, Warner Losh wrote: > On Thu, Oct 4, 2018 at 12:18 PM Eugene Grosbein wrote: > > > 05.10.2018 0:38, Warner Losh wrote: > > > > > I'd also suggest that rl stands in stark contrast to the cs, wb, sn, smc, > > > sf, tl, tx and vr drivers, which nobody has mentioned in this thread, and > > > which I doubt are in use in any FreeBSD system of any age today. > > > > vr(4) mentioned in the STAY list or else I would be first yelling as > > it is still very common in embedded solutions (including integrated ports > > in my home router). > > > > Sorry, I'd meant to type vx. :) It's for the first generation of 3com cards > after the 3C5x9 ones supported by the ep driver. I mentioned vx. Working fine here: vx0: <3COM 3C590 Etherlink III PCI> port 0x1100-0x111f irq 20 at device 0.0 on pci16 -- Joel ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Recommendation for Hyervisor to host FreeBSD
On 05-07-2012 9:05, Mark Felder wrote: > On Thu, 05 Jul 2012 06:43:06 -0500, Pete French > wrote: > > > So, my work surprise for a Thursday morning is an urgent requirement to > > see if we can run a set of FreeBSD machines under virtualised servers. > > I have not done this before personally, but I notice from post here > > that it doesnt seem uncommon, and I see Xen related commits flowing > > past, so I am guessing it is doable. > > > > So, for running 8 or 9 STABLE can anyone recommend which hypervisor > > works best, and is 8 or 9 better as the OS to run ? Am doing a bit > > of research myself, but nothing beats persoanl experience in these > > matters! > > > > I can't recommend ESX at all. We are struggling to keep our FreeBSD > servers from crashing. I can make them crash on demand just by stressing > I/O and network at the same time. I have a PR regarding the issue, but no > known fix yet. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=168416&cat= This may also be of interest for people looking at VMware ESX: http://forums.freebsd.org/showthread.php?t=31929 -- Joel ___ 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: ATA/Cdrom(?) panic
On 16-11-2011 16:33, Alexander Motin wrote: > On 11/16/11 16:14, Bjoern A. Zeeb wrote: > > On Wed, 16 Nov 2011, Alexander Motin wrote: > > > >> Hi. > >> > >> On 11/16/11 08:43, Bjoern A. Zeeb wrote: > >>> we have seen this or a very similar panic for about 1 year now once in > >>> a while and I think I reported it before; this is FreeBSD as guest on > >>> vmware. Seems it was a double panic this time. Could someone please > >>> see what's going on there?It was on 8.x-STABLE in the past and this > >>> is 8.2-RELEASE-p4. > >> > >> The part of code reporting "completing request directly" is IMHO broken > >> by design. It returns request completion before request will actually be > >> completed by lower levels without any knowledge of what's going on > >> there. There is kind of protection against double request completion, > >> but it looks like not always working. May be because that part of code > >> is not locked and nothing prevents that semaphore timeout and normal > >> request timeout/completion to happen simultaneously. It is surprising to > >> see even two traps same time, not sure what synchronized them so > >> precisely. > >> > >> Simple removing that semaphore timeout is not an option, because it will > >> cause deadlock when this wait happen within taskqueue thread that is > >> used to handle requests completion and abort that wait. Avoid waiting > >> inside taskqueue is also impossible without major rewrite. That's why > >> ATA_CAM drops that code completely. > > > > So the bottom line of what you are saying is: > > 1) it's hard to fix right in 8 > > 2) it's not an issue in 9 anymore at all? > > Right. Hmm. We're running many FreeBSD 8.2 machines as guests in VMware but have never encountered the panic described above. Should I be worried? :-) -- Joel ___ 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: repeating crashes with 8.1
Ok I'll try testing that on some box I can reach with both hands. fyi nagasaki is: [r...@nagasaki ~]# uname -a FreeBSD nagasaki.bogus.com 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #13: Sun May 30 22:19:23 UTC 2010 r...@nagasaki.bogus.com:/usr/obj/usr/src/sys/GENERIC i386 [r...@nagasaki ~]# On 10/22/10 1:17 PM, Randy Bush wrote: >> Do you know how this panic is triggered ? Are you able to >> create it on demand ? > > no i do not. bring server up and it'll happen in half an hour. > and the server was happy for two months. so i am thinking hardware. Perhaps. The reason I ask is that I had a box go down last night with the same set of errors. The box has a number of ipv6 routes, but its next hop was down and the problems started soon after. So I wonder if it has something to do with that. Do you have ipv6 on this box and are all the next hop addresses correct / reachable ? Oct 22 02:06:02 i4 kernel: em1: discard frame w/o packet header Oct 22 02:06:10 i4 kernel: em2: discard frame w/o packet header Oct 22 02:06:21 i4 kernel: em1: discard frame w/o packet header >>> >>> it was co-incident with a border router being taken down for new router >>> install. that router was the v6 exit the servers was using. i have now >>> pointed default6 to a different exit. the server seems happy. >> >> >> Are you servers still up ? I guess the question now is how to >> trigger this problem on demand. Perhaps lots of inbound ipv6 traffic >> with a bad next hop out ? How recent are you sources ? The kernel >> said Oct 21st. Were the sources from then too ? > > yes, kernel and world from 21 oct > > chris had an idea on retrigger, install a static for a small dest that > points to a hole. send a packet to the small dest. > > randy > ___ 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: repeating crashes with 8.1
e...@pci0:13:0:0: class=0x02 card=0x108c15d9 chip=0x108c8086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel Corporation 82573E Gigabit Ethernet Controller (Copper) (82573E)' class = network subclass = ethernet e...@pci0:14:0:0: class=0x02 card=0x109a15d9 chip=0x109a8086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel PRO/1000 PL Network Adaptor (82573L)' class = network subclass = ethernet whole machine is below On 10/21/10 3:51 PM, Randy Bush wrote: >> I need to know which hardware it is and that doesnt show me. > > how do i find out. > >>> em0: port 0x2000-0x201f mem >>> 0xe800-0xe801 irq 16 at device 0.0 on pci13 > > joel, do you know? > > randy > rip.psg.com:/root# pciconf -lv hos...@pci0:0:0:0: class=0x06 card=0x988015d9 chip=0x27788086 rev=0xc0 hdr=0x00 vendor = 'Intel Corporation' device = 'E7230/3000/3010 Processor to I/O Controller' class = bridge subclass = HOST-PCI pc...@pci0:0:1:0: class=0x060400 card=0x988015d9 chip=0x27798086 rev=0xc0 hdr=0x01 vendor = 'Intel Corporation' device = 'E7230/3000/3010 PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:3:0: class=0x060400 card=0x988015d9 chip=0x277a8086 rev=0xc0 hdr=0x01 vendor = 'Intel Corporation' device = '82975X PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:28:0: class=0x060400 card=0x988015d9 chip=0x27d08086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:28:4: class=0x060400 card=0x988015d9 chip=0x27e08086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801GR/GH/GHM (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI pc...@pci0:0:28:5: class=0x060400 card=0x988015d9 chip=0x27e28086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801GR/GH/GHM (ICH7 Family) PCIe Root Port' class = bridge subclass = PCI-PCI uh...@pci0:0:29:0: class=0x0c0300 card=0x988015d9 chip=0x27c88086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uh...@pci0:0:29:1: class=0x0c0300 card=0x988015d9 chip=0x27c98086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uh...@pci0:0:29:2: class=0x0c0300 card=0x988015d9 chip=0x27ca8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB uh...@pci0:0:29:3: class=0x0c0300 card=0x988015d9 chip=0x27cb8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB Universal Host Controller' class = serial bus subclass = USB eh...@pci0:0:29:7: class=0x0c0320 card=0x988015d9 chip=0x27cc8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) USB 2.0 Enhanced Host Controller' class = serial bus subclass = USB pc...@pci0:0:30:0: class=0x060401 card=0x988015d9 chip=0x244e8086 rev=0xe1 hdr=0x01 vendor = 'Intel Corporation' device = '82801 Family (ICH2/3/4/5/6/7/8/9,63xxESB) Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI is...@pci0:0:31:0: class=0x060100 card=0x988015d9 chip=0x27b88086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = 'Intel 82801GB/GR (ICH7 Family) LPC Interface Controller - 27B8 (945GL)' class = bridge subclass = PCI-ISA atap...@pci0:0:31:1:class=0x01018a card=0x988015d9 chip=0x27df8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) Ultra ATA Storage Controller' class = mass storage subclass = ATA atap...@pci0:0:31:2:class=0x01018f card=0x988015d9 chip=0x27c08086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller' class = mass storage subclass = ATA no...@pci0:0:31:3: class=0x0c0500 card=0x988015d9 chip=0x27da8086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation'
Re: Reporting Functional Server Models
On 18-07-2010 12:38, Sean Bruno wrote: > I spent some time last week validating the 7, 8 and -CURRENT on > different vendor hardware over here in my lab. > > Is there a current h/w compatibility list that folks are maintaining > that I can update with my findings? I don't think there is such a list, but posting your findings to this mailing list would probably be a good start... -- Joel ___ 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: RELENG_8 -- shutdown -p no longer powers off boxes
On 22-04-2010 7:35, Jeremy Chadwick wrote: > Looks like some form of regression in RELENG_8, between the dates of > 2010/03/30 and 2010/04/22. My 2010/03/30 kernel (built from RELENG_8 > source dated 2010/03/30 @ 10:30 PDT) doesn't have this problem. > > Symptom: shutdown -p no longer powers off either of my systems; instead, > the box reboots (e.g. shutdown -p behaves like shutdown -r). Systems > are a Supermicro X7SBL-LN2 board, and a Supermicro X7SBA board. These > are server-class boards. I have not tried using the physical power > switch yet. For the record: I have the same problem on at least two boxes, both running 9-CURRENT. -- Joel ___ 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: eeebox and FreeBSD notes
Luigi Rizzo skrev: for what it is worth, i have put some notes on using FreeBSD on the EEE Box. http://info.iet.unipi.it/~luigi/FreeBSD/eeebox.html Most things work, the one big remaining issue is configuring X11 so that it recognises non standard resolutions e.g. 1680x1050 or similar using the "intel" driver. I bought one of these last week but it hasn't arrived yet. Looks like an interesting machine. If you manage to find a xorg.conf that works with the correct resolution and the intel driver, could you add that to your notes as well? -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install issues with 7.x
Ryan skrev: Sadly with the quality of BIOS recently, that is not an option. Not much to offer. Attached is a picture of what I have to change. Other and XP are the same, Vista unlocks AHCI. Another way of accomplishing disabling firewire is to remake the install CD with a different kernel and not quite sure how to do that. Take a look at the release(7) manpage for information about building your own customized release CD. -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Install issues with 7.x
Ryan skrev: Hello, I purchased a new Clevo M860TU on the account that it ran linux very well and was hoping it would fair the same on FreeBSD. Not so much, little help? I posted this in mobile originally but though stable would be a better choice. Don't know if it is more appropriate here or ACPI. I'm giving you as much information as I know how to get. as I cannot get sysinstall to load I am having to type all these dmesg. The boot process is hanging. This is all with 7.x, I can give 6.x if needed. Hardware: Intel P9500 4gb DDR3-1066 Nvidia 9800M GT Atheros AR5006e FreeBSD 7.1-BETA2 These snippets of dmesg happen around the end where it hangs. 1. Default ... cpu0: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0xc6a02d40 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU0._OSC] (Node 0xc68556e0), AE_AML_INTERNAL est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 ACPI Error (dsopcode-0350): No pointer back to NS node in buffer obj 0xc6a0e300 [20070320] ACPI Exception (dswexec-0556): AE_AML_INTERNAL, While resolving operands for [OpcodeName unavailable] [20070320] ACPI Error (psparse-0626): Method parse/execution failed [\_PR_.CPU1._OSC] (Node 0xc685560), AE_AML_INTERNAL est1: on cpu1 p4tcc1: on cpu1 ... cpu0: Cx states changed cpu1: Cx states changed unknown: timeout waiting for read DRQ unknown: timeout waiting for read DRQ acd0: DVDR at ata3-master UDMA33 GEOM_LABEL: Label for provider acd0 is iso9660/FreeBSD_Install run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config Disabling firewire completely in BIOS might at least get the machine booting. You should try that if you haven't already. I've seen this problem on at least two different systems... -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Re: FreeBSD Security Advisory FreeBSD-SA-07:01.jail
Hi Simon,
Thanks very much for the patch :)
On Fri, 27 Jul 2007 11:07:29 +0200, "Simon L. Nielsen" wrote:
>
>Your patch is very close to the "correct"/cleaner patch which is
>attached. How exactly does it fail without your patch? Does it say
>"cannot open : No such file or directory" and then no jails start when
>booting (that would be my guess from a quick check of the bug)?
Sure does:
eval: cannot open : No such file or directory
and no jails start.
>
>Would it be possible for you to test the attached patch and see if it
>fixes the issue for you?
It does indeed. I was actually pretty foolish in the way that I addressed
it, now that I see what your patch does. I was so busy scratching my head
at the variables before the 'while' loop that I didn't see that the problem
was in the ${_fstab} being fed to it on stdin!
>
>I haven't heard of this issue before, so not many people are using 5.5
>with jails. The bug was certainly introduced as a merge error in the
>with the patch for FreeBSD-SA-07:01.jail.
Or maybe they're not patching often enough? Actually, my suspicion is that
not many are using the jail_example_mount_enable variable, because without
this set the responsible code is never called.
>
>As this is clearly a bug in a Security Advisory patch and RELENG_5 /
>RELENG_5_5 are still supported I expect that an updated advisory will
>be released to fix this bug shortly.
>
>Thanks for reporting the issue, and sorry about the bad patch :-(.
No problem! It feels good to help :) I never implement new patches into
my prod environment before testing, so this has basically been an
interesting exercise for me.
cheers,
joel
-- Joel Hatton --
Infrastructure Manager | Hotline: +61 7 3365 4417
AusCERT - Australia's national CERT | Fax: +61 7 3365 7031
The University of Queensland| WWW: www.auscert.org.au
Qld 4072 Australia | Email: [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP: Re: FreeBSD Security Advisory FreeBSD-SA-07:01.jail
Hi,
I'm dredging up an old issue here, but it appears to be unresolved in
RELENG_5_5 at this time. After upgrading to 5.5-RELEASE-p14, I found that
my jails wouldn't start anymore, and it comes down to this bit again. By
way of explanation, I'll include the patch for what I changed.
--- /tmp/jail Wed Feb 14 15:16:30 2007
+++ /etc/rc.d/jail Fri Jul 27 13:46:51 2007
@@ -218,7 +218,7 @@
{
local _device _mountpt _rest
- while read _device _mountpt _rest; do
+ cat ${jail_fstab} | while read _device _mountpt _rest; do
case ":${_device}" in
:#* | :)
continue
In short, the jail_mount_fstab function is not given the fstab file on
which the local variables depend. My patch may not be the most robust but
for me today it is expedient.
Sorry if this has been discussed already, but I was surprised that this
hadn't been fixed yet. It certainly would have caused some anxious moments
if I'd upgraded a prod server with multiple jails before I realised!
cheers,
joel
On Fri, 12 Jan 2007 04:40:59 +0100, Philipp Wuensche wrote:
>Mark Andrews wrote:
>>> I'm not sure I understand that quite correct, where is this problem
>>> appearing?
>>>
>>> Other things:
>>>
>>> tail is used in line 230: tail -r ${_fstab} | while read _device
>>> _mountpt _rest; do
>>>
>>> If the per-jail fstab is larger than 10 lines, which is the default of
>>> tail to show, the remaining mountpoints will not be unmounted?
>>
>> The default for the -r option is to display all of the input.
>
>Ah, didn't know that. Thanks for correcting me there.
>
>greetings,
>philipp
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Installing sendmail SUID installworld suggestion
Hi, When sendmail is set to SUID in /etc/make.conf with SENDMAIL_SET_USER_ID=y, it would be very helpful if installworld could also rename (or, to be consistent with /etc/mail/README, remove) /etc/mail/submit.cf. This is pretty trivial, but I seem to burn myself every time I rebuild a particular system with this option set by forgetting that submit.cf gets recreated during the install. I'm running 5.5R, so I don't know if this behaviour has been modified for later releases. cheers, -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PATCH: new acpi embedded controller I/O model
Mån 2007-02-26 klockan 18:20 -0800 skrev Nate Lawson: > If you are having EC timeout problems as in the below PR, please try the > latest EC code. I just committed it in rev 1.69 of acpi_ec.c to > -current. Thanks for working on this, but my laptop (HP nx7400) shuts down right after boot (or sometimes during boot) after this commit. I see this on the console: acpi_tz3: WARNING - Current temperature (3416.3) exceeds safe limits ... WARNING: System temperature too high, shutting down soon! Everything works fine with an older kernel. -- Joel ___ 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.2-RC1 issues Acer Aspire 5102 WLMi
On Mon, 2006-12-18 at 10:51 +0300, Abdullah Al-Marrie wrote: > 5. RealTek chip High Definition Audio System isn't detected, and > doesn't work for sure. There's a driver for HDA in current. You can grab binary modules for RELENG_6 here: http://people.freebsd.org/~ariff/lowlatency/ -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with the installer sysinstall.
On Thu, 2006-11-02 at 09:02 -0500, Michael Butler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Joel Dahl wrote: > > On Thu, 2006-11-02 at 14:49 +0100, Michel Talon wrote: > >> By the way another minor problem is that the audio does not > >> work. According to the mobo manual, it is a Realtek ALC882 audio chip. > None > >> of the sound modules have recognized the chip. Sound works under Linux. > > > > HDA sound is only supported (by the snd_hda(4) driver) in CURRENT atm. > > > .. or on stable (releng_6) with the mega-patch at > http://people.freebsd.org/~ariff/ The RELENG_6 patch also includes a lot of other stuff (some parts not even committed to CURRENT yet), so beware... -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with the installer sysinstall.
On Thu, 2006-11-02 at 14:49 +0100, Michel Talon wrote: > > By the way another minor problem is that the audio does not > work. According to the mobo manual, it is a Realtek ALC882 audio chip. None > of the sound modules have recognized the chip. Sound works under Linux. HDA sound is only supported (by the snd_hda(4) driver) in CURRENT atm. -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Machine hangs when loading snd_emu10k1
On Sat, 2006-10-14 at 14:39 -0500, Mark Kane wrote: > I can open a PR if needed, but I don't really have any data or > debugging info (no errors on the screen, or in /var/log/messages). I > only know that after the system was up since the last rebuild and I > rebooted it yesterday, the system hangs indefinitely upon loading the > snd_emu10k1 module even though I had not changed any system > configuration in that time. I did have a new world/kernel built before > yesterday's reboot, but not installed. So, loading snd_emu10k1 worked before the last rebuild? Could you perhaps do a binary search and try to narrow it down to a specific commit? -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Showstopper - 6.2-PRERELEASE does not see SATA DVD drives (fwd)
On Wed, 2006-09-27 at 17:31 -0400, Frank wrote: > On Wed, 27 Sep 2006, Mike Jakubik wrote: > > > Frank wrote: > >> I am sending this again since it has been 4 days with no response. > >> > >> I consider this a showstopper since I could boot from CD but sysinstall > >> could not see the DVD drives, thus no CD install. I had to mount the CD > >> in > >> another machine and do a NFS install. > > > > SATA optical drives are not supported, neither is your brand new gaming > > sound > > card. This is far from being a show stopper. Please consult the hardware > > notes in the future before complaining on the lists. > > The Hardware Notes do not mention SATA at all except for RAID controllers. Just FYI, We've been looking at integrating the supported hardware info from the ata(4) manual page into the hardware notes. This *should* at least kill some of the confusion that always surrounds what SATA/ATA stuff we support and what we don't. -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sound card
On Thu, 2006-09-07 at 20:39 +0600, S. M. Ibrahim (Lavlu) wrote: > thanks working, though the volume manager is not in my control :( , waiting > for the driver from freeBSD team :) A new HDA driver (snd_hda(4)) has been announced on the multimedia@ list just a few days ago. Check the archives. -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hp or Toshiba laptop?
On Thu, 2006-09-07 at 08:38 -0400, Christian Lopez de Castilla Wagner wrote: > Hi guys, > I'm looking into buying a new laptop in the next week, > due to budget, time and the fact that I'm near the end of civilization > right now, > I have the following choices: > Toshiba Tecra A6-SP3032 (Core Duo 1.83GHz, Intel PRO/Wireless 3945ABG > (802.11a/b/g), Intel PRO/1000 VE 10/100/1000 Base-TX, FastIR, Intel > GMA950, Realtek ALC861 Audio, 5-in-1 cardreader, FireWire) > or > hp nx6320 (Same specs, except Broadcom NetLink Gig-Ethernet (BCM5788M) > and ADI1981HD audio, no cardreader). I'd go for the HP. I bought a HP nx7400 2 weeks ago (which has similar specs) and everything except sound and the wireless stuff seems to work. A Beta driver for the sound exists and it works well on my laptop, but it hasn't been committed to current yet. Dunno about the status of wireless support, but I heard rumors about a port of the wpi(4) driver from OpenBSD. -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0-Release sysinstall panic.
On Wed, 2006-02-08 at 19:57 +0100, Tanel Rebane wrote: > Hello! > > I'm trying to install FBSD 6.0-Release on one of my servers. The > server, with the same hardware, has been running FBSD 5.4-Stable just > fine. The problem is that every time I try to install FBSD 6.0- > Release the system crashes when trying to extract base into /, the > crashes seem to occur at random point into the progress. > > I've tried as much as I can think of, as disabling the onboard USB, > IEEE1394, LAN, audio and FDD from BIOS. I've also tried to boot > without support for ACPI and underclocked the Athlon XP-M 2600+ to > 800MHz to minimize any hardware faults. The system should be stable > as it has no problem running both prime and memtest86 without faults > for 7+ days. Have you tried the latest snapshots of 6.0-STABLE? ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/Jan_2006/ -- Joel - joel at FreeBSD dot org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> Joel Hatton wrote: > > What was the rationale behind changing this behaviour for 206_1? > > That xterm should install as xterm and not xterm-static. This is certainly sensible, however it appears that the onus has now been put on the maintainer of xorg-clients to change its installation process to accommodate xterm. This hasn't happened yet (after cvsup this morning), which means that xterm remains incompatible with the current xorg-clients version and thus will fail during every portupgrade -a until then, unless I make xterm a held package. According to UPDATING, upgrading "xorg-clients to 6.8.2_1 or newer" is ok, but this is not the case: # pkg_info -I xorg-clients\* xorg-clients-6.8.2_1 X client programs and related files from X.Org # portupgrade -p xterm ... (building) ---> Installing the new version via the port ===> Installing for xterm-206_1 ===> xterm-206_1 conflicts with installed package(s): xorg-clients-6.8.2 They install files into the same place. Please remove them first with pkg_delete(1). Couldn't this transition have been better managed? cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cvsup flags in /usr/src/Makefile.inc1 outdated?
Hi, I've just noticed that cvsup flags in my RELENG_6 Makefile.inc1 are still: SUPFLAGS?= -g -L 2 -P - But, from man CVSUP(1): -P m|a|port|lo-hi|- Controls the establishment of the auxiliary TCP connection(s) used to carry information between the client and the server. Altogether, the client and server require four unidirectional channels to communicate: two from the client to the server, and two from the server to the client. These four unidirec- tional channels can be set up in different ways, to support various firewall setups. The modes provided for this are multiplexed mode, passive mode, and active mode. All but ^^^ multiplexed mode are deprecated. Multiplexed mode can handle any situation that the other modes can handle. This means that if I don't specify any overrides in /etc/make.conf or my supfile, running 'make update' in /usr/src will cause cvsup to try to use passive mode and, in my firewalled environment, fail. Yep, I found this out by accident :) regards, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xorg-clients conflicts with xterm (patch)
> > xterm-206_1 Terminal emulator for the X Window System > xorg-clients-6.8.2_1 X client programs and related files from X.Org > > then, portupgrade -fp xterm xorg-clients > ... > ===> Installing for xterm-206_1 > > ===> xterm-206_1 conflicts with installed package(s): > xorg-clients-6.8.2 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > On this note, I generated the same error trying to install xterm-206_1 _after_ deinstalling xorg-clients-6.8.2_1. >From Updating: 20051113: AFFECTS: users of x11/xterm, x11/xorg-clients, x11/XFree86-4-clients AUTHOR: [EMAIL PROTECTED] Xterm no longer installs with '-static' prefix. Users should upgrade XFree86-clients to 4.5.0_1 or xorg-clients to 6.8.2_1 or newer before attempting upgrade of xterm to 206_1 or newer. Previous versions remove xterm on deinstall so CONFLICTS have been set accordingly. What was the rationale behind changing this behaviour for 206_1? cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.x, 6.x and CPUTYPE
> > I always build my production servers with CPUTYPE=i686 so they can be > transplanted to any machine with a PPro or better processor (or even > qemu if necessary). Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this method. Do you know of any particular disadvantages of continuing with this less-than-optimised model - I guess I mean, is this something that is likely to break or become uneconomical at some point? cheers, joel -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
5.x, 6.x and CPUTYPE
Hi, I've noticed that some CPU definitions have changed in /etc/make.conf between 5 and 6. For good or for bad, I have up until now been building 5.x for both p3 and p4 architectures with 'i686' but this particular definition's removal from 6.x has given me cause to rethink my strategy. I'd like to know: Should I use 'i386' and build once for all, or use p3/p4 defs and build once for each? And if the latter, why? (does this give any worthwhile performance increase?) If I don't specify a CPUTYPE at all, will this be auto-detected in some way (which would probably not suit me) or will it fall back to i386? Is this a consistent requirement for world/kernel/ports? Finally, when building on a single host, but where multiple requirements are being met, is it possible to define different make.conf files for make or is it easier to just edit this file before each build? thanks, joel -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments))
> Ah, that's they key. aliases don't work with dhclient at the moment for > most interfaces because the interfaces generate bogus link events when > aliases are modified. We hope to fix this, but it's going to take some > time. Ok - thanks. I'm fortunate at the moment that I've stopped using the jail I had on that particular machine. Even though this is a somewhat unusual situation (ie dhcp + jail alias) I don't suppose there's any move to in the mean time incorporate a 'DHCLIENT=' make option for ISC/OpenBSD versions? ;) joel -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.0 RC1 dhclient (was Re: 6.0 RC1 usbd.conf (and installation comments))
I said: > > DHCP configuration - for some reason my machine didn't acquire a > default route on boot, but rerunning the dhclient script after > boot caused the interface to be set up again successfully. I > haven't looked into this further yet, I'll repost if it is a > repeatable problem. This issue is repeatable. Although I haven't had time to trace it further, I have worked out that if I configure my dhcp interface with an alias eg ifconfig_em0_alias0 a default route is not added; after commenting that line in /etc/rc.conf the route is ok again on reboot. I've tried alternating between commented/uncommented with consistent success/fail results so I guess this needs looking at. joel -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
6.0 RC1 usbd.conf (and installation comments)
Hi, I've just overnight upgraded from 5 stable to 6 on one of my workstations. As I'm becoming used to expecting, this was a very smooth migration - my perennial thanks to all of the developers who make this type of operation almost trivial. A couple of notes on the extremely few 'gotchas' I experienced - I should quickly add that none of these are in any way serious: most files in /etc/rc.d changed, so installing them all with mergemaster was laborious - a note in UPDATING similar to that for 5.x: "The simplest solution is an 'rm -rf /etc/rc.d/*' and then 'mergemaster -i'." would have reminded me to do just that and saved about 10 minutes of clicking 'q', then 'i' :) I did, in this case, run mergemaster -i, but didn't think to do the above. On this note, I still can't work out how to use the edit-merge part of mergemaster properly, but it is certainly a pebkac issue. /etc/usbd.conf has lost the [Device] configuration for the mouse, which although doesn't prevent the mouse from working, it did mean that I had to add those lines again so that I could turn on '-z 4' for the scroll wheel. If this was the wrong way to do it, let me know - adding this item to the moused_flags didn't work. I'm actually wondering if this shouldn't be the default nowadays - what standard usb mouse _doesn't_ have one? DHCP configuration - for some reason my machine didn't acquire a default route on boot, but rerunning the dhclient script after boot caused the interface to be set up again successfully. I haven't looked into this further yet, I'll repost if it is a repeatable problem. I rebuilt all of my ports afterwards (with portupgrade -af), with no failures, and everything so far appears to be working fine. cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
On 平成 17/10/18, at 13:05, Mike Jakubik wrote: On Mon, October 17, 2005 11:56 pm, Brett Glass wrote: Features=0x178bfbff,PG E,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT> Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x3 Multicore: 2 physical cores How come the kernel is reporting that an AMD chip has HTT? Is this a bug? No, this is how dual core is reported. Huh? Don't scare me like that, Mike. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 6.0 release date and stability
On 平成 17/10/18, at 17:21, Pertti Kosunen wrote: Brett Glass wrote: How come the kernel is reporting that an AMD chip has HTT? Is this a bug? It is the AMD HyperTransport™ Technology, not Hyper Threading as Intels have. http://www.amd.com/us-en/Processors/DevelopWithAMD/ 0,,30_2252_2353,00.html Whew. That's a relief. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Infra-red in FreeBSD... Remote control in XMMS... LIRC ??
I wrote a simple python program that interfaces directly with /dev/ugen0.1 to work with the usb rf ati remote wonder plus. Rather then interfacing through lircd, I just output stuff in the format that lircd uses so that programs like mplayer just work. The format is something like: hexcode repeat-count keybinding configfile or: '0040151f0a00 00 MUTE /home/jwood/remotewonderplus.conf\n' '0040151f0a00 01 MUTE /home/jwood/remotewonderplus.conf\n' '0040151f0a00 02 MUTE /home/jwood/remotewonderplus.conf\n' '0040151f0a00 03 MUTE /home/jwood/remotewonderplus.conf\n' if I were to hold the mute key down. If anyone would like the code, reply to me off list, as I am not on the list. -Joel On Tue, 27 Sep 2005, Oleg Korecky wrote: Did somebody use LIRC on the FreeBSD ? Or what you can recommend instead LIRC ? Thanks ! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ep0 Interrupt Storm, 3Com EtherLink III (PnP)
8809MB [17898/16/63] at ata0-master WDMA2 ad2: 2014MB [4092/16/63] at ata1-master WDMA2 acd0: DVDROM at ata1-slave PIO4 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s1a ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable- [EMAIL PROTECTED]" Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange case of root filesystem corruption
On 平成 17/09/19, at 5:32, Ulf Magnusson wrote: Some more info: Windows is installed on the same drive. When I launched Partition Magic it complained about the LBA and CHS parameters for a partition on the drive not being identical. Just in case it's helpful.. FWIW, I've had bad luck with using Partition Magic more than two or three times on a drive. I just don't even use it any more. Also, I've had bad luck using MSW-side software to do anything with the partitions after *BSD partitions are cut. MSWindows can't seem to obey its own rules. If you have to dual-boot, cut the primary (BIOS-level) partitions once with MSW (and PM, if you must), then leave the BIOS-level partitions alone. Better yet, use two drives. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ 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.
On 平成 17/08/29, at 12:30, C. Michailidis wrote: [...] I understand that the automatically generated values by sysinstall are the "dumbest" settings you can ask for... but auto-allocating a maximum of 256mb for the root, var, and tmp filesystems (even if you have an incredibly large slice in the 100's of GB) seems to be BEYOND dumb. Perhaps I've just pointed out that I am, in fact, beyond dumb, lol! ;-) Anyway, If it's simply a matter of not having enough programming resources, I'd be more than happy to make the changes to sysinstall and offer the unified diffs. Just let me know your thoughts so that the changes may be relevant for all users. I can sympathize. I've been caught by bad partition sizes. But I never take the default sizes. In particular, I check the size of /var and its sub-partitions carefully. (Seems like nobody uses / tmp that heavily anymore, but /var/tmp gets hit a lot, and /var/log may need to be relatively huge, depending on what the system is doing, etc.) A partition "wizard" (I hate that term, but you know what I mean.) that would coach new users and remind old users about the effects of freeBSD layout on partition sizes would, I'm sure, be welcome, if you want to take the trouble. Mind you, simple ruled apportionment would not be sufficient. We would like to have sets of rules, one for a pure web server, one for a basic home-user websurfing, e-mailing, letter-writing coffee-table-top, several for different kinds of firewalls and bridges, ... And what about older disks, where cylinder sizes, number of reported heads, etc. were meaningful? No, that's probably not relevant except for RAIDs. (As long as I'm making demands on your time, why not think big? ;^) Anyway, it could be a useful project, but you'll want to recognize there's a lot of stuff hiding under the surface there. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[NNOT] Stability on Soekris class h/w? (was Re: 6.0-BETA2 as reliable webserver?)
On 平成 17/08/20, at 13:24, Peter Jeremy wrote: On Fri, 2005-Aug-19 23:42:18 +0200, Frans-Jan v. Steenbeek wrote: building. Since we are moving in a few months, we decided to use a HP laptop instead (reasonably fast CPU, 512 Megs) since we had a few to spare. The toy is currently set up with FreeBSD 6.0-BETA2, Apache 2.0, MySQL 5.0 and PHP-5.0 with all the reasonable modules. Everything is compiled from ports. No changes to the kernel yet, no world-rebuilding done. I'd also be extremely loath to bet my company on a laptop running beta software. As others have pointed out, laptops aren't designed for this. (Though my old Compaq laptop ran FreeBSD 24x7 for several years and I only stopped using it because the lid was cracking too badly). Yeah, I've had my home server running on an old iBook (not FreeBSD). I had replaced the original disk with a larger used one because the original was just 6GB. The used disk lasted only a year. Had to open it back up and put the 6GB drive back in until I can afford a new disk (or a Mac Mini). I need to add RAM to that poor child, too. That said, 512 MB RAM in the HP notebook might leave enough RAM for a RAM disk. One could mirror Apache, PHP, MySQL (app, not DB), libraries, and the web app itself onto a RAM disk. That way the server could respond to initial hits out of the RAM disk while the HD is spinning up. If you're really concerned about noise: - use an older desktop and maybe even underclock it to keep it cooler - build your own system. Either go the low power route (mini-ITX) so you don't need noisy fans or use an over-rated PSU and CPU heatsink to keep fan speed (and noise) down. In either case, you'll need to look around to find a quiet HDD. So, what's the stability of FreeBSD 5.x/6.x on Soekris class hardware? I'm thinking especially in terms of mulit-port nics that would support bridging, etc. - [as a completely left-field suggestion] look at something like an Apple G5 system - large fans running slowly generate very little noise. Maybe even Mac Mini? ;-> fbsd on PPC is still not even close to stable, and the iNTEL Macs are still at least ten months away. But openBSD and netBSD run rather well on PPC if the eye candy of Mac OS X is unpleasant or the cost of Mac OS X Server (for a little added peace of mind?) is uncomfortable. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
I have two which reliably fail if you put TWO disks on them in a gmirror config within minutes of starting a "make buildworld". Pardon the interruption, but is this two drives on one channel? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ad10: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=11441599
On 平成 17/08/10, at 7:36, O. Hartmann wrote: [...] When is SCSI back for desktops? I vote for that. In my opinion, ATA is primarily for home media systems, if that. Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB umass device errors and successes
da0: 1.000MB/s transfers Jul 29 09:37:07 P4Machine kernel: da0: 124MB (253952 512 byte sectors: 64H 32S/T 124C) (branded: Shintaro, but this time 256mb) Jul 29 12:37:55 P4Machine kernel: umass0: at uhub2 port 2 (addr 2) disconnected Jul 29 12:37:55 P4Machine kernel: (da0:umass-sim0:0:0:0): lost device Jul 29 12:37:55 P4Machine kernel: (da0:umass-sim0:0:0:0): removing device entry Jul 29 12:37:55 P4Machine kernel: umass0: detached Jul 29 12:38:02 P4Machine kernel: uhub4: Prolific Technology Inc. USB Embedded Hub, class 9/0, rev 2.00/1.00, addr 2 Jul 29 12:38:02 P4Machine kernel: uhub4: 1 port with 0 removable, self powered Jul 29 12:38:03 P4Machine kernel: umass0: Prolific Technology Inc. USB Mass Storage Device, rev 2.00/1.00, addr 3 Jul 29 12:38:03 P4Machine kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jul 29 12:38:03 P4Machine kernel: da0: Removable Direct Access SCSI-0 device Jul 29 12:38:03 P4Machine kernel: da0: 1.000MB/s transfers Jul 29 12:38:03 P4Machine kernel: da0: 248MB (507904 512 byte sectors: 64H 32S/T 248C) (branded: MyFlash) Jul 27 10:24:42 P4Machine kernel: umass0: USBest Technology USB Mass Storage Device, rev 2.00/1.00, addr 2 Jul 27 10:24:42 P4Machine kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jul 27 10:24:42 P4Machine kernel: da0: Removable Direct Access SCSI-2 device Jul 27 10:24:42 P4Machine kernel: da0: 1.000MB/s transfers Jul 27 10:24:42 P4Machine kernel: da0: 992MB (2031616 512 byte sectors: 64H 32S/T 992C) (branded: no brand, but cute Christmas logo and packaged in what appears to be a rubber case) Jul 27 10:31:20 P4Machine kernel: umass1: USBest Technology USB Mass Storage Device, rev 2.00/1.00, addr 2 Jul 27 10:31:20 P4Machine kernel: da1 at umass-sim1 bus 1 target 0 lun 0 Jul 27 10:31:20 P4Machine kernel: da1: Removable Direct Access SCSI-2 device Jul 27 10:31:20 P4Machine kernel: da1: 1.000MB/s transfers Jul 27 10:31:20 P4Machine kernel: da1: 125MB (256000 512 byte sectors: 64H 32S/T 125C) I hope all this is helpful! -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dangerous situation with shutdown process
Comment from out in left field -- On 2005/07/16, at 6:03, Kevin Oberman wrote: [...] I believe that the Windows solution to this problem is to put a really, really long delay between when the system is finished syncing and when the power is turned off. That's what I vote for. If the system has ATA on it, send a line to the console that says waiting for ATA technology drives to quit lying after the final sync, and then wait 30 seconds to cut power. This might be the best solution for FreeBSD, as well, but it will irritate people. My impression is that in this case irritation is recommended. (I'm half wondering if Microsoft and the drive manufacturer's haven't defined some hidden API for forcing the drive electronics to be truthful.) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Two Options: which to choose?
On Thu, 30 Jun 2005 17:07:59 -0400 (EDT) Matt Juszczak <[EMAIL PROTECTED]> wrote > [...] > Therefore, part of me is thinking of switching back to either 4.11 or to > OBSD 3.7. Problem is, this switch wouldn't be temporary, it would have to > be permanant. I couldn't set things up now and then move them again a > month from now. If you're wanting the system to be untouched for two years, set openbsd aside. If you don't understand what I mean, read their FAQ again and hunt up their support policy and read carefully the instructions on security patches and on updates and upgrades. OpenBSD is a great OS, and I recommend learning it and using it, but the pace is pretty stiff, especially until you get used to it. -- Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: SATA vs SCSI ...
On Mon, 27 Jun 2005 10:13:04 +0400 "Artem Kuchin" <[EMAIL PROTECTED]> wrote > Marc G. Fournier <[EMAIL PROTECTED]> wrote: > > looking at the specs between two cards, the SATA card(s) seem to rate > > ~100-150MB/s on each channel (if I'm reading right), with both the > > 3Ware and ICP cards having 4 individual channels ... looking at the > > SCSI cards, they are rated at 320MB/s, but that is total for the SCSI > > bus itself, right? > > > > So, if I have three drives on a SCSI bus, each 'maxing out evenly', > > I'd be cap'd at about the same 100MB/s per drive, no? > > > > In fact, looking at the SATA 2.x specs, each chanell there is rated at > > 300MB/s, which, again, if I could 'max out evenly', could seriously > > blow away the SCSI bus itself ... > > > > *If* I'm reading this right ... ? > > For the last 6 month i really think that if you don't need something high-end > scsi then you should go for SATA. There are test on sites such as > Tom's hardware guide and ixbt.com. I'm always pretty cautious about how much trust I give those benchmarks done by fanboy sites. Interesting stuff, but if it's mission critical and benchmark is important, I'm going to design and run the benchmark myself. And I'll cost that in when I give the estimate to the customer, if the customer wants SATA. (I think of a recent benchmark of Mac OS X/PPC and MySQL and nobody mentioning sync issues in the benchmark article.) > They show then on sequrncial read > there is no difference between scsi and sata. Acatuallty, modern hdds use > the same mechanics for sata and scsi versions of them. The brains > (electronics) > on the hdds are different of course. However, when it comes to random > read/writes > scsi wins because of command queueing. This was an issue until recently, > Recently SATA with NCQ became widly available. Test show that some of those > SATA disks with NCW ***WIN*** over scsi 320. The test envolve artificialy > random > read/write tests as well as real application benchmarking. I din't rememeber > where > excatly i saw the tests on those site, but you could search. Well, I've been fighting on and off for about four weeks with an ATAPI drive with SMART reporting bad sectors, and I'll offer this: when you cost an ATAPI/SATA hard drive, make sure you factor in the cost of backup/mirror. Considering the business about Mac OS X and MySQL and sync, I'd factor in UPS as well. Make sure you set it up to start taking the system down long enough before the battery gives out that the drives have plenty of time to clear their internal cache. > So, my opinion, workstation never needs SCSI and every server MUST be > on mirror or RAID5 and there you should use SATA with NCQ drivers unless, > your applicaton is really weird and needs something extremely speedy. Then, > however, > you could go for RAID 0+1 and get perfomance that SCSI will never get you. Now that I have a bad taste in my mouth from SMART, I'm interpreting that as "three SATA drives in RAID5 equals one SCSI drive". Contrary to what you expect, I do not expect performance from that. -- Joel Rees <[EMAIL PROTECTED]> digitcom, inc. 株式会社デジコム Kobe, Japan +81-78-672-8800 ** <http://www.ddcom.co.jp> ** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lifetime of FreeBSD branches
Random comment from the peanut gallery, but ... (B (B> >> Thanks for the info guys. Does this "security support" also mean that (B> >> current ports will be compatible with the release? (B> > (B> > No, there are no guarantees about that. The ports/ people generally (B> > try to make things work with older releases, but there are no gurantees (B> > there. It's simply too much work to make such guarantees, and this is (B> > after all an volunteer project (for most parts anyway). See also (B> > http://www.freebsd.org/ports/ for the "official" statement. (B> (B> Right, i didnt think so. Debian is a volunteer project too, and their (B> packaging system supports all of their branches. I guess i should look (B> into rolling my own packages, to be sure. And yes, i realize that we just (B> dont have an infrastructure for something like this. (B (BI'm thinking that, if a company really doesn't have the infrastructure, (Bthere are several good options. You mention Linux. MacOSX is closer to (Bthe BSDs than Linux in many ways, tends to have relatively long-term (Bstability, and you can pay Apple for a rather high level of support if (Byou join their developer's program. (B (BThe best option, however, may be to invest in the infrastructure -- a (Blong term relationship with a qualified contractor, or even an employee (Bwhose primary duty would be to (learn how to) do the heavy lifting on (Bbackporting and upgrading. That way, the OS itself becomes more a part (Bof the company's resources. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB changes.
On Thu, 28 Apr 2005 13:51:37 -0700 (BJulian Elischer <[EMAIL PROTECTED]> wrote (B (B> (B> (B> Joe Altman wrote: (B> (B> >On Thu, Apr 28, 2005 at 01:40:50PM -0700, Julian Elischer wrote: (B> > (B> > (B> >>Since I can't make this happen here, I'm going to need help.. (B> >> (B> >> (B> > (B> >What do you need? Relatively speaking, I'm sort of a newbie at the (B> >more complex aspects of bugs, and this strikes me as somewhat complex. (B> > (B> >But if you are willing to tell me what you need, and how to proceed or (B> >what to read to help you, I'll do what I can. (B> > (B> > (B> (B> I asked you to add 2 lines to that file and try again. (B (BIf I were Joe, I'd be wondering if that meant re-compiling the kernel. (B (BDid this go anywhere? (I also have UHB hardware that fusses on boot.) (B (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Misleading security message output
> > The first question that comes to mind: do you really need logs from a (B> > year back? (B> (B> Nope. Should I need to tweak the default config files to ensure (B> that I dont get them? (B (BSince that's the element that brings three possible mis-features (Btogether in the unfortunate interaction, and is also the element that (Byou have the most direct and immediate control over, and also should not (Bbe a difficult fix, I would sure see it as the tempting fix. (B (BI think I'd also want to submit a feature request to whoever is (Bcurrently claiming the program that generates the logs. (B (B> > Maybe it's because I'm such a newb, but I'm wondering which program has (B> > what bug? Is it that the default configuration files for the login logs (B> > doesn't put on age limit on the rotation? Is it that the log lines don't (B> > conain a full 4-digit year in the timestamp? Or is it that the (B> > logscraper doesn't know to check the age of a log file, or doesn't know (B> > to work on the tail of the log? (B> (B> The bug is in the security logscraper script, because it (B> presented a log entry from a year ago as something that happened (B> yesterday. (B (BThe way I see it, that's less where the bug is and more where the bugs (Bshow up. (B (B> The proximate cause of the bug is that the log (B> files don't contain a year as part of the date format. The (B> easy work-around is to include timed rotation as part of the (B> standard configuration so that the lack of a year in the logfile (B> date format does not expose the bug in the script. There are (B> two plausible "real fixes" for the bug: 1) use a backup+diff (B> scheme to find "yesterday's log messgaes" -- this is what NetBSD (B> does, or 2) change the syslog daemon to include the year in the (B> logfile date stamp -- this is what daemontools' multilog does. (B> Option 2 is likely to be difficult to roll into the standard (B> because it would almost certainly break third-party logfile (B> scrapers. (B (BI'm thinking that the logscrapers are likely not to be going to the (Btrouble of grabbing only two digits out of the year field, but I (Bprobably don't see as much code as you do. (B (BI see I'm preaching to the choir, and that we just have different points (Bof view about how deep you want to reach into freeBSD to fix your bug. (B (B:) (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Misleading security message output
I'm just a newb, but (B (B> > > I had an interesting experience, this morning. The nightly (B> > > security message from a CVS server machine that runs a version (B> > > of FreeBSD-4 had arrived, and it claimed that someone who hadn't (B> > > done any work for us for some considerable time had had three (B> > > failed login attempts, late that night. Curious. (B> > > (B> > > After much hunting around, and checking perimeter logs, it (B> > > turned out that nothing of the sort had happened. The security (B> > > log script had been fooled by the age of the messages.0.gz file, (B> > > which contained messages from more than a year ago. (B (BThe first question that comes to mind: do you really need logs from a (Byear back? (B (BEven though you say the server hardly ever needs touching, it seems to (Bme that general backup principles would say that if you need logs that (Bold, you would have your automatic backup sript gleaning the old logs at (Bone to three months, putting the old logs on some backup medium and (Bdeleting them from the server. (B (B> > > The search (B> > > pattern "$yesterday" doesn't contain a year, because log file (B> > > timestamps don't contain years. The log file was so old because (B> > > rotation is determined by size, and this machine simply doesn't (B> > > have much to log, despite being used daily. It never goes down, (B> > > and is basically completely stable. (B (BSomething seems upside down here. Maybe it's just the way I'm reading it. (B (BAnyway, as Joshua pointed out, you can combine conditions: (B (B> > Well, you could modify /etc/newsyslog.conf, where it says: (B> > (B> > /var/log/messages 600 14100 * J (B> > (B> > change it to: (B> > (B> > /var/log/messages 600 14*@T00 J (B> > (B> > This assumes you want 14 message logs, rotated once a day at midnight. (B> > Any message logs over 14 days will be deleted. (B> > (B> > man newsyslog.conf (B> > (B> > > This could be avoided, perhaps, with a NetBSD-style backup/diff (B> > > mechanism, or (incompatibly) with daemontools/multilog-style (B> > > 64-bit time stamps in the log files. It can be worked-around (B> > > by forcing faster log-file rotations, now that I know about (B> > > the problem. I can't think of a really good widely-applicable (B> > > solution, using the existing framework, though. (B> > (B> > I'm not quite sure what you mean. Do you want a way to have the (B> > timestamp record the year as well, so that you can keep the default (B> > setting? (B> (B> That'd be one way to do it. Multilog, in the daemontools (B> package gives log messages a timestamp that (implicitly) (B> includes the date. The NetBSD method, of keeping a "yesterday" (B> backup of the log files, and diffing against the "now" versions (B> avoids the problem by making the search for "stuff that happened (B> since the last log e-mail" explicit. I don't much mind how the (B> bug is fixed. It would be nice, I think, if the bug fix didn't (B> amount to a documentation addition along the lines of "in order (B> for the nightly security messages to work properly, you must (B> tune the log-file rotation period so that log files are rotated (B> at least once per year. See newsyslog.conf(5)." (B> (B> A reasonable bug-fix could be to add a when value of $ML to the (B> /var/log/messages line of the default /etc/newsyslog.conf. On (B> most machines that will have no effect, because rotation will (B> still be triggered by the size field. It will just make the (B> logic in the nightly security script correct. (B (BMaybe it's because I'm such a newb, but I'm wondering which program has (Bwhat bug? Is it that the default configuration files for the login logs (Bdoesn't put on age limit on the rotation? Is it that the log lines don't (Bconain a full 4-digit year in the timestamp? Or is it that the (Blogscraper doesn't know to check the age of a log file, or doesn't know (Bto work on the tail of the log? (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
merging locale stuff in mtree?
Just finished rebuilding and installing the world and the kernel by the (B"canonical" method. (B (BIn using mergemaster, I find myself puzzled by the locale stuff in mtree. (BI have not installed a lot of locales, haven't even started X11 at all (Byet, but the updates seem to want to put a lot of stuff about locales in (BBSD.X11-4.dist and BSD.local.dist. Is all that locale stuff necessary (Bthere if you haven't installed all those locales? (B (B(I tried to merge BSD.local.dist, and I think I botched it.) (B (BI'm not really clear on what mtree does, in case that isn't obvious. (BSearch the web only turned up stuff about an alternative to tripwire, (Bbut I suppose it might be mergemaster's db configuration? (Scanned man (Bon mtree and /usr/src/etc/mtree/README, but it hasn't sunk it yet.) (B (BAppreciate a cluestick if anyone cares to hit me with one. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 broken?
> > > FWIW, you are just in time anyway because they added a security (B> > > notice and if you cvsup now, you will also get that fix. (B (BAnd it's nice to have that out of the way. (B (B> > So the system is not in an unstable situation such that repeating the (B> > cvsup would have me trying to build from inconsistent libraries or (B> > anything like that? (B> (B> When you do the buildworld, you get a new world and then the kernel will (B> build. This is one of the reasons to buildworld, buildkernel, and (B> install kernel. (B (BI'm just a following the instructions in the on-line manual. Well, (BI used sudo from the main admin account while in multi-user mode, except (BI forgot that a couple of times and had to break out. And I forgot to (Bgrab it at the beastie menu on the reboot just now, but it seems to be (Binstalling world okay after a second reboot to single-user. (B (B> Since the buildkernel died, your libraries haven't been (B> updated. You wouldn't do that until after you have booted the new (B> kernel in single user mode. The sequence may be awkward at times but it (B> saves you from the little disasters :). (B (BNo problem with that. Just wanted to make sure the libraries would not (Bbe in a half-way state from not having completed the previous build. (B (B> > What the heck, I'll take a backup and give it a spin. (B> (B> Just remember you build and install the world and the kernel. I just got (B> through upgrading to get the ifconf fix. No, problem. (B> (B> Kent (B (BThanks again. It just finished the install, so I'll see what happens in (Bthe second pass of mergemaster (That looks like it could be a very (Buseful tool.) and then build ports. (B (BI guess it's obvious I haven't done this very much on freeBSD. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 broken?
On Thu, 14 Apr 2005 22:32:42 -0700 (BKent Stewart <[EMAIL PROTECTED]> wrote (B (B> On Thursday 14 April 2005 09:23 pm, Joel wrote: (B> > On Thu, 14 Apr 2005 11:20:54 -0700 (B> > Nate Lawson <[EMAIL PROTECTED]> wrote (B> > (B> > > Jon Noack wrote: (B> > > > On 4/14/2005 8:28 AM, David Wolfskill wrote: (B> > > >> On Thu, Apr 14, 2005 at 01:26:17PM +0200, Jose M Rodriguez wrote: (B> > > >>> Anyone seen this? (B> > > >> (B> > > >> [... (B> > > >> /usr/src/sys/kern/subr_bus.c:1082: warning: no previous (B> > > >> prototype for 'devclass_get_drivers' (B> > > >> *** Error code 1 (B> > > >> ... (B> > > >> ] (B> > > >> (B> > > >> Yup; just a few minutes ago, with sys/kern/subr_bus.c rev. (B> > > >> 1.156.2.6. (B> > > >> (B> > > >> Perhaps something was overlooked in the MFC from 2005-04-14 (B> > > >> 04:54:15 UTC? (B> > > > (B> > > > Yeah, we also need to MFC rev. 1.68 of src/sys/sys/bus.h. (B> > > (B> > > I've committed the prototype, much apologies for the breakage. I (B> > > compiled the patch in my RELENG_5 tree just fine, but it appears (B> > > the kernel build may be referencing /sys for includes instead of (B> > > ../../../sys or whatever. Thus build-testing MFC patches on a (B> > > -current box is not a good test. (B> > (B> > Okay, I started a build makeworld in /usr/src last night, and then (B> > build make kernel hits this. (B> > (B> > What do we do next? Is it okay to go back to cvsup, and will that (B> > pick up the changes? (B> > (B> (B> Joel, (B> (B> Can I give you a bad time. (B (BOf course. My kids would say I deserve it, too, since I'm such a tease (Baround the house. (B (B> We were always told that if you follow (B> x-stable, you were to follow cvs-all. (B (B... as in editing the example to set the default host to (Bcvsup3.jp.freebsd.org, and doing (B (Bsudo cvsup -g -L 2 stable-supfile (B (Bright before the make buildworld? (B (B> Then, you would have seen his fix (B> committed around 1811 UTC. (B (BI think I was in bed by then. (UTC+9 here.) (B (B> FWIW, you are just in time anyway because they added a security notice (B> and if you cvsup now, you will also get that fix. (B (BSo the system is not in an unstable situation such that repeating the (Bcvsup would have me trying to build from inconsistent libraries or (Banything like that? (B (BWhat the heck, I'll take a backup and give it a spin. (B (BThanks. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_5 broken?
On Thu, 14 Apr 2005 11:20:54 -0700 (BNate Lawson <[EMAIL PROTECTED]> wrote (B (B> Jon Noack wrote: (B> > On 4/14/2005 8:28 AM, David Wolfskill wrote: (B> > (B> >> On Thu, Apr 14, 2005 at 01:26:17PM +0200, Jose M Rodriguez wrote: (B> >> (B> >>> Anyone seen this? (B> >> (B> >> (B> >> [... (B> >> /usr/src/sys/kern/subr_bus.c:1082: warning: no previous prototype for (B> >> 'devclass_get_drivers' (B> >> *** Error code 1 (B> >> ... (B> >> ] (B> >> (B> >> Yup; just a few minutes ago, with sys/kern/subr_bus.c rev. 1.156.2.6. (B> >> (B> >> Perhaps something was overlooked in the MFC from 2005-04-14 04:54:15 UTC? (B> > (B> > Yeah, we also need to MFC rev. 1.68 of src/sys/sys/bus.h. (B> (B> I've committed the prototype, much apologies for the breakage. I (B> compiled the patch in my RELENG_5 tree just fine, but it appears the (B> kernel build may be referencing /sys for includes instead of (B> ../../../sys or whatever. Thus build-testing MFC patches on a -current (B> box is not a good test. (B (BOkay, I started a build makeworld in /usr/src last night, and then build (Bmake kernel hits this. (B (BWhat do we do next? Is it okay to go back to cvsup, and will that pick (Bup the changes? (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with AMD64 and 8 GB RAM? (solved)
On Fri, 2005-04-08 at 13:04 -0700, David O'Brien wrote: > The MSI K8T Master2-FAR works fine with 1GB DIMM's. Where on MSI's > website did they state 2GB double-stacked DIMM's were supported? I haven't been following the discussion, but if we're talking about the MSI K8T Master2-FAR, one can read the following from MSI's website: " • Supports DIMM sizes from 64MB (128Mb x 16 DRAMs) to 2GB. • Supports 4 DDR DIMMs up to 8GB (Registered Memory only) " http://www.msi.com.tw/program/products/server/svr/pro_svr_detail.php?UID=484 :-) -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: adding opentsa to the system's openssl
On Thu, 07 Apr 2005 10:40:05 +0200 (B"Ronald Klop" <[EMAIL PROTECTED]> wrote (B (B> /usr/ports/sysutils/portdowngrade (B> (B> Never used it. So I can't tell you more. (B (BThanks. I think I talked myself into compiling this one completely (Boutside the source and ports trees because of the patches, but this will (Bbe good for future reference. (B (B(I'd seen it before. I see things and they just don't register. I'm not (Bquite old enough to blame it on my age, though.) (B (BBTW, openssl took the opentsa patch, made, and installed to the default (Bopenssl location from outside the ports tree without any problems I (Bcould see, if anyone cares to know. (B (B> [...] (B> > (B> > Short version -- (B> > (B> > What kind of grief am I likely to cause myself if I grab the opentsa (B> > patch, apply it to the openssl source in /usr/sys/crypto, and make world? (B> > [...] (B (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
adding opentsa to the system's openssl
I know this is kind of like jumping off the high board before I've (Bchecked for water in the pool, but I'm wondering. (B (BLong version of the story -- (B (BI need to get an opentsa server running, and their site only has patches (Bfor openssl 0.9.7e, not for the latest, 0.9.7f. (B (BThe current version in ports is 0.9.7f. I don't know how to massage the (Bports collection to get a downlevel version yet, and the boss doesn't (Bwant me to take time to learn how. (Silly boss.) So I just used the (Bsample stable-supfile to get the system sources and note that the system (Bversion has gone up from 0.9.7d to 0.9.7e . (B (BSo, I'm thinking to myself this could be heaven or this could be ... (B (BIf this works, we are going to be wanting to build a dedicated time (Bstamp server anyway, ... (B (Band similar sirens are calling from far away, ... (B (Bbut I really don't want to find myself in the situation where I can (Bcheckout anytime but never ... (B (BShort version -- (B (BWhat kind of grief am I likely to cause myself if I grab the opentsa (Bpatch, apply it to the openssl source in /usr/sys/crypto, and make world? (B (BThere's a voice in my other ear that says the patch was not built to mix (Bwith freebsd patches to openssl, so I should just grab the stock openssl (Band build it completely outside the ports tree, configure the timestamp (Bstuff to use the independently built openssl. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc. $B3t<02qhttp://www.ddcom.co.jp> ** (B (B___ (Bfreebsd-stable@freebsd.org mailing list (Bhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable (BTo unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 5-STABLE doesn't compile: fails on Kerberos5?
I was trying to "make buildworld" the 5-STABLE tree (fetched as of about an hour ago), and I got these error messages a bit of the way into it. Any idea what was causing this? I'll get back to you right away if you need more information or anything. /usr/local/libexec/ccache/cc -O -march=pentium2 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libkrb5/../../include -DINET6 -c /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/cache.c /usr/local/libexec/ccache/cc -O -march=pentium2 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn1 -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/usr/src/kerberos5/lib/libkrb5/../../include -DINET6 -c /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c: In function `setpw_send_request': /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c:170: error: syntax error before "chpw" /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c:188: error: `chpw' undeclared (first use in this function) /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c:188: error: (Each undeclared identifier is reported only once /usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5/changepw.c:188: error: for each function it appears in.) *** Error code 1 Stop in /usr/src/kerberos5/lib/libkrb5. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Joel Heikkila <[EMAIL PROTECTED]> ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: using ADAPTIVE_MUTEXES savely?
On Fri, 2005-02-11 at 12:44 +0100, Mipam wrote: > Hi, > > Does anybody run with the kernel option ADAPTIVE_MUTEXES > in RELENG_5 yet? Is it safe to use or should be used with care? There is no ADAPTIVE_MUTEXES option in RELENG_5 AFAIK, since it's enabled by default. You can however use NO_ADAPTIVE_MUTEXES to disable it. >From src/sys/conf/NOTES: " # ADAPTIVE_MUTEXES changes the behavior of blocking mutexes to spin # if the thread that currently owns the mutex is executing on another # CPU. This behaviour is enabled by default, so this option can be used # to disable it. options NO_ADAPTIVE_MUTEXES " -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Sparc64 Install 5.3
Hi all Is it possible to install 5.3 on a sparc64 (Ultra 5) without using serial console, I seem to get garbled consoles when I try to install via normal screen and keyboard? Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd: ioctl(CDRIOCFIXATE): Input/output error
On Tue, 2005-01-11 at 16:55 +0200, Nikolay Pavlov wrote: > Hi, freebsd users. > After upgrade from 4.10 to 5.3, I can't write disks > with burncd tool. I see this error: > > # burncd -emv -s 10 data akt.iso fixate > adding type 0x08 file akt.iso size 554522 KB 277261 blocks > next writeable LBA 0 > addr = 0 size = 567830528 blocks = 277261 > writing from file akt.iso size 554522 KB > written this track 554522 KB (100%) total 554522 KB > fixating CD, please wait.. > burncd: ioctl(CDRIOCFIXATE): Input/output error > > Also I can't blank cd.. burncd blank command just hang all the time.. Perhaps related to: http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/010776.html & http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/010825.html I'm still getting "fatal trap 12" (see thread above) when I'm trying to blank a cd from the console, and the system hangs if I do it in X... -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd freeze system
On Tue, 2005-01-04 at 18:10 +1100, Peter Jeremy wrote: > On Tue, 2005-Jan-04 00:20:59 +0100, Norbert Augenstein wrote: > >i have tried to burn an iso of 26MB of size, and my system locks > >up so i have to reboot. > > /var/log/messages is unlikely to include the last 30 seconds or so of > logging following a crash. Try running burncd from the console and > see if there are any messages. > > Also, you might like to expand on "locks up". Can you ping the system > from another host? Switch VTYs? If you have DDB enabled, can you > enter it? > > >As i can burn it in Win, i am out of ideas. > > I presume this is Winbloze on the same host (dual-boot). > I saw something similar with fixate a couple of days ago: http://lists.freebsd.org/pipermail/freebsd-stable/2005-January/010776.html -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: setting net.inet.tcp.inflight_* on 5.3-STABLE
On Sun, 2005-01-02 at 16:52 -0800, darren david wrote: > hi all- > > so i'm attempting to tweak my kernel to eke out a bit more oomph from my >Gigabit interface, but i can't seem to set any of the > "net.inet.tcp.inflight_*" params with sysctl. i get: > > sysctl: unknown oid 'net.inet.tcp.inflight_enable' > It's "net.inet.tcp.inflight.enable" :-) -- Joel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_5: Fatal trap 12: page fault while in kernel mode
ec8d0 "/usr/src/sys/i386/i386/trap.c", line=699)
at /usr/src/sys/kern/subr_witness.c:714
#24 0xc04fe57a in _mtx_lock_flags (m=0xc1a3a3f4, opts=0,
file=0xc06ec8d0 "/usr/src/sys/i386/i386/trap.c", line=699)
at /usr/src/sys/kern/kern_mutex.c:271
#25 0xc0694c11 in trap_pfault (frame=0xd5453bc8, usermode=0, eva=65532)
at /usr/src/sys/i386/i386/trap.c:699
#26 0xc069490d in trap (frame=
{tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi =
-1046234384, tf_ebp = -716882904, tf_isp = -716882956, tf_ebx = -1044264
at /usr/src/sys/i386/i386/trap.c:417
#27 0xc0682c1a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#28 0x0018 in ?? ()
#29 0x0010 in ?? ()
#30 0x0010 in ?? ()
#31 0x in ?? ()
#32 0xc1a3baf0 in ?? ()
#33 0xd5453c28 in ?? ()
#34 0xd5453bf4 in ?? ()
#35 0xc1c1c818 in ?? ()
#36 0xfffc in ?? ()
#37 0x0001 in ?? ()
#38 0x in ?? ()
#39 0x000c in ?? ()
#40 0x in ?? ()
#41 0xc052cb63 in turnstile_wait (ts=0x0, lock=0xc1c1c818, owner=0xfffc)
at /usr/src/sys/kern/subr_turnstile.c:480
#42 0xc04fea8c in _mtx_lock_sleep (m=0xc1c1c818, td=0xc1a3baf0, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:560
#43 0xc04fe5af in _mtx_lock_flags (m=0xc1c1c818, opts=0,
file=0xc06d246a "/usr/src/sys/kern/kern_sema.c", line=79)
at /usr/src/sys/kern/kern_mutex.c:273
#44 0xc05078aa in _sema_post (sema=0xc1c1c818,
file=0xc06c1ac2 "/usr/src/sys/dev/ata/ata-queue.c", line=395)
at /usr/src/sys/kern/kern_sema.c:79
#45 0xc0454c7b in ata_completed (context=0xc1c1c7d0, dummy=1)
at /usr/src/sys/dev/ata/ata-queue.c:395
#46 0xc052b542 in taskqueue_run (queue=0xc1a29c40)
at /usr/src/sys/kern/subr_taskqueue.c:191
#47 0xc052b65b in taskqueue_thread_loop (arg=0x0)
at /usr/src/sys/kern/subr_taskqueue.c:237
#48 0xc04f0e36 in fork_exit (callout=0xc052b620
,
arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:807
#49 0xc0682c7c in fork_trampoline ()
at /usr/src/sys/i386/i386/exception.s:209
--
Joel
Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.3-STABLE #0: Sat Jan 1 14:36:28 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/WRK
WARNING: WITNESS option enabled, expect reduced performance.
mptable_probe: MP Config Table has bad signature: \^E\^G
ACPI APIC Table:
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 3000+ (2162.75-MHz 686-class CPU)
Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0
Features=0x383fbff
AMD Features=0xc040
real memory = 536805376 (511 MB)
avail memory = 515629056 (491 MB)
ioapic0 irqs 0-23 on motherboard
npx0: [FAST]
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
cpu0: on acpi0
acpi_button0: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
agp0: mem 0xe000-0xe3ff at device 0.0
on pci0
pci0: at device 0.1 (no driver attached)
pci0: at device 0.2 (no driver attached)
pci0: at device 0.3 (no driver attached)
pci0: at device 0.4 (no driver attached)
pci0: at device 0.5 (no driver attached)
isab0: at device 1.0 on pci0
isa0: on isab0
pci0: at device 1.1 (no driver attached)
ohci0: mem 0xe8003000-0xe8003fff irq 22 at
device 2.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ulpt0: hp deskjet 5550, rev 2.00/1.00, addr 2, iclass 7/1
ulpt0: using bi-directional mode
ohci1: mem 0xe8004000-0xe8004fff irq 21 at
device 2.1 on pci0
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: on ohci1
usb1: USB revision 1.0
uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00,
addr 2, iclass 3/1
ums0: 5 buttons and Z dir.
pci0: at device 2.2 (no driver attached)
pci0: at device 4.0 (no driver attached)
pcm0: port 0xb400-0xb47f,0xb000-0xb0ff mem
0xe8001000-0xe8001fff irq 21 at device 6.0 on pci0
pcm0: [GIANT-LOCKED]
pcm0:
pcib1: at device 8.0 on pci0
pci1: on pcib1
fxp0: port 0x9000-0x903f mem
0xe700-0xe701,0xe702-0xe7020fff irq 17 at device 9.0 on pci1
miibus0: on fxp0
inphy0: on miibus0
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:b3:d6:fd:4b
atapci0: port
0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 9.0 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
pcib2: at device 30.0 on pci0
pci2: on pcib2
pci2: at device 0.0
Re: 4.x can't read 5.x dump?
Thanks Ken (and thanks to Paul, who replied with similar info), I can appreciate this - I shouldn't have been, but I guess I was just caught out by the change in the filesystem type and didn't realise that dump depended so heavily on it. I can work around, so all is well. Sorry about the double posting btw, I didn't expect my first one to make it to the list. cheers, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] > On Thu, Dec 02, 2004 at 10:48:43AM +1000, Joel Hatton wrote: > > > I'm backing up a 5.x machine at the moment with this command: > > > > dump -0Lau -b128 -f - /var | gzip -2 | ssh FreeBSD4 dd of=aacd0s1f.gz > > > > After the dump finishes, I try to read the file on the 4.x destination: > > > > # gzip -dc aacd0s1a.gz | restore -ivf - > > Verify tape and initialize maps > > Tape is not a dump tape > > > > I can scp the file back to the 5.x machine and it loads just fine, so what > > gives? This type of failure is somewhat scary for me right now, given that > > I may have to restore files to another destination that may not be 5.x > > based. > > This is, unfortunately, something that you should not expect to work > for any *nix variant. The dump mechanism of creating backups creates > output that has "intimate knowledge" of the filesystem so that it can > recreate that filesystem exactly as it exists on the disk. As the > filesystem itself evolves (has features added to it) the dump programs > need to have their data structures change to accomodate the extra > information that is now needed. For example if in 4.X there were no > ACLs but 5.X added ACLs then the dump program's data structures would > need to be changed so it had the ability to store the ACL information > in the output, and the restore program would need to be modified to > look for that and do the right thing if it finds ACL information. > > If there had been no filesystem changes between 4.X and 5.X then > there would not be any need to change dump, and what you are trying > to do would work. But there were filesystem changes between 4.X and > 5.X, so dump was changed, and now there is extra stuff in the dump > images that the 4.X version of restore doesn't understand. This same > general principle holds for all OS's, not just FreeBSD. > > If you need to be able to "restore" stuff from a 5.X machine on a > variety of different platforms (4.X, or some other *nix) then don't > use dump to create the images, use something like Gnu tar which can > be made to understand the concept of incremental backups. You do > however run the risk of not being able to do a "perfect" restore of > a filesystem if you use some of the more advanced filesystem features > like immutable files or ACLs - the tar mechanisms of doing backups > may not be able to record that extra information. > > -- > Ken Smith > - From there to here, from here to | [EMAIL PROTECTED] > there, funny things are everywhere. | > - Theodore Geisel | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.x can't read 5.x dump?
Hi, I'm backing up a 5.x machine at the moment with this command: dump -0Lau -b128 -f - /var | gzip -2 | ssh FreeBSD4 dd of=aacd0s1f.gz After the dump finishes, I try to read the file on the 4.x destination: # gzip -dc aacd0s1a.gz | restore -ivf - Verify tape and initialize maps Tape is not a dump tape I can scp the file back to the 5.x machine and it loads just fine, so what gives? This type of failure is somewhat scary for me right now, given that I may have to restore files to another destination that may not be 5.x based. thanks, -- Joel Hatton -- Security Analyst| Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland| WWW: www.auscert.org.au Qld 4072 Australia | Email: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Microtech USB6SCSI Cable - working well ?
Hi, I'm planning to buy the Microtech USB-SCSI Cable (http://www.microtechint.com/qs-usbscsi.html). I've seen the ref in usbdevs source code * product MICROTECH SCSIDB25 0x0004 USB-SCSI-DB25 product MICROTECH SCSIHD50 0x0005 USB-SCSI-HD50 * Questions :) - does this mean that it will work ? or just that FreeBee will print a pretty message when I'll plug it ? - what would be the diff between the DB25 (female) and the HD50 (male) version ? I mean, is there a version to plug disks and a version to plug s'thg else ??? - (for those who have it ;) will any SCSI drive fit this cable (&FreeBee) ? any ref of hard drives working (pliz) ? thX for answers, Jo ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.fr To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Is OpenBSD safer than other BSDs ?
'lo folks :-) I'm using OpenBSD as my home gateway and I was wondering : is an OpenBSD box really safer than a FreeBSD one if your configure things (like inetd, ipf, ...) the same way ? if not, what's the point in using Open rather Free for a Gateway/Firewall/DNS cache/DHCPd ? thnX for answers === Joel CARNAT software is like sex : it's better when it's free :P To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: CFT: boot patch for 4.x
On Fri, 14 Jul 2000, John Baldwin wrote: > Hey all, > > I would really like to get the new boot0 into -stable in time > for 4.1, but I'd like a few folks to test it out and get some > feedback before I do. You can find the patch at > http://people.FreeBSD.org/~jhb/patches/boot0.rel4.patch. The > patch is relative to /usr/src, so to apply it: > > # cd /usr/src > # patch < where_ever_the_patch_file_lives/boot0.rel4.patch > > Then either make a new world or rebuild the utilities your > self. You can then use boot0cfg or fdisk to install the new > boot0 boot manager. Thanks. > > -- > > John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message > It seems to work just fine and solves some problems i had with the previous one. Not being able to boot windows beeing the third partion, about 2G after a 10G and 4G freebsd partions. - Nevyn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
