Re: Lost the require meny alternative with Gimp upgrade
Warren Block skrev: On Thu, 16 Oct 2008, Leslie Jensen wrote: I upgraded Gimp to version 2.6.1 and now I do not have the require (for scanning) meny choice anymore. Acquire, maybe? Yes, sorry about that. Any ideas on how to get the function back. I can scan using xscanimage but it takes more steps to get the scanned image into Gimp. In gimp 2.6.1, the SANE scanner plugin is on the File/Create menu. Thank you :-) I've found it /Leslie -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD RELENG_7 scsi and usb, usb disks take precedence
Dan Nelson [EMAIL PROTECTED] writes: Hi, No patching needed. You can wire down the unit number of your scsi bus and drive with boot hints as described in the scsi(4) manpage. Wire the adaptec card down as scbus0, and wire the device at scbus0.0 down as da0. Nice. I've never used scsi related hints ATM. I've learned something today © ;) -- bof mot de passe invalide ca veut dire quoi? Que tu peux s'assoir dans les places réservées des autobus. -+- LW in GNU : Pour l'invalide, c'est l'opéra ou la concorde. -+- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
updating a port with problems (libxml2)
Hi all, I use portsnap to keep the port tree of my FreeBSD 7 box up to date. According to portaudit, which I run nightly, there is a problem with the current version of libxml2. So, as usual, I run sudo portsnap fetch sudo portsnap update, and then: $ cd /usr/ports/textproc/libxml2 $ sudo make deinstall $ sudo make reinstall clean But this last command results in an error: === libxml2-2.6.32 has known vulnerabilities: = libxml2 -- two vulnerabilities. Reference: http://www.FreeBSD.org/ports/portaudit/d71da236-9a94-11dd-8f42-001c2514716c.html = Please update your ports tree and try again. It would appear that the port has not yet been updated. Is this some temporary glitch? Otherwise, the approach I use is not very robust, since I have now managed to deinstall a library upon which a dozen or so programs depend. However, this is the first time this has happened. Comments, suggestions most welcome. Thanks. - Colin Brace Amsterdam http://lim.nl -- View this message in context: http://www.nabble.com/updating-a-port-with-problems-%28libxml2%29-tp20028504p20028504.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: updating a port with problems (libxml2)
On Fri, Oct 17, 2008 at 01:01:09AM -0700, Colin Brace wrote: Hi all, I use portsnap to keep the port tree of my FreeBSD 7 box up to date. According to portaudit, which I run nightly, there is a problem with the current version of libxml2. So, as usual, I run sudo portsnap fetch sudo portsnap update, and then: $ cd /usr/ports/textproc/libxml2 $ sudo make deinstall $ sudo make reinstall clean But this last command results in an error: === libxml2-2.6.32 has known vulnerabilities: = libxml2 -- two vulnerabilities. Reference: http://www.FreeBSD.org/ports/portaudit/d71da236-9a94-11dd-8f42-001c2514716c.html = Please update your ports tree and try again. It would appear that the port has not yet been updated. Is this some temporary glitch? Otherwise, the approach I use is not very robust, since I have now managed to deinstall a library upon which a dozen or so programs depend. However, this is the first time this has happened. Comments, suggestions most welcome. Sometimes it takes a while after a problem has been found with a port until a fixed version is available in the ports tree. In the worst case the port might never get fixed. So, no, your approach is not very robust. -- 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: updating a port with problems (libxml2)
Colin Brace [EMAIL PROTECTED] writes: Hi all, I use portsnap to keep the port tree of my FreeBSD 7 box up to date. According to portaudit, which I run nightly, there is a problem with the current version of libxml2. So, as usual, I run sudo portsnap fetch sudo portsnap update, and then: $ cd /usr/ports/textproc/libxml2 $ sudo make deinstall $ sudo make reinstall clean But this last command results in an error: === libxml2-2.6.32 has known vulnerabilities: = libxml2 -- two vulnerabilities. Reference: http://www.FreeBSD.org/ports/portaudit/d71da236-9a94-11dd-8f42-001c2514716c.html = Please update your ports tree and try again. It would appear that the port has not yet been updated. Is this some temporary glitch? Otherwise, the approach I use is not very robust, since I have now managed to deinstall a library upon which a dozen or so programs depend. However, this is the first time this has happened. Comments, suggestions most welcome. Hi Colin, I hit a similar difficulty with cups-base a few days ago. Matthew Seaman suggested this as a way of getting the dodgy port to install, which I used because I *really* needed to print something:- portupgrade -m DISABLE_VULNERABILITIES=yes cups-base Lo and behold, within 6 hours of my re-installing the vulnerable port, the port was fixed and I upgraded to that hth Glyn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: updating a port with problems (libxml2)
On 10/17/08 01:01, Colin Brace wrote: Hi all, I use portsnap to keep the port tree of my FreeBSD 7 box up to date. According to portaudit, which I run nightly, there is a problem with the current version of libxml2. So, as usual, I run sudo portsnap fetch sudo portsnap update, and then: Note that 'portsnap fetch update' will accomplish the same thing. $ cd /usr/ports/textproc/libxml2 $ sudo make deinstall $ sudo make reinstall clean But this last command results in an error: === libxml2-2.6.32 has known vulnerabilities: = libxml2 -- two vulnerabilities. Reference: http://www.FreeBSD.org/ports/portaudit/d71da236-9a94-11dd-8f42-001c2514716c.html = Please update your ports tree and try again. It would appear that the port has not yet been updated. Is this some temporary glitch? Otherwise, the approach I use is not very robust, since I have now managed to deinstall a library upon which a dozen or so programs depend. However, this is the first time this has happened. Comments, suggestions most welcome. To get libxml2 reinstalled before the port is bumped you'll want to try 'make -DDISABLE_VULNERABILITIES reinstall'. In general, it's easier to use portupgrade(1). See Using the Ports Collection[1] in the FreeBSD Handbook. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html -- Benjamin Lee signature.asc Description: OpenPGP digital signature
Re: FreeBSD and Nagios - permissions
Jeremy Chadwick wrote: You get the point now, I'm sure. Hi, just to say a big thank you to the people on the list for keeping up with my dumb questions on sudo, this morning I re-read the manual and got it working within minutes. I'm still not convinced that sudo is the way to go in our particular case so next week we'll test the C wrapper approach as well. Have a good weekend, -- per ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Breach of Contract Reported for FREEBSD.ORG
Jeremy Chadwick wrote: [snip] ICANN requires registrars to verify the domain info once a year. I just went through this with GoDaddy. I think the registrars see this as an opportunity to market services. Different registrars bungle their marketing effort in different ways. GoDaddy sent me instructions on what to do in order to correct errors, but had absolutely nothing on how to proceed if the information was correct. So I viewed this as something they could take advantage of in order to get me to their site for a hard sell campaign. So how do you folks who comply with ICANN's requirement deal with this? http://blog.forret.com/2004/12/domain-registry-of-america-scam/ -- This organisation is now known as Domain Renewal Group, by the way. What is described in the above URI looks very very similar to what I saw when I first went to check up on the ICANN whois confirmation email I received from GoDaddy. Initially they seemed to be touting their new TDNAM service, which I gather is some form of bulk auction. GoDaddy took over the domains from the RegisterFly debacle so they have a few million domains to monetize. A perfect example of registrar gone bad. At first I was alarmed - Why am I in some danger of losing my domains? is what I thought. As I went deeper into it by examining my account, I confirmed that I indeed had Auto Renew on, so it would just bill my credit card even if I took no action. However, I tend to do it manually just so I'm satisfied it's done. So in the end this was just a hard sell for a new service they wanted to push, for which I have no use. There must have been complaints because when I just went looking for what I saw a few weeks ago it seems to have vanished. I'm quite interested in knowing; it might be tolerable if you've only one domain, but if you're a hosting provider and have 100? I'm not qualified for this because these days I only carry two .com domains. At work we are a large .org entity and we have an entire group of people whose sole function is to deal with this. Relatively low down in the hierarchy my DNS servers are only slaves to those higher up. It is a function handled by others and is out of my hands. But a scam is a scam and the first thing which needs to occur is recognizing a scam when you see it. Most legitimate businesses recognize the need for large scale management and more than likely market some form of service of assistance. It's a matter of trade-off of the fees they charge versus whether it is worth it to you time/money wise to pay for the service. For something like this I would only consider a service of this type offerred by the registrar I'm already dealing with. And even then, I'd double check behind them as I had time. Back in the day I worked 2 blocks from Network Solutions and had a friend that worked there as a DBA. So I had the proverbial someone you know insider access. He no longer works for them and moved to California some years ago. But it goes to the point of the working relationship you maintain with your registrar. I'm fairly cynical so I tend to believe large companies only pay attention to large accounts and have a certain tendency to ignore and forget to service the little guy. In that vein it's a YMMV, depends on who represents you on the other end of the circuit. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Radius Authentication
Hi Todor, Thanks, Ive read before that there has to be a user on the local server with the same name as the windows domain and i have used the man pages for the configuration, i think the problem lies with the autentication against the Radius server, or the Radius server itself. I shall venture forth and try to combat this plague!!! :-P thanks for the speedy reply btw! =) Todor Genov-2 wrote: Hi Matt, The three important steps here are as follows: 1.) Confirm that authentication against the RADIUS server succeeds using any command line RADIUS util. 2.) configure /etc/radius.conf as per man pam_radius and man radius.conf 3.) Add a user on the FreeBSD machine whose name corresponds with the Windows domain account (if the name contains spaces then refer to the pre-Windows2000 compatible username in AD). This is mandatory as pam_radius is only used for authentication. UID, GID, home dir and all *nix relevant account parameters are still retrieved from the local user database. An alternative to step 3 would be to use the template_user option in radius.conf, but this means that all your Windows users will appear to the system with same UID/GID as the template_user. MattAD wrote: I would just like to know if anyone on earth has been able to get the pam_radius module working on FreeBSD, using a windows domain username through ssh... ??? This has become a mystery to me. My /etc/pam.d/sshd config looks like so: # # $FreeBSD: src/etc/pam.d/sshd,v 1.16 2007/06/10 18:57:20 yar Exp $ # # PAM configuration for the sshd service # # auth authrequiredpam_nologin.so no_warn authsufficient pam_opie.so no_warn no_fake_prompts authrequisite pam_opieaccess.so no_warn allow_local authsufficient pam_radius.so no_warn try_first_pass #auth sufficient pam_krb5.so no_warn try_first_pass #auth sufficient pam_ssh.so no_warn try_first_pass authsufficient pam_unix.so no_warn try_first_pass # account account requiredpam_nologin.so #accountrequiredpam_krb5.so account requiredpam_login_access.so account requiredpam_unix.so # session #sessionoptionalpam_ssh.so session requiredpam_permit.so # password #password sufficient pam_krb5.so no_warn try_first_pass passwordrequiredpam_unix.so no_warn try_first_pass :confused: -- Regards, Todor Genov Systems Operations Verizon Business South Africa (Pty) Ltd [EMAIL PROTECTED] Tel: +27 11 235 6500 Fax: 086 692 0543 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Radius-Authentication-tp20013780p20027802.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
On Fri, Oct 17, 2008 at 02:13:45PM +0200, andys wrote: Hi, on a newly installed FreeBSD 7.0 system on a dell 1950 server I see the following error from bsdlabel. Is there any known issues with this or is the only reasonable explanation that I have managed to mess it up without even knowing? :P And should I manually change the partition c to fix the prob? Is this safe to do? bsdlabel -A /dev/da0s1 # /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 17750 sectors/unit: 285155328 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152004.2BSD 2048 16384 28552 b: 20971520 75497472 swap c: 2851536870unused0 0 # raw part, don't edit d: 20971520 209715204.2BSD 2048 16384 28552 e: 20971520 419430404.2BSD 2048 16384 28552 f: 12582912 629145604.2BSD 2048 16384 28552 bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities It's complaining that 285153687 (see c partition) does not equal 285155328 (see sectors/unit up top). thanks for any advice, Im not really confident with the FreeBSD disk management as I havent used it much, I'm left wondering why you're messing around with bsdlabel on a FreeBSD install in the first place. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
bsdlabel partiton c error message on new install
Hi, on a newly installed FreeBSD 7.0 system on a dell 1950 server I see the following error from bsdlabel. Is there any known issues with this or is the only reasonable explanation that I have managed to mess it up without even knowing? :P And should I manually change the partition c to fix the prob? Is this safe to do? bsdlabel -A /dev/da0s1 # /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 17750 sectors/unit: 285155328 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152004.2BSD 2048 16384 28552 b: 20971520 75497472 swap c: 2851536870unused0 0 # raw part, don't edit d: 20971520 209715204.2BSD 2048 16384 28552 e: 20971520 419430404.2BSD 2048 16384 28552 f: 12582912 629145604.2BSD 2048 16384 28552 bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities thanks for any advice, Im not really confident with the FreeBSD disk management as I havent used it much, thanks Andy. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: updating a port with problems (libxml2)
On Fri, 17 Oct 2008 01:01:09 -0700 (PDT) Colin Brace [EMAIL PROTECTED] wrote: $ cd /usr/ports/textproc/libxml2 $ sudo make deinstall $ sudo make reinstall clean ... It would appear that the port has not yet been updated. Is this some temporary glitch? Otherwise, the approach I use is not very robust, since I have now managed to deinstall a library upon which a dozen or so programs depend. portupgrade builds before deinstalling, and creates a backup package in case the port builds but fails to install. BTW you don't need reinstall in the above case, it's only needed if you want to install twice without using the deinstall or clean targets in between. e.g. make install pkg_delete package name of current port make reinstall ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Under heavy load internet gets killed, only a reboot can bring it back up
On Thu, 2008-10-16 at 08:56 +0900, Pyun YongHyeon wrote: It seems that msk(4) in HEAD does not build correctly on RELENG_7. Try attached patch. Save attached patch to /path/to/patch #cd /usr/src/sys/dev/msk #patch -p0 /path/to/patch/msk.watchdog.diff And rebuild your kernel. This patch failed with the following error: /if_msk.c /usr/src/sys/dev/msk/if_msk.c:845:50: error: macro MEXTADD passed 8 arguments, but takes just 7 /usr/src/sys/dev/msk/if_msk.c: In function 'msk_jumbo_newbuf': /usr/src/sys/dev/msk/if_msk.c:844: error: 'MEXTADD' undeclared (first use in this function) /usr/src/sys/dev/msk/if_msk.c:844: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/msk/if_msk.c:844: error: for each function it appears in.) *** Error code 1 Stop in /usr/obj/usr/src/sys/MYKERNEL. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
(SOLVED) Under heavy load internet gets killed, only a reboot can bring it back up
I 'solved' this by buying a new nic. It's an Eminent with a RTL8139D chipset. -- Regards, Aniruddha ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
HiJeremy, yep I understand what its complaining about I just dont understand how that could be wrong after doing a fresh install. The reason I was looking is because we left some space unallocated and I need to create a new slice or however you call it in BSD... cheers Andy. Jeremy Chadwick writes: ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
On Fri, Oct 17, 2008 at 03:20:54PM +0100, andys wrote: HiJeremy, yep I understand what its complaining about I just dont understand how that could be wrong after doing a fresh install. The reason I was looking is because we left some space unallocated and I need to create a new slice or however you call it in BSD... It sounds to me that someone left some space in the wrong part of the sysinstall process then -- they should have left some space for slices, when in fact it appears they left some space for actual partitions. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
Well its a strange one, cos mostly the free space is where it should be, the difference between the current partition c and the whole disk is very small :S. So to remedy this can I just update the size of partion c? Or am I in more trouble than that? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Installing Samba : FreeBSD Vs Linux ?
Hello I am on the way to setup a brand new Samba server with OpenLDAP backend I am very interrested by feedback of real world samba admins running it with FreeBSD or Linux , my boss push hardly to use Linux but I would much prefer FreeBSD so good arguments are welcome ( my boss is a smart guy , if I give enough litterature that says FreeBSD is better, he will be OK ) More seriously I'm also searching for eventuals benchmarks that compare those two configurations. Thanks a lot. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
On Fri, Oct 17, 2008 at 03:38:08PM +0100, andys wrote: Well its a strange one, cos mostly the free space is where it should be, the difference between the current partition c and the whole disk is very small :S. So to remedy this can I just update the size of partion c? Or am I in more trouble than that? I don't have an answer. Someone more familiar with the aspects of bsdlabel and labelling will have to answer your question. You should consider re-asking your original question on freebsd-fs. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kgdb of kernel issues FB7.0 (mangled inode)
I wasn't sure if I should have edited this. -- Message: 29 Date: Thu, 16 Oct 2008 18:48:31 -0700 From: Kayven Riese [EMAIL PROTECTED] Subject: kgdb of kernel issues FB7. To: freebsd-questions@freebsd.org, [EMAIL PROTECTED], [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 I was running my FreeBSD 7.0-RELEASE (160GB HD) on this laptop: http://www.monkeyview.net/id/965/fsck/dmesg/PB12001901.vhtml Right now I am swapped out http://www.monkeyview.net/id/965/fsck/torrent/p5120212.vhtml but I have the problem disk mounted using this: http://www.monkeyview.net/id/965/fsck/torrent/p5120226.vhtml This is a much older disk with 60GB and $ uname -a FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 $ It makes clunking sounds sometimes, but for the most part it seems to run fine. Some diagnostics on the 160GB HD FB 7.0 that have been done: # mount /dev/da0s4 /mnt/usr # fsck_ufs -y /mnt/usr ** /dev/da0s4 (NO WRITE) ** Last Mounted on /mnt/usr ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=2779162 (4 should be 0) CORRECT? no fsck_ufs: cannot alloc 871186332 bytes for inoinfo # I have been told that doing fsck while mounted is a very bad thing, but I did fsck before the above depicted instantiation of the fsck command and after this and it always did the same thing. I have done fsck using the argument /dev/da0s4, I have done fsck in single user mode (the 160GB hard boots a character based shell, but crashes and reboots during startx) and always the fsck looks the same. My configuration of the 160GB is a little goofy, in my estimation, just to explain. I currently have three hard drives representing all the times I have installed FreeBSD, two of them are dual booted with MS Vista, and this latest one with 160GB has FreeBSD all to itself, but when I was creating it, I mistook partitions for slices so I configured 4 partitions, leaving some of the disk unallocated thinking that would be good for that 10% utilization thing. I mount three partitions on /, /var, and /usr; respectively and the last one as swap. I learned the vi editor in 1985 and tend to recount the flavor of unix as evax but at this point I wonder if this evax concept is mistaken. I have done a bunch of c programming in university courses, but also spent some time doing molecular biology but they had me on a SUN SPARCstation I guess. Didn't mess with that source code. Anyway. Sorry for not being concise. I thought maybe my background might be useful information. I was told to do another diagnostic, alleged to pin the disk down as having no bad sectors: # dd if=/dev/da0 bs=65536 of=/dev/null 2442045+1 records in 2442045+1 records out 160041885696 bytes transferred in 5718.122211 secs (27988539 bytes/sec) # echo $? 0 # I was told that the fact that it returns 0 was good. I also tried the port called recoverdisk, but that was taking extremely long. I accidently disconnected the USB port # /usr/src/tools/tools/recoverdisk zsh: permission denied: /usr/src/tools/tools/recoverdisk # set -o vi # ls /usr/src/tools/tools/recoverdisk Makefilerecoverdisk.1 recoverdisk.c # cd /usr/src/tools/tools/recoverdisk # make Warning: Object directory not changed from original /usr/src/tools/tools/recoverdisk cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c recoverdisk.c cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -o recoverdisk recoverdisk.o gzip -cn recoverdisk.1 recoverdisk.1.gz # ls Makefilerecoverdisk.1 recoverdisk.c recoverdisk recoverdisk.1.gzrecoverdisk.o # ./recoverdisk usage: recoverdisk [-r worklist] [-w worklist] source-drive [destination] # ./recoverdisk /dev/da0s4 startsize len state done remaining% done 590348288 1048576 134551002112 0 590348288 134551002112 0.0043684 It had run for perhaps half an hour and still was only 0.3% done or so. finally, the guy downstairs told me to debug the kernel so I found this page: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-gdb.html and after mounting the /usr partition I am here: -rw-r--r-- 1 root wheel 21360 Jun 22 10:30 yarrow.o # kgdb
Re: Installing Samba : FreeBSD Vs Linux ?
I am very interrested by feedback of real world samba admins running it with FreeBSD or Linux , my boss push hardly to use Linux but I would much prefer FreeBSD do what your boss wants. it's his company, and it's his right to make bad decision ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bsdlabel partiton c error message on new install
On Fri, Oct 17, 2008 at 02:13:45PM +0200, andys wrote: Hi, on a newly installed FreeBSD 7.0 system on a dell 1950 server I see the following error from bsdlabel. Is there any known issues with this or is the only reasonable explanation that I have managed to mess it up without even knowing? :P And should I manually change the partition c to fix the prob? Is this safe to do? bsdlabel -A /dev/da0s1 # /dev/da0s1: type: SCSI disk: da0s1 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 17750 sectors/unit: 285155328 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 2097152004.2BSD 2048 16384 28552 b: 20971520 75497472 swap c: 2851536870unused0 0 # raw part, don't edit d: 20971520 209715204.2BSD 2048 16384 28552 e: 20971520 419430404.2BSD 2048 16384 28552 f: 12582912 629145604.2BSD 2048 16384 28552 bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities thanks for any advice, Im not really confident with the FreeBSD disk management as I havent used it much, If you were using sysinstall, I am not sure how this would come up. Do you have more than one slice on the disk - that which MS refers to as a 'primary partition'? Something you might do to create a 'dual boot' machine. Are you in the position where you can just wipe it and do a reinstall? I wouldn't just move or resize the c partition after the fact. The c partition should be equal to the size of the slice it is in. That should just be true after the fdisk part of the operation unless there is something wrong with the size or alignment of the slice itself. And, in that case, I would expect it to have complained way back in the sysinstall-fdisk part of the process. So, I would start over if I could. Just some pictorial perspective to make it easier (I hope) to visualize. Whole device | slice 1: FreeBSD Slice 2 : slice 3: Slice 4 | | : :: | | :- partition c -:: | |Some MS thing : '''' : Some Linux : Extra | | :pa' pb ' pd ' pe ' pn: thing : slice | | : '''' :: | | : '''' :: | - A device (whole disk) can have up to 4 slices labeled 1..4. Each slice can be of different types. MS calls slices 'primary partitions'. Each FreeBSD type slice can be divided in to 8 (really 7) partitions that are labeled a..h. But, c must be used to define the whole slice. Slices are created by fdisk. Fdisk also writes the device's MBR. Partitions are created by bsdlabel (disk label in early versions of FreeBSD) bsdlabel also writes the slice's boot block. It is possible to leave empty space in the whole disk that is not allocated to any slice or within any given slice that is not allocated to any partition. The total of a..h not counting c, plus any non- allocated space, must add up to c. It is possible to create what someone has dubbed a 'dangerously dedicated' disk and just not create slices, but just use bsdlabel to divide the whole disk in to FreeBSD partitions a-h. The c partition must still refer to the whole space available for FreeBSD partitioning. I think it is also possible to just newfs the disk without using either fdisk or bsdlabel and create one filesystem without slices or partitions.I haven't tried it. Both fdisk and bsdlabel are supposed to keep track of the sizes correctly, automatically. That is why I suggest starting over. If you use sysinstall, it calls fdisk and bsdlabel for you and you don't have to do it separately unless you want to look and see what it did. jerry thanks Andy. ___ 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: Installing Samba : FreeBSD Vs Linux ?
On Friday 17 October 2008 10:42:05 Wojciech Puchar wrote: do what your boss wants. it's his company, and it's his right to make bad decision This is off-topic, but I wholly disagree. As a professional employee, it's my job to advise my boss on technological matters, and to persuade him to change course if I think he's making a bad decision. I'm not paid to do data entry, but to know enough about my job to know what's best for my employer. The final decision is his, but until he's made it, I'll do what I can to steer him. -- Kirk Strauser ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
On Fri, Oct 17, 2008 at 4:42 PM, Wojciech Puchar [EMAIL PROTECTED] wrote: I am very interrested by feedback of real world samba admins running it with FreeBSD or Linux , my boss push hardly to use Linux but I would much prefer FreeBSD do what your boss wants. it's his company, and it's his right to make bad decision ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] If he's a good boss (as the poster seem to be implying) then he will be asking because he hasn't made his mind up his mind completely, but yeah don't get fired over it :) From what I have seen, both are perfectly capable and since its samba that will be doing most of the actual work its probably doesn't matter that much. Of course the next question if he goes with Linux, is which distro. Perhaps the question should be FreeBSD v Red Hat v Ubuntu v SUSE v latest flavour of the month. Since keeping it patched is essential, these sorts of admin features do matter. I am not sure what File System you plan on using but FreeBSD does have one killer feature Linux doesn't, ZFS. Linux thanks to licensing issues doesn't really have a solid implementation yet (although there have been attempts). If you need its features and can put a decent amount of RAM in to the file server, to good be a good choice and perhaps just the angle you are looking for. To be honest I haven't used ZFS in serious production yet although I have been running it at home on my DIY 1.25tb NAS without any issues for nearly a year. Still if you have spent a lot an expensive RAID system disabling it and using ZFS's superior (unless you really spent a lot on that RAID hardware) redundancy may not go down to well. Hope that's of some help. Charlie M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
On Fri, Oct 17, 2008 at 04:34:00PM +0200, Frank Bonnet wrote:
Hello
I am on the way to setup a brand new Samba server with OpenLDAP backend
I am very interrested by feedback of real world samba admins running it
with FreeBSD
or Linux , my boss push hardly to use Linux but I would much prefer FreeBSD
so good arguments are welcome ( my boss is a smart guy , if I give enough
litterature that says FreeBSD is better, he will be OK )
More seriously I'm also searching for eventuals benchmarks that compare
those two configurations.
Linux-based systems and FreeBSD systems should support Samba roughly
identically well. I seem to recall seeing some benchmarks for FreeBSD
network server operations under heavy load just crushing comparative
Linux-based servers, but I don't recall where.
Anyway, if you can find benchmarks to that effect, or at least benchmarks
that don't show Linux substantially beating FreeBSD, you should be
covered. Add in some stuff about how FreeBSD is better (for your
purposes, at least) in general, regardless of the specific Samba stuff,
and you should have a win.
FreeBSD support for Samba is, in my limited experience (haven't used
Samba much in the last four years), excellent. So is Samba support on,
for instance, Debian. I believe you'll have to look outside of Samba
support for reasons to pick one over the other.
--
Chad Perrin [ content licensed PDL: http://pdl.apotheon.org ]
print substr('Just another Perl hacker', 0, -2);
pgpfTFH33bcA2.pgp
Description: PGP signature
Re: Installing Samba : FreeBSD Vs Linux ?
On Fri, Oct 17, 2008 at 05:13:45PM +0100, Charles Mason wrote: From what I have seen, both are perfectly capable and since its samba that will be doing most of the actual work its probably doesn't matter that much. Of course the next question if he goes with Linux, is which distro. Perhaps the question should be FreeBSD v Red Hat v Ubuntu v SUSE v latest flavour of the month. Since keeping it patched is essential, these sorts of admin features do matter. And did this bug ever get addressed? If so, when/what commit? http://www.vnode.ch/fixing_seekdir The workaround is very, very painful when it comes to directories which have many files. That workaround is to disable the name cache entirely in Samba: directory name cache size = 0 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with www/mod_cband
FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? -- -- Best, David Karapetyan http://davidkarapetyan.homeunix.com University of Notre Dame Department of Mathematics 255 Hurley Hall Notre Dame, IN 46556-4618 Phone: 574-631-5706 Cell: 202-460-5173 Fax: 574-631-6579 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 12:57:41PM -0400, David Karapetyan wrote: FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? Be aware that mod_cband has quite a horrible bug. This is a Debian bug report, but the same problem applies to FreeBSD. Be sure to read the entire bug, not just the original report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418645 Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. The best solution I've found on FreeBSD is to use pf(4) with ALTQ, and give each VirtualHost its own IP address, then rate-limit the IP address using pf(4). Yes, I realise this is impractical for sites which have many vhosts and use name-based virtualhosts. Welcome to my world... -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
On Friday 17 October 2008 18:55:19 Jeremy Chadwick wrote: On Fri, Oct 17, 2008 at 05:13:45PM +0100, Charles Mason wrote: From what I have seen, both are perfectly capable and since its samba that will be doing most of the actual work its probably doesn't matter that much. Of course the next question if he goes with Linux, is which distro. Perhaps the question should be FreeBSD v Red Hat v Ubuntu v SUSE v latest flavour of the month. Since keeping it patched is essential, these sorts of admin features do matter. And did this bug ever get addressed? If so, when/what commit? http://www.vnode.ch/fixing_seekdir lib/libc/gen/readdir.c revision 1.15 date: 2008/05/05 14:05:23; author: kib; state: Exp; lines: +7 -6 Do not read away the target directory entry when encountering deleted files after a seekdir(). The seekdir shall set the position for the next readdir operation. When the _readdir_unlocked() encounters deleted entry, dd_loc is already advanced. Continuing the loop leads to premature read of the target entry. Submitted by: Marc Balmer mbalmer at openbsd org Obtained from: OpenBSD MFC after: 2 weeks -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Friday 17 October 2008 19:53:59 Jeremy Chadwick wrote: Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. Never used it, but www/mod_bw is not a real world alternative? -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 08:31:29PM +0200, Mel wrote: On Friday 17 October 2008 19:53:59 Jeremy Chadwick wrote: Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. Never used it, but www/mod_bw is not a real world alternative? http://www.ivn.cl/apache/files/txt/mod_bw-0.8.txt I believe the problem I ran into with this module was that it would only work with static content, and not with interpreted languages (such as PHP) or other things. I know there's a directive in the module to tell it what output types it supports, but I don't think it worked quite right. I'd have to go back and try it. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no access to web server behind ipfw
Chen Xu wrote: $cmd 100 divert natd ip from any to any in via $pif $cmd 101 check-state You use in via $pif, I'm not 100% sure but I think you should only use via $pif. # Authorized inbound packets $cmd 421 allow tcp from any to 192.168.1.10 80 in via $pif setup limit src-addr 5 I think it's bad to use statefull rules for inbound connections. -- Christer Hermansson http://www.chdevelopment.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
--- On Fri, 10/17/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: Problem with www/mod_cband To: David Karapetyan [EMAIL PROTECTED] Cc: freebsd-questions@freebsd.org, [EMAIL PROTECTED] Date: Friday, October 17, 2008, 1:53 PM On Fri, Oct 17, 2008 at 12:57:41PM -0400, David Karapetyan wrote: FreeBSD office19.resnet.nd.edu 7.0-RELEASE-p5 FreeBSD 7.0-RELEASE-p5 #0: Wed Oct 1 10:10:12 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Hello everyone. Every time I try to use the mod_cband module in my apache22 webserver, apache segfaults upon restart. Things work fine when I disable the module from httpd.conf. Is this module broken, and if so, what comparable alternatives are there? Be aware that mod_cband has quite a horrible bug. This is a Debian bug report, but the same problem applies to FreeBSD. Be sure to read the entire bug, not just the original report. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418645 Regarding alternatives: there aren't. Bandwidth limiting is a long-standing feature of Apache that's missing, which is a huge disappointment. The best solution I've found on FreeBSD is to use pf(4) with ALTQ, and give each VirtualHost its own IP address, then rate-limit the IP address using pf(4). Yes, I realise this is impractical for sites which have many vhosts and use name-based virtualhosts. Welcome to my world... IMHO, that solution is considerably sexier than what mod_cband claims to do (having read only pkg-descr). It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files and makes an update to a .htaccess file for the virtualhost when the virtualhost in question exceeds a given bandwidth limit which would be configured in the script. Think `tail -f`. Functionality is handled outside of apache so no danger of crashes. Just create the .htaccess in such a way that the end-user can't delete/modify it, and have it do a Redirect. For robustness' sake, move any existing .htaccess file to .htaccess.X and move it back when the virtualhost is back in compliance or paid up or whatever. - mdh __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problem with www/mod_cband
On Friday 17 October 2008 20:47:38 mdh wrote: IMHO, that solution is considerably sexier than what mod_cband claims to do (having read only pkg-descr). It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files I don't think you fully understand the problem. Apache writes a served file to the log when a download is *completed*. Consider a 700MB iso download and you quickly see your solution will not work. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no access to web server behind ipfw
Hi Christer, I followed the example from the handbook. Yes, it is OK to divert in and out separately. skipto is used to point to the divert out rule number when it is outbound. I run into problem only when with natd to redirect from gateway to local machine. tcpdump shows that packets of both directions are actually go through fine, but only head is there, body was ripped off. I am looking into OpenBSD's PF right now. It is such a simple goal to reach but seems not so easy. -Chen * Christer Hermansson [EMAIL PROTECTED] [081017 14:54]: Chen Xu wrote: $cmd 100 divert natd ip from any to any in via $pif $cmd 101 check-state You use in via $pif, I'm not 100% sure but I think you should only use via $pif. # Authorized inbound packets $cmd 421 allow tcp from any to 192.168.1.10 80 in via $pif setup limit src-addr 5 I think it's bad to use statefull rules for inbound connections. -- Christer Hermansson http://www.chdevelopment.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
decision This is off-topic, but I wholly disagree. As a professional employee, it's my job to advise my boss on technological matters, yes - advise no - persuade! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
If he's a good boss (as the poster seem to be implying) then he will be asking because he hasn't made his mind up his mind completely, but yeah don't get fired over it :) in most cases and with system doing ONLY samba, both linux and freebsd will work fine. so his boss is not smart for sure persuading his employer linux (or whatever), instead of just saying make it work fine, whatever you do ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
Uit een eerder bericht (17-10-2008 17:42): do what your boss wants. it's his company, and it's his right to make bad decision A boss hires someone that knows what he/she is talking about and relies on his/her vision. To get informed this person might get his/her information before he/she decides what the best solution might be; I do hope he/she doesn't take any notice on your stupid reply. Jos Chrispijn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
A boss hires someone that knows what he/she is talking about and relies on his/her vision. so - he/she should not persuade what OS will be, just WHAT should be done. To get informed this person might get his/her information before he/she decides what the best solution might be; I do hope he/she doesn't take any notice on your stupid reply. what reply is stupid ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how determine all possible drivers for my system
Hello maillist of my favorite WortstationServer OS
May i asking: how i can determine all drivers of existing devices, but who is
not present in GENERIC kernel.
For definition of all devices useful to me I have written the following a
little stupid script:
--
#!/bin/sh
MODLIST=`find /boot/kernel -type f -name *.ko -print`
LOGFILE=/var/tmp/kldlog.txt
# ignore for kldload module
IGNORE_MODLIST=/boot/kernel/kernel.ko /boot/kernel/tom.ko
/boot/kernel/iw_cxgb.ko
# (comment: tom.ko and iw_cwbg.ko after loading make kernel panic on my
system)
REPORTS=/var/tmp/reports.txt
FINAL_FILTER=(already exist)|(File exist)|(Unsupported file type)|\
(already present)|(failed to register)|(Exec format error)|\
(symbol [aA-zZ]++ undefin)|(Weak symbols not supported)|\
(already registered)|(unable to register)
# not know another easy way for fopen(/dev/klog)
/etc/rc.d/syslogd stop
echo kern.*${LOGFILE} /var/tmp/syslogd.conf
syslogd -f /var/tmp/syslogd.conf
#
truncate -s0 ${LOGFILE}
for MOD in ${MODLIST}; do
ignore=0
for IGNORE_MOD in $IGNORE_MODLIST; do
if [ ${IGNORE_MOD} = ${MOD} ]; then
ignore=1
fi
done
if [ $ignore -eq 1 ]; then
echo Skipping ${MOD}... ${LOGFILE}
else
echo Try Loading ${MOD}... ${LOGFILE}
sync;
kldload ${MOD} ${LOGFILE} 21
fi
done
/etc/rc.d/syslogd start
egrep -Eiv \${FINAL_FILTER}\ ${LOGFILE} |tee ${REPORTS}
-
Result working off that scripts is the file reports.txt: {
Oct 17 23:51:11 kernel: acpi_aiboost0: ASUStek AIBOOSTER on acpi0
Oct 17 23:51:11 kernel: ppc0: cannot reserve I/O port range
Oct 17 23:51:12 kernel: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24
ascq=0x00 sks=0x48 0x00 0x01
Oct 17 23:51:12 kernel: cd0 at ata3 bus 0 target 0 lun 0
Oct 17 23:51:12 kernel: cd0: PIONEER DVD-RW DVR-212D 1.09 Removable CD-ROM
SCSI-0 device
Oct 17 23:51:12 kernel: cd0: 3.300MB/s transfers
Oct 17 23:51:12 kernel: cd0: Attempt to query device size failed: NOT READY,
Medium not present
Oct 17 23:51:12 kernel: cryptosoft0: software crypto on motherboard
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtmalloc.ko: depends on dtrace - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtraceall.ko: depends on profile - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD dtraceall.ko: depends on profile - not available
Oct 17 23:51:13 kernel: KLD dtrace_test.ko: depends on dtraceall - not
available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD profile.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD prototype.ko: depends on dtrace - not available
Oct 17 23:51:13 kernel: This module (opensolaris) contains code covered by
the
Oct 17 23:51:13 kernel: Common Development and Distribution License (CDDL)
Oct 17 23:51:13 kernel: see
http://opensolaris.org/os/licensing/opensolaris_license/
Oct 17 23:51:13 kernel: KLD dtrace.ko: depends on cyclic - not available
Oct 17 23:51:13 kernel: KLD sdt.ko: depends on dtrace
Re: Problem with www/mod_cband
On Fri, Oct 17, 2008 at 11:47:38AM -0700, mdh wrote: It seems possible, however, that mod_cband's functionality could be replicated by a simple script that watches the access log files and makes an update to a .htaccess file for the virtualhost when the virtualhost in question exceeds a given bandwidth limit which would be configured in the script. Well, that's assuming you want to use the maximum aggregate bandwidth per site every month concept. I, for one, do not, because all it takes is one prick wget -r'ing the site and pow, the site is down for everyone. You could block based on IP, but believe me, they'll find or get another. (I've personally seen this with Italian users, where they'd switch to another IP to get around pf(4) blocks I put in place.) I personally prefer to just bandwidth limit sites, only permitting XXX Kbyte/sec across *all visitors*. It's the only safe way to deal with 95th-percentile billing in co-locations. Also, don't forget that Apache only writes an entry to the log file *after* the transfer is finished, not when the request is submit. :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
new compiler error?
Hi: I have been trying to upgrade to the latest gnash on my W/S running: FreeBSD 6.3-RELEASE-p5 #3. First, I upgraded the kernel and base to the latest patch level, then I executed a portupgrade -R gnash, and after all the pre-requisite packages were upgraded successfully gnash itself began to compile. Then this: === ../libcore/.libs/libgnashcore.so: undefined reference to `std::basic_ostreamchar, std::char_traitschar std::basic_ostreamchar, std::char_traitschar ::_M_insertbool(bool)' /usr/ports/graphics/gnash/work/gnash-0.8.4/libbase/.libs/libgnashbase.so: undefined reference to `std::basic_istreamchar, std::char_traitschar std::basic_istreamchar, std::char_traitschar ::_M_extractunsigned int(unsigned int)' collect2: ld returned 1 exit status gmake[2]: *** [gprocessor] Error 1 gmake[2]: Leaving directory `/usr/ports/graphics/gnash/work/gnash-0.8.4/utilities' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/graphics/gnash/work/gnash-0.8.4' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/graphics/gnash. *** Error code 1 Stop in /usr/ports/graphics/gnash. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.43253.1 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gnash-0.8.2_2 UPGRADE_PORT_VER=0.8.2_2 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! graphics/gnash (gnash-0.8.2_2)(new compiler error) === What do I need to do to get this accomplished? I am struggling with limited flash support, and have been doing fairly well with gnash/firefox. I would like to upgrade my gnash-0.8.2_2 to the latest version gnash-0.8.4. and possibly get a bit more functionality. Oh, one more possible clue. The first time I attempted this, I issued a portupgrade gnash without recursion. At about the same point of failure, the system powered down. I mean I saw an LD error, and then POOF, laptop went power-down! I didn't believe that was the cause, so after cleaning the file systems, I tried again, and again it powered down. So I pretty much upgraded everything and after the -R attempt, gnash simply failed. TIA Bob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
back to kde3
People, I spent the past several days trying to insure that everythinge kde4 was properly set to run upon reboot. But upon rebooting just now, I find myself back in kde3. i Yanked the startup from /etc/ttys, so *must* have hit the old kdm[3] from root. No problem with version3--at least things Work there. What I'm wondering is: if with some future release, say, 7.2 or 7.3, will our KDE default to version 4? gary -- Gary Kline [EMAIL PROTECTED] http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DHCP release/renew lease - elegant solution?
I have an always-on FreeBSD box which is connected to the internet. My ISP is some cable company and the IP address is determined via DHCP; I used to always get the same IP address but recently the address seems to be changing very frequently whenever I reboot the machine. My problem is that recently, after being on for a day or so, the internet connection to the FreeBSD box breaks down, it stops working or becomes very intermittent/flaky. I then reboot the machine, and thereafter it usually uses a new IP address and the internet connection returns fo running fine. There is no need to reboot the cable modem. My goal is to do some dhclient magic which will automatically fix this problem without needing a reboot of the machine. If possible, I would like to have the same IP address as often as possible, but I'm not sure that this is possible. My FreeBSD version is 5.5, so it uses the ISC DHCP client, but the details between the current DHCP client and mine are probably insignificant. My /etc/dhclient.conf file is empty. I have been reading man pages, and it seems that the way to release, get a new IP address is this: dhclient -r dhclient fxp0 An except from my dhclient man page: The client normally doesn't release the current lease as it is not required by the DHCP protocol. Some cable ISPs require their clients to notify the server if they wish to release an assigned IP address. The -r flag explicitly releases the current lease, and once the lease has been released, the client exits. I could put this into a crontab and run it every 12 hours. However, this does not seem like a very elegant solution to my problem. I am wondering whether there is a more elegant solution. Thanks in advance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
I have tried the reccomendations that you guys have suggested with no luck. Is
there a site that I could get some sample filters I could try? I have tried a
few that were in the freebsd corporate guide. This printer will work from
Windows printer spooler and this BSD box can print to a HP just fine.
Here is my current printcap.
corp-admin|hp|laserjet|Hewlett Packard LaserJet 5Si:\
:lp=\
:sd=/var/spool/output/corp-admin:\
:rm=corp-admin:\
:lf=/var/log/lpd-errs:\
:if=/usr/local/libexec/crlfilter:\
:sh:\
:tr=\f:\
:mx#0:
admincolor|LANIER LD160c RPCS:\
:lp=\
:mx#0:\
:sd=/var/spool/output/admincolor:\
:rm=admincolor:\
:lf=/var/log/lpd-errs:\
:if=/usr/local/libexec/crfilter:\
:sh:\
:tr=\f:
And here is the filter
#!/bin/sh
# /usr/local/libexec/crlfilter
#
# simple parlor trick to add CR to LF for printer
# Every line of standard input is printed with CRLF
# attached.
#
awk '{printf %s\r\n, $0}' -
-- Original message --
From: Warren Block [EMAIL PROTECTED]
On Thu, 16 Oct 2008, [EMAIL PROTECTED] wrote:
I am trying to setup a Lanier LD160c (admincolor) that has a network
interface. I am new to FreeBSD and tried to follow the handbook. I
am able to print to a HP 5SI (corp-admin) with no problems. There are
no errors in the lpd-errs and the file is drained from the queue, but
the printer does not print anything. And this is a working printer to
Windows. lpr -P admincolor testfile.txt
printcap:
corp-admin|hp|laserjet|Hewlett Packard LaserJet 5Si:\
:lp=\
:sd=/var/spool/output/corp-admin:rm=corp-admin:\
:lf=/var/log/lpd-errs:\
:if=/usr/local/libexec/crlfilter:sh:tr=\f:mx#0:
admincolor|hp|laserjet|LANIER LD160c RPCS:\
:lp=\
:sd=/var/spool/output/admincolor:rm=admincolor:\
:lf=/var/log/lpd-errs:
Note here that in the second entry you don't have the :sh: and :mx#0:
entries. No :if=: either, but maybe that's because you don't need an
input filter for this printer.
At first guess, this printer may be touchy about the print queue name.
That's the :rp=: parameter, which is not here at all. There are a
couple of KB entries on the Lanier site that say to use lp.
printcap entries are easier to read if you put one option per line:
admincolor:\
:lp=:\
:sh:\
:mx#0:\
:rm=admincolor:\
:rp=lp:\
:sd=/var/spool/output/admincolor:\
:lf=/var/log/lpd-errs:
-Warren Block * Rapid City, South Dakota USA
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: back to kde3
--- On Fri, 10/17/08, Gary Kline [EMAIL PROTECTED] wrote: From: Gary Kline [EMAIL PROTECTED] Subject: back to kde3 To: FreeBSD Mailing List freebsd-questions@FreeBSD.ORG Date: Friday, October 17, 2008, 5:39 PM People, I spent the past several days trying to insure that everythinge kde4 was properly set to run upon reboot. But upon rebooting just now, I find myself back in kde3. i Yanked the startup from /etc/ttys, so *must* have hit the old kdm[3] from root. If you installed from ports, change the line in /etc/ttys from /usr/local/bin/kdm to /usr/local/kde4/bin/kdm The KDE4 stuff is all installed under /usr/local/kde4 in order to not conflict with KDE3 installs. - mdh __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: back to kde3
myself back in kde3. i Yanked the startup from /etc/ttys, so *must* have hit the old kdm[3] from root. No problem with version3--at least things Work there. What I'm wondering is: if with some future release, say, 7.2 or 7.3, will our KDE default to version 4? my default to xdm, and fvwm2 :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
lpr -P admincolor testfile.txt printcap: corp-admin|hp|laserjet|Hewlett Packard LaserJet 5Si:\ :lp=\ :sd=/var/spool/output/corp-admin:rm=corp-admin:\ :lf=/var/log/lpd-errs:\ :if=/usr/local/libexec/crlfilter:sh:tr=\f:mx#0: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: i have no idea what does :lp=\ do. my setup is like yours for network printers except of that. anything else is fine. is your printer printer compatible i mean can it get textfiles? or maybe it'spostscript only or whatever? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
If this printer is hooked up on the network (e.g. via Ethernet), I believe you need to set the lp variable to the hostname or IP address of the printer, e.g.: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=192.168.1.100\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: I think this also makes the assumption that the printer knows how to speak the LPR protocol. If it listens on a custom port, you can use [EMAIL PROTECTED] instead. See the printcap(5) man page, I guess. he said that lpd queue gets drained. so printer DO accept the data. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (SOLVED) Under heavy load internet gets killed, only a reboot can bring it back up
I 'solved' this by buying a new nic. It's an Eminent with a RTL8139D chipset. you SOLVED it not 'solved'. onboard NICs are usually crap, except high end motherboard. they solder in what's cheapest in the moment. if chips are buggy, they add workaround in windoze drivers. and finally - for average windoze user there is nothing strange that he/she needs to reboot the system many times a day. they don't even know why network stopped working - is it hardware problem, driver problem, system crash. they just reboot. on 3 motherboards i've got with gigabit NIC, 1 are completely unusable (nvidia), one are barely usable after turning off txcsum and rxcsum: re0: RealTek 8168/8168B/8168C/8168CP/8111B/8111C/8111CP PCIe Gigabit Ethernet port 0xd000-0xd0ff mem 0xf900-0xf9000fff irq 17 at device 0.0 on pci4 re0: turning off MSI enable bit. re0: Chip rev. 0x3800 re0: MAC rev. 0x the fully working one is: bge0: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev. 0x4101 mem 0xc010-0xc010 irq 16 at device 0.0 on pci3 miibus0: MII bus on bge0 bge0: Ethernet address: 00:14:5e:94:49:19 bge0: [ITHREAD] but the last one is on IBM server. i've just seen re0: turning off MSI enable bit. looks like fix recently added as i upgraded this machine to 7.1 from 6.3 already funny thing - feature that has to be disabled ;) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing Samba : FreeBSD Vs Linux ?
On Fri, Oct 17, 2008 at 8:04 PM, Frank Bonnet [EMAIL PROTECTED] wrote: Hello I am on the way to setup a brand new Samba server with OpenLDAP backend I am very interrested by feedback of real world samba admins running it with FreeBSD or Linux , my boss push hardly to use Linux but I would much prefer FreeBSD so good arguments are welcome ( my boss is a smart guy , if I give enough litterature that says FreeBSD is better, he will be OK ) More seriously I'm also searching for eventuals benchmarks that compare those two configurations. Thanks a lot. Hi This is probably not a reliable or objective comparison, but I get much better performance at home b/w a fbsd7/windows vista client and a fbsd6.2 server (freenas) over a 11g wireless network than in the office b/w a windows xp client and an ubuntu 8.04 server over a 100 Mbps ethernet network (even if I am the only person using the server). my server at home runs on an assembled 1.8 GHz athlon xp system with 512 MB RAM. The one in the office is a Wipro NetPower server with a 3 GHz Pentium 4 and 2 GB RAM. both servers run the default samba versions they came with, and both clients are kept upto date it could possibly be a problem with the default ubuntu server configuration, but i have not checked it out yet -- Gautham Ganapathy http://lisphacker.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: back to kde3
On Fri, 17 Oct 2008 14:39:23 -0700 Gary Kline [EMAIL PROTECTED] wrote: I spent the past several days trying to insure that everythinge kde4 was properly set to run upon reboot. But upon rebooting just now, I find myself back in kde3. i Yanked the startup from /etc/ttys, so *must* have hit the old kdm[3] from root. No problem with version3--at least things Work there. What I'm wondering is: if with some future release, say, 7.2 or 7.3, will our KDE default to version 4? Do you mean it defaults to the old version of kdm? They're in different locations, you have to set one of following ttyv8 /usr/local/kde4/bin/kdm -nodaemon xterm on secure ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure Whichever version you use, kdm defaults to the last desktop or window manager. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Oddities with VLAN/CARP Interfaces on Primary/Failover Setup
Mike Sweetser - Adhost wrote: We currently have a primary/failover setup for two FreeBSD 6.3 servers running PF, and we're running into odd issues when setting up multiple subnets on a single VLAN and CARP interface. We have issues with them coming up properly, and even worse, having both servers believe they are master. If both instances think they're MASTER, make sure you're allowing the multicast traffic for syncing state (in ipfw): | allow carp from $partner to 224.0.0.18 in via $iface Carp is protocol 112 from /etc/protocols. Here's a snippet of one of the VLANs and CARP interfaces in question: ifconfig_vlan10=inet 10.142.255.252 netmask 255.255.0.0 vlan 10 vlandev em2 ifconfig_vlan10_alias0=inet 10.210.0.2 netmask 255.255.0.0 ifconfig_carp10=inet 10.142.255.254 netmask 255.255.0.0 vhid 10 advskew 0 pass testpass ifconfig_carp10_alias0=inet 10.210.0.1 netmask 255.255.0.0 The main difference between this and our other VLAN/CARP interfaces is that because it's separate subnets, the aliases here are set up with /16 netmasks, while the regular aliases on the others are set up with /32s. Is this correct, or should these also be set as /32s? It's correct. If you did a /32 on the alias, your system would have no way of knowing how large the second subnet is. The /32 netmask is for adding an alias on the same subnet. I'm not sure carp can work correctly with aliases. Have you tried creating a separate vhid instance per subnet? For example: | ifconfig_vlan10=inet 10.142.255.252 netmask 255.255.0.0 vlan 10 vlandev em2 | ifconfig_vlan10_alias0=inet 10.210.0.2 netmask 255.255.0.0 | ifconfig_carp10=inet 10.142.255.254 netmask 255.255.0.0 vhid 10 advskew | 0 pass testpass | ifconfig_carp11=inet 10.210.0.1 netmask 255.255.0.0 vhid 11 advskew | 0 pass testpass -- Chris Cowart Network Technical Lead Network Infrastructure Services, RSSP-IT UC Berkeley pgpqOoyOt5N1x.pgp Description: PGP signature
Re: freebsd-questions Digest, Vol 237, Issue 16
--- Message: 11 Date: Fri, 17 Oct 2008 08:39:40 -0700 From: Kayven Riese [EMAIL PROTECTED] Subject: Re: kgdb of kernel issues FB7.0 (mangled inode) To: freebsd-questions@freebsd.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 I need to keep posting to questions because I don't know how to ask questions. I can't run my drive that is currently mounted with its partitions like this: device name would be mounted if masteris mounted now /dev/da0s1 //mnt/tmp /dev/da0s3 /var /mnt/var /dev/da0s4 /usr /mnt/usr I can't run this hardrive. It is my newest. I can mount it and I can get a single user prompt. Before It crashed it would give me a character based shell, and then I would type startx and get KDE. Now it reboots on startx. It had some sort of mangled inode (see below) but the fsck -y -f /usr that I have done in single user mode just now after swapon -a failed just like all the other times I have done fsck on it (see below) requesting 0.871 TBytes or something. I have just learned about var/crash and providing that wy waaay at the bottom of this transmission. I wasn't sure if I should have edited this. -- Message: 29 Date: Thu, 16 Oct 2008 18:48:31 -0700 From: Kayven Riese [EMAIL PROTECTED] Subject: kgdb of kernel issues FB7. To: freebsd-questions@freebsd.org, [EMAIL PROTECTED], [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 I was running my FreeBSD 7.0-RELEASE (160GB HD) on this laptop: http://www.monkeyview.net/id/965/fsck/dmesg/PB12001901.vhtml Right now I am swapped out http://www.monkeyview.net/id/965/fsck/torrent/p5120212.vhtml but I have the problem disk mounted using this: http://www.monkeyview.net/id/965/fsck/torrent/p5120226.vhtml This is a much older disk with 60GB and $ uname -a FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 11:05:30 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP i386 $ It makes clunking sounds sometimes, but for the most part it seems to run fine. Some diagnostics on the 160GB HD FB 7.0 that have been done: # mount /dev/da0s4 /mnt/usr # fsck_ufs -y /mnt/usr ** /dev/da0s4 (NO WRITE) ** Last Mounted on /mnt/usr ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=2779162 (4 should be 0) CORRECT? no fsck_ufs: cannot alloc 871186332 bytes for inoinfo # I have been told that doing fsck while mounted is a very bad thing, but I did fsck before the above depicted instantiation of the fsck command and after this and it always did the same thing. I have done fsck using the argument /dev/da0s4, I have done fsck in single user mode (the 160GB hard boots a character based shell, but crashes and reboots during startx) and always the fsck looks the same. My configuration of the 160GB is a little goofy, in my estimation, just to explain. I currently have three hard drives representing all the times I have installed FreeBSD, two of them are dual booted with MS Vista, and this latest one with 160GB has FreeBSD all to itself, but when I was creating it, I mistook partitions for slices so I configured 4 partitions, leaving some of the disk unallocated thinking that would be good for that 10% utilization thing. I mount three partitions on /, /var, and /usr; respectively and the last one as swap. I learned the vi editor in 1985 and tend to recount the flavor of unix as evax but at this point I wonder if this evax concept is mistaken. I have done a bunch of c programming in university courses, but also spent some time doing molecular biology but they had me on a SUN SPARCstation I guess. Didn't mess with that source code. Anyway. Sorry for not being concise. I thought maybe my background might be useful information. I was told to do another diagnostic, alleged to pin the disk down as having no bad sectors: # dd if=/dev/da0 bs=65536 of=/dev/null 2442045+1 records in 2442045+1 records out 160041885696 bytes transferred in 5718.122211 secs (27988539 bytes/sec) # echo $? 0 # I was told that the fact that it returns 0 was good. I also tried the port called recoverdisk, but that was taking extremely long. I accidently disconnected the USB port # /usr/src/tools/tools/recoverdisk zsh: permission denied: /usr/src/tools/tools/recoverdisk # set -o vi # ls /usr/src/tools/tools/recoverdisk Makefilerecoverdisk.1 recoverdisk.c # cd /usr/src/tools/tools/recoverdisk # make Warning: Object directory not changed from original /usr/src/tools/tools/recoverdisk cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall
Re: DHCP release/renew lease - elegant solution?
On Fri, 17 Oct 2008 14:24:00 -0700 Nerius Landys [EMAIL PROTECTED] wrote: The -r flag explicitly releases the current lease, and once the lease has been released, the client exits. I could put this into a crontab and run it every 12 hours. However, this does not seem like a very elegant solution to my problem. I am wondering whether there is a more elegant solution. Before you look for a more elegant solution I suggest you try the inelegant solution and see if it actually works. At the moment all you really know is that rebooting fixes the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
On Fri, 17 Oct 2008, [EMAIL PROTECTED] wrote: I have tried the reccomendations that you guys have suggested with no luck. Here is my current printcap. admincolor|LANIER LD160c RPCS:\ :lp=\ :mx#0:\ :sd=/var/spool/output/admincolor:\ :rm=admincolor:\ :lf=/var/log/lpd-errs:\ :if=/usr/local/libexec/crfilter:\ :sh:\ :tr=\f: Please trim your responses and don't top-post, as it makes responding to your messages difficult. The printcap still has no :rp=lp: line. HP printers aren't picky about that, but other brands sometimes are. You've also added a filter and kept the multiple printer names. Things like that make more complexity to debug. Wait until you have basic communication working. The exact suggested printcap entry: admincolor:\ :lp=:\ :sh:\ :mx#0:\ :rm=admincolor:\ :rp=lp:\ :sd=/var/spool/output/admincolor:\ :lf=/var/log/lpd-errs: Note: one printer name (who needs more than one, really?). rm= and rp= entries. No filter; I think that printer can handle PostScript and PCL. Put that printcap entry in /etc/printcap, then send a PostScript test to the printer (all one line): printf %%\!PS\n/Courier findfont 20 scalefont setfont 72 72 moveto (Test!) show showpage\f | lpr -P admincolor -Warren Block * Rapid City, South Dakota USA___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: back to kde3
On Friday 17 October 2008 16:26:54 RW wrote: On Fri, 17 Oct 2008 14:39:23 -0700 Gary Kline [EMAIL PROTECTED] wrote: I spent the past several days trying to insure that everythinge kde4 was properly set to run upon reboot. But upon rebooting just now, I find myself back in kde3. i Yanked the startup from /etc/ttys, so *must* have hit the old kdm[3] from root. No problem with version3--at least things Work there. What I'm wondering is: if with some future release, say, 7.2 or 7.3, will our KDE default to version 4? Do you mean it defaults to the old version of kdm? They're in different locations, you have to set one of following ttyv8 /usr/local/kde4/bin/kdm -nodaemon xterm on secure ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure Whichever version you use, kdm defaults to the last desktop or window manager. Thanks. I was hoping that when KDE4 was more stable, polished, we would say goodbye to version 3 and have just-one new KDE. ___ 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]
Disable CTRL-ALT-DEL
Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
