Re: /etc/rc.d/named dilemma
Nerius Landys nlan...@gmail.com wrote: I am still bambuzzled by the network taking 30 seconds to come up. One thing I've run into recently is an Ethernet switch that needs to resolve spanning tree after a port reset. The physical link comes back up quickly, but it seems to take about 30 seconds before the switch will handle any traffic. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
Hi, I'm trying to update the netatalk port to its newest version. uname -a FreeBSD piggie.int.daemon.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I use portmaster -a to update the ports but when it reaches netatalk it gives this error message: - === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. [snip] === Giving up on fetching files: netatalk-2.0.4.tar.bz2 netatalk-2.0.4.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/net/netatalk/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 Stop in /usr/ports/net/netatalk. *** Error code 1 Stop in /usr/ports/net/netatalk. === make failed for net/netatalk === Aborting update === Update for netatalk-2.0.3_5,1 failed === Aborting update --- I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Anyone any idea how to solve this? Vincent ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2
On Sun 2009-08-23 10:24:53 UTC+0200, Vincent Zee (zen...@xs4all.nl) wrote: === Vulnerability check disabled, database not found === Extracting for netatalk-2.0.4,1 = MD5 Checksum mismatch for netatalk-2.0.4.tar.bz2. = SHA256 Checksum mismatch for netatalk-2.0.4.tar.bz2. I'm getting a checksum mismatch here too. This probably means the tarball was modified. I checked the distinfo file and it is the same as on my other machine. On which the update went fine. Solution #1: Use make NO_CHECKSUM=yes, just ignore the mismatch and hope it will build. Solution #2: Copy /usr/ports/distfiles/netatalk-2.0.4.tar.bz2 from your other machine and rebuild. Solution #3: Don't bother building from ports if you already have a working binary on your other machine. Use pkg_create -vb netatalk\*, copy the resulting file to the new machine, then use pkg_add. This assumes the same architecture (eg. i386) on both machines. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Serial console trouble: loader and login works, but no kernel messages
First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Translation
Dear FreeBSD, Just question about translated version of FreeBSD if it available in Lao Language or not? if not how can I start to translate this FreeBSD in to Lao. Your sincerely, Nakhonekham Xongmixay Managing Director Nakhonevaly URI: http://www.nakhonevaly.com Tel: +856(0)20 2426689 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
mplayer - fribidi
After update fribidi (FreeBSD 7.2), mplayer stop working: mplayer /libexec/ld-elf.so.1: Shared object libfribidi.so.0 not found, required by mplayer. Rebuild of mplayer doesn't work with a new fribidi: === mplayer-0.99.11_14 depends on shared library: fribidi.0 - not found ===Verifying install for fribidi.0 in /usr/ports/converters/fribidi === Returning to build of mplayer-0.99.11_14 Error: shared library fribidi.0 does not exist *** Error code 1 Stop in /usr/ports/multimedia/mplayer. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. === make failed for multimedia/mplayer === Aborting update Thanks. -- Mitja - http://starikarp.redbubble.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: cvs tag usage
free...@edvax.de wrote: If you are interested in the bleeding edge of FreeBSD's development, you follow RELENG_7. This will then deliver the -CURRENT branch to you with all modifications. It may happen that a -CURRENT of today doesn't compile, but tomorrow, it will do. It's considered to be the experimental branch where changes can appear and disappear. Hello, I think you are confusing RELENG_7 with . (as the CVS tag says) or HEAD. RELENG_7 will deliver 7-STABLE, not CURRENT. CURRENT is the bleeding edge. Also: You follow the -STABLE branch of FreeBSD 7.2 and will always get the latest *stable* 7.2 sources, but won't reach 7.3 with this setting. That's not quite right. 7.3 is just a point along the 7-STABLE path. For example, if you tracked STABLE via RELENG_7 starting with, say, FreeBSD 7.1, your system would have run 7.2 at some point, and then beyond it. Tracking STABLE isn't like using CVSup or Csup to reach RELENG_7_2_0 or RELENG_7_2, but you eventually get the 7.2 functionality by tracking RELENG_7. For example, start with 7.1 from CD: fbsd71toS# uname -a FreeBSD fbsd71toS.taosecurity.com 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan 1 14:37:25 UTC 2009 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 After Csup to RELENG_7, you get fbsd71toS# uname -a FreeBSD fbsd71toS.taosecurity.com 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat Aug 22 23:02:30 EDT 2009 r...@fbsd71tos.taosecurity.com:/usr/obj/usr/src/sys/FREEBSD7 i386 As you can see, it's not theoretical -- I ran this test this weekend. :) Thank you, Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: netbooks for freebsd?
Wednesday, 19 August 2009 at 16:00:25 -0700, Steve Franks said: Al Plant wrote: Jeff Hamann wrote: I would like to try some experimental software on a netbook. Can somebody recommend a netbook that can do FreeBSD. I'm displeased with my Lenovo S10. On the upside, all the hardware worked on 7.2 out of the box, after I swapped the internal broadcom wifi for a highpower atheros. The ACPI is a real nightmare on it, however. dmesg is constantly full of acpi barfs, and it hangs on shutdown, and won't suspend, which is pretty much a requirement for a notebook at my house. Tried all the standard lenovo acpi hacks, but no luck. I'm running 7.2 release on an s10e. The acpi is a problem - but David Naylor on the acpi@ list gave me a patch which eliminated most of the errors. Let me know if you're interested and I'll ping it over (or try the acpi list to see if there's an update). Haven't tried suspend-resume, but I am running the broadcom wireless successfully with ndis. Peter Harrison. Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: No Device Node assigned for HD?
You have two options: 1. Use the RR2310 BIOS screen (or hptraidconf from inside FreeBSD) to initialize the drive and create a single drive JBOD array with it. 2. Connect the drive to a header on your motherboard and create a partition table on it, then reconnect it to your RR2310 card. I would suggest doing #2 above if you don't plan on using the drive as part of a RR2310-controlled array. If you add a partition table and let your RR2310 card treat it as Legacy then the drive can be moved around freely between motherboard connectors and RR2310 connectors. If you do #1 then you need a RocketRAID card to access the data on the drive. /Daniel Eriksson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: netbooks for freebsd?
2009/8/19 Jeff Hamann jeff.ham...@forestinformatics.com: I would like to try some experimental software on a netbook. Can somebody recommend a netbook that can do FreeBSD. Late to the discussion, sorry I can't give positive advice, but: I can explicity UNADVISE the (ee?)pc 1005ha Networking (atheros 9285, iirc) might work under ndis, wired (I forget which chipset) doesn't work. I put ubuntu on it, and even _that_ took some hacks. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as -D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial line - at least not at speed/settings that the client is set up to receive. I'm gonna try 9600 bps soon just to be sure it isn't that, but seeing how many others have mentioned using -S115200 I doubt it'll help. Thanks/regards, Thomas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Punkbuster
Can anyone tell me how to update punkbuster ... seems pbweb.x86 doesn't work anymore (302 errors) and I'm unable to run pbsetup.run it gives me a float point error, even after unpacking it with upx -d Specifically for enemy territory. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Serial console trouble: loader and login works, but no kernel messages
Did you try booting with the keyboard disconnected from the FreeBSD machine? Perhaps the vidconsole is favored when a keyboard is detected? On a linux box I had, I would get serial output from Grub, lose it during kernel load and then get a login once the OS was up, much like what you describe. I had to add a kernel argument to my Grub config so the kernel would output to the serial port. Did you look here: http://www.freebsd.org/doc/en/articles/console-server/freebsd.html I think 7.2 might be what you are missing but I can't check it myself. On Sun, Aug 23, 2009 at 3:13 PM, Thomas Backmanseren...@exscape.org wrote: On Aug 23, 2009, at 20:25, Tim Judd wrote: On 8/23/09, Thomas Backman seren...@exscape.org wrote: First off: Not subscribed to this list, please make sure to Cc me if you don't reply directly. :) Anyway, I finally got my null modem cable, and plugged in in between a machine running 8.0-BETA2 and one running WinXP using Hyperterminal. My settings: /boot/loader.conf: boot_multicons=YES boot_serial=YES comconsole_speed=115200 console=comconsole,vidconsole /etc/ttys: # Serial terminals # The 'dialup' keyword identifies dialin lines to login, fingerd etc. ttyu0 /usr/libexec/getty std.115200 vt100 on secure /boot.config (which is read properly): -Dh -S115200 Anything wrong in the above? Hyperterminal is set to 115200 bps, 8 bits, no parity, 1 stop bit, and no flow control (if that's the correct translation to English). On the serial console, I go from the screen with the FreeBSD logo, with single-user options etc. (which works fine), and then nothing, until a login tty pops up (which also works fine). The main, if not only, reason I want a serial console is to be able to use it for single user mode, DDB, and so on. All kernel messages, and all rc messages are seen only on the graphics card; the serial console receives nothing but the /boot.config: - Dh ..., the logo screen, and then the login screen, during startup and *nothing* at all during shutdown. Also, I'm able to login and use the system both via the serial console and via the graphics card/ keyboard... Is this supposed to be? I'm not complaining, I just got the impression it was one or the other. Any advice on how to get the kernel/rc messages etc. to the serial console (only or as well)? Regards, Thomas Do you use the VGA/vidconsole at all? A serial-only device (think soekris, ALIX/WRAP boards) that has no VGA will have different requirements than a serial-only device will. Your loader.conf statements are different than mine in the definition that you have more than I do to enable serial. My loader.conf just has one statement: console=comconsole - to feed ALL bootloaders, kernel probing, rc startup on the serial device. /etc/ttys defines the login lines. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. Of course, you're on 8.0 and I don't run BETAs. So the 8.0 BETA might still be having com port oddities, plus I noticed your ttys line is ttyu0, not ttyd0. Did 8.0 change the serial line device? To enable a serial-only device in my setups: /boot/loader.conf: console=comconsole /boot.config: -D /etc/ttys: # enable serial line, cons25 or vt100, depending if I'm originating from a bsd or windows box. Enabling dual-setups should be just the loader.conf change to dual console. HTH (Sorry for the lack of inline replies.) I do have a graphics card, and ideally I'd like to be able to use both, but serial has higher priority (with serial access, I can use minicom on another *nix box and essentially ssh into DDB, and stuff like that - right now I have to borrow a monitor, and write info down manually if needed, turning my head back and forth). I've tried lots of combinations of console=, including simply 'console=comconsole' and/or combinations of that and -D, -h- -Dh and -P in /boot.config. The extra lines in loader.conf are from the handbook, which says they're needed to use comconsole_speed. It seems they do the same thing as -D and -h, though. Oh, and re: /etc/ttys: Yup, it's ttyuX when using uart(4) which seems to be the default now. Actually, since my last buildworld half an hour ago I'm on 9.0-CURRENT. ;) Also, I made sure to set flags to 0x10 for the serial port as per the handbook (although I did it using loader.conf, not the kernel config); before the change, dmesg didn't mention any flags, but it now does. Didn't help squat, though. Though trial and error, I found when you use a dual-setup: comconsole,vidconsole, the first one (comconsole) will get rc output, and vidconsole won't. This doesn't mirror my experience; comconsole and comconsole,vidconsole appears to be just the same for me. I've never gotten anything except the boot loader and a login prompt over to the serial line - at least not at
antivirus gateway
Hello I wish to use freebsd7.2 as an antivirus gateway. is there any document about that? Could you give an advice ? Thanks Bu elektronik posta ve varsa ekleri tamamen gizli ve gönderilen kişiler listesine özeldir. Eğer adınız gönderilen kişiler listesinde yer almıyorsa, lütfen derhal gönderen kişiyi bilgilendiriniz ve içeriğini herhangi başka bir kişiye iletmeyiniz, herhangi bir amaç için kullanmayınız, sayısal ve basılı ortamlar dahil olmak üzere saklamayınız ve kopyalamayınız. This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by reply e-mail and delete all copies of this message and attachments. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ezjail jail migration
Has anyone tried to migrate ezjail jails between 7.2 and 6.4? I've read it works fine 6.4 - 7.2, but what about 7.2 - 6.4. Is there any chance I could get away with this by not being forced to reinstall all the running stuff - proftpd, apache? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: What should be backed up?
On Sat, 22 Aug 2009 15:58:25 +0200,
Erik Norgaard norga...@locolomo.org said:
E Yes, it's easy to miss something that should have been backed up. There
E is no point in backup of files other than those you modify yourself,
E unless you plan to create an exact image and recover using dd.
Touching a timestamp file and backing up stuff newer than that works
fine for things you modify, but I frequently copy over source tarballs
and the timestamp method won't work for those. I use MD5 to find what
I've added, changed, or deleted:
root# mkdir /root/toc
root# cd /root/toc
root# date; find / -type f -print | xargs /sbin/md5 -r orig.md5; date
Tue Mar 24 20:55:20 EDT 2009
Tue Mar 24 20:58:50 EDT 2009
root# wc -l orig.md5
198760 orig.md5
root# df -m /
Filesystem1M-blocks Used Avail Capacity Mounted on
/dev/aacd0s1a 7931 1882 541426%/
root# grep -v /root/toc orig.md5 x
root# mv x orig.md5
This was from a 7.1 installation. The box hashed 199,000 files (1.8 Gb)
in just over 3 minutes, which was fine with me. Next, I back up /etc in
case I mangle something:
root# mkdir /etc.orig
root# cd /etc
root# find . -print | pax -rwd -pe /etc.orig
After all my tweaks are in place, user accounts installed, etc., I run
the script below to get a new table-of-contents. Then I can compare the
two MD5 files to see exactly what I've added, removed, or modified.
--
Karl Vogel I don't speak for the USAF or my company
Burned so much oil, it was single handedly responsible for the formation
of OPEC.
--a Chevy Vega owner, on Car Talk's 10 worst cars of the millennium
===
#!/bin/ksh
# Get a table of contents for a configured system.
PATH=/bin:/sbin:/usr/sbin:/usr/bin
export PATH
out=new.md5
top=/root/toc
# First time this is run, {/usr /home /var} are all under /.
# We want to check the same things when we do the comparison run.
fsys=/
root=`df $fsys`
for dir in /usr /home /var
do
x=`df $dir`
test $x != $root fsys=$fsys $dir
done
# Get the TOC.
cd $top || exit 1
date; find $fsys -xdev -type f -print0 | xargs -0 md5 -r $out; date
# How much space are we checking?
echo; df -m $fsys; echo
grep -v $top $out x.$$
mv x.$$ $out
wc -l $out
exit 0
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Translation
Dear Mr Nakhonekham, Just question about translated version of FreeBSD if it available in Lao Language or not? if not how can I start to translate this FreeBSD in to Lao. As far as I know, there is no Lao translation of FreeBSD. Now I know there is a Thai group of FreeBSD users, you may want to contact them. Best regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: RAID10 setup
You're on the right track, additional comments inline. On Saturday 22 August 2009 06:49:06 am Phil Lewis wrote: This question was asked a few weeks ago, but the original poster must have had their questions amswered. As follow-ups offered further assistance given more detail, I wonder if I could be so bold as to provide that detail for my own circumstances. I have six disks: ad4 - 500MB ad5 - 500MB ad6 - 500MB ad7 - 400MB ad8 - 500MB ad10 - 500MB These are SATA drives, with ad8 and ad10 on a PCIe SATA controller. ad7 was my first disk and currently contains FreeBSD7.2-RELEASE. I've been using that to gain some familiarity with FreeBSD, but it need not be preserved (in fact, I'd rather not preserve it!). When I built the machine, I just plugged the 400GB drive in any old slot, so it can move if that makes sense. When I got the new drives I tried to get identical to the 400GB drive, but couldn't. The 400GB drive currently has a single slice using the full drive. Just make sure you have the disk(s) you plan to boot from on a controller that will boot in your machine. If the controllers have different performance characteristics then you probably want to share the wealth of the better one between multiple mirrors. What I'd like to end up with is a three-way stripe across three two-way mirrors, containing as much of the system as possible. This is certainly do-able. If it were me I'd put the whole OS on the spare change partitions and leave the whole stripe for your serious data consumer(s): /home, /data, possibly /usr/local or some or all of /var, etc. Depends on your intended use of the storage naturally. I understand that you can't boot from a stripe, so some part of some disk will have to be outside the stripe. However, as the stripe will also be limited to the smallest disk, I'm going to have 5 x 100 GB bits left over anyway, so I guess /boot can go on one of these..? Absolutely. I'd make a gmirror of two or three of them and put / on it. If you really want to be minimal w/ your use of the extra space then you could do /boot as you propose. If possible, I'd like set this up pre-install. If it has to be done post-install, or is easier to describe how to do post-install, then that's fine. Either will work. Exactly how you do it depends on how much of the base system you want to end up on the stripe. From here on in, this email becomes speculative. All of the examples I've seen for setting up GEOM stripes and mirrors have used the raw disk as the base-level provider. On the other hand, I've seen nothing that says that the bottom level cannot be a slice, rather than a raw disk, and given the way GEOM works, I suspect this is true. Yes, you can use partitions, slices or any other GEOM providers as members of gstripe, gmirror and friends. My current plan, based on this assumption, is as follows: With my current FreeBSD installation, create 2 slices on each 500GB disk, 1 x ~400GB, 1 x ~100GB (the same size as the slice of my 400GB disk, and the rest of the disk). Boot from the FreeBSD 7.2-RELEASE dvd, and enter fixit mode. I'm not sure which would be best, or even if both are feasible for what I want to do. (I was at this point in my researchwhen I found this post!). From here, kldload geom_stripe and kldload geom_mirror. Then, create the three mirrors: gmirror label -v main0 /dev/ad4s1 /dev/ad5s1 gmirror label -v main1 /dev/ad6s1 /dev/ad571 gmirror label -v main2 /dev/ad8s1 /dev/ad10s1 This should give me /mirror/main0|main1|main2, right? Right. Next create the stripe: gstripe label -v -s 131072 raid10 /dev/mirror/main0 /dev/mirror/main1 /dev/mirror/main2 (that's all one line) If I'm right so far, then hopefully I should be able to boot to the install dvd again (or just rerun sysnstall?), and from there I should be able to choose a slice from outside 'raid10' to mount /boot, and use 'raid10' for everything else. Do I need anything else on a non-striped slice? /boot or equivalent is the only thing required to smell like a normal disk (which gmirror is capable of but gstripe isn't). You may want to use some of the space for swap. The virtual memory system should do its own version of stripe or interleave if you feed it multiple swap devices. Maybe I could even create another mirror: gmirror label -v boot /dev/ad4s2 /dev/ad5s2 and use that to mount /boot, leaving me with s2 on ad6,8 and 10 as 3 spare 100GB slices? Or am I just way off track? You seem to be pretty well on track. It seems you've already parsed the gstripe and gmirror man pages. You should probably look at fdisk(8) and bsdlabel(8) as well in case sysinstall doesn't tie up all your loose ends. Additionally you could just reinstall to a plain disk (or use your existing installation) and use dump/restore (and/or rsync) to move your filesystems to their multi-disk destinations. PS. I
Re: What should be backed up?
On Aug 23, 2009, at 7:14 PM, Karl Vogel wrote: Touching a timestamp file and backing up stuff newer than that works fine for things you modify, but I frequently copy over source tarballs and the timestamp method won't work for those. This is one of the several reasons that I use rsync (via rsnapshot). At each increment, it backs up the minimum that is need. With the cost of having a complete backup which duplicates what you would find in a reinstall, you have a complete system. Suppose you accidently trash something from the original installation. It may be easier to restore it from your backups than going to original installation media. Disk space is cheap, so having a complete back-up (under most circumstances) makes sense. With -- link-dest you can maintain many snapshots with the minimal of copying, transmitting, and writing files. Of course everyone's back up needs are different, and what works for me isn't necessarily the best for others. But if you haven't looked at rsnapshot, I'd recommend that you do before writing your own scripts. Even if you don't use rsnapshot itself, look at what it does with rsync. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
