Re: "make deinstall" within /usr/ports/lang - need to recover default language installs
Dear Chaps, Thank you very much for responding so quickly. Curiously the freeBSD 9.0 was installed with the standard answers to a sysinstall session and did contain a version of perl. I now seem to be in the state of discovering which languages I need and then re-installing. Is there a list/database for freeBSD 9.0 standard sysinstalls languages that I can view and use to re-install (via pkg_add -v -r perl etc) ? [there must a config file for sysinstall to use itself] Kind regards, Rob > lang/ contains all languages and so on ruby, lua, python, perl.. Of > course you removed perl since you typed make deinstall in that parent > port tree. > > You can type make install in /usr/ports/lang/perl5.14 to install it > again. You don't need to reinstall FreeBSD, you're not on Windows > here, you can repair everything :) > > Note: there is no perl installed by default, it's in the ports for few > years now. > > Regards, On 19/03/2013 01:19, Matthew Seaman wrote: > On 19/03/2013 07:54, Rob Navarro wrote: >> Hi Chaps, >> >> I typed "make deinstall" within the /usr/ports/lang directory of a >> FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of >> default compiled languages. >> >> How can I get back to the default FreeBSD default installed language >> state (with Perl installed etc)? > Ummm the default state is with just the base system installed: no > extra languages like perl or python and no other additional software > packages. > >> Crossing my fingers that I need not re-install the OS... > Nope. You absolutely do not need to do that -- all you did will have > affected the ports, which on FreeBSD is a distinct entity from the base > system. > > To recover, you simply need to re-install the appropriate ports. If you > know what you want installed, then it's easy: you can just feed a list > of those ports into portmaster(8) or portupgrade(8). > > If you don't know what you need installed in order to support various > end user programs, then there are various ways of checking that the > dependencies of the required ports are installed. For instance, if > you're using pkgng, you could run 'pkg check -da' At worst, and > requiring the least amount of extra software, just try re-installing the > packages in question. This should work, but you might end up doing a > lot of strictly unnecessary recompiling. > > Matthew > > > > ___ > 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"
"make deinstall" within /usr/ports/lang - need to recover default language installs
Hi Chaps, I typed "make deinstall" within the /usr/ports/lang directory of a FreeBSD 9.0 and mistakenly lost Perl, Python, Ruby and a whole host of default compiled languages. How can I get back to the default FreeBSD default installed language state (with Perl installed etc)? Crossing my fingers that I need not re-install the OS... Kind regards, Rob ___ 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: Strange delays in ZFS scrub or resilver
A bit of a stab in the dark here, but are any of the disks in your array Advanced Format drives? If so, did you create a pool with a block size of 4k? Lastly, are all the partitions on your disks (if any) aligned to 4k sector boundaries (in the case of the Advanced Format disks)? Rob On Feb 23, 2013, at 11:23 PM, John Levine wrote: > I have a raidz of three 1 TB SATA drives, in USB enclosures. One of > the disks went bad, so I replaced it last night and it's been > resilvering ever since. I can watch the activity lights on the disks > and it cranks away for a minute or so, then stops for a minute, then > cranks for a minute, and so forth. If I do a zpool status while it's > stopped, the zpool waits until the I/O resumes, and a ^T shows it > waiting for zio->io_cv. > > I'm running FreeBSD 9.1, amd64 version, totally vanilla install on a > mini-itx box with 4GB of RAM. The root/swap disk is an SSD separate > from the zfs disks. When the disks are active, top shows about 10% > system time and 4% interrupt. When it isn't, top shows about 99.8% > idle. The server isn't doing much else, and nothing else currently > touches the disks. (They're for remote backup of a system somewhere > else, and I have the backup job turned off until resilvering > completes.) > > I'm running this on the console, and there are no disk error messages. > > Any idea what's going on or how to fix it? I could move the disks to > an ESATA enclosure if USB is losing interrupts or something. > > My recollection is that when I've done a scrub, it does the same thing, > work, pause, work, pause. > > R's, > John > ___ > 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: Re[2]: newfs create to little inodes
On Mon, Apr 16, 2012 at 10:02 AM, Robert Bonomi wrote: > > Something about -your- installation is causing you to run out of inodes. > This is a release engineering issue in 9.0, not just his installation. The defaults are screwed up. See bin/162659. -- Rob Farmer ___ 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: Still having trouble with package upgrades
I ran into problems with pkg-upgrade when I upgraded from 8.2p6->9.0-RELEASE, and part of the problem ended up being a tool pkg_upgrade used (uma). That was the reason portupgrade didn't work as well. I ended up hacking the support tool and pkg_upgrade to do what I needed, but they are both definitely broken. iirc, one of the issues with uma was it's url generation. It would generate urls like 9-RELEASE instead of 9.0-RELEASE, the former being the format for 9-STABLE and the later (which I needed) was for an upgrade for a release. Sadly, I've forgotten the other issues, but I remember making about 3 hacks to the tools to get it working. Rob On 3/7/12 11:05 AM, David Jackson wrote: Many of your issues are non-issues, as your suggestions were implemented in some form long ago. For example, updated applications are compiled and available online. You can use "pkg_add -r" to install the newest binary package that is available, or you can update your an installed application by updating the ports and using portupgrade, which has options to control whether you compile updates from source or install binary packages. pkg-add -r does not seem to be an "upgrade all packages" sort of feature I am looking for. I have tried pkg-upgrade, portmaster, and portupgrade, all of these do not work. I am working on getting the logs ___ 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: Querying a cvsup server
On Tue, Feb 7, 2012 at 9:13 AM, Warren Block wrote: > I'm not looking for a specific version of a file, but trying to find out > whether any arbitrary cvsup mirror is current with the main repository. > Not version control, but network monitoring. http://www.mavetju.org/unix/freebsd-mirrors/cvsup-stats-global.php -- Rob Farmer ___ 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: make release custom kernel conf not found
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller wrote: > Thanks Rob... > > I put the kernel conf file in the source tree as opposed to linking to > it and it certainly did compile the custom kernel. > > What confuses me (not that I expect you to have the answer) is that > Chapter 9 of the handbook has a tip that recommends keeping the kernel > config in /root/kernels and symlinking to it from the source tree. If > it doesn't work, why is there a tip recommending this practice? > I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the "right" way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. -- Rob Farmer ___ 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: make release custom kernel conf not found
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller wrote: > Hi All, > > I am performing a `make release` to build a new release with a custom > kernel. The `make release` fails with the following error: > > cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64 > KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL > ERROR: Missing kernel configuration file(s) (MYKERNEL). > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src/release. > + umount /dev > *** Error code 1 > > Stop in /usr/src/release. > > I have the kernel config at /root/kernels/MYKERNEL and > /usr/src/sys/amd64/conf/MYKERNEL is a symlink to the kernel config. > The applicable environment variables are set in my .profile as > follows: > > BUILDNAME=8.2-RELEASE-MYKERNEL-1.1 > CHROOTDIR=/app/release > CVSROOT=/home/cvs > EXTPORTSDIR=/usr/ports > EXTSRCDIR=/usr/src > KERNELS="GENERIC MYKERNEL" > MAKE_DVD=YES > NODOC=YES > NO_FLOPPIES=YES > > I am unsure how to get `make release` to realize the location of the > kernel config. Also, I notice that in the command to make the kernel, > DESTDIR is set to /R/stage/kernels while the CHROOTDIR (and the > location where I want the release to be built) is /app/release. > > I am wondering if someone knows how I may resolve the issue so I can > get the release built. I appreciate any advice and feedback. Thanks. > The kernel is built inside the chroot, so all paths are really /app/release/. Your symlink points to /app/release/root/kernels/MYKERNEL. It will be easiest to get rid of the symlink and copy the actual file into your EXTSRCDIR before starting the make release; alternately you could use the LOCAL_PATCHES or LOCAL_SCRIPT variables to import it. -- Rob Farmer ___ 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"
SSD for ZIL suggestions?
I'm looking at getting a couple of SSDs to act as ZIL drives on FreeBSD 8/9 systems. Are there any recommended drives? Rob ___ 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"
9.0-RELEASE and RealTek (re) watchdog timeout
I'm attempting to transfer a large amount of data from one zfs pool on one system to a zfs pool on another via zfs send/receive. The sender is 8.2 and the receiver is 9.0. The receiver is using a re network driver, and sometime during the transfer all connectivity is lost with the receiver. Looking at the machine, I see: re0: watchdog timeout re0: link state changed to DOWN re0: link state changed to UP every 5-15 seconds in the logs. I've tried disabling MSI/MSI-X, but that didn't have an affect. The only way I've gotten connectivity back was to reboot the machine. Has anyone seen this before? Any ideas? pciconf of the network interface: vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(128) link x1(x1) cap 11[b0] = MSI-X supports 4 messages in map 0x20 enabled cap 03[d0] = VPD ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0002[140] = VC 1 max VC0 ecap 0003[160] = Serial 1 1234567812345678 Rob ___ 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: Revision control advice
On 22 December 2011 15:07, Outback Dingo wrote: > On Wed, Dec 21, 2011 at 10:24 PM, ss griffon wrote: >> On Wed, Dec 21, 2011 at 7:49 PM, Da Rock >> wrote: >>> On 12/22/11 11:37, Chris Hill wrote: >>>> >>>> Hello list, >>>> >>>> I apologize for this posting being not-much-on-topic, but my other >>>> resources have come to naught and I think you folks may have some >>>> experience >>>> in this area. >>>> >>>> I'm looking to set up some sort of revision control system at work. Simple >>>> enough, except that our situation is approximately the reverse of what most >>>> revision control systems are designed for. >>>> >>>> Unlike, e.g., FreeBSD kernel development, we have dozens or hundreds of >>>> small, rapid-fire projects that are created at the rate of 3 to 20 per >>>> month. They last a few days or a few months and are (usually) not developed >>>> afterward. Each project has one to three developers working on it, >>>> sometimes >>>> simultaneously. Usually it's one guy per project. >>>> >>>> Since my programmers are not necessarily UNIX-savvy, I'd like to deploy a >>>> web interface for them which will allow them to create new repositories >>>> (projects) as well as the normal checkin, checkout, etc. I want to set this >>>> up once, and from there on have the programmers deal with managing their >>>> own >>>> repos. And heaven forfend exposing them to the horrors of the shell. >>>> >>>> I've built a test server (9.0-RC3, amd64) for experimenting with this >>>> stuff. So far I've installed and played with: >>>> - fossil. I like the simplicity and light weight, but it doesn't seem to >>>> allow creation of new repos at all (let alone multiple ones) from the web >>>> interface, and the documentation is meager. I've pretty much given up on >>>> it. >>>> - subversion, which looks like the heavy hitter of RCSs, but it's not at >>>> all clear to me how to handle the multiple-project scenario. Still working >>>> on it. >>>> - git looks promising, but I have not installed it yet. >>>> >>>> If anyone can point me to a tool that might be suitable, I would be most >>>> grateful. >>> >>> I'd suggest subversion. It allows individual files to be versioned, you can >>> setup a webdav interface, and there are other tools that can help maintain >>> it. >>> >>> Forget the individual repositories. Setup a single repository and have >>> directories for each project. in each directory you can then setup trunk, >>> branches, whatever, as per best practices in the Book. >>> >>> Designate a person or two to administer, and use directory level auth, or >>> another alternative I haven't thought of. >>> >>> My 2c's anyway. HTH >>> >>> ___ >>> freebsd-questions@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" >> >> Yeah I would second what Mr Rock says. Set up a single repo where >> folders can be used for projects. Since svn lets you checkout sub >> folders of a repo, each developer can check out the folder that >> corresponds to their project. Also, Tortoise svn is a very nice >> graphical utility that will allow your developers to manage there svn >> folders without even needing a web interface (most non unix people >> that I know like tortoise), so there is less maintenance for you :) >> Finally, kudos to moving towards using version control, its an >> important step for a software company. > > git or mercurial - best choices For what reasons? Rob -- Idiot : A member of a large and powerful tribe whose influence in human affairs has always been dominant and controlling. (Ambrose Bierce - The Devils Dictionary) ___ 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: AHCI driver and static device names
and I should expect something to come out of it. In my case, I have not moved the cabling of a disk at all and thus expect the device name to stay the same. All I have done is add a new disk to the controller. I have a reasonable expectation that that action should not re-order the device nodes and screw up god knows what (ALL mounts could break, and the system could even fail to boot). This is how things used to work, and in fact still do work in Linux and other *nix. Or how about those silly BIOSes that assume that you must really want to boot to the new disk you just attached to the machine, so helpfully rearrange your boot order for you so now you're booting to a strange disk with who knows what on it? Honestly, there's so much that can go wrong. That's what sysadmins are for. None of those are related to my point. If a something breaks before I boot the system, that's a whole other issue. I am talking about breaking filesystem mounting by changing an age old methodology. I dislike the idea of having to use labels to get static functionality (increases the likelihood of something going wrong for a disk replace operation if I forget to label), but I'll give gpt labels a try. I find that labels solve more problems than they introduce, when applied properly. The semantic meaning given to the devices often mean I can discover what's on a particular disk in my pile'o'drives just by plugging it in and looking at the kernel log; no mounting necessary. Likewise, when juggling disks or controllers around, I don't have to worry about remembering to update the fstab, since the labels follow the data. If you want to use labels then by all means use them. I can seem advantages to using them. What I'm saying is that it is broken to have to use them in order to fix issues with the ahci driver using dynamic device names. The fact that you have to use them to ensure your system doesn't break horribly when you do something simple like add a disk is a clear indication of a broken design in the ahci driver imho. Rob ___ 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: AHCI driver and static device names
Can glabels, gpt, and zfs all work together? I have a system where I have disks with 4 gpt partitions. Partitions 2 and 3 are part of gmirror arrays, and partition 4 is part of a zfs pool. glabel says it writes to the end of the partition, which I believe zfs also writes to doesn't it? Rob On 12/4/11 4:28 AM, per...@pluto.rain.com wrote: CyberLeo Kitsana wrote: You cannot combine GPT with glabel (or any other geom class that writes data to the first or last 34 sectors of a disk, like gmirror) due to layout conflicts. This is overstated. Since a GPT ordinarily is intended to be booted from, and so must be recognized by the BIOS, it must be written directly on the actual drive -- the "rank 1 provider" in GEOM terms -- because that is the only way for the GPT metadata to be located where the BIOS expects to find it (at both the beginning and the end of the drive). It is, however, possible to combine GPT with gmirror, gjournal, etc. by using GPT partitions, rather than drives, as providers for the other geoms. For example, create a mirror from ad0p1 and ad2p1 rather than from ad0 and ad2. Similarly, it "should" be possible to glabel a GPT partition -- although this seems unlikely to be useful in practice since GPT provides its own labelling scheme. ___ 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: AHCI driver and static device names
On 12/3/11 11:04 AM, CyberLeo Kitsana wrote: To answer your question, though: You cannot combine GPT with glabel (or any other geom class that writes data to the first or last 34 sectors of a disk, like gmirror) due to layout conflicts. MBR and BSD schemes can be used, since they occupy only the first sectors of the device, and their monikers will be appended to the label. Thus, labeling a single-slice MBR disk (/dev/ada0) with 'test' would produce /dev/ada0, /dev/ada0s1, /dev/label/test, and /dev/label/tests1; nesting a BSD table within s1 would add /dev/ada0s1a and /dev/label/tests1a as well. Do gpt labels work the same as glabel, ie provide a static device name that can be acted upon with /etc/fstab, zfs, gmirror, etc? The other option seems to be to use tunefs or a partitioning tool to label each partition, which is even more ugly imo. Ugly how? Labels appear a lot more semantically elegant than the opaque 'ada4s1a' moniker. Ugly in that the driver has created a situation where we need workarounds to perform the tasks we need. *nix systems have always relied upon static device nodes, and using dynamic names without updating the relating tools/methods is ugly. The workarounds also could fail if someone forgets to perform them (specifically labels), since it's not necessary on just about any other *nix system. It's perfectly within reason to assume people will forget to apply a label when replacing a disk. Case in point. I have a system with 15 drives in it. I decided I wanted to install on the 2nd device instead of the 1st, but I partitioned all the other 14 drives. I completed installation and when to boot the system and it failed. Stupid me, the GPT boot loader found disk1 with a partitioning scheme but no fs. So, I popped out disk 1 and when to boot again. Hey, now it starts to boot only to fail to find the root fs because it's looking on ada1 and the fs is on ada0. That is a mess. This is not necessarily common, but also not uncommon. More likely is the case where you add a drive to the system and the above scenario plays out because the device names get re-ordered. I'm not sure the problem the dynamic device nodes intends to solve, but it's certainly caused all sorts of pain and the need for the 2 (that I know of) workarounds. I dislike the idea of having to use labels to get static functionality (increases the likelihood of something going wrong for a disk replace operation if I forget to label), but I'll give gpt labels a try. Rob ___ 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: AHCI driver and static device names
Is there a loader.conf entry to enable the static ids, or will the ahci driver always use static ids if "options ATA_STATIC_ID" is in the kernel config? I desire to use stock kernels and the 9-rc2 boot iso seems to not have ATA_STATID_ID set (unless there's a loader.conf value to enable the functionality) Rob On 12/3/11 3:44 AM, Denise H. G. wrote: On 2011/12/03 at 10:51, Rob wrote: I was getting ready to install the latest FreeBSD 9-RCs image, and I found that 9 now defaults to using the ahci driver for sata disks. This would be great if it weren't for the fact that the ahci driver seems to do dynamic device name assignment as opposed to the static ones used with the older drivers. I've looked around on google and while this is mentioned (in old threads), the "solution" is to use labels or elaborate mapping via hints which really aren't solutions imo. If I have 15 disks in an array, I want to be able to label them and know which bay is which device name. If I have to replace a drive, I have no idea what dynamic device name it will have when it comes time to partition (and label, if I were using that). I could probably figure it out by looking at what disks are used on the system, but that's more work that it really should be. It seems AHCI driver uses static naming policies if you have 'options ATA_STATIC_ID' in your kernel configuration. Anyway, I just have one SATA disk, which the system recognizes as 'ada4'. I don't know whether this will apply in your case. Is there a way to use the ahci driver and get static device names? Rob ___ 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: AHCI driver and static device names
glabel looks to place a label on the whole disk, but the manpage is unclear (to me) how the partitions are handled. If I use glabel to label a disk "test" and this disk has 4 partitions on it, then how is each partition accessed? testp1...testp4 for gpt? The other option seems to be to use tunefs or a partitioning tool to label each partition, which is even more ugly imo. Rob On 12/2/11 9:27 PM, Derrick Ryalls wrote: Look for disk labels, I think glabel is the command. Then you use /dev/label/mylabel etc for the disks. Let me know if this isn't enough to find the right man page or spot in the handbook. I use it in my raid array but am running short on time right now. On Fri, Dec 2, 2011 at 6:51 PM, Rob mailto:li...@midsummerdream.org>> wrote: I was getting ready to install the latest FreeBSD 9-RCs image, and I found that 9 now defaults to using the ahci driver for sata disks. This would be great if it weren't for the fact that the ahci driver seems to do dynamic device name assignment as opposed to the static ones used with the older drivers. I've looked around on google and while this is mentioned (in old threads), the "solution" is to use labels or elaborate mapping via hints which really aren't solutions imo. If I have 15 disks in an array, I want to be able to label them and know which bay is which device name. If I have to replace a drive, I have no idea what dynamic device name it will have when it comes time to partition (and label, if I were using that). I could probably figure it out by looking at what disks are used on the system, but that's more work that it really should be. Is there a way to use the ahci driver and get static device names? Rob _ freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org> mailing list http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions <http://lists.freebsd.org/mailman/listinfo/freebsd-questions> To unsubscribe, send any mail to "freebsd-questions-__unsubscr...@freebsd.org <mailto: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"
AHCI driver and static device names
I was getting ready to install the latest FreeBSD 9-RCs image, and I found that 9 now defaults to using the ahci driver for sata disks. This would be great if it weren't for the fact that the ahci driver seems to do dynamic device name assignment as opposed to the static ones used with the older drivers. I've looked around on google and while this is mentioned (in old threads), the "solution" is to use labels or elaborate mapping via hints which really aren't solutions imo. If I have 15 disks in an array, I want to be able to label them and know which bay is which device name. If I have to replace a drive, I have no idea what dynamic device name it will have when it comes time to partition (and label, if I were using that). I could probably figure it out by looking at what disks are used on the system, but that's more work that it really should be. Is there a way to use the ahci driver and get static device names? Rob ___ 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"
wireless help with wep authentication
Running fbsd 8.2R on a Dell C640 laptop. Using a pcmcia card with atheros. My 2wire wireless router comes setup default with wep open with wireless security enabled, i.e., needs the default passkey from the router. I cannot get the ifconfig line correct so as to authenticate this way, and have tried many different strings of text here. However, following the handbook, I turned off "enable security" (on the 2wire router) to test things, hence, using wep (not as authmode shared or authmode open) and it works using the following in /etc/rc.conf: wlans_ath0="wlan0" ifconfig_wlan0="ssid Mynetname DHCP" Mynetname is different -- of course. I can browse the web and ping with 0% packet loss. I have not delved into using a /etc/wpa_supplicant.conf yet, I was hoping i could get it done in rc.conf with ifconfig. I have tried many many things, for days on end for authenticating with the passkey from the router. Any help appreciated, I can provide further info and things I've tried -- most things in the handbook wireless section, minus wpa_supplicant.conf. Thanks In Advance, Rob ___ 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"
AMD 850/950 support?
Anyone know if FreeBSD 8.2 supports the AMD 850 and/or 950 southbridge? I've been looking on the web without much luck (unusual) and the hardware docs for the release for the ata driver only mentions 5 amd chipsets. Is there perhaps a different chipset I should be looking for to determine ata support for those southbridges? Rob ___ 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"
SATA SDD cards
Has anyone tried using an SATA SSD card (SATA add-on card that is a SSD drive) in FreeBSD? I was looking at an OCZ RevoDrive and was wondering if anyone had tried using one of those specifically, or any SATA SSD card in general. Rob ___ 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: Virtualbox on 8.2 64-bit (cont)
On 6/14/11 4:52 PM, Mario Lobo wrote: Also, do you know the difference between pre-built packages on the freebsd ftp server in packages-8.2-release vs packages-8-stable? Well, IF you installed the source tree from the SAME cd which you installed the FreeBSD you have now, there won't be any problems. You said you want to keep the stock kernel you installed so I assume that you haven't updated anything from the internet. You MUST install the source tree from the same DVD/CD from where you installed your running kernel! The diference is that the packages are meant to run on their respective version. I believe that packages that don't rely on a specific thing of one version should run without problems on both. But this is not normal or even needed at all, specially because it is so easy to bring everything uptodate to the same version. I installed from an 8.2 boot only CD (ie network install) and have since patched up to 8.2-p2. I assume I can just run sysinstall from my system and pull the src tree from the ftp server? When 8.3 comes out, what do I need to do to update the src tree? This may be documented in the UPDATING docs, but having never messed with the source tree I haven't had cause to look. If so just tell me to go read the respective doc. :) Rob ___ 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: Virtualbox on 8.2 64-bit (cont)
On 6/14/11 8:06 AM, Ondrej Majerech wrote: On 06/09/2011 15:49, Rob wrote: On 6/6/11 8:39 PM, Mario Lobo wrote: You need to rebuild your kernel with options COMPAT_FREEBSD32 # Compatible with i386 binaries included. I noticed that when I tried to build the ports, but I don't have anything in /usr/src and no information was given as to what packages/src I needed to install. I'd like to avoid diverging from the stock release kernel for upgrade simplicity. What exactly does that do? Will it introduce upgrade complexity (ie will I have to upgrade these libs before I upgrade the kernel or some such)? Needless to say, that option seems to be enabled in GENERIC: [starlight] ~ > grep COMPAT_FREEBSD32 /usr/src/sys/amd64/conf/GENERIC options COMPAT_FREEBSD32 # Compatible with i386 binaries Also I don't remember having to issue make build32 install32 or anything of that sort. You do need to have the FreeBSD source tree installed on your system, though. Did you try just fetching the source tree without building from it and then trying to build VirtualBox again? ~ Ondra Is there a pkg_add command for installing the source tree, or should I just use sysinstall? Rob ___ 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: Virtualbox on 8.2 64-bit (cont)
On 6/9/11 4:55 PM, Mario Lobo wrote: On Thursday 09 June 2011 10:49:37 Rob wrote: On 6/6/11 8:39 PM, Mario Lobo wrote: On Monday 06 June 2011 17:56:53 Rob wrote: I was attempting to install virtualbox on my 8.2-p2 64-bit system this weekend, and hit a rather curious situation. The pre-packaged version of virtualbox retrievable by pkg_add is 3.2.12 (which looks in ports/amd64/packages-8.2-release). Poking around on the ftp server, I see that packages-8.1-release also has a 3.x version, but packages-8-stable has the latest 4.0.8. I went to look in ports, which contains 4.0.8, and build it myself but I got an error saying I need to have the 32-bit libraries installed in order to build virtualbox. So, my question is 2-fold: 1) What is the reason the 64-bit pre-packaged version of virtualbox is still at the 3.x version? Would there be a problem with installing the packages (virtualbox and kernel module) from packages-8-stable? 2) How do I build virtualbox 4.0.8 on a 64-bit system w/o the 32-bit libs. Is that possible? Searching around has produced old e-mail threads indicating this was a problem as of 2 or so years ago with the 3.x release. If it's not possible to build w/o the 32-bit libs, what do I need to install? Rob You need to rebuild your kernel with options COMPAT_FREEBSD32# Compatible with i386 binaries included. And as per the port's error message: cd /usr/src; make build32 install32; /etc/rc.d/ldconfig restart I noticed that when I tried to build the ports, but I don't have anything in /usr/src and no information was given as to what packages/src I needed to install. I'd like to avoid diverging from the stock release kernel for upgrade simplicity. What exactly does that do? Will it introduce upgrade complexity (ie will I have to upgrade these libs before I upgrade the kernel or some such)? Rob To remain with the same kernel you installed, you must install the source tree from the same CD/DVD you used for installation. You will have to run sysinstal and go to Configure Do post-install configuration of FreeBSD then Distributions Install additional distribution sets then mark [ ] src Sources for everything Choose the CDROM as installation media. After that you'll have all the sources on your HD and can proceed to the compilation of the 32 libs. If the sources are from the same CD you installed the system, they will be in sync with your kernel. No upgrade issues. What is that command doing though? It's building what from src? What is the output of build32? I assume it's not a kernel. Also, do you know the difference between pre-built packages on the freebsd ftp server in packages-8.2-release vs packages-8-stable? Rob ___ 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: Virtualbox on 8.2 64-bit (cont)
On 6/6/11 8:39 PM, Mario Lobo wrote: On Monday 06 June 2011 17:56:53 Rob wrote: I was attempting to install virtualbox on my 8.2-p2 64-bit system this weekend, and hit a rather curious situation. The pre-packaged version of virtualbox retrievable by pkg_add is 3.2.12 (which looks in ports/amd64/packages-8.2-release). Poking around on the ftp server, I see that packages-8.1-release also has a 3.x version, but packages-8-stable has the latest 4.0.8. I went to look in ports, which contains 4.0.8, and build it myself but I got an error saying I need to have the 32-bit libraries installed in order to build virtualbox. So, my question is 2-fold: 1) What is the reason the 64-bit pre-packaged version of virtualbox is still at the 3.x version? Would there be a problem with installing the packages (virtualbox and kernel module) from packages-8-stable? 2) How do I build virtualbox 4.0.8 on a 64-bit system w/o the 32-bit libs. Is that possible? Searching around has produced old e-mail threads indicating this was a problem as of 2 or so years ago with the 3.x release. If it's not possible to build w/o the 32-bit libs, what do I need to install? Rob You need to rebuild your kernel with options COMPAT_FREEBSD32# Compatible with i386 binaries included. And as per the port's error message: cd /usr/src; make build32 install32; /etc/rc.d/ldconfig restart I noticed that when I tried to build the ports, but I don't have anything in /usr/src and no information was given as to what packages/src I needed to install. I'd like to avoid diverging from the stock release kernel for upgrade simplicity. What exactly does that do? Will it introduce upgrade complexity (ie will I have to upgrade these libs before I upgrade the kernel or some such)? Rob ___ 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: Virtualbox on 8.2 64-bit
On 6/6/11 8:13 PM, Mario Lobo wrote: On Monday 06 June 2011 17:56:53 Rob wrote: I was attempting to install virtualbox on my 8.2-p2 64-bit system this weekend, and hit a rather curious situation. The pre-packaged version of virtualbox retrievable by pkg_add is 3.2.12 (which looks in ports/amd64/packages-8.2-release). Poking around on the ftp server, I see that packages-8.1-release also has a 3.x version, but packages-8-stable has the latest 4.0.8. I went to look in ports, which contains 4.0.8, and build it myself but I got an error saying I need to have the 32-bit libraries installed in order to build virtualbox. So, my question is 2-fold: 1) What is the reason the 64-bit pre-packaged version of virtualbox is still at the 3.x version? Would there be a problem with installing the packages (virtualbox and kernel module) from packages-8-stable? 2) How do I build virtualbox 4.0.8 on a 64-bit system w/o the 32-bit libs. Is that possible? Searching around has produced old e-mail threads indicating this was a problem as of 2 or so years ago with the 3.x release. If it's not possible to build w/o the 32-bit libs, what do I need to install? Rob You need to rebuild your kernel with options COMPAT_FREEBSD32# Compatible with i386 binaries included. I'm running the stock 8.2 kernel. Is that option compiled into the kernel? Where do I find the options that are enabled in the stock kernel? Also, does COMPAT_FREEBSD32 mean I don't need the 32-bit libs for compilation, or that the kernel will run binaries compiled for 32-bit systems? If the later, then I'll still need to install the 32-bit version of the libraries in order to build, right? Rob ___ 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"
Virtualbox on 8.2 64-bit
I was attempting to install virtualbox on my 8.2-p2 64-bit system this weekend, and hit a rather curious situation. The pre-packaged version of virtualbox retrievable by pkg_add is 3.2.12 (which looks in ports/amd64/packages-8.2-release). Poking around on the ftp server, I see that packages-8.1-release also has a 3.x version, but packages-8-stable has the latest 4.0.8. I went to look in ports, which contains 4.0.8, and build it myself but I got an error saying I need to have the 32-bit libraries installed in order to build virtualbox. So, my question is 2-fold: 1) What is the reason the 64-bit pre-packaged version of virtualbox is still at the 3.x version? Would there be a problem with installing the packages (virtualbox and kernel module) from packages-8-stable? 2) How do I build virtualbox 4.0.8 on a 64-bit system w/o the 32-bit libs. Is that possible? Searching around has produced old e-mail threads indicating this was a problem as of 2 or so years ago with the 3.x release. If it's not possible to build w/o the 32-bit libs, what do I need to install? Rob ___ 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: SATA Host Adapter Recommendation
I have a Highpoint 4-port PCI-E 4x card in a server that has worked well for a few years. It's a bit pricey, but I've had no problems with it. Recently, I've gotten 3 Rosewill RC-218 cards because they're much cheaper and I don't need the RAID functionality on other cards. I'm building servers with them now, but FreeBSD recognizes the disks attached to them fine (so long as your on >= 8.2 and you add hw.hptrr.attach_generic=0 in /boot/loader.conf). I haven't tried hot-swapping any drives yet, but I'm assuming since it's SATA it should work fine. I should probably verify that soon. Rob On 5/21/11 9:26 PM, Jason C. Wells wrote: I am looking to get 2 sata host adapters. The mandatory requirements are good freebsd support and hot swap capability. I plan to use gmirror. I have discovered that my onboard chipsets don't support hot swap. The highpoint cards are rated highly on newegg. Are these good with freebsd? Thanks, Jason C. Wells ___ 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"
No keyboard after ports update, 2x moused_enable="YES" culprit
System Info: 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Tue Aug 10 11:43:36 EDT 2010, and xorg-server-1.7.7_1,1 X.Org X server and related programs Not having updated my ports in nearly 1 year, I did a sledgehammer approach with portmaster as follows: portmaster -D -R -f -m BATCH=yes -a This took a few rounds. I did this as I started having all sorts of issues after running down various port problems when going through a rather long /usr/ports/UPDATING. Maybe not the best method, but I think everything is finally done. After restarting X, prior to any reboot, I lost the mouse in X. So I figured a reboot was in order. Issue: After a reboot I found I had no keyboard -- not even in console mode. Trying the obvious first, I unplugged the keyboard and plugged it back in the ps2 port, and keyboard worked immediately -- this was repeatable. Reboot, same thing, no keyboard. Some digging around revealed that I had the following line in /etc/rc.conf twice: moused_enable="YES" I removed one of these (which I guess was the culprit) and left one as it should have been, then all was well. Keyboard found at reboot, no further issues -- mouse was available in X too. I have no idea why I had moused_enable="YES" in there twice, whether it was from an old or recent rc.conf edit, but it clearly seems to have been causing the issue. Other (maybe valuable) info: I am running hald in /etc/rc.conf as follows: dbus_enable="YES" hald_enable="YES" ...and these were there prior to the ports update. I figured this "issue" may be of some value since I did not do any src updates. I'll be glad to try to help or test this further, but keep in mind I'm not a coder. Thanks, Rob ___ 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: post-installation of CDDL files
On Sat, Mar 12, 2011 at 4:05 PM, Alexander Best wrote: > hi there, > > my current world does not include any CDDL files, because i had WITHOUT_CDDL > in my src.conf. > > now i'd like to build world with CDDL files (in order to use dtrace). what are > the necessary steps for doing so? > > i've removed the WITHOUT_CDDL part from my src.conf, but targets buildworld > and > toolchain both fail: > > make: don't know how to make /usr/lib/libctf.a. Stop > > cheers. > alex > > -- > a13x > ___ > 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" > Install it manually. Go to src/cddl/lib/libctf and make obj make depends make make install Then buildworld will work. -- Rob Farmer ___ 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: Coldfusion, Postgres and Java under FreeBSD
On Mon, Mar 7, 2011 at 11:36 PM, n j wrote: > openjdk-7.0.122_1 > Java Development Kit 7 > Long description : Sources : Changes : Download > > vs. > > openoffice.org-2.1.0 > Integrated wordprocessor/dbase/spreadsheet/drawing/chart/browser > Long description | Package | Sources | Main Web Site > > In any way, I stand corrected. I should probably start testdriving > OpenJDK to see if it can successfully replace diablo-jdk. > I would recommend openjdk6 unless you have a specific need for 7. It is getting a lot more attention (for example, the web plugin from IcedTea is available in 6). -- Rob Farmer ___ 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: setting up svn server - Connection refused
On Fri, Feb 25, 2011 at 1:23 AM, Anton Shterenlikht wrote: > I'm learning how to set up svn server. > I've read through several sections of > http://svnbook.red-bean.com/nightly/en/ > > Here's what I do: > > ZEEV> svnadmin create /home/mexas/zzz > ZEEV> svnlook info zzz > > 2011-02-25 09:15:28 + (Fri, 25 Feb 2011) > 0 > ZEEV> svnserve -d > ZEEV> ps ax | grep svnserve > 66952 ?? Ss 0:00.01 /usr/local/bin/svnserve.bin -d > ZEEV> mkdir /home/mexas/zzz.work > ZEEV> cd /home/mexas/zzz.work/ > > When I try to connect to the svn server, I get this: > > > ZEEV> svn co svn://localhost/home/mexas/zzz . > svn: Can't connect to host 'localhost': Network is unreachable > ZEEV> svn co svn://10.10.10.14/home/mexas/zzz . > svn: Can't connect to host '10.10.10.14': Connection refused > > ZEEV> ifconfig em1 > em1: flags=8843 metric 0 mtu 1500 > > options=209b > ether 00:13:21:5b:05:1d > inet 10.10.10.14 netmask 0xff00 broadcast 10.10.10.255 > inet6 fe80::213:21ff:fe5b:51d%em1 prefixlen 64 scopeid 0x5 > nd6 options=29 > media: Ethernet autoselect (100baseTX ) > status: active > ZEEV> > > I get exactly the same "Connection refused" if I > connect from another host. > > I turned the firewall off completely. > > What could be the problems? >From the rc script (which would probably be better than starting it manually): # Note: # svnserve bind per default at the ipv6 address! # If you want svnserve binding at ipv4 address, you have # to use option 'svnserve_flags' with --listen-host parameter Have you tried something like this in rc.conf: svnserve_flags="-d --listen-port=3690 --listen-host 1.2.3.4" Also check the other variables in that file - you need to specify where the repo is (-r), the user to run as, etc. svn+ssh avoids all of this because there is no sever - it just executes svn in the user's ssh session and manipulate the repo's files directly (this allows users to accidentally or intentionally trash up the repo, so svnserve is safer if you don't fully trust all your committers. Plus you have to watch for permission and umask issues with svn+ssh). -- Rob Farmer ___ 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: Backtick versus $()
On Thu, Feb 24, 2011 at 5:06 PM, Andres Perera wrote: > On Thu, Feb 24, 2011 at 8:30 PM, Chip Camden > wrote: >> >> -- >> Sterling (Chip) Camden | sterl...@camdensoftware.com | 2048D/3A978E4F >> http://chipsquips.com | http://camdensoftware.com | http://chipstips.com >> > > btw, would you stop putting ads on your signature? it's annoying > LOL - how hypocritical. This thread was four days dead then suddenly two people show up and start pushing this mksh shell, which seems to be part of some obscure OpenBSD fork. If anyone is "advertising" it's you. -- Rob Farmer ___ 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: Backtick versus $()
On Thu, Feb 24, 2011 at 1:05 PM, Thorsten Glaser wrote: > Rob Farmer predatorlabs.net> writes: > >> Have you used the default FreeBSD shell (tcsh) recently? > > tcsh is not a shell. Well, it’s an interactive command line > interpreter, not a bad one compared to what else is offered > at that, but… > (New) people will still copy and paste commands into an interactive tcsh, so it is a good idea to be compatible when posting stuff to the mailing lists, etc. if possible. There was something on the ports@ list a while back, about PRs for new ports, where this came up. > http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/ > I've read it before. Who hasn't? And I find it unconvincing, since it is just a list of shortcomings. If those shortcomings don't affect me, why do I care? -- Rob Farmer ___ 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: Backtick versus $()
On Thu, Feb 24, 2011 at 12:51 PM, Thorsten Glaser wrote: > Andres Perera zoho.com> writes: > >> "mandated by posix" and reality usually aren't in sync, as i'm sure you know > by > > In this case, closely enough. > >> now since you pointed out solaris > > It’s just /bin/sh on long outdated versions (newer ones, both > from Horracle and not, have AT&T ksh93 there instead). No need > to use it, anyway. sh scripts can usually depend on a POSIX > shell (and it’s sensible to do so). Some operating environments > have guaranteed that (MirBSD even guarantees mksh but Debian > Policy §10.4 explicitly states POSIX plus a few extensions). > > And AFAIK all FreeBSD® shells have it. Have you used the default FreeBSD shell (tcsh) recently? [rfarmer@sapphire] ~> echo $(date ) Illegal variable name. [rfarmer@sapphire] ~> echo `date` Thu Feb 24 12:59:00 PST 2011 [rfarmer@sapphire] ~> uname -a FreeBSD sapphire.predatorlabs.net 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r218838: Sat Feb 19 03:39:34 PST 2011 rfar...@sapphire.predatorlabs.net:/usr/obj/usr/src/sys/SAPPHIRE amd64 And I read the article you posted - basically it seemed to say "some keyboards are screwed up, so rather than fix them would everyone stop using this character please." I have a good feeling what the success rate of that will be. -- Rob Farmer ___ 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: HAL's demise
On Thu, Feb 24, 2011 at 11:34 AM, Edwin L. Culp W. wrote: > Sounded like a good idea to me but ;) > > pkg_deinstall hal-0.5.14_12 > ---> Deinstalling 'hal-0.5.14_12' > pkg_delete: package 'hal-0.5.14_12' is required by these other packages That list is recursive - kdelibs4 depends on hal, then other stuff depends on it. If it could be configured to work without hal, most likely the rest of the list would be just fine. -- Rob Farmer ___ 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: Run your own portsnap mirror?
On Wed, Feb 9, 2011 at 2:56 PM, patrick wrote: > Is there any official way to run a private portsnap mirror? ie. Have > one, external server fetch from the official portsnap sources, and > then internal servers pulling from the private mirror? > ___ > 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" > http://www.freebsd.org/cgi/cvsweb.cgi/projects/portsnap/ There is a note explaining why this might not be a good idea, though. -- Rob Farmer ___ 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: shutdown computer after the halt command
On Mon, Feb 7, 2011 at 7:31 PM, John R. Levine wrote: >> It's quite easy to see you're wrong, just follow the steps I outlined >> above. If you are correct, reboot(8) should print things like: >> >> Stopping sshd. >> >> to the console. > > Sigh. I shut down my FreeBSD 8.1 laptop all the time with halt -p, and I > can assure you it prints all those messages. > Well, that's not what everyone else sees. >> You can also reference init.c if you still think you're correct. > > No thanks, I've already read the man page for init, including this > paragraph: > That man page hasn't been more than minorly tweaked in over 10 years, according to cvsweb. > Perhaps your copy of FreeBSD was installed incorrectly, or it's been > so long since you tried halt or reboot that you forgot what happened. > Just did - it kills all process and moves to the syncing disks stage. Nothing rc related is touched. -- Rob Farmer ___ 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: 8.2 prerelease, virtualbox, and windows guests that freeze...
On Sun, Feb 6, 2011 at 7:03 PM, Chris Brennan wrote: > Net, I've formatted drives as fat32 that were well over 4gb. In fact I have > an external 120gb we datavault that's fat32 > Max per file, not the whole partition. Virtual machines generally store the whole disk as a single file, though Vmware has an option to split it up for these situations. -- Rob Farmer ___ 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: manual page formatting issues
Yep, that was it. Thanks very much Yuri. On Sat, Feb 5, 2011 at 3:07 PM, Yuri Pankov wrote: > On Sat, Feb 05, 2011 at 02:24:31PM +1000, Rob wrote: > > Hi, > > > > I'm running FreeBSD 8.1-RELEASE (running on VMWare Server 2.0.2) and am > > having some odd issues the formatting of man pages. > > > > If I view a man page (as root) in the console it displays correctly. If I > > view the man page (again, as root) in a (PuTTY) terminal session, the > bold > > formatting of the command line arguments is missing. > > > > See the following screen shot examples: > > > > Console: http://imageupload.org/?di=612968791464 > > > > Terminal: http://imageupload.org/?di=112968791464 > > > > In the console session I have the TERM=cons25. > > > > In the terminal session I have it set to TERM=xterm. My PuTTY settings > are > > pretty much the default, including the "Connection->Data->Terminal-type > > string" set to xterm. > > > > The pager in both sessions is set to more. > > > > I've played around with various terminal settings, to no avail. Can > someone > > please offer some pointers as to how I might fix this? > > > > Thanks, > > Rob > > You probably forgot to change Window->Colors->Default Bold Foreground > color values in PuTTY (works just fine here). > > > HTH, > Yuri > ___ 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"
manual page formatting issues
Hi, I'm running FreeBSD 8.1-RELEASE (running on VMWare Server 2.0.2) and am having some odd issues the formatting of man pages. If I view a man page (as root) in the console it displays correctly. If I view the man page (again, as root) in a (PuTTY) terminal session, the bold formatting of the command line arguments is missing. See the following screen shot examples: Console: http://imageupload.org/?di=612968791464 Terminal: http://imageupload.org/?di=112968791464 In the console session I have the TERM=cons25. In the terminal session I have it set to TERM=xterm. My PuTTY settings are pretty much the default, including the "Connection->Data->Terminal-type string" set to xterm. The pager in both sessions is set to more. I've played around with various terminal settings, to no avail. Can someone please offer some pointers as to how I might fix this? Thanks, Rob ___ 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: Opening Opera as user
On Tue, Feb 1, 2011 at 9:47 PM, Rem P Roberti wrote: > That's interesting. The problem is that there is no /root/.opera folder. > As a matter of fact there doesn't seem to be any folders at all that refer > to the linux-opera browser, in my /home/user directory, or anywhere else. > So I have no idea where the program is storing the profile info. > > Rem > I think /usr/local/bin/opera is a shell script that sets a couple environment variables and starts the real binary, so maybe you could open it and see if there are any clues. Otherwise, I have no other idea. Sorry :( -- Rob Farmer ___ 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: Opening Opera as user
On Tue, Feb 1, 2011 at 6:17 PM, Rem P Roberti wrote: > I installed linux-opera, and I guess I made a mistake by opening it the > first time as root, when I should have opened as user. At any rate, I can > now only open the browser as root, and when I do I get this message: > > opera: $HOME set to /root. Use -personaldir if you do not want to use > /root/.opera/ > > Can someone give me a heads up on how to fix this, as the above message is a > mystery to me. > Most likely, it is trying to use /root/.opera for your profile and is crashing early in the startup because the regular user can't write there. I would save any bookmarks or other useful items and then delete the folder. I haven't run into this in FreeBSD but you can get similar problems in Windows if a global profile is created in C:\Program Files\Opera by an administrator. -- Rob Farmer ___ 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: Can't install - Octave, SuiteSparse
On Thu, Jan 27, 2011 at 15:25, Gerald Pfeifer wrote: > Sorry, I just realized I totally missed this question. Are you > still seeing the problem? > > Looking at the web archive of this thread, I do not see anything > stand out. What happens if you remove gcc-4.4.6.20101012 and try > to build everything with GCC 4.5? > > It may be worthwhile doing a 'portupgrade -a' or similar and rebuild > all ports with one and the same compiler before trying again. > > Gerald > IIRC, there was a problematic version of gcc45 somewhere in that time period but it was corrected next time the port was updated. I would suggest the reporter try again with a recent version - I suspect it will work fine. -- Rob Farmer ___ 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: Should I use the standard-supfile or stable-supfile?
On Thu, Jan 20, 2011 at 15:42, Ed Flecko wrote: > Thank you Nerius! > > Would it be smart to run this daily via cron? > > Ed > ___ > 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" > No, the errata branches are only updated once every couple months (on average) - that's overkill. Just subscribe to the announce list - there will be a message whenever an update is issued: http://lists.freebsd.org/mailman/listinfo/freebsd-announce -- Rob Farmer ___ 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: use of menus crashes Firefox?
On Thu, Jan 20, 2011 at 16:43, Keith Seyffarth wrote: >> Doing a "bt" would have been helpful right about there, but I think I've got >> enough info to suggest rebuilding your kernel with the following option: >> >> options P1003_1B_SEMAPHORES > > thanks again, Chuck. > > I can easily get the bt if needed, but I looked into rebuilding the > kernel. It looks like I need to first update the source tree. I think I > can see how to do that with cvsup, but if I do that, am I going to be > trying to build an 8.3 kernel to run in a 7.2 environment? I suspect > that would not have the desired end result of a running computer... > > Or should I just build the kernel with what's currently in /usr/src? > So have you tried this? == Firefox 3.6 and HTML5 Certain functions used to display HTML5 elements need the sem module. If your Firefox crashes with the following message while viewing a HTML5 page: "Bad system call (core dumped)" you need to load the sem module (kldload sem). To load sem on every boot put the following into your /boot/loader.conf: sem_load="YES" == -- Rob Farmer ___ 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: use of menus crashes Firefox?
On Tue, Jan 18, 2011 at 18:53, Keith Seyffarth wrote: > > Chuck Swiger writes: > >> On Jan 18, 2011, at 6:01 PM, Keith Seyffarth wrote: >>> $ gdb --exec=firefox3 >>> This GDB was configured as >>> "i386-marcel-freebsd"."/usr/local/bin/firefox3": not in executable >>> format: File format not recognized >> >> What does "file /usr/local/bin/firefox3" say? > > $ file /usr/local/bin/firefox3 > /usr/local/bin/firefox3: Bourne shell script text executable > Right - firefox3 is a script that sets up a couple environment variables and runs the real binary. You need to gdb the real binary (which is in /usr/local/lib/firefox or somesuch - its not in any remotely normal $PATH). Since the environment stuff the script does is required for it to start, temporarily editing the script and running firefox3 is probably the easiest thing to do. -- Rob Farmer ___ 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 build a BROKEN port?
On Wed, Dec 29, 2010 at 17:42, Charlie Kester wrote: > Most of the time, possessives are formed with apostrophe+s. I'm not > sure, but "its" might be the only exception to the rule. So I tend to be > more forgiving when people get it wrong -- especially when English is > not their native tongue. > It is not an exception - just the only one that's confusing. Apostrophes for possessives only applies to nouns, not pronouns (its, hers, yours, etc.). "It's" recieves an apostrophe because it is a contraction, like "that's." Supposedly, English has a lot more homonyms than other languages. -- Rob Farmer ___ 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: SD/CF card reader
On Mon, Dec 27, 2010 at 16:26, Polytropon wrote: > On Sun, 26 Dec 2010 19:35:20 -0600, Adam Vande More > wrote: >> > GEOM: da1: partition 1 does not start on a track boundary. >> > GEOM: da1: partition 1 does not end on a track boundary. >> > GEOM: da1: partition 1 does not start on a track boundary. >> > GEOM: da1: partition 1 does not end on a track boundary. >> >> >> Yeah I don't know about that. I think it's just a warning but maybe trying >> using FreeBSD zero out device, partition(slice) and newfs_msdos it. > > Those messages seem to be uncritical as I've tried to access > various media - without any problems. Those cards work well > on my v7 system (where those messages aren't shown). I just > continue as if those messages haven't been issued. > They are useless and have been removed from current recently (large discussion of the details): http://lists.freebsd.org/pipermail/svn-src-head/2010-December/023131.html Even Windows doesn't bother with the alignment in recent versions. -- Rob Farmer ___ 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: java
On Sun, Dec 26, 2010 at 16:59, xinyou yan wrote: > $javac helloworld.java //No problem > $java helloworld.class It should be "java helloworld" (no extension). -- Rob Farmer ___ 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: Portupgrade status [Was Re: Portmaster general questions and problems]
On Sun, Dec 26, 2010 at 13:42, Bob Hall wrote: > On Sun, Dec 26, 2010 at 11:39:58AM -0800, Ron (Lists) wrote: >> But, due to portupgrade no longer being maintained and failing to work >> anymore, > > I'm a bit confused about this. I did a quick google search and saw that > someone had stopped maintaining portupgrade, but I also saw things that > suggested that other people were maintaining it. The handbook continues > to list it ahead of portmanager and portmaster, with no mention that it > isn't being maintained. I've never stopped using portupgrade, and it has > always worked. Updates come through periodically, two in the past month. > For a port that isn't being maintained, it seems to be remarkably well > maintained. I assume you are referring to my message from a couple months ago. At the time, the previous maintainer dropped it and transferred it to a mailing list. There had been no commits for around a year and a half. I am personally skeptical of anything maintained by a mailing list, because that seems to frequently lead to patches and bug reports being ignored for months or years. Then, the removal of MD5 distinfo broke it and it stayed broken for over a week with no indication given that a fix was in the works. On the other hand, Doug Barton has been very responsive to issues with portmaster and fixed this problem less than 48 hours after it appeared. Hence my recommendation to switch. -- Rob Farmer ___ 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"
kernel config file according to config(5): inconsistent ?
Hi, I read the guidelines in the man pages of config(5) on how to make a customized kernel config file: nooption name [, name [...]] nooptions name [, name [...]] Remove the specified kernel options from the list of previously defined options. This directive can be used to cancel the effects of option or options directives in files included using include. So I put following in my MYKERNEL config file: include GENERIC nocpu I486_CPU nocpu I586_CPU ident MYKERNEL nomakeoptions DEBUG nooptions MD_ROOT nooptions NFSCLIENT , NFSSERVER , NFSLOCKD , NFS_ROOT nooptions MSDOSFS , CD9660 nooptions PROCFS , PSEUDOFS The comma separated items seemed to cause an error when I do the buildkernel. If I remove the commas and make a 'nooptions' per item, then it is OK. Something seems to be inconsistent here, right? Same inconsistency for "nodevices" with the syntax in the manpages and the real config file Rob. ___ 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: Well, I broke it! FreeBSD V8.1 release
On Wed, Dec 22, 2010 at 12:45, Jason Helfman wrote: > IMHO... > It seems that /etc/rc.conf is in need of a sytax check script. Something > similiar to visudo for editing /usr/local/etc/sudoers. > Just run it with /bin/sh. If no errors appear the syntax is good. Or you can use /bin/sh -x to see more detail. -- Rob Farmer ___ 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"
FBSD 8: custom kernel config ends boot at "mountroot>". Plz. help!
Hi, My system boots fine with the GENERIC kernel on FreeBSD 8.0 I made a custom kernel, but the boot process then ends with the mountroot> error and prompt. Apparently something is wrong with my kernel config file. Can somebody check it below and tell me what is wrong with my kernel config file? Especially the GEOM_PART_* at the end might be the culprit, although this configuration used to work for 7.3. Thank you! Rob. # My kernel config file: cpuI686_CPU identMYKERNEL options SCHED_ULE# ULE scheduler options PREEMPTION# Enable kernel thread preemption options INET# InterNETworking options INET6# IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS# Berkeley Fast Filesystem options SOFTUPDATES# Enable FFS soft updates support options UFS_ACL# Support for access control lists options UFS_DIRHASH# Improve performance on big directories options COMPAT_FREEBSD7# Compatible with FreeBSD7 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV# install a CDEV entry in /dev devicepci deviceata deviceatadisk# ATA disk drives options ATA_STATIC_ID# Static device numbering devicescbus# SCSI bus (required for SCSI) deviceda# Direct Access (disks) devicepass# Passthrough device (direct SCSI access) deviceatkbdc# AT keyboard controller deviceatkbd# AT keyboard devicepsm# PS/2 mouse devicevga# VGA video card driver devicesplash# Splash screen and screen saver support devicesc devicepmtimer deviceloop# Network loopback deviceether# Ethernet support devicepty# BSD-style compatibility pseudo ttys devicemd# Memory "disks" devicebpf# Berkeley packet filter options SC_DISABLE_REBOOT options DEVICE_POLLING options HZ=1000 nodevice mem nodevice io nodevice uart_ns8250 nooptions GEOM_PART_BSD nooptions GEOM_PART_EBR nooptions GEOM_PART_EBR_COMPAT nooptions GEOM_PART_MBR ___ 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: FreeBSD .dlink 8.1-RELEASE FreeBSD 8.1-RELEASE #1: Tue Nov 9 21:13:03 MSK 2010 r...@.dlink:/usr/obj/usr/src/sys/GENERIC i386
On Sat, Dec 4, 2010 at 05:16, K. Yura wrote: > Can't use watch. How to install snp snoop device? > The module is built during normal kernel builds, unless you are using the MODULES_OVERRIDE directive in your kernel. Run kldload snp. Put snp_load="YES" in /boot/loader.conf to get it automatically every boot. If you are going to manually build things in /usr/src, you should run make obj in the directory first, to create a directory in /usr/obj for output. Otherwise, your .o files and such are mixed in with your sources. -- Rob Farmer ___ 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: RELEASE vice CURRENT vice STABLE
On Fri, Dec 3, 2010 at 13:26, JB wrote: > The other *BSD are developed sequentially, that is, there is one > branch and each major/minor release cycle follows the previous one > (at no time there is a parallel major/minor branch development). > > In case of FreeBSD, it seems (visually) that there is some mainline > CURRENT branch repository since FreeBSD 1.0 time, from which major > branches are started in parallel (right now there are 8.2-CURRENT > and 9.0-CURRENT developed, if I am correct), and they end their own > life so to speak, without affecting other major branches; but there > were periods of sequential dvelopments as well, e.g. 5.0 thru 5.2. > So, this is the overview, as I see it. In the past 5.x and prior, I believe things were a bit different, but this represents what has happened for the last several years: There is only one current. It is the main branch in CVS and is where primary development occurs. There are no guarantees with current - the ABI may change at any time, features added/removed, and other major changes made, with the build sometimes broken. Some debugging stuff is turned on by default and there is an expectation that you follow the commit mails and curr...@freebsd.org list to keep track of things which may affect you. Current is branched off every 18 months (approximately) to make a stable branch. On this branch, the ABI is consistent (applications will not need recompiled due to changes) and backwards compatibility isn't broken within the branch. Nothing is committed directly here - if a change in current meets these criteria, then it may be MFC'ed (merged from current) after it has been proven to work properly (can be several days to weeks/months depending on the severity). There are two supported stable branches right now, 7 and 8. The CVS tags have the form RELENG_8. For current and stable you build your system from source, though snapshots are generated monthly for a convenient starting point. Several times per year, a new release is created from the stable branches - such as 8.1. There is a list on the website of which are currently supported and when they will EoL. Once a release is created, only security fixes and serious errata fixes may be applied on that branch. CVS tags are like RELENG_8_1. These can also be updated with freebsd-update (binary updates). Current is (right now) called 9.0 for cases where a version number is necessary, because that is what will be branched from it next, but it will become 10.0, 11.0, etc. without a new branch in CVS once more stable branches exist. See: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/version-guide/index.html -- Rob Farmer ___ 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: porting software to FreeBSD, what to do if Makefile lacks?
2010/11/18 O. Hartmann : > Well, > in this case, it would really be a 'nice to have', maybe this is worth a PR? > Try asking on the ports@ list. I'm not sure what the criteria is for something being listed there - if something isn't going to be used by very many ports, it may not be worth adding, from a bloat point of view. I would say it is probably safe for your port to assume csh is /bin/csh, though. -- Rob Farmer ___ 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: porting software to FreeBSD, what to do if Makefile lacks?
On Wed, Nov 17, 2010 at 16:58, O. Hartmann
wrote:
> Thanks.
> I got it. But it seems that my first porting task run into some difficulties
> for the advanced porters, since there is no autotool environment.
>
> By the way, the global environment variable ${CSH} seems to be noneexistent,
> instead ${SH} exists.
Interesting - I assumed it would be listed in bsd.commands.mk, but it
seems to not be. Most of the base system tools are. In any case, glad
to hear you got it working.
--
Rob Farmer
___
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: porting software to FreeBSD, what to do if Makefile lacks?
2010/11/17 O. Hartmann :
> Hello.
>
> I try to create a port of a software which does not have a Makefile and is
> build via a propriate csh script. Installation is done temporarely into some
> lib's and exe's subfolder withing the source folder, so I need to tell the
> top level Makefile of the port to use a specific build script instead
> implying having Makefile and a home-brewn install script, which takes the
> binaries and libs out of the temporary folders and install them at the
> proper places within the FreeBSD's tree. How can I perform these two tasks?
You want to override the do-build target, something like:
do-build:
${CSH} ${WRKSRC}/build-script.csh
For the install, do the same with the do-install target. Unless your
install script is particularly long or complicated, it will probably
be best to put it right into the port's Makefile. Then you can use the
INSTALL macros to ensure permissions are set correctly, binaries are
stripped if the user doesn't specify WITH_DEBUG, etc.
If you haven't already, check out the Porter's Handbook - it will
familiarize you with important guidelines and covers a lot of common
problems:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/
--
Rob Farmer
___
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"
ZFS and 4k sector drives
I'm trying to figure out how, if it's possible, to make the 4k sector drives work with ZFS raidz2 pools. It seems that most of the 4k sector drives are using emulation, and reporting 512 byte sectors to the OS instead of their native 4k size. I know someone who had an issue trying to insert one of these drives into a running ZFS pool with other 512 byte sector drives with bad results. At one point I was told that it might be possible to use geli to specify the sector size (4k) and add those geli devices to a ZFS pool. I've even seen mention of using gnop. Does anyone know how well either solution works? Is there a known way to get these 4k sector drives to work in ZFS raidz2? In addition to that, how does ZFS handle drives with different sector sizes? Can I have a pool with 512 byte and 4k sector drives, or should all drives in a pool have the same sector size? Rob ___ 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: JMicron JMB363 PCIe controler doesn't work
On Sat, Nov 13, 2010 at 17:39, Ian Smith wrote: > Hey Woj, long time; yeah you picked a hell of time to re-surface. > > More likely nobody who knows would be bothered wasting their time wading > through the present volume of bullshit infecting this once-useful list, > which has been lately taken over by a gang of clueless vandals who want > to use it as a Twitter replacement from their mobiles, shoving up middle > fingers at those trying to restore some sanity. I've about had enough. There has always been crap on this list - that's the logical conclusion of unmoderated discussion forums. Its cyclic and will probably die down soon for a while. Filter your mail by thread, killfile the worst offenders, or get a moderator who can bump the BS over to c...@. In fact, you received excellent suggestions last time you brought this up (complaining about Wojciech Puchar, interestingly enough): http://lists.freebsd.org/pipermail/freebsd-questions/2009-May/199607.html Writing more mail to complain about too much mail is self-defeating. That's why I don't reply to stuff like the devil thread - it just increases its longevity. -- Rob Farmer ___ 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: Tips for installing windows and freeBSD both.. anyone??
On Sat, Nov 13, 2010 at 13:53, Chad Perrin wrote: >> Right, and this isn't a GUI problem - its a problem with combining the >> documents. What software allows multiple people to open and write to >> the same file simultaneously without trashing the file or losing data? > > Git and Mercurial come to mind. I'm not familiar with DVCSes, but I assume they work much the same as a centralized one - that is they don't open a file and leave it open - you work on something, then use locking for the actual commit part. Two people can't edit the same working copy at once, nor can they commit at exactly the same time. The difference is that locking is done at the application layer, rather than by the OS itself. -- Rob Farmer ___ 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: Tips for installing windows and freeBSD both.. anyone??
On Sat, Nov 13, 2010 at 10:48, Robert Bonomi wrote: > >> From owner-freebsd-questi...@freebsd.org Thu Nov 11 23:20:20 2010 >> Date: Thu, 11 Nov 2010 21:21:51 -0800 >> From: Rob Farmer >> To: freebsd-questions@freebsd.org >> Subject: Re: Tips for installing windows and freeBSD both.. anyone?? >> >> On Thu, Nov 11, 2010 at 17:19, Chad Perrin wrote: >> >> This isn't really a GUI problem, because the issue is the file format >> >> changing such that your .bat no longer worked. If you retained the >> >> original format or fixed the script, it would still work fine. >> > >> > Actually, my understanding was that the problem was someone refused to >> > type a simple command, and would rather make a series of seven clicks >> > thirty times while babysitting the application, and had no conception of >> > the benefits of letting more than one person work in parallel on a given >> > task. =A0It wasn't the file format that changed; it was someone's toleran= >> ce >> > for using a keyboard instead of a mouse. =A0This is the kind of thinking >> > that leads to the Mac defaulting to a mouse with only one button. >> >> Well, our info about this situation is limited, so it is hard to say >> exactly what happened. > > What hapened was a new 'senior-level' employee was 'offended' at the thought > of having to use 'obselete' tools that he was unfamilair with, and bitched > and moaned until management 'bought' Windows, and Windows apps, to 'shut h > im up'. >> Switching to a GUI doesn't preclude multiple people working in >> parallel, which is why I think the file format or whatever changed >> too, and that was really the problem. > > > Au Contraire, WINDOWS *itself* forbids more than one application from having > the same file open forworking on. As Bruce mentions, that's not true. Besides, that is a great feature, since it prevents files from being modified, moved, deleted, etc. while open in an application that can't handle those things. With older versions of Windows sometimes you could get files stuck in a locked state but I haven't seen that in a while. > > Said employee _demanded_ a GUI-based application. The 'obselete' tool > in effective production use did not exist in a windows version. > > Since said employee bundled all the formerly separate worksheets into a > _single_ workbook, *his* action, combined with Windows enforcement of > only _single-user_access_ to a given file, precluded multiple people > working on _anything_ in the workbook at the same time. Right, and this isn't a GUI problem - its a problem with combining the documents. What software allows multiple people to open and write to the same file simultaneously without trashing the file or losing data? Many load the whole file into memory then write the whole thing back out, blindly assuming that nothing has changed since. > > That wasn't the fault of the GUI environment, per se, it merely "facilitated" > the self-centered intrests of the above-mentioned employee. > > "Top Management" was a bunch of idiots. they let him get away with this, > and more -- he moved 'his' workhook _off_ the company servers, and kept > it _exclusively_ on his personal laptop. His excuse -- that way he could > work on it 'at home', too. But the company no longer had a copy of _their_ > production data. Indeed, so why do you include it as an anti-GUI argument? > >> My reading of the anecdote was that the batch file was indeed easy to >> use, > > The batch file approach was _so_ easy to use, that the company _secretary_ > would produce a custoized variation of it every week. Each line was a > 'magic incantation' that was simly copied, followed by a file name. > > Compare that to what is necessary _today_ to use a COM or .NET automation > interface. You create a script or exe which is double-clicked and does whatever you want. AutoIt was already mentioned. > >> but it no longer worked when the GUI switch was made. Again, that >> isn't really a reflection on the GUI, since there are ways to automate >> this kind of thing (for Windows, AutoIt was mentioned, plus there are >> probably solutions that are more native to the application). > > There were *NO* automation options at the time (Early Win95 days). The > necessary 'hooks' DID NOT EXIST in either the application *OR* the GUI. > So said MICROSOFT themselves. OLE automation has existed for years - Wikipedia says Microsoft published a book on it in December 1993 (OLE 2 Programmer's Refe
Re: Tips for installing windows and freeBSD both.. anyone??
On Fri, Nov 12, 2010 at 11:06, Polytropon wrote: > On Thu, 11 Nov 2010 21:21:51 -0800, Rob Farmer > wrote: >> I'm not saying the CLI is universally bad - if you gain competence >> with a set of programs that you use frequently, it can be very >> efficient. It does make it hard to enter a new area, though - you've >> got to learn some before you can do anything. > > When entering WHICH field new to you this is different? > > Repeat after me: Computers. Are. Not. Easy. :-) None - but people don't feel like they are entering a new field. Everyone uses computers - public schools have spent massive amounts of money to start kids using computers at 5 or 6 years old, if they haven't already at home. So the discussion isn't framed as learning something new - its "why should we change the way everyone has been working for years?" To use a US example, you see the same thing with the SI/metric system. Scientists and other technical people use it almost universally without issue (except for some oddities, PSI is somewhat popular) - it is better for real/serious work, but the general public doesn't see it as new or valuable - its just a stupid change in the way everything has always been done. -- Rob Farmer ___ 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: mergemaster comparing everything.
On Fri, Nov 12, 2010 at 09:04, Leon Meßner wrote: > On Fri, Nov 12, 2010 at 09:40:01AM -0700, Warren Block wrote: >> On Fri, 12 Nov 2010, Leon Me?ner wrote: >> >> > is there a trick besides using the rcs funktion of mergemaster to get >> > around having to look at every file in /etc for comparison? >> > I know there once was a bug in mergemaster but it's closed for a long >> > time now. >> ... >> > 90% of the differences are just in this cvs? tag lines. This is an >> > upgrade from 8.1 to -STABLE. >> >> 'mergemaster -Ui' helps. > > thanks, that helped. Did the default behavior of mergemaster change > somewhere because i didn't have to do this awhile ago (months not > years). The problem is the svn to cvs exporter doesn't properly tag the existing revisions for releases, but rather checks in a brand new revision and tags that. So, when you switch branches (such as release to stable) with CVS, all the $FreeBSD$ tags change, and you get the false positives in mergemaster. Using your example (etc/periodic/daily/300.calendar), there is: 1.5.36.1.4.1 for RELENG_8_1 1.5.36.1 for RELENG_8 1.5 for MAIN (current) There are many more 1.5.x revisions for other branches. These shouldn't exist - the file hasn't changed since 2000 and 1.5 should just be tagged with for all releases since then. -- Rob Farmer ___ 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: Tips for installing windows and freeBSD both.. anyone??
On Thu, Nov 11, 2010 at 23:16, Chad Perrin wrote: > It sounds like in some respects we're violently agreeing with each other. > On one hand, I think that CLI programs can be great for frequent tasks, > especially if you have something like the Unix pipeline at your disposal > to automate complex tasks, and that GUIs have some discoverability > advantages; on the other hand, you think that GUI programs can be great > for cases where someone does not want to take the time to learn a better > way to do something, perhaps because he does not perform the tasks very > often, but if you do something often enough it might make sense to learn > a more efficient CLI-based way to do it. > > Another difference in our apparent approaches to this is that I think > it's a good idea to favor CLI tools when at all reasonable to do so, > while you seem to think it's a good idea to favor GUI tools when at all > reasonable to do so. We agree on the extremes, but not in the middle, in > other words. I just wish that we could agree without it feeling like > you're trying to convince people they shouldn't ever bother learning how > to use CLI tools unless they absolutely have to. Well, I think to some extent we are considering two different sets of people. If a programmer or sysadmin doesn't use the CLI, they probably aren't very good at their job, since they are missing out on a lot of tools. I was thinking more generally about end-users, who tend to be very reluctant to use the CLI (the whole there's a big black box, what do I do now? thing is intimidating) and it is usually more trouble than it is worth to convince them to use the CLI, even if it would make their jobs easier. Most general computer users will never give up the GUI, because it involves investing in computer skills and they don't see that as terribly worthwhile - they just want to get started on their work. I think some UNIX fans are reluctant to accept this, and in doing so limit its ability to grow. That's my reason for preferring GUI in most situations. -- Rob Farmer ___ 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: Tips for installing windows and freeBSD both.. anyone??
On Thu, Nov 11, 2010 at 17:19, Chad Perrin wrote: >> This isn't really a GUI problem, because the issue is the file format >> changing such that your .bat no longer worked. If you retained the >> original format or fixed the script, it would still work fine. > > Actually, my understanding was that the problem was someone refused to > type a simple command, and would rather make a series of seven clicks > thirty times while babysitting the application, and had no conception of > the benefits of letting more than one person work in parallel on a given > task. It wasn't the file format that changed; it was someone's tolerance > for using a keyboard instead of a mouse. This is the kind of thinking > that leads to the Mac defaulting to a mouse with only one button. Well, our info about this situation is limited, so it is hard to say exactly what happened. Switching to a GUI doesn't preclude multiple people working in parallel, which is why I think the file format or whatever changed too, and that was really the problem. > > >> >> However, it still points out one of the biggest problems with the CLI >> - there is a barrier to entry in knowing what commands to run with >> what arguments to make everything work the way you want. File > Print >> was easy for your office staff to figure out. The CLI equivalent >> apparently wasn't. > > That was not evident in the explanation of what happened. The > explanation suggested nothing about the batch file in question being > difficult to use (or "figure out"). From the sound of it, three > instructions on a 3x5 card would have sufficed to ensure everybody knew > what to do, except in the case of people who do not know how to operate a > keyboard. My reading of the anecdote was that the batch file was indeed easy to use, but it no longer worked when the GUI switch was made. Again, that isn't really a reflection on the GUI, since there are ways to automate this kind of thing (for Windows, AutoIt was mentioned, plus there are probably solutions that are more native to the application). >> >> I think many here are underestimating the value of GUIs, because they >> have been running many of these traditional UNIX commands for years >> (or decades) and are also technically oriented enough that learning >> them in the first place wasn't a big deal. > > I think that GUIs are quite valuable when used where appropriate. I > think that the rest of the time, people greatly exaggerate the value of > the GUI, to the extent that they begin to think the CLI (as well as TUIs > in general) has no value at all. I used to be one of those idiots, and > there was a time when I would have been on your side of this little > debate. That was almost fifteen years ago. Times change, and I grow in > knowledge and experience. The end result is that I believe those who are > competent to operate a computer professionally would benefit from > learning how to use the command line for those tasks that are more > efficiently performed without the GUI mediating the experience, at least > for almost any task that is performed with any regularity at all. I'm not saying the CLI is universally bad - if you gain competence with a set of programs that you use frequently, it can be very efficient. It does make it hard to enter a new area, though - you've got to learn some before you can do anything. That can pay off, if you keep using that program, but if it is a one-off or occasional thing (like the svn tagging example earlier in this thread), it's probably not worthwhile. While you argue that it increases flexibility, which is true in some ways, it also decreases flexibility by limiting me to the programs I know or am willing to read documentation for. I never read documentation for GUI programs - I jump right in and look through the menus to find what I need or realize the program isn't adequate and move on. -- Rob Farmer ___ 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: pseuadofs security announcement...
On Thu, Nov 11, 2010 at 01:01, wrote: > CouLd someone confirm my reading of the pseudofs security announcement issued > yesterday? > > It seems that it only applies to 7 prior to 7.3 and 8 prior to RC1. This > means that it doesn't apply to 8.1-R, correct? Yes - 8.1 is r210188, it was fixed in r196859. -- Rob Farmer ___ 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: Tips for installing windows and freeBSD both.. anyone??
d, on 'publication day', somebody had to sit there and > click on each relevant/changed sheet in the workbook, click on' file', click > on print, select the page to print, and click 'doit'. What a *wonderful* > productivity increase!! We've now got a system that requires a -human- to > play babysitttr the machine. For a couple of -hours- every week. all to save > the complainer from having to enter a few numbers redundantly. This isn't really a GUI problem, because the issue is the file format changing such that your .bat no longer worked. If you retained the original format or fixed the script, it would still work fine. However, it still points out one of the biggest problems with the CLI - there is a barrier to entry in knowing what commands to run with what arguments to make everything work the way you want. File > Print was easy for your office staff to figure out. The CLI equivalent apparently wasn't. I think many here are underestimating the value of GUIs, because they have been running many of these traditional UNIX commands for years (or decades) and are also technically oriented enough that learning them in the first place wasn't a big deal. -- Rob Farmer ___ 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: portupgrade fails to run or do anything
On Sun, Nov 7, 2010 at 12:12, Jerry wrote: > Really! When did "r...@freebsd.org" drop the port? If he is not > actively maintaining the port then perhaps he should inform the proper > authority. "He" is a mailing list. ports/ports-mgmt/portupgrade/Makefile Revision 1.256 Tue Jul 21 13:12:15 2009 PDT (15 months, 2 weeks ago) by sem Log: - Drop maintainership to ruby@ Beyond this point virtually no development has happened. The sourceforge project hasn't been updated since around that time and there are open PRs over two years old. Unfortuantely, FreeBSD has a lot of these niche mailing lists that virtually nobody reads but have PRs auto-assigned to them, effectively acting as a black hole. freebsd-rc is one of the worst offenders - other than Doug Barton, there don't seem to be any developers involved there and it has a massive buildup of unreviewed patches. So I would say portupgrade is unmaintained and thus encourage people to move to portmaster. -- Rob Farmer ___ 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: portupgrade fails to run or do anything
On Sun, Nov 7, 2010 at 10:15, Ron (Lists) wrote: > None of these suggestions help. I have never had to put www/ in front > of the port name before. The tab expansion is handled by > bash-completion as used to be smart enough to know the command I was > typing and could auto-complete port names, but no longer, which is why I > suspect that I have a screwed up database. Perhaps it is fallout from recent infrastructure changes? http://lists.freebsd.org/pipermail/cvs-ports/2010-October/205680.html Portupgrade doesn't seem to have an active maintainer, so perhaps try portmaster. -- Rob Farmer ___ 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: SSHgaurd and PF
On Tue, Nov 2, 2010 at 11:42, Justin V. wrote: > So i added this: > > auth.info;authpriv.info;ftp.info /var/log/auth.log > > > This is existing: > > ftp.info /var/log/xferlog > > > > > I see my failed attempts going to auth.log and sshguard is still not > blocking or logging.. > > I restarted both syslog and sshguard.. I feel like we are almost there > > > thanks, > > jv Great - then try: ftp.info |exec /usr/local/sbin/sshguard in your /etc/syslog.conf (don't forget to restart syslog) and it should be working - I'm not sure what the threshold for sshguard to block someone is, but you could test it - just make sure you have a way to get back in if it works and your IP is blocked (or wait for the next script kiddie). -- Rob Farmer ___ 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: SSHgaurd and PF
On Tue, Nov 2, 2010 at 10:40, Justin V. wrote: > Actually this was installed after the port completed: > > > yeaguy# grep sshg /etc/syslog.conf > auth.info;authpriv.info |exec /usr/local/sbin/sshguard > > But it is not exactly what the HOWTO ways, the HOWTO does not mention the > "exec" part. Could be that the docs are written for Linux or another version of syslog. The port and the man page say include the exec, so I would go with that. > > Put this line high into this file: > > auth.info;authpriv.info |/usr/local/sbin/sshguard Ok - if that isn't working, then check to see if your ftp server is logging to syslog under auth or authpriv. If not you'll need to change the setup to get the logs from the right place. -- Rob Farmer ___ 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: SSHgaurd and PF
On Tue, Nov 2, 2010 at 10:03, Justin V. wrote: > This is the guide I used: > > http://www.sshguard.net/docs/setup/firewall/pf/ > > I followed this section to block all brute attempts: Right, but did you do this part too? http://www.sshguard.net/docs/setup/getlogs/syslog/ The part you mentioned sets up the table and has pf drop the connection attempts, but you need to configure syslog to fill the table with IPs of attackers. -- Rob Farmer ___ 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: SSHgaurd and PF
On Tue, Nov 2, 2010 at 09:34, Justin V. wrote: > Hi, > > Would this be considered bruteforce?? Yes > > This goes on and on: > > > Nov 2 05:42:19 yeaguy pure-ftpd: (?...@a214.amber.fastwebserver.de) [WARNING] > Authentication failed for user [Administrator] > Nov 2 05:42:53 yeaguy last message repeated 3 times [...] > > My sshgaurd config: Something isn't set up right if you are getting that many attempts - it should kill them right away: Nov 1 10:47:51 peridot sshd[77847]: reverse mapping checking getaddrinfo for 178-238-137-213.hostnoc.eu [178.238.137.213] failed - POSSIBLE BREAK-IN ATTEMPT! Nov 1 10:47:53 peridot sshd[77967]: reverse mapping checking getaddrinfo for 178-238-137-213.hostnoc.eu [178.238.137.213] failed - POSSIBLE BREAK-IN ATTEMPT! Nov 1 10:47:54 peridot sshd[78123]: reverse mapping checking getaddrinfo for 178-238-137-213.hostnoc.eu [178.238.137.213] failed - POSSIBLE BREAK-IN ATTEMPT! Nov 1 10:47:56 peridot sshd[78228]: reverse mapping checking getaddrinfo for 178-238-137-213.hostnoc.eu [178.238.137.213] failed - POSSIBLE BREAK-IN ATTEMPT! Nov 1 10:47:56 peridot sshguard[49177]: Blocking 178.238.137.213:4 for >420secs: 4 failures over 5 seconds. Do you have the syslog.conf part set up as well as the pf part? I've only used it for ssh but something like the following needs to be there: auth.info;authpriv.info |exec /usr/local/sbin/sshguard > yeaguy# nslookup a214.amber.fastwebserver.de > Server: 10.1.1.1 > Address: 10.1.1.1#53 > > Non-authoritative answer: > Name: a214.amber.fastwebserver.de > Address: 217.79.189.214 > I wouldn't waste your time trying to find out who they are - just block and move on. That site is probably a shared web hosting account that was compromised by a bad php script - even if you successfully complain (assuming it is a legit hoster that cares) and they do something about it, there are thousands more. -- Rob Farmer ___ 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: Continuing problem with "portsnap"
On Tue, Nov 2, 2010 at 05:21, Jerry wrote: >> >> portsnap fetch extract >> >> Looking up portsnap.FreeBSD.org mirrors... 5 mirrors found. >> >> Fetching snapshot tag from portsnap1.FreeBSD.org... failed. >> >> Fetching snapshot tag from portsnap5.FreeBSD.org... failed. >> >> Fetching snapshot tag from portsnap2.FreeBSD.org... failed. >> >> Fetching snapshot tag from portsnap6.FreeBSD.org... failed. >> >> Fetching snapshot tag from portsnap4.FreeBSD.org... failed. >> >> No mirrors remaining, giving up. What does this give: fetch http://portsnap1.freebsd.org/pub.ssl fetch http://portsnap1.freebsd.org/snapshot.ssl openssl rsautl -pubin -inkey pub.ssl -verify < snapshot.ssl You should get something like: portsnap|1288656202|c4523276897a50ff0ca27add61344a4e96cc19a5f7e0bc8f8e17d138819e19a2 It seems like you are having a problem fetching the tag - can you ping the servers? are you behind a proxy? >> Working from Sweden, maybe a little slow! >> As you can see it can't find any mirrors. >> >> portsnap fetch >> Looking up portsnap.FreeBSD.org mirrors... none found. This is a separate issue due to bad DNS - the list of mirrors is obtained from: host -t srv _http._tcp.portsnap.freebsd.org and falls back to just portsnap.freebsd.org if it doesn't work. -- Rob Farmer ___ 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: Can't install - Octave, SuiteSparse
On Wed, Oct 27, 2010 at 01:09, Zbigniew Komarnicki wrote: > I suspect that problem is with this: > /usr/local/bin/ld: final link failed: Nonrepresentable section on output > collect2: ld returned 1 exit status This is probably a GCC problem. What exact version are you using (pkg_info | grep gcc)? There is another recent report of issues with the latest update to lang/gcc45: http://lists.freebsd.org/pipermail/freebsd-ports/2010-October/064212.html Perhaps the maintainer knows more (cc'd) or you could try rolling back temporarily - I've successfully built suitesparse with 4.5.2.20101014 on amd64 current recently. -- Rob Farmer ___ 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: FreeBSD 8.1-RELEASE Installation success
On Mon, Oct 25, 2010 at 17:25, Michael D. Norwick wrote: > 4 weeks ago I backed up all my data and reformatted from Debian 'lenny' to > GPT/ZFS/8.1-RELEASE. The next two weeks did not go so well. While I tried > hard to get ZFS formatted drives to work reliably, intermittent unexplained > core dumps with reboots gave me cause for concern. There have been some significant fixes to ZFS in the last several months. 8-STABLE is probably the best branch to follow for ZFS right now. On Mon, Oct 25, 2010 at 19:18, Michael D. Norwick wrote: > I spoke a little too soon. I was UPGRADING to KDE4 4.5.2 as I was typing > the message. 'portupgrade kde4' was @ approx. 38% when it error'd out on > something about 'kdelibs4-4.4.5' too old. Going to /usr/ports/kdelibs4 and > 'make clean', 'make', borked also. I do not have much time tonight for > fiddling so, I deleted my ports tree and cvsup'd /usr/ports again. I'll try > again tomorrow evening if the winds we are currently experiencing here in > western wisconsin don't blow all our buildings away and kill my horses. What KDE did you start with? Did you do: 20100902: AFFECTS: users of KDE4 AUTHOR: k...@freebsd.org KDE SC ports has been updated to 4.5.1. A number of files were moved between packages, manual intervention into update procedure is required: # pkg_delete -f kdehier4\* kdelibs-4\* kdebase-4\* kdebase-runtime-4\* kdebase-workspace-4\* # rm -rf /usr/local/kde4/share/PolicyKit/policy # cd /usr/ports/misc/kdehier4 && make install clean # portmaster -a (portupgrade -a can be used here too, if you want to stick with that) Upgrading big stuff like KDE is going to require some manual intervention because obsolete dependencies need removed, old libraries might interfere with the build of new ones, etc. Best practice is to look at /usr/ports/UPDATING for any special instructions when updating ports. ports-mgmt/portupdate-scan can help with this. In reality, myself and most people tend to wait for something to go wrong before checking (you can tell by the regular threads where people report a problem it already addresses.) -- Rob Farmer ___ 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 disable SCTP kernel in FreeBSD
On Mon, Oct 25, 2010 at 07:11, Chetan Shukla wrote: > Hi, > How we can disable SCTP kernel in FreeBSD. > I tried lsmod and kldstat but neither of them worked. lsmod is a linux command and kldstat shows modules that are loaded. In the GENERIC kernel SCTP is compiled in, so it won't show up this way unless you run kldstat -v (and it can't be unloaded since there's no module). I'm not familiar with SCTP, but I bet you can shut it off/control it with sysctl (assuming it does anything by default). To completely delete support for it will require building a custom kernel. -- Rob Farmer ___ 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: libxul compilation problem
2010/10/17 Fernando Apesteguía : > The machine has one single core cpu. Finally I was able to compile the > thing, compiling > the offending file by hand (nsHtml5ElementName.cpp) without the -O2 > optimization flag. > With this flag, cc1plus eats up all the memory of my system in a few > seconds. Without > the flag, the file is compiled without any problems and quite fast. > > Should this issue be a candidate for filing a PR? It's hard to say whether this is really a bug or not - I still think your overall memory is low - 1 GB of RAM should be a supported configuration, but that assumes a decent amount of swap - I'll bet sysinstall's recommended partitioning would give you 2 GB. Try mailing the maintainers (ge...@freebsd.org) and see what they say. -- Rob Farmer ___ 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: libxul compilation problem
2010/10/16 Fernando Apesteguía : > I didn't run X or whatsoever. That's why I think I should have enough memory. > In fact after getting that error, I rebooted so I could update the > ports from a "fresh" > running system (nothing cached or so). But even in that case, I'm getting the > same error. > > Any VM tuning I can try? I'm not really knowledgeable about that kind of thing. However, the port is marked MAKE_JOBS_SAFE which means that it will try to run multiple compiler instances in parallel, to speed things up if you have multiple CPUs/cores. You can try running with "make -DDISABLE_MAKE_JOBS" to just run one at a time - maybe you have enough memory for that but not multiple jobs at once? -- Rob Farmer ___ 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: libxul compilation problem
2010/10/15 Fernando Apesteguía : > The process being killed is cc1plus while compiling libxul. I'm > running a stock 8.1-RELEASE GENERIC kernel on amd64 platform. > The machine has 1Gb of physical memory and 256MB for swap (I have had > this setup for quite a long time and have always kept > my system up to date using the ports infrastructure without problems). 1.25 GB of total memory is rather low these days, especially if you were compiling with X or other things running (you didn't say one way or another). For a large port like this you are probably going to need more swap - Mozilla stuff is not know for being light on resources. -- Rob Farmer ___ 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: Like it or not, Theo is having a good laugh ..
On Oct 9, 2010, at 1:07 PM, Jerry wrote: > On Sat, 9 Oct 2010 09:47:04 -0700 > Rob Farmer articulated: > >> On Sat, Oct 9, 2010 at 05:30, Henry Olyer >> wrote: > >> "Surrilous" isn't an English word, nor an obvious typo of one, so I >> have no idea what you mean here. > > surrilous (adj.) coarsely abusive, vulgar or low (especially in language) > foul- mouthed I have never heard this word and couldn't find a definition using google define or dictionary.com (which aggregates many major dictionaries). Perhaps it is a word, but an extremely obscure one. -- Rob Farmer > > Although the OP might have meant scurrilous (an obvious typo): > > scur·ril·ous –adjective > > 1. grossly or obscenely abusive: a scurrilous attack on the mayor. > > 2. characterized by or using low buffoonery; coarsely jocular or derisive: a > scurrilous jest. > > -- > Jerry ✌ > freebsd.u...@seibercom.net > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __ > ___ > 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: Like it or not, Theo is having a good laugh ..
On Sat, Oct 9, 2010 at 10:06, b. f. wrote: > We're not going to resolve these problems in this > thread. Certainly. I will drop this issue - in fact, I largely did so after my conversation with Gonzalo Nemmi; however, people kept sending me stuff off list so I felt compelled to address some of it. (For example, the one about making a video and DMCAing it was only re-posted to the list after it was sent to me and I publicly replied). -- Rob Farmer ___ 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: Like it or not, Theo is having a good laugh ..
On Sat, Oct 9, 2010 at 05:30, Henry Olyer wrote: > I'm not sure which writer said it, but whoever it is who started that > paragraph with "Kinda wish you..." you sir are the problem. Not just a > problem for us FreeBSDer's, but also for American's. While we are analyzing people's behavior, please don't top-post. > > You probably don't see yourself that way. I understand that. But what you > are doing is surrilous. That's when instead of making the points underlying "Surrilous" isn't an English word, nor an obvious typo of one, so I have no idea what you mean here. > your position you resort to name calling and bad mouthing. Any "name calling" I may have done was only after many other people did it first - the only difference is every message I've sent has the list CC'd. > > Disagree? Well, re-read what you wrote. See what I mean? I *still* see no explaination of why the EAR doesn't apply or why I am wrong - just tangents about my world view, etc. The only other person who actually addressed the issue of US export laws, Robert Bonomi, largely agreed with me. Is this an overly restrictive and outdated law? Probably, but it still exists. -- Rob Farmer ___ 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: Like it or not, Theo is having a good laugh ..
On Fri, Oct 8, 2010 at 21:47, Jarrod Slick wrote: > @rob, > > Kinda wish you would make a video wherein you read your above statement from > a teleprompter with a green-screened American flag billowing in the > background. You might want to add in a statement about your deep respect > and admiration for the troops, though. To add in even more of that good ol' > fashioned American [self-]righteousness you could even, in a senseless spat > of litigiousness, DMCA yourself and have the video removed from whatever > third-party site you decide to post it on. > > Oh, and disclaimer . . . I'm an American. > > Anyhow, I'll go back to lurking. > You can imply that I'm a nationalistic jackass all you like, but the fact still remains that nobody has presented an argument (well reasoned and coherent or otherwise) for why FreeBSD wouldn't be subject to the EAR or why changing the license for this code would make one bit of difference (beyond public relations). -- Rob Farmer ___ 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: Like it or not, Theo is having a good laugh ..
On Fri, Oct 8, 2010 at 10:31, Ian Smith wrote: > We've had a clear explanation of why it's still there - an historical > oversight at worst, pre present levels of paranoia and litigiousness - > by Jung-uk Kim, who's been importing Intel ACPICA code into FreeBSD for > five or so years, among large works on other core aspects of FreeBSD. > > He stated that it will be dealt with in the next import of the code. > End of story? Let facts get in the way of such a splendid beat-up?] What do you mean by "dealt with"? Just drop clauses from the license? Has someone who legally represents the copyright holder approved that in writing? > If anyone finds any State Secrets or vaguely crypto code in Intel's free > (in both senses) ACPICA code implementation of open ACPI specifications, > I'm sure we'll get to hear about it. Meanwhile, please shut the FUD up. Export restrictions apply to more than crypto, and removing the license terms saying this doesn't actually remove the restrictions - they are a law. The only people spreading FUD here are those who are have an anti-American attitude and are unwilling to accept that since key parts of FreeBSD are contributions by people in the US and are then exported, it just might actually be affected by what US lawmakers say about exports. -- Rob Farmer ___ 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: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core
On Thu, Oct 7, 2010 at 10:19, Gonzalo Nemmi wrote: > If you have a point, then there´s no point in me addressing your point > .. unless you are asking me for legal advice .. > Should that be the case, just let me know; I charge by the hour .. no > "pro bono". Seeing as your messages says things like "El 07/10/2010" and "Rob Farmer escribió" and you seem unwilling to actually talk about US law, I'm curious to know where you attended law school and what states you are licensed to practice in, since you seem to be offering paid professional services. -- Rob Farmer ___ 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: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core
On Thu, Oct 7, 2010 at 03:23, Gonzalo Nemmi wrote: > Im saying what I already said. And yet, you haven't really addressed my core point. Consider the following scenario: I write a tutorial on how to use GCC (a program originally written in the US by a US citizen and stills recieves significant contributions from US citizens) to compile programs for targeting ICBM's. I burn my tutorial plus a copy of GCC to a CD and ship it to Supreme Leader Kim Jong-il's residence, then he sends me $50,000 cash in exchange. The GPL has no problems whatsoever with this (it never addresses exports, says there shall be no discrimination against certain fields of endeavor, and the added "services and support" sidestep any sales issues). Yet, do you really think this would be a-ok with customs? There are various laws that covered the situation, in addition to the license - for example, there are restrictions on transporting more than $9,999 worth of paper currency across the US border in a single transaction (even just to Canada). My point is that the US export restrictions apply to the Intel ACPI code, they apply to most of the GNU toolchain, they apply to work Yahoo has paid people to do, etc. FreeBSD, like it or not, is largely under the jurisdiction of US export law. You are saying that there should be a disclaimer telling people to "watch out for this one. Ask your lawyer about it's terms and conditions." People shouldn't be watching out for a particular license, but rather the broader implications of distributing stuff internationally, which, due to cold-war era laws, can involve a significant prison sentence if done wrong. If you are interested in adding a disclaimer, consider the following one from Red Hat's legal department, which covers the *entire* distribution: By clicking on and downloading Fedora, you agree to comply with the following terms and conditions: Fedora software and technical information is subject to the U.S. Export Administration Regulations and other U.S. and foreign law, and may not be exported or re-exported to certain countries (currently Cuba, Iran, Iraq, North Korea, Sudan, and Syria) or to persons or entities prohibited from receiving U.S. exports (including those (a) on the Bureau of Industry and Security Denied Parties List or Entity List, (b) on the Office of Foreign Assets Control list of Specially Designated Nationals and Blocked Persons, and (c) involved with missile technology or nuclear, chemical or biological weapons). You may not download Fedora software or technical information if you are located in one of these countries, or otherwise affected by these restrictions. You may not provide Fedora software or technical information to individuals or entities located in one of these countries or otherwise affected by these restrictions. You are also responsible for compliance with foreign law requirements applicable to the import and use of Fedora software and technical information. Perhaps there are loopholes (I export to Canada, then a Canadian exports to somewhere else) but this doesn't change the situation for people in the US, like the OP. You are talking about reviewing the licenses, but exporting is also matter of criminal law. If I consulted a lawyer about doing such an export, it is reasonable to expect that they would bring this up, rather than just summarize license terms on a one-off basis. -- Rob Farmer ___ 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"
Fwd: Canon Support Centre - Ref # 00066023
I have a Canon LBP7200Cdn printer (d = duplex, n = network). Canon advertise on their web site that this printer works on Debian and Red Hat Linux, and they provide drivers for CUPS and some source code. However, I have not been to make this printer work on either Debian or PC-BSD, and I have not heard of anyone else being able to get it to work as a network printer on any Linux/Unix system. It works OK through Windows (maybe it can be set up as a Samba share, but I doubt it). The source software does not compile on PC-BSD. I have not tried a USB connection. The problem seems to be related to the Canon CAPT printer language and the need to translate from postscript (Canon `pstocapt3` program failed with a segmentation fault in one experiment). Canon support have now confirmed that the printer will not work with Linux, in spite of them providing some drivers purporting to work with Linux (Debian and Red Hat) (see below). This same software seems to be provided for all of the Canon LBP series printers. Cheers to all, Rob Hurle -- Forwarded message -- From: Techsupport Date: 7 October 2010 14:19 Subject: Canon Support Centre - Ref # 00066023 To: "rob1...@gmail.com" Ref # 00066023 Dear Rob, Thank you for your enquiry. I sincerely regret to advise that the Linux ( Debian ) is not supported by this printer. However, please find link below the only Linux Printer Driver compatible with Canon LBP 7200 http://support-au.canon.com.au/P/search?model=LASER+SHOT+LBP7200Cdn&menu=download&filter=0&tagname=g_os Once again, I sincerely apologise for any inconvenient. If you have further enquiries in relation this or any other matter, please do not hesitate in contacting us on 13 13 83 and quote reference 00066023 Regards Stanley Consumer Technical Support Canon Australia Pty Ltd For on-line technical support visit www.canon.com.au, click on 'Support' and then select 'FAQs'. To speak to Canon Technical Support, please call 131383 (Australia), or 09 4890470 (New Zealand). ___ The information in this e-mail is confidential and privileged material and is intended only for the use of the person(s) to whom it is addressed. If you are not the intended recipient of this e-mail please return it to the sender at Canon Australia and destroy any copies made. ___ From: MyCanon [...@uber.biz] Sent: Thursday, October 7, 2010 3:55 PM To: canonm...@uber.biz;cctechsupp...@canon.com.au Cc: Techsupport Subject: New form submission for form: Support Request A new submission has been made to the form you created Title : Mr First Name : Rob Last Name : Hurle Email : rob1...@gmail.com Company Name : Mobile : 0417 293 603 Phone : 0262472397 Address : PO Box 4013 Suburb : Ainslie State : ACT Post Code : 2602 Preferred Method of Contact : Email Details : The LBP7200Cdn does not appear to work through Linux (Debian) when using a network connection. Do you have any solutions for this? -- - Rob Hurle ANU, College of Asia and the Pacific School of Culture, History and Language Histories of Asia and the Pacific e-mail: rob1...@gmail.com Telephone (ANU): +61 2 6125 3169 Mobile (in VN): +84 948 243 538 Mobile (in OZ): +61 417 293 603 - ___ 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: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core
On Wed, Oct 6, 2010 at 20:38, Gonzalo Nemmi wrote: > > As a lawyer, no matter how much I review your set up, it´s a _fact_ that a > license place in a place like > /usr/src/sys/contrib/dev/acpica/hardware/hwsleep.c, that is to say, lost > amongs a gazillion files: _will_ scape any review. > > Furthermore, you can count on legal advise about the thing you tell you > lawyer to review, but if you ignore _what_ you want to get reviewed: you > can´t count on anyone knowing it for you. I would assume that such a review would involve extracting all the licenses in the source tree, eliminating the duplicates, and having those reviewed. I'm saying I don't find the "oh I missed that one" argument convincing, because if there is the possibility of missing a license, then you aren't looking closely enough in the first place. This license is not just in src/sys/contrib/dev/acpica/hardware/hwsleep.c - it is in all the files within the acpica contrib directory, plus the upstream vendor states that it applies to the entire tarball on their website. You should reasonably expect that each piece of software (ie directory) within contrib may be under a different license and needs to be reviewed. >> Making the license more visible may be a good idea, but doesn't >> materially change the situation any. > > It does by making it visible and thus telling potential > exporters/re-exporters "watch out for this one. Ask your lawyer about it´s > terms and conditions". What I meant by "doesn't materially change the situation any" is that everything exported from the US should be considered under export restrictions unless proven otherwise. Jung-uk Kim says: Historically FreeBSD never touched the license header. However, I am going to do it next time to avoid confusions. ( http://lists.freebsd.org/pipermail/freebsd-questions/2010-October/222451.html ) I don't think this makes a bit of difference (it fact it would be somewhat misleading) since the export restrictions are a valid law and dropping clauses from the license doesn't change that - are you saying I'm wrong here? -- Rob Farmer ___ 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: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core
On Wed, Oct 6, 2010 at 20:04, Michael Powell wrote: > I was under the impression that the most onerous of these export rules and > restrictions applied to crypto technology. If this is so, what I don't quite > grasp is what do crypto export restrictions have to do with acpi? Is acpi a > copyrighted, patented, or trademark otherwise owned by some entity? Quite > possibly so as it is in contrib. I just have no idea who might "own" it. Or > how it would fall afoul of crypto export restrictions. > > Looking forward to enlightenment. :-) I'm not a lawyer either, so take all this with a grain of salt. Basically, there are two reasons the US will block an export, which you can read about at: http://www.bis.doc.gov/licensing/exportingbasics.htm 1) The export is considered "dangerous" for one reason or another, and needs to be licensed so the government can keep track of who is getting it and why they want it. Examples include military equipment, nuclear equipment, controlled substances, firearms, etc. Crypto is defined as a "munition" and is restricted for this reason. There are a lot of opinions about whether this is "right", but it has held up in court. 2) The destination is "designated as supporting terrorist activities" or is embargoed for political reasons (socialist/totalitarian government - Cuba, Iran, North Korea, Sudan, and Syria). Most of the people in these countries don't have access to a computer and the rights to install whatever they want on it, so this is targeted at government officials. As such, you are correct that for the vast majority of cases, the ACPI code shouldn't have problems or need a license. The biggest legal risk I can see is if ftp.freebsd.org and such allow people in the embargoed countries to download code - I've seen a brief reference saying Sourceforge was forced to IP ban these. -- Rob Farmer ___ 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: Like it or not, Theo has a point... freebsd is shipping export-restricted software in the core
On Wed, Oct 6, 2010 at 14:46, Randal L. Schwartz wrote: > I understand that entirely. Which is why it would be reasonable (and > downright ethical) to ensure that every FreeBSD integrator be made well > aware of this restriction. > > It hadn't occurred to *me* for example to think that FreeBSD might be > restricted. And I hadn't seen any prominent disclaimers. Why rely on a > very very buried notice? If your business model involves importing/exporting large collections of material which you did not create, and further more do not outright own, but are licensed to use under certain conditions, then you need to have both a lawyer and an accountant review your setup for any potential issues. There are entire college degrees in international business and it is folly to think that all the ins and outs of a particular scenario will be readily apparent. A competent review would turn up this license clause and would give you advice on what to do about it. I don't think complaining that you weren't aware of the license terms before exporting is valid. Furthermore, this isn't really a license issue, but more of a issue of federal law. If you are in the US, these laws regarding what may be exported to where always apply, regardless of what the license says. Making the license more visible may be a good idea, but doesn't materially change the situation any. -- Rob Farmer ___ 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: rebuilding world - is "chflags -R noschg *" necessary?
On Thu, Sep 23, 2010 at 04:02, Anton Shterenlikht wrote: > The fbsd manual states in section 24.7 Rebuilding "world": > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html > > in subsection 24.7.6 Remove /usr/obj > > *quote* > Some files below /usr/obj may have the immutable flag set (see chflags(1) for > more information) which must be removed first. > > # cd /usr/obj > # chflags -R noschg * > *end quote* > > I've never seen a file under /usr/obj/ with immutable flag set. > > Why would there be object files with immutable flag set? > Is this step really necessary? It will happen on amd64 if you build the lib32 bits (i386 compatibility libraries). -- Rob Farmer > > many thanks > anton > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > ___ > 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: why is the PHP stuff line "off" by default in ports/lang/php5?
On Mon, Sep 20, 2010 at 08:00, wrote: > I think that response was not all that unreasonable. I'm not sure if you are referring to me or ale here. > 3) I think (proof left to the reader) there is an apache/php package. There's not. There's no way to run pkg_add -r and get the apache module (either that or it is poorly named and not found with a search). And, as I understand it, at one point there was, then it changed. My suggestion was to add it back via a slave port (say lang/php5-apache). This would be *in addition* to the existing lang/php5 port and everyone who is worried about unnecessary dependency bloat, security, etc. would be free to keep using that. Supposedly, there is a reason that shipping a binary package for this is impossible, despite the fact that every major Linux distribution does (and thus millions of web servers run this way) and supposedly there are many detailed descriptions of this reason in the list archives, though I can't find any. Adding the slave port was a good faith suggestion about how to improve the situation to meet everyone's needs. I feel it is rather dismissive and somewhat rude just say "The answer is simply 'no'" without any explanation. If it has been discussed so many times (for the record, I have been subscribed to this list for two years and have never seen such a thread), then it shouldn't be too hard to post a link. And if the maintainer is too busy with other work to do that, then, as I said, don't reply and let someone else explain it. -- Rob Farmer ___ 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: why is the PHP stuff line "off" by default in ports/lang/php5?
On Mon, Sep 20, 2010 at 00:45, Alex Dupre wrote: > This "issue" has been discussed too many times. The answer is simply > "no", but you can search the archives for the actual reason. You have to > comile the module for your specific apache installation. > > -- > Alex Dupre > If you can't be bothered to give the "actual reason," then why even reply? I have searched the archives. Unfortunately, there are so many messages revolving around how to set up php, secure it, etc. that it becomes difficult to find anything relevant. The only thing I came across was a thread from 2007 about how this is "more like a personal preference than engineering as such"[1] and "its just one of those things that you learn to live with after a while."[2] [1] http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151399.html [2] http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151384.html -- Rob Farmer ___ 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: why is the PHP stuff line "off" by default in ports/lang/php5?
On Sun, Sep 19, 2010 at 04:47, Ian Smith wrote: > In freebsd-questions Digest, Vol 3, Issue 9, Message: 21 > On Fri, 17 Sep 2010 20:03:46 -0700 patrick wrote: > > > I don't for sure, but I'd say it's off by default because not everyone > > runs PHP with Apache, and mod_php5/libphp5.so is strictly for Apache. > > No, not everyone installs PHP to use with Apache, but I guess that maybe > half do. This comes up many times in the last 5 or so years since you > could last install the module from a package rather than only the port. > > It's also one of those ports that takes a good while to build on slower > hardware (which of course developers don't tend to run :) but no amount > of requesting a version with '"Build Apache module" on' helped so far. > > > Lots of people use PHP with FastCGI or other purposes. > > True, yet those people probably also tend to be less likely to want to > install from packages (when available) anyway. Sure, adding libphp5.so > to the (or one different?) package would add maybe 3MB to it. I'd be > happy to spend an extra few MB and minutes to save likely an hour. > > > If you always want it to be on, add the option to /etc/make.conf. Or, > > if you're using portupgrade or some other port management utility for > > upgrades, there are ways to set the default options for the ports you > > use. > > Not a problem when you have the horsepower and time to build it, but a > significant loss of ability to install apache+php from packages, as you > once could from the CDs .. guess I just got spoiled back there in the > olden days :) Adding a slave port would probably be a good solution and shouldn't be too difficult. -- Rob Farmer ___ 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: virtaullBox AMD64 32bit lib
On 15 September 2010 17:43, Gholam Mostafa Faridi wrote: > I want install virtualBox on AMD 64 and I use FreeBSD 8.1 and I have SRC > directory , but when I run make install clean I see this error > " Requires 32-bit libraries installed under /usr/lib32. > Do: cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32 " > and I run this command > "cd /usr/src; make build32 install32; ldconfig -v -m -R /usr/lib32" > and after minutes I see this error > > "===> gnu/lib/csu (obj,depend,all,install) > sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.o > /usr/obj/usr/src/lib32/usr/lib32/crtbegin.o > sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.o > /usr/obj/usr/src/lib32/usr/lib32/crtend.o > sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbeginT.o > /usr/obj/usr/src/lib32/usr/lib32/crtbeginT.o > sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtbegin.So > /usr/obj/usr/src/lib32/usr/lib32/crtbeginS.o > sh /usr/src/tools/install.sh -o root -g wheel -m 444 crtend.So > /usr/obj/usr/src/lib32/usr/lib32/crtendS.o > ===> lib/csu/i386-elf (obj,depend,all,install) > ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32 -o gcrt1.o -r > crt1_s.o gcrt1_c.o > ld: Relocatable linking with relocations from format elf64-x86-64 > (gcrt1_c.o) to format elf32-i386-freebsd (gcrt1.o) is not supported > *** Error code 1 > > Stop in /usr/src/lib/csu/i386-elf. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > ldconfig: warning: /usr/lib32: No such file or directory " > > I make post about this error in freebsdforums but they can not help me > please see link > > http://forums.freebsd.org/showthread.php?t=17607 > > they said problem is ccache and I disable and remove ccache ,but still I > have that probelm > please help me I had a similar problem, and removing the contents of /usr/obj and then rebuilding world (cvsup'ed as of 15/09) with make -DNO_CCACHE seemed to work. This was on a real AMD64 machine too. Rob ___ 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: CPU temp munin plugin
2010/9/15 Dánielisz László : > Hi, > > What plugin do you use in munin to get values of your CPU? There are several, and some have dependencies on other software - what cpu are you using? Rob ___ 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: vmware-guestd6: error during make install
On Fri, Sep 3, 2010 at 06:01, Matthias Apitz wrote: > I tried to install the vmware-freebsd-tools.tar.gz directly as > VMWare.com it provides (I have compat6x already installed for some other > reason). But in vmware-freebsd-tools.tar.gz there are only kernel > modules for FreeBSD 6 and 7 and using the modules for 7 it crashes, ofc. > > Who can I get the tools installed? My EULA says: 3.4 VMware Tools. You may distribute the VMware Tools to any third party provided that (i) you only distribute the VMware Tools as a whole in object code format whether or not as part of, the Virtual Machine you create with the Software; (ii) you do not use VMware's name, logo or trademarks to market the VMware Tools, except you may refer to VMware names, logos or trademarks to indicate that the VMware Tools are compatible with or designed for use with the Software and (iii) you agree to indemnify, hold harmless, and defend VMware from and against any claims or lawsuits, including attorneys' fees, that arise or result from your use or distribution of VMware Tools. Notwithstanding the foregoing, you may distribute and modify the Open Source Software of VMware Tools; however, VMware may not provide any support, pursuant to Section 5, for such modified VMware Tools. Assuming you aren't in a US export restricted country (Cuba, Iran, North Korea, Sudan, and Syria) I should be able to give you a legal copy. This is the ISO that ships with Workstation 7.1.1 build-282343. It has kernel modules for 8.0 i386 & amd64. http://www.predatorlabs.net/dl/vmware-tools-freebsd-711.iso -- Rob Farmer ___ 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: vmware-guestd6: error during make install
On Fri, Sep 3, 2010 at 00:59, Matthias Apitz wrote: > > > Hello, > > I'm trying to install the port /usr/ports/emulators/vmware-guestd6 (even > the freshest from FreeBSD server) in 8-CURRENT: Do you have a particular reason for using this port? Assuming you mean 8.X, the Tools that ship on this iso with Vmware will work (assuming your copy of vmware isn't too old) if you install misc/compat6x or you can try emulators/open-vm-tools (open sourced copy of Vmware Tools that you build). If you meant 9-CURRENT, things may be more difficult since Vmware only ships binaries for releases and open-vm-tools is marked broken on current. -- Rob Farmer > > current# pwd > /usr/ports/emulators > current# mv vmware-guestd6 vmware-guestd6.old > current# tar xzf ~guru/vmware-guestd6.tar.gz > current# cd vmware-guestd6 > current# make > ===> Vulnerability check disabled, database not found > > > Choose "VM" -> "Install VMware Tools..." from VMware Workstation > menu to connect VM's CD-ROM drive and installation CD image temporary. > Press "Install" button when a dialog pops up. > > > This port mounts /dev/acd0 to /mnt. > > Are you ready? [Y/n]: y > /bin/mkdir -p /mnt > /sbin/umount /mnt 2>&1 >/dev/null > umount: /mnt: not a file system root directory > *** Error code 1 (ignored) > /sbin/umount /dev/acd0 2>&1 >/dev/null > umount: /dev/acd0: unknown file system > *** Error code 1 (ignored) > /sbin/mount -t cd9660 /dev/acd0 /mnt > ===> Extracting for vmware-guestd-6.0.3.80004_2 > /sbin/umount /mnt > (cd /usr/ports/emulators/vmware-guestd6/work; /usr/bin/tar xf > /usr/ports/emulators/vmware-guestd6/work/vmware-tools-distrib/lib/modules/source/vmmemctl.tar) > ===> Patching for vmware-guestd-6.0.3.80004_2 > LC_ALL=C /usr/bin/sed -i.bak "`/usr/bin/printf > 's|\0152\013\0350|\0152\\\n\0350|g'`" > /usr/ports/emulators/vmware-guestd6/work/vmware-tools-distrib/lib/sbin32-6/vmware-checkvm > sed: > /usr/ports/emulators/vmware-guestd6/work/vmware-tools-distrib/lib/sbin32-6/vmware-checkvm: > No such file or directory > *** Error code 1 > > Stop in /usr/ports/emulators/vmware-guestd6. > > there is no directory work/vmware-tools-distrib/lib/sbin32-6 but only > work/vmware-tools-distrib/lib/sbin32-63 > > creating a symlink helps a bit but later it can't find vmware-guestd for > installation which is not there, i.e. not in the tar file of the > vmware-tools; > > Any ideas? > > matthias > > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > Solidarity with the zionistic pirates of Israel? Not in my name! > ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! > ___ > 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" > -- Rob Farmer ___ 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"
