supermicro 6014H-82
Hi list I've got the subj and tried to install FreeBSD. 5.3-R, 5.4-BETA1, 5.4-STABLE did not install at all. They timeouted on ATA and hang while probing asr0, but 5.2.1-R installed fine. Any suggestion? I would like to use 5.4-R. Does anybody use the subj with 5.3-R or later? Best Regards -- EMIT-RIPN, EVM7-RIPE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC Drivers in FreeBSD which support ALTQ?
What are they? I can't use Intel cards because they are crashing my Adaptec RAID... -AL. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supermicro 6014H-82
In safe mode 5.4-B1 and 5.3-R is booted fine from install CD without any hangs. On 29 2005 12:44, you wrote: Have you tried installing it in safe mode? Eugene Mitrofanov wrote: Hi list I've got the subj and tried to install FreeBSD. 5.3-R, 5.4-BETA1, 5.4-STABLE did not install at all. They timeouted on ATA and hang while probing asr0, but 5.2.1-R installed fine. Any suggestion? I would like to use 5.4-R. Does anybody use the subj with 5.3-R or later? Best Regards -- EMIT-RIPN, EVM7-RIPE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supermicro 6014H-82
Perhaps you should try to install 5.2.1-R, then cvsup to 5.4 (or anything else you want). Eugene Mitrofanov wrote: Hi list I've got the subj and tried to install FreeBSD. 5.3-R, 5.4-BETA1, 5.4-STABLE did not install at all. They timeouted on ATA and hang while probing asr0, but 5.2.1-R installed fine. Any suggestion? I would like to use 5.4-R. Does anybody use the subj with 5.3-R or later? Best Regards -- Best regards, Sergey Shyman SSI-RIPE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
usb modem
dear all i have usb modem and detect in my freebsd 5.3 , i just want know how to configure that usb modem be dial-up an dial-in . thx SONJAYA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD on Bochs
Hi All: I have a question about Freebsd on bochs. I'm interesting to build owner Freebsd scratch. Due the hardware limited , I want to run this scratch on Bochs. Therefore , I refered a article , http://sig9.com/articles/freebsd-on-bochs , to build a image under 5.2R. when I booted the image file under Bochs-2.0.2 .. it stoped on a prompt , mountroot . The bochs' console screenshot is following lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounter TSC frequency 500159 Hz quality 800 Timecounters tick every 10.000 msec ad0: FAILURE - SETFEATURES ENABLE RCACHE status=41READY,ERROR error=4ABORTED ad0: FAILURE - SETFEATURES ENABLE WCACHE status=41READY,ERROR error=4ABORTED GEOM: create disk ad0 dp=0xc1a81e60 ad0: 511MB Generic 1234 [1040/16/63] at ata0-master PIO2 Manual root filesystem specification: fstype:device Mount device using filesystem fstype eg. ufs:da0s1a ? List valid disk boot devices empty line Abort manual input -- the bochs' log records 00505152373i[HD ] SET FEATURES subcommand 0xaa not supported by disk. 00505289771i[HD ] SET FEATURES subcommand 0x02 not supported by disk. What's happen?! Did I miss something else ?! ps. my bochs configuration is as following -- megs: 64 romimage: file=$BXSHARE/BIOS-bochs-latest, address=0xf vgaromimage: $BXSHARE/VGABIOS-lgpl-latest floppya: 1_44=/dev/fd0, status=ejected # hard disk ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14 ata0-master: type=disk, path=freebsd.img, mode=flat, cylinders=1040, heads=16, spt=63 boot: disk log: out.txt mouse: enabled=0 keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/sdl-pc-us.map Regards Jumbler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supermicro 6014H-82
I installed in safemode and then build custom kernel. I took the PAE as example removed the PAE option, added acpi and SMP , compiled and installed. This works great. Booting GENERIC will fail on my supermicro too. Hang at the ICH5 ata controller with timeouts. chers, -Dennis On Tue, Mar 29, 2005 at 11:09:54AM +0300, Eugene Mitrofanov wrote: Hi list I've got the subj and tried to install FreeBSD. 5.3-R, 5.4-BETA1, 5.4-STABLE did not install at all. They timeouted on ATA and hang while probing asr0, but 5.2.1-R installed fine. Any suggestion? I would like to use 5.4-R. Does anybody use the subj with 5.3-R or later? Best Regards -- EMIT-RIPN, EVM7-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Ted Mittelstaedt writes: The main point I've been trying to make is that just because FreeBSD's drivers don't support whatever modification has been made in the Adaptec code on the Vectra, does not mean that the FreeBSD driver is broken or has a bug in it. When something doesn't work, it's broken. If you consider a change in firmware to be a hardware problem, then a lack of proper handling of the firmware in the OS must also be a problem. I don't see why the same standards wouldn't apply to both. The key point here, though, is that Windows apparently works correctly with the firmware, whatever changes that firmware may contain. FreeBSD does not. Therefore FreeBSD is broken. But you are correct in that these are trapdoor systems - if you do not install the Compaq/HP-written drivers at the right times during the install, then Windows loads it's default drivers which may or may not (usually not) work. And once loaded you cannot unload them and replace them with the manufacturer-supplied ones because the operating system won't let you do things like unloading the device driver that runs the controller that the system disk is on, things like that. You have to nuke and repave. I often wonder why people even buy servers from these vendors when they have so much vendor-specific junk on them. I suppose there isn't much competition. It seems to me that it should be possible to build equally good servers with entirely off-the-shelf, standard components, and no magic firmware or software. But vendors apparently cannot resist changing _something_. I think Dell is the same way, though. I suspect all the name brand systems are - that is why people buy name-brand server systems, to get the extra little features like the preemptive disk failure monitoring, the case-open/case-closed, temperature, fanspeed, power supply voltage monitoring, and all the other proprietary little features. I suppose it's seductive initially, but after fighting with proprietary hardware and software for a while, it gets old. Forget the case-open switch and the three-dimensional beeping animated temperature monitoring application, and just buy commodity hardware and software. In exchange for sacrificing a few frills, you get something that behaves predictably and can be maintained cheaply without critical dependencies on one supplier. I'm pleased that I built my current server myself out of stuff bought right off the shelf. It may be 1-2% less performant than a name-brand, all-in-one server, but at least I know exactly what's in the machine, and virtually none of it is dependent on any single supplier or single model of hardware component. If I want to buy spare disks, I can get them for 80, and I can choose from a wide variety of brands; if this were a proprietary name-brand machine, I'd have to pay 300 per disk, and I'd be at the mercy of the vendor (if he stopped selling the specially tweaked disks required by his server, I'd be out of luck). That's the problem with my HP machine. It still runs great and may continue to do so for a long time, but if it breaks down, there's no way to fix it, as just plugging in commodity parts won't do. Even the memory had to be ordered special. It's very much like buying the Lexus that comes with the key chip - you get the extra feature of not being able to start the car without a key with a chip in it, with the downside that only Lexus supplies the chipped keys (and charges you up the ass for them of course) Yes. :-) Actualy I didn't cover that. Manufacturers put these proprietary things in their server products because they are features that are very useful to organizations that run hundreds if not thousands of servers all over the country or the world - with the caveat of course that every server has to be the same model and come from that same manufacturer to get the full benefit of the little fancy features. But to most of us who don't run these large networks, these features do nothing at best, and are an annoyance at worst. The trend in the IT industry has always been away from proprietary and towards commodity. The fancy little features eventually disappear over time. And they often are not missed. The HP disk sector atomicity thing was a great feature if you had disks on an external cabinet that didn't have a UPS on it. Sure, laugh, but when you have a large HP minicomputer with a disk pack the size of a refrigerator that has 50 scsi disks in it, that consumes 15Kw, you don't just go down and grab a UPS from Office Depot. But naturally for small PC's it was a completely stupid and useless feature which is why no other disk manufacturer bothered to license HP's patent on it. What does sector atomicity do? While I can't of course say that the Adaptec microcode in Anthony's server was modified to support this particular feature, clearly HP had some fancy feature support in mind which is why they tampered with the microcode to begin
Re: enable acpi
On 03/13/05 03:17 koen de wijs said the following: Hello Could anyone tell me how to enable acpi with FreeBSD 5.3? I read on the FreeBSD that acpi isn't enabled in some cases. When I shutted down with FreeBSD 5.2.1, the power of my pc automaticaly goes down and with 5.3 not. How do I enable acpi? acpi related, but on freebsd 4.11 (cvsupped and built on 24 march). i've compiled with device acpica in the kernel, but i get sporadic page faults as attached. i do know that acpica is experimental and that LINT does warn of kernel panics and machine hangs. however i was wondering if anyone has got this working succesfully on any machine. the box in question is a Benq Joybook 6000 with the following dmesg segment: Mar 29 17:50:44 prophet /kernel: Copyright (c) 1992-2005 The FreeBSD Project. Mar 29 17:50:44 prophet /kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 29 17:50:44 prophet /kernel: The Regents of the University of California. All rights reserved. Mar 29 17:50:44 prophet /kernel: FreeBSD 4.11-STABLE #3: Tue Mar 29 17:40:52 MYT 2005 Mar 29 17:50:44 prophet /kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ALPHAQUE Mar 29 17:50:44 prophet /kernel: Timecounter i8254 frequency 1193182 Hz Mar 29 17:50:44 prophet /kernel: Timecounter TSC frequency 1395479702 Hz Mar 29 17:50:44 prophet /kernel: CPU: Intel(R) Pentium(R) M processor 1400MHz (1395.48-MHz 686-class CPU) Mar 29 17:50:44 prophet /kernel: Origin = GenuineIntel Id = 0x695 Stepping = 5 Mar 29 17:50:44 prophet /kernel: Features=0xa7e9f9bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE Mar 29 17:50:44 prophet /kernel: real memory = 234815488 (229312K bytes) Mar 29 17:50:44 prophet /kernel: avail memory = 223420416 (218184K bytes) Mar 29 17:50:44 prophet /kernel: Preloaded elf kernel kernel at 0xc04a4000. Mar 29 17:50:44 prophet /kernel: netsmb_dev: loaded Mar 29 17:50:44 prophet /kernel: Pentium Pro MTRR support enabled Mar 29 17:50:44 prophet /kernel: md0: Malloc disk Mar 29 17:50:44 prophet /kernel: Using $PIR table, 6 entries at 0xc00fe840 Mar 29 17:50:44 prophet /kernel: acpi0: INSYDE RSDT_000 on motherboard Mar 29 17:50:44 prophet /kernel: acpi0: power button is handled as a fixed feature programming model. Mar 29 17:50:44 prophet /kernel: Timecounter ACPI-fast frequency 3579545 Hz Mar 29 17:50:44 prophet /kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_cpu0: CPU on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_tz0: thermal zone on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_button0: Sleep Button on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_lid0: Control Method Lid Switch on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_button1: Power Button on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_acad0: AC adapter on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_cmbat0: Control method Battery on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_cmbat1: Control method Battery on acpi0 Mar 29 17:50:44 prophet /kernel: acpi_ec0: embedded controller port 0x66,0x62 on acpi0 and the following acpi sysctls: hw.acpi.supported_sleep_state: S3 S4 S5 hw.acpi.power_button_state: S5 hw.acpi.sleep_button_state: S1 hw.acpi.lid_switch_state: S1 hw.acpi.standby_state: S1 hw.acpi.suspend_state: S3 hw.acpi.sleep_delay: 0 hw.acpi.s4bios: 1 hw.acpi.verbose: 0 hw.acpi.disable_on_poweroff: 1 hw.acpi.cpu.max_speed: 8 hw.acpi.cpu.current_speed: 8 hw.acpi.cpu.performance_speed: 8 hw.acpi.cpu.economy_speed: 4 hw.acpi.thermal.min_runtime: 0 hw.acpi.thermal.polling_rate: 30 hw.acpi.thermal.tz0.temperature: 3152 hw.acpi.thermal.tz0.active: 1 hw.acpi.thermal.tz0.thermal_flags: 0 hw.acpi.thermal.tz0._PSV: 3762 hw.acpi.thermal.tz0._HOT: -1 hw.acpi.thermal.tz0._CRT: 3762 hw.acpi.thermal.tz0._ACx: 3760 3130 -1 -1 -1 -1 -1 -1 -1 -1 hw.acpi.acline: 1 hw.acpi.battery.life: -1 hw.acpi.battery.time: -1 hw.acpi.battery.state: 7 hw.acpi.battery.units: 2 hw.acpi.battery.info_expire: 5 any pointers would be much appreciated. -- Regards, /\_/\ All dogs go to heaven. [EMAIL PROTECTED](0 0)http://www.alphaque.com/ +==oOO--(_)--OOo==+ | for a in past present future; do| | for b in clients employers associates relatives neighbours pets; do | | echo The opinions here in no way reflect the opinions of my $a $b. | | done; done | +=+ Mar 29 17:55:10 prophet /kernel.working: kernel trap 12 with interrupts disabled Mar 29 17:55:10 prophet /kernel.working: Mar 29 17:55:10 prophet /kernel.working: Mar 29 17:55:10 prophet /kernel.working: Fatal trap 12: page fault while in kernel mode Mar 29 17:55:10 prophet /kernel.working: fault virtual address = 0x70 Mar 29 17:55:10
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 29 Mar 2005 12:23:46 +0200 Anthony Atkielski wrote: The key point here, though, is that Windows apparently works correctly with the firmware, whatever changes that firmware may contain. FreeBSD does not. Therefore FreeBSD is broken. Wrong. Windows does /not/ work correctly with the firmware if you let it use it's own drivers (like FreeBSD does). /Both/ OS's choke then! Forget the case-open switch and the three-dimensional beeping animated temperature monitoring application, and just buy commodity hardware and software. In exchange for sacrificing a few frills, you get something that behaves predictably and can be maintained cheaply without critical dependencies on one supplier. Right. Plus Windows as well as FreeBSD will run on it flawlessly. So what's your point in all those previous messages if you knew so well what was the correct attitude in buying hardware? -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strcoll(3) case sensitivity?
--On måndag, mars 28, 2005 21.56.00 -0600 Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Mar 29), Palle Girgensohn said: On many unix systems, strcoll(3) is case insensitive for locales other than C/POSIX. Not so for FreeBSD. Just curious, is this a design decision or simply the lack of time and efforts to write the code for it? The only thing I can find is ache's commit back in 1996 in /usr/src/share/colldef: 1996-06-09 12:24 ache * la_LN.ISO8859-1.src, la_LN.ISO_8859-1.src, lt_LN.ISO_8859-1.src: Make collation table compatible with POSIX WG15 view, i.e. capital letters first I wish I could find the POSIX docs for this, but sadly they don't seem to exists openly on the net? /Palle ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
dick hoogendijk writes: Wrong. Windows does /not/ work correctly with the firmware if you let it use it's own drivers (like FreeBSD does). /Both/ OS's choke then! Sorry, but that's incorrect. For eight years I ran a completely standard retail version of Windows NT on the machine, straight off the shelf. No special drivers required. I never had any problems. Right. Plus Windows as well as FreeBSD will run on it flawlessly. I haven't tried Windows on a home-made box, but FreeBSD seems to run on it without any trouble. Apparently FreeBSD does have a problem with the on-board gigabit Ethernet interface on this motherboard, but I just plugged in my existing 3Com 100 Mbps Ethernet card and configured that instead, and the problem went away. So what's your point in all those previous messages if you knew so well what was the correct attitude in buying hardware? My point was that FreeBSD doesn't work on the machine. I wanted to know why. I still don't know why it doesn't work on the machine. Apparently nobody here really knows how FreeBSD works. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: usb modem
Read this http://freebsd.packards-home.net/index.php -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of sonjaya Sent: Tuesday, March 29, 2005 4:28 AM To: freebsd-questions@freebsd.org Subject: usb modem dear all i have usb modem and detect in my freebsd 5.3 , i just want know how to configure that usb modem be dial-up an dial-in . thx SONJAYA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ppp conf
Just add the 9 to front of phone number you code in ppp.conf for ISP. Read this http://freebsd.packards-home.net/index.php -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of RdBSD Sent: Tuesday, March 29, 2005 2:59 AM To: freebsd-questions@freebsd.org Subject: ppp conf Dear all, I want to connect to isp using dial up modem, but my office has a rule if we want to connect to outside we have to dial 9 first then destination number. How can i configure ppp.conf ? Thanks for the answer. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a question about the pkg_add and make install clean
On Tuesday 29 March 2005 05:17, Kent Stewart wrote: On Monday 28 March 2005 07:27 pm, well sun wrote: That is if I want to install the latest version, I should use the make install or get the xxx.tbz from the freebsd-current directory. Is it correct? You have to understand up front that the KDE people will tell you that make install clean will not build a clean KDE. You have to make and then, make install for all of the pieces to be built. make install clean will build kde. It's a metaport, the component parts will be built as dependencies. It's updating or deleting the kde port that doesn't affect the components. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATI Rage Mobility
On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? A frequent mistake is that people forget to install the DRI drivers. So, did you install /usr/ports/graphics/dri? Damn, forgot the attachments (common problem of mine, I'm afraid...) xorg's log would be nice too. tijl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sFTP nologin
* Grant Peel [2005-03-25 09:19 -0500] Is there a quick - secure way to allow the sshd sFTP subsystem to allows sftp connections without allowing shell accounts? I'm using this shell-script as a nologin-shell: - #!/bin/sh if [ $1 = -c -a $2 = /usr/libexec/sftp-server ]; then exec /bin/sh $@ else echo You are not allowed to login sleep 2 exit 0 fi - This will allow sftp, but not shell login (or scp) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: aac/fxp system instability
Fixed this! Resolved all my IRQ conflicts, didn't do it... Compiled the fxp driver into the kernel (instead of having it as a module), *fixed it*! -AL. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
PR and recompiling
Hi there, I have some problems (ATA_IDENTIFY timeout) when I try to install FreeBSD 5.3-RELEASE (CD). With Google, I have found the PR of my problem, posted by another user: http://www.freebsd.org/cgi/query-pr.cgi?pr=74124 It says to comment some lines in /usr/src and then to recompile all. How can I recompile the kernel if I can't install FreeBSD ?! Thanks in advance, -- WEB: http://xjp.altervista.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: a question about the pkg_add and make install clean
On Tuesday 29 March 2005 04:27, well sun wrote: thanks your answers. I use the ports-supfile and stable-supfile under /usr/share/examples/cvsup to do upgrade. I think I understand what the difference between the pkg_add and make install. That is if I want to install the latest version, I should use the make install or get the xxx.tbz from the freebsd-current directory. Is it correct? Could I make the default directory from 5.3-release to 6.0-current by change one configuration file? If I want to override the default fetching site of pkg_add command by some faster sites, how can I do? by and large, speed should not be the prime reason for choosing a package server. The default FreeBSD package collection often lags the ports collection considerably. Many packages are only updated during FreeBSD releases, some not even then. For KDE you are better-off using the fruit-salad servers, you will find a link here: http://freebsd.kde.org/instructions.php#kde-from-packages However, if you have a reasonably up-to-date machine I'd stick to ports; and use portupgrade or portmanager to maintain them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bandwidthd
guys, Is there anyone can help me install bandwidthd in RedHat? I have tried all the possible way in installing bandwidthd, like downloading and installing all it's pre-requisites like lipng, libpcap, gd. But I always got the same error.. like, error locating libpcap. Someone on this may be able to help. People here often have diverse experience.But, you should note that this is the FreeBSD questions list. Redhat is a Lunix OS. It is not FreeBSD Unix. You might prefer to ask that particular question on a list that is intended for Linux. jerry Tkae Note: I already install the newest version of those three pre - requisites. Can anyone tell me what else should i do or is there something missing on my intsallation? Thanks -- Raymond Gosmo Lualhati Technical Support Enginner Asiagate Networks Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A Riddle
On Mar 27, 2005, at 11:09 AM, [EMAIL PROTECTED] wrote: Firstly, anyone who uses their own server for lists is a complete idiot. Do you have an actual reason to back up this assertion? Are you trying to insult everyone who has found AOL or Yahoo or Gmail to be more convenient for not clogging their server with lists traffic? Or do you just feel important because you laid out the $20 for your own domain? What if they just don't want people storing the content of their email and are competent enough to manage their own server? Or what if they have their own domain but it is virtually hosted within a larger service provider? And YES, they do default to top posting. You hit reply, and you get this (see below). See what? Its not really conducive to bottom posting, and when you do a google search and hit a long thread you read the answer you want first, rather than having to page down 200 times. Your browser can't do a search within the page and highlight what you're looking for? If you're over 50 and once used a pdp11 then you may argue the opposite, but times are a-changing, so get with it. So because the rest of the new netizen order are mentally defective, everyone else must retard themselves to fit in with the sheeple? Aren't you that [EMAIL PROTECTED] that keeps harassing people then gets kicked off the list, only to show up again as a slightly altered alias? Methinks that is the real reason you use web mail providers...using your own domain for harassing people would make it too easy to block you. -Bart ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Questions using PartitionMagic for dual-boot with WinXP-Pro
Jerry - Thank you for your email - that pretty much cleared everything up. I am quite definitely installing FreeBSD (5.3) - not Linux - sorry about the many misleading mentions of Linux. Those crept in because many of the tips I had googled seemed to mention Linux utilities (such as boot managers) in the same breath as FreeBSD-specific things, making me think that whenever the tools I was using (such as PartitionMagic) didn't mention FreeBSD, I should just pick the closest generic Linux thing and it would work. I think I'm clear now on the following: (1) I give the new FreeBSD slice any old file system - FreeBSD will overwrite it (with FFS I assume?). (2) The dreaded 1024-cylinder limit is a thing of the past, due to BIOS LBA. And even though BIOS LBA still has an 8GB limit, that's not a problem as long as my first slice is DOS (which it is) because it will actually start at Cylinder 0, Head 1, Sector 1, leaving space for FreeBSD's boot manager (or MBR?). I have read chapter 2 of the handbook several times, as well as another document on freebsd.org about installing multiple OSes, but there are 2 issues which I don't think are made clear enough for newbies in the docs: (1) The docs should emphasize (as you did) that it doesn't matter what file system you set for FreeBSD's slice - FreeBSD will overwrite it anyays. (2) Several frightening warnings are given, saying that a slice needs to be within the 1024 cylinder limit in order to be bootable. These warnings are obsolete because of BIOS LBA and because of the free space available if the first slice is for DOS. Your email cleared up both these issues. Thanks, Stefan Jerry McAllister [EMAIL PROTECTED] wrote: Hi - I need help partitioning a laptop (using PartitionMagic) which already has WinXP-Pro on it, so it can dual-boot FreeBSD. I kind of wonder why you are asking on this (FreeBSD questions) list. I don't see any FreeBSD installation in the plan you outline. SUMMARY === I'm thinking of doing the following layout (things I'm unsure about are in brackets [...]): - boot (Z:) - FAT [or FAT32?]- 2MB [less/more?] - primary - install Easy Boot [or LILO?] here - winxp (C:) - NTFS - 20GB - primary (I will move/resize this existing partition, using PMagic) - winxp2 (X:) - FAT [or FAT32, NTFS?] - 15GB - logical [or primary?] - linux - ext2 - 24GB - primary - swap - ext2 [or FAT, FAT32?] - 1MB - logical [or primary?] but I'm unsure about a lot of these parameters and I'm afraid of making the computer unbootable! The above layout sums up my questions - same questions in more detail below: DETAILS === Specs: Compaq v3125us, Windows XP Professional (with Service Pack 2), 60GB hard disk, 512MB RAM, and NO floppy drive. (Also: Pioneer DVR-K14 Slimline (DVD+/-RW, CD-RW), Intel Extreme Graphics 2 video chipset, ACPI power management.) I have PartitionMagic 8.0. (Note: In the questions below, I use the word partition because that's what PartitionMagic uses. I understand that in FreeBSD this is called a slice.) Yes, FreeBSD recognizes the four primary divisions and calls them slices. Withing each slice, it can be divides in to up to 8 partitions. (1) PartitionMagic says that if an OS partition starts after the boot boundary, that OS won't be bootable. It says I have boot boundaries at 2GB, and at 1024 cylinders. Most modern BIOS and boot loaders no longer have that problem. An older BIOS still might, but it is basically an obsolete thing. Does this mean I should create a small partition BEFORE my WinXP partition, to put Boot Easy or LILO there? (Apparently PartitionMagic has a command to MOVE an existing partition - so it looks like I can just move the existing WinXP partition slightly to open up some space in front of it.) I have never tried moving anything to a higher address and squeezing anything in before it. Shrinking and putting in a major division above has worked well. I don't think you have to put in a slice for those MBR utilities. They use sector 0 and extra unused space. If I do need to create a boot partition: ...(a) How big should it be? ...(b) What file system should it be - FAT, FAT32, ext2 or ext3? ...(c) Should it be a primary partition, or logical (extended)? Anybody have a preference on using LILO versus Boot Easy? Will there be a screen during the regular FreeBSD install that lets me install Boot Easy or LILO? Where do you intend to put FreeBSD? It doesn't supply Lilo or Boot Easy. Those are either Linux or third party things, not related to FreeBSD. (2) Should the file system for my Linux partition be ext2 or ext3? (3) Do I need a Linux swap partition? If so: ...(a) How big should the Linux swap partition be? (I heard it should be twice the size of my RAM. I have 512MB, so should my Linux swap partition be 1024MB?) Again, why would you ask about Linux swap on a FreeBSD list? I know some people
Re: A Riddle
On Mar 27, 2005, at 11:42 AM, [EMAIL PROTECTED] wrote: Apparently you can't read. I didn't say you were an idiot for running your own server. Can't read what? I'm not sure what line you're specifically referencing here, probably because you didn't inline the comment. But that's okay...we'll use a technique favored by trolls, and just stick your reply line wherever it is most convenient to twist the meaning! Only that you were an idiot to use your server to download tons of crap from lists that you don't want to read when for free you can have it stored elsewhere. A ton of crap? Wow...how much email do you keep in your spools, anyway? Are you running a mail server on an under-resourced system or something? If you aren't running with enough disk space for handling your domain's email, that sounds more like a violation of the competency clause in running your own mail server. I have a server, and a domain (several) and lots of other cool stuff. Like this cool Transformer, and this remote controlled boat, and this neat-o minibike my dad got me for Christmas! I got tired of wasting cpu cycles and disk space, considering that maybe 1 out of 20 messages actually interests me. Oh, the hardship of being a sysadmin for a home network...the horror! The HORROR! You guys always complain about wasted bandwidth. Well if you use yahoo or gmail or aol then you don't waste any bandwidth of your own. You just read what you want to read. I think most wasted bandwidth complaints today are veiled hints for the other person to shut up because they're wasting time. If you're running your own server and bandwidth is a premium, you already have a problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
On Mar 26, 2005, at 2:39 PM, [EMAIL PROTECTED] wrote: This is the kind of disinformation I have been referring to What in particular are you referring to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
On Mar 26, 2005, at 5:33 PM, [EMAIL PROTECTED] wrote: Yes, the theory is very nice; you've done a nice job reading Intel's marketing garb. What theory? All I see is On Mar 26, 2005, at 5:33 PM, [EMAIL PROTECTED] wrote: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem using MAKE
I'm trying to update my source tree. When I 'CD' to /usr/src and execute the command, make update I get this error make: don't know how to make update. Stop Am I missing something? Did I forget to install a port to aid in the MAKE process?? Thanks for the help in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Anthony Atkielski wrote: Ted Mittelstaedt writes: The main point I've been trying to make is that just because FreeBSD's drivers don't support whatever modification has been made in the Adaptec code on the Vectra, does not mean that the FreeBSD driver is broken or has a bug in it. When something doesn't work, it's broken. I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken? According to you, it is. According to the vast majority, it's not broken, it's merely unsupported. You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken. As you stated, you can't have it both ways. Why not just agree that both FBSD AND your hardware are broken? Oh - I know, it worked for 8 years... Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken. Can't have it both ways mate. Know the difference. -- Best regards, Chris The time it takes to rectify a situation is inversely proportional to the time it took to do the damage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: openntpd UTC problem
On Tuesday 29 March 2005 05:42, Anthony Atkielski wrote: markzero writes: Has anybody had any luck with getting OpenNTPD (net/openntpd) to work with anything other than UTC? I'm on GMT and recently we moved into daylight savings. As OpenNTPD has decided that I'm on UTC, I'm now an hour out (which is causing a few problems, as you can probably guess). UTC is the same as GMT, within a few seconds. Neither time zone observes any change in the summer months. If you want a change in summer, you might try something like WET (Western European Time), which is the same as GMT except that it switches to summer time during the summer. You can use tzsetup to pick a time zone. Remember also that your local real-time clock on your machine should be set to UTC. Not necessarily, if you run a dual-boot computer with windows you normally set your cmos clock to local time and let the less flexible OS handle the change-over. There's a sysinstall menu entry for setting your location, and type of clock, which I presumably forgot to set (one of the pitfalls of living in GMT). I had similar problems which all sorted themselves out when I ran sysinstall and rebooted. My time zone is now BST. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error installing openssh-portable
Redmond Militante [EMAIL PROTECTED] writes: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o -L. -Lopenbsd-compat/ -L/usr/lib -rpath=/usr/lib:/usr/local/lib -L/usr/local/lib -lssh -lopenbsd-compat -lcrypto -lutil -lz -lcrypt -lkrb5 -lcrypto -lcom_err -lasn1 -lroken /usr/lib/libkrb5.so: undefined reference to `des_is_weak_key' /usr/lib/libkrb5.so: undefined reference to `des_pcbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cfb64_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_set_odd_parity' /usr/lib/libkrb5.so: undefined reference to `des_read_pw_string' /usr/lib/libkrb5.so: undefined reference to `des_set_key' /usr/lib/libkrb5.so: undefined reference to `des_ede3_cbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cbc_cksum' *** Error code 1 Stop in /usr/ports/security/openssh-portable/work/openssh-3.9p1. *** Error code 1 Stop in /usr/ports/security/openssh-portable. any ideas on how to fix? cvsup'ing ports didn't work. I seem to recall DES being optional back when; you'll need to install it to get this linking. It should be in the crypto library. Or maybe my memory is just off... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dependency problem: atk-1.0.901
Bnonn [EMAIL PROTECTED] writes: Hi Lowell, thanks for your comments...I'm not trying to install via a package. I'm going into /usr/ports/x11-wm/xfce4 (or gtk20) and typing make install clean. Afaik this is how to install a port, unless I'm missing something really obvious. This is when the error occurs. I haven't tried installing using packages (pkg_add?). Okay, that's completely correct. When the make install runs, it recognizes atk 1.6.1 and has no problem with it, but then bails out later saying it can't find 1.0.91. I think we'll need to see the exact error messages. Yes, I ran cvsup on all ports, and the system, from cvsup.freebsd.org (I think that's the correct address). Had no problems doing this. Okay, so you should be up to date. I'll check uname -r when I get home and see if there appears to be a problem there. Unfortunately, that should be fine. You had me confused by talking about packages. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gcc error
On 26 Mar Kris Kennaway wrote: On Sat, Mar 26, 2005 at 04:24:42PM +0100, Dick Hoogendijk wrote: Hi, I'm getting desperate. First I couldn't compile just a gnome package. OK, it could be missed.. But now I want to compile the new KDE-3.4 and it does not work :-( Compiling kdelibs3 I get (again) this annoying error. Googling learned it shows up quit often, but I found no solution. So, what is this and waht can be done about it? I guess it's a gcc compiler error. I deleted all gcc packages that were installed (back to the systems's version - FreeBSD-4.11R). It did not help. The error I get: c++: cannot specify -o with -c or -S and multiple compilations The same error happens sometimes with 'cc' Show us the full error, not a context-free excerpt. I did, a couple of days ago. But nobody responded. In the meantime I (again) did some googling and came up with some results resambling mine. Waht I noticed was that those questions also were not replied to. /One/ reply mentioned it worthwhile to delete the /usr/ports and do a fresh install from the ports.tar.gz file ruling out corruption of Makefiles. So I did. I wiped out /usr/ports and started off fresh. Alas.. Making of x11/kdelibs3 still gave the same error (see other msg). I give up. Don't understand why others with fbsd-4.11Rp1 can compile kde34 and I cannot. All is cvsupped to the latest.. -- dick -- http://nagual.st/ -- PGP/GnuPG key: F86289CE ++ Running FreeBSD 4.11 ++ FreeBSD 5.3 + Nai tiruvantel ar vayuvantel i Valar tielyanna nu vilja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPC: Timed out
Alan Curtis [EMAIL PROTECTED] writes: I am trying to find out why I can mount my FreeBSD disk as an NFS share on one of my Macs but not the other. When I ran $ showmount -e on my FreeBSD machine, I got the expected response Exports list on localhost: /usr 192.168.1.101 192.168.1.102 which includes both the Macs. But when I ran it on my Mac $ showmount -e 192.168.1.100 I got this error RPC: Timed out: Can't do Exports rpc so I went back to the FreeBSD machine and tried again $ showmount -e localhost and now get the same error (almost) RPC: Timed out showmount: can't do exports rpc Any ideas what is wrong? Which machine works, which doesn't, and are you sure there are no firewalls involved? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Chris writes: I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? Because it works with Windows NT. If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken? No, but if the base code in the OS fails to handle the hardware properly, Windows is broken. As for drivers, it depends on the hardware. Nobody has demonstrated to me that the hardware on this machine is so exotic that it cannot be supported with standard drivers thus far. And the copy of Windows I ran came right off the shelf; it was not a tweaked version from HP (such a version came preinstalled, but the first thing I did with the hardware was wipe the hard disk). According to you, it is. According to the vast majority, it's not broken, it's merely unsupported. Same thing. And we really don't know if it's supported or not. I _still_ do not know what the messages mean, and neither does anyone else here. Everyone is just _guessing_ and freely speculating in the direction that he finds most pleasing. You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken. Yes ... except that it worked with Windows NT. Why not just agree that both FBSD AND your hardware are broken? Oh - I know, it worked for 8 years... Yes. Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken. Yes. But offhand I don't recall anything for which I was unable to obtain a Windows driver. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPC: Timed out
On Mar 29, 2005, at 9:20 AM, Lowell Gilbert wrote: Alan Curtis [EMAIL PROTECTED] writes: I am trying to find out why I can mount my FreeBSD disk as an NFS share on one of my Macs but not the other. When I ran $ showmount -e on my FreeBSD machine, I got the expected response Exports list on localhost: /usr 192.168.1.101 192.168.1.102 which includes both the Macs. But when I ran it on my Mac $ showmount -e 192.168.1.100 I got this error RPC: Timed out: Can't do Exports rpc so I went back to the FreeBSD machine and tried again $ showmount -e localhost and now get the same error (almost) RPC: Timed out showmount: can't do exports rpc Any ideas what is wrong? Which machine works, which doesn't, and are you sure there are no firewalls involved? 192.168.1.101 works, 192.168.1.102 does not. Both firewalls are off (for now for purposes of diagnosis). I think the key is something to do with why $ showmount -e localhost on the FreeBSD box sometimes works and sometimes does not. Alan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Basic grep isn't working for me
Andrew [EMAIL PROTECTED] writes: This command has always worked before, but we recently moved to a new server and now it isn't. --- su-2.05b# /usr/local/bin/keychain | grep -c existing KeyChain 2.5.1; http://www.gentoo.org/proj/en/keychain/ Copyright 2002-2004 Gentoo Foundation; Distributed under the GPL * Found existing ssh-agent (84261) 0 --- Any help would be much appreciated. It is printing its output on standard error, not standard output. In sh, you could do this by redirecting standard error onto standard output: $ keychain 21 |grep exist * Found existing ssh-agent (46206) $ but you can't do that in csh-type shells. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 27, 2005, at 7:01 PM, Anthony Atkielski wrote: Chris writes: Tell that to the MS developers then - perhaps they will listen to you. Done. What did they say? Tell them to stop producing bloated code. I've tried, but that is both a tendency of many developers (especially PC developers) and a marketing imperative. Isn't that how many FOSS projects get started...do some task more efficiently and better? Code that allows every 12 year-old on the planet to code a new back door, Trojan, or virus. Bloat alone doesn't allow that, Nope, but it sure makes it a lot simpler! Actually it helps hamper finding bugs that allow it to happen. and Microsoft code isn't any more vulnerable to this than any other code of comparable complexity for PC systems. As has been shown time and time again in Microsoft-sponsored studies comparing Windows to Linux. After removing the power supply and encasing my system in concrete, it is FAR more secure than I've ever dreamt possible, and that was with it running DOS! :-) Tell them - and once they start doing that - maybe the real technical users around the world won't snicker when they here the word, Microsoft. What does any of this have to do with FreeBSD? They're among the chorus that keeps snickering. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
k3b dvd-image burning fails.
I have trouble burning dvd-r images to dvd+r discs on freebsd 5.4. Allmost 50% of burns are failing with same error. (same images works sometimes and sometimes not). on windows I have never trouble (no single bad burn with same computer, same dvd+r drive and same media). now it always halts around 72% done with this same error message: -- 3379789824/4643059712 (72.8%) @0.0x, remaining 3:31 3379789824/4643059712 (72.8%) @0.0x, remaining 3:32 :-( write failed: Input/output error /dev/pass0: flushing cache /dev/pass0: closing track /dev/pass0: closing session growisofs comand: --- /usr/local/bin/growisofs -Z /dev/cd0=/storage/dvd-r/dvd1.img -use-the-force-luke=notray -use-the-force-luke=tty -speed=8 -- So. what could be wrong? -- kpn @ IRCnet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Anthony Atkielski wrote: Chris writes: I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? Because it works with Windows NT. If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken? No, but if the base code in the OS fails to handle the hardware properly, Windows is broken. As for drivers, it depends on the hardware. Nobody has demonstrated to me that the hardware on this machine is so exotic that it cannot be supported with standard drivers thus far. And the copy of Windows I ran came right off the shelf; it was not a tweaked version from HP (such a version came preinstalled, but the first thing I did with the hardware was wipe the hard disk). According to you, it is. According to the vast majority, it's not broken, it's merely unsupported. Same thing. And we really don't know if it's supported or not. I _still_ do not know what the messages mean, and neither does anyone else here. Everyone is just _guessing_ and freely speculating in the direction that he finds most pleasing. You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken. Yes ... except that it worked with Windows NT. Why not just agree that both FBSD AND your hardware are broken? Oh - I know, it worked for 8 years... Yes. Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken. Yes. But offhand I don't recall anything for which I was unable to obtain a Windows driver. Ok - I'm about to set the game point and win this one. Anthony, you of all people know that with NT 4, you have learned that one MUST read the HCL (Hardware Compatability List) BEFORE you try to install. That being said, you also know that if it aint on the HCL, you're SOL *Shake your head yes* Ok, now - being that you know this, did you check FBSD's version of the HCL BEFORE you installed? Did it specifically list that adapter WITH the HP/Compaq enhanced microcode? NO - It does not. So, what does that mean? That means it not listed as a supported item. What does that mean? Well - much like the HCL list of NT4, YOU are on your own. You can't argue with that - and if you can, you are showing that you are indeed out of your mind. -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem using MAKE
On Mon, 28 Mar 2005 20:21:07 -0500 (EST), Michael A. Alestock [EMAIL PROTECTED] wrote: I'm trying to update my source tree. When I 'CD' to /usr/src and execute the command, make update I get this error make: don't know how to make update. Stop Am I missing something? Did I forget to install a port to aid in the MAKE process?? Thanks for the help in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Well I am not sure about the make: don't know how to make update message. I use cvsup to update src/ports/doc. You need to add options to /etc/make.conf to use make update Here is my cvsup related options in /etc/make.conf - SUP_UPDATE=yes SUP=/usr/local/bin/cvsup # - default installation for cvsup SUPFLAGS=-g -L 2 # options for cvsup SUPHOST=cvsup.uk.freebsd.org # the server to use SUPFILE=path+filename to your src_all sup file PORTSSUPFILE=path+filename to ports_all sup file DOCSUPFILE=path+filename to doc_all sup file - Try man make.conf for more details. Good luck -- Kind regards Abu Khaled ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 28, 2005, at 3:08 PM, Anthony Atkielski wrote: Chris Warren writes: I'm not an NT fan myself, but from reading your past posts, it seems to do everything you need far better than freebsd. Why not just stick with NT/2k? Just curious. I wanted to diversify my experience. In arguing? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 28, 2005, at 9:21 AM, Anthony Atkielski wrote: Chris writes: Yay! *claps* Isn't that what Ted has been telling you to an extent - that it's the HP/Compaq microcode in the drivers? No. He and most other people have been trying to convince me that it's defective hardware, and not a deficiency of the operating system. Microcode *in the hardware*um...hello?tap tap tap This thing on? In this case, the OS is defective, because it's not doing its job. I know the job can be done because Windows NT does it. I think, correct me if I'm wrong Ted (et al), that he's saying the microcode in the hardware was modified, thus has a bug proprietary to the HP implementation of that controller, and the driver/interface in NT either didn't get the error or was *ignoring* the error, whereas FreeBSD, with a driver/interface based on the generic and marketed version of the controller, was saying HELLO, SOMETHING ISN'T RIGHT HERE!, and spewed it to the error logs. That makes it a hardware problem, unless you modify that driver to ignore the error (like NT does) or get rid of the proprietary and/or possibly failing controller in the first place. Anthony - have you ever setup a new HP/Compaq server? Ever use the SmartStart CD's? I don't remember if I ever did it myself. Compaq servers are such a nightmare that I tried to avoid dealing with them. Because they modify things so they're *almost* off the shelf, but aren't, perhaps? Among other things they do to introduce glitches? In contrast, you CAN'T (hear me again) CAN'T install Windows (shrink wrap) on the above without them. It's becasue HP/C has propriatarty drivers. That may be, but I installed an off-the-shelf retail version of Windows NT on this system, and it ran without any problems at all. If you want to keep insisting on how superior it is, then reinstall it and ignore the warnings. Why is this not an option to consider? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b dvd-image burning fails.
more to this one. /var/log/messages shows this: Mar 29 17:49:40 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065087 Mar 29 17:49:40 judaspriest kernel: ad6: FAILURE - READ_DMA timed out Mar 29 17:49:45 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065119 Mar 29 17:49:46 judaspriest kernel: ad6: FAILURE - READ_DMA timed out Mar 29 17:49:51 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065151 Mar 29 17:49:51 judaspriest kernel: ad6: FAILURE - READ_DMA timed out Mar 29 17:49:56 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065183 Mar 29 17:49:56 judaspriest kernel: ad6: FAILURE - READ_DMA timed out Mar 29 17:50:01 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065183 Mar 29 17:50:01 judaspriest kernel: ad6: FAILURE - READ_DMA timed out Mar 29 17:50:06 judaspriest kernel: ad6: TIMEOUT - READ_DMA retrying (2 retries left) LBA=280065183 Mar 29 17:50:06 judaspriest kernel: ad6: FAILURE - READ_DMA timed out and ad6 is what I'm reading image from. On Tue, 29 Mar 2005 17:43:40 +0300, Perttu Laine [EMAIL PROTECTED] wrote: I have trouble burning dvd-r images to dvd+r discs on freebsd 5.4. Allmost 50% of burns are failing with same error. (same images works sometimes and sometimes not). on windows I have never trouble (no single bad burn with same computer, same dvd+r drive and same media). now it always halts around 72% done with this same error message: -- 3379789824/4643059712 (72.8%) @0.0x, remaining 3:31 3379789824/4643059712 (72.8%) @0.0x, remaining 3:32 :-( write failed: Input/output error /dev/pass0: flushing cache /dev/pass0: closing track /dev/pass0: closing session growisofs comand: --- /usr/local/bin/growisofs -Z /dev/cd0=/storage/dvd-r/dvd1.img -use-the-force-luke=notray -use-the-force-luke=tty -speed=8 -- So. what could be wrong? -- kpn @ IRCnet -- -- kpn @ IRCnet ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading from 5.3-RELEASE-p5 to p6
On Monday 28 March 2005 16:46, you wrote: I just upgraded a test machine from 5.3-RELEASE-p5 to 5.3-RELEASE-p6. The make buildworld went fine. When I tried to make buildkernel it kept saying that: kernel build for GENERIC complete on xx.xx.xx time I tried using the old way of bulding a kernel and that went without issue. I'm bringing this up to see if it's a bug or if it's just something dorked up on my end. hrmm, I should clarify that I am doing: #make buildkernel KERNCONF=MYKERNEL -- Thanks, Josh Paetzel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 29, 2005, at 9:28 AM, Anthony Atkielski wrote: Chris writes: I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? Because it works with Windows NT. If a machine with a gig of memory runs fine under DOS but actually has a bad big of memory hardware near the 512 meg address range, it would probably still run flawlessly for a very very long time... If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken? No, but if the base code in the OS fails to handle the hardware properly, Windows is broken. But if you swap the hardware with a replacement and it works, how do you explain Windows being broken when that would suggest it was the hardware that was broken? As for drivers, it depends on the hardware. Nobody has demonstrated to me that the hardware on this machine is so exotic that it cannot be supported with standard drivers thus far. You never put it on another identical Vectra to prove it was reproducible. And the copy of Windows I ran came right off the shelf; it was not a tweaked version from HP (such a version came preinstalled, but the first thing I did with the hardware was wipe the hard disk). The problem being asserted is that the hardware was tweaked. The firmware microcode. According to you, it is. According to the vast majority, it's not broken, it's merely unsupported. Same thing. Really? Windows XP must be broken. I can't install it on my Mac. You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken. Yes ... except that it worked with Windows NT. Fine. FreeBSD is broken. Reinstall Windows and stop complaining. Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken. Yes. But offhand I don't recall anything for which I was unable to obtain a Windows driver. Because Windows is far superior in every way shape and form. You should reinstall it and leave this list. PS-if you can still get a driver for the timex Ironman triathlon watch, care to share the link? I can't seem to find it anymore for the Windows 2000 system to work without some IR interface...I wanted to use the screen to update it still...or is Windows broken because I can't use it anymore? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: supermicro 6014H-82
FYI: the problem is solved. I've installed 5.2.1-R and cvsup to 5.4-pre. All works fine for me. It seems that it is a feature of the GENERIC kernel from 5.3 / 5.4 boot cd. Thanks Hi list I've got the subj and tried to install FreeBSD. 5.3-R, 5.4-BETA1, 5.4-STABLE did not install at all. They timeouted on ATA and hang while probing asr0, but 5.2.1-R installed fine. Any suggestion? I would like to use 5.4-R. Does anybody use the subj with 5.3-R or later? Best Regards -- EMIT-RIPN, EVM7-RIPE ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 29 Mar 2005, Chris wrote: Anthony Atkielski wrote: Chris writes: I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? Because it works with Windows NT. This whole thread is about ridiculous. Does it work in XP? Does it work in Linux? Does it work on an Apple Friggin IIe? Point is, I have cards that work in FreeBSD, that dont work in XP. I have cards that work in 2000 that do not work in FreeBSD. What I do is, I search the lists for an answer. If I cant find one, then, I ask for guidance. This Anthony has searched for guidance, and, has been told to send a nice mail, with output, to the people who work on the drivers. I killfiled Anthony awhile ago, because of his senseless asinine behavior. Yet, I still get replies, because, some of Bart and Chris's comments have been pretty good. =) However, we have come full circle for the 32,767th time now, and, this thread needs to die. Therefore, Andrew is an NT Nazi, plain and simple. He will never give up on beating the dead horse that is it worked on NT. Like hitler with poland, he will not release the primitive, shortsighted, and unabashedly ignorant viewpoint that if it worked in NT, it should work in FreeBSD, and if it dosent, than FreeBSD is flawed NT uber alles! I now, in accordance with the laws of discussion threads, I invoke Godwin's law on myself, and the thread. It needs to die. Thank's for flying FreeBSD. -- Duo Although the Buddhists will tell you that desire is the root of suffering, my personal experience leads me to point the finger at system administration. --Philip Greenspun ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b dvd-image burning fails.
On Tuesday 29 March 2005 2:43 pm, Perttu Laine wrote: I have trouble burning dvd-r images to dvd+r discs on freebsd 5.4. Allmost 50% of burns are failing with same error. (same images works sometimes and sometimes not). on windows I have never trouble (no single bad burn with same computer, same dvd+r drive and same media). now it always halts around 72% done with this same error message: -- 3379789824/4643059712 (72.8%) @0.0x, remaining 3:31 3379789824/4643059712 (72.8%) @0.0x, remaining 3:32 :-( write failed: Input/output error /dev/pass0: flushing cache /dev/pass0: closing track /dev/pass0: closing session growisofs comand: --- /usr/local/bin/growisofs -Z /dev/cd0=/storage/dvd-r/dvd1.img -use-the-force-luke=notray -use-the-force-luke=tty -speed=8 -- So. what could be wrong? I can't say what causes this in k3b, but I had the same problem when using k3b. I just use the command line for growisofs now and I haven't had any problems. -- Rod If you stay the same long enough you'll be in style some day again. Cren Dog ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: k3b dvd-image burning fails.
On Tue, 29 Mar 2005 17:43:40 +0300, Perttu Laine [EMAIL PROTECTED] wrote: I have trouble burning dvd-r images to dvd+r discs on freebsd 5.4. I haven't been using k3b on FreeBSD, but you may want to report this as a bug with the port maintainer. --Nick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing IMP from ports
On Mon, Mar 28, 2005 at 09:38:28PM -0800, Ted Mittelstaedt wrote: [EMAIL PROTECTED] wrote: Hi all, I'm just trying to find out if it is currently possible to install IMP (Webmail part of the Horde project) from ports at the moment. If not, does anyone know when the dependent packages will be fixed ? Quite a few of the Pear packages seem to have been marked as BROKEN at the moment :( If not from ports, what other ways of installing IMP / Horder are advised ? TIA, did you upgrade your ports tree? Try it on a freshly installed system that you have run a portupgrade on. If that doesen't work I have notes that may help. I did an update before trying this, yeah. -- Wayne Pascoe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Bart Silverstrim writes: What did they say? MS developers are much like most other developers: it's never their fault. Isn't that how many FOSS projects get started...do some task more efficiently and better? FOSS? Nope, but it sure makes it a lot simpler! Actually it helps hamper finding bugs that allow it to happen. It depends on how the code is written, but I'll agree that most bloated code is written in great haste, with no attention at all given to the many holes that are opened by all those millions of extra lines of deadwood. As has been shown time and time again in Microsoft-sponsored studies comparing Windows to Linux. After removing the power supply and encasing my system in concrete, it is FAR more secure than I've ever dreamt possible, and that was with it running DOS! :-) There's nothing unique about Windows. But more people attack Windows, so more holes are found and exploited. Linux is rapidly catching up. And Mac OS X isn't immune, although I suspect that almost all the holes being found in OS X are in Apple's code, not the base OS. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Chris writes: Ok - I'm about to set the game point and win this one. Anthony, you of all people know that with NT 4, you have learned that one MUST read the HCL (Hardware Compatability List) BEFORE you try to install. That being said, you also know that if it aint on the HCL, you're SOL *Shake your head yes* My machine is on both the Windows and FreeBSD lists. Ok, now - being that you know this, did you check FBSD's version of the HCL BEFORE you installed? No, but I didn't check Windows' list, either. As it happens, it's on both lists. Did it specifically list that adapter WITH the HP/Compaq enhanced microcode? No. But it mentioned the machine, and it didn't list any exclusions. NO - It does not. So, what does that mean? That means it not listed as a supported item. What does that mean? Well - much like the HCL list of NT4, YOU are on your own. In other words, the FreeBSD list is worthless, since if something on the list doesn't work, one can always claim that there is some _specific_ detail about one's hardware that the list didn't _explicitly_ approve. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Bart Silverstrim writes: In arguing? In operating systems, or more specifically, UNIX versions. I considered installing Solaris, but it won't fit on my disks. I tried installing Mandrake, but it refused to get past the splash screen on installation. At least FreeBSD installed, although it won't boot on its own, and as long as I don't do any disk I/O, it runs fine. So I guess it's already ahead of Solaris and Mandrake Linux, but still way behind Windows NT. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Bart Silverstrim writes: I think, correct me if I'm wrong Ted (et al), that he's saying the microcode in the hardware was modified, thus has a bug proprietary to the HP implementation of that controller, and the driver/interface in NT either didn't get the error or was *ignoring* the error, whereas FreeBSD, with a driver/interface based on the generic and marketed version of the controller, was saying HELLO, SOMETHING ISN'T RIGHT HERE!, and spewed it to the error logs. That is 100% guesswork. You have no idea why FreeBSD generated the error messages. If you do, then tell me _exactly_ what they mean. If it's just a matter of all-wise FreeBSD detecting a bug that dopey Windows NT missed, why were there never any problems with data loss or corruption under NT, and why did NT never stall as a result of problems with the disks ... and why didn't NT ever crash? FreeBSD not only spews out error messages that nobody understands or can explain, but it stalls, and sometimes it panics. That makes it a hardware problem, unless you modify that driver to ignore the error (like NT does) or get rid of the proprietary and/or possibly failing controller in the first place. If it's an error you can ignored, it's not a hardware problem. If it's a failing controller, well, it's been failing for eight years now, and yet it still works. Because they modify things so they're *almost* off the shelf, but aren't, perhaps? A lot more than almost, I'm afraid. Among other things they do to introduce glitches? What they introduce is mainly incompatibilities. You have to do everything their way, or not at all. If you want to keep insisting on how superior it is, then reinstall it and ignore the warnings. Why is this not an option to consider? Because I'd rather run FreeBSD, if I could just get it to work. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Bart Silverstrim writes: If a machine with a gig of memory runs fine under DOS but actually has a bad big of memory hardware near the 512 meg address range, it would probably still run flawlessly for a very very long time... This machine has 384 MB of very expensive RAM, and all of it was used by Windows NT. But if you swap the hardware with a replacement and it works, how do you explain Windows being broken when that would suggest it was the hardware that was broken? I don't recall ever swapping anything. I have no reason to believe that a hardware failure has occurred. You never put it on another identical Vectra to prove it was reproducible. Why does it have to be reproducible on another machine? It doesn't work on my machine, and that's sufficient. If you can tell me what all the error messages mean, then please do so. If you can't, you're just throwing darts. The problem being asserted is that the hardware was tweaked. The firmware microcode. No assertion is worthy of my time unless it is preceded by an explanation of the exact meaning of all the error messages I'm seeing. Really? Windows XP must be broken. I can't install it on my Mac. Swap out the hardware and see if it goes away. See if you can reproduce the problem on another Mac. It's possible that Windows uses the hardware much more efficiently than the Mac OS X, and it doesn't run on your machine simply because you have a hardware failure that OS X couldn't detect. Fine. FreeBSD is broken. Reinstall Windows and stop complaining. I'd rather fix FreeBSD. PS-if you can still get a driver for the timex Ironman triathlon watch, care to share the link? I can't seem to find it anymore for the Windows 2000 system to work without some IR interface...I wanted to use the screen to update it still...or is Windows broken because I can't use it anymore? Did it ever work on Windows NT-based systems? All I recall is that it looked like a custom-written trigger for photosensitive epilepsy. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: su command problem
Thank you very much! I had checked the password file, but had been focused on the mysql account. I only just noticed that the root account was set to use /bin/csh for it's shell. When I changed it to /usr/local/bin/bash, suddenly everything started working. Thank you for your direction, I really appreciate it. Thank you to everybody who helped me on this. Insert huge sigh of relief here God Bless John --- Kevin Kinsey [EMAIL PROTECTED] wrote: John Public wrote: I'm apologize for being unclear. Let me try again. I have not modified the mysql-server.sh script in any way. The 'su -m mysql -c date' line is merely an example of what I used to see if 'su' is having a problem. All that line does is run the 'date' command as the mysql user. I used this for testing between the 5.3 system and the 5.2.1 system to see if there was a difference. Indeed there was a difference. On the 5.2.1 system the command ran 'date' w/o any problem and then returned control to the root shell, but on the 5.3 system, it su'ed me to the mysql account, but did not execute the 'date' command and stayed w/ the mysql account. This is how I have come to the conclusion that it has something to do w/ the su command or security relating to it, rather than the scripts which are used to run mysql or nagios. I guess I'm trying to determine if this is a bug in the 'su' command or if there is a security setting somewhere in 5.3 which changes the behavior of 'su'. Thanks again for your attention. John So, we need to check on a few things between the two systems; I'd start with the contents of /etc/passwd, which should be the same on both machines. FWIW, I can't reproduce the problem on 5.3 nor 4.11, as long as I'm running as root or using sudo. Running without privileges gives a Password prompt, as expected Kevin Kinsey __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Duo writes: Does it work in XP? Probably, but I'm not going to spend hundreds of euro to find out for sure. Does it work in Linux? I don't know. Mandrake seems to have a problem. I didn't try any of the other 23,441 distros of Linux. Does it work on an Apple Friggin IIe? ? Point is, I have cards that work in FreeBSD, that dont work in XP. I have cards that work in 2000 that do not work in FreeBSD. OK -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Discrepancy between ps -i -o inblk and figuring numbers by hand
On 2005-03-25 20:17, Jonathan Stewart [EMAIL PROTECTED] wrote: --- Giorgos Keramidas [EMAIL PROTECTED] wrote: On 2005-03-25 10:08, Jonathan Stewart [EMAIL PROTECTED] wrote: --- Giorgos Keramidas keramida at ceid dot upatras dot gr wrote: So, what you are looking for is a single byte count that increases sequentially for all read() and write() system calls? Pretty much, yes. To be specific all read() and write() calls for a given process. Even something that counted in 512 byte or UFUFSlocks would be useful. To what end, may I ask? Per process statistics may include byte counts from a few thousand threads that read and/or write from a few hundred descriptors. Even per file descriptor statistics quickly get useless when one considers that a single byte read may cause the read-ahead of a few thousand bytes or that a single write may reach the corresponding device several seconds later. As I mentioned in an earlier email my main use of this is really just for one program. I can do a du to find out how much information it needs to read and then by watching how much it has read get a rough idea of how much longer it will be. Not really a necessary feature just a nice to have kind of thing. I can try hacking something together, but the main difficulty of making modifications to the struct filedesc of each file descriptor is that userlevel programs need some way of getting access to this information too, i.e. through an ioctl() on the descriptor. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Tue, Mar 29, 2005 at 01:25:34PM +0200, Anthony Atkielski wrote: My point was that FreeBSD doesn't work on the machine. I wanted to know why. I still don't know why it doesn't work on the machine. Apparently nobody here really knows how FreeBSD works. So you keep saying. It probably is true that the people who maintain whichever Adaptec driver it was you're having trouble with - who I guess would 'really know how FreeBSD works' in this context - don't follow the -questions list too closely. Really, your best bet at this point is to gather up all the error messages, boot-time output, details of the BIOS/microcode versions of your adapter, etc. and file a PR. You clearly have identified a real problem, and that is the officially supported way of getting it looked at. Regards, Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
At 12:29 PM -0300 3/26/05, Alejandro Pulver wrote: Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). Let me see if I understand the situation: You have a FreeBSD box running Samba. You have Win2k boxes which connect to file shares on that FreeBSD box. When they do, the PC's can not access partitions on the FreeBSD box, unless the FreeBSD box has already accessed them. I don't quite understand the reference to NTFS. Are you saying that the *FreeBSD* box is mounting NTFS partitions, and it then makes those partitions available to the PC's via Samba? Where are those NTFS partitions located? Are they on the hard drives of the FreeBSD box? Or is the FreeBSD box mounting them from some other file server? Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? What *exactly* is your /etc/fstab file? The fact that you have directories under /mnt does not tell us anything about what filesystems you are mounting, or how they are getting mounted. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: su command problem
On Tue, 29 Mar 2005 08:25:10 -0800 (PST), John Public [EMAIL PROTECTED] wrote: Thank you very much! I had checked the password file, but had been focused on the mysql account. I only just noticed that the root account was set to use /bin/csh for it's shell. When I changed it to /usr/local/bin/bash, suddenly everything started working. It's usually considered dangerous to change root's shell outside of 'sh' or 'csh'. You may end up with a broken shell if you need to drop to single user mode. -jw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DRAC with BerkeleyDB 4.2
Hello, I recently compiled sendmail 8.13.3 for BerkeleyDB 4.2; and everything works fine, except that my pophash database (DRAC) is apparently no longer read/honored by sendmail. So, does anyone know how to compile drac-1.12_3 for use with BerkeleyDB 4.2? (FreeBSD 4.10-R). The Makefile offers no options for that. Thanks, - Mark ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Anthony Atkielski wrote: Chris writes: Ok - I'm about to set the game point and win this one. Anthony, you of all people know that with NT 4, you have learned that one MUST read the HCL (Hardware Compatability List) BEFORE you try to install. That being said, you also know that if it aint on the HCL, you're SOL *Shake your head yes* My machine is on both the Windows and FreeBSD lists. No - NOT the PC - the hardware that's in question. The Adaptec WITH the modified code. I'm willing to bet, it's not. Keep on target - don't toss other crap to divert. Stick to the one part of the hardware that IS the red hearing. Ok, now - being that you know this, did you check FBSD's version of the HCL BEFORE you installed? No, but I didn't check Windows' list, either. As it happens, it's on both lists. Again - I doubt that that perticulare Adaptec WITH the modifide code is listed. Now I'll bet an untouched Adaptec is. Did it specifically list that adapter WITH the HP/Compaq enhanced microcode? No. But it mentioned the machine, and it didn't list any exclusions. The PC is NOT the issue. The modified Adaptec IS. Stay on target, stay on target. NO - It does not. So, what does that mean? That means it not listed as a supported item. What does that mean? Well - much like the HCL list of NT4, YOU are on your own. In other words, the FreeBSD list is worthless, since if something on the list doesn't work, one can always claim that there is some _specific_ detail about one's hardware that the list didn't _explicitly_ approve. No - not worthless - NOT SUPPORTED. Just like the HCL that MS puts out. Another thing to understand, most of the HP added code is related to SNMP. That's what HP/Compaq does. Now, you also need to realize that the drivers under NT talk to HAL (Hardware Abstration Layer) which happenes to be far more forgiving of altered code then something under Unix where the driver talks directly to the hardware. Think about it. -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error installing openssh-portable
hi is /usr/ports/cryptlib the port you're referring to? i've also read that make -DWITHOUT_KERBEROS=yes would also work, but it didn't in my case. [Tue, Mar 29, 2005 at 09:14:07AM -0500] This one time, at band camp, Lowell Gilbert said: Redmond Militante [EMAIL PROTECTED] writes: hi all i get this installing the openssh-portable port on a 4.8-RELEASE machine === Building for openssh-portable-3.9.0.1,1 if test ! -z ; then /usr/bin/perl5 ./fixprogs ssh_prng_cmds ; fi (cd openbsd-compat make) cc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o -L. -Lopenbsd-compat/ -L/usr/lib -rpath=/usr/lib:/usr/local/lib -L/usr/local/lib -lssh -lopenbsd-compat -lcrypto -lutil -lz -lcrypt -lkrb5 -lcrypto -lcom_err -lasn1 -lroken /usr/lib/libkrb5.so: undefined reference to `des_is_weak_key' /usr/lib/libkrb5.so: undefined reference to `des_pcbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cfb64_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_set_odd_parity' /usr/lib/libkrb5.so: undefined reference to `des_read_pw_string' /usr/lib/libkrb5.so: undefined reference to `des_set_key' /usr/lib/libkrb5.so: undefined reference to `des_ede3_cbc_encrypt' /usr/lib/libkrb5.so: undefined reference to `des_cbc_cksum' *** Error code 1 Stop in /usr/ports/security/openssh-portable/work/openssh-3.9p1. *** Error code 1 Stop in /usr/ports/security/openssh-portable. any ideas on how to fix? cvsup'ing ports didn't work. I seem to recall DES being optional back when; you'll need to install it to get this linking. It should be in the crypto library. Or maybe my memory is just off... -- Redmond Militante Software Engineer / Medill School of Journalism FreeBSD 5.2.1-RELEASE-p13 #0: Mon Mar 28 17:07:51 CST 2005 i386 11:15AM up 45 mins, 2 users, load averages: 0.00, 0.02, 0.05 pgpXB0dpxBM4y.pgp Description: PGP signature
Re: hyper threading.
If you think that then you are either a fool or an old fool.. -Original Message- From: Anthony Atkielski [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tue, 29 Mar 2005 06:43:59 +0200 Subject: Re: hyper threading. [EMAIL PROTECTED] writes: And the circumstances that you have described have nothing to do with modern computing, so as I said, its irrelevant. The circumstances have not changed in modern computing. That's one reason why 30-year-old operating systems like UNIX remain popular. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: ATI Rage Mobility
On Tue, 29 Mar 2005 14:27:15 +0200, Tijl Coosemans [EMAIL PROTECTED] wrote: xorg's log would be nice too. It got scrubbed off, somehow... Anyways, try #2. -- Cheers, Edwin Mons ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATI Rage Mobility
On Tue, 29 Mar 2005 14:27:15 +0200, Tijl Coosemans [EMAIL PROTECTED] wrote: xorg's log would be nice too. Try #3, this time as an URL to the logs: http://edwinm.ik.nu/Xorg.0.log Cheers, Edwin Mons ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade (vs. Portmanager) question
On Mon, 28 Mar 2005, Jay O'Brien wrote: Francisco Reyes wrote: /usr/ports/sysutils/pkg_tree Interesting. Thanks! I wonder how that compares to portmanager. I have never used port manager, but pkg_tree only lets you see a tree of the ports. It doesn't help you manage them. I don't know if port manager has an equivalent. -- http://stringsutils.com Utility for developers. Compute length, MD5, CRC and more. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Anthony's drive issues.Re: ssh password delay
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bart Silverstrim Sent: Tuesday, March 29, 2005 6:51 AM To: freebsd-questions@freebsd.org Subject: Re: Anthony's drive issues.Re: ssh password delay In this case, the OS is defective, because it's not doing its job. I know the job can be done because Windows NT does it. I think, correct me if I'm wrong Ted (et al), that he's saying the microcode in the hardware was modified, thus has a bug proprietary to the HP implementation of that controller, He is saying that the microcode was modified and that we speculate that the mods contain a bug proprietary to the HP implementation of that controller. and the driver/interface in NT either didn't get the error or was *ignoring* the error, Or had whatever extra code was needed for the microcode mods. whereas FreeBSD, with a driver/interface based on the generic and marketed version of the controller, was saying HELLO, SOMETHING ISN'T RIGHT HERE!, and spewed it to the error logs. That makes it a hardware problem, unless you modify that driver to ignore the error (like NT does) or get rid of the proprietary and/or possibly failing controller in the first place. This the problem with standards, everyone's got one. Anthony - have you ever setup a new HP/Compaq server? Ever use the SmartStart CD's? I don't remember if I ever did it myself. Compaq servers are such a nightmare that I tried to avoid dealing with them. Because they modify things so they're *almost* off the shelf, but aren't, perhaps? Among other things they do to introduce glitches? Yes, they do - I've got a Compaq professional workstation on my desk at work which has a modded microcode in an Adaptec 2940U adapter card (I know it's modded because the card will not work in any other non-Compaq system, even where non-Compaq-branded 2940U cards will work) that displays similar disk strangeness (although it doesen't spew errors) This is the same scsi chipset as Anthonys Vectra. (aic7880) This incidentally is WHY I am speculating it's a microcode mod (and it was I that started this line of discussion regarding the microcode on his SCSI chipset) because I have proof positive that modded microcode in other manufacturer's aic7880-based SCSI adapters has problems with the ahc driver. In contrast, you CAN'T (hear me again) CAN'T install Windows (shrink wrap) on the above without them. It's becasue HP/C has propriatarty drivers. That may be, but I installed an off-the-shelf retail version of Windows NT on this system, and it ran without any problems at all. If you want to keep insisting on how superior it is, then reinstall it and ignore the warnings. Why is this not an option to consider? He doesen't want to run Windows (on this system at least) He wants the FreeBSD ahc driver modded so that it won't generate errors and SCSI bus resets anymore under FreeBSD. I think he thinks the way to get this done is to say the ahc driver is full of bugs and then the driver author will be so embarassed that he will fall over himself to make the mods to the ahc driver (AKA 'fix' the driver) Unfortunately, Anthony won't do the least bit of troubleshooting (such as pulling the Quantum disk and just running on the Seagate disk in this system to see if perhaps the problem is execerbated by one or the other implementations of SCSI in one or the other of the disks - granted that is a long shot, but it's within the realm of possibility it might fix it) so I doubt he would do anything that the ahc driver (who most likely isn't even subscribed to freebsd-questions) tells him to do in the way of troubleshooting either. Also long forgotten in this discussion is Anthony stated once on this list that Mandrake Linux wouldn't even install on this Vectra system either. I am not sure why he's trying to hold FreeBSD up to the driver support of Windows NT when Linux won't even talk to the card in his system. (and we all know that Windows has far better support for the oddest-ballist modifications of standard computer components such as SCSI adapters than FreeBSD does since they have unlimited money to buy oddball samples of hardware to experiment with) Ted ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Chris writes: No - NOT the PC - the hardware that's in question. The Adaptec WITH the modified code. I'm willing to bet, it's not. Should I check for restrictions on chipset temperature, relative humidity, and atmospheric pressure as well? Again - I doubt that that perticulare Adaptec WITH the modifide code is listed. Now I'll bet an untouched Adaptec is. Nothing on the list says either way. The PC is NOT the issue. The modified Adaptec IS. FreeBSD is the target, not the controller. No - not worthless - NOT SUPPORTED. Just like the HCL that MS puts out. There are lots of configurations unsupported by Microsoft that will still run Windows without problems. Another thing to understand, most of the HP added code is related to SNMP. That's what HP/Compaq does. Now, you also need to realize that the drivers under NT talk to HAL (Hardware Abstration Layer) which happenes to be far more forgiving of altered code then something under Unix where the driver talks directly to the hardware. Are you saying that Windows NT has a superior design? -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem using MAKE
On Mon, 28 Mar 2005 20:21:07 -0500 (EST), Michael A. Alestock [EMAIL PROTECTED] wrote: I'm trying to update my source tree. When I 'CD' to /usr/src and execute the command, make update I get this error make: don't know how to make update. Stop Am I missing something? Did I forget to install a port to aid in the MAKE process?? check out /etc/make.conf, or if that does not exist copy /usr/share/example/etc/make.conf to /etc. I would read this file (and do a man 5 make.conf too). In make.conf there is a section that explains using make update. -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sbp, camcontrol, and Tagged Queuing
On 3/17/2005 8:23 PM Bob Johnson wrote: On Thursday 17 March 2005 10:08 pm, Drew Tomlinson wrote: I posted this a while back and am still having the same problem. Can anyone offer any insight as to if the sbp man page suggestion about tagged queuing is something I should try? Is there any risk of screwing up my drives by trying this? Tagged queueing queues up multiple instructions for the drive simultaneously. The drive then attempts to sort them out and execute them in optimum order. Some drives that claim to support tagged queueing do not correctly do so, and don't perform well when it is used (and may lose data). If you set the queue size to one, as recommended in the passage you reference, then only one instruction will be issued to the drive at time, and it will behave like a drive without tagged queueing. It will do no harm to the drive. If the drive correctly implements tagged queueing, this will slow down the drive, but if it does not correctly implement it, then this may dramatically speed up the drive (and make it more stable). I have an external drive that manages 1.3 MBps transfers with queueing enabled, and 25 MBps transfers when I set the queue size to one. As for whether it will help your specific problem, I don't know, but I can't see how it would do any harm to test it. Using the camcontrol utility, I found these drives were already set to 1 blacklamb# camcontrol tags da2 -v (pass3:sbp0:0:0:0): dev_openings 1 (pass3:sbp0:0:0:0): dev_active0 (pass3:sbp0:0:0:0): devq_openings 1 (pass3:sbp0:0:0:0): devq_queued 0 (pass3:sbp0:0:0:0): held 0 (pass3:sbp0:0:0:0): mintags 2 (pass3:sbp0:0:0:0): maxtags 255 blacklamb# camcontrol tags da3 -v (pass4:sbp0:0:0:1): dev_openings 1 (pass4:sbp0:0:0:1): dev_active0 (pass4:sbp0:0:0:1): devq_openings 1 (pass4:sbp0:0:0:1): devq_queued 0 (pass4:sbp0:0:0:1): held 0 (pass4:sbp0:0:0:1): mintags 2 (pass4:sbp0:0:0:1): maxtags 255 Thus setting tagged queuing to 1 had no effect. Thanks again for your explanation. I sure wish I could solve this issue! Thanks, Drew This issue is not specific to FreeBSD. Any OS that supports tagged queuing has problems with some drives. - Bob [...] da2 and da3 are two IDE drives in a firewire enclosure. These are also the drives that come up referenced after restarting. What do these errors mean? How can I correct them? Is the following section from the sbp man page applicable to my situation? Some (broken) HDDs don't work well with tagged queuing. If you have prob- lems with such drives, try ``camcontrol [device id] tags -N 1'' to dis- able tagged queuing. Thanks for your help! Drew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Tue, 2005-03-29 at 20:50 +0200, Anthony Atkielski wrote: Chris writes: No - NOT the PC - the hardware that's in question. The Adaptec WITH the modified code. I'm willing to bet, it's not. Should I check for restrictions on chipset temperature, relative humidity, and atmospheric pressure as well? Of course you should - if you are running it somewhat out off the ordinary, you should check that it will run with your peculiar setup. I think a bespoke hardware modification fits the bill perfectly for out of the ordinary, and so would require extra verification. I suppose if you where to run it at high temperatues, or a very humid environment, and the os throw up some errors, that would be the OS fault as well, since your hardware is above reproach? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Ted Mittelstaedt writes: He is saying that the microcode was modified and that we speculate that the mods contain a bug proprietary to the HP implementation of that controller. What makes it a _bug_? Why would the modified firmware contain a bug ... but not FreeBSD? Or had whatever extra code was needed for the microcode mods. Yes, or approached the hardware in a way that made the modifications irrelevant. Yes, they do - I've got a Compaq professional workstation on my desk at work which has a modded microcode in an Adaptec 2940U adapter card (I know it's modded because the card will not work in any other non-Compaq system, even where non-Compaq-branded 2940U cards will work) that displays similar disk strangeness (although it doesen't spew errors) This is the same scsi chipset as Anthonys Vectra. (aic7880) And what does Compaq give you in exchange for the headache of a non-standard adapter card? Can you replace Compaq's distorted adapter with a standard one, or is it theirs or nothing? This incidentally is WHY I am speculating it's a microcode mod (and it was I that started this line of discussion regarding the microcode on his SCSI chipset) because I have proof positive that modded microcode in other manufacturer's aic7880-based SCSI adapters has problems with the ahc driver. How did you resolve the problem? He doesen't want to run Windows (on this system at least) Correct. It's a more or less spare system and I'm more interesting in getting more experience with UNIX than with getting more experience with Windows. I already know plenty about Windows. He wants the FreeBSD ahc driver modded so that it won't generate errors and SCSI bus resets anymore under FreeBSD. That would be nice, if it's a legitimate bug in the FreeBSD code (which I suspect it is). If it's a regression (i.e., a change that would break the behavior with standard hardware), then the utility of changing it is debatable (although I still wouldn't object to a version that would run on my hardware). In any case, this wonderfully fun experience is pushing me more and more in the direction of home-built hardware, and further and further away from brand-name machines. I'm glad I decided to build my own server instead of buying that IBM eSeries machine. Who knows what problems I might have had with it? Unfortunately, Anthony won't do the least bit of troubleshooting (such as pulling the Quantum disk and just running on the Seagate disk in this system to see if perhaps the problem is execerbated by one or the other implementations of SCSI in one or the other of the disks - granted that is a long shot, but it's within the realm of possibility it might fix it) so I doubt he would do anything that the ahc driver (who most likely isn't even subscribed to freebsd-questions) tells him to do in the way of troubleshooting either. Anything isn't going to do anything until someone can tell him what the existing messages are saying. I don't go pulling boards every time I see a message that I don't recognize. Also long forgotten in this discussion is Anthony stated once on this list that Mandrake Linux wouldn't even install on this Vectra system either. It stops after the splash screen, but I think that is related to the same problem that prevents FreeBSD from booting directly from disk. I am not sure why he's trying to hold FreeBSD up to the driver support of Windows NT when Linux won't even talk to the card in his system. I don't know what Linux will or won't do, and unlike you, I'm not prepared to make wild guesses. I know only that Mandrake Linux will stall after displaying a splash screen, and that's that. ... and we all know that Windows has far better support for the oddest-ballist modifications of standard computer components such as SCSI adapters than FreeBSD does since they have unlimited money to buy oddball samples of hardware to experiment with ... I suspect they just ask the vendor for information on the hardware. Even Microsoft has neither the time nor the money to test every conceivable hardware configuration. A more likely scenario is that the vendor itself writes the driver and then has Microsoft certify it. The certification is pretty rudimentary, IIRC; essentially MS ensures that the system doesn't melt or spew acrid smoke when the driver is invoked and that's about it. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to find files less than a day old?
Hello, I'm trying to write a script to concatenate a bunch of files. Basically I want to grab a bunch of files out of a directory that are less than an hour or so old and put them in one file. This is what I am using so far: find . -mtime -1 -type f | xargs cat temp.txt However, this only grabs files that are less than a day old, so I get some files returned that I don't want. I tried using -0.5 instead of -1 and it didn't work. How can I accomplish this? Thanks /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
[EMAIL PROTECTED] writes: If you think that then you are either a fool or an old fool.. I've never encountered a situation in which experience was a disadvantage. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba problems
On Tue, 29 Mar 2005 11:52:15 -0500 Garance A Drosihn [EMAIL PROTECTED] wrote: At 12:29 PM -0300 3/26/05, Alejandro Pulver wrote: Hello, I am using FreeBSD 5.3 with Samba 3.0.7,1. I can read all files from a Windows 2000 Pro. But when I try to access a mount point that is an NTFS filesystem, I have no read permission (files and directories appear as zero length files) until I access them from the server machine (like doing an 'ls'). Let me see if I understand the situation: You have a FreeBSD box running Samba. You have Win2k boxes which connect to file shares on that FreeBSD box. When they do, the PC's can not access partitions on the FreeBSD box, unless the FreeBSD box has already accessed them. Yes. I don't quite understand the reference to NTFS. Are you saying that the *FreeBSD* box is mounting NTFS partitions, and it then makes those partitions available to the PC's via Samba? Where are those NTFS partitions located? Are they on the hard drives of the FreeBSD box? Or is the FreeBSD box mounting them from some other file server? The NTFS slice I mount at '/mnt/w2k' is in the server. I only have two machines. Note: I have subdirectories under '/mnt' like 'w2k', 'wxp', 'cam', and 'tmp'. What am I doing wrong? What *exactly* is your /etc/fstab file? The fact that you have directories under /mnt does not tell us anything about what filesystems you are mounting, or how they are getting mounted. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] This is my '/etc/fstab': # DeviceMountpoint FStype Options DumpPass# /dev/ad2s4b noneswapsw 0 0 /dev/ad2s4a / ufs rw 1 1 /dev/ad2s4e /tmpufs rw 2 2 /dev/ad2s4f /usrufs rw 2 2 /dev/ad2s4d /varufs rw 2 2 devfs /devdevfs rw 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /dev/fd0/floppy msdosfs rw,noauto 0 0 /dev/ad0s5 /mnt/w2kntfsro 0 0 /dev/ad0s1 /mnt/wxpmsdosfs rw 0 0 /dev/ad2s1 /mnt/debext2fs rw,noauto 0 0 /dev/da0s1 /mnt/cammsdosfs rw,noauto 0 0 procfs /proc procfs rw 0 0 linprocfs /compat/linux/proc linprocfs rw 0 0 Please see the complete thread (there is more information there). Thanks and Best Regards, Ale ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Or had whatever extra code was needed for the microcode mods. Yes, or approached the hardware in a way that made the modifications irrelevant. And how do you write software that will be able to communicate with hardware, irrelevent of what changes have been made to that hardware? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Anthony Atkielski wrote: Chris writes: No - NOT the PC - the hardware that's in question. The Adaptec WITH the modified code. I'm willing to bet, it's not. Should I check for restrictions on chipset temperature, relative humidity, and atmospheric pressure as well? Be realistic Anthony - you know full well that if an item is not listed, its not supported. You know this because you use Windows (NT to be exact) for many, many years. Don't play symantics. Again - I doubt that that perticulare Adaptec WITH the modifide code is listed. Now I'll bet an untouched Adaptec is. Nothing on the list says either way. If' it's not listed - it's not supported - isnt that what MS drills into its user base? The PC is NOT the issue. The modified Adaptec IS. FreeBSD is the target, not the controller. No - not worthless - NOT SUPPORTED. Just like the HCL that MS puts out. There are lots of configurations unsupported by Microsoft that will still run Windows without problems. This isnt the argument - the argument is what I defined it as - and yet again, you want to squirm your way out of it with symantical crap. You simply can't argue the fact one way and have it not work the other. Another thing to understand, most of the HP added code is related to SNMP. That's what HP/Compaq does. Now, you also need to realize that the drivers under NT talk to HAL (Hardware Abstration Layer) which happenes to be far more forgiving of altered code then something under Unix where the driver talks directly to the hardware. Are you saying that Windows NT has a superior design? Stop turning shit around when you get pinned up against a wall. As I mentioned, I presented you with the reality from an MS point of view. You need to realize that you need to retire this whole thread. BTW - as Ted asked, why are you NOT persuing this so rabbidly with Mandrake? Perhaps your a secret agent for Linux? -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re: ATI RAGE Mobility
On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? from kernel LINT file # DRM options: # mgadrm:AGP Matrox G200, G400, G450, G550 # tdfxdrm: 3dfx Voodoo 3/4/5 and Banshee # r128drm: ATI Rage 128 # radeondrm: ATI Radeon up to 9000/9100 # DRM_DEBUG: include debug printfs, very slow # # mga requires AGP in the kernel, and it is recommended # for AGP r128 and radeon cards. device mgadrm device r128drm device radeondrm device tdfxdrm options DRM_DEBUG You may need to add the device mgadrm Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ATI RAGE Mobility
Sorry, Rage mobility is mach64... you're trying to use a rage128/radeon driver. That won't work. There is some preliminary mach64 support but you have to build it yourself. It really sucks, it's not so worth it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Busby Sent: Tuesday, March 29, 2005 11:23 AM To: freebsd-questions@freebsd.org Subject: re: ATI RAGE Mobility On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? from kernel LINT file # DRM options: # mgadrm:AGP Matrox G200, G400, G450, G550 # tdfxdrm: 3dfx Voodoo 3/4/5 and Banshee # r128drm: ATI Rage 128 # radeondrm: ATI Radeon up to 9000/9100 # DRM_DEBUG: include debug printfs, very slow # # mga requires AGP in the kernel, and it is recommended # for AGP r128 and radeon cards. device mgadrm device r128drm device radeondrm device tdfxdrm options DRM_DEBUG You may need to add the device mgadrm Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATI RAGE Mobility
On Tue, 29 Mar 2005 14:28:19 -0800, Andrew Heyn [EMAIL PROTECTED] wrote: Sorry, Rage mobility is mach64... you're trying to use a rage128/radeon driver. That won't work. There is some preliminary mach64 support but you have to build it yourself. It really sucks, it's not so worth it. I built it myself, but it ain't working... Edwinm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Is there any way you guys could take this idiotic conversation off-list? It's a complete waste time for the vast majority of us. Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
Thats because you seem unable to grasp modern concepts. If you think that performance criteria of modern controllers and processors are the same as 30 years ago, then you are incapable of commenting on anything modern. Every controller/processor is different and has its own advantages and inefficiencies. The fact that you can make ignorant statements like I proved polling is faster because 20 years ago I wrote a driver, then you think that you know things that you don't. -Original Message- From: Anthony Atkielski [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tue, 29 Mar 2005 21:02:40 +0200 Subject: Re: hyper threading. [EMAIL PROTECTED] writes: If you think that then you are either a fool or an old fool.. I've never encountered a situation in which experience was a disadvantage. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD on Bochs
On Tue, Mar 29, 2005 at 05:57:23PM +0800, jumbler chi wrote: Hi All: I have a question about Freebsd on bochs. I'm interesting to build owner Freebsd scratch. Due the hardware limited , I want to run this scratch on Bochs. Therefore , I refered a article , http://sig9.com/articles/freebsd-on-bochs , to build a image under 5.2R. when I booted the image file under Bochs-2.0.2 .. it stoped on a prompt , mountroot . This doesn't address you're question directly, but I'd like to point out that I've had very good luck with FreeBSD under qemu, and it feels much faster than Bochs did. Regards Jumbler ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] -- Brian Reichert [EMAIL PROTECTED] 55 Crystal Ave. #286Daytime number: (603) 434-6842 Derry NH 03038-1725 USA BSD admin/developer at large ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to find files less than a day old?
On Tue, 29 Mar 2005 13:02:37 -0600 (CST), Brian John [EMAIL PROTECTED] wrote: Hello, I'm trying to write a script to concatenate a bunch of files. Basically I want to grab a bunch of files out of a directory that are less than an hour or so old and put them in one file. This is what I am using so far: find . -mtime -1 -type f | xargs cat temp.txt However, this only grabs files that are less than a day old, so I get some files returned that I don't want. I tried using -0.5 instead of -1 and it didn't work. How can I accomplish this? find . -mtime -1h -type f man find -- Noel Jones ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
Stop feeding this troll, he has been banned from de DragonFly BSD list for his stupid comments, his e-mail address doesn't even exist. His only goal is make the longest thread of messages in history. Stop him! On Tue, 29 Mar 2005 14:54:30 -0500, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thats because you seem unable to grasp modern concepts. If you think that performance criteria of modern controllers and processors are the same as 30 years ago, then you are incapable of commenting on anything modern. Every controller/processor is different and has its own advantages and inefficiencies. The fact that you can make ignorant statements like I proved polling is faster because 20 years ago I wrote a driver, then you think that you know things that you don't. -Original Message- From: Anthony Atkielski [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tue, 29 Mar 2005 21:02:40 +0200 Subject: Re: hyper threading. [EMAIL PROTECTED] writes: If you think that then you are either a fool or an old fool.. I've never encountered a situation in which experience was a disadvantage. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- Guillermo García Rojas Covarrubias Director General SoloBSD http://www.solobsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: ATI RAGE Mobility
I would like to state that at one point, I did get this to work. This was also a long time ago, when the patches mentioned in some of the proceeding links had to be done.. (which were and probably still are XFree86 specific) http://people.freebsd.org/~anholt/dri/news.html http://am-productions.biz/docs/fujitsu-p2110.php leads to http://dri.freedesktop.org/wiki/Building I noticed that I had to make sure I rebuilt mach64.ko and some of the X libraries regarding dri if I was to upgrade the kernel. Note this from the Wiki: The DRM is shipped with the kernel, so you shouldn't need to build it. If you choose to, simply run make make install from the drm/bsd directory. This is contrary to the suggestion to install ports/graphics/drm. The building referred to above is within the X tree. The history to the mach64 dri support may be of interest: http://people.freebsd.org/~anholt/dri/news.html (already gave this link) You can always (if you are patient) contact anholt who is rather busy on freenode.net in #dri. Beware, I asked a question there, and fixed it myself before I got an answer. Hope this helps more than my other post. It still sucked pretty bad once I got DRI working with my mach64, but... It was better... Thanks! Andrew -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Busby Sent: Tuesday, March 29, 2005 11:23 AM To: freebsd-questions@freebsd.org Subject: re: ATI RAGE Mobility On Monday 28 March 2005 20:25, Edwin Mons wrote: On Mon, 28 Mar 2005 20:20:50 +0200, Edwin Mons wrote: I'm trying to enable DRI on my IBM ThinkPad A20m, which has an ATI Rage Mobility P/M AGP 2x rev 100 GPU onboard. I succesfully installed the mach64 DRM module, which shows the following lines in my dmesg: drm0: Rage Mobility P/M AGP 2X port 0x2000-0x20ff mem 0xf420-0xf4200fff,0xf500-0xf5ff irq 11 at device 0.0 on pci1 info: [drm] AGP at 0xf800 64MB info: [drm] Initialized mach64 1.0.0 20020904 on minor 0 However, when I start X.org 6.8.2, it doesn't show anything about DRM in the logfiles (attached). glxinfo reports it doesn't use Direct Rendering as well. Attached is my xorg.conf, as well. My questions: 1) does anybody know if it is possible to have DRI on this configuration at all, and 2) how does one get it to work? from kernel LINT file # DRM options: # mgadrm:AGP Matrox G200, G400, G450, G550 # tdfxdrm: 3dfx Voodoo 3/4/5 and Banshee # r128drm: ATI Rage 128 # radeondrm: ATI Radeon up to 9000/9100 # DRM_DEBUG: include debug printfs, very slow # # mga requires AGP in the kernel, and it is recommended # for AGP r128 and radeon cards. device mgadrm device r128drm device radeondrm device tdfxdrm options DRM_DEBUG You may need to add the device mgadrm Hope it helps. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPC: Timed out
On Mar 28, 2005, at 8:53 PM, Alan Curtis wrote: $ showmount -e 192.168.1.100 I got this error RPC: Timed out: Can't do Exports rpc so I went back to the FreeBSD machine and tried again $ showmount -e localhost and now get the same error (almost) RPC: Timed out showmount: can't do exports rpc Any ideas what is wrong? Are both portmap and mountd running on that host? Do you have a firewall in the way? -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to find files less than a day old?
On Tue, 29 Mar 2005 13:02:37 -0600 (CST), Brian John [EMAIL PROTECTED] wrote: Hello, I'm trying to write a script to concatenate a bunch of files. Basically I want to grab a bunch of files out of a directory that are less than an hour or so old and put them in one file. This is what I am using so far: find . -mtime -1 -type f | xargs cat temp.txt However, this only grabs files that are less than a day old, so I get some files returned that I don't want. I tried using -0.5 instead of -1 and it didn't work. How can I accomplish this? find . -mtime -1h -type f man find -- Noel Jones ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] I read the man page and didn't see that. It doesn't appear to work on the box that I am ssh-ing to. Sorry, I should have mentioned that it is not a FreeBSD box that I am connected to. I think it may be a Solaris 9 box. Is there any way to get this to work in Solaris? Thanks /Brian ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with man
I've got a server that I just recently upgraded to the latest of everything, but for some reason when you type man and then what you want to look at the manual for I get this error: man: unable to find the file /etc/manpath.config I've looked under /etc and it's there and it's not corrupt or anything. So what might be wrong? Would this be a file system issue because the box DID reboot while it was registering the upgrade for bash. I've tried under CSH and TCSH and it's the same problem. Is there any way to fix this or is this a sign of a much larger issue? Any pointers would be nice. Oh, and please reply directly to me. I don't subscribe directly to this list. Thanks. Steven Lake -Owner/Webmaster Raiden's Realm www.raiden.net Come see Monk the comic strip and laugh till you die! :) http://www.raiden.net/Monk/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
You are wrong about just about everything, I unsubscribed because dragonfybsd is more than a year away from being usable in a commercial environment and memory fails when you shock it with a heavy load. And I'm pretty sure my email exists. My goal is to seek intelligent life. Its a long journey. -Original Message- From: Guillermo Garcia-Rojas [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tue, 29 Mar 2005 14:03:15 -0600 Subject: Re: hyper threading. Stop feeding this troll, he has been banned from de DragonFly BSD list for his stupid comments, his e-mail address doesn't even exist. His only goal is make the longest thread of messages in history. Stop him! On Tue, 29 Mar 2005 14:54:30 -0500, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thats because you seem unable to grasp modern concepts. If you think that performance criteria of modern controllers and processors are the same as 30 years ago, then you are incapable of commenting on anything modern. Every controller/processor is different and has its own advantages and inefficiencies. The fact that you can make ignorant statements like I proved polling is faster because 20 years ago I wrote a driver, then you think that you know things that you don't. -Original Message- From: Anthony Atkielski [EMAIL PROTECTED] To: freebsd-questions@freebsd.org Sent: Tue, 29 Mar 2005 21:02:40 +0200 Subject: Re: hyper threading. [EMAIL PROTECTED] writes: If you think that then you are either a fool or an old fool.. I've never encountered a situation in which experience was a disadvantage. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- --- Guillermo García Rojas Covarrubias Director General SoloBSD http://www.solobsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 29, 2005, at 11:09 AM, Anthony Atkielski wrote: Bart Silverstrim writes: What did they say? MS developers are much like most other developers: it's never their fault. From the way you were complaining, I had the impression that MS was bending backwards to help in issues while the FreeBSD people were immature children. Is this evidence to the contrary, that MS isn't the pinnacle of perfection in dealing with every software issue? Isn't that how many FOSS projects get started...do some task more efficiently and better? FOSS? http://en.wikipedia.org/wiki/FLOSS http://www.dwheeler.com/oss_fs_why.html http://www.dwheeler.com/oss_fs_refs.html Nope, but it sure makes it a lot simpler! Actually it helps hamper finding bugs that allow it to happen. It depends on how the code is written, but I'll agree that most bloated code is written in great haste, with no attention at all given to the many holes that are opened by all those millions of extra lines of deadwood. Especially in projects driven by money and politics in a workplace, and with looming deadlines. You can do the job to get it shoved out the door or do the job right. In the practical world, you end up shoving it out the door 99% of the time. In a world where you do it as a hobby in spare time, it takes longer, but there's far more leeway to do it right instead of just shoving it out the door. It happens, as with everything else, that there are exceptions but the primary reason for the shoving to happen isn't as great. As has been shown time and time again in Microsoft-sponsored studies comparing Windows to Linux. After removing the power supply and encasing my system in concrete, it is FAR more secure than I've ever dreamt possible, and that was with it running DOS! :-) There's nothing unique about Windows. But more people attack Windows, so more holes are found and exploited. Linux is rapidly catching up. And Mac OS X isn't immune, although I suspect that almost all the holes being found in OS X are in Apple's code, not the base OS. A) No OS is immune, because they are 1) complicated, thus have bugs and 2) are used by people, so stupid social engineering tricks (see anna kournikova nude!) will get idiots to click click on things they shouldn't be click clicking on B) The More popular thus more exploited is a crap argument. Why? Ask the three little pigs. Any twit can build a shelter that is architecturally poor but cheap, so it falls apart or is broken into easily. Notice how quakes can do a LOT more damage in areas where buildings are not built to withstand the tremors, while other places like San Francisco, where people spend huge amounts of money in research and proper implementation, limit the damage a similar quake would inflict? Windows was designed for single user non-network desktops. It was extended to encompass the current network-is-the-rule environment. It's legacy shows. That 30 year old UNIX was better designed for network sharing and multiple users in scant resources. It has since been extended and modified, but the legacy shows. The more popular thus more exploited just means there are more targets available. Spreading a limited-target virus has BEEN DONE; it was targeting a specific vendor's firewall product, and it inflicted a noticeable amount of damage on the Internet in the form of bandwidth stealing and because of the rapid spread of higher-bandwidth connections, the number of targets available isn't quite such a big deal. It only takes a small number to be able to saturate connections and inflict damage. I'd dig out AGAIN the research paper summarizing the attack and it's affects, but I'm sure that the intended audience wouldn't bother reading it anyway. Search for it yourself if you're such a big boy and everyone else is too immature to know about this sort of idea. If apologists would get their heads out of their butts they'd see that it isn't always There's more Windows, thus easier to exploit!, it's Windows' design is inherently less secure, so it's easier to target!, as well as a healthy dose of the average Windows user is more clueless than the average Linux user! thrown in to boot. Many of the features in the recent The Road to Windows Longhorn 2005 article on Paul Thurrott's Supersite for Windows seems oddly to match many of the features already available on OS X...Hmm, wonder why...could it be because of the security imposed by UNIX under OS X that makes that kind of model a decent tradeoff of usability and security in the first place? If it wasn't such a pain in the butt for Joe Sixpack to use, ideas in EROS would help a helluva lot more on the desktop for security. Security is an inconvenience. Users want mindless interactions. Somewhere it meets in the middle in order to be usable. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To
Re: Anthony's drive issues.Re: ssh password delay
Martin McCann writes: And how do you write software that will be able to communicate with hardware, irrelevent of what changes have been made to that hardware? The hardware and software must agree on a minimum set of standards. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
Chris writes: Be realistic Anthony - you know full well that if an item is not listed, its not supported. But it _is_ listed. And unsupported is not synonymous with doesn't work. If' it's not listed - it's not supported - isnt that what MS drills into its user base? Only if they call for support. Even then, they can still get suggestions, sometimes--but MS won't commit to anything on unsupported hardware. You need to realize that you need to retire this whole thread. BTW - as Ted asked, why are you NOT persuing this so rabbidly with Mandrake? I'm not that interested in running Linux. Linux is for kids. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: hyper threading.
[EMAIL PROTECTED] writes: Thats because you seem unable to grasp modern concepts. None were under discussion. If you think that performance criteria of modern controllers and processors are the same as 30 years ago, then you are incapable of commenting on anything modern. The principles of modern controllers are surprisingly similar to those of old controllers. The biggest change is that the PC world is only now discovering what mainframe designers knew 40 years ago. -- Anthony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to find files less than a day old?
On Tue, 29 Mar 2005 14:11:45 -0600 (CST), Brian John
[EMAIL PROTECTED] wrote:
On Tue, 29 Mar 2005 13:02:37 -0600 (CST), Brian John
[EMAIL PROTECTED] wrote:
Hello,
I'm trying to write a script to concatenate a bunch of files.
Basically I
want to grab a bunch of files out of a directory that are less than an
hour or so old and put them in one file.
This is what I am using so far:
find . -mtime -1 -type f | xargs cat temp.txt
However, this only grabs files that are less than a day old, so I get
some
files returned that I don't want. I tried using -0.5 instead of -1
and it
didn't work. How can I accomplish this?
find . -mtime -1h -type f
man find
--
Noel Jones
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
I read the man page and didn't see that. It doesn't appear to work on the
box that I am ssh-ing to. Sorry, I should have mentioned that it is not a
FreeBSD box that I am connected to. I think it may be a Solaris 9 box.
Is there any way to get this to work in Solaris?
Maybe the solaris find command supports the -newer option. I think
-newer is more widely supported, and likely to be available on
Solaris.
If necessary, you could then create a reference file using touch with
the proper time stamp on it. You can do this automatically within a
script, using the date command to figure out the current time. You
can calculate the time one hour ago by using a command something like
TZ={your timezone + 1} date
--
Noel Jones
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to find files less than a day old?
On Tue, 29 Mar 2005 14:11:45 -0600 (CST), Brian John
[EMAIL PROTECTED] wrote:
On Tue, 29 Mar 2005 13:02:37 -0600 (CST), Brian John
[EMAIL PROTECTED] wrote:
Hello,
I'm trying to write a script to concatenate a bunch of files.
Basically I
want to grab a bunch of files out of a directory that are less
than an
hour or so old and put them in one file.
This is what I am using so far:
find . -mtime -1 -type f | xargs cat temp.txt
However, this only grabs files that are less than a day old, so I get
some
files returned that I don't want. I tried using -0.5 instead of -1
and it
didn't work. How can I accomplish this?
find . -mtime -1h -type f
man find
--
Noel Jones
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
I read the man page and didn't see that. It doesn't appear to work on
the
box that I am ssh-ing to. Sorry, I should have mentioned that it is
not a
FreeBSD box that I am connected to. I think it may be a Solaris 9 box.
Is there any way to get this to work in Solaris?
Maybe the solaris find command supports the -newer option. I think
-newer is more widely supported, and likely to be available on
Solaris.
If necessary, you could then create a reference file using touch with
the proper time stamp on it. You can do this automatically within a
script, using the date command to figure out the current time. You
can calculate the time one hour ago by using a command something like
TZ={your timezone 1} date
--
Noel Jones
Is there a way that I could do this without using find? I basically just
need a listing of files to pipe to cat. Is there any easier way to do
this? If there isn't, could you explain in more explicit email how to
this?
/Brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anthony's drive issues.Re: ssh password delay
On Mar 29, 2005, at 11:18 AM, Anthony Atkielski wrote: Bart Silverstrim writes: I think, correct me if I'm wrong Ted (et al), that he's saying the microcode in the hardware was modified, thus has a bug proprietary to the HP implementation of that controller, and the driver/interface in NT either didn't get the error or was *ignoring* the error, whereas FreeBSD, with a driver/interface based on the generic and marketed version of the controller, was saying HELLO, SOMETHING ISN'T RIGHT HERE!, and spewed it to the error logs. That is 100% guesswork. You have no idea why FreeBSD generated the error messages. If you do, then tell me _exactly_ what they mean. It's deduction. If you want someone to pinpoint on the nailhead what is wrong without troubleshooting, go to a psychic. If it's just a matter of all-wise FreeBSD detecting a bug that dopey Windows NT missed, why were there never any problems with data loss or corruption under NT, and why did NT never stall as a result of problems with the disks ... and why didn't NT ever crash? FreeBSD not only spews out error messages that nobody understands or can explain, but it stalls, and sometimes it panics. I'd speculate that there's a difference in the driver, but that would be just more guesswork, and since neither you nor anyone on the list is able/willing to get another system exactly like yours to install it on to rule out hardware failure (you know, *reproducing the bug*?), then I guess you're SOL. That makes it a hardware problem, unless you modify that driver to ignore the error (like NT does) or get rid of the proprietary and/or possibly failing controller in the first place. If it's an error you can ignored, it's not a hardware problem. Really? I have a free program running on my NT machines, ntpdate I believe is the name, that just hammers the registry with requests constantly. I'd never have known it was querying it so much if it wasn't for regmon. *Contant* hits. dunno why, doesn't seem to hurt anything...thus I ignore it. NT doesn't seem to care. Only gets in the way when I'm troubleshooting registry errors. I've already told you I had a scsi bus reset problem what showed up under Linux but not NT several years ago. But you probably ignored that. If it's a failing controller, well, it's been failing for eight years now, and yet it still works. I've had power supply fans that have lasted for years despite making odd noises that are indicative of impending failure. It's not unheard of. Because they modify things so they're *almost* off the shelf, but aren't, perhaps? A lot more than almost, I'm afraid. You said previously with the microcode version that it WAS NOT off-the-shelf. It was an HP-branded firmware. When asked about the HCL, you insisted on the controller, not to my recollection the entire machine as you have it configured on the HCL. Which is it? If it lists the controller generically in the HCL, go get an off-the-shelf controller and put it in so the firmware code ISN'T proprietarily altered then start bitching the list. Among other things they do to introduce glitches? What they introduce is mainly incompatibilities. You have to do everything their way, or not at all. What did you think I meant by glitches? Do you prefer gotchas? If you want to keep insisting on how superior it is, then reinstall it and ignore the warnings. Why is this not an option to consider? Because I'd rather run FreeBSD, if I could just get it to work. That's nice. Some hardware is being a pain. People here either ignore you at this point or tell you to replace that controller and/or disks and see what it takes from there. You refuse and insist people sit down and trace the error for an eight-year-old set of hardware that has proprietary extensions. While they're at it, why don't they get FreeBSD to run on my TiVO. Just need to alter a few drivers here and there... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to find files less than a day old?
It doesn't appear to work on my FreeBSD box, either. What does work is this:
find /var/log -newerct '1 hour ago' -exec cat {} /var/tmp/filename \;
Jerry
http://www.syslog.org
I read the man page and didn't see that. It doesn't appear to work on the
box that I am ssh-ing to. Sorry, I should have mentioned that it is not a
FreeBSD box that I am connected to. I think it may be a Solaris 9 box.
Is there any way to get this to work in Solaris?
Thanks
/Brian
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
