Re: Is freebsd-update braindamaged, or I'm using it wrong?
On 01/10/2013 10:16, Ivan Voras wrote: > This is the first time I've used freebsd-update in years, and I'm > immediately flagging it as something I won't use in the future. For > the last half hour it has been forcing me to manually resolve, one by > one, in an editor, hundreds of "merge conflicts" such as these: > > 1 <<< current version > 2 # $FreeBSD: release/9.0.0/etc/gettytab 209954 2010-07-12 19:09:18Z bcr $ > 3 === > 4 # $FreeBSD: release/9.2.0/etc/gettytab 243623 2012-11-27 19:23:54Z peterj > $ > 5 >>> 9.2-RELEASE > 6 # from: @(#)gettytab 5.14 (Berkeley) 3/27/91 > 7 # > > This is fairly ridiculous. Then, at a random file it has proposed its > own merge and asked the prompt "Does this look reasonable?". It was > not, but when I answered it with "n" it stopped the whole process > (instead of maybe opening the file in the editor for me to merge > again). > > I've since retried the process and it behaves the same, and then tried > it on another system and again - the same type of manual merges and > the same exit from the process when answering "n" to a botched merge. > > In both cases, I'm upgrading from either 9.0-RELEASE or 9.1-RELEASE to > 9.2-RELEASE and the command line was "freebsd-update upgrade -r > 9.2-RELEASE". > > Am I doing something wrong, or is freebsd-update simply quirky and not > that useful? It is a little quirky, you arent the first to note this. For example http://freebsd.1045724.n5.nabble.com/Should-I-be-able-to-use-mergemaster-with-freebsd-update-td5822457.html "not that useful?" is subjective, some machines I've used it on happily, I'm more likely to build and use mergemaster though. Vince > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: booting FreeBSD on Apple Mac mini with GPT disk partition
On 03/09/2013 21:29, Kim Shrier wrote: > Does anyone know if work on booting FreeBSD on modern Apple hardware > was ever completed? I have looked on the wiki, forums, and email archives > but I don't see anything definitive. > > I would like to have a GPT partitioned disk with a freebsd-boot, freebsd-swap, > and multiple freebsd-ufs partitions on a new Mac mini. Any pointers would be > appreciated. I believe efi boot is almost done https://wiki.freebsd.org/UEFI I haven't tested yet although I may sometime soon as it would be nice to have my macbook dual boot without having to use bootcamp. Vince > > Thanks, > Kim > -- > Kim Shrier - k...@westryn.net > Shrier and Deihl, Westryn Internet Services > Internet Software Development and Hosting > Remote Unix Admin, Security > http://www.westryn.net/ > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Kernel dumps [was Re: possible changes from Panzura]
On 10/07/2013 23:09, Kevin Day wrote: >> >> Those sound useful. Just out of curiosity, however, since we're on the >> topic of kernel dumps: Has anyone even looked into the notion of an >> emergency fall-back network stack to enable remote kernel panic (or system >> hang) debugging, the way OS X lets you do? I can't tell you the number of >> times I've NMI'd a Mac and connected to it remotely in a scenario where >> everything was totally wedged and just a couple of minutes in kgdb (or now >> lldb) quickly showed that everything was waiting on a specific lock and the >> problem became manifestly clear. >> >> The feature also lets you scrape a panic'd machine with automation, running >> some kgdb scripts against it to glean useful information for later analysis >> vs having to have someone schlep the dump image manually to triage. It's >> going to be damn hard to live without this now, and if someone else isn't >> working on it, that's good to know too! > > At a previous employer, we had a system where on a panic it had a totally > separate stack capable of just IP/UDP/TFTP and would save its core via TFTP > to a server. This isn’t as nice as full remote debugging, but it was a whole > lot easier to develop. The caveats I remember were: > > 1) We didn’t want to implement ARP, so you had to write the mac address of > the “dump server” to the kernel via sysctl before crashing. > 2) We also didn’t want to have to deal with routing tables, so you had to > manually specify what interface to blast packets out to, also via sysctl. > 3) After a panic we didn’t want to rely on interrupt processing working, so > it polled the network interface and blocked whenever it needed to. Since this > was an embedded system, it wasn’t too big of a deal - only one network driver > had to be hacked to support this. Basically a flag that would switch to > “disable normal processing, switch to polled fifos for input and output” > until reboot. > 4) The whole system used only preallocated buffers and its own stack (carved > out from memory on boot) so even if the kernel’s malloc was trashed, we could > still dump. > > I’m not sure this really would scratch your itch, but I believe this took me > no more than a day or two to implement. Parts #1 and #2 would be pretty easy, > but I’m not sure how generic the kernel could support an emergency network > mode that doesn’t require interrupts for every network card out there. Maybe > that isn’t as important to you as it was to us. > > The whole exercise is much easier if you don’t use TFTP but a custom protocol > that doesn’t require the crashing system to receive any packets, if it can > just blast away at some random host oblivious if it’s working or not, it’s a > lot less code to write. > There was some work on something similar at one point, not sure what came of it. http://lists.freebsd.org/pipermail/freebsd-current/2010-September/020164.html Vince > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: bsnmp jail MIBS
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24/03/2013 20:36, Nicolas de Bari Embriz Garcia Rojas wrote: > Hi all, any idea of how to properly configure the bsnmp-jails MIBS so that I > bsnmpd can properly resolve > > I would like to use enterprises.fokus.begemot.jails instead of .1.3.6.1.4.1.12325.1. > > I am using bsnmpd under FreeBSD 9.1, I copied the JAILS-MIB.txt to :/usr/share/snmp/mibs > > but not working, snmptranslate .1.3.6.1.4.1.12325.1. returns this: > > SNMPv2-SMI::enterprises.12325.1. > > any ideas ? As far as I know snmptranslate looks for its mibs in /usr/local/share/snmp/mibs/ as its part of net-snmp having it there works for me [root@banshee /usr/local/share/snmp/mibs]# snmptranslate -m all .1.3.6.1.4.1.12325.1. BEGEMOT-MIB::begemot. [root@banshee /usr/local/share/snmp/mibs]# ls -la JAIL-MIB.txt - -rw-r--r-- 1 root wheel 2548 Mar 24 21:07 JAIL-MIB.txt [root@banshee /usr/local/share/snmp/mibs]# hope thats helpful. Vince > > regards > > > -- >> nbari > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRT20fAAoJEF4mgOY1fXowSUgP/2nsrgG52yFG9kHwf0TPO+Yt p2WUDUrbDnfL9UCyI19ijoywAPkurlLhdGbmYu81OOEDMv0YQxnI/fhBGSlIsZwF FGuB+dFj80PclkaSG356QdT+TPHGXpIj/JKTNvTdcPXt949Uoq3ckE06pHQuPJ4D iRDkbFRzZOVqGesyBpmbf2bXy/TfvHPQ+/NO4oS2c+v1ayvC9A505MJcQVSJOn/x 5zRRLxSDAalQJVcq+NcDTLrDk8I8S5gDA34MkscwZUB1jR741Busyz8WTRthd3oB W2FtXwCu6n+qghdUBJVuYtlvuo9UEA32kG4uuSeQqBlsL1jL7kmiEJLrEB9saTYd /yZmSh4DRz5GT6XeFTZpH3N3b+o21QicczwblvDkAT7j46//gtLYo+wMuC5m+zdV fJivIog9pfPjvekj5o8bMGV16sqt/FO11HYNOJxHSTKbY7El6xFE0VgppnnrSBpT KjXn9UJWBiouFfpsSL2DvLMKpfc8QardVRz2NR9IkpuqPeVErgkhZ3Tj0vXcEwPC 27KslN0u5wcTgq3D5vvcV++xn5+EPyEUnphNMRYtRm7u3x6K7FTlz800ok7+gZNU rsDjwZ8SuiktOEOI3XGIPaMvceJTJWq4pJxQapZIxjGxYlqyFWOuRyPja1IEpdik 8RgSHMr03vAwvwWyNhJm =UTDJ -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: attaching iscsi (or ggate) disk before mounting root
On 23/02/2013 10:52, Wojciech Puchar wrote: > how to do it? Only way I know to get iscsi that early would be to use http://freebsd.1045724.n5.nabble.com/iSCSI-boot-driver-0-2-5-isboot-ko-has-been-released-td5736301.html I never did get round to trying it myself though Vince > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: IPMI console [Re: Chicken and egg, encrypted root FS on remote server]
On 20/02/2013 20:31, Paul Schenkeveld wrote: > Hi Daniel, > > On Wed, Feb 20, 2013 at 10:55:47PM +1030, Daniel O'Connor wrote: >> On 20/02/2013, at 21:43, Paul Schenkeveld wrote: What about getting a remote console like HP's ILO or Dell's DRAC ? You get to login remotely, you can use some degree of access control... you can even remote boot. >>> For new hardware I could indeed use this, the current hardware does not >>> support remote console. >>> >>> I don't have experience with ILO nor DRAC but I do have experience with >>> SuperMicro's KVM over LAN which does need a java client to run. If I can >>> enter the passphrase over ssh that would be better as I can use any device >>> including a smartphone to dial in and enter the passphrase. >> >> If you setup a serial console you don't need Java if you use ipmitool, eg >> ipmitool -H remoteip -U ADMIN -I lanplus sol activate > Tried that with some Supermicro servers, the serial console allows me to > get into BIOS config and shows boot messages up to starting the kernel, > once the kernel starts output stops. > > In the BIOS setup, console redirect defaults to com2 port which explains > why output stops after the loader passes control to the kernel. > > BTW, ipmitool always gives me "Info: cannot activate SOL payload with > encryption" but ipmi-console (sysutils/freeipmi) works. > > If I change the console redirect to com1, my screen stays blank. Would > you perhaps know how to use com1 for redirect and connect to it using > ipmi-console (or ipmi-tool)? I have a supermicro using ipmi sol running happily using com2 my notes were ahem,less than through however hopefully they are enough? (FreeBSD 9.1-RELEASE) For Serial over lan (ipmi) edit /boot.config to contain -Dh edit /boot/loader.conf to add ipmi_load="YES" hint.uart.0.flags="" hint.uart.1.flags="0x10" console="comconsole vidconsole" comconsole_speed="19200" boot_multicons="yes" edit /etc/ttys change line for ttyu1 ttyu1 "/usr/libexec/getty std.19200" vt100 on secure -- root@kyanite london]# ipmitool -I lanplus -U admin -E -H 192.168.22.118 sol activate Unable to read password from environment Password: [SOL Session operational. Use ~? for help] FreeBSD/amd64 (copia.namesco.net) (ttyu1) login: Hope thats helpful Vince > Thanks, > > Paul Schenkeveld > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: reason for "magic" crashes.
On 24/06/2012 18:05, Wojciech Puchar wrote: > i've got third crash third week in a row. > > Every time in sunday after 18:00, every time with rsync process (which > means rsync based backup that is done every day, not just in sunday!), > > you may see a crash (viewed from KVM) at > > http://www.tensor.gdynia.pl/~wojtek/crash.png > > what is important - syncing disk doesn't go on, system hangs here. > > For 99% system is not overheating at sunday, but i will be 100% sure > as i added ipmitool sensor logged from cron every 5 minutes. > > Please give me an idea what to check. >From the FAQ http://www.freebsd.org/doc/en/books/faq/troubleshoot.html#TRAP-12-PANIC and http://www.freebsd.org/doc/en/books/faq/advanced.html#KERNEL-PANIC-TROUBLESHOOTING Hope that helps. Vince > > > There is nothing in cron that is done at sunday. > > i don't run "periodic" stuff in /etc/crontab > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Replacing rc(8) (Was: FreeBSD Boot Times)
On 18/06/2012 09:11, Atte Peltomäki wrote: > On Fri, Jun 15, 2012 at 03:43:37PM -0400, Outback Dingo wrote: >> On Fri, Jun 15, 2012 at 8:48 AM, Atte Peltomäki >> wrote: >>> On Thu, Jun 14, 2012 at 02:09:38PM -0400, Richard Yao wrote: Also, I am certain that the OpenRC developers would be thrilled if FreeBSD adopted OpenRC. If FreeBSD core is interested in OpenRC, feel free to contact the OpenRC and/or the Gentoo FreeBSD developers. We would all love to see OpenRC in upstream FreeBSD. >>> Replacing rc(8) has a lot of risks and not many benefits. Current system >>> is somewhat limited, but it works, it's simple to understand and >>> everyone already knows it and uses it. >>> >>> Solaris SMF is by far the most advanced bootup/service manager I've come >>> across, [...] >>> >>> Personally, as much as I like power of SMF, I think FreeBSD devs have >>> much more important (and interesting) things to do. >> Theres always Launchd also. > Launchd is strikingly similar to SMF, which probably isn't a > coincidence, knowing how much other code Apple pulled from Solaris > during those days. > There was even some work done to get it working for FreeBSD if anyone feels like taking it up again. http://wiki.freebsd.org/launchd ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: mfid, raid monitoring daemon
On 09/03/2012 11:52, Damien Fleuriot wrote: > On 3/8/12 7:08 PM, Sean Bruno wrote: >> I'm trying to decide if I should cram "mfid" for mfi(4) controllers into >> the src tree or if we should package it up into a ports package. I >> suspect that either one is acceptible, but it seems to make more sense >> to put it into the src tree since mfiutil is also there. >> >> Comments? >> >> Sean >> >> ref: http://svnweb.freebsd.org/base/user/sbruno/mfid/ > > For what it's worth, we use the following plugin for our Nagios RAID > checks on MFI controllers. > I'm attaching the nagios script below for those that are interested. > The downside is it uses Megacli and all the linux compatibility stuff :( > > > > I for one would be *delighted* if a system came up that would allow me > to skip the whole linux compatibility layer ! > Can you not get enough info via mfiutil? not to mention there is a FreeBSD megacli sysutils/megacli as well as sysutils/linux-megacli that said I favour a port for the reasons you give below. Vince > IMO: > - port: flexibility (can choose to install or not, can update whenever > you want) > - base: no hassle with managing the port, at the cost of less > flexibility (installed by default, updates only with the base system) > > > I slightly favor a port. > > > > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: E-Mail if updates available?
On 30/03/2011 06:31, Jo Galara wrote: > Hi, > > on Debian I'm using apticron which sends me an email if there are > updates available for installed packages. Is there a similar program for > FreeBSD? > Hi, I use ports rather than packages, so a combination of a cron for portsnap to update the portstree (at some silly time so I wont accidentally update ports while portsnap is doing stuff to the ports tree, see the manpage.) and "portmaster -L | grep New" I dont cron it but you could easily enough, (portmaster is ports-mgmt/portmaster , you could use the tools from ports-mgmt/portupgrade of you prefer.) Oh and I'd suggest freebsd-questions as a better list for this kind of query. Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: about zlib on FreeBSD
Dag-Erling Smørgrav wrote: > Jiandong Lu writes: > >> zlib package of ms windows could handle .zip archives, it compiles >> minizip into the zip library. >> > > Firstly, zlib is one thing and one thing only, namely the reference > implementation of Jean-Loup Gailly's gzip (aka. deflate) compression > algorithm. See zlib.net. > > Secondly, Microsoft don't maintain official packages of third-party > software, so there is no such thing as "zlib package of ms windows". > Various projects (Cygwin, MSYS, MinGW, GNUWin32) ship pre-compiled zlib > binaries for Windows, but none of the four I mentioned include zip > support in their version of zlib. > > >> Should we merge minizip into libz ? >> > > No. Why should we? > > If you want to create or unpack .zip files on FreeBSD, use tar(1). > > DES > To be fair, bsdtar(1) on my 8-STABLE box says it can read but not that it can create zipfiles. It it can create them that would be handy. Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Tracing Wake on Lan problem?
Matthew Hagerty wrote: > >> > Yes, but I'm trying to use Intel's driver at this point (since the > stock 7.2R em driver, as stated, does not support WoL yet): > > http://downloadcenter.intel.com/filter_results.aspx?strTypes=all&ProductID=1938&OSFullName=FreeBSD*&lang=eng&strOSs=52&submit=Go! > > > And it does appear to offer support for WoL. They (Intel) have > functions in their if_em.c source file that sets up the WoL. However, > there is no IFCAP_WOL define in Intel's code, so maybe it does not > interface with ifconfig correctly at this point? I don't know. I was > hoping to get some pointers on where to look or how to tell. Also, > I'm not opposed to adding the WoL support - I'm not too bad in C - > I've just never written a FreeBSD device driver and the excellent post > by Stefan Sperling (referenced from the WoL wiki) seems to be too far > out of date. > > The wiki itself states: "Note that the obsolete ioctl-based > configuration approach is discussed there, but ifcaps should be used > instead." > > So, not knowing anything about either ioctl-based or ifcaps config, I > can't find any resources on how to get started in the right direction > (hence my post to hackers). > > Also, if Intel's driver code works, it seems to me that it makes more > sense to use their code for em devices, no? Is there a copyright > problem with that? Sorry I missed the first email or two and didnt realise you were trying the latest from the intel site. Intel (well an intel employee but as part of his day job from what I understand from his posts,) maintains the driver in the source tree. The last I remember him saying about wake on lan for em was http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009461.html As to why FreeBSD isnt using the one currently on the intel site, not certain but it may just be a case of it needing updating/committing, as an email from the maintainer http://markmail.org/message/u4crubkss3354nlt indicates from a previous similar enquiry. hope that helps, Vince > > Matthew > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Tracing Wake on Lan problem?
Matthew Hagerty wrote: > Bob Bishop wrote: >> Hi, >> >> On 11 Aug 2009, at 04:55, Matthew Hagerty wrote: >> >>> I'm trying to get the Wake on Lan feature working on a 7.2-release >>> box. [etc] >> >> You may need to turn WoL on in the BIOS, have a look in the same >> place as the LAN boot settings. >> >> -- >> Bob Bishop >> r...@gid.co.uk > I guess I assumed that, since the WoL works with my Intel Pro/100 NIC, > that the APCI and wake-up settings in the BIOS were set correctly. It > is only when I try the Pro/1000 that I'm having problems; and it seems > to be a driver or config issue. > > Matthew I think you are out of luck as yet. according to http://wiki.freebsd.org/WakeOnLan grep -l IFCAP_WOL /usr/src/sys/dev/*/*.c should get a list of drivers that support WOL. 16:28:19 <~>) [jh...@crab] 0 $ grep -l IFCAP_WOL /usr/src/sys/dev/*/*.c /usr/src/sys/dev/ae/if_ae.c /usr/src/sys/dev/age/if_age.c /usr/src/sys/dev/alc/if_alc.c /usr/src/sys/dev/ale/if_ale.c /usr/src/sys/dev/fxp/if_fxp.c /usr/src/sys/dev/jme/if_jme.c /usr/src/sys/dev/nge/if_nge.c /usr/src/sys/dev/re/if_re.c /usr/src/sys/dev/stge/if_stge.c /usr/src/sys/dev/txp/if_txp.c /usr/src/sys/dev/vr/if_vr.c (16:28:21 <~>) [jh...@crab] 0 $ uname -r 7.2-STABLE The Pro/1000 driver is if_em (or if_igb) So i think you are out of luck on 7.x Vince > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: 8 week projects
On 24/6/09 17:40, Sean Bruno wrote: > My open source class this summer has a lot of people in it looking for 8 > week projects. > > If you have a decently spec'd out project that a Junior/Senior CS > student can accomplish, send me a link or pointer to it and I'll see if > I can get the project some attention. > > Dont know about decently spec'd but http://www.freebsd.org/projects/ideas/ has a bunch of ideas if thats any help. Vince > Sean > > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: sysinstall, GJOURNAL and ZFS
On 9/6/09 15:57, Dan Naumov wrote: >> UFS2+SoftUpdates works fine on properly configured UFS2 - and very fast. >> > Yes, UFS2+SoftUpdates is very fast, however, in the case of a power > loss or having to pull the plug on a locked up system, it has a > noticeably higher chance of leaving you with an unbootable system than > if you were using Linux with ext3/ext4 or Windows with NTFS. > > > Interestingly in my experience its been the opposite, I've lost a few ext3 filesystems though bad power, same for NTFS (NT4, less so with 200x) but as yet never for ufs2 (fsck has always fixed it.) That said, there have been a few projects to update/replace/whatever sysinstall, look at the desktopBSD installer (bsdinstaller) and finstall. I'm not sure what the status of either of these 2 are though. Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: setting up local authorative name server with a no-ip.com registered domain
On 11/4/09 21:56, Aryeh M. Friedman wrote: > I have 3 domains that are registered with no-ip.com > (istudentunion.com, org and net). All three are also using their > "no-ip plus" service which provides both static and dynamic resolution > via their nameservers. When I configure the domains nameservers to > be theirs everything works great (for the most part), but when I > change the nameservers to my own sites BIND (base 7.3-RELEASE) I can > get everything to resolve locally and via dig/host/nslookup remotely > (if and only if I specify the nameserver by IP). What appears to be > happing is this: > > ~/Desktop:ar...@flosoft% !d > dig ns istudentunion.org +trace > > ; <<>> DiG 9.4.3-P2 <<>> ns istudentunion.org +trace > ;; global options: printcmd > .463753INNSI.ROOT-SERVERS.NET. > .463753INNSC.ROOT-SERVERS.NET. > .463753INNSL.ROOT-SERVERS.NET. > .463753INNSK.ROOT-SERVERS.NET. > .463753INNSM.ROOT-SERVERS.NET. > .463753INNSA.ROOT-SERVERS.NET. > .463753INNSE.ROOT-SERVERS.NET. > .463753INNSB.ROOT-SERVERS.NET. > .463753INNSH.ROOT-SERVERS.NET. > .463753INNSD.ROOT-SERVERS.NET. > .463753INNSG.ROOT-SERVERS.NET. > .463753INNSF.ROOT-SERVERS.NET. > .463753INNSJ.ROOT-SERVERS.NET. > ;; Received 500 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms > > org.172800INNSB2.ORG.AFILIAS-NST.org. > org.172800INNSA2.ORG.AFILIAS-NST.INFO. > org.172800INNSC0.ORG.AFILIAS-NST.INFO. > org.172800INNSB0.ORG.AFILIAS-NST.org. > org.172800INNSA0.ORG.AFILIAS-NST.INFO. > org.172800INNSD0.ORG.AFILIAS-NST.org. > ;; Received 437 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 86 ms > > istudentunion.org.86400INNSns2.istudentunion.org. > istudentunion.org.86400INNSns1.istudentunion.org. > ;; Received 103 bytes from 199.19.54.1#53(B0.ORG.AFILIAS-NST.org) in > 88 ms > > ;; connection timed out; no servers could be reached > Since your nameservers for istudentunion.org are in the istudentunion.org domain, you will need glue at the parent nameservers to prevent a chicken and egg problem. Exactly how you tell no-ip this i'm not sure but its not a terribly unusual request. Once the have added it you will need to wait for the .org tld zone to update (not sure of their schedule but better than the once or twice a day of 10 years ago :) The other way around this is to have the nameservers for the domain to be in an already resolving domain, that way you dont need to worry about glue. This is very common. Vince > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: startup options
Chuck Robey wrote: > I was wondering if it was possible, with a machine that has about 2 > year old > dual AMD64 processors and an up-to-date AMI BIOS, to get the machine > to be able > to start up from a power shutdown, after some sort of a network signal? > > If it might be possible, could you maybe put me onto the path of > whatever info > there might be on that subject? Wake on LAN is I believe a work in progress. http://wiki.freebsd.org/WakeOnLan its not an area I have much knowledge of though so other might be able to help more. Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: If not the force, what should I use?
Jonathan McKeown wrote: On Wednesday 13 August 2008 10:40:53 Vincent Hoffman wrote: Jonathan McKeown wrote: People keep talking about forcestart. Unless I'm misunderstanding things horribly, forcestart does exactly that - forces the service to start regardless of any error that may occur. The better option for starting something as a one-off (not enabled in rc.conf) is mnemonically named onestart - which only ignores the rcvar but still fails on any other error. And yes, I like having onestart/onestop distinguished from start/stop. I believe it "forces" a start even though its not actually enabled (in rc.conf) rather than regardless of errors. If you really want a command line of onestart/onestop install the sysutils/bsdadminscripts port which has a script called rconestart and rconestop which do exactly that ;) No, you don't need to install anything - it's part of rc.subr. From the rc.subr(8) manpage: argument may have one of the following prefixes which alters its operation: fast Skip the check for an existing running process, and sets rc_fast=YES. force Skip the checks for rcvar being set to ``YES'', and sets rc_force=YES. This ignores argument_precmd returning non-zero, and ignores any of the required_* tests failing, and always returns a zero exit status. oneSkip the checks for rcvar being set to ``YES'', but performs all the other prerequisite tests. I certainly use onestart - generally when I'm configuring and testing a new service before enabling it in rc.conf. I also use it with NFS. Whenever I've changed /etc/exports, I force mountd to reread it by issuing /etc/rc.d/mountd onereload Doh I just skimmed though /etc/rc.subr not the manpage, thanks for the pointers. Vince Jonathan ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD))
Jonathan McKeown wrote: On Tuesday 12 August 2008 17:51:32 Mike Meyer wrote: On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" <[EMAIL PROTECTED]> wrote: Umm, I have used Gentoo and I do not remember having to use "forcestart" at the command line... Ok, given that you 1) want to have both " this service if it's part of our normal runtime" and " this service even if it's not part of our normal runtime" as script commands, and that 2) without a prefix gets the "if it's part of our normal runtime" meaning, as we want the user to have to explicitly say "Yes, I know this looks odd, but I know what I'm doing so do it anyway" to get the "even if it's not part of our normal runtime" behavior, then what would you have us use instead of "force"? People keep talking about forcestart. Unless I'm misunderstanding things horribly, forcestart does exactly that - forces the service to start regardless of any error that may occur. The better option for starting something as a one-off (not enabled in rc.conf) is mnemonically named onestart - which only ignores the rcvar but still fails on any other error. And yes, I like having onestart/onestop distinguished from start/stop. I believe it "forces" a start even though its not actually enabled (in rc.conf) rather than regardless of errors. If you really want a command line of onestart/onestop install the sysutils/bsdadminscripts port which has a script called rconestart and rconestop which do exactly that ;) Vince Jonathan ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: If not the force, what should I use? (Was: FreeBSD in Business (was Re: Idea for FreeBSD))
Stefan Lambrev wrote: Mike Meyer wrote: On Tue, 12 Aug 2008 17:10:22 +0200 "Adrian Penisoara" <[EMAIL PROTECTED]> wrote: While we're at it, I wish we could leverage the posibility for the admin to manually start the service at the CLI, no matter whether the service has been enabled or not -- that is the "_enable" keyword should have effect only in the bootup/automatic contexts. Like keywords - forcestart forcerestart forcestop ?!?! Yes, I am always reminded of that :). Well, to tell you the truth, I do not know of any other OS which requires prefixing with "force" the start/stop actions in order to act on the service at the command line, and personally I wish it weren't the case. Well I bet you can find this in most linux distros that copy FreeBSD. What about gentoo? Umm, I have used Gentoo and I do not remember having to use "forcestart" at the command line... Ok, given that you 1) want to have both " this service if it's part of our normal runtime" and " this service even if it's not part of our normal runtime" as script commands, and that 2) without a prefix gets the "if it's part of our normal runtime" meaning, as we want the user to have to explicitly say "Yes, I know this looks odd, but I know what I'm doing so do it anyway" to get the "even if it's not part of our normal runtime" behavior, then what would you have us use instead of "force"? Personally, I think "start -f" or "start --force" might have been better, but it's to late to fix such a minor thing. I think the idea (behind not using force) is to implement something like in RH where there is a number of folders (for every run level) populated with links to the real rc scripts which are in /etc/init.d/ and when you type /etc/init.d/script start it will be started but the boot up rc.scripts will never do start on /etc/init.d/ itself only on the folder with links. It's not much better (or worse?) then the current system in freebsd, so I do not see why we should bother. http://en.wikipedia.org/wiki/Init I hate sysV style init myself, half of why I moved to *BSD Vince ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Idea for FreeBSD
Adrian Penisoara wrote: I also agree that it would be good for the rc.d scripts to (re)configure themselves, since they are the ones who really know what's best for them. While we're at it, I wish we could leverage the posibility for the admin to manually start the service at the CLI, no matter whether the service has been enabled or not -- that is the "_enable" keyword should have effect only in the bootup/automatic contexts. /etc/rc.d/$service forcestart seems to be what you want. I do like the idea of being able to enable/disable services from the rc scripts as /etc/rc.d/$service rcvar | sed 's/NO/YES/' >> /etc/rc.conf and/or editing rc.conf can feel a little clunky at times. Vince I think a drop-in command like "rcadm" (someone mentioned this as an idea, but cant remember who) would be a good start for managing the states of services. Mike Meyer also brought up many good points that I agree with. Please try not to get caught up in the XML stuff, that is not a requirement or suggestion, it is just an example of how Sun did it, now how FreeBSD has to;) Someone recommended Puppet, but this is an entire framework that would have to be added/implemented and configured to work with FreeBSD as well as learning a new markup language for it. launchd has a lot of good ideas, but I am not sure how mature it is yet; maybe it is a good place to start. Let's put another name on the table: Upstart (upstart.ubuntu.com). It's quite fast. If we start with the basics and break it down and program this from a modular standpoint it is not so bad. Begin with the basic (high-level) approach. A shell script (service) that is aware of where rc scripts are located and that can keep track of what the current state of the services (PID's) are. An enable/disable command is nothing more that throwing a start/stop command to these rc files. The rc.conf can assist with knowing what should be enabled/disabled and what flags to throw at it. For EXAMPLE, (you got that, example only) Solaris uses one master service that is started first, and the whole point of that first service is to monitor the other services and know what state they are in and starts dependent services upon boot. Consider it the service manager almost. That would very important to for service crash recovery, to keep critical services running. Side note:what about starting up and monitoring services in jails, probably we'd need one such master service per jail ? My 5cents, Adrian. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Idea for FreeBSD
Alex Kozlov wrote:
On Thu, Aug 07, 2008 at 11:25:39AM -0400, Mike Meyer wrote:
On Thu, 7 Aug 2008 09:15:00 +0300 Alex Kozlov <[EMAIL PROTECTED]> wrote:
[1]:
$cat /usr/local/bin/service
Basically what I had in mind, but it can be made more portable across
FreeBSD configurations.
[...]
And here's where you go wrong. What you want now is:
Yes. This is more correct:
Just to save reimplementing the wheel, have a look also at the
sysutils/bsdadminscripts port. it has rcstart (and various hardlinks,)
which are intended for pretty much what youre intending I think.
Vince
#!/bin/sh
name=$1
cmd=$2
if [ -z "${name}" -o -z "${cmd}" ]; then
echo ${0##*/} service_name command
exit 3
fi
. /etc/rc.subr
load_rc_config ${name}
for dir in /etc/rc.d ${local_startup}; do
if [ -r "${dir}/${name}" ]; then
run_rc_script "${dir}/${name}" ${cmd}
exit 0
fi
if [ -r "${dir}/${name}.sh" ]; then
run_rc_script "${dir}/${name}.sh" ${cmd}
exit 0
fi
done
echo "service '${name}' not found"
exit 2
--
Adios
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Sysinstall is still inadequate after all of these years
Gary Jennejohn wrote: On Thu, 17 Jul 2008 09:30:17 -0700 Randy Bush <[EMAIL PROTECTED]> wrote: I think the best route to that is to have a separate utility for managing disk partitioning. The installer can then use that utility, and sysadmins can also use it later after the system is installed. i often invoke sysinstall on a running system to slice/partition/etc a new drive [radically trimmed Cc list] sade(8) is supposed to take the place of sysinstall for disk operations. Ahh thats nice to know, might be worth adding to the handbook, I used to use /usr/ports/sysutils/sfdisk but somethng in base beats it. Vince --- Gary Jennejohn ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
