Re: Help with Booting
Hi, On Saturday 23 April 2011 12:57:32 Doug Hardie wrote: > > On 22 April 2011, at 21:28, Erich Dollansky wrote: > > > It looks to me that not even the loader loads. Is this true? > > > I am not sure. The last message is the timestamp from the original > distribution build. Then is a line with just the '/' character that should > spin a bit. It doesn't. > > By playing around a bit I got it a bit farther. I took one of the raid disks > and mounted it in a different system. I did an install on it but without > changing the label other than to use all the disk. Then I put it back in the > production system and booted. It appears to retain the RAID characteristics, > but all I get is a '-' at the top left of the screen. I then plugged in the > memstick image and booted from that. Right after the last DOS window I > pressed F10 which took me to a FreeBSD boot line with the default pointing > to ad0. I used 0:ad(4,a)/boot/loader and it went on to the same point as > before, but then a bit farther. I now see: > this is all to weird for me. Could you install a disk not using the raid hardware? It would then exclude the motherboard as the cause. Erich > Loading /boot/defaults/loader.conf > /boot/kernel/kernel text=0x8ffac1 | > > The '|' normally spins a couple of times and moves on to the next section. > However, its hung there now. > > > > > > On Saturday 23 April 2011 05:38:41 Doug Hardie wrote: > >> I have an AMD based system that is driving me nuts. I am trying to > >> install 8.2 on it but can't get past the first boot. I had a system up > >> and running on it before, but I had to remove a drive and do the install > >> on another computer. That worked, but now I need to use the built in RAID > >> hardware. As best as I can tell I am going to have to install on the the > >> actual hardware. Motherboard is an Arima NM46X. The machine appears to > >> be about 6 years old. > >> > >> I have tried to boot the install disk, the live filesystem disk, and the > >> memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the > >> same thing: > >> > >> Bootstart starts. > >> > >> BTX loader lists the drives and memory > >> > >> FreeBSD bootstrap loader version 1.1 starts. I get the build date and > >> then a new line with just a '/' on it. It never begins to spin. No > >> additional I/O occurs with the boot device. > >> > >> The memstick and CDs are good. They boot just fine on another computer, > >> just not this one. I have had to work around CD issues in the past, but I > >> thought the memstick would work if the BIOS would recognize it and boot > >> from it. It recognizes it and tries to boot. I need some ideas here as > >> the RAID is essential for this application. Thanks, > >> > >> > >> ___ > >> 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: How to be an imap Client?
In freebsd-questions Digest, Vol 359, Issue 7, Message: 1 On Thu, 21 Apr 2011 21:27:13 -0700 per...@pluto.rain.com wrote: > To: freebsd-questions@freebsd.org > > Jerry wrote: > > > > > Actually yes. Ignoring for a moment the reply you sent me > > > > directly, conveniently bypassing the group forum, > > > > > > perry's message, like this one, was likely posted to you, cc the > > > list. That's long been customary on freebsd lists, even this > > > 'kindergarten' one; noone 'conveniently bypassed' anything. If you > > > don't like private copies, sent as a courtesy, just delete them and > > > move on. > > > > Wrong, it was sent directly, not CC'd. As per my stated policy, it was > > answered/referred to on the list forum. I am seriously considering > > changing that policy to also include reporting them as Spam. > > Before making any such accusations, you had better make D@#% sure of > your facts, lest you find yourself on the wrong end of a libel suit. > > My email client respects Reply-To: and I checked my logs just to be > sure. That reply, as this one, was sent _only_ to the list. Apologies for assuming you must have cc'd Jerry. I should have checked your original post in freebsd-questions Digest, Vol 359, Issue 4, which shows any ccs, but not headers such as Reply-To: per message .. Message: 23 Date: Wed, 20 Apr 2011 23:22:35 -0700 From: per...@pluto.rain.com Subject: Re: How to be an imap Client? To: freebsd-questions@freebsd.org Message-ID: <4dafcd2c.tj0+rgq2u5+tzv2y%per...@pluto.rain.com> Content-Type: text/plain; charset=us-ascii Jerry wrote: > On Wed, 20 Apr 2011 10:01:28 -0500 > Martin McCormick articulated: > > ... our entire network is on the blacklist ... > > Why are you blacklisted? It seems correcting that problem > would be my first priority. Being a university, okstate.edu has students, most of whom are not in the CIS department or in any way under control of the CIS department's sysadmin. Need I say more? -- Having admin'd small clubs of at most 25 members mostly using regularly virus-, trojan- and malware-infested Windows boxes, I can hardly imagine having to deal with perhaps half of 25,000 similarly vulnerable laptops, at least 1% of which will be trying hard to spam or portscan the planet at any given time - nearly all, as Martin points out, without intent or knowledge of their poor blighted owners .. and they're a smarter crew! cheers, Ian ___ 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: Help with Booting
On 22 April 2011, at 21:28, Erich Dollansky wrote: > Hi, > > does the loader start? > > It looks to me that not even the loader loads. Is this true? > > Erich I am not sure. The last message is the timestamp from the original distribution build. Then is a line with just the '/' character that should spin a bit. It doesn't. By playing around a bit I got it a bit farther. I took one of the raid disks and mounted it in a different system. I did an install on it but without changing the label other than to use all the disk. Then I put it back in the production system and booted. It appears to retain the RAID characteristics, but all I get is a '-' at the top left of the screen. I then plugged in the memstick image and booted from that. Right after the last DOS window I pressed F10 which took me to a FreeBSD boot line with the default pointing to ad0. I used 0:ad(4,a)/boot/loader and it went on to the same point as before, but then a bit farther. I now see: Loading /boot/defaults/loader.conf /boot/kernel/kernel text=0x8ffac1 | The '|' normally spins a couple of times and moves on to the next section. However, its hung there now. > > On Saturday 23 April 2011 05:38:41 Doug Hardie wrote: >> I have an AMD based system that is driving me nuts. I am trying to install >> 8.2 on it but can't get past the first boot. I had a system up and running >> on it before, but I had to remove a drive and do the install on another >> computer. That worked, but now I need to use the built in RAID hardware. >> As best as I can tell I am going to have to install on the the actual >> hardware. Motherboard is an Arima NM46X. The machine appears to be about 6 >> years old. >> >> I have tried to boot the install disk, the live filesystem disk, and the >> memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the same >> thing: >> >> Bootstart starts. >> >> BTX loader lists the drives and memory >> >> FreeBSD bootstrap loader version 1.1 starts. I get the build date and then >> a new line with just a '/' on it. It never begins to spin. No additional >> I/O occurs with the boot device. >> >> The memstick and CDs are good. They boot just fine on another computer, >> just not this one. I have had to work around CD issues in the past, but I >> thought the memstick would work if the BIOS would recognize it and boot from >> it. It recognizes it and tries to boot. I need some ideas here as the RAID >> is essential for this application. Thanks, >> >> >> ___ >> 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: Help with Booting
Hi, does the loader start? It looks to me that not even the loader loads. Is this true? Erich On Saturday 23 April 2011 05:38:41 Doug Hardie wrote: > I have an AMD based system that is driving me nuts. I am trying to install > 8.2 on it but can't get past the first boot. I had a system up and running > on it before, but I had to remove a drive and do the install on another > computer. That worked, but now I need to use the built in RAID hardware. As > best as I can tell I am going to have to install on the the actual hardware. > Motherboard is an Arima NM46X. The machine appears to be about 6 years old. > > I have tried to boot the install disk, the live filesystem disk, and the > memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the same > thing: > > Bootstart starts. > > BTX loader lists the drives and memory > > FreeBSD bootstrap loader version 1.1 starts. I get the build date and then a > new line with just a '/' on it. It never begins to spin. No additional I/O > occurs with the boot device. > > The memstick and CDs are good. They boot just fine on another computer, just > not this one. I have had to work around CD issues in the past, but I thought > the memstick would work if the BIOS would recognize it and boot from it. It > recognizes it and tries to boot. I need some ideas here as the RAID is > essential for this application. Thanks, > > > ___ > 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: Help with Booting
On 22 April 2011, at 16:37, Michael Ross wrote: > Am 23.04.2011, 00:38 Uhr, schrieb Doug Hardie : > >> I have an AMD based system that is driving me nuts. I am trying to install >> 8.2 on it but can't get past the first boot. I had a system up and running >> on it before, but I had to remove a drive and do the install on another >> computer. That worked, but now I need to use the built in RAID hardware. >> As best as I can tell I am going to have to install on the the actual >> hardware. Motherboard is an Arima NM46X. The machine appears to be about 6 >> years old. >> >> I have tried to boot the install disk, the live filesystem disk, and the >> memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the same >> thing: >> >> Bootstart starts. >> >> BTX loader lists the drives and memory >> >> FreeBSD bootstrap loader version 1.1 starts. I get the build date and then >> a new line with just a '/' on it. It never begins to spin. No additional >> I/O occurs with the boot device. >> >> The memstick and CDs are good. They boot just fine on another computer, >> just not this one. I have had to work around CD issues in the past, but I >> thought the memstick would work if the BIOS would recognize it and boot from >> it. It recognizes it and tries to boot. I need some ideas here as the RAID >> is essential for this application. Thanks, >> > > Architecture mismatch, trying to boot a amd64 on an i386 machine? That machine runs amd64 just fine. I have to build the disk on another computer. This one will not boot any of the CDs from 6.0 and on. I have only tried the 8.2 memstick version. All of the CDs and memstick boot just fine on a different computer. I suspect its something with the BIOS but no ideas where to even start looking.___ 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"
APPLICATIONS: Custody Evaluator & Parenting Coordinator
You are receiving this email because sometime during the past 20+ years you have registered with PACE, or one of our affiliated companies, to receive free information and offers concerning child custody matters (publications, tests and testing instruments, child custody membership organizations, parental alienation, custody experiences from mental health professionals, child custody seminars, etc.) If you feel you have received this email in error or you no longer wish to receive our child custody related information, you can safely and permanently be removed from the PACE email list by using the UNSUBSCRIBE LINK at the bottom of this email. 73 Valley Drive, Furlong, PA 18925 (800) 633-PACE (7223)FAX (215) 794-3386st...@pace411.com There are also ASSOCIATE credentials for these titles above. See "CRITERIA" below. IMPORTANT! THERE IS A "GRANDFATHERING PERIOD" NOW IN EFFECT FOR THESE CREDENTIALS: There are also ASSOCIATE credentials for these titles above. See "CRITERIA" below. During the Grandfathering Period, "Application Processing Fees" have been reduced by 50% and the PACE “Fast-Track” Application is in use. THE SITE YOU ARE VISITING IS FOR MENTAL HEALTH PROFESSIONALS SEEKING CREDENTIALING INFORMATION If you are a LICENSED ATTORNEY CLICK HERE FOR THE ATTORNEY CERTIFICATION SITE Since 1991 PACE has been recognized as a national mental health professional organization. PACE registers qualified mental health professionals for inclusion in the These individuals hold the following credentials: Nationally Registered Parenting Coordinator™ (NRPC) What is a Parenting Coordinator? The use of Parenting Coordinators is a relatively new intervention to manage high-conflict custody cases. Parents retain and compensate a clinician to arbitrate ongoing child-related disputes either by private agreement or by Court Order. That clinician then becomes the Parenting Coordinator. What does the Parenting Coordinator do? The Parenting Coordinator works directly with the parents to help them communicate more effectively and avoid conflicts about child-related issues. Parents who are constantly in court about child-related issues (such as a holiday visitation schedule or the sharing of information about a child’s academic or medical developments) might benefit from opinions and guidance to help make communication more effective. In addition, the parenting coordinator mediates issues, and when the parents are unable to agree, the parenting coordinator is often given the power to arbitrate what the result should be. Ultimately, the court has the final say over child custody and visitation issues, but a Parenting Coordinator can drastically reduce the need to go to court and therefore reduce conflict for the children in families involved in such disputes. Members will have two documents to verify their certification. One is a license-sized certificate (8" X 5") with special built-in security characteristics and the other is a full-sized certificate for your office. They both contain all of the relevant information and attest to the fact that the named recipient "has satisfied the requirements for education, training, and experience, contained in PACE’S Criteria for inclusion in the and is therefore recognized as a Nationally Registered Parenting Coordinator." Additionally, court personnel and prospective clients will be invited to visit a new website, being developed as both a registry and also to enhance the credibility and stature of the Nationally Registered Parenting Coordinator™(NRPC). Nationally Certified Custody Evaluator™ (NCCE) PACE, as a recognized professional organization, certifies qualified custody evaluators to practice the mental health specialty of Custody Evaluator at the independent practice level. They will hold the credential of Nationally Certified Custody Evaluator™ (NCCE). Members will have two documents to verify their certification. One is a license-sized certificate (8” X 5”) with special built-in security characteristics and the other is a full-sized certificate for your office. They both contain all of the relevant information and attest to the fact that the named recipient "has satisfied the requirements for education, training, and experience, contained in PACE’S Criteria for Practice at the Independent Practice Level and is therefore recognized as a Nationally Certified Custody Evaluator." Additionally, court personnel and prospective clients will be invited to visit a new website, being developed as both a Registry and also to enhance the credibility and stature of the Nationally Certified Custody Evaluator™ (NCCE). There is a Question & Answer Section at the bottom of this site There is a “37-Minute Fill-In and Send Application” near the bottom of this site. PACE'S Criteria for Registration A. Doctoral or Masters Degree (or equivalent) in a mental health specialty from a university/colle
Re: Missing plugin for Firefox
On Friday April 22 2011 5:46:19 PM Jimmie James wrote: > It's a youtube video, so it's flash. > > >I'm running the latest port of Firefox 4.0 I have Sockwave Flash 10.2 r153 plugin in Firefox. I have been playing flash videos in Firefox even before version 4.0. It doesn't play this video. There's no flash capability in Opera or Konqueror, right? I'm running the native(freebsd) Firefox. I could try the Linux version, I think. -- System Name: doris.StevenFriedrich.org Window Manager(s): kde4-4.6.2 X Window System: xorg-7.5.1X.Org X Server 1.7.7 OS version: FreeBSD 8.2-RELEASE i386 (5.9 MB kernel) Platform:HP pavilion zd8000 (zd8215us) CPU: 2.40GHz Intel Pentium 4 with 511 MB memory FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: (play/rec) default ___ 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: Help with Booting
Am 23.04.2011, 00:38 Uhr, schrieb Doug Hardie : I have an AMD based system that is driving me nuts. I am trying to install 8.2 on it but can't get past the first boot. I had a system up and running on it before, but I had to remove a drive and do the install on another computer. That worked, but now I need to use the built in RAID hardware. As best as I can tell I am going to have to install on the the actual hardware. Motherboard is an Arima NM46X. The machine appears to be about 6 years old. I have tried to boot the install disk, the live filesystem disk, and the memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the same thing: Bootstart starts. BTX loader lists the drives and memory FreeBSD bootstrap loader version 1.1 starts. I get the build date and then a new line with just a '/' on it. It never begins to spin. No additional I/O occurs with the boot device. The memstick and CDs are good. They boot just fine on another computer, just not this one. I have had to work around CD issues in the past, but I thought the memstick would work if the BIOS would recognize it and boot from it. It recognizes it and tries to boot. I need some ideas here as the RAID is essential for this application. Thanks, Architecture mismatch, trying to boot a amd64 on an i386 machine? Michael ___ 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: Security monitoring all file changes
2011/4/21 Artem Kuchin : > Hello! > > We are running hosting servers and i think we need to monitor and log all > changes in filesystems (ftp log is written already, but > we give shell access and also files can be changed by scripts), so, when a > client asks when the file/directory > was changed or deleted and by whom we can answer that question. > > In what directtion should i look? Is Audit the thing for it? mtree is probably what you are looking for: http://www.freebsd.org/cgi/man.cgi?query=mtree&apropos=0&sektion=0&manpath=FreeBSD+8.2-RELEASE&format=html -pete -- pete wright www.nycbug.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"
Help with Booting
I have an AMD based system that is driving me nuts. I am trying to install 8.2 on it but can't get past the first boot. I had a system up and running on it before, but I had to remove a drive and do the install on another computer. That worked, but now I need to use the built in RAID hardware. As best as I can tell I am going to have to install on the the actual hardware. Motherboard is an Arima NM46X. The machine appears to be about 6 years old. I have tried to boot the install disk, the live filesystem disk, and the memstick image for FreeBSD 7.0 through 8.2. All of them do exactly the same thing: Bootstart starts. BTX loader lists the drives and memory FreeBSD bootstrap loader version 1.1 starts. I get the build date and then a new line with just a '/' on it. It never begins to spin. No additional I/O occurs with the boot device. The memstick and CDs are good. They boot just fine on another computer, just not this one. I have had to work around CD issues in the past, but I thought the memstick would work if the BIOS would recognize it and boot from it. It recognizes it and tries to boot. I need some ideas here as the RAID is essential for this application. Thanks, ___ 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: Missing plugin for Firefox
flash On Friday 22 April 2011 18:30:10 Steven Friedrich wrote: > Missing plugin for Firefox, but I don't know which one. > > I tried to view this music video, but I have no idea how to discover what > format it is. > > http://popnewswire.tv/play-the-belle-brigade-the-belle-brigade/10481 > > I'm running the latest port of Firefox 4.0 > > --- > - System Name: laptop2.StevenFriedrich.org > Window Manager(s): kde4-4.6.2 > X Window System: xorg-7.5.1X.Org X Server 1.7.7 > OS version: FreeBSD 8.2-RELEASE i386 (5.2 MB kernel) > Platform:HP pavilion zd8000 (zd8215us) > CPU: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory > > FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) > Installed devices: > pcm0: (play/rec) default > ___ > 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: Missing plugin for Firefox
It's a youtube video, so it's flash. How to: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/desktop-browsers.html Steven, wrote: Missing plugin for Firefox, but I don't know which one. I tried to view this music video, but I have no idea how to discover what format it is. http://popnewswire.tv/play-the-belle-brigade-the-belle-brigade/10481 I'm running the latest port of Firefox 4.0 -- I am currently away on leave, traveling through time and will be returning last week. Life is tough, but it's tougher when you're stupid. ___ 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: dialog(1) changed in RELENG_9 (was RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD)
On 04/22/11 11:50, Devin Teske wrote: -Original Message- From: Alexander Best [mailto:arun...@freebsd.org] Sent: Friday, April 22, 2011 8:42 AM To: Devin Teske Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; 'Teske, Devin' Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD On Fri Apr 22 11, Devin Teske wrote: -Original Message- From: Alexander Best [mailto:arun...@freebsd.org] Sent: Friday, April 22, 2011 7:55 AM To: Devin Teske Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; Teske, Devin Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD On Thu Apr 21 11, Devin Teske wrote: Hi List Members! I'm proud to announce the first update to my host-setup utility (a dialog(1)-based host configurator for FreeBSD). The following changes have been made: - fixed bug where /etc/resolv.conf would be created with 0600 permissions - fixed bug when switching from one default gateway to NO default gateway - fixed typo in the title of netmask prompt and ifconfig options dialog - fixed bug that prevented entry of netmask if no netmask is configured You can get the updated version here: http://druidbsd.sourceforge.net/download/host-setup.txt otaku% sudo ./host-setup.txt User cancelled. otaku% echo $? 1 otaku% Can you provide me with the output of "uname -spr"? FreeBSD 9.0-CURRENT amd64 I haven't yet had a chance to pull that one down and install it yet. Hopefully you can help me out with this one here. It's working fine for me on FreeBSD 8.1-RELEASE i386. Where you're bombing out is line 2403: [ $retval -eq 0 ] || die "User cancelled." Functionally, that is testing the return status of dialog(1) for the initial menu. See if you can execute this (a rough approximation of the initial menu): dialog --clear --title foo --hline bar --menu abc 17 55 9 1 a 2 b 3 c 4 d 5 e X x 2> /tmp/dialog.menu.foo doesn't work. :( Bummer! We'll have to fix that. otaku% echo $? 255 otaku% cat /tmp/dialog.menu.foo Error: Unknown option --hline. Use --help to list options. Aha! I think I remember seeing in the list a thread related to swapping out dialog(1) for something new. This must be it. otaku% taku% whereis dialog dialog: /usr/bin/dialog /usr/share/man/en.ISO8859-15/man1/dialog.1.gz /usr/src/gnu/usr.bin/dialog otaku% /usr/bin/dialog cdialog (ComeOn Dialog!) version 1.1-20100428 Copyright 2000-2007,2008 Thomas E. Dickey This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I can't recall as I don't have the thread in front of me, but why was dialog(1) replaced with cdialog? licensing? performance? I guess I could code my script to support this new dialog(1), but... can you see if the below works (I removed the "--hline" option): dialog --clear --title foo --menu abc 17 55 9 1 a 2 b 3 c 4 d 5 e X x 2> /tmp/dialog.menu.foo If that succeeds, then I can modify my script to not use `--hline' on RELENG_9 and higher (referencing `sysctl -n kern.osreldate` for example). [...] A menu should appear. Select an item and then execute for me: echo $? If the above doesn't work, then I suspect that your dialog(1) is not working properly. I'd then go and try this as a sanity check: cd /usr/share/examples/dialog otaku% cd /usr/share/examples/dialog cd: no such file or directory: /usr/share/examples/dialog Really? I would have thought that the examples in that directory (which are merely shell scripts) would have been recoded for cdialog rather than altogether removed. Maybe there was licensing issues there too. Was there? sh menubox echo $? The result in both cases (as long as you actually select a menu item) should be "0". Also... (just as a sanity check for me) your /bin/sh is not a symlink to bash is it? otaku% file /bin/sh /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.0 (900034), stripped Cool. Though I'm still disappointed that my beloved dialog(1) has gone missing (rather, replaced with something doesn't accept the same arguments and/or options)(which is the problem that we're experiencing here). Is there anybody familiar with the changing-out dialog(1) that can bring me up to speed with reasoning and specifics for RELENG_9? Also, might it be prudent -- before cutting 9_0_RELEASE -- to add the fact that dialog(1) no longer accepts `--hline' to the UPGRADING and/or ERRATA documents? It's almost entirely compatible, but I apologize for the breakage you experienced. The reasons it was replaced it were that it (a) has a better libdialog API, (b) has a better license (LGPL instead of GPL), (c) is maintained, and (d) supports 8-bit character sets. If there is some specific feature you are interested in (--hline for instance), I'd suggest writing to Thomas Dickey, the maintainer. -Nathan __
[UPDATE] jail_build(8) -- a dialog(1)-based utility for building jails from binary releases
Hi List,
I'm happy to report that I've fixed a critical bug in my jail_build(8) utility:
- Fixed bug that could cause binary distribution sets to not be unpacked if/when
the inodes of the split tar archive pieces did not occur in sequential order.
The result would be entire swaths of missing files in the jail destination
directory. Problem was missing "-s" argument to force find(1) to produce
lexicographically sorted results when building the list of tar pieces to be
concatenated into a pipe to tar(1).
You can get the updated script here:
http://druidbsd.sf.net/download/jail_build.txt
or
http://druidbsd.sf.net/download/jail_build.gz
or
http://druidbsd.sf.net/
For those not familiar, my jail_build(8) script can be used to unpack a binary
release (found at ftp://ftp-archive.freebsd.org/pub/FreeBSD/releases or
ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases or if you have a
CD/DVD-ROM from either Walnut Creek or FreeBSDMall) as a new jail to any desired
destination directory. Creating a jail from a binary release is much faster than
using the build(7) process. The only downside is that you may not have the
absolutely latest code (unless you use the release(7) process to create your
binary release from, say, HEAD). NOTE: This may not work for RELENG_9 binary
releases as FreeBSD-9 is expected to introduce a new binary release format
(shunning the split tarballs of yesteryear for a single tar-xv archive), however
this has been tested with every binary release from FreeBSD-1.0 to FreeBSD-8.1
with success.
Here's the patch to show what changed:
--- jail_build.orig 2011-04-22 14:54:43.0 -0700
+++ jail_build 2011-04-22 14:06:56.0 -0700
@@ -2,11 +2,11 @@
# -*- tab-width: 4 -*- ;; Emacs
# vi: set tabstop=4 :: Vi/ViM
#
-# Revision: 1.0
-# Last Modified: October 13th, 2010
+# Revision: 1.0.1
+# Last Modified: April 22nd, 2011
COPYRIGHT
#
-# (c)2010. Devin Teske. All Rights Reserved.
+# (c)2010-2011. Devin Teske. All Rights Reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions
@@ -247,7 +247,7 @@ dialog --title "$progname" \
# Get a list of viable repositories to build our jail from
#
repositories="$(
- find -H "$JAIL_BUILD_REPOS" -type d -maxdepth 2 \
+ find -s -H "$JAIL_BUILD_REPOS" -type d -maxdepth 2 \
-name '*-RELEASE' -o \
-name '*-STABLE' -o \
-name '*-CURRENT'\
@@ -490,7 +490,7 @@ esac
# NOTE: Required for repositories that live on NFS (otherwise we could get
# cached responses for `-e', `-f', `-r', and `-w' tests).
#
-find $repos > /dev/null 2>&1
+find -s $repos > /dev/null 2>&1
#
# Determine which distribution-set(s) exist
@@ -582,7 +582,7 @@ for dist in $dists_real; do
-C "'$destdir'" ${quiet:+"> /dev/null 2>&1"}
retval=$?
elif [ -e "$repos/$dist.aa" ]; then
- eval cat $( find "$repos/$dist_path" \
+ eval cat $( find -s "$repos/$dist_path" \
-name "$dist_name.??" -exec echo "'{}'" ';' \
) '|' tar --unlink -pzx${verbose:+v}f - -C "'$destdir'" \
${quiet:+"> /dev/null 2>&1"}
--
Cheers,
Devin Teske
-> FUN STUFF <-
-BEGIN GEEK CODE BLOCK-
Version 3.12
GAT/CS/B/CC/E/IT/MC/M/MU/P/S/TW d+(++) s: a- C+++@$ UB$ P@$ L$ E-
W+++ N? o? K? w@ O M++$ V- PS+>++ PE@ Y+ PGP-> t(+) 5? X(+) R(-) tv+ b+>++ DI+
D+(++) G++ e> h r+++ z+++
--END GEEK CODE BLOCK--
Learn about the "Geek Code": http://www.geekcode.com/
-> LEGAL DISCLAIMER <-
This message contains confidential and proprietary information
of the sender, and is intended only for the person(s) to whom it
is addressed. Any use, distribution, copying or disclosure by any
other person is strictly prohibited. If you have received this
message in error, please notify the e-mail sender immediately,
and delete the original message without making a copy.
-> END TRANSMISSION <-
_
The information contained in this message is proprietary and/or confidential.
If you are not the intended recipient, please: (i) delete the message and all
copies; (ii) do not disclose, distribute or use the message in any manner; and
(iii) notify the sender immediately. In addition, please be aware that any
message addressed to our domain is subject to archiving and review by persons
other than the intended recipient. 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"
Re: Jails: How do i limit what ifconfig shows?
But then the root in the jail can just go and compile a new version of ifconfig from the ports collection. (Generally its a flawed idea to just remove the binaries. Someone can just download new ones. And if downloading new binaries is not allowed, they can always just push stdin through b64.. etc etc.) On 22 April 2011 23:00, Michael Ross wrote: > Am 22.04.2011, 22:21 Uhr, schrieb xor : > >> Hullo >> First off, thanks for a lovely operating system <3 >> >> I decided to go for FreeBSD perhaps 3 days ago. Before, ive been an >> Debian/OpenBSD guy, and ive only used my obsd box for redundant >> firewalls and networking. Ive not been running any services off the >> boxen. >> >> The reason I decided to go for FreeBSD is because of the Jails. Ive >> looked around a bit, but I can not find anything about how to limit >> what interfaces that ifconfig shows. I would like it to hide pretty >> much everything so that _no_ information about the host systems >> networking leaks into the jails. I dont want jails to know anything >> but their IP-numbers and which computer to use for DNS lookups, >> essentially. >> >> Is there any good text out there that describes how to do this? Ive >> searched a bit for it, but Ive been unable to find anything but the >> basics. > > Maybe you can remove the ifconfig binary from the jail. > Works for me. > > > Michael > ___ 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"
Missing plugin for Firefox
Missing plugin for Firefox, but I don't know which one. I tried to view this music video, but I have no idea how to discover what format it is. http://popnewswire.tv/play-the-belle-brigade-the-belle-brigade/10481 I'm running the latest port of Firefox 4.0 System Name: laptop2.StevenFriedrich.org Window Manager(s): kde4-4.6.2 X Window System: xorg-7.5.1X.Org X Server 1.7.7 OS version: FreeBSD 8.2-RELEASE i386 (5.2 MB kernel) Platform:HP pavilion zd8000 (zd8215us) CPU: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: (play/rec) default ___ 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: Jails: How do i limit what ifconfig shows?
Am 22.04.2011, 22:21 Uhr, schrieb xor : Hullo First off, thanks for a lovely operating system <3 I decided to go for FreeBSD perhaps 3 days ago. Before, ive been an Debian/OpenBSD guy, and ive only used my obsd box for redundant firewalls and networking. Ive not been running any services off the boxen. The reason I decided to go for FreeBSD is because of the Jails. Ive looked around a bit, but I can not find anything about how to limit what interfaces that ifconfig shows. I would like it to hide pretty much everything so that _no_ information about the host systems networking leaks into the jails. I dont want jails to know anything but their IP-numbers and which computer to use for DNS lookups, essentially. Is there any good text out there that describes how to do this? Ive searched a bit for it, but Ive been unable to find anything but the basics. Maybe you can remove the ifconfig binary from the jail. Works for me. Michael ___ 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"
Jails: How do i limit what ifconfig shows?
Hullo First off, thanks for a lovely operating system <3 I decided to go for FreeBSD perhaps 3 days ago. Before, ive been an Debian/OpenBSD guy, and ive only used my obsd box for redundant firewalls and networking. Ive not been running any services off the boxen. The reason I decided to go for FreeBSD is because of the Jails. Ive looked around a bit, but I can not find anything about how to limit what interfaces that ifconfig shows. I would like it to hide pretty much everything so that _no_ information about the host systems networking leaks into the jails. I dont want jails to know anything but their IP-numbers and which computer to use for DNS lookups, essentially. Is there any good text out there that describes how to do this? Ive searched a bit for it, but Ive been unable to find anything but the basics. Thanks! ___ 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: dialog(1) changed in RELENG_9 (was RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD)
On Fri Apr 22 11, Devin Teske wrote: > > -Original Message- > > From: Alexander Best [mailto:arun...@freebsd.org] > > Sent: Friday, April 22, 2011 8:42 AM > > To: Devin Teske > > Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; 'Teske, > > Devin' > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for > > configuring > > FreeBSD > > > > On Fri Apr 22 11, Devin Teske wrote: > > > > > > > -Original Message- > > > > From: Alexander Best [mailto:arun...@freebsd.org] > > > > Sent: Friday, April 22, 2011 7:55 AM > > > > To: Devin Teske > > > > Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; > > > > Teske, Devin > > > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for > > > > configuring FreeBSD > > > > > > > > On Thu Apr 21 11, Devin Teske wrote: > > > > > Hi List Members! > > > > > > > > > > I'm proud to announce the first update to my host-setup utility (a > > > > > dialog(1)-based host configurator for FreeBSD). The following > > > > > changes > > > > have been > > > > > made: > > > > > > > > > > - fixed bug where /etc/resolv.conf would be created with 0600 > > > > permissions > > > > > - fixed bug when switching from one default gateway to NO default > > > > gateway > > > > > - fixed typo in the title of netmask prompt and ifconfig options > > > > > dialog > > > > > - fixed bug that prevented entry of netmask if no netmask is > > > > > configured > > > > > > > > > > You can get the updated version here: > > > > > > > > > > http://druidbsd.sourceforge.net/download/host-setup.txt > > > > > > > > otaku% sudo ./host-setup.txt > > > > User cancelled. > > > > otaku% echo $? > > > > 1 > > > > otaku% > > > > > > Can you provide me with the output of "uname -spr"? > > > > FreeBSD 9.0-CURRENT amd64 > > I haven't yet had a chance to pull that one down and install it yet. Hopefully > you can help me out with this one here. > > > > > > > > > It's working fine for me on FreeBSD 8.1-RELEASE i386. > > > > > > Where you're bombing out is line 2403: > > > [ $retval -eq 0 ] || die "User cancelled." > > > > > > Functionally, that is testing the return status of dialog(1) for the > > > initial menu. See if you can execute this (a rough approximation of > > > the initial > > > menu): > > > > > > dialog --clear --title foo --hline bar --menu abc 17 55 9 1 a 2 b 3 c > > > 4 d 5 e X x 2> /tmp/dialog.menu.foo > > > > doesn't work. :( > > Bummer! We'll have to fix that. > > > > > > otaku% echo $? > > 255 > > otaku% cat /tmp/dialog.menu.foo > > > > Error: Unknown option --hline. > > Use --help to list options. > > Aha! I think I remember seeing in the list a thread related to swapping out > dialog(1) for something new. This must be it. > > > > > > > otaku% > > > > taku% whereis dialog > > dialog: /usr/bin/dialog /usr/share/man/en.ISO8859-15/man1/dialog.1.gz > > /usr/src/gnu/usr.bin/dialog > > > > otaku% /usr/bin/dialog > > cdialog (ComeOn Dialog!) version 1.1-20100428 Copyright 2000-2007,2008 > > Thomas > > E. Dickey This is free software; see the source for copying conditions. > > There > is NO > > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > > PURPOSE. > > I can't recall as I don't have the thread in front of me, but why was > dialog(1) > replaced with cdialog? licensing? performance? > > I guess I could code my script to support this new dialog(1), but... can you > see > if the below works (I removed the "--hline" option): > > dialog --clear --title foo --menu abc 17 55 9 1 a 2 b 3 c 4 d 5 e X x 2> > /tmp/dialog.menu.foo > > If that succeeds, then I can modify my script to not use `--hline' on RELENG_9 > and higher (referencing `sysctl -n kern.osreldate` for example). that works with $? == 0 > > > > > > [...] > > > > > > > > A menu should appear. Select an item and then execute for me: > > > > > > echo $? > > > > > > If the above doesn't work, then I suspect that your dialog(1) is not > > > working properly. I'd then go and try this as a sanity check: > > > > > > cd /usr/share/examples/dialog > > > > otaku% cd /usr/share/examples/dialog > > cd: no such file or directory: /usr/share/examples/dialog > > Really? I would have thought that the examples in that directory (which are > merely shell scripts) would have been recoded for cdialog rather than > altogether > removed. Maybe there was licensing issues there too. Was there? > > > > > > > sh menubox > > > echo $? > > > > > > The result in both cases (as long as you actually select a menu item) > > > should be "0". > > > > > > Also... (just as a sanity check for me) your /bin/sh is not a symlink > > > to bash is it? > > > > otaku% file /bin/sh > > /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically > > linked (uses shared libs), for FreeBSD 9.0 (900034), stripped > > Cool. Though I'm still disappointed that my beloved dialog(1) has gone missing > (rather, replaced with something doesn't accept the same arguments and/o
RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD
> -Original Message- > From: Bruce Cran [mailto:br...@cran.org.uk] > Sent: Friday, April 22, 2011 9:35 AM > To: Alexander Best > Cc: Devin Teske; freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; > 'Teske, Devin' > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring > FreeBSD > > On Fri, 22 Apr 2011 15:41:46 + > Alexander Best wrote: > > > FreeBSD 9.0-CURRENT amd64 > > A new version of dialog was imported a few days ago - maybe something broke? Looks like `--hline' is not supported anymore. Thinking this should either be patched or documented in ERRATA/UPGRADING. > > -- > Bruce Cran _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. 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"
dialog(1) changed in RELENG_9 (was RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD)
> -Original Message- > From: Alexander Best [mailto:arun...@freebsd.org] > Sent: Friday, April 22, 2011 8:42 AM > To: Devin Teske > Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; 'Teske, > Devin' > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring > FreeBSD > > On Fri Apr 22 11, Devin Teske wrote: > > > > > -Original Message- > > > From: Alexander Best [mailto:arun...@freebsd.org] > > > Sent: Friday, April 22, 2011 7:55 AM > > > To: Devin Teske > > > Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; > > > Teske, Devin > > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for > > > configuring FreeBSD > > > > > > On Thu Apr 21 11, Devin Teske wrote: > > > > Hi List Members! > > > > > > > > I'm proud to announce the first update to my host-setup utility (a > > > > dialog(1)-based host configurator for FreeBSD). The following > > > > changes > > > have been > > > > made: > > > > > > > > - fixed bug where /etc/resolv.conf would be created with 0600 > > > permissions > > > > - fixed bug when switching from one default gateway to NO default > > > gateway > > > > - fixed typo in the title of netmask prompt and ifconfig options > > > > dialog > > > > - fixed bug that prevented entry of netmask if no netmask is > > > > configured > > > > > > > > You can get the updated version here: > > > > > > > > http://druidbsd.sourceforge.net/download/host-setup.txt > > > > > > otaku% sudo ./host-setup.txt > > > User cancelled. > > > otaku% echo $? > > > 1 > > > otaku% > > > > Can you provide me with the output of "uname -spr"? > > FreeBSD 9.0-CURRENT amd64 I haven't yet had a chance to pull that one down and install it yet. Hopefully you can help me out with this one here. > > > > > It's working fine for me on FreeBSD 8.1-RELEASE i386. > > > > Where you're bombing out is line 2403: > > [ $retval -eq 0 ] || die "User cancelled." > > > > Functionally, that is testing the return status of dialog(1) for the > > initial menu. See if you can execute this (a rough approximation of > > the initial > > menu): > > > > dialog --clear --title foo --hline bar --menu abc 17 55 9 1 a 2 b 3 c > > 4 d 5 e X x 2> /tmp/dialog.menu.foo > > doesn't work. :( Bummer! We'll have to fix that. > > otaku% echo $? > 255 > otaku% cat /tmp/dialog.menu.foo > > Error: Unknown option --hline. > Use --help to list options. Aha! I think I remember seeing in the list a thread related to swapping out dialog(1) for something new. This must be it. > > > otaku% > > taku% whereis dialog > dialog: /usr/bin/dialog /usr/share/man/en.ISO8859-15/man1/dialog.1.gz > /usr/src/gnu/usr.bin/dialog > > otaku% /usr/bin/dialog > cdialog (ComeOn Dialog!) version 1.1-20100428 Copyright 2000-2007,2008 Thomas > E. Dickey This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR > PURPOSE. I can't recall as I don't have the thread in front of me, but why was dialog(1) replaced with cdialog? licensing? performance? I guess I could code my script to support this new dialog(1), but... can you see if the below works (I removed the "--hline" option): dialog --clear --title foo --menu abc 17 55 9 1 a 2 b 3 c 4 d 5 e X x 2> /tmp/dialog.menu.foo If that succeeds, then I can modify my script to not use `--hline' on RELENG_9 and higher (referencing `sysctl -n kern.osreldate` for example). > > [...] > > > > > A menu should appear. Select an item and then execute for me: > > > > echo $? > > > > If the above doesn't work, then I suspect that your dialog(1) is not > > working properly. I'd then go and try this as a sanity check: > > > > cd /usr/share/examples/dialog > > otaku% cd /usr/share/examples/dialog > cd: no such file or directory: /usr/share/examples/dialog Really? I would have thought that the examples in that directory (which are merely shell scripts) would have been recoded for cdialog rather than altogether removed. Maybe there was licensing issues there too. Was there? > > > sh menubox > > echo $? > > > > The result in both cases (as long as you actually select a menu item) > > should be "0". > > > > Also... (just as a sanity check for me) your /bin/sh is not a symlink > > to bash is it? > > otaku% file /bin/sh > /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically > linked (uses shared libs), for FreeBSD 9.0 (900034), stripped Cool. Though I'm still disappointed that my beloved dialog(1) has gone missing (rather, replaced with something doesn't accept the same arguments and/or options)(which is the problem that we're experiencing here). Is there anybody familiar with the changing-out dialog(1) that can bring me up to speed with reasoning and specifics for RELENG_9? Also, might it be prudent -- before cutting 9_0_RELEASE -- to add the fact that dialog(1) no longer accepts `--hline' to the UPGRADING and/or ERRATA documents? -- Devin > > > -- > > Devin > >
Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD
On Fri, 22 Apr 2011 15:41:46 + Alexander Best wrote: > FreeBSD 9.0-CURRENT amd64 A new version of dialog was imported a few days ago - maybe something broke? -- Bruce Cran ___ 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: Subversion over SSH works through GIT but not with SVN
Hello Greg, hello list, thank you very much for your answer, it was very useful! Greg Larkin wrote: On 4/20/11 7:21 AM, Michael Grünewald wrote: I have recently discovered that by subversion client (1.16_2) is not able any more to access my subversion accounts over svn+ssh (with key based authentication). It seems very odd to me, because in the same time git can access these accounts (with the git svn command) and commit to these repositories! [...] Finally, if all else fails, I run commands through truss or strace to see if there are any strange errors generated by system calls, like a missing library or config file, or an unexpected chdir() or chroot(). I feel here a bit ashamed: I plainly forgot to inform subversion that my login name on the remote machine is not the same as on the local, what git has been told years ago. Your clue to use ssh instead of the svn put me on the right track. To my defence, the login name that ssh uses during its conversation is not printed on the diagnostic line when verbose output is enabled. While this information is very basic and elementary, it maybe would be useful to debug a connection (I admit, ``login name'' should stand quite high on the list of things to check when something goes wrong!) In my case, if the login names had been present in the verbose output os SSH ,I woud have spotted it by diff'ing the outputs of the successful and unsuccessful transactions. Maybe I should file a PR for this? Why do I instantly think ``login name'' when I hear ssh and not when I hear svn? Well, I hope my therapist will be able to help me sorting it out :) -- Thank you very much, Michael ___ 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: how to protect my system from third party apps crashes
Sorry sent to OP only... On 21/04/2011 11:21, Michael wrote: Hello. I'm having stability issues on my desktop system running FreeBSD 8.2-R on amd64. It happens quite often that some application (say web browser) goes nuts and totally locks-up my system. When it happens it looks like the application is frozen but I can't kill it. WCPU usage goes up rapidly and after a while system doesn't respond to anything than brutal hard reset. I guess it's not the system itself to blame, but it would be good if it could handle misbehaving programs. What I'm looking for is some kind of protection from system lock ups. I don't mind when the browser hangs, but I don't want it to kill my whole system. Any suggestions, hints, ideas please? I am aware that it's a workaround to the problem instead of a real solution, but that's what is needed. Michael ___ 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" I find sometimes viewing flash video with firefox causes the machine to appear to hang. In fact killing all instances of npviewer.bin frees everything up again. I usually have an xterm open just in case. Don't have a problem with other apps so this might not be the solution for you. My firefox is 3.6.10, flashplayer is linux-f10-flashplugin-10.1r85 and I'm on 8.1R x86 Chris ___ 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: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD
On Fri Apr 22 11, Devin Teske wrote: > > > > -Original Message- > > From: Alexander Best [mailto:arun...@freebsd.org] > > Sent: Friday, April 22, 2011 7:55 AM > > To: Devin Teske > > Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; Teske, > > Devin > > Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for > > configuring FreeBSD > > > > On Thu Apr 21 11, Devin Teske wrote: > > > Hi List Members! > > > > > > > > > > > > I'm proud to announce the first update to my host-setup utility (a > > > dialog(1)-based host configurator for FreeBSD). The following changes > > have been > > > made: > > > > > > > > > > > > - fixed bug where /etc/resolv.conf would be created with 0600 > > permissions > > > > > > - fixed bug when switching from one default gateway to NO default > > gateway > > > > > > - fixed typo in the title of netmask prompt and ifconfig options dialog > > > > > > - fixed bug that prevented entry of netmask if no netmask is configured > > > > > > > > > > > > You can get the updated version here: > > > > > > > > > > > > http://druidbsd.sourceforge.net/download/host-setup.txt > > > > otaku% sudo ./host-setup.txt > > User cancelled. > > otaku% echo $? > > 1 > > otaku% > > Can you provide me with the output of "uname -spr"? FreeBSD 9.0-CURRENT amd64 > > It's working fine for me on FreeBSD 8.1-RELEASE i386. > > Where you're bombing out is line 2403: > [ $retval -eq 0 ] || die "User cancelled." > > Functionally, that is testing the return status of dialog(1) for the initial > menu. See if you can execute this (a rough approximation of the initial > menu): > > dialog --clear --title foo --hline bar --menu abc 17 55 9 1 a 2 b 3 c 4 d 5 > e X x 2> /tmp/dialog.menu.foo doesn't work. :( otaku% echo $? 255 otaku% cat /tmp/dialog.menu.foo Error: Unknown option --hline. Use --help to list options. otaku% taku% whereis dialog dialog: /usr/bin/dialog /usr/share/man/en.ISO8859-15/man1/dialog.1.gz /usr/src/gnu/usr.bin/dialog otaku% /usr/bin/dialog cdialog (ComeOn Dialog!) version 1.1-20100428 Copyright 2000-2007,2008 Thomas E. Dickey This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. [...] > > A menu should appear. Select an item and then execute for me: > > echo $? > > If the above doesn't work, then I suspect that your dialog(1) is not working > properly. I'd then go and try this as a sanity check: > > cd /usr/share/examples/dialog otaku% cd /usr/share/examples/dialog cd: no such file or directory: /usr/share/examples/dialog > sh menubox > echo $? > > The result in both cases (as long as you actually select a menu item) should > be "0". > > Also... (just as a sanity check for me) your /bin/sh is not a symlink to > bash is it? otaku% file /bin/sh /bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), for FreeBSD 9.0 (900034), stripped > -- > Devin > > > > > > > > > > or > > > > > > http://druidbsd.sourceforge.net/download/host-setup.gz > > > > > > or > > > > > > http://druidbsd.sourceforge.net/ > > > > > > > > > > > > > > > > > > For those not familiar with my host-setup(1) utility, it is a 2,500+ > > line shell > > > script that utilizes the dialog(1) utility to walk the system > > administrator > > > through setting up their TimeZone, Hostname, Network Interfaces, Default > > > Gateway, and DNS. Our custom FreeBSD installer sets this script as the > > root > > > login shell, making it very easy for field engineers to quickly get a > > system on > > > the network without having to use the command-line (and without having > > to reboot > > > either). Underneath the hood - behind the system of prompts and dialogs > > - this > > > script manages both the contents of /etc/rc.conf, /etc/resolv.conf, and > > others > > > as well as utilizing ifconfig(8), route(8), and many other tools to > > avoid > > > requiring a reboot, prompting you if you would like to make the new > > changes > > > effective when values are changed from their active settings. > > > > > > > > > > > > Here's the patch to show the details: > > > > > > > > > > > > --- host-setup.3_0 2011-02-10 19:14:30.0 -0800 > > > > > > +++ host-setup 2011-04-21 13:38:58.0 -0700 > > > > > > @@ -2,12 +2,12 @@ > > > > > > # -*- tab-width: 4 -*- ;; Emacs > > > > > > # vi: set tabstop=4 :: Vi/ViM > > > > > > # > > > > > > -# Revision: 3.0 > > > > > > +# Revision: 3.1 > > > > > > # Created: September 21st, 2010 > > > > > > -# Last Modified: December 6th, 2010 > > > > > > +# Last Modified: April 21st, 2011 > > > > > > COPYRIGHT > > > > > > # > > > > > > -# Devin Teske (c)2006-2010. All Rights Reserved. > > > > > > +# Devin Teske (c)2006-2011. All Rights Reserved. > > > > > > # > > > > > > # Redistribution and use in source and binary forms, with or without > > > > > > # modi
RE: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD
> -Original Message-
> From: Alexander Best [mailto:arun...@freebsd.org]
> Sent: Friday, April 22, 2011 7:55 AM
> To: Devin Teske
> Cc: freebsd-hack...@freebsd.org; freebsd-questions@freebsd.org; Teske,
> Devin
> Subject: Re: [UPDATE] host-setup(1): a dialog(1)-based utility for
> configuring FreeBSD
>
> On Thu Apr 21 11, Devin Teske wrote:
> > Hi List Members!
> >
> >
> >
> > I'm proud to announce the first update to my host-setup utility (a
> > dialog(1)-based host configurator for FreeBSD). The following changes
> have been
> > made:
> >
> >
> >
> > - fixed bug where /etc/resolv.conf would be created with 0600
> permissions
> >
> > - fixed bug when switching from one default gateway to NO default
> gateway
> >
> > - fixed typo in the title of netmask prompt and ifconfig options dialog
> >
> > - fixed bug that prevented entry of netmask if no netmask is configured
> >
> >
> >
> > You can get the updated version here:
> >
> >
> >
> > http://druidbsd.sourceforge.net/download/host-setup.txt
>
> otaku% sudo ./host-setup.txt
> User cancelled.
> otaku% echo $?
> 1
> otaku%
Can you provide me with the output of "uname -spr"?
It's working fine for me on FreeBSD 8.1-RELEASE i386.
Where you're bombing out is line 2403:
[ $retval -eq 0 ] || die "User cancelled."
Functionally, that is testing the return status of dialog(1) for the initial
menu. See if you can execute this (a rough approximation of the initial
menu):
dialog --clear --title foo --hline bar --menu abc 17 55 9 1 a 2 b 3 c 4 d 5
e X x 2> /tmp/dialog.menu.foo
A menu should appear. Select an item and then execute for me:
echo $?
If the above doesn't work, then I suspect that your dialog(1) is not working
properly. I'd then go and try this as a sanity check:
cd /usr/share/examples/dialog
sh menubox
echo $?
The result in both cases (as long as you actually select a menu item) should
be "0".
Also... (just as a sanity check for me) your /bin/sh is not a symlink to
bash is it?
--
Devin
>
> >
> > or
> >
> > http://druidbsd.sourceforge.net/download/host-setup.gz
> >
> > or
> >
> > http://druidbsd.sourceforge.net/
> >
> >
> >
> >
> >
> > For those not familiar with my host-setup(1) utility, it is a 2,500+
> line shell
> > script that utilizes the dialog(1) utility to walk the system
> administrator
> > through setting up their TimeZone, Hostname, Network Interfaces, Default
> > Gateway, and DNS. Our custom FreeBSD installer sets this script as the
> root
> > login shell, making it very easy for field engineers to quickly get a
> system on
> > the network without having to use the command-line (and without having
> to reboot
> > either). Underneath the hood - behind the system of prompts and dialogs
> - this
> > script manages both the contents of /etc/rc.conf, /etc/resolv.conf, and
> others
> > as well as utilizing ifconfig(8), route(8), and many other tools to
> avoid
> > requiring a reboot, prompting you if you would like to make the new
> changes
> > effective when values are changed from their active settings.
> >
> >
> >
> > Here's the patch to show the details:
> >
> >
> >
> > --- host-setup.3_0 2011-02-10 19:14:30.0 -0800
> >
> > +++ host-setup 2011-04-21 13:38:58.0 -0700
> >
> > @@ -2,12 +2,12 @@
> >
> > # -*- tab-width: 4 -*- ;; Emacs
> >
> > # vi: set tabstop=4 :: Vi/ViM
> >
> > #
> >
> > -# Revision: 3.0
> >
> > +# Revision: 3.1
> >
> > # Created: September 21st, 2010
> >
> > -# Last Modified: December 6th, 2010
> >
> > +# Last Modified: April 21st, 2011
> >
> > COPYRIGHT
> >
> > #
> >
> > -# Devin Teske (c)2006-2010. All Rights Reserved.
> >
> > +# Devin Teske (c)2006-2011. All Rights Reserved.
> >
> > #
> >
> > # Redistribution and use in source and binary forms, with or without
> >
> > # modification, are permitted provided that the following conditions
> >
> > @@ -1353,8 +1353,10 @@ dialog_input_hostname()
> >
> > # permissions and ownership to match resolv.conf(5) before
> >
> > # we write it out and mv(1) it into place).
> >
> > #
> >
> > - quietly chmod "$( stat -f '%#Lp' "$RESOLV_CONF" )"
> "$tmpfile"
> >
> > - quietly chown "$( stat -f '%u:%g' "$RESOLV_CONF" )"
> "$tmpfile"
> >
> > + local mode="$( stat -f '%#Lp' "$RESOLV_CONF" 2> /dev/null )"
> >
> > + local owner="$( stat -f '%u:%g' "$RESOLV_CONF" 2> /dev/null
> )"
> >
> > + quietly chmod "${mode:-0644}" "$tmpfile"
> >
> > + quietly chown "${owner:-root:wheel}" "$tmpfile"
> >
> >#
> >
> > # Operate on resolv.conf(5), replacing only the last
> >
> > @@ -1646,7 +1648,7 @@ dialog_input_netmask()
> >
> > #
> >
> > while :; do
> >
> > - dialog --title "$brand${band:+}${progname:-$0}" \
> >
> > + dialog --title "$brand${brand:+ }${progname:-$0}" \
> >
> > --hline "Use numbers, punctuation, TAB or ENTER" \
> >
> >
Re: [UPDATE] host-setup(1): a dialog(1)-based utility for configuring FreeBSD
On Thu Apr 21 11, Devin Teske wrote:
> Hi List Members!
>
>
>
> I'm proud to announce the first update to my host-setup utility (a
> dialog(1)-based host configurator for FreeBSD). The following changes have
> been
> made:
>
>
>
> - fixed bug where /etc/resolv.conf would be created with 0600 permissions
>
> - fixed bug when switching from one default gateway to NO default gateway
>
> - fixed typo in the title of netmask prompt and ifconfig options dialog
>
> - fixed bug that prevented entry of netmask if no netmask is configured
>
>
>
> You can get the updated version here:
>
>
>
> http://druidbsd.sourceforge.net/download/host-setup.txt
otaku% sudo ./host-setup.txt
User cancelled.
otaku% echo $?
1
otaku%
>
> or
>
> http://druidbsd.sourceforge.net/download/host-setup.gz
>
> or
>
> http://druidbsd.sourceforge.net/
>
>
>
>
>
> For those not familiar with my host-setup(1) utility, it is a 2,500+ line
> shell
> script that utilizes the dialog(1) utility to walk the system administrator
> through setting up their TimeZone, Hostname, Network Interfaces, Default
> Gateway, and DNS. Our custom FreeBSD installer sets this script as the root
> login shell, making it very easy for field engineers to quickly get a system
> on
> the network without having to use the command-line (and without having to
> reboot
> either). Underneath the hood - behind the system of prompts and dialogs - this
> script manages both the contents of /etc/rc.conf, /etc/resolv.conf, and others
> as well as utilizing ifconfig(8), route(8), and many other tools to avoid
> requiring a reboot, prompting you if you would like to make the new changes
> effective when values are changed from their active settings.
>
>
>
> Here's the patch to show the details:
>
>
>
> --- host-setup.3_0 2011-02-10 19:14:30.0 -0800
>
> +++ host-setup 2011-04-21 13:38:58.0 -0700
>
> @@ -2,12 +2,12 @@
>
> # -*- tab-width: 4 -*- ;; Emacs
>
> # vi: set tabstop=4 :: Vi/ViM
>
> #
>
> -# Revision: 3.0
>
> +# Revision: 3.1
>
> # Created: September 21st, 2010
>
> -# Last Modified: December 6th, 2010
>
> +# Last Modified: April 21st, 2011
>
> COPYRIGHT
>
> #
>
> -# Devin Teske (c)2006-2010. All Rights Reserved.
>
> +# Devin Teske (c)2006-2011. All Rights Reserved.
>
> #
>
> # Redistribution and use in source and binary forms, with or without
>
> # modification, are permitted provided that the following conditions
>
> @@ -1353,8 +1353,10 @@ dialog_input_hostname()
>
> # permissions and ownership to match resolv.conf(5) before
>
> # we write it out and mv(1) it into place).
>
> #
>
> - quietly chmod "$( stat -f '%#Lp' "$RESOLV_CONF" )" "$tmpfile"
>
> - quietly chown "$( stat -f '%u:%g' "$RESOLV_CONF" )" "$tmpfile"
>
> + local mode="$( stat -f '%#Lp' "$RESOLV_CONF" 2> /dev/null )"
>
> + local owner="$( stat -f '%u:%g' "$RESOLV_CONF" 2> /dev/null )"
>
> + quietly chmod "${mode:-0644}" "$tmpfile"
>
> + quietly chown "${owner:-root:wheel}" "$tmpfile"
>
>#
>
> # Operate on resolv.conf(5), replacing only the last
>
> @@ -1646,7 +1648,7 @@ dialog_input_netmask()
>
> #
>
> while :; do
>
> - dialog --title "$brand${band:+}${progname:-$0}" \
>
> + dialog --title "$brand${brand:+ }${progname:-$0}" \
>
> --hline "Use numbers, punctuation, TAB or ENTER" \
>
> --inputbox "$msg" 10 50 \
>
> "$_netmask" \
>
> @@ -1664,7 +1666,7 @@ dialog_input_netmask()
>
> [ $retval -eq $SUCCESS ] || return $retval
>
># Return success if NULL value was entered
>
> - [ "$_netmask" ] || return $SUCCESS
>
> + [ "$_input" ] || return $SUCCESS
>
># Take only the first "word" of the user's input
>
> _netmask="$_input"
>
> @@ -1705,7 +1707,7 @@ dialog_input_options()
>
> msg="Please enter additional network media options to be"
>
> msg="$msg passed to ifconfig(8) for the $interface interface:"
>
> -dialog --title "$brand${band:+}${progname:-$0}" \
>
> +dialog --title "$brand${brand:+ }${progname:-$0}" \
>
>--hline "Use numbers, punctuation, TAB or ENTER" \
>
>--inputbox "$msg" 9 70 \
>
>"$options" \
>
> @@ -2183,9 +2185,12 @@ dialog_menu_netdev_edit()
>
>local dr="$( sysrc_get defaultrouter )" err
>
>err=$( ifconfig $interface inet $ipaddr \
>
> netmask $netmask $options 2>&1 )
>
> - if [ $? -eq $SUCCESS -a "$dr" ]; then
>
> -err=$( route add default "$dr" 2>&1 )
>
> -[ $? -eq $SUC
Re: building a port with very long list of build options
> From owner-freebsd-questi...@freebsd.org Thu Apr 21 22:45:24 2011 > Date: Thu, 21 Apr 2011 20:17:31 -0700 > From: Carl > To: freebsd-questions@freebsd.org > Subject: building a port with very long list of build options > > Let's say I want to build a port for which I need to specify a huge > number of build options (eg. ghostscript). In my case I am > cross-compiling on an amd64 host for what will be a NanoBSD i386 target, > but I don't think that's important here. The scenario precludes using > the familiar configuration menu. The problem is that the desired list of > options far exceeds what would be sane to specify on the 'make' command > line. In fact, it apparently even exceeds what typical text editors > tolerate when trying to enter the line in a shell script. What is the > recommended solution? One *can* use a script with an 'insanely long' set of options, by the sinple expedient of using "\" to continue the list on the next line. In fact, when I make a script-file for building something with lots of options, I usually, fore 'readability' put each option on a separate line. e.g.: ./Configure \ --option_001 \ --option_002 \ --option_003 \ --option_003 \ ... ... --option_203 \ making _sure_ there is a blank line after the last option specification. ___ 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: building a port with very long list of build options
On 04/22/2011 10:33 AM, Manolis Kiagias wrote: > On 04/22/2011 10:08 AM, Carl wrote: >>> This form will override the Makefile present in the current directory >>> and will use the specified make file with name your_own_make_file_name . >> make -f your_own_make_file_name >> >> Yes, I did see that, but I interpreted that to mean my make file >> *replaces* the original, in which case I would need to populate my >> make file not only with the list of build options I want but also a >> copy of everything in the original make file. If I'm correct, that >> doesn't seem to me to be a good idea from a maintenance perspective. I >> was hoping for something like the -f option that somehow inserted >> rather than replaced. >> >> Carl / K0802647 > Assuming you have already selected some options during make config, you > could try adding your own to the file /var/db/ports//options > ___ A probably more elegant way is to use the ports-mgmt/portconf port. This allows per port settings to be applied, which are honored by make, portupgrade and the other tools. Just install and use /usr/local/etc/ports.conf to add your options: Here is the sample supplied with the portconf: editors/openoffice.org-2: WITH_CCACHE|LOCALIZED_LANG=it print/ghostscript-* print/lpr-wrapper: A4 sysutils/fusefs-kmod*: !KERNCONF | !NOPORTDOCS www/firefox-i18n: WITHOUT_SWITCHER | FIREFOX_I18N=fr it x11/fakeport: CONFIGURE_ARGS=--with-modules="aaa bbb ccc" ___ 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: Cannot boot from ZFS raidz1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu Apr 21 10:52:49 UTC 2011, Wolfgang Riegler wrote: > I have used this setup guide > (http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1) line by line > with the 8.2-RELEASE DVD for amd64 to install a VirtualBox guest for > testing. > The only difference to the setup guide: I use a SAS controler, so > devicename is da0, da1, da2 instead of ad0, etc. I tried it with a > SATA controler as well, but no differences. > > After reboot, I get the following error from the loader: > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS object directory > Can't find root filesystem - giving up > ZFS: unexpected object set type 0 > ZFS: unexpected object set type 0 > > FreeBSD/x86 boot > Default: zroot:/boot/kernel/kernel > boot: > ZFS: unexpected object set type 0 > > FreeBSD/x86 boot > Default: zroot:/boot/kernel/kernel > boot: I managed to delete your message before I got a chance to send a reply to the list. Against better judgement I'm going to send this reply to the list, knowing that I might create a new thread with the same subject as your OP. A VirtualBox guest will only see one hard drive at the BIOS level during boot. Thus, you should recreate your system using mirrored drives for booting the OS. Once the OS has gained control over the system, ZFS is able to see all the attached disks. Maybe it's not so bad to separate the OS and your data, with the OS stored on a couple of mirrored disks and your precious data stored on three disks in raidz1 formation. This recipe is a good starting point for setting up the OS: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror I prefer using the remaining disk space for the freebsd-zfs partitions and not limiting them to only 60 GiB. HTH, Trond. - -- - -- Trond Endrestøl | trond.endres...@fagskolen.gjovik.no ACM, NAS, NUUG, SAGE, USENIX |FreeBSD 8.2-STABLE & Alpine 2.00 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk2xSxcACgkQbYWZalUoElve+wCfefbLOdr3xY7YyzbiuMfn4SVT cYIAn1tpdOh921kjkThYVwq83sGYHwEG =N8Ei -END PGP SIGNATURE-___ 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: building a port with very long list of build options
On Fri, Apr 22, 2011 at 3:08 AM, Carl wrote: > On 2011-04-21 8:52 PM, Polytropon wrote: > >> This has been possible and common in the past. For example, >> the many options for the mplayer and mencoder ports could >> be specified in a file, so changing of a port's file was >> not needed. I'm not fully sure this option is still present, >> but at least on v7 it worked. >> >> Create a file Makefile.local in the port's directory and >> specify all your options as desired. This file will be >> sourced when you issue a "make" command and will override >> settings of the regular Makefile (e. g. if you want >> different CFLAGS for _this_ port). The file is to be in >> the known syntax, NAME=value. >> > > Does that solution allow for locating Makefile.local outside the ports tree > so as not to contaminate builds for other targets using the same ports tree? > > On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: > >> If you read the make manual page , you will see the following option : >> >> ... >> >> *-f* *makefile* >> Specify a makefile to read instead of the default one. >> >> ... >> >> which is used as >> >> make -f your_own_make_file_name >> >> This form will override the Makefile present in the current directory >> and will use the specified make file with name your_own_make_file_name . >> > > Yes, I did see that, but I interpreted that to mean my make file *replaces* > the original, in which case I would need to populate my make file not only > with the list of build options I want but also a copy of everything in the > original make file. If I'm correct, that doesn't seem to me to be a good > idea from a maintenance perspective. I was hoping for something like the -f > option that somehow inserted rather than replaced. > > Carl / K0802647 > Please study make manual page in detail . There are many more commands to be applicable , for example ( .include ) which you may use to include the original make file name Makefile at any suitable point in your own make file . Also studying the currently used Makefile files in FreeBSD may give many ideas to apply . Thank you very much . Mehmet Erol Sanliturk ___ 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: building a port with very long list of build options
On 22 April 2011 08:08, Carl wrote: > On 2011-04-21 8:52 PM, Polytropon wrote: >> >> This has been possible and common in the past. For example, >> the many options for the mplayer and mencoder ports could >> be specified in a file, so changing of a port's file was >> not needed. I'm not fully sure this option is still present, >> but at least on v7 it worked. >> >> Create a file Makefile.local in the port's directory and >> specify all your options as desired. This file will be >> sourced when you issue a "make" command and will override >> settings of the regular Makefile (e. g. if you want >> different CFLAGS for _this_ port). The file is to be in >> the known syntax, NAME=value. > > Does that solution allow for locating Makefile.local outside the ports tree > so as not to contaminate builds for other targets using the same ports tree? > > On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: >> >> If you read the make manual page , you will see the following option : >> >> ... >> >> *-f* *makefile* >> Specify a makefile to read instead of the default one. >> >> ... >> >> which is used as >> >> make -f your_own_make_file_name >> >> This form will override the Makefile present in the current directory >> and will use the specified make file with name your_own_make_file_name . > > Yes, I did see that, but I interpreted that to mean my make file *replaces* > the original, in which case I would need to populate my make file not only > with the list of build options I want but also a copy of everything in the > original make file. If I'm correct, that doesn't seem to me to be a good > idea from a maintenance perspective. I was hoping for something like the -f > option that somehow inserted rather than replaced. > Or, at the bottom of your Makefile defining variables (including BATCH= yes to skip the OPTIONS dialog), stick the line: .include "Makefile" and use make -f _my_Makefile Chris ___ 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: building a port with very long list of build options
On 04/22/2011 10:08 AM, Carl wrote: > >> >> This form will override the Makefile present in the current directory >> and will use the specified make file with name your_own_make_file_name . > make -f your_own_make_file_name > > Yes, I did see that, but I interpreted that to mean my make file > *replaces* the original, in which case I would need to populate my > make file not only with the list of build options I want but also a > copy of everything in the original make file. If I'm correct, that > doesn't seem to me to be a good idea from a maintenance perspective. I > was hoping for something like the -f option that somehow inserted > rather than replaced. > > Carl / K0802647 Assuming you have already selected some options during make config, you could try adding your own to the file /var/db/ports//options ___ 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: building a port with very long list of build options
On 2011-04-21 8:52 PM, Polytropon wrote: This has been possible and common in the past. For example, the many options for the mplayer and mencoder ports could be specified in a file, so changing of a port's file was not needed. I'm not fully sure this option is still present, but at least on v7 it worked. Create a file Makefile.local in the port's directory and specify all your options as desired. This file will be sourced when you issue a "make" command and will override settings of the regular Makefile (e. g. if you want different CFLAGS for _this_ port). The file is to be in the known syntax, NAME=value. Does that solution allow for locating Makefile.local outside the ports tree so as not to contaminate builds for other targets using the same ports tree? On 2011-04-21 9:11 PM, Mehmet Erol Sanliturk wrote: If you read the make manual page , you will see the following option : ... *-f* *makefile* Specify a makefile to read instead of the default one. ... which is used as make -f your_own_make_file_name This form will override the Makefile present in the current directory and will use the specified make file with name your_own_make_file_name . Yes, I did see that, but I interpreted that to mean my make file *replaces* the original, in which case I would need to populate my make file not only with the list of build options I want but also a copy of everything in the original make file. If I'm correct, that doesn't seem to me to be a good idea from a maintenance perspective. I was hoping for something like the -f option that somehow inserted rather than replaced. Carl / K0802647 ___ 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"
