Job Offer
Storistes de France is currently looking for English Corrections
Officer. We currently need three english corrections officer, someone
who can edit our customer service messages and correct errors in our
english customer service messages.
This is an opportunity is open to anyone who know how to write english
without errors and someone who can correct mistakes/errors in English
Language and we also need someone who will be working as our agent.
You are required to work for one hour daily by checking your email for
our customer service message and edit it because of correction and
other english errors.
WHAT WE EXPECT FROM A CANDIDATE:
- Applicants must be living in USA,Canada or Australia.
- Applicants must be high school or vocational high school graduates.
- Above 18 years old.
- Confident computer skills.
- Applicants must be avaliable to check his/her e-mail messages
between 7am - 12noon.
- Good working relationship with new people.
- Required to be online at least 1-3hours and 2 days per week.
WHAT WE OFFER
- Speedy career progress
- High earnings plus performance results bonus.
- A Personal Toshiba Laptop.
- Weekly payment of $250.00.
- Monthly Salary : Starting from $10,000 - $55,000.00.
To apply please send your CV/Resume to our email:
[EMAIL PROTECTED]
Milla Cole
Storistes de France
Website: http://www.storistes-de-france.com/
___
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 capture freebsd 6.3 kernel panics
[EMAIL PROTECTED]@mgEDV.net wrote: hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... I recently had a system that would not dump to the swap partition for one reason or the other. I used an external USB hard disk, and it dumped there with no problems. With the current sizes of cheap usb flash drives, even that is probably an option. You may wish to explore this solution. Manolis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to capture freebsd 6.3 kernel panics
hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Job Offer
Storistes de France is currently looking for English Corrections
Officer. We currently need three english corrections officer, someone
who can edit our customer service messages and correct errors in our
english customer service messages.
This is an opportunity is open to anyone who know how to write english
without errors and someone who can correct mistakes/errors in English
Language and we also need someone who will be working as our agent.
You are required to work for one hour daily by checking your email for
our customer service message and edit it because of correction and
other english errors.
WHAT WE EXPECT FROM A CANDIDATE:
- Applicants must be living in USA,Canada or Australia.
- Applicants must be high school or vocational high school graduates.
- Above 18 years old.
- Confident computer skills.
- Applicants must be avaliable to check his/her e-mail messages
between 7am - 12noon.
- Good working relationship with new people.
- Required to be online at least 1-3hours and 2 days per week.
WHAT WE OFFER
- Speedy career progress
- High earnings plus performance results bonus.
- A Personal Toshiba Laptop.
- Weekly payment of $250.00.
- Monthly Salary : Starting from $10,000 - $55,000.00.
To apply please send your CV/Resume to our email:
[EMAIL PROTECTED]
Milla Cole
Storistes de France
Website: http://www.storistes-de-france.com/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vi+urxvt8.9+oxim for traditional chinese, HOW??
some are displayed correctly, but some are wrong, still looks like \XX\XX, feel like not all the characters are not well represented TFC On Jan 30, 2008 11:30 PM, Edward G.J. Lee [EMAIL PROTECTED] wrote: On Wed, Jan 30, 2008, Tsu-Fan Cheng wrote: Hi, I use rxvt-unicode8.9+oxim, want to vi a text document in tradictional chinese. I have locale set as LC_CTYPE=zh_TW.UT-8. I first have my input looks like xx/xx/. Then I set LC_CTYPE to en_US.ISO8859-1, I got nothing. How should I get this done?? thank you!! Try, env LC_ALL=en_US.ISO8859-1 vi or if you are using sh/bash LC_ALL=en_US.ISO8859-1 vi Edward ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Panics with GEOM
Hello.
Not sure this belongs to questions, but I'm in need of urgent help.
Please advise where to post if this is not appropriate.
An amd64/SMP server of mine worked quite reliably for some times.
Now I added two more disks and created a gmirror with them; from that
point on it experienced locks, crash and panics.
Since it was a 6.2 at the time, I immediately upgraded to 6.3: this did
not solve, but, at least, the box would reboot and get me a crash dump.
So here it is: looks like the i/o subsystem has problems, so the two
disk might really be related, but still, I'm not sure.
# kgdb kernel.debug /var/crash/vmcore.5
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined
symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x50006
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x8020e076
stack pointer = 0x10:0xa831c7a0
frame pointer = 0x10:0xa831c7e0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 88587 (clamscan)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 3d8h32m39s
Dumping 1023 MB (2 chunks)
chunk 0: 1MB (151 pages) ... ok
chunk 1: 1023MB (261744 pages) 1007 991 975 959 943
110ipfw: 65534 Deny TCP 192.168.101.1:58319 192.168.101.4:54663 in via fxp0
110ipfw: 65534 Deny TCP 192.168.101.1:58319 192.168.101.4:54663 in via fxp0
927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639
623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319
303 287 271 255 239 223 207 191 175panic: ahd_run_qoutfifo recursion
cpuid = 1
159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:172
172 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x80257115 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0x80257825 in panic (fmt=0xff00110e9980 X\023\021\021) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0x803b50c6 in trap_fatal (frame=0xc, eva=18446742974484093312) at
/usr/src/sys/amd64/amd64/trap.c:669
#4 0x803b546d in trap_pfault (frame=0xa831c6f0, usermode=0) at
/usr/src/sys/amd64/amd64/trap.c:580
#5 0x803b56cd in trap (frame=
{tf_rdi = -1098891843040, tf_rsi = -1098516260992, tf_rdx =
-1098692440992, tf_rcx = 1, tf_r8 = 0, tf_r9 = 327686, tf_rax = 2048, tf_rbx =
-1098891843040, tf_rbp = -1473132576, tf_r10 = -1098978658048, tf_r11 =
-1098938410752, tf_r12 = -1098516260992, tf_r13 = 327686, tf_r14 =
-1098891842864, tf_r15 = -1705935624, tf_trapno = 12, tf_addr = 327686,
tf_flags = 1108101564416, tf_err = 0, tf_rip = -2145329034, tf_cs = 8,
tf_rflags = 66178, tf_rsp = -1473132624, tf_ss = 16}) at
/usr/src/sys/amd64/amd64/trap.c:353
#6 0x8039c49b in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:168
#7 0x8020e076 in g_io_request (bp=0xff0024f12a20,
cp=0xff003b541780) at /usr/src/sys/geom/geom_io.c:275
#8 0x803709ad in ufs_strategy (ap=0xff0024f12a20) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:1973
#9 0x803e5549 in VOP_STRATEGY_APV (vop=0x805702c0,
a=0xa831c840) at vnode_if.c:1796
#10 0x802b510c in bufstrategy (bo=0xff0024f12a20,
bp=0xff003b541780) at vnode_if.h:928
#11 0x802b4575 in breadn (vp=0xff000a55eba0, blkno=-1098516260992,
size=819186784, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0x800) at
buf.h:426
#12 0x802b48fe in bread (vp=0xff0024f12a20, blkno=-1098516260992,
size=819186784, cred=0x1, bpp=0x0) at /usr/src/sys/kern/vfs_bio.c:723
#13 0x80363886 in ffs_read (ap=0xff0024f12a20) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:523
#14 0x803e3efa in VOP_READ_APV (vop=0x800, a=0xff003b541780) at
vnode_if.c:643
#15 0x80370649 in ufs_readdir (ap=0xa831cad0) at vnode_if.h:343
#16 0x803e419d in VOP_READDIR_APV (vop=0x800, a=0xff003b541780) at
vnode_if.c:1427
#17 0x802d0657 in getdirentries (td=0xff00110e9980,
uap=0xa831cbc0) at vnode_if.h:746
#18 0x803b6052 in syscall (frame=
{tf_rdi = 4, tf_rsi = 58564608, tf_rdx = 4096, tf_rcx = 58550056, tf_r8 =
0, tf_r9 = 140737488347784, tf_rax = 196, tf_rbx = 58550016, tf_rbp = 58550016,
Re: CVSup update or upgrade
On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: NOTE: I don't use mergemaster unless I go from say 6.3 to 7.0 Not wise. New features and fixes are applied to configuration files and rc scripts regu;arly. You'll probably miss them. STABLE is the security fix branch. Wrong. According to the handbook: 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. RELENG_6 is STABLE RELENG_6_3 is for security fixes regards, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 915resolution on HP Compaq
Mike Barnard wrote: Thanks Doug, I have always been a sceptic when it comes to running the CURRENT branch, but i guess there is a first time for everything... Ill load up the CURRENT branch and see how it works. Suprisingly, even the wireless card does not work. I'll post the updates after moving on to CURRENT. Mike, Just to be clear, 7.x != CURRENT. 7.0 is at the Release Candidate 1 stage right now and I've been using it successfully on my laptop, on my job, since last October/November. I'm not recommending that you go to -CURRENT, but to 7.x. -- Regards, Doug ___ 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 capture freebsd 6.3 kernel panics [solved]
On Fri, February 1, 2008 12:46, Manolis Kiagias wrote: [EMAIL PROTECTED]@mgEDV.net wrote: On Fri, February 1, 2008 11:54, Manolis Kiagias wrote: [EMAIL PROTECTED]@mgEDV.net wrote: hi, since i migrated from 6.2-REL to 6.3-REL i got several panics when copying much data from one volume to another. because of the copy-job taking several hours, i don't get a realistic chance to CATCH the stupid panic and see what's going on (or at least get an idea of). this is really frustrating me! is there a way to avoid the auto-reboot? is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. cheers... I recently had a system that would not dump to the swap partition for one reason or the other. I used an external USB hard disk, and it dumped there with no problems. With the current sizes of cheap usb flash drives, even that is probably an option. You may wish to explore this solution. Manolis well, although this is a good idea (and i'll keep it as my backup plan for now) , i rather like to prevent the server from rebooting and simply stay at the panic instead of analyzing crash dumps :) is there a way for that? Well, according to this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-options.html compiling your kernel with options KDB will cause it to enter the debugger instead of automatic reboot. This is not something I ever tried myself but it maybe worth the trouble. Manolis yeah, in the mean time, i exactly did this. loaded /usr/src/sys, compiled with options KDB, options DDB and booted with that kernel. this gives me at least the option to SEE what happened... thx for the replies, guys! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: SATA question
snip -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Darryl Hoar Sent: Tuesday, January 29, 2008 6:59 AM To: freebsd-questions@freebsd.org Subject: SATA question Well, maybe I spoke to soon. While looking at dmesg in prep for doing a custom kernel for my new server, I noticed an oddity. ad4 - DMA limited to UDMA33, device found non-ata66 cable. ad4 - SAMSUN HE160HJ JF800-24 Is this telling me the system recognized my 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as a UDMA33 ? No doubt, a pciconf followed by insertion of the ID into the ata detection routines would help - assuming your sata chipset is supported. You don't have the entire dmesg here but it looks like it's using the generic driver. Ted atapci0: ServerWorks HT1000 SATA150 controller port 0xecb0-0xecb7,0xeca0-0xeca 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at d evice 14.0 on pci3 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ServerWorks HT1000 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: ATA channel 0 on atapci1 ata1: ATA channel 1 on atapci1 acd0: CDRW HL-DT-STCD-RW/DVD-ROM GCC-T10N/A102 at ata0-master UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 152587MB SAMSUNG HE160HJ JF800-24 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 152587MB SAMSUNG HE160HJ JF800-24 at ata3-master UDMA33 This is the copied relevant portions of demsg's output. I have only used pciconf to list devices, so am basically unfamilar with it. So, how do I get the system to recognize the drives as SATA ? thanks, Darryl ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Building kernel with DEBUG
Near the top of the /usr/src/sys/i386/GENERIC file, is the line: makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols Is this line really necessary? If I don't intend to ever debug a kernel, why should I leave it? It would seem like I could save some time compiling a kernel if I just remove or commented out that line. -- Gerard [EMAIL PROTECTED] Beware of Programmers who carry screwdrivers. Leonard Brandwein signature.asc Description: PGP signature
Re: CVSup update or upgrade
On Fri, Feb 01, 2008 at 07:41:24AM -0500, Gerard wrote: On Thu, 31 Jan 2008 19:57:49 -0600 Chris [EMAIL PROTECTED] wrote: Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) You can just type: shutdown now to go into single user mode. It avoids the reboot sequence. Going to single user mode is the less important part of rebooting. The other part is that after the reboot you will be running the *new* kernel which might possibly be needed for a successful installworld. It is also a good test that the new kernel actually work. If the new kernel should fail to work it is fairly easy to use the old kernel instead. If you have already overwritten all userland programs with ones which require the new (non-working) kernel it can be difficult to recover from. Just going to single user mode without rebooting misses the point. The important thing is not to go into single user mode, it is to *reboot* into single user mode (or even into multi-user mode if you want to, but there are fewer things that can go wrong when going to single user mode.) # cd /usr/src # make installworld I prefer to use the following after make installworld mergemaster -i -v -U Read the man pages for mergemaster for further details. # shutdown -r now After rebooting, you might want to cd to the /usr/src directory and run: make delete-old-libs to clear out any garbage. It is not actually required however. -- Gerard [EMAIL PROTECTED] In the long run we are all dead. John Maynard Keynes -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Preventing KDE from restarting
Hi I am looking for an easy way to shutdown kde. If I ctrl-alt-backspace, the xserver and kdm restart automatically. Is there a way to make it quit directly to console? Thanks. ___ 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 capture freebsd 6.3 kernel panics
is there a way to save the panic to disk? btw, there's no swap partition i could use as dump device. so there is no way to save ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panics with GEOM
advise where to post if this is not appropriate.
An amd64/SMP server of mine worked quite reliably for some times.
Now I added two more disks and created a gmirror with them; from that point
on it experienced locks, crash and panics.
i use amd64/SMP+gmirror+gstripe+geli and works stable for a long time.
problem is probably somewhere else
Since it was a 6.2 at the time, I immediately upgraded to 6.3: this did not
solve, but, at least, the box would reboot and get me a crash dump.
So here it is: looks like the i/o subsystem has problems, so the two disk
might really be related, but still, I'm not sure.
# kgdb kernel.debug /var/crash/vmcore.5
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol ps_pglobal_lookup]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as amd64-marcel-freebsd.
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0x50006
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x8020e076
stack pointer = 0x10:0xa831c7a0
frame pointer = 0x10:0xa831c7e0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 88587 (clamscan)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 3d8h32m39s
Dumping 1023 MB (2 chunks)
chunk 0: 1MB (151 pages) ... ok
chunk 1: 1023MB (261744 pages) 1007 991 975 959 943
110ipfw: 65534 Deny TCP 192.168.101.1:58319 192.168.101.4:54663 in via
fxp0
110ipfw: 65534 Deny TCP 192.168.101.1:58319 192.168.101.4:54663 in via
fxp0
927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655
639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351
335 319 303 287 271 255 239 223 207 191 175panic: ahd_run_qoutfifo
recursion
cpuid = 1
159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:172
172 __asm __volatile(movq %%gs:0,%0 : =r (td));
(kgdb) bt
#0 doadump () at pcpu.h:172
#1 0x80257115 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0x80257825 in panic (fmt=0xff00110e9980 X\023\021\021) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0x803b50c6 in trap_fatal (frame=0xc, eva=18446742974484093312)
at /usr/src/sys/amd64/amd64/trap.c:669
#4 0x803b546d in trap_pfault (frame=0xa831c6f0,
usermode=0) at /usr/src/sys/amd64/amd64/trap.c:580
#5 0x803b56cd in trap (frame=
{tf_rdi = -1098891843040, tf_rsi = -1098516260992, tf_rdx =
-1098692440992, tf_rcx = 1, tf_r8 = 0, tf_r9 = 327686, tf_rax = 2048,
tf_rbx = -1098891843040, tf_rbp = -1473132576, tf_r10 = -1098978658048,
tf_r11 = -1098938410752, tf_r12 = -1098516260992, tf_r13 = 327686, tf_r14 =
-1098891842864, tf_r15 = -1705935624, tf_trapno = 12, tf_addr = 327686,
tf_flags = 1108101564416, tf_err = 0, tf_rip = -2145329034, tf_cs = 8,
tf_rflags = 66178, tf_rsp = -1473132624, tf_ss = 16}) at
/usr/src/sys/amd64/amd64/trap.c:353
#6 0x8039c49b in calltrap () at
/usr/src/sys/amd64/amd64/exception.S:168
#7 0x8020e076 in g_io_request (bp=0xff0024f12a20,
cp=0xff003b541780) at /usr/src/sys/geom/geom_io.c:275
#8 0x803709ad in ufs_strategy (ap=0xff0024f12a20) at
/usr/src/sys/ufs/ufs/ufs_vnops.c:1973
#9 0x803e5549 in VOP_STRATEGY_APV (vop=0x805702c0,
a=0xa831c840) at vnode_if.c:1796
#10 0x802b510c in bufstrategy (bo=0xff0024f12a20,
bp=0xff003b541780) at vnode_if.h:928
#11 0x802b4575 in breadn (vp=0xff000a55eba0,
blkno=-1098516260992, size=819186784, rablkno=0x0, rabsize=0x0, cnt=0,
cred=0x0, bpp=0x800) at buf.h:426
#12 0x802b48fe in bread (vp=0xff0024f12a20,
blkno=-1098516260992, size=819186784, cred=0x1, bpp=0x0) at
/usr/src/sys/kern/vfs_bio.c:723
#13 0x80363886 in ffs_read (ap=0xff0024f12a20) at
/usr/src/sys/ufs/ffs/ffs_vnops.c:523
#14 0x803e3efa in VOP_READ_APV (vop=0x800, a=0xff003b541780) at
vnode_if.c:643
#15 0x80370649 in ufs_readdir (ap=0xa831cad0) at
vnode_if.h:343
#16 0x803e419d in VOP_READDIR_APV (vop=0x800, a=0xff003b541780)
at vnode_if.c:1427
#17 0x802d0657 in getdirentries (td=0xff00110e9980,
uap=0xa831cbc0) at vnode_if.h:746
#18 0x803b6052 in syscall (frame=
{tf_rdi = 4, tf_rsi = 58564608, tf_rdx = 4096, tf_rcx = 58550056,
tf_r8 = 0, tf_r9 = 140737488347784, tf_rax = 196,
Re: how to enable the quota on
Giotis Eugen wrote: hello, im trying to enable quota on and i recieve the following error: fstab: /etc/fstab:2: Inappropriate file type or format and i typed: /etc/rc.conf and i recieve the error: /etc/rc.conf: Permission denied. Can you help me ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] It is not clear what you are actually typing here, but you should really open these files with an editor like, vi, ee, or nano. e.g. ee /etc/fstab and ee /etc/rc.conf to change the contents of the files. Then follow this guide from the handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/quotas.html ___ 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 enable the quota on
im trying to enable quota on and i recieve the following error: fstab: /etc/fstab:2: Inappropriate file type or format how do you enable it? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to enable the quota on
hello, im trying to enable quota on and i recieve the following error: fstab: /etc/fstab:2: Inappropriate file type or format and i typed: /etc/rc.conf and i recieve the error: /etc/rc.conf: Permission denied. Can you help me ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Display / Screen resolution question on IBM TP 1171
Angel Heaven wrote: Next problem: it has no sound. It seems like no sound card is detected at all. Any help is appreciated. Have you tried kldload snd_driver? The instructions in the Handbook section 7.2.1 usually work for me. -- Tore ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, Feb 01, 2008 at 09:45:30AM -0500, Gerard wrote:
On Fri, 1 Feb 2008 15:14:59 +0100
Erik Trulsson [EMAIL PROTECTED] wrote:
{snip]
Going to single user mode is the less important part of rebooting.
The other part is that after the reboot you will be running the *new*
kernel which might possibly be needed for a successful installworld.
It is also a good test that the new kernel actually work. If the new
kernel should fail to work it is fairly easy to use the old kernel
instead. If you have already overwritten all userland programs with
ones which require the new (non-working) kernel it can be difficult
to recover from.
Just going to single user mode without rebooting misses the point.
The important thing is not to go into single user mode, it is to
*reboot* into single user mode (or even into multi-user mode if you
want to, but there are fewer things that can go wrong when going to
single user mode.)
From:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
From the same document:
23.4.9 Reboot into Single User Mode
You should reboot into single user mode to test the new kernel works. Do
this by following the instructions in Section 23.4.5
/usr/src/UPDATING (which contains the really official instructions for how
to upgrade) also tells you to reboot.
Just going into single user mode without rebooting is not very useful.
The section of the handbook you quote below should probably be rewritten
somewhat.
23.4.5 Drop to Single User Mode
You may want to compile the system in single user mode. Apart from the
obvious benefit of making things go slightly faster, reinstalling the
system will touch a lot of important system files, all the standard
system binaries, libraries, include files and so on. Changing these on
a running system (particularly if you have active users on the system
at the time) is asking for trouble.
Another method is to compile the system in multi-user mode, and then
drop into single user mode for the installation. If you would like to
do it this way, simply hold off on the following steps until the build
has completed. You can postpone dropping to single user mode until you
have to installkernel or installworld.
As the superuser, you can execute:
# shutdown now
from a running system, which will drop it to single user mode.
--
Gerard
[EMAIL PROTECTED]
The greatest productive force is human selfishness.
Robert Heinlein
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
strange panic: freebsd 6.3: ffs_alloccg: map corrupted
hi folks, during copying ~350GB from one volume to another on the local machine (separate disks, separate fs's) i get the following panic: start = 0, len = 23691, fs = /newdata panic: ffs_alloccg: map corrupted KDB: enter: panic [ thread pid 835 tid 10070 ] stopped at kdb_enter +0x2c: leave the destination filesystem i created from scratch today, and the other which is read from is fsck'd. because of privacy/security considerations, i cannot really post the whole configuration of the machine (like fs-layout, other details, dmesg will be ok if needed). the backtrace can be viewed on this image: http://www.mgedv.at/panic_ffs_alloccg.png any ideas how to react on this? cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 15:14:59 +0100
Erik Trulsson [EMAIL PROTECTED] wrote:
{snip]
Going to single user mode is the less important part of rebooting.
The other part is that after the reboot you will be running the *new*
kernel which might possibly be needed for a successful installworld.
It is also a good test that the new kernel actually work. If the new
kernel should fail to work it is fairly easy to use the old kernel
instead. If you have already overwritten all userland programs with
ones which require the new (non-working) kernel it can be difficult
to recover from.
Just going to single user mode without rebooting misses the point.
The important thing is not to go into single user mode, it is to
*reboot* into single user mode (or even into multi-user mode if you
want to, but there are fewer things that can go wrong when going to
single user mode.)
From:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
23.4.5 Drop to Single User Mode
You may want to compile the system in single user mode. Apart from the
obvious benefit of making things go slightly faster, reinstalling the
system will touch a lot of important system files, all the standard
system binaries, libraries, include files and so on. Changing these on
a running system (particularly if you have active users on the system
at the time) is asking for trouble.
Another method is to compile the system in multi-user mode, and then
drop into single user mode for the installation. If you would like to
do it this way, simply hold off on the following steps until the build
has completed. You can postpone dropping to single user mode until you
have to installkernel or installworld.
As the superuser, you can execute:
# shutdown now
from a running system, which will drop it to single user mode.
--
Gerard
[EMAIL PROTECTED]
The greatest productive force is human selfishness.
Robert Heinlein
signature.asc
Description: PGP signature
Re: CVSup update or upgrade
On Thu, 31 Jan 2008 19:57:49 -0600 Chris [EMAIL PROTECTED] wrote: Assuming you went from 6.3-RELEASE to 6.3-STABLE and also assuming you do not have customization in /etc - here's what I do... After a cvsup of the src tree (ensuring I want the STABLE branch (*default release=cvs tag=RELENG_6) # cd /usr/src # make buildworld # make buildkernel KERNCONF=GENERIC (Assuming you use GENERIC) # make installkernel KERNCONF=GENERIC (Assuming you use GENERIC) # shutdown -r now (no need for Single-User Mode if YOU are the only user) You can just type: shutdown now to go into single user mode. It avoids the reboot sequence. # cd /usr/src # make installworld I prefer to use the following after make installworld mergemaster -i -v -U Read the man pages for mergemaster for further details. # shutdown -r now After rebooting, you might want to cd to the /usr/src directory and run:make delete-old-libs to clear out any garbage. It is not actually required however. -- Gerard [EMAIL PROTECTED] In the long run we are all dead. John Maynard Keynes signature.asc Description: PGP signature
Re: Spamassassin: Fill /var/log/maillog
On Thu, Jan 31, 2008 at 09:45:10PM +0100, Martin Schweizer typed: Hello I get allways the following message in /var/log/maillog: Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: connection from localhost.sample.ch [127.0.0.1] at port 64026 Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: setuid to root succeeded Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: still running as root: user not specified with -u, not found, or set to root,falling back to nobody Jan 31 17:21:36 acsvfbsd02 spamd[53289]: spamd: processing message [EMAIL PROTECTED] for root:65534 Jan 31 17:21:42 acsvfbsd02 spamd[53289]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /nonexistent/.spamassassin/auto-whitelist.lock.acsvfbsd02.acutronic.ch.53289 for /nonexistent//.spamassassin/auto-whitelist.lock: No such file or directory Jan 31 17:21:42 acsvfbsd02 spamd[53289]: spamd: clean message (0.0/7.0) for root:65534 in 6.2 seconds, 19091 bytes. Jan 31 17:21:42 acsvfbsd02 spamd[53289]: spamd: result: . 0 - HTML_MESSAGE scantime=6.2,size=19091,user=root,uid=65534,required_score=7.0,rhost=localhost.acutronic.ch,raddr=127.0.0.1,rport=64026,mid=[EMAIL PROTECTED],autolearn=failed There was a pr years ago: http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2005-March/054262.html Is there an other solution today? See the audit trail of this PR, it was allready implemented in 2005. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=78700cat=ports regards, Ruben ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Preventing KDE from restarting
Oren Almog wrote: I am looking for an easy way to shutdown kde. If I ctrl-alt-backspace, the xserver and kdm restart automatically. Is there a way to make it quit directly to console? There's probably a line in /etc/ttys starting kdm. No need to delete it, just turn it off. HTH, Alphons -- VISTA - Viruses Intruders Spyware Trojans Adware ___ 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 enable the quota on
On Fri, Feb 01, 2008 at 02:42:39PM +0200, Giotis Eugen wrote: hello, im trying to enable quota on and i recieve the following error: fstab: /etc/fstab:2: Inappropriate file type or format and i typed: /etc/rc.conf and i recieve the error: /etc/rc.conf: Permission denied. I don't know what you entered to get the first message. You don't say. But, on the second, /etc/rc.conf is NOT an executable file. It is a data file that other programs and scripts read to set variables for their operations. You might need to edit /etc/rc.conf (with vi or emacs or some other editor) to change variable settings, but you would not execute it. Where are you getting your information about starting quotas? Which steps have you actually tried? jerry Can you help me ? ___ 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: CVSup update or upgrade
On Friday 01 February 2008 00:47:12 Allen wrote: Now, this wouldn't work for some reason or another, but the system seemed to be doing just fine. I did uname -a and sure enough I had 6.3 Stable going. However, when typing kdm to load up that so I can use a gui, it no longer loads, at all, it pops up for a split second to just stop totally, and then gives me a message about the hostname. I thought it was odd, and XDM actually loads, but won't load X itself as it too goes out with errors about hostname. So the hostname isn't set, the clue would be that machine presents itself as amnesia. Check /etc/rc.conf so see if you set a hostname or if you use DHCP, check if the dhcp server gives you one. How this got lost in the upgrade, I don't know. mergemaster doesn't touch /etc/rc.conf, only /etc/defaults/rc.conf. I've been looking on FreeBSD.org but I don't fnid anything about this, but when did FreeBSD go from .tgz files to .tbz? I'm just wondering what happened as I thought it was atypo at first and realized every one of my books said .tbz and so did my screen heh. When libbz2 was brought into the base system, don't recall when exactly, somewhere around 5.0 I guess. tgz use gzip compression, tbz use bzip2 compression, which generally compresses better, but uses more CPU-time. FreeBSD can still read both though, it's just a change of default. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: firefox only runs with 'sudo'
In response to Steve Franks [EMAIL PROTECTED]: Don't get it. I installed firefox from the package at ftp4.us.freebsd.org like always (so I thought) but if I run 'firefox', I get a prompt back, and no firefox, but if I run it as sudo, it comes up fine. Where should I start fixing permissions at, do you think? I'm going to guess that your ~/.mozilla directory has incorrect ownership. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
firefox only runs with 'sudo'
Don't get it. I installed firefox from the package at ftp4.us.freebsd.org like always (so I thought) but if I run 'firefox', I get a prompt back, and no firefox, but if I run it as sudo, it comes up fine. Where should I start fixing permissions at, do you think? Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
How to get best results from FreeBSD-questions
How to get the best results from FreeBSD questions. === Last update $Date: 2005/08/10 02:21:44 $ This is a regular posting to the FreeBSD questions mailing list. If you got it in answer to a message you sent, it means that the sender thinks that at least one of the following things was wrong with your message: - You left out a subject line, or the subject line was not appropriate. - You formatted it in such a way that it was difficult to read. - You asked more than one unrelated question in one message. - You sent out a message with an incorrect date, time or time zone. - You sent out the same message more than once. - You sent an 'unsubscribe' message to FreeBSD-questions. If you have done any of these things, there is a good chance that you will get more than one copy of this message from different people. Read on, and your next message will be more successful. This document is also available on the web at http://www.lemis.com/questions.html. = Contents: I:Introduction II: How to unsubscribe from FreeBSD-questions III: Should I ask -questions or -hackers? IV: How to submit a question to FreeBSD-questions V:How to answer a question to FreeBSD-questions I: Introduction === This is a regular posting aimed to help both those seeking advice from FreeBSD-questions (the newcomers), and also those who answer the questions (the hackers). Note that the term hacker has nothing to do with breaking into other people's computers. The correct term for the latter activity is cracker, but the popular press hasn't found out yet. The FreeBSD hackers disapprove strongly of cracking security, and have nothing to do with it. In the past, there has been some friction which stems from the different viewpoints of the two groups. The newcomers accused the hackers of being arrogant, stuck-up, and unhelpful, while the hackers accused the newcomers of being stupid, unable to read plain English, and expecting everything to be handed to them on a silver platter. Of course, there's an element of truth in both these claims, but for the most part these viewpoints come from a sense of frustration. In this document, I'd like to do something to relieve this frustration and help everybody get better results from FreeBSD-questions. In the following section, I recommend how to submit a question; after that, we'll look at how to answer one. II: How to unsubscribe from FreeBSD-questions == When you subscribed to FreeBSD-questions, you got a welcome message from [EMAIL PROTECTED] In this message, amongst other things, it told you how to unsubscribe. Here's a typical message: Welcome to the freebsd-questions@freebsd.org mailing list! If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.freebsd.org/mailman/options/freebsd-questions/[EMAIL PROTECTED] (obviously, substitute your mail address for [EMAIL PROTECTED]). You can also make such adjustments via email by sending a message to: [EMAIL PROTECTED] with the word 'help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. Normally, Mailman will remind you of your freebsd.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. Here's the general information for the list you've subscribed to, in case you don't already have it: FREEBSD-QUESTIONS User questions This is the mailing list for questions about FreeBSD. You should not send how to questions to the technical lists unless you consider the question to be pretty technical. Normally, unsubscribing is even simpler than the message suggests: you don't need to specify your mail ID unless it is different from the one which you specified when you subscribed. If Majordomo replies and tells you (incorrectly) that you're not on the list, this may mean one of two things: 1. You have changed your mail ID since you subscribed. That's where keeping the original message from majordomo comes in handy. For example, the sample message above shows my mail ID as [EMAIL PROTECTED] Since then, I have changed it to [EMAIL PROTECTED] If I were to try to remove [EMAIL PROTECTED] from the list, it would fail: I would have to specify the name with which I joined. 2. You're subscribed to a mailing list which is subscribed to
The Complete FreeBSD: errata and addenda
The trouble with books is that you can't update them the way you can a web page or any other online documentation. The result is that most leading edge computer books are out of date almost before they are printed. Unfortunately, The Complete FreeBSD, published by O'Reilly, is no exception. Inevitably, a number of bugs and changes have surfaced. The Complete FreeBSD has been through a total of five editions, including its predecessor Installing and Running FreeBSD. Two of these have been reprinted with corrections. I maintain a series of errata pages. Start at http://www.lemis.com/errata-4.html to find out how to get the errata information. Note also that the book has now been released for free download in PDF form. Instead of downloading the changed pages, you may prefer to download the entire book. See http://www.lemis.com/grog/Documentation/CFBSD/ for more information. Have you found a problem with the book, or maybe something confusing? Please let me know: I'm no longer constantly updating it, but I may be able to help Greg ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cron to attach a gz file
On Friday 01 February 2008 08:48:02 Peter Boosten wrote: [EMAIL PROTECTED] wrote: I know I can use mail -s logfile /var/log/httpd_access.log in cron to email the content of a log file to a particular email address but how do I make that log file a binary attachment (*.gz)? gzip -c /var/log/httpd_access.log | uuencode httpd_access.log.gz | mail -s logfile [EMAIL PROTECTED] If you want an actual MIME attachment, see /usr/ports/mail/nail Nice tip, thanks for that. From a modern mail reader point of view there is not much difference between a MIME or a uuencoded attachment. But there is between an uuencoded /body/ and an attachment. At the risk of this degrading into a mail useragent battle: kmail didn't give an option to uudecode the body. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA question
Darryl Hoar wrote: Well, maybe I spoke to soon. While looking at dmesg in prep for doing a custom kernel for my new server, I noticed an oddity. ad4 - DMA limited to UDMA33, device found non-ata66 cable. ad4 - SAMSUN HE160HJ JF800-24 Is this telling me the system recognized my 160GB 7.2K RPM Serial ATA 3Gbps 3.5-in Cabled Hard Drive as a UDMA33 ? atapci0: ServerWorks HT1000 SATA150 controller port 0xecb0-0xecb7,0xeca0-0xeca 3,0xecb8-0xecbf,0xeca4-0xeca7,0xece0-0xecef mem 0xefdfe000-0xefdf irq 6 at d evice 14.0 on pci3 ata2: ATA channel 0 on atapci0 ata3: ATA channel 1 on atapci0 atapci1: ServerWorks HT1000 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x 177,0x376,0x8c0-0x8cf at device 2.1 on pci0 ata0: ATA channel 0 on atapci1 ata1: ATA channel 1 on atapci1 acd0: CDRW HL-DT-STCD-RW/DVD-ROM GCC-T10N/A102 at ata0-master UDMA33 ad4: DMA limited to UDMA33, device found non-ATA66 cable ad4: 152587MB SAMSUNG HE160HJ JF800-24 at ata2-master UDMA33 ad6: DMA limited to UDMA33, device found non-ATA66 cable ad6: 152587MB SAMSUNG HE160HJ JF800-24 at ata3-master UDMA33 This is the copied relevant portions of demsg's output. I have only used pciconf to list devices, so am basically unfamilar with it. So, how do I get the system to recognize the drives as SATA ? I think you are placing a lot of faith in an error message and that your drives *may* be being recognised as SATA drives with just something spurious (in the driver) causing this message to appear. It looks like the same chipset is providing both IDE/UDMA and SATA, so maybe the driver is trying them as IDE first, producing the error messages, then finding they are SATA after all. Just a guess Have you tried any basic disk benchmarks? Even a diskinfo -t should show you the kind of throughput your are getting, or something like dd bs=64k if=/dev/zero of=/some/file/on/the/disk count=1 That takes ~10 secs on my machine. If your performance is better than UDMA33 then you could just ignore the message or file an informational PR (if there isn't one already). Don't forget to be careful about bits/sec versus bytes/sec UDMA 33 is 33MB/s which is 33*1000*1000 bytes but 8 times as many bits, which some applications report. Having failed to get a definitive answer here you could also try the driver maintainer whom I believe to be [EMAIL PROTECTED] Confirm that from the manpage and don't forget to mention the version of FreeBSD you have (6.3?) See also this thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg01706.html hth, --Alex On a random SATA150 disk I get ~60017191 bytes/sec for a dd, which ~= 6 kbytes/sec from diskinfo and ~= 60MB/s or twice UDMA33. I believe that to be about par for a modern SATA disk. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: suitable laptops
On Tue, Jan 29, 2008 at 12:56:58PM -0800, Lee Shackelford wrote: Dear FreeBSD enthusiast. Greetings. Is anyone aware of a list of laptop computers on which it is especially easy to install FreeBSD, or conversely, on which it is unusually difficult to install FreeBSD? Alternately, does anyone know of a vendor who offers a laptop with FreeBSD pre-installed? If this question has been answered before, it is sufficient to direct me to the location of the answer. Many thanks for your assistance. Yours truly, L e e S h a c k e l f o r d @ d o t . c a . g o v I've had really good luck with Thinkpads. Because they're among the best laptops available, open source developers tend to focus on supporting them faster than a lot of other laptops. It's the best of both worlds. Also . . . Lenovo is selling some Thinkpad models with SuSE Linux installed. Those are likely to be better supported by FreeBSD than other models, I would imagine. Aside from that, I think the FreeBSD Laptop Compatibility List brought up by others should be useful: http://laptop.bsdgroup.de/freebsd/ -- CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ] They always say that when life gives you lemons you should make lemonade. I always wonder -- isn't the lemonade going to suck if life doesn't give you any sugar? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld releng7 exterme performance loss
Every 2 weeks or so I rebuild my sources on my laptop ( Dell Latitude D630 ). Last wednesday I wanted to update my system again since it was allready a couple of weeks ago I rebuilded my sources. There were no abnormalities during the build/install. But when I restarted my system the system performance was absolutely *horrible*. When I try typing anything in a terminal window the lag is about 20 seconds before the command even shows up. Switching ttys takes at least as long. When logging in remotely the performance is better; giving a random command through the ssh session sometimes even allows a command run on a local-console to run/finish ( or at least thats what the screen shows ). Even trying to shutdown the system using shutdown -p now doesn't have any effect: I get the message System is going down NOW but nothing realy happens, I just get my prompt back and I can continue entering commands. When I push the power-off button the system actually starts shutting down but it stops at Writing entropy file . leaving my only choise to power off the system the hard way. When booting the system to single-user mode however it reacts normally and also shutting down works as it should Last 2 days I tried redownloading the sources from a different mirror ( cvsup2.freebsd.org instead of cvsup.nl.freebsd.org ) to rule out outdated/corrupted sources. But I still get the same behaviour. Gladly I still had my previous sources so I managed to restore my system in a working state. Those sources are from about 3 weeks ago. Does anyone know what could have caused this behaviour and how to fix it ? Below is some system information, however I'm not sure what I should provide to help out, if I should test something I'll gladly do. Working system (sources from about 3 weeks ago, rebuilded today ) : [EMAIL PROTECTED] uname -a FreeBSD Rena.FStaals.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Fri Feb 1 20:23:11 CET 2008 root@:/usr/obj/usr/src/sys/RENAKERNEL i386 dmesg: http://fstaals.net/junk/rena/dmesg_old.txt With today's ( 1 frebruary 2008 ) sources : [EMAIL PROTECTED] cat /root/uname FreeBSD 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Fri Feb 1 18:32:59 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/RENAKERNEL i386 dmesg: http://fstaals.net/junk/rena/dmesg_2008_01_02.txt Kernel config used for both the builds : http://fstaals.net/junk/RENAKERNEL.txt -- -Frank Staals ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
This has begun to annoy me...
I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLW Fri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Thoughts? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
In response to Kurt Buff [EMAIL PROTECTED]: I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLWFri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Thoughts? Looks like a failing disk to me. Depending on the importance of the data on that drive, make sure you're getting backups and get a new drive on order. If it's always done this, it could also be faulty or non-standard hardware (such as the SATA controller). -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Feb 1, 2008 11:46 AM, Bill Moran [EMAIL PROTECTED] wrote: In response to Kurt Buff [EMAIL PROTECTED]: I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLWFri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Thoughts? Looks like a failing disk to me. Depending on the importance of the data on that drive, make sure you're getting backups and get a new drive on order. If it's always done this, it could also be faulty or non-standard hardware (such as the SATA controller). That's pretty much what I expected. It's done this since I've been running the machine, about six months now. Given your comment, I expect it's an issue with the controller. Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
That's pretty much what I expected. It's done this since I've been running the machine, about six months now. Given your comment, I expect it's an issue with the controller. with controller - it would start immediately, not after 6 months i think but please use smartmontools. good idea is to use it always, not only when problems start to appear ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Fri, Feb 01, 2008 at 11:40:32AM -0800, Kurt Buff wrote: I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLWFri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Thoughts? Not so much write *errors* as write *problems*. What seems to have happened is that some write requests do not finish fast enough so the ATA driver gets a timeout, but retries the operation and it works on the second try. (If it hadn't worked on the second try either then there should have been much scarier messages in the log.) It might be because of a disk going bad where the disk has to do remapping of bad blocks when it detects write problems which take extra time, causing timeouts. It might be because of sub-standard cabling which cause errors (but then there ought to have been problems with reading as well as writing.) It might be because FreeBSD's ATA driver uses a timeout value which is a bit too aggressive (too low) for your controller/disk combination. You could changing the disk for another. If you get similar messages with the other disk too, then it is probably not the disk which is at fault. -- Insert your favourite quote here. Erik Trulsson [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: This has begun to annoy me...
In response to Kurt Buff [EMAIL PROTECTED]: On Feb 1, 2008 11:46 AM, Bill Moran [EMAIL PROTECTED] wrote: In response to Kurt Buff [EMAIL PROTECTED]: I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLWFri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Thoughts? Looks like a failing disk to me. Depending on the importance of the data on that drive, make sure you're getting backups and get a new drive on order. If it's always done this, it could also be faulty or non-standard hardware (such as the SATA controller). That's pretty much what I expected. It's done this since I've been running the machine, about six months now. Given your comment, I expect it's an issue with the controller. I recommend you _not_ trust that system. In my experience, systems with weird errors like this can suddenly lose your data for no reason. -- Bill Moran http://www.potentialtech.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Friday 01 February 2008 20:40:32 Kurt Buff wrote: I've been getting this in my daily security email from one of my boxes for quite a while, and have been ignoring it, because of workload. However, it's finally annoyed me enough to pursue it. What would the significance of the following section be? zsquid.mycompany.com kernel log messages: +++ /tmp/security.4blejPLWFri Feb 1 03:02:08 2008 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4662143 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113995359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=112970015 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4668319 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4849151 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=115527359 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113714335 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113715199 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. Disk errors (as in bad sectors) or bad cable. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
You could changing the disk for another. If you get similar messages with the other disk too, then it is probably not the disk which is at fault. smartmontools gets error info from DRIVE directly, so it's easy to know if it was drive media error or drive communication errors! -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] ___ 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: This has begun to annoy me...
+ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. yes it use. use ports/sysutils/smartmontools to make sure. print smart output and/or these errors and request replacement in your shop. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Friday 01 February 2008 14:23:27 Wojciech Puchar wrote: You could changing the disk for another. If you get similar messages with the other disk too, then it is probably not the disk which is at fault. smartmontools gets error info from DRIVE directly, so it's easy to know if it was drive media error or drive communication errors! -- Insert your favourite quote here. I have a laptop doing same thing, but even with the occasional spontaneous reboot, it is still more reliable than Windows, and as I haven't had time to mess with it, it stays in there. Probably will run dban on the drive, see if it makes happy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
I have a laptop doing same thing, but even with the occasional spontaneous reboot, it is still more reliable than Windows, and as I haven't had time to mess with it, it stays in there. Probably will run dban on the drive, see if it makes happy. what is dban? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Fri, 2008-02-01 at 22:37 +0100, Wojciech Puchar wrote: I have a laptop doing same thing, but even with the occasional spontaneous reboot, it is still more reliable than Windows, and as I haven't had time to mess with it, it stays in there. Probably will run dban on the drive, see if it makes happy. what is dban? Darik's Boot and Nuke: http://dban.sourceforge.net/ ___ 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: This has begun to annoy me...
use ports/sysutils/smartmontools What do you use for SATA RAID drives? (/dev/mfi[num]) i don't use hardware RAID at all. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
--On Friday, February 01, 2008 21:08:53 +0100 Wojciech Puchar [EMAIL PROTECTED] wrote: +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. yes it use. use ports/sysutils/smartmontools What do you use for SATA RAID drives? (/dev/mfi[num]) -- Paul Schmehl ([EMAIL PROTECTED]) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Fwd: This has begun to annoy me...
Sorry, didn't do a reply-all when I should have... -- Forwarded message -- From: Kurt Buff [EMAIL PROTECTED] Date: Feb 1, 2008 2:13 PM Subject: Re: This has begun to annoy me... To: Wojciech Puchar [EMAIL PROTECTED] On Feb 1, 2008 12:08 PM, Wojciech Puchar [EMAIL PROTECTED] wrote: +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. yes it use. use ports/sysutils/smartmontools to make sure. print smart output and/or these errors and request replacement in your shop. I've installed the port, and started the daemon. We'll see what tomorrow brings. Thanks, Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: This has begun to annoy me...
On Fri, Feb 01, 2008 at 02:14:05PM -0800, Kurt Buff wrote: On Feb 1, 2008 12:08 PM, Wojciech Puchar [EMAIL PROTECTED] wrote: +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. yes it use. use ports/sysutils/smartmontools to make sure. print smart output and/or these errors and request replacement in your shop. I've installed the port, and started the daemon. We'll see what tomorrow brings. You could also run the following command immediatly, without having to wait for the daemon to collect data: # smartctl -a /dev/ad6 and consider running a long test as well: # smartctl -t long /dev/ad6 followed by another smartctl -a /dev/ad6 again once the test completes (the drive will tell you how long it takes, expect something like 30 to 45 minutes or so, depending on the size and speed of the drive). Kurt -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wpa_supplicant not starting with /etc/rc.d/netif
I forgot to mention, I'm running 6.3. On Feb 2, 2008 12:32 AM, Reinis Ivanovs [EMAIL PROTECTED] wrote: Hello, I have been following these instructions from the manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#NETWORK-WIRELESS-WPA-WPA-PSK However, in the step that requires me to run /etc/rc.d/netif start, instead of it starting wpa_supplicant, I see only ral0: no link giving up. I've added ifconfig_ral0=WPA DHCP to /etc/rc.conf, and it works just fine if I start it manually with wpa_supplicant -B -c /etc/wpa_supplicant.conf -i ral0. What should I do to get it working? Could it be that there's some bug in your scripts? Regards, Reinis -- http://untu.ms/ -- http://untu.ms/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Oops
Wojciech Puchar wrote: ufs:mirror/gm0s1a fsck -p / mount / last won't work with fstab not having right entry. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] He never said that fstab was complaining! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
wpa_supplicant not starting with /etc/rc.d/netif
Hello, I have been following these instructions from the manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#NETWORK-WIRELESS-WPA-WPA-PSK However, in the step that requires me to run /etc/rc.d/netif start, instead of it starting wpa_supplicant, I see only ral0: no link giving up. I've added ifconfig_ral0=WPA DHCP to /etc/rc.conf, and it works just fine if I start it manually with wpa_supplicant -B -c /etc/wpa_supplicant.conf -i ral0. What should I do to get it working? Could it be that there's some bug in your scripts? Regards, Reinis -- http://untu.ms/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wpa_supplicant not starting with /etc/rc.d/netif
On Sat, 2008-02-02 at 00:32 +0200, Reinis Ivanovs wrote: Hello, I have been following these instructions from the manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#NETWORK-WIRELESS-WPA-WPA-PSK However, in the step that requires me to run /etc/rc.d/netif start, instead of it starting wpa_supplicant, I see only ral0: no link giving up. I've added ifconfig_ral0=WPA DHCP to /etc/rc.conf, and it works just fine if I start it manually with wpa_supplicant -B -c /etc/wpa_supplicant.conf -i ral0. What should I do to get it working? Could it be that there's some bug in your scripts? Regards, Reinis I've not done this, but the documentation says: Note: If the /etc/rc.conf is set up with the line ifconfig_ath0=DHCP then it is no need to run the dhclient command manually, dhclient will be launched after wpa_supplicant plumbs the keys. As such, I don't understand why you're running the ifconfig command in /etc/rc.conf with the extra WPA flag. Try making it read ifconfig_ral0=DHCP and see if that helps. Best James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Compiz Fusion
Is there a tutorial on how to configure compiz fusion on FBSD 6.3 / gnome or fluxbox. I just can't get it to work following their instructions since they are written for a couple of linux distros. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wpa_supplicant not starting with /etc/rc.d/netif
Hi, James, It doesn't work with just DHCP, and I'm not sure you've read that correctly. All it says is that you don't have to run dhclient manually, and I'm not doing that anyway. Regards, Reinis On Feb 2, 2008 1:06 AM, James Harrison [EMAIL PROTECTED] wrote: On Sat, 2008-02-02 at 00:32 +0200, Reinis Ivanovs wrote: Hello, I have been following these instructions from the manual: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#NETWORK-WIRELESS-WPA-WPA-PSK However, in the step that requires me to run /etc/rc.d/netif start, instead of it starting wpa_supplicant, I see only ral0: no link giving up. I've added ifconfig_ral0=WPA DHCP to /etc/rc.conf, and it works just fine if I start it manually with wpa_supplicant -B -c /etc/wpa_supplicant.conf -i ral0. What should I do to get it working? Could it be that there's some bug in your scripts? Regards, Reinis I've not done this, but the documentation says: Note: If the /etc/rc.conf is set up with the line ifconfig_ath0=DHCP then it is no need to run the dhclient command manually, dhclient will be launched after wpa_supplicant plumbs the keys. As such, I don't understand why you're running the ifconfig command in /etc/rc.conf with the extra WPA flag. Try making it read ifconfig_ral0=DHCP and see if that helps. Best James -- http://untu.ms/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: This has begun to annoy me...
On Fri, Feb 01, 2008 at 09:08:53PM +0100, Wojciech Puchar wrote: +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 It looks like disk write errors to me, but I'm not sure. yes it use. use ports/sysutils/smartmontools to make sure. print smart output and/or these errors and request replacement in your shop. The disk is failing. Smartmontools, which is a great package, will only tell you want you already know, that the disk is failing. I would copy every thing important off that disk _NOW_ then go and get a replacement disk TODAY. It's possible that the disk may spin for another 2 months or it might burst into flames in the next 20 minutes. Either way the disk is telling you, I'm sick. Also, what ever you do, do not power down that machine until you have copied off the data. When you power cycle machines with disk in this state there is a very good chance the disk will not spin back up. I see this all the time at my job. Good Luck Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.3 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgputPSgOb4ff.pgp Description: PGP signature
Re: Compiz Fusion
I agree. There should be docs for Compiz-Fusion on FreeBSD. There isn't any right now as far as I know. On Feb 1, 2008 3:08 PM, E. J. Cerejo [EMAIL PROTECTED] wrote: Is there a tutorial on how to configure compiz fusion on FBSD 6.3 / gnome or fluxbox. I just can't get it to work following their instructions since they are written for a couple of linux distros. ___ 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]
Squid3.0 missing something with pf transparent proxy.
I haven't been using squid since version 2.5. I just built a new 3.0 and did a very basic configuration that works fine configuring the prefs - advanced - network and adding the host and port but when I use the pf redirect it seems to not get the url parsing right for some reason. I put http://www.google.com and see 1201906217.304 0 172.16.0.14 NONE/400 1809 GET /google.com/ - NONE/- text/html 1201906217.466 0 172.16.0.14 NONE/400 1809 GET /favicon.ico - NONE/- text/html 1 in the squid access.log rather than http:://www.google.com.and the screen shows: http://encontacto.net/transSquid3.0.png The pf redirect, etc is working fine, /dev/pf has squid as the group with rw perms, I have no idea where to look. I've got the idea that I must have missed something in the 3.0 configuration. Does anyone have it working and could you give me a hint or maybe share your squid.conf that works, just the diffs from the squid.conf.dist. Thanks, ed ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Preventing KDE from restarting
I do have that line but it is disabled (off). Looking at /usr/local/share/config/kdm/kdmrc does reveal a few options that can immediately restart a session but they are all either commented out or not set. Hi I am looking for an easy way to shutdown kde. If I ctrl-alt-backspace, the xserver and kdm restart automatically. Is there a way to make it quit directly to console? Thanks. Check /etc/ttys. You probably have something like: ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm on secure If so, turn it off and reboot. From that point. If not check rc.conf and related directories to see where xdm is being started. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiz Fusion
E. J. Cerejo wrote: Is there a tutorial on how to configure compiz fusion on FBSD 6.3 / gnome or fluxbox. 1. Use the port/package. 2. Every now and then I see messages fly by in which you can find exactly which flags/options to use. 3. You are right, there should be documentation... Alphons P.S. I found this stashed in a folder meant for future reference: Assuming you have already setup you X server for composite, to run compiz-fusion enter these commands: (as normal user) compiz --replace --sm-disable --ignore-dekstop-hints ccp emerald --replace Credits to Manolis Kiagias :-) -- VISTA - Viruses Intruders Spyware Trojans Adware ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Compiz Fusion
Nerius Landys wrote: I agree. There should be docs for Compiz-Fusion on FreeBSD. There isn't any right now as far as I know. On Feb 1, 2008 3:08 PM, E. J. Cerejo [EMAIL PROTECTED] wrote: Is there a tutorial on how to configure compiz fusion on FBSD 6.3 / gnome or fluxbox. I just can't get it to work following their instructions since they are written for a couple of linux distros. ___ 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] I know those guys over at PC-BSD have it working when you install pc-bsd they should write a how to! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: This has begun to annoy me...
Am 01.02.2008, 23:14 Uhr, schrieb Kurt Buff [EMAIL PROTECTED]: +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=4570911 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=42958719 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=113343327 +ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=117315327 Sooner or later. this messages will be followed by something along the line of ad6: WRITE_DMA failed and you'll get READ_DMA failures as well. As others have suggested, do not trust this drive. You may command atacontrol mode ad6 pio or put hw.ata.ata_dma=0 in loader.conf. The errors will disappear. Use this if you can't backup because the reads fail. Worked for me. YMMV. I've installed the port, and started the daemon. We'll see what tomorrow brings. Even if smart does not find anything -- use the drive for junk purposes at max. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mpd with a dual pppoe setup
Hi, I'm building a new router/firewall for my work, I have installed freebsd7 and updated it and compiled pf into the kernel and installed mpd5 for pppoe. Before I make this system life I would like your input on my mpd settings. We have 2 adsl lines and I want to use the new firewall to do load balancing between them. I've been searching all over the net to find out more about how I can use mpd for this but all I can find is single pppoe or mlppp conections, our isp does not support mlppp so thats not an option. PF will be used for the load balancing and I want to use ancors for when one of the dsl lines goes down. For now I have only configured mpd but I'm not sure if its done corectly, I can't test it because that will mean that I will have to take our current system off line and that is not an option. Here is what I've done so far. /usr/local/etc/mpd5/mpd.conf default: load wan1 load wan2 wan1: new -i ng0 provider PPPoE0 set iface route default set iface up-script /usr/local/etc/mpd/script-wan1.sh set iface down-script /usr/local/etc/mpd/script-wan1.sh set bundle authname [EMAIL PROTECTED] set bundle password passwd set ipcp ranges static-ip-0/32 isp-gateway-0/32 load common_setting wan2: new -i ng1 wan2 PPPoE1 set iface route default set iface up-script /usr/local/etc/mpd/script-wan2.sh set iface down-script /usr/local/etc/mpd/script-wan2.sh set bundle authname [EMAIL PROTECTED] set bundle password passwd set ipcp ranges static-ip-1/32 isp-gateway-1/32 load common_setting common_setting: set iface addrs 1.1.1.1 2.2.2.2 set iface disable on-demand set iface idle 0 set iface enable tcpmssfix set bundle disable multilink set link no acfcomp protocomp set link disable pap chap set link accept chap set link keep-alive 10 60 set link max-redial -1 set link mtu 1492 set link mru 1492 set ipcp yes vjcomp set ipcp enable req-sec-dns open iface # PPTP pptpd: load pt0 load pt1 load pt2 load pt3 load pt4 load pt5 load pt6 load pt7 load pt8 load pt9 load pt10 load pt11 load pt12 load pt13 load pt14 load pt15 pt0: new -i ng2 pt0 pt0 set ipcp ranges 192.168.2.1/32 192.168.1.240/32 load pts pt1: new -i ng3 pt1 pt1 set ipcp ranges 192.168.2.1/32 192.168.1.241/32 load pts pt2: new -i ng4 pt2 pt2 set ipcp ranges 192.168.2.1/32 192.168.1.242/32 load pts pt3: new -i ng5 pt3 pt3 set ipcp ranges 192.168.2.1/32 192.168.1.243/32 load pts pt4: new -i ng6 pt4 pt4 set ipcp ranges 192.168.2.1/32 192.168.1.244/32 load pts pt5: new -i ng7 pt5 pt5 set ipcp ranges 192.168.2.1/32 192.168.1.245/32 load pts pt6: new -i ng8 pt6 pt6 set ipcp ranges 192.168.2.1/32 192.168.1.246/32 load pts pt7: new -i ng9 pt7 pt7 set ipcp ranges 192.168.2.1/32 192.168.1.247/32 load pts pt8: new -i ng10 pt8 pt8 set ipcp ranges 192.168.2.1/32 192.168.1.248/32 load pts pt9: new -i ng11 pt9 pt9 set ipcp ranges 192.168.2.1/32 192.168.1.249/32 load pts pt10: new -i ng12 pt10 pt10 set ipcp ranges 192.168.2.1/32 192.168.1.250/32 load pts pt11: new -i ng13 pt11 pt11 set ipcp ranges 192.168.2.1/32 192.168.1.251/32 load pts pt12: new -i ng14 pt12 pt12 set ipcp ranges 192.168.2.1/32 192.168.1.252/32 load pts pt13: new -i ng15 pt13 pt13 set ipcp ranges 192.168.2.1/32 192.168.1.253/32 load pts pt14: new -i ng16 pt14 pt14 set ipcp ranges 192.168.2.1/32 192.168.1.254/32 load pts pt15: new -i ng17 pt15 pt15 set ipcp ranges 192.168.2.1/32 192.168.1.255/32 load pts pts: set iface disable on-demand set iface enable proxy-arp set iface enable tcpmssfix set iface idle 1800 set iface up-script /usr/local/sbin/vpn-linkup set iface down-script /usr/local/sbin/vpn-linkdown set bundle enable multilink set bundle enable crypt-reqd set link yes acfcomp protocomp set link no pap chap set link enable chap-msv2 set link mtu 1460 set link keep-alive 10 60 set ipcp yes vjcomp set bundle enable compression set ccp yes mppc set ccp yes mpp-e128 set ccp yes mpp-stateless set ipcp nbns set ipcp dns 208.67.220.220 208.67.222.222 /usr/local/etc/mpd5/mpd.links # mpd.links PPPoE0: set link type pppoe set pppoe iface fxp0
Removing FreeBSD
Hi. I recently purchased a HDD from a man that runs a data center, and on this HDD is FreeBSD. My problem is I want it off, and for some ungodly reason, it keeps coming back. I cant format the drive with Windows, and I cant load it as a slave to format, either. Any help would be greatly appreciated. Thanks - M White Black and White Computer Repair Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bnw CmpRpr wrote: Hi. I recently purchased a HDD from a man that runs a data center, and on this HDD is FreeBSD. My problem is I want it off, and for some ungodly reason, it keeps coming back. I cant format the drive with Windows, and I cant load it as a slave to format, either. Any help would be greatly appreciated. Thanks - M White Black and White Computer Repair The following assumes the drive is /dev/ad0 (the OS name for it) and it is modern enough to not get confused by a low level format... boot in single user mode (item 4 on the menu) and at the command line do: dd if=/dev/zero of=/dev/ad0 bs=512 count=1 This will clear the MBR partition table and make the machine think it is a brand new drive. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com Free software != Free beer Blog: http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHo7zaQi2hk2LEXBARAsdxAKDPTkTXZ/s1EaFp5AIybNBSSdufKwCgtG79 tbzQNJIAPIJ0CZLidKtZP4s= =OlhM -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing FreeBSD
On Fri, 1 Feb 2008 15:55:59 -0800 (PST) Bnw CmpRpr [EMAIL PROTECTED] wrote: Hi. I recently purchased a HDD from a man that runs a data center, and on this HDD is FreeBSD. My problem is I want it off, and for some ungodly reason, it keeps coming back. I cant format the drive with Windows, and I cant load it as a slave to format, either. Any help would be greatly appreciated. Thanks - M White Black and White Computer Repair Ensure that the jumpers are set correctly and or is in the proper cable pattern (if using CS) if you intend on using it as a slave for Windows (XP I assume) Once that is done, WindowsXP has no issues seeing the drive but must be formatted. Here again, WindowsXP (assuming) can and will reformat a drive that has been used by FreeBSD. -- Best regards, Chris only available on a need to know basis ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing FreeBSD
Aryeh M. Friedman wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bnw CmpRpr wrote: Hi. I recently purchased a HDD from a man that runs a data center, and on this HDD is FreeBSD. My problem is I want it off, and for some ungodly reason, it keeps coming back. I cant format the drive with Windows, and I cant load it as a slave to format, either. Any help would be greatly appreciated. Thanks - M White Black and White Computer Repair The following assumes the drive is /dev/ad0 (the OS name for it) and it is modern enough to not get confused by a low level format... boot in single user mode (item 4 on the menu) and at the command line do: dd if=/dev/zero of=/dev/ad0 bs=512 count=1 This will clear the MBR partition table and make the machine think it is a brand new drive. I reckon he's smart enough to find the freebsd list and smart enough to ask the right question, so he's smart enough to appreciate FreeBSD. So he should leave it on there :P Still in case previous attempts at formatting have removed the OS he could try Darik's Boot and Nuke floppy/usb/cd http://dban.sourceforge.net/. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CVSup update or upgrade
On Fri, 1 Feb 2008 14:12:43 +0100 Ruben de Groot [EMAIL PROTECTED] wrote: On Thu, Jan 31, 2008 at 07:57:49PM -0600, Chris typed: 23.2.2.1 What Is FreeBSD-STABLE? FreeBSD-STABLE is our development branch from which major releases are made. Changes go into this branch at a different pace, and with the general assumption that they have first gone into FreeBSD-CURRENT for testing. This is still a development branch, however, and this means that at any given time, the sources for FreeBSD-STABLE may or may not be suitable for any particular purpose. It is simply another engineering development track, not a resource for end-users. RELENG_6 is STABLE RELENG_6_3 is for security fixes I stand corrected. -- Best regards, Chris Emperor Palpatine: Everything that has transpired has done so according to my design. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Removing FreeBSD
Hi, Bnw CmpRpr wrote: Hi. I recently purchased a HDD from a man that runs a data center, and on this HDD is FreeBSD. My problem is I want it off, and for some ungodly reason, it keeps coming back. I cant format the drive with Windows, and I cant load it as a slave to format, either. Any help would be greatly appreciated. Thanks the devils operating system can only be removed if you drill with a 6.6mm drill a hole 66.6 mm from top and 66.6mm from left through the drive from the top measured from the top left corner. But I also wonder why Windows' fdisk does not allow you to remove the partition and then create a new Windows partition. If you simply add to the currently installed FreeBSD partition, you will not get very far. It might be of interest what kind of data are stored there. Has NSA a copy of it? - M White Black and White Computer Repair are you sure? Erich Never miss a thing. Make Yahoo your home page. I missed Microsoft's offer to take over Yahoo because I trusted Yahoo to keep me updated. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vi+urxvt8.9+oxim for traditional chinese, HOW??
On Fri, Feb 01, 2008, Tsu-Fan Cheng wrote: some are displayed correctly, but some are wrong, still looks like \XX\XX, feel like not all the characters are not well represented Maybe there have some characters not in Big-5 range. Can you send me the file personally? Edward ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
