Re: Disable CTRL-ALT-DEL
Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier There are two ways of doing this, both described in the FreeBSD FAQ here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
Manolis Kiagias wrote: Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier There are two ways of doing this, both described in the FreeBSD FAQ here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
Peter Boosten wrote: Manolis Kiagias wrote: Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier There are two ways of doing this, both described in the FreeBSD FAQ here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' Peter It seems you are right. Just checked on 6.3 and 7.0 and it does not exist. It does exist in 6.2, however. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
On Sat, Oct 18, 2008 at 10:58:29AM +0300, Manolis Kiagias wrote: Peter Boosten wrote: Manolis Kiagias wrote: Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier There are two ways of doing this, both described in the FreeBSD FAQ here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' Peter It seems you are right. Just checked on 6.3 and 7.0 and it does not exist. It does exist in 6.2, however. Hmm... # sysctl hw.syscons.kbd_reboot=0 hw.syscons.kbd_reboot: 1 - 0 # sysctl hw.syscons.kbd_reboot=1 hw.syscons.kbd_reboot: 0 - 1 # uname -a FreeBSD icarus.home.lan 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Oct 2 03:04:20 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PDSMI_PLUS_RELENG_7_amd64 amd64 -- | 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: Disable CTRL-ALT-DEL
On Sat 2008-10-18 09:47:51 UTC+0200, Peter Boosten ([EMAIL PROTECTED]) wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' That's odd.. $ sysctl hw.syscons.kbd_reboot hw.syscons.kbd_reboot: 1 $ uname -a FreeBSD blizzard.phoenix 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed Oct 1 05:34:19 UTC 2008 [EMAIL PROTECTED] daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
andrew clarke wrote: On Sat 2008-10-18 09:47:51 UTC+0200, Peter Boosten ([EMAIL PROTECTED]) wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' That's odd.. $ sysctl hw.syscons.kbd_reboot hw.syscons.kbd_reboot: 1 $ uname -a FreeBSD blizzard.phoenix 6.3-RELEASE-p5 FreeBSD 6.3-RELEASE-p5 #0: Wed Oct 1 05:34:19 UTC 2008 [EMAIL PROTECTED] daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] What about this: [EMAIL PROTECTED]:~]$ uname -a FreeBSD atlantis.dyndns.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #10: Fri Oct 17 18:31:22 EEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ATLANTIS i386 [EMAIL PROTECTED]:~]$ sysctl -a |grep syscons hw.syscons.kbd_debug: 1 hw.syscons.bell: 1 hw.syscons.saver.keybonly: 1 hw.syscons.sc_no_suspend_vtswitch: 0 [EMAIL PROTECTED]:~]$ (Actual sources are not yesterdays, I just rebuilt the kernel yesterday) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
Jeremy Chadwick wrote: On Sat, Oct 18, 2008 at 10:58:29AM +0300, Manolis Kiagias wrote: Peter Boosten wrote: Manolis Kiagias wrote: Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Best regards, Olivier There are two ways of doing this, both described in the FreeBSD FAQ here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#CAD-REBOOT Hmmm, didn't know about the second one, and doesn't seem to be working either (on both 7.0 and 6.3): sysctl hw.syscons.kbd_reboot=0 sysctl: unknown oid 'hw.syscons.kbd_reboot' Peter It seems you are right. Just checked on 6.3 and 7.0 and it does not exist. It does exist in 6.2, however. Hmm... # sysctl hw.syscons.kbd_reboot=0 hw.syscons.kbd_reboot: 1 - 0 # sysctl hw.syscons.kbd_reboot=1 hw.syscons.kbd_reboot: 0 - 1 # uname -a FreeBSD icarus.home.lan 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Oct 2 03:04:20 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PDSMI_PLUS_RELENG_7_amd64 amd64 Mystery solved. The sysctl only exists if you have not already compiled the kernel with options SC_DISABLE_REBOOT I just checked, and all the systems that do not show this were compiled with SC_DISABLE_REBOOT I installed a clean (vmware) 7.0 and hw.syscons.kbd_reboot exists. ___ 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 ?
Frank Bonnet schrieb: 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 ) In the dark ages of FreeBSD 5.x ;) we've used Linux (Debian, RedHat) but nowadays I would certainly prefer FreeBSD again, because: - The software in the ports is close to what comes from upstream, Linux-Distros often keep old versions or inhouse modifications which can lead to disasters like e.g. the Debian OpenSSL bug or unuseable LDAP-servers that are delivered with RedHat. - Linux-Distros are conservative in updating software versions or fixing bugs in their so called stable releases. In most cases (RedHat, Debian) the fixes are backported to older versions, in other cases (Ubuntu) fixes may break your system or bugs are simply ignored. If you need a newer version of a certain software, you will very soon find yourself using backports from foreign repositories or start rolling your own packages. But if you have to leave the package management system of your distro anyway, why not use the comfort of FreeBSD ports? - Once you are familiar with it, FreeBSD is easier to manage IMHO, it's clean and mostly well documented. - FreeBSD has jails. :) More seriously I'm also searching for eventuals benchmarks that compare those two configurations. I don't think that there are great performance differences nowadays. bye, Uwe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
mounting an MP3 player?
Hello, can anyone tell me how to mount an MP3 player (usb)? I seem to be too stupid to figure it out by myself. I thought it would be as easy as mounting a usb memory stick which I can mount with a device file of the form /dev/da#s#, e. g. /dev/da0s1, which is present after connecting the memory stick, but not if connecting the player instead; in this case I've got only /dev/da1 to /dev/da4. I tried all these and also /dev/usb, /dev/usb1, ..., /dev/usb4, but that doesn't work (as I expected but tried nevertheless). If I connect the player to the usb bus I get the following in /var/log/messages: | kernel: umass1: TrekStor TrekStor, rev 2.00/1.00, addr 2 and from usblist: | Generic USB SD Reader 1.00 at scbus1 target 0 lun 0 (da1,pass0) | Generic USB CF Reader 1.01 at scbus1 target 0 lun 1 (da2,pass1) | Generic USB SM Reader 1.02 at scbus1 target 0 lun 2 (da3,pass2) | Generic USB MS Reader 1.03 at scbus1 target 0 lun 3 (da4,pass3) and from usbdevs: | Controller /dev/usb4: | addr 1: high speed, self powered, config 1, EHCI root hub(0x), Intel(0x), rev 1.00 | port 1 powered | port 2 powered | port 3 powered | port 4 powered | port 5 powered | port 6 addr 2: high speed, power 400 mA, config 1, TrekStor(0x2791), TrekStor(0x071b), rev 1.00 | port 7 powered | port 8 powered Which device file should I use (or create?) to get access to this MP3 player? (I'm using FreeBSD 6.0) Thanks Johannes-Maria ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
Olivier Nicole wrote: Hi, On FreeBSD 6.3 how to disable the CTRL-ALT-DEL from halting/rebooting the system? Compile your own kernel with this option: # Disable CTRL-ALT-DEL options SC_DISABLE_REBOOT Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
gconcat question
Dear mailing list, What are the steps to bring back gconcatenated disks if doing an upgrade from FreeBSD6 to FreeBSD7 like this? As-is situation: FreeBSD 6.2-STABLE ad0 has FreeBSD ad1, ad2 and ad3 are gconcatenated using 'gconcat label -v data /dev/ad1 /dev/ad2 /dev/ad3'. Planned upgrade: Reboot from cdrom, install FreeBSD7 from cd to ad0 /Roger ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Using mirroring to replace drive?
Hi, For years I've been upgrading by building a temp server, transferring a production function to it and temporarily decommissioning the one server while I upgrade and rebuild it. I was thinking of trying a different approach since having tried out gvinum in the last couple of years. The current scenario is that I have a machine where the adaptec controller is suggesting I replace a failing SCSI drive which happens to be the system disk. I purchased a couple of new drives and thought I might just plug it in and mirror the failing drive on the new drive. Then pull the failing drive and plug in the other new drive as the second mirrored drive and be done with it. One obvious outcome would be a having a system drive mirror for future such issues. I have never built a mirror on the fly but it seems many have from what I've read and the cookbooks out there make it sound very easy. I was going to use GEOM Mirror on 6.2 (then upgrade to 7.0 after establishing the new good drives). 1. Is this an appropriate way to deal with this? 2. Are there any high risk aspects of doing this while running a server in production? I'm thinking of things like how probable it is of trashing the original disk, making the system unbootable in the process etc? 3. Are there better approaches that are safer (aside from my normal hardware swap MO). 4. Does using GEOM Mirror RAID-1 make the upgrade from 6.2 to 7.0 a dangerous proposition. I do upgrades via cvsup and buildworld. The environment is FreeBSD 6.2 Supermicro with Adaptec SCSI All ~73 GB Maxtor and Seagate drives Current da0 system is Maxtor, there will be minor size differences, the replacement Cheetah is a hair larger. Apache, PHP5 and Mysql No existing RAID Configuration ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
disable ipv6 lookups
I'd like to disable ipv6 () lookups entirely since I'm not using ipv6 at all. I tried taking INET6 out of my kernel but i still see lookups being made. I stumbled accross some references in old resolv.conf manpages (it's not in there anymore) about where you can enable inet6 but not on how you can disable them at all. Why are lookups default anyway? I mean hardly anybody is unsing ipv6 other than some geeks over tunnels. I'd love to use it when i can get it w/o tunnel but i'd say 99% of all users out there waste cpu cycles on making lookups even though they don't have ipv6 suport. Sorry if this sounds kinda whiny, I am seriously wondering about this. Sandra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Disable kontact/kmail automatic activation
Hello all, I am running FreeBSD 7.1-PRERELEASE #2 with KDE: 3.5.10. A few *PORTUPGRADEs* ago , I can't recall when, I noticed that when KDE is started, usually after system startup , kontact application is started automatcally, which I 'd like to disable. Kde is started from /etc/ttys, and I have no automatic activation for any apps from $HOME/.kde/Autostart. I 'd like to be able to call kmail at my own will. Can you please tell how can I disable kontact automatic activation? thanx, -- Benzi Mizrahi, computing center, Weizmann Institute of Science, Tel: 972-8-9342456 Rehovot, Israel.Fax: 972-8-9344102 Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? FreeBSD: Are you guys coming or what? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mounting an MP3 player?
On Sat, Oct 18, 2008 at 11:32:37AM +0200, Johannes-Maria Kaltenbach wrote: Hello, can anyone tell me how to mount an MP3 player (usb)? I seem to be too stupid to figure it out by myself. I thought it would be as easy as mounting a usb memory stick which I can mount with a device file of the form /dev/da#s#, e. g. /dev/da0s1, which is present after connecting the memory stick, but not if connecting the player instead; in this case I've got only /dev/da1 to /dev/da4. I tried all these and also /dev/usb, /dev/usb1, ..., /dev/usb4, but that doesn't work (as I expected but tried nevertheless). If I connect the player to the usb bus I get the following in /var/log/messages: | kernel: umass1: TrekStor TrekStor, rev 2.00/1.00, addr 2 It should say more after that. Can you post it? and from usblist: | Generic USB SD Reader 1.00 at scbus1 target 0 lun 0 (da1,pass0) | Generic USB CF Reader 1.01 at scbus1 target 0 lun 1 (da2,pass1) | Generic USB SM Reader 1.02 at scbus1 target 0 lun 2 (da3,pass2) | Generic USB MS Reader 1.03 at scbus1 target 0 lun 3 (da4,pass3) It looks like your player has a number of areas of storage e:g SD card, flash card, it's own internal memory etc. and they all have an associated device node: $ ls /dev | grep da You can manipulate these devices with camcontrol(8) E.g: # camcontrol stop 1:0:0 # camcontrol rescan 1:0:0 # camcontrol load 1:0:0 should initialise /dev/da0 (the SD card?) Then: # mount -t msdosfs /dev/da0 /mnt/dos will mount it you can read/write files from it. When you're finished: # umount /mnt/dos # camcontrol eject 1:0:0 If you have problems, post back the signifigant parts of /var/log/messages and any other errors. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disable CTRL-ALT-DEL
--- On Sat, 10/18/08, Jeremy Chadwick [EMAIL PROTECTED] wrote: From: Jeremy Chadwick [EMAIL PROTECTED] Subject: Re: Disable CTRL-ALT-DEL To: Manolis Kiagias [EMAIL PROTECTED] Cc: Olivier Nicole [EMAIL PROTECTED], freebsd-questions@freebsd.org, Peter Boosten [EMAIL PROTECTED] Date: Saturday, October 18, 2008, 4:10 AM It seems you are right. Just checked on 6.3 and 7.0 and it does not exist. It does exist in 6.2, however. Hmm... # sysctl hw.syscons.kbd_reboot=0 hw.syscons.kbd_reboot: 1 - 0 # sysctl hw.syscons.kbd_reboot=1 hw.syscons.kbd_reboot: 0 - 1 # uname -a FreeBSD icarus.home.lan 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Thu Oct 2 03:04:20 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PDSMI_PLUS_RELENG_7_amd64 amd64 It's definitly there in RELENG_7 as of this moment (just cvsup'd): /usr/src/sys/dev/syscons/syscons.c:SYSCTL_INT(_hw_syscons, OID_AUTO, kbd_reboot, CTLFLAG_RW|CTLFLAG_SECURE, enable_reboot, - 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]
error installing kmymoney2 on amd64 system running freebsd 6.3
Hi freebsd peeps, Who can help me sort this error out when I try to installl kmymoney2 on my amd64 system. The error I get is: test ! -f sk.gmo || touch sk.gmo rm -f es_AR.gmo; /usr/local/bin/msgfmt -o es_AR.gmo ./es_AR.po test ! -f es_AR.gmo || touch es_AR.gmo rm -f pt_BR.gmo; /usr/local/bin/msgfmt -o pt_BR.gmo ./pt_BR.po test ! -f pt_BR.gmo || touch pt_BR.gmo rm -f es.gmo; /usr/local/bin/msgfmt -o es.gmo ./es.po test ! -f es.gmo || touch es.gmo rm -f fr.gmo; /usr/local/bin/msgfmt -o fr.gmo ./fr.po test ! -f fr.gmo || touch fr.gmo rm -f nl.gmo; /usr/local/bin/msgfmt -o nl.gmo ./nl.po test ! -f nl.gmo || touch nl.gmo rm -f pt.gmo; /usr/local/bin/msgfmt -o pt.gmo ./pt.po test ! -f pt.gmo || touch pt.gmo rm -f en_GB.gmo; /usr/local/bin/msgfmt -o en_GB.gmo ./en_GB.po test ! -f en_GB.gmo || touch en_GB.gmo rm -f ca.gmo; /usr/local/bin/msgfmt -o ca.gmo ./ca.po test ! -f ca.gmo || touch ca.gmo rm -f gl.gmo; /usr/local/bin/msgfmt -o gl.gmo ./gl.po test ! -f gl.gmo || touch gl.gmo rm -f ru.gmo; /usr/local/bin/msgfmt -o ru.gmo ./ru.po test ! -f ru.gmo || touch ru.gmo rm -f zh_CN.gmo; /usr/local/bin/msgfmt -o zh_CN.gmo ./zh_CN.po test ! -f zh_CN.gmo || touch zh_CN.gmo gmake[2]: Leaving directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/po' Making all in doc gmake[2]: Entering directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc' Making all in en gmake[3]: Entering directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc/en' if test -n /usr/local/bin/meinproc; then echo /usr/local/bin/meinproc --check --cache index.cache.bz2 --stylesheet /usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl ./index.docbook; /usr/local/bin/meinproc --check --cache index.cache.bz2 --stylesheet /usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl ./index.docbook; fi /usr/local/bin/meinproc --check --cache index.cache.bz2 --stylesheet /usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl ./index.docbook gzip -9 -c -N ../../doc/en/kmymoney2.1 kmymoney2.1.gz make get-files make: don't know how to make w. Stop gmake[3]: *** [index.docbook.tex] Error 2 gmake[3]: Leaving directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc/en' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9' gmake: *** [all] Error 2 *** Error code 2 Stop in /usr/ports/finance/kmymoney2. uname -a FreeBSD amd_desktop.telfort.nl 6.3-RELEASE-p4 FreeBSD 6.3-RELEASE-p4 #21: Wed Oct 1 08:07:27 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL amd64 What's wrong? Brgds Dino __ 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]
fsdb yields GEN=ffffffffb5f6de87
I was running a java make job and did a du last week and suddenly brought my frankenstein ASUS M6800N Notebook to a frozen mouse state. That was running from a FreeBSD 7.0 on a 160GB HD. I was looking at this question: http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016043.html and I have been given the same advice that I am just not ready to acquiesce to (I know I am not much of a sysadmin until I do, though), i.e. retrieve data and reinstall the operating system. I have results of fsdb of my own: http://www.monkeyview.net/id/965/fsck/inodes/pa180020.vhtml but I don't have quite the same absurdity, i.e. a file that has more bits than atoms in the universe (well.. that's a BIT of an exaggeration) I am thinking, though that the fact that GEN=b5f6de87 might be an absurd value. Is that the case? I found multiple inodes with this configuration. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
pfSense
Guys, I've been using the FBSD firewall pfSense since last January without fully understanding it. Now I'm getting some clues as to one *possibility* why my new laptop may not be working. --It is more probably a hardware fauly, but maybe somebody can clue me in How both my wife and my daughter and I (with my new ThinkPad G41) were given IP's _within_ the Range that was set up. My private IP's are listed as 10.47.0.0 -- 10.47.0.255 and my Range is listed as 10.47.0.101 to 10.47.0.120. The Range is described on one site: You will need to set the Range of the DHCP server which will regulate how many IP addresses you will give out. My wife's Dell XP has 10.47.0.119; daughter's Macbook is 10.47.0.115; and when I clicked around and made my daughter's computer IP static, pfSense gave me an error. It said that it was incorrectly within the Range. How can I change/edit it so that it is outside the range? I would like everything possible to be set in concrete. Will pfSense pick an IP outside the range? tia, 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]
Re: pfSense
Gary Kline [EMAIL PROTECTED] wrote: [pfSense question removed] Please ask your question on the pfSense mailing list or forum. Thanks. http://www.pfsense.org/index.php?option=com_contenttask=viewid=66Itemid=71 http://forum.pfsense.org/ -- Sahil Tandon [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: pfSense
On Sat, Oct 18, 2008 at 02:44:57PM -0700, Gary Kline wrote: I've been using the FBSD firewall pfSense since last January without fully understanding it. Now I'm getting some clues as to one *possibility* why my new laptop may not be working. --It is more probably a hardware fauly, but maybe somebody can clue me in How both my wife and my daughter and I (with my new ThinkPad G41) were given IP's _within_ the Range that was set up. My private IP's are listed as 10.47.0.0 -- 10.47.0.255 and my Range is listed as 10.47.0.101 to 10.47.0.120. The Range is described on one site: You will need to set the Range of the DHCP server which will regulate how many IP addresses you will give out. My wife's Dell XP has 10.47.0.119; daughter's Macbook is 10.47.0.115; and when I clicked around and made my daughter's computer IP static, pfSense gave me an error. It said that it was incorrectly within the Range. How can I change/edit it so that it is outside the range? I would like everything possible to be set in concrete. Will pfSense pick an IP outside the range? You should ask this on the pfSense mailing list, but, I will answer your question regardless -- but I make the assumption the DHCP server used in pfSense is ISC dhcpd. You *cannot* include static IPs (in this case, static IP means an IP address that is always returned for a specific MAC address) within the dynamic pool. ISC dhcpd will not let you do this, and for good reasons (you can read the docs if you want the answer). Instead, you should give your wire and daughter's machines IPs outside of the dynamic pool range, e.g. 10.47.0.121 and upwards. This will work fine. -- | 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]
The FreeBSD Diary: 2008-09-28 - 2008-10-18
The FreeBSD Diary contains a large number of practical examples and how-to guides. This message is posted weekly to freebsd-questions@freebsd.org with the aim of letting people know what's available on the website. Before you post a question here it might be a good idea to first search the mailing list archives http://www.freebsd.org/search/search.html#mailinglists and/or The FreeBSD Diary http://www.freebsddiary.org/. These are the articles posted during this period: 5-Oct : Removing dead mailing lists from Mailman Mailing lists can outlive their usefulness http://freebsddiary.org/mailman-removing-dead-lists.php?2 -- Dan Langille BSDCan - http://www.BSDCan.org/ - BSD Conference ___ 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 21:46:53 -0700 Gary Kline [EMAIL PROTECTED] wrote: On Friday 17 October 2008 16:26:54 RW wrote: 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. KDM defaults to the previous desktop whatever it is, whether it's kde3 kde4, gnome, fluxbox or whatever, it's completely agnostic. You can remove kde3 if you want to. Personally I hope KDE3 stays for as long as possible since it's by far my favourite desktop, and KDE4 one of my least favourite. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gconcat question
On Saturday 18 October 2008, Roger Olofsson wrote: What are the steps to bring back gconcatenated disks if doing an upgrade from FreeBSD6 to FreeBSD7 like this? As-is situation: FreeBSD 6.2-STABLE ad0 has FreeBSD ad1, ad2 and ad3 are gconcatenated using 'gconcat label -v data /dev/ad1 /dev/ad2 /dev/ad3'. The concat device should just appear automatically after the upgrade as long as you (continue to) load the geom_concat kernel module. Be aware that if the on-disk metadata format has changed then it will automatically be upgraded. This is usually a good thing but if you need to roll back to 6.x for some reason it's something to take into consideration. Planned upgrade: Reboot from cdrom, install FreeBSD7 from cd to ad0 Just curious, is there a reason you're going this route instead of upgrading from source? JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using mirroring to replace drive?
On Saturday 18 October 2008, Chris Pratt wrote: Hi, For years I've been upgrading by building a temp server, transferring a production function to it and temporarily decommissioning the one server while I upgrade and rebuild it. I was thinking of trying a different approach since having tried out gvinum in the last couple of years. The current scenario is that I have a machine where the adaptec controller is suggesting I replace a failing SCSI drive which happens to be the system disk. I purchased a couple of new drives and thought I might just plug it in and mirror the failing drive on the new drive. Then pull the failing drive and plug in the other new drive as the second mirrored drive and be done with it. One obvious outcome would be a having a system drive mirror for future such issues. I have never built a mirror on the fly but it seems many have from what I've read and the cookbooks out there make it sound very easy. I was going to use GEOM Mirror on 6.2 (then upgrade to 7.0 after establishing the new good drives). 1. Is this an appropriate way to deal with this? It could be. However if the new disks are not the same size as the failing disk (or perhaps even if they are) I would recommend using dump/restore to do the transfer rather than including the failing drive in the mirror. Assuming you can only have 2 disks attached at any given time and want to mirror at the disk level (as opposed to partition or slice), the sequence would be something like this: Connect new disk. Gmirror label ... (create a single-member (broken) mirror on the new disk) Partition (fdisk) and label (bsdlabel) the new mirror device, installing boot blocks as appropriate (fdisk -B and bsdlabel -wB, for example) Newfs and mount (to a temporary location) each filesystem on the mirror. Dump the contents of each filesystem from the original disk to the mirror device. Use the -L flag to dump to dump from a snapshot for live filesystems. Edit temproot/etc/fstab and change the relevant mountpoint entries to refer to the ones on the mirror. Ensure that temproot/boot/loader.conf contains 'geom_mirror_load=YES'. Shut down, remove the old disk and connect the second new disk. Boot (from the first new disk). If this doesn't succeed switch back to the old disk and figure out why. Gmirror insert ... (add the second disk to the mirror) Wait for rebuild to complete Finished! 2. Are there any high risk aspects of doing this while running a server in production? I'm thinking of things like how probable it is of trashing the original disk, making the system unbootable in the process etc? Like other GEOM classes gmirror stores its metadata in the last sector of the provider (the disk, in this case). If you decide to include the old disk in a mirror there is a chance that this sector will have been in use by the filesystem, though in the whole-disk scenario this is somewhat rare. Using the approach I outlined above avoids the possibility altogether. Other risks are minimal. The system will be I/O loaded during the dump/restore and mirror resync phases, though decent hardware can make this less obvious. If you manage to tickle a UFS snapshot bug during the dump the system could panic, though in my experience (on lightly-loaded systems without other snapshots and not using quotas) this has not happened. Having a fallback plan (revert to the unmodified original disk) is another selling point of the method I outlined above. 3. Are there better approaches that are safer (aside from my normal hardware swap MO). See my response to 1). 4. Does using GEOM Mirror RAID-1 make the upgrade from 6.2 to 7.0 a dangerous proposition. I do upgrades via cvsup and buildworld. Not really. The gmirror module in 7.x will read and understand (and possibly update) the on-disk metadata as soon as it sees it. Just be sure to load it. Worst case you end up booting from a single drive and have to manually specify your root partition. The environment is FreeBSD 6.2 Supermicro with Adaptec SCSI All ~73 GB Maxtor and Seagate drives Current da0 system is Maxtor, there will be minor size differences, the replacement Cheetah is a hair larger. Apache, PHP5 and Mysql No existing RAID Configuration JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error installing kmymoney2 on amd64 system running freebsd 6.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dino Vliet wrote:
Hi freebsd peeps,
Who can help me sort this error out when I try to installl kmymoney2 on my
amd64 system. The error I get is:
test ! -f sk.gmo || touch sk.gmo
rm -f es_AR.gmo; /usr/local/bin/msgfmt -o es_AR.gmo ./es_AR.po
test ! -f es_AR.gmo || touch es_AR.gmo
rm -f pt_BR.gmo; /usr/local/bin/msgfmt -o pt_BR.gmo ./pt_BR.po
test ! -f pt_BR.gmo || touch pt_BR.gmo
rm -f es.gmo; /usr/local/bin/msgfmt -o es.gmo ./es.po
test ! -f es.gmo || touch es.gmo
rm -f fr.gmo; /usr/local/bin/msgfmt -o fr.gmo ./fr.po
test ! -f fr.gmo || touch fr.gmo
rm -f nl.gmo; /usr/local/bin/msgfmt -o nl.gmo ./nl.po
test ! -f nl.gmo || touch nl.gmo
rm -f pt.gmo; /usr/local/bin/msgfmt -o pt.gmo ./pt.po
test ! -f pt.gmo || touch pt.gmo
rm -f en_GB.gmo; /usr/local/bin/msgfmt -o en_GB.gmo ./en_GB.po
test ! -f en_GB.gmo || touch en_GB.gmo
rm -f ca.gmo; /usr/local/bin/msgfmt -o ca.gmo ./ca.po
test ! -f ca.gmo || touch ca.gmo
rm -f gl.gmo; /usr/local/bin/msgfmt -o gl.gmo ./gl.po
test ! -f gl.gmo || touch gl.gmo
rm -f ru.gmo; /usr/local/bin/msgfmt -o ru.gmo ./ru.po
test ! -f ru.gmo || touch ru.gmo
rm -f zh_CN.gmo; /usr/local/bin/msgfmt -o zh_CN.gmo ./zh_CN.po
test ! -f zh_CN.gmo || touch zh_CN.gmo
gmake[2]: Leaving directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/po'
Making all in doc
gmake[2]: Entering directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc'
Making all in en
gmake[3]: Entering directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc/en'
if test -n /usr/local/bin/meinproc; then echo /usr/local/bin/meinproc
--check --cache index.cache.bz2 --stylesheet
/usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl
./index.docbook; /usr/local/bin/meinproc --check --cache index.cache.bz2
--stylesheet /usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl
./index.docbook; fi
/usr/local/bin/meinproc --check --cache index.cache.bz2 --stylesheet
/usr/local/share/apps/ksgmltools2/customization/kde-chunk.xsl ./index.docbook
gzip -9 -c -N ../../doc/en/kmymoney2.1 kmymoney2.1.gz
make get-files
make: don't know how to make w. Stop
gmake[3]: *** [index.docbook.tex] Error 2
gmake[3]: Leaving directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc/en'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory
`/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9'
gmake: *** [all] Error 2
*** Error code 2
Stop in /usr/ports/finance/kmymoney2.
uname -a
FreeBSD amd_desktop.telfort.nl 6.3-RELEASE-p4 FreeBSD 6.3-RELEASE-p4 #21: Wed
Oct 1 08:07:27 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERNEL
amd64
What's wrong?
Brgds
Dino
Hi Dino,
I committed the recent update for kmymoney2 0.8.9. I didn't come across
this problem, but maybe I can help you solve it.
Please send me a copy of
/usr/ports/finance/kmymoney2/work/kmymoney2-0.8.9/doc/en/Makefile so I
can have a look at it. Also, please send me the output of pkg_info |
awk '{ print $1 }'.
Regards,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFI+pe70sRouByUApARAtdqAKDHmGhRTmOB0+CzEfFx2J/d6NUsIACdEu7t
/dWSqqoWdIrZt7a8XWskcH8=
=ucn0
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Using mirroring to replace drive?
On Oct 18, 2008, at 7:03 PM, John Nielsen wrote: On Saturday 18 October 2008, Chris Pratt wrote: 1. Is this an appropriate way to deal with this? It could be. However if the new disks are not the same size as the failing ... it. Worst case you end up booting from a single drive and have to manually specify your root partition. JN Wow, I was asking a concept question and got what appears to be a comprehensive plan. I appreciate the effort, it will save me quite a bit of time. Thanks very much, Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Inode numbering
Hi! Because I didn't find sufficient informations and try and error would be incomplete (and insecure regarding the result), I'd like to ask the following question: Let's assume we have a directory D with an inode number i(D). It contains a file F with its inode number i(F). May I state that i(D) i(F)? I need to ask this in order to solve my data loss problem: I will need to write a inode recovery program (having iintensive looks at fsck_ffs' and fsdb's source code) to iterate over all the inodes. Maybe this additional question can be answered: Is there a mechanism that output inode numbers according to a certain algorithm, or is it random? If I would try to check every imaginable inode nummer according to the states connected, not connected - orphan or not connec- ted - not used, could I iterate from 1 to the maximum of the type ino_t, which is __uint32_t? My idea is to trace back orphaned inodes by brute force because fsck_ffs doesn't do the job, but similar to fsck_ffs, they will be reconnected to the directory they originally have been gnereated in, or in a kind of lost+found directory when the information from the respective superstructure (e. g. file names) are lost. I may assume that at least the inode of my former home directory has gone away, so if everything else is still there (I have some evidences from fsdb to assume this), after reconnecting everything should be accessible. Only the file names from the first hierarchy level (the files and subdirs directly within the home directory) would change into #123456 as you know it from fsck_ffs' lost+found, but the content inside the subdirs should still be present with the original filenames - assumed that the corresonding inode information structures are still complete. Thanks for comments! And please tell me if there's already a tool that does this! :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
KDE4 general q....
One thing I just confirmed is that the kttsd is missing. Anybody know about this? say, is it missing but just not loaded? It may be time to go back to kde3 for some more months. Feedback, please. tia, 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]
Re: Inode numbering
Polytropon [EMAIL PROTECTED] wrote: Let's assume we have a directory D with an inode number i(D). It contains a file F with its inode number i(F). May I state that i(D) i(F)? In general, no. It might work in the special case where nothing on the filesystem is ever moved or removed, and no hard links are ever added. As a simple example, suppose I have directories foo and foo/bar, and file foo/baz, with i(foo) == 15, i(foo/baz) == 20, and i(foo/bar) == 25, satisfying your criterion. If I do mv foo/baz foo/bar (so baz is now foo/bar/baz), I will have i(foo/bar) == 25 and i(foo/bar/baz) == 20. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
