Re: Clarification about AMD64 port for Core Duo
On Thu, Jan 12, 2012 at 04:02:21PM +, Frank Lay wrote: > Hello, > > The CURRENT (9.0R) release notes have the following to say about the > AMD64 port: > > -->8- > As of this writing, the following processors are supported: > ... > * All Intel Core 2 (not Core Duo) and later processors > ... > -->8- > > Yet I see many people on the Internet claiming that they're running > FreeBSD version <= 9.0 successfully with Core Duos. What's the meaning > of this? I own a C2D E8400 (Wolfdale) processor, would I perhaps be > safer chosing the i386 port? Or is this all hyperbole? > > I'd appreciate any time you could spare explaining this to me. Do not confuse the Core 2 Duo processors with the Core Duo processors. They are not the same thing. The original Core Duo (and Core Solo) processors were 32-bit only and never became very widespread. The later Core 2 series supports both 64-bit and 32-bit operation and became quite popular, and I am fairly certain that most of the people you say you have seen claiming to run FreeBSD with a Core Duo are actually using a Core 2 Duo. As for your own C2D E8400, well the 'C2D' is short for 'Core 2 Duo', so yes it should support amd64 just fine. -- Erik Trulsson ertr1...@student.uu.se ___ 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 newline scape sequence does not work in Freebsd's bash
On Fri, Dec 30, 2011 at 06:47:45PM -0800, Edward Martinez wrote: > On 12/30/11 17:06, ??? wrote: > > I used ' singe quotes, so double quotes is: > > > > $ FRUIT_BASKET="apples oranges pears" > > $ echo -e "My fruit basket contains: \n $FRUIT_BASKET" > > My fruit basket contains: > > apples oranges pears > > > Thanks for the help, it worked. I find it interesting that FreeBSD's > echo man page does not mention the -e option is needed to > enable backslash escapes. I remembered why it worked on linux > is because i created an echo alias with the -e option. > So i will do the same for FreeBSD. The echo(1) manpage on FreeBSD doesn't say anything about '-e' because that version of echo doesn't have such an option. The echo you were actually using is the one builtin into bash and is described in the bash(1) manpage (including mention of the -e option.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: Is it safe to interrupt (Ctrl + C) while building a port or kernel?
On Thu, Nov 03, 2011 at 01:48:47PM -0500, Robert Bonomi wrote: > > On Thu, 03 Nov 2011 18:29:06 +0100, Damien Fleuriot > On 11/3/11 6:20 PM, Robert Bonomi wrote: > > >> From owner-freebsd-questi...@freebsd.org Thu Nov 3 12:10:08 2011 > > >> From: =?koi8-r?B?4c7Uz84g68zF09M=?= > > >> To: freebsd-questions@freebsd.org > > >> Date: Thu, 03 Nov 2011 21:10:19 +0400 > > >> Subject: Is it safe to interrupt (Ctrl + C) while building a port or > > >> kernel? > > >> > > >> Sometimes, while building process of some port or system kernel are in > > >> progress, you suddenly remember that you did something wrong and have to > > >> stop, solve your mistake and start one more time. > > >> > > >> Is it clear to interrupt the building process just by pressing Ctrl + > > >> ? > > > > > > Yes. > > > > > >> If it's so, do I need to run "make clean" before I start "make" one more > > >> time? > > > > > > Authoritative answer: "It depends". > > > > > > On what you 'did wrong", and what it takes to fix it. > > > > > > e.g., if you're building a kernel the 'classial' way, that is 'configure, > > > make depend, cd , make', and realize you left something out of the config > > > file, after you edit the config file, you have to rerun _all_ those steps. > > > > > > > Is it even advisable to build the kernel the "old" way ? > > On a slow processor, it makes a *BIG* differnence. > Even more so if you build everything you need into the kernel. > > 'make buildkernel' always recompiles an relinks *everything*. whether or > not any dependenies for the module have changed. If that is a problem then just use 'make -DNO_CLEAN buildkernel' and it won't reompile stuff that doesn't need to be recompiled. (Works for buildworld as well.) -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: What USB dialup modem WILL work with 8.2?
On Fri, Aug 26, 2011 at 01:34:03PM -0500, Lars Eighner wrote: > > On the basis of what I now believe was malicious advice, I am out of pocket > for a USB US Robotics 56k dialup modem. However, this device attaches as a > ugen device. I haven't found a way to make ppp on demand work with it > attached that way. > > I do not load umass because I am using hplip and it must be grabbed by ugen. > Otherwise my kernel is generic. However, I would be very surprised that > umass is necessary for the modem to attach correctly. umass should certainly not be needed for a modem to work, it is for hard disks and the like. What probably is needed on the other hand is umodem(4) and/or ucom(4). I do not belive they are included in a GENERIC kernel so you might not have those modules loaded. If you have not already tried it make sure those modules are loaded and see if your modem attaches to umodem. > > So I am asking again: does anyone have a dialup modem of any kind which > works correctly on 8.x to provide ppp-on-demand? If so what is it? IF you have a classic RS-232 serial port that is supported then any external modem that connects via RS-232 should work. As for what serial ports work is another question. Just about all of those built-in on motherboards should work, but unfortunately many modern motherboards do not include serial ports any longer. Expansion cards (PCI or PCI-E) may or may not work depending on exactly what chips are used on the cards. (If that use classic 16550A chips (or a good copy thereof) chances are excellent that it will work. If they use more modern (and more powerful) chips the chances are not quite so excellent.) (As for promises about what *will* 100% guaranteed work, which seems to be what you really want, I am afraid I can't give any. It has been several years since I last used a dialup modem, so I don't know for sure what *will* work with todays software, only what should work.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: 'mount -u' stumper
On Wed, Jun 22, 2011 at 06:45:27AM -0500, Robert Bonomi wrote: > > Environment is FreeBSD 7.2 i386 > > I have a Berkeley FFS filesystem that is mounted ro at boot time. > > If I do a 'mount -u' to make it writable, it _is_ made writable, but > "soft-updates' is also set. Incidentally, does anybody know _where_ > the 'soft-updates' optioon is documented?? I've looked evereywhere I > can think of, brute-force grepped wholee sections of the /usr/share/man > directory tree, all without succeess. > > If I use 'mount -u -r' to return it to the readonly state, 'soft-updates' is > *still* set. > > _HOW_ do I make'soft-updates' go away on a mounted filesystem ?? > > 'umount' and then 'mount' does the trick, but it is no a viable production' > option. > > THe underlying situation -- the need to make the filesystem writable -- comes > up only rarely, and it doesn't seem to hurt anything if the filesystem is > left with soft-updates set, but I _would_ like to clear it, because it *is* > logically inconsistant with the read-only status of the filesystem. > > Anybody got a bright idea I haven't thought of? To change if a given filesystem should use soft-updates or not you use tunefs(8) on that filesystem. (Read the manpage to find exact syntax.) Note that this cannot be done on a filsystem which is mounted read/write - only on filesystems that are unmounted or mounted read-only. -- Erik Trulsson ertr1...@student.uu.se ___ 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: sound card not recognized by freebsd 8.2 but mentioned in PC-BSD 8.2
On Sat, Apr 16, 2011 at 09:42:38AM +0700, Erich Dollansky wrote: > Hi, > > did you really get no other answer? > > On Friday 15 April 2011 22:11:05 Zhang Weiwu, Beijing wrote: > > Hello. I intend to use FreeBSD instead of PC-BSD. The sound card doesn't > > work on FreeBSD 8.2. I tried to follow the manual and loaded all sound > > card drivers > > > > # kldload snd_driver > > this will never work. Yes, it will. 'snd_driver' is a meta-module which depends on, and therefore will pull in, all the available sound drivers. (If you don't believe me try checking the output of 'kldstat' before and after doing 'kldload snd_driver') -- Erik Trulsson ertr1...@student.uu.se ___ 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: Mailing list etiquette (Was: Re: Linksys-E4200 Wireless N-router)
On Fri, Apr 08, 2011 at 01:11:52PM -0600, Chad Perrin wrote: > On Fri, Apr 08, 2011 at 06:42:16PM +0100, Arthur Chance wrote: > > > > section 8.6 starts: > > > > start quote > > Unless there is a good reason to do otherwise, reply to the sender and > > to FreeBSD-questions. > > end quote > > I, for one, am glad this does not happen more often. I really do *not* > need a bunch of duplicates cluttering up my inbox. I have yet to see > anyone complain of not receiving a CC in addition to the mail from the > list. > > I consider "not cluttering up the inboxes of people subscribed to the > list" a "good reason to do otherwise". You seem to miss one crucial fact: Not all the people who write to this list are subscribed to it. They will not see any replies directed only to the list. It is for their benefit that that rule exists. -- Erik Trulsson ertr1...@student.uu.se ___ 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 vim ports have personal KNOBS for options
On Sun, Mar 27, 2011 at 10:19:44PM +0400, Subbsd wrote: > Ive wanted to ask why the option of vim port has not yet been handed > via dialog by default. Personally, to make them work, we must define > WITH_OPTIONS=yes in make.conf (or WITH_VIM_OPTIONS=yes). Life without > it is so difficult ;) Because the maintainer of the vim port has a dislike for the OPTIONS framework. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Bit order == byte order??
On Fri, Mar 04, 2011 at 01:09:23AM -0800, per...@pluto.rain.com wrote: > Erik Trulsson wrote: > > On Thu, Mar 03, 2011 at 11:26:12AM -0500, Frank Solensky wrote: > > > In sys/netinet/ip.h, the first octet of the ip header structure > > > tests the byte ordering to determine the ordering of the header > > > length (ip_hl) and version (ip_v) fields. > > > > > > My question: that always works? While my reading of the > > > language specification document leaves both the ordering of > > > the bits within a byte and the bytes within a longer field as > > > implementation choices, the two are independent of each other. > > > > > > I haven't run into a CPU where this assumption was proven > > > incorrect ... > > > > Unless you have a CPU where memory is addressed bit-by-bit rather > > than byte-by-byte the ordering of bits within a byte is not only > > completely irrelevant, it is also pretty much impossible to > > determine programatically. > > Agreed it is at least difficult to determine programatically, > however it is quite important when dealing with hardware that > converts between a sequence of bytes and a bitstream, e.g. > serial ports, network interfaces, SATA ports. Driver writers > had _better_ know which bit of the byte, as well as which > byte of a word/longword/quadword, is going on the wire first. Although it certainly matters for serial I/O devices which bit goes out first on the wire, you only need to know if the I/O hardware will push out data with the most significant bit first or the least significant bit first and possibly adjust the values you write to the I/O hardware if it does not match the order you want the bits to go out. You still don't need to know anything about in which order bits are stored in a byte inside the CPU or in RAM. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Bit order == byte order??
On Thu, Mar 03, 2011 at 11:26:12AM -0500, Frank Solensky wrote: > In sys/netinet/ip.h, the first octet of the ip header structure tests > the byte ordering to determine the ordering of the header length > (ip_hl) and version (ip_v) fields. > > My question: that always works? While my reading of the language > specification document leaves both the ordering of the bits within a > byte and the bytes within a longer field as implementation choices, > the two are independent of each other. > > I haven't run into a CPU where this assumption was proven incorrect. > It just surprised me to see that recently Unless you have a CPU where memory is addressed bit-by-bit rather than byte-by-byte the ordering of bits within a byte is not only completely irrelevant, it is also pretty much impossible to determine programatically. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Upgrading from FreeBSD 4.10 to 8.1?
On Fri, Jan 07, 2011 at 12:02:59PM +, Frank Shute wrote: > On Thu, Jan 06, 2011 at 07:45:28AM -0800, patrick wrote: > > > > I know this is a bit crazy, but is there any opinion as to whether a > > binary upgrade using an 8.1 CD would work to upgrade a system running > > 4.10? Normally I would want to do a fresh install, but it's at a > > remote client site where it's not going to be easy to do it that way, > > and I'm going to need to guide someone less experienced through the > > install/upgrade process. > > An upgrade using a CD wouldn't work as the filesystem changed from > UFS1 to UFS2 betweeen 4 and 5. That by itself should not be a showstopper, since newer FreeBSD releases (incl. 8.1) still support UFS1 and can run perfectly fine on it. Although it is generally a good idea to use UFS2 rather than UFS1 with FreeBSD 5+ it is certainly not necessary. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Detecting updates to ports not installed
On Thu, Dec 30, 2010 at 08:19:00AM -0800, Chip Camden wrote: > Hello fellow BSDophiles, > > The chromium port is trying my patience. I'm not using it now, because of > its unpatched vulnerabilities. Buit I'm keeping it installed, so I'll be > notified by portversion when an update comes through. Is there a more > excellent way to receive the same sort of notification for a port that is > not installed? I think you can use http://www.freshports.org for that purpose. (I have never used it myself, but it looks like it should do the trick.) -- Erik Trulsson ertr1...@student.uu.se ___ 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 11:01:10AM -, Dave wrote: > Hi... > > I was trying to disable the console screensaver, and found that in > sysinstall, there is no way to select "none" as an option. > > So I went and edited /etc/rc.conf to comment out the line:- > Saver="fire" (or whatever it is) > > I put a ; at the beginning of the line, and now FreeBSD wont come up, > showing an error (unexpected ;) and leaving me with a # prompt. To comment out a line in a shell script (which is what rc.conf actually is) you should put a '#' at the beginning of the line, not a ';'. > > How do I get to re-edit rc.conf, to correct the problem, as all command > line commands result in a "not found" error. > > Also. What's the "Correct" way to disable a console screensaver? Changing rc.conf is the "Correct" way. If you do it by hand or use some other tool (like sysinstall) to do it does not really matter. Putting 'saver="NO"' in rc.conf or not having and 'saver=' line there will both do the same thing - not starting any screen saver. > > Sysinstall alows you to select and enable one, but not remove it! > > Bit of an oversight that I suspect Probably. The shortcomings of sysinstall are many and varied, so one more is not surprise. -- Erik Trulsson ertr1...@student.uu.se ___ 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: EVFILT_VNODE doesn't scale to large directory trees?
On Mon, Oct 25, 2010 at 10:48:58AM +0400, Igor V. Ruzanov wrote: > On Sun, 24 Oct 2010, Kenton Varda wrote: > > |That doesn't answer my question. I'm not even using make. I could write a > |few thousand words describing exactly what I'm trying to do and why it does, > |in fact, make sense, but it's really beside the point. I just want to know > |if there is any scalable way to monitor a very large directory tree for > |changes. Is there? > | > Dig `kqueue' - its the native FreeBSD's events polling/notification > mechanism. Since the OP mentioned using EVFILT_VNODE I would assume he is already using kqueue but is not satisfied with it. -- Erik Trulsson ertr1...@student.uu.se ___ 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 06, 2010 at 04:08:35PM -0700, Randal L. Schwartz wrote: > >>>>> "Erik" == Erik Trulsson writes: > > Erik> Since it essentially says that if you export it from the USA you will > Erik> have to follow whatever laws and regulations covers such exports, it > Erik> doesn't really add any burden since anybody doing such an export would > Erik> be legally required to do so anyway. > > Erik> AFAICT the paragraph in question does not add any restrictions or > Erik> burdens, it just points out potentially existing ones. > > Yes, you always have to obey the law when you export. But this clause > seems to imply that the associated software *knowingly* triggers the > export laws, probably in a bad way. > > Do you have a different opinion, and is it a legal opinion? To me it looks much more like a case of some corporate standard cover-your-ass boilerplate text that is used regardless of whether there is reason to believe any particular piece of software needs any special export approval. -- Erik Trulsson ertr1...@student.uu.se ___ 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 06, 2010 at 02:16:37PM -0700, Randal L. Schwartz wrote: > >>>>> "RW" == RW writes: > > RW> It doesn't say approval is needed. It says that it's needed if it's > RW> required by the appropriate agencies. In other words, it's needed if > RW> it's needed. > > But doesn't this then shift the burden to every exporter, knowing or > unknowing, willing or unwilling? > > > Seems like an onerous burden. Is it well-documented? Since it essentially says that if you export it from the USA you will have to follow whatever laws and regulations covers such exports, it doesn't really add any burden since anybody doing such an export would be legally required to do so anyway. AFAICT the paragraph in question does not add any restrictions or burdens, it just points out potentially existing ones. -- Erik Trulsson ertr1...@student.uu.se ___ 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: simplest way to get gnome/ kde up and running
On Sun, Oct 03, 2010 at 08:22:06PM +0800, Foo JH wrote: > Hi guys, > > I've been trying without luck to get KDE/ Gnome configured. I've been > reading and re-reading (and trying and re-trying) to get the window > manager running, but it's been driving me nuts. > > - How far I've gotten: > 1. Installing Xorg from the DVD package is easy. I've added the > hald_enable and dbus_enable to /etc/rc.conf > 2. Xorg -configure looks like it's working too: i get the skeleton > outlined window manager that I believe is fwm The default window manager included with X.org is actually twm (not that it actually matters for this question.) > 3. Xorg -configure xorg.conf.new -retro works too > > - Where I'm stuck: > 1. So far ~/.xinitrc is missing. But I followed the Handbank anyway and > did this: > echo "/usr/local/bin/gnome-session" > ~/.xinitrc > > 2. Running startx crashes now because it complains > /usr/local/bin/gnome-session is missing - that's true. > > Am I missing something? Or is there an easier way that Linux distros > have been very successful at? I'm a Freebie and I'd prefer to go with > FreeBSD as much as possible. Have you actually installed KDE and/or Gnome? I don't see that step included in what you say you have done. If you have not you will of course need to do that before you can configure either of them. For Gnome you will probably want the x11/gnome2 port/package while for KDE you will probably want either x11/kde3 or x11/kde4 (depending on if you want KDE 3.x or KDE 4.x) -- Erik Trulsson ertr1...@student.uu.se ___ 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: A command to check network transfer
On Fri, Oct 01, 2010 at 12:07:56PM +0200, Zbigniew Szalbot wrote: > Hi there, > > 2010/10/1 Fernando Apesteguía : > >> I cannot for the life of mine remember the command which allows me to > >> check incoming and outgoing transfer on lo0 and re0. Can you please > >> help? :) > > > > I use iftop[1] > > No, this one is built into the system. I havent't used it for some > time and cannot now recollect it. :( Try 'systat -if 1' or 'netstat -I re0 -w 1' / 'netstat -I lo0 -w 1'. One of them is probably what you are thinking of. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Linux filesystems accessible from FreeBSD 8-stable?
On Fri, Sep 24, 2010 at 08:48:00PM +0100, Frank Shute wrote: > On Thu, Sep 23, 2010 at 01:59:40PM -0400, Leif Walsh wrote: > > > > I can't seem to get a definitive answer on this from the internet, > > there's a lot of conflicting information. > > > > I have some data drives formatted with ext4, which I'd like to access > > from freebsd, preferably without totally reformatting because I don't > > have much temp space for copying. Read-only would be fine, read-write > > would be much preferred. > > > > Is this possible? Am I missing the big "ext4 drivers in > > freebsd/fuse/something" sign? Does anyone happen to know if it's > > possible to migrate an ext4 drive back to ext3, which it seems I can > > access from bsd if I let it pretend the journal doesn't exist? > > > > Wikipedia seems to think you're right in thinking you can migrate (or > mount only?) an ext4 as ext3: > > http://en.wikipedia.org/wiki/Ext4 Well, not quite. That article says: The ext3 file system is partially forward compatible with ext4, that is, an ext4 filesystem can be mounted as an ext3 partition (using "ext3" as the filesystem type when mounting). However, if the ext4 partition uses extents (a major new feature of ext4), then the ability to mount the file system as ext3 is lost. So, if an ext4 filesystem can be mounted as ext3 (and presumably as ext2 since ext3 filesystems can be mounted as ext2) seems to depend on how the ext4 filesystem was created/used. -- Erik Trulsson ertr1...@student.uu.se ___ 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: PDF to HTML translations
On Sun, Sep 05, 2010 at 08:57:11AM +0200, Roland Smith wrote: > On Sat, Sep 04, 2010 at 05:09:20PM -0600, Chad Perrin wrote: > > What PDF to HTML translators, other than pdftohtml, am I likely to be > > able to find in ports? I went looking for pdf2html, expecting to find > > that there, but no luck. Before I spend hours sifting through, still > > without knowing whether I missed something that should be obvious, > > Yes, you did. :-) > > > I > > figured I'd ask here whether anyone knows of something off the top of > > his/her head. > > Try textproc/pdftohtml Uhm, he said "other than pdftohtml" so I suspect he already knew about that one. -- Erik Trulsson ertr1...@student.uu.se ___ 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: two ata-related problems
On Fri, Sep 03, 2010 at 09:11:02AM -0400, Lowell Gilbert wrote: > per...@pluto.rain.com writes: > > > Two questions about installing FreeBSD 8.1 on a Dell Precision 420 > > (yes, I know it's old): > > I have a similar machine running as a lab tool. > > > 1. Should FreeBSD 8.1 be able to recognize a 100MB ATAPI Zip drive? > >I'm not finding it in the dmesg, although BIOS Setup recognizes > >it. (It and a CDROM are on the secondary IDE channel; I've tried > >with each of them as master and either way the CD is recognized > >but the Zip is not.) > > The default kernel definitely won't, but with the vpo device enabled, it > probably will. There's a kernel module for that, so you can try > "kldload vpo". Why would you need vpo for an ATAPI device? It is only for parallell devices. You should only need the 'ata' and 'atapifd' devices (both of whoch are included in GENERIC) to handle an ATAPI Zip drive. So, yes, FreeBSD 8.1 *should* be able to recognize an ATAPI Zip drive. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Upgrade 6.4-stable to 7.3
On Tue, Jul 27, 2010 at 03:02:48PM +0100, Michael Doyle wrote: > I would like to upgrade a server that is currently running version 6.4 > up to version 7.3 > Having looked at /usr/src/UPDATING on a 7.3 machine, I don't see any > major problems flagged. > > Given that I have console access to this machine, and I want to > preserve the user directories (it's our mail server) > would I be better off doing a source upgrade or a binary upgrade? Since you are running 6.4-STABLE, I think you will have to do a source upgrade. AFAIK binary upgrades are only supported when going from one -RELEASE to another (so 6.4-RELEASE to 7.3-RELEASE should be possible with a binary upgrade, 6.4-STABLE to 7.3-RELEASE would not.) > > In the past, I've usually done a wipe-and-reinstall when moving > between major version numbers > but I would rather avoid that this time around. > > Also, would people recommend staying with version 7.3 or jumping all > the way to version 8.1 ? Unless you have some specific reason to use 7.3 you might as well go all the way up to 8.1. You should probably do it in two steps though - first from 6.4 to 7.3 and then from 7.3 to 8.1 Just remember to make good backups first, just in case something goes wrong. (There should not be any serious problems involved - the source upgrades I have done from 6.x to 7.x and later from 7.x to 8.x were fairly uneventful - but you never know what might happen.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: 'file' Command Giving False Positives
On Fri, Jul 02, 2010 at 05:35:04PM +0200, Polytropon wrote: > On Fri, 02 Jul 2010 11:25:20 -0400, Lowell Gilbert > wrote: > > Why is it incorrect? "LZ" as the first two bytes in a file is (unless > > my memory is badly mistaken) exactly what the old command.com looked for > > as the flag of an executable. > > If I ask *my* memory, it tells me that what you mean is "MZ". As > far as I remember, those are the initials of a programmer involved > with the creation of the DOS binary executable format. :-) "MZ" is indeed what an MS-DOS style .EXE file should start with. For an MS-DOS .COM file there is no header or other metadata in the file so there is no good way of distinguishing it from any other binary file. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Question on packages and ports (and versions)
On Thu, Jun 10, 2010 at 04:58:56PM +0200, Antonio Vieiro wrote: > Hi all, > > I can't find an answer to this question, so I decided to post here. > Since I'm not very good at english let me ask this with an example. > > I assume that packages and ports may have different versions of the > same software (am I right?) so, for instance, if you install gnome > with packages you can have a certain "glib" version (say 1.0), but if > you install gnome with ports you can have a more recent "glib" version > (say 1.1). > > Now my question is, am I right on this assumption? If so, may I have > those two versions installed at the same time (from a package and a > port)? How does software from packages and ports interfere each other? > > Does software installed from packages live in different directories > than software installed from ports? If not, how does FreeBSD select > one over the other? A package is best seen as simply a pre-compiled port, i.e. packages are built from ports. After it has been installed there is no difference between software installed via ports or software installed via packages. -- Erik Trulsson ertr1...@student.uu.se ___ 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: ziz a dumb question?
On Sat, May 01, 2010 at 03:55:43PM +0200, Polytropon wrote: > On Sat, 01 May 2010 11:59:52 +0100, Chris Whitehouse > wrote: > > Seriously? Or joking? How did you measure it? > > Well... erm... in fact... I didn't measure anything, I just > utilized the numbers. :-) Modern PCs come with a 700 W power > supply (and more) Some modern PCs come with such hefty power supplies. Most come with far more modest power supplies. A typical modern PC (not one equipped with the absolutely fastest CPU and graphics card, but rather one intended for office use) normally draw less than 200W under load. If you take a modern PC optimized for low power consumption (such as a laptop) it will draw less than 50W under load. (For really low-power computers it will be less than 30W.) >, and the specs for my AS/400e 9406-170 say > 654 W with expansion unit (326 W without), measured kVA values > (according to manual) are similar. Weight is 70.5 kg, and > size is two big towers side by side. > > > > > My 2 year old desktop uses > > 60-100 watts depending on how hard it's working. > > Sounds like a notebook / laptop class computer. > > > > > 10 disks and lots of > > noise must use a few watts, though size and weight wouldn't have that > > much influence per se :) > > But it's more than 10 years old, too old to seriously > measure something! :-) > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" -- Erik Trulsson ertr1...@student.uu.se ___ 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: perl links
On Sat, Apr 10, 2010 at 07:14:48AM +0800, Aiza wrote: > When installing perl i see 2 links between /usr/local/bin and /usr/bin. > Is this still required or is it something left over from when perl was > part of the base system? > > symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl > symlinking /usr/local/bin/perl5.8.9 and /usr/bin/perl5 It is still required (at least the first one.) It is there to be compatible with a very large number of existing Perl scripts which assume that the Perl interpreter can be found as /usr/bin/perl This has nothing do to with when Perl was part of the base system - it is a Perl convention which was established before FreeBSD (or Linux for that matter) even existed. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Enough Is Enough
On Sat, Mar 27, 2010 at 01:28:26PM -0500, Programmer In Training wrote: > On 03/27/10 13:06, Tijl Coosemans wrote: > > > In /usr/ports/UPDATING look for the 20100205 entry for "users of Qt 3 > > and KDE 3". > > Pointless in as far as that does not address the underlying problem of > rebuilding EVERYTHING that needs to link against the jpeg library. GIMP > and gegl failed because a dependency for it is linked against jpeg-7 and > not jpeg-8. > > If I cannot basically reinstall the entire system via portupgrade -a I'm > reduced to fixing the problem ad-hoc and that is unacceptable because > eventually I'll have to deal with programs that link to whatever just > got rebuilt. In essence, this is a problem that is not easily solved > just by reading /usr/ports/UPDATING for Qt because it involves more than > Qt (by the way, thanks for the hat tip on Qt, but it's not high on my > priority list for being fixed right now, GIMP, Scribus and possibly a > few other apps that I'm currently unaware of there being an issue with > ARE). So don't use portupgrade if doesn't do what is needed. The simple solution is to *first* deinstall *all* ports (or at least all ports that depend, directly or indirectly, on jpeg in this case) and then reinstall them all. This might require a bit more manual intervention than using portupgrade would have, but on the other hand it is almost guaranteed to work correctly every time. The problems you are running into is essentially due to trying to build updated binaries while still having old binaries installed (and having this trigger bugs in the build mechanism of various ports.) If you first remove all the old binaries and then build new ones you avoid many potential problems. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Hardware RAID controller questions - 3Ware vs RocketRaid
On Thu, Mar 18, 2010 at 09:37:32AM +0100, Andy Wodfer wrote: > Hi, > We're setting up two backup servers where each server will have about 4TB of > harddrives (for now) connected (4x1TB and 8x500GB drives). Last night we ran > into trouble with the 3ware controllers we have (9650SE-8LPML) because we > couldn't create a larger RAID5 than 1.99TB. That is strange, since all the 3ware 9000-series controllers (including the 9650) are supposed to be able to handle arrays larger than 2TB. -- Erik Trulsson ertr1...@student.uu.se ___ 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 use cdrecord
On Sun, Mar 14, 2010 at 11:47:35AM +0800, Aiza wrote: > Chris Hill wrote: > > On Sun, 14 Mar 2010, Aiza wrote: > > > > [snip] > >> tried cdrecord -v speed=2 dev=acd0 blank=fast > >> gives this error "Open by devname not supported on this OS. > >> > >> What device am i to use? > > > > cdrecord wants to see your ATA burner as a SCSI device, so you'd use > > cdrecord dev=1,0,0 ... > > The numbers after dev= depend on where your burner is; find it using > > cdrecord -scanbus > > > > HTH. > > > > -- > > Chris Hill ch...@monochrome.org > > > > > > > cdrecord -scanbus gives a error. Invalid argument. Camiocommand ioctl > failed, can not open scsi driver Do you have that atapicam(4) kernel module loaded? If not load it. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Ports overlay
On Sun, Mar 07, 2010 at 02:45:41AM -0600, CyberLeo Kitsana wrote: > Hi! > > By necessity and convenience, I have developed a series of additions and > changes to the ports tree. These changes are probably not worthy of > inclusion into the official tree, so I'm looking to maintain an overlay, > of sorts, in the spirit of Gentoo's overlay capability. > > Is there an official method of hooking changes into a ports tree, while > maintaining the ability to csup or portsnap the unmodified version? How > do others tackle this particular problem? I don't know if there is any "official" method, but the method I use to keep local changes in the ports tree is as follows: I use cvsup to maintain a local copy of the whole repository, and then use cvs to checkout/update the ports tree from that copy of the repository. cvs knows how to detect and keep local changes. The disadvantage of this method is that updating the ports tree will be slower. The advantage is much increased flexibility in maintaining local changes or checking the history of any file. -- Erik Trulsson ertr1...@student.uu.se ___ 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: selling freebsd cd for profit
On Sun, Feb 28, 2010 at 11:10:33AM +, Matthew Seaman wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 28/02/2010 01:56:27, Chad Perrin wrote: > > Actually, once your project becomes a commercial enterprise, the GPL > > stops allowing reference to upstream sources to suit the requirements of > > code redistribution. If you sell GPLed software, you have to provide the > > sources yourself -- and, if you offer the *option* of access to the > > sources without actually ensuring that everybody gets a copy of the > > sources right away, you have to maintain sources for each distributed > > version for a number of years after the last such distribution. I'm not > > saying you *don't* have to maintain sources that long after the fact if > > you make sure everybody gets a copy right away; I haven't read the text > > of the GPL in detail in a while, and don't recall that specific detail. > > Hmmm... I think the concept of 'modification' is pretty important > here. If you're just redistributing software without modifying it, > you've fulfilled the intent of the GPL simply by giving a link to a > well-known download site. After all, what's the difference between > that, and your outsourcing a download facility to a service provider > like, say, SourceForge? The difference is that when you just give a link to a well-known site you have no guarantees that they will keep the source for that particular version of the software in question for as long as needed. Going by the strict letter of the GPL (v2) I don't see that merely providing a link to somebody else's site is sufficient. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Is it possible to see memory over 3GB on 32-bit FreeBSD?
On Wed, Feb 17, 2010 at 03:02:17PM -0500, Bill Moran wrote: > In response to Yuri : > > > I know that 32-bot Linux can see something like 3.6GB. > > Is this possible on FreeBSD? > > > > I see this message in system log: > > real memory = 6442450944 (6144 MB) > > avail memory = 3123482624 (2978 MB) > > Most systems usually see about 3.5G ... don't know why FreeBSD would see > less than that. It very much depends on what hardware you have in the system. Just about every expansion card or I/O device will reserve some of the address space for its own use. Some devices will need a lot of space - a graphics card with 256MB of RAM on it will use (at least) 256MB of the address space for example. > > amd64 is the way to go. If you _must_ stick with i386, you can try PAE > in your kernel, but I don't know if that's even supported any more. > > -- > Bill Moran > http://www.potentialtech.com > http://people.collaborativefusion.com/~wmoran/ > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: backup terminal title
On Sun, Feb 07, 2010 at 09:49:54AM +0100, Dominic Fandrey wrote: > Dominic Fandrey wrote: > > per...@pluto.rain.com wrote: > >>> I wish to use the "\033]0;%s\007" sequence in a shell-script to > >>> set the title of a terminal. But only if I am able to undo it. > >>> > >>> My requirement is that this must be done without using anything > >>> outside the base system. > >> There is an escape sequence which will cause the terminal to echo > >> back its current title, but it's a bit tricky to use given only > >> base-system tools because the echo ends with, IIRC, \007 rather > >> than \n. It may be possible in some shells to temporarily set the > >> line-end character to \007. You probably also want to (somehow) > >> cover problematic cases like terminals that don't reply to the > >> inquiry even though TERMCAP implies that they should. > > > > That actually doesn't sound tricky at all, remember that the > > original sequence to change the title also ends with \007. > > Where can I find this magical sequence? > > > > I've been trying to read: > > http://www.xfree86.org/current/ctlseqs.html > > > > But the Syntax is really cryptic. > > I finally got it: > > printf "\033[22;0t" > This stores the current icon and window titles on a stack. > printf "\033[23;0t" > This restores them from the stack. > > It works fine with xterm, has no effect on rxvt-unicode (which I > am using), though. > > That might well be a termcap problem. I've got to look into this. Not a termcap problem. A terminal problem rather. This "storing title on a stack" stuff is something very few terminals support. Recent xterms does, but few if any others. Other terminals will at best have sequences for "set title" and "read current title". -- Erik Trulsson ertr1...@student.uu.se ___ 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: Errors on UFS Partitions
On Sun, Jan 17, 2010 at 12:30:09AM -0500, The-IRC FreeBSD wrote: > Thanks everyone for their input it has helped greatly. > > Does anyone know a way to toggle soft-updates on a UFS non-root partition > while the system is live or without having to recreate the partition? Sure. Use the tunefs(8) utility for this. (Note that it cannot be used on a filesystem which is mounted read-write.) -- Erik Trulsson ertr1...@student.uu.se ___ 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 update system.
On Tue, Jan 12, 2010 at 09:45:35PM +0600, keneasson wrote: > Hello, > > Forgive cross posting, i have an unusable system and an not sure where to > post. > This follows up a more lengthy post, but i've got some new info so again. > > libxul requiers libiconv > libiconv requires libxul libiconv does not require libxul AFAICT. > > i have WITH_GECKO=libxul in make.conf That is likely what is causing your problems. Remove that line and see if things work better. > > i'm using FreeBSD 8.0-stable. > > thanks. > ken > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: does toor have passwd or not? According to logins -p: yes
On Wed, Dec 30, 2009 at 12:33:41PM +, Anton Shterenlikht wrote: > I was checking for passwordless accounts with 'logins -p'. > None was found. However, I understand toor doesn't have > passwd by default, and I never touched it, so I expected > logins -p to show toor, but it didn't. > > Just to check I also tried to su toor with root passwd - no access. > > Please can somebody clarify if toor does indeed have > passwd. toor, like many other system accounts, by default has its password entry set to '*' which indicates that password authenictation is disabled for that account. (See the passwd(5) manpage for details.) This means that unless you set a password for toor you cannot login as toor, so the mere presence of that account is not a security problem. -- Erik Trulsson ertr1...@student.uu.se ___ 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: "Checksum mismatch -- will transfer entire file"
On Mon, Dec 28, 2009 at 11:46:37AM +0600, Victor Sudakov wrote: > Victor Sudakov wrote: > > [dd] > > > > I would be happy to use svn as I do for my own projects. > > > > To run a cvs repository, you just need /usr/bin/cvs started from > > inetd. It is even in the base system. > > > > To run a subversion repository, you need much more infrastructure and > > more overhead (lots of dependencies from ports, probably a Web server, > > a database backend etc). Besides, cvs is conveniently integrated with > > Kerberos (we use :gserver: all the time) which I am not sure is > > possible with subversion. > > I have just built and installed ports/devel/subversion on a fresh box. > The port installed 17 dependent ports: Several of which are only build-dependencies. If you were to install subversion as a package far fewer dependencies would be installed. Of the ports you list autoconf/automake, libtool, help2man, perl, python, and tcl (and possibly some more) are only needed when building the port. > > apr-ipv6-gdbm-1.3.8.1.3.9 Apache Portability Library > autoconf-2.62 Automatically configure source code on many Un*x > platforms > autoconf-wrapper-20071109 Wrapper script for GNU autoconf > automake-1.9.6_3GNU Standards-compliant Makefile generator (1.9) > automake-wrapper-20071109 Wrapper script for GNU automake > expat-2.0.1 XML 1.0 parser written in C > gdbm-1.8.3_3The GNU database manager > help2man-1.36.4_3 Automatically generating simple manual pages from program > o > libiconv-1.13.1 A character set conversion library > libtool-2.2.6b Generic shared library support script > m4-1.4.13,1 GNU m4 > neon28-0.28.6 An HTTP and WebDAV client library for Unix systems > perl-5.8.9_3Practical Extraction and Report Language > python26-2.6.4 An interpreted object-oriented programming language > sqlite3-3.6.19 An SQL database engine in a C library > subversion-1.6.6_1 Version control system > tcl-8.5.8 Tool Command Language > tcl-modules-8.5.8 Tcl common modules > > There could have been more but I had disabled some crap like the BDB > backend. > > Please compare all this with a single /usr/bin/cvs binary and be > horrified. Of course it needs python26, perl and tcl - all the three > of them. I don't think I want all this on every server I plan to > makeworld on. > > To cut a long story short, I would rather continue using cvs, perhaps > until there is subversion-light in the base system. > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > sip:suda...@sibptus.tomsk.ru > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: What happened to /home?
On Thu, Dec 24, 2009 at 08:33:20AM +0200, Giorgos Keramidas wrote: > On Wed, 23 Dec 2009 15:40:13 -0800, Rem P Roberti > wrote: > >On 2009.12.24 00:21:47 +, Pieter de Goeje wrote: > >>On Thursday 24 December 2009 00:01:11 Rem P Roberti wrote: > >>> Today I booted my laptop and discovered that /home was gone. > >>> Well...not exactly..but for all intents and purposes. The system > >>> isn't seeing it although I can see it when I cd to /. But if I try > >>> and cd to /home from there the system tells me "home:Not a > >>> directory." What happened, and what can I do about it? > >> > >> Usually /home is a symlink to /usr/home. Perhaps the symlink is > >> busted? What it the output of `ls -ld /home' ? If you can still login > >> as a regular user, what does `pwd -P' say just after you are logged > >> in? > > > > I can still login as regular user, and when I run 'pwd -P' the output is > > / and then it goes back to the prompt. Output of 'ls -ld /home is: > > > > lrwxr-xr-x 1 root wheel 8 Dec 18 12:08 /home -> usr/home > > That's your problem right there. /home does not point to the absolute > path of '/usr/home' but to a *relative* path starting at whatever > happens to be your current directory when you access '/home'. Wrong. Relative paths in symlinks start at the symlink is in, not the current directory. I.e. that the symlink is relative should not be a problem. (Under AmigaOS relative symlinks worked as you describe, which made them a PITA and fairly useless, but under Unix relative symlinks have a more sane behaviour.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: Where is gfortran in FreeBSD 7.2 Release (i386)?
On Mon, Dec 21, 2009 at 01:14:22PM -0800, Jeff Hamann wrote: > I've been trying to figure out where gfortran went since it doesn't appear in > the /usr/ports collection in FreeBSD 7.2 (i386). > > I need it to build plots of numerical "things" and use the following lots: > > ./configure \ > CC="gcc -arch i386" \ > CXX="g++ -arch i386" \ > OBJC="gcc -arch i386" \ > F77="gfortran -arch i386" \ > FC="gfortran -arch i386" \ > --with-python \ > --with-openssl > > My web searches turn up lots of on-responses (i.e. you shouldn't be using > fortran anway's it's dead...), and I seem to have gcc42 installed. > > $ gcc -v > Using built-in specs. > Target: i386-undermydesk-freebsd > Configured with: FreeBSD/i386 system compiler > Thread model: posix > gcc version 4.2.1 20070719 [FreeBSD] > $ > > A little help please? Install the lang/gcc44 port which includes Fortran support. The Fortran compiler will be installed as gfortran44. -- Erik Trulsson ertr1...@student.uu.se ___ 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 is too filesystem errors sensitive
On Tue, Dec 08, 2009 at 02:09:03PM +0300, cronfy wrote: > > >>>> panics like 'freeing free block' or 'ffs_valloc: dup alloc' > >> > >> Is there a way to say "Dear kernel, don't panic, I'am holding your > >> hand, keep working please-please-please?" If so, can it lead to > >> complete filesystem corruption indeed or it is not so serious? > > > > Afaik you can't do this. And you shouldn't do if it'd be possible. The > > file system errors you mention above should not happen under any > > normal circumstances. They may happen after a crash caused by other > > reasons but should get repaired by fsck. The kernel cannot continue > > with such errors because the whole file system metadata cannot be > > trusted anymore until repaired. > > > Thanks. > > What I can definitely state is that after reboot nothing will get any > better. I will have same filesystem with same errors + new errors that > appeared because soft-updates were not synced, and I will have fsck > running in background. I'd prefer to just start fsck in background, > skipping that annoying reboot phase ;-) Am I willing strange? Background fsck can only handle a few, very specific, filsystem problems. (Basically situations where blocks are marked as being in use, even though they are not really used by anything. Softupdates is supposed to guarantee that those are the only types of filesystem errors that can occur, but in reality that guarantee does not always hold.) If you have other instances of filesystem corruption (which includes everything which can trigger a kernel panic) you need to use a foreground fsck to fix it. Personally I would recommend not using background fsck at all unless you know exactly what you are doing and why. -- Erik Trulsson ertr1...@student.uu.se ___ 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: 7.2-STABLE to 8-R
On Tue, Nov 24, 2009 at 01:18:51PM -0800, Charlie Kester wrote: > On Tue 24 Nov 2009 at 13:09:48 PST Roland Smith wrote: > >On Tue, Nov 24, 2009 at 05:40:25PM +, John wrote: > >> > >> Regarding ports, I think I'll take the long route. This box is my main > >> machine, my desktop - and so there are a LOT of ports installed. It will > >> be easier to make portmanager rebuild everything in pristine mode. It > >> will take a long time, but I accept this. Before this is done, I run the > >> built-in routines in /usr/ports - clean out */work/* and distfiles. > > > >I would _strongly_ advise you to make a list of all your current ports, e.g. > >with > >'portmaster -L >ports.list', deleting all ports and re-installing the ports > >labeled as 'leaf ports' and 'root ports' in ports.list. > > > >While portmaster/-manager do their best, they just cannot cover all the > >corner > >cases, especially since some ports require extra action (e.g. perl!) There is > >a good chance you'll end up with a big mess like binaries linked to both 7.x > >and 8.x libraries or ports failing to build for mysterious reasons. Both have > >happened to me in the past and are a major PITA to fix. > > > >I've done the complete delete/reinstall run a couple of times now on my > >desktop with ???490 ports installed. > > Can someone remind me once again, when rebuilding all of my ports, what > is the trick for avoiding the options dialogs? I'd like to have this > run largely unattended. I seem to recall someone describing a method to > go through all of them upfront, rather than having the build process > interrupted each time a port wants that input. Use 'make config-recursive' to go through all the option dialogs first. See the ports(7) manpage for other make targets and variables that influence which/how ports are built. > > I know that portupgrade has a batch build option, but unless I'm > mistaken, that skips any ports that need interaction to build. > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: Hi! a question about log in dmesg
On Sat, Nov 07, 2009 at 12:27:26PM -0600, Jesús Abidan wrote: > Hi, there, i am a pretty good user in linux and i don't know i am getting > some strange info in my dmesg file: > > at_matroute: v=(16)10ff007f00 > at_matroute: head=0xc42c1700 > at_matroute: returnr rn=0xc45b126c > at_matroute: v=(16)10ff007f00 > at_matroute: head=0xc42c1700 > at_matroute: returnr rn=0xc45b126c > at_matroute: v=(16)10ff007f00 > at_matroute: head=0xc42c1700 > at_matroute: returnr rn=0xc45b126c > at_matroute: v=(16)10ff007f00 > at_matroute: head=0xc42c1700 > at_matroute: returnr rn=0xc45b126c > at_addroute: v=(16)10fffe > at_addroute: n=(16)10 > at_addroute: head=0xc42c1700 treenodes=0xc45b12e8 > at_addroute: returns rn=0xc45b12e8 > at_addroute: v=(16)10ff007f00 > at_addroute: n=null > at_addroute: head=0xc42c1700 treenodes=0xc45b126c > at_addroute: returns rn=0xc45b126c > at_delroute: v=(16)10ff00 > at_delroute: n=(16)10ff80 > at_delroute: head=0xc42c1700 > at_delroute: returns rn=0xc45b2e88 > at_delroute: v=(16)10ff80 > at_delroute: n=(16)10ffc0 > at_delroute: head=0xc42c1700 > at_delroute: returns rn=0xc45b2e0c The above is (far too verbose) information about Appletalk routing. You presumably have the sysutils/netatalk port installed and activated. > > > and > > calcru: runtime went backwards from 229 usec to 114 usec for pid 690 (devd) > calcru: runtime went backwards from 551 usec to 468 usec for pid 376 > (dhclient) > calcru: runtime went backwards from 1999 usec to 999 usec for pid 360 > (dhclient) > calcru: runtime went backwards from 39486 usec to 19742 usec for pid 360 > (dhclient) > calcru: runtime went backwards from 668 usec to 334 usec for pid 146 > (adjkerntz) > calcru: runtime went backwards from 57078 usec to 47420 usec for pid 51 (sh) > calcru: runtime went backwards from 1964549 usec to 1411651 usec for pid 51 > (sh) > > > i know there is an issue about acpi and intel chipset or something like that > but i have no results about changing things in bios. I have desactivate udma > and no results. the firs message about at_matroute and delroute issues i > have no idea. > > Anyone has a clue??? > > greetings to everyone out there! > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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_RC2?
On Wed, Oct 28, 2009 at 07:48:16AM -0600, David McDonald wrote: > I looked at the contents of the link to 8.0_RC1 and found files there > marked RC2. I will give it a try but is that the real RC2 release > for FreeBSD 8.0? In general one should not assume that any Release or Release Candidate files available for download until the official announcment has gone out. (It has happened that a release had to be pulled at the last minute even after images had gone out to most mirrors, but before the official announcement.) In this particular case the official announcement for 8.0-RC2 has just been made so I guess any RC2 files found now are indeed the real deal. -- Erik Trulsson ertr1...@student.uu.se ___ 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: need C help, passing char buffer[] by-value....
On Mon, Oct 19, 2009 at 09:03:22AM -0500, David Kelly wrote: > On Sun, Oct 18, 2009 at 11:30:49PM -0400, Robert Huff wrote: > > > > Glen Barber writes: > > > > > > "//" comments are recognized by both C and C++. > > > > How about "... are recognized by both C++ and more recent versions > > of C."? > > I think gcc++ and gcc use the same preprocessor? Comments are stripped > in the preprocessor. > > The only thing we can really say is that gcc accepts // as a comment. Is > becoming an accepted convention in other C's but I doubt one can > universally state that its accepted in all "recent versions". It is accepted in recent versions of C, but not necessarily by all C compilers, depending on which version of C they support. "//" comments were added to C in the 1999 revision of the C standard, and was already then a very common extension that was supported by many compilers. If gcc supports "//" comments or not depends on which mode it is running in. If you run it in strict C89 mode, then it will not support "//" comments, but if you run it in C99 mode (or as a C++ compiler), it will support them. -- Erik Trulsson ertr1...@student.uu.se ___ 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: FWD: is this Intel CPU ok for 7.2 AMD64?
On Thu, Oct 15, 2009 at 03:13:49PM +0200, Len Conrad wrote: > > -- Original Message -- > From: "Len Conrad" > Reply-To: > Date: Wed, 14 Oct 2009 22:48:26 +0200 > > the FreeBSD 6.2 i386 dmesg.boot shows: > > CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > > Features=0xbfebfbff > Features2=0x659d> > AMD Features=0x2010 > Logical CPUs per core: 2 > real memory = 3220963328 (3071 MB) > avail memory = 3150913536 (3004 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0: Changing APIC ID to 8 > ioapic1: Changing APIC ID to 9 > ioapic1: WARNING: intbase 32 != expected base 24 > ioapic2: Changing APIC ID to 10 > ioapic2: WARNING: intbase 64 != expected base 56 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 32-55 on motherboard > ioapic2 irqs 64-87 on motherboard > > thanks, > Len > > == > > So, is there a definite, unique answer? > > Does it matter whether I run IA64 or AMD64 in the above Dell 1850? It matters very much. AMD64 should work fine. IA64 will will not work at all. -- Erik Trulsson ertr1...@student.uu.se ___ 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: is this Intel CPU ok for 7.2 AMD64?
On Wed, Oct 14, 2009 at 05:08:23PM -0400, jhell wrote: > > No you want: IA64 not AMD64 No, he does not want that. IA64 is for Intel's Itanium CPUs which are only used in a few big servers and just about nowhere else. The below is an ordinary x86 CPU (which the Itanium most certainly is not.) > > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ia64/ISO-IMAGES/7.2/ > > > On Wed, 14 Oct 2009 16:48, lconrad@ wrote: > > the FreeBSD 6.2 i386 dmesg.boot shows: > > > > CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 > > > > Features=0xbfebfbff > > Features2=0x659d> > > AMD Features=0x2010 > > Logical CPUs per core: 2 > > real memory = 3220963328 (3071 MB) > > avail memory = 3150913536 (3004 MB) > > ACPI APIC Table: > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > > cpu0 (BSP): APIC ID: 0 > > cpu1 (AP): APIC ID: 1 > > cpu2 (AP): APIC ID: 6 > > cpu3 (AP): APIC ID: 7 > > ioapic0: Changing APIC ID to 8 > > ioapic1: Changing APIC ID to 9 > > ioapic1: WARNING: intbase 32 != expected base 24 > > ioapic2: Changing APIC ID to 10 > > ioapic2: WARNING: intbase 64 != expected base 56 > > ioapic0 irqs 0-23 on motherboard > > ioapic1 irqs 32-55 on motherboard > > ioapic2 irqs 64-87 on motherboard > > > > thanks, > > Len > > > > > > ___ > > 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" > > > > -- > > ;; dataix.net!jhell 2048R/89D8547E 2009-09-30 > ;; BSD since FreeBSD 4.2Linux since Slackware 2.1 > ;; 85EF E26B 07BB 3777 76BE B12A 9057 8789 89D8 547E > > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: server specification.
On Tue, Oct 13, 2009 at 05:42:28AM +, Marwan Sultan wrote: > > Hello gurus, > > > > Im going to a new server, and i donot want to have a problem.. > > May please anyone advice me of any feed back of FreeBSD 7.2 with the > following specification: > > any problems? > > > > > > 1x Intel Core 2 Quad Q6600 > Kentsfield 2.4GHz 2x 4MB L2 > Cache LGA 775 > > 2GB DDR2 ECC > > 3WARE RAID SATA 2 ports > > 2x 250GB SATA in RAID 1 > > > > So any problems with quad kentsfield and FBSD 7.2 ? No problems AFAIK, but then the exact CPU model is almost never a problem. Far more likely to cause problems is the chipset used on the motherboard where one or more components (ethernet controller, SATA controller, etc) might not be supported or might have problems. (The same goes for any additional controllers that might be included on the motherboard or on add-on cards.) Most chipsets work fine, but some of the very newest might not be supported yet. -- Erik Trulsson ertr1...@student.uu.se ___ 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: reporter on deadline seeks comment about reported security bug in FreeBSD
On Mon, Sep 14, 2009 at 05:21:48PM -0400, Mikel King wrote: > > On Sep 14, 2009, at 3:12 PM, Dan Goodin wrote: > > > Hello, > > > > Dan Goodin, a reporter at technology news website The Register. > > Security > > researcher Przemyslaw Frasunek says versions 6.x through 6.4 of > > FreeBSD > > has a security bug. He says he notified the FreeBSD Foundation on > > August > > 29 and never got a response. We'll be writing a brief article about > > this. Please let me know ASAP if someone cares to comment. > > > > Kind regards, > > > > Dan Goodin > > 415-495-5411 > > Hasn't 6.x been End Of Lifed? Not at all. The 6.2 and earlier releases have been EOL'd, but 6.3 and 6.4 are still supported by the security team. 6.4 (and 6.x in general) will be supported until November 2010, which is more than a year away. (See http://security.freebsd.org/ for official EOL information.) > I mean considering that 8.0 is expected > to be released either later this month or early next, and 6.x will be > officially retired at that time, is it possible that this was > overlooked? Personally I don't think it's ever good to overlook > security, especially in the case of a root exploit. > > http://www.freebsd.org/releases/6.4R/announce.html -- Erik Trulsson ertr1...@student.uu.se ___ 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: shell command line argument + parsing function
On Mon, Aug 31, 2009 at 01:07:36AM +0200, Stefan Miklosovic wrote:
> hi,
>
> assuming I execute shell script like this
>
> $ ./script -c "hello world"
>
> I want to save "hello world" string to variable COMMENT in shell script.
>
> code:
>
> #!/bin/sh
>
> parse_cmdline() {
> while [ $# -gt 0 ]; do
> case "$1" in
> -c)
> shift
> COMMENT="$1"
> ;;
> esac
> shift
> done
> }
>
> parse_cmdline $*
>
> echo $COMMENT
>
> exit 0
>
> but that only write out "hello". I tried to change $* to $@, nothing
> changed.
But if you use "$@" (with the quote marks) instead it should work fine.
For further explanation please read the sh(1) man page where it explains the
special parameters $* and $@, while paying special attention to how they
expand when used within double-quotes.
>
> It is interesting, that if I dont put "while" loop into function
> parse_cmdline,
> and do echo $COMMENT, it writes "hello world".
>
> I WANT that function style. How to do it ?
>
> thank you
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
--
Erik Trulsson
ertr1...@student.uu.se
___
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: Firefox 3.5 on FBSD
On Wed, Aug 26, 2009 at 08:21:57AM -0600, Andrew Falanga wrote: > Hi, > > Well, I installed firefox 3.5 on my box at home but it wasn't working > correctly. Every time I'd start it I'd get, "Bad system call (core dump)," > or something similar. Does anyone here run firefox 3.5 on their box? If > so, what is the trick? kldload sem See the 20090628 entry in /usr/ports/UPDATING -- Erik Trulsson ertr1...@student.uu.se ___ 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: Boot failure
On Fri, Aug 07, 2009 at 12:26:10PM -0400, Identry wrote: > >> Should I use any flags? Should I mount the filesystems read write or read > >> only? > > > > You should never fsck a filesystem when its mounted! > > Ah... glad I asked. Actually it is only when a filesystem is mounted read-write that you must not run fsck on it. Running it on a filesystem which is mounted read-only should be OK. (Otherwise we would all be in a lot of trouble since when fsck is run normally during the startup sequence the root filesystem (/) is mounted read-only, and is in fact where the fsck binary is loaded from.) > > > I think you should start by reading the manual pages for fsck and > > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. > > Okay, that makes sense, and is simpler than what I was planning. I > have a long train ride, so I'm going to print out and read those man > pages, and whatever I can find in the Handbook, and maybe there's some > info in my Absolute FreeBSD book... > > > If this command quits with errors, you might try fsck_ffs without flags, > > or 'fsck_ffs -y' to have it try and repair all damage that it finds. > > Excellent. Thanks for all your advice Roland. > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: kernel designations terminology confusion -- amd64 used for into quad core
On Thu, Aug 06, 2009 at 05:18:09PM +0800, Erich Dollansky wrote: > Hi, > > On 06 August 2009 pm 16:40:41 Mark Stapper wrote: > > Erich Dollansky wrote: > > > > > IA 64? Wans't this once - or still is - the term used for the > > > Itanium? > > > > The one that didn't stick... indeed. > > do they really sell machines with this CPU in numbers? Yes, but not very large numbers - especially not compared to x86 machines. According to some estimates quoted in the Wikipedia article on Itanium, Intel manufactures around 200,000 Itanium CPUs per year, which translates to a far smaller number of machines since most of them are multi-CPU systems. By far the largest seller of Itanium-based systems is HP (which also partnered with Intel in creating the IA64 architecture in the first place.) > > I have not seen one in the wild. Not surprising since the Itanium is mainly used in the kind of high-end server systems that us ordinary people rarely see and certainly can't afford to buy. -- Erik Trulsson ertr1...@student.uu.se ___ 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: kernel designations terminology confusion -- amd64 used for into quad core
On Wed, Aug 05, 2009 at 02:14:49PM +0100, David Southwell wrote: > Hi every one > > My understanding is that one uses the amd64 for building a kernel for systems > with Intel Quad Core processors. That depends on if you installed the amd64 version of FreeBSD or the i386 version. The kernel should of course match the rest of the system. Intel's Quad Core processors (at least all the models they have released so far) supports both amd64 and i386. (i386 being 32-bit, while amd64 is 64-bit.) > > It is helpful when naming conventions follow a logical strand. I mean why > does > freebsd use a single manufacturer's name to represent a genre? The amd64 architecture is called that because it was AMD who invented and created it and was for a while the only one using it and since AMD named the architecture AMD64 that was the name FreeBSD used too. Later Intel also started using it (while using their own name(s) for it), but FreeBSD has stuck with the name amd64. This is no more strange than calling the i386 architecture for i386 even if it runs on a whole lot of processors other than the original Intel 80386. -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: cvs tag usage
On Tue, Aug 04, 2009 at 03:07:20PM -0400, Glen Barber wrote: > On Tue, Aug 4, 2009 at 1:43 PM, David Southwell wrote: > > I am confused about the usage of the tag for src. > > > > I took a look at the web pages and found the following choices: > > > > _7_BP > > _7_2_BP > > BP ? BP = Branch Point. It is a tag which marks the place where the corresponding branch was created. > > > _7_2_0_RELEASE > > Should be RELENG. Don't blindly follow how-tos. > > > _7_2 > > > > But could not find anything that told me where -p2 fits into this!! > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html > > > > > # uname -a > > > > 7.2-RELEASE-p2 FreeBSD 7.2-RELEASE-p2 #0: Wed Jun 24 00:14:35 UTC 2009 > > r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > > > To synchronize src do I use: > > > > *default release=cvs tag=RELENG_7_2 > > will this automatically track the latest version in 7_2 and therefore keep > > track with 7.2-RELEASE-p2 or later?? > > > > or > > do I need to use something like: > > > > *default release=cvs tag=RELENG_7_2-p2 > > > > No. Read the link I posted above. > > > Where can I find some explanation on this? > > > > Thanks in advance > > > > > > -- > Glen Barber > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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 find what symlink points to?
On Mon, Jul 27, 2009 at 05:44:59AM -0700, Unga wrote: > > Hi all > > I need to remove some unwanted symlinks on /dev using a C program. > > The "struct dirent" only shows the symlink name, how do I find what that > symlink points to for verification purpose? By using the readlink(2) system call. -- Erik Trulsson ertr1...@student.uu.se ___ 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: question about a driver - Gigabit - HP NC362i
On Fri, Jul 10, 2009 at 07:33:37PM +0100, João Pagaime wrote: > hello all > > any chance of the following NIC working with > the latests freeBSD release: > > Embedded HP NC362i Integrated Dual Port Gigabit Server Adaptor > > FreeBSD's hardware release notes dont look very promising Looks like a quite good chance of it working. That controller is apparently based around Intel's 82576 controller chip, which should be supported by the igb(4) driver. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Checksum mismatches when csup-ing.
On Tue, Jun 23, 2009 at 02:43:36PM +0200, Paul van der Zwan wrote:
>
> On 23 jun 2009, at 05:55, Frank Shute wrote:
>
> > On Mon, Jun 22, 2009 at 07:17:40PM +0200, Paul van der Zwan wrote:
> >>
> >> The last few days I see a dozens of Checksum mismatches when csup-ing
> >> src-all from cvsup.freebsd.org.
> >> No errors appear on ports-all.
> >> Is there a problem with the cvs repository ?
> >
> > Most people will use a local mirror as listed in the handbook:
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html
> >
> > Check and see if you have the same problem with one of the mirror
> > sites.
> >
>
> I have tried both cvsup.freebsd.org and cvsup.nl.freebsd.org with both
> csup and cvsup and I get checksum mismatches on all attempts.
>
> > If you've got the same problem, then your cvsup config file for src
> > could be up the creek.
> >
> I have deleted /usr/sup/src-all/* bun that did not fix the checksum
> errors,
> just gave me a lot of SetAttr messages the first run.
> If you mean my c{v}sup config file, that hasn't been changed in years
> and
> how would an error in that file cause errors on src-all but none on
> ports-all ?
>
>
> > If the problem disappears, then the server is up the creek.
> >
> I am stumped, as far as I can tell it's no local config problem, but
> what's causing it?
> I have no idea..
> Am I the only one seeing these errors ?
Nope, I am seeing exactly the same thing. (And I am using different mirrors
than you are.)
Since I too am only seeing this for src-all and not ports-all I
suspect it may be a problem with the svn->cvs export. (src-all is nowadays
maintained in a subversion repository and the changes automatically exported
to the cvs repository, while ports-all is still maintained directly in the
cvs repository.)
Note: I use cvsup to maintain a local copy of the cvs repository.
It is not clear if you too is doing that, or if you use cvsup to check out
just the latest version.
>
> Paul
>
> >>
> >> The fact that all errors are on src-all and none on ports-all make me
> >> suspect it is not a local problem on
> >> my system as both end up on the same filesystem here.
> >>
> >> Paul
> >>
> >> PS I am not on this list so please reply directly as well
> >>
--
Erik Trulsson
ertr1...@student.uu.se
___
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: Very slow disk speed / mpt0: LSILogic SAS/SATA Adapter
On Wed, Jun 17, 2009 at 01:35:52PM +0200, Matej ?erc wrote: > Hi, > > we have a HP ProLiant server with RAID 0/1 controller onboard. It is > detected as mpt0 (I have attached a part of dmesg output at the end of the > mail). As reported by some already ( > http://www.mail-archive.com/freebsd-performa...@freebsd.org/msg02446.html), > we are also getting extremely slow write speeds. I read somewhere that there > are some improvements which could solve the situation in 7.2 (our system has > 7.1 installed and I am currently unable to turn it off and it will stay so > for at least 3 months). > > There are some information that setting hw.mpt.enable_sata_wc=1 solves the > write speed (it actually does as I tested!), but I would like to know more > about how danger that option is. We are using softupdates and now have this > hw.mpt.enable_sata_wc=0, after reading that it might be very dangerous when > using sata_wc=1. Not very dangerous at all, as long as you are not using background fsck. The problem with write caching on standard IDE/SATA drives is that they report that a write operation is finished even if it has only reached the disk's cache. This means that some of the guarantees that softupdates is supposed to provide regarding which order data is written to the disk, cannot be fulfilled. This essentially means that if you lose power to the machine unexpectedly you might have some filesystem inconsistencies afterward that you would not have had without the disks' cache being enabled. (A normal reset would not cause this problem since the disks would still retain the contents of their caches.) If you are using background fsck this could be a big problem, since for background fsck to work properly the only inconsistencies on the filesystem must be that some blocks are marked as in use when they actually are not. (That is one of the guarantees that softupdates is supposed to provide, but may not be able to provide due to the behaviour of the disks' cache.) If you do have other inconsistencies on the filesystem the whole system may throw a kernel panic when it encounters one of them. (A normal foreground fsck would fix all such inconsistencies before the system starts running for real.) It is also the case that if your system is really busy writing to the disks (with write caching enabled) and you lose power at exactly the wrong time you could potentially lose a lot of data from the filesystem, since any given write could theoretically get delayed indefinitely before it hits the disk's platters. (If the write that gets delayed is the creation of a directory in which lots of writes happen later you could lose all of them.) If you have write caching disabled you will not lose more than the last 30 seconds or so of updates. Using an UPS is one obvious way of drastically reducing the number of times the machine loses power unexpectedly, and if it is so important that this server is not taken down I assume you already have an UPS, in which case enabling the write caching is essentially riskfree. > > I am really looking forward to getting more information about this, it is > actually driving me nuts. We have a number of other servers and there are no > problems with RAID controllers at all. And as I said, I cannot actually turn > of this machine and bring it back to reinstall new OS. > > Thank you very much for your comments and thoughts, > Matej > > > The server model is ML110G5. > > mpt0: port 0xd000-0xd0ff mem > 0xfcefc000-0xfcef,0xfcee-0xfcee irq 16 at device 0.0 on pci5 > mpt0: [ITHREAD] > mpt0: MPI Version=1.5.16.0 > mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) > mpt0: 1 Active Volume (2 Max) > mpt0: 3 Hidden Drive Members (10 Max) -- Erik Trulsson ertr1...@student.uu.se ___ 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: Pre-compiled package shortage
On Wed, Jun 17, 2009 at 12:59:08AM -0400, David Karapetyan wrote: > Hello everyone. I am a former user of Freebsd-7.2 Release who migrated to > Debian. I was unable to find an ftp server that had a decent enough list of > precompiled packages (including the default at ftp.freebsd.org; for > example, when installing gnome2 via precompiled packages, the package > manager was unable to find a number of dependencies available in package > form. True, I can compile them from source, but this is rather time > consuming. Does anyone know of an ftp server dedicated to maintaining a > comprehensive list of precompiled packages (a la Debian Testing)? In all > other regards, I favor freebsd over Debian or any other linux distribution, > and would like to return to using it. There are a number of ports that for legal reasons cannot be redistributed as pre-compiled packages. Quite possibly you ran into one or more of those. Other than those ftp.freebsd.org (and mirrors) should have a complete set of pre-compiled packages. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Control-Z the Sleep Signal
On Tue, Jun 09, 2009 at 11:42:15PM +0200, Polytropon wrote: > On Tue, 09 Jun 2009 16:30:30 -0500, Martin McCormick > wrote: > > Which signal is sent to a process when one types ^z or > > Control-z? It appears to be SIGSTOP and according to signal's > > man page, this is one signal you can't catch. > > You can check the setting with this command: > > % stty -a > cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; > eol2 = ; erase = ^H; erase2 = ^H; intr = ^C; kill = ^U; > lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; > status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; > ^ > > This entry indicates that ^Z sends the suspend signal. Not quite. It indicates (according to stty(1)) that ^Z generates the SUSP character. The termios(4) manpage (referenced by stty(1)) says that SUSPIf the ISIG flag is enabled, receipt of the SUSP character causes a SIGTSTP signal to be sent to all processes in the foreground process group for which the terminal is the controlling terminal, and the SUSP character is discarded when processed. So it appears to be SIGTSTP which is sent by typing ^Z, which agrees with signal(3) where the SIGTSTP signal is described as "stop signal generated from keyboard" -- Erik Trulsson ertr1...@student.uu.se ___ 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: Opinion request about a file server
On Sat, Jun 06, 2009 at 01:31:16AM +0200, Wojciech Puchar wrote: > > Not counting the CPU and its power circuitry, I would be very suprised if > > the other components on a normal motherboard pulled as much as half of that > > even when under load. > > > > In fact a typical modern desktop computer will, when idle, draw less than > > 100W for the whole system. It is not even difficult to put together a > > system that will stay under 100W even when under load. > > > but power supplies are not really efficient when used at small load. > maybe some newer are better... It is true that most PSUs have their highest efficiency at about half their maximum load and that this efficiency tends to drop very noticeably at very low loads. The efficency of high-quality PSUs has improved quite a bit over the last couple of years though, to the extent that a modern high-quality PSU running at a low load will still have higher efficiency than an ordinary 5-year old PSU had at its best. Be that as it may, when I was talking about the power draw of the whole system, I meant the whole system, including PSU, so any power losses in the PSU are included in the 100W mentioned. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Opinion request about a file server
On Sat, Jun 06, 2009 at 12:43:23AM +0200, Wojciech Puchar wrote: > > Much less than a Pentium 4! Exactly I don't know. This server is a > > normal PC with a 380W PSU (still too much for the hardware). The funny > > thing is that the CPU in it (Pentium Dual Core E5200 45nm) is supposed > > to draw under 4W of power when idle with EIST enabled. This power draw > > unless CPU are constantly loaded it takes minor part of power. maybe your > CPU takes 4W, but other chips on motherboard takes MUCH more. A bit more perphaps, but not MUCH more. The main chipset itself will almost certainly not draw more than 20-25W when working. Less when idle. (If it is a chipset with integrated graphics you can add a few watts to that, but probably not much more than that.) Modern RAM-memory will draw perhaps 1-3W per DIMM, depending on size and technology. The remaing chips does not draw much. (After all they don't generate enough heat to require heatsinks.) The only really power hungry component in a modern system apart from the CPU is the graphic card - and that only when using the more high-end models. > > it would be good to measure it with electricity meter :) i bet close to > 100W Not counting the CPU and its power circuitry, I would be very suprised if the other components on a normal motherboard pulled as much as half of that even when under load. In fact a typical modern desktop computer will, when idle, draw less than 100W for the whole system. It is not even difficult to put together a system that will stay under 100W even when under load. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Intel NIC issues
On Tue, Jun 02, 2009 at 09:56:01PM +0100, Graeme Dargie wrote: > Hi all > > > > Ok lets not go to war over this I just need some advice. > > > > I have a 1u rack system that has one of these motherboards > http://www.supermicro.com/products/motherboard/Xeon/E7501/X5DPR-iG2+.cfm Are you *sure* that you actually have that particular motherboard? As you can see if you look through their product listings ( http://www.supermicro.com/products/motherboard/Xeon1333/#e7501 ) Supermicro has several other similar models, some of which are equipped with one Gigabit NIC and one 100Mbit NIC much like you seem to have.. > > > > Now according to where I got the server and that page it is supposed to > have dual gigabit nics on board. > > > > Dmesg shows the following > > > > em0: port 0x3000-0x301f mem > 0xfc22-0xfc23,0xfc20-0xfc21 irq 31 at device 4.0 on pci3 > > em0: [FILTER] > > em0: Ethernet address: 00:30:48:24:84:f2 > > > > fxp0: port 0x4400-0x443f mem > 0xfc321000-0xfc321fff,0xfc30-0xfc31 irq 17 at device 2.0 on pci4 > > miibus0: on fxp0 > > inphy0: PHY 1 on miibus0 > > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > fxp0: Ethernet address: 00:30:48:24:84:f3 > > fxp0: [ITHREAD] > > > Now for reasons I can not fathom, one nic is showing just fine and the > other is using a different driver and only speeds of upto 100mbs. The obvious reason is that there is two different ethernet controllers on that board - one Gigabit and one 100Mbit. It is worth noting that according to the above, they are found on different PCI-buses, while the dual-gigabit controller you thought you had is a single chip where obviously both ports would be connected to the same bus. > > > > I have tried both 7.1 and 7.2 So is the information on the board wrong > or is there something I am missing. Most likely you have a different motherboard than you think you have. The *complete* dmesg output as well as the output of 'pciconf -lv' might be useful in determining what you actually have. (Opening the box and checking for any useful labels on the motherboard can also of course be useful, but is not something we can help you doing.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: UK Currency Symbol in 7.2 Console
On Mon, Jun 01, 2009 at 08:28:51AM +0100, Graham Bentley wrote: > > keymap="uk.cp850" > Same here! > > > For reporting bugs: send-pr(1). > > This isn't a bug though, as my UK keyboard works fine on 7.2-RC2 > > Lets see thats 1 out 3 of us so far that this doesnt work for > - so ... thats not a bug? > > > Your problem can probably be fixed by: > > # vidcontrol -f 8x16 /usr/share/syscons/fonts/cp850-8x16.fnt > > # kbdcontrol -l /usr/share/syscons/keymaps/uk.cp850.kbd > > Thanks for the reply Frank, but sadly the above makes no > difference at all - I still get a beep, not a pound sign :( >From within which program? It is quite possible that is the program you are using which refuses to accept characters outside standard ASCII. You probably have to set the LC_CTYPE or LC_ALL environment variable to something suitable to make programs accept such characters. (I know it makes a difference for some shells at least.) Using the correct *.fnt or *.kbd files just tell the system which key should generate a character and what it should look like if displayed, not which characters are to be considered printable or not. -- Erik Trulsson ertr1...@student.uu.se ___ 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: find and searching for specific expression in files
On Sat, May 30, 2009 at 11:25:12AM +0200, Zbigniew Szalbot wrote: > Hello, > > Can you please give me a hint how to use find to search for a specific > text within files? Generally, you don't - find(1) does not examine the contents of files by itself, just their directory information. You normally use grep(1) to search within a file. > > I am using find in the following manner: > > find /path/to/files/ -mtime -2 -ls |less > to find files which have been recently modified. But I would like to > extend the search to find specific expression within files. -name is used > to specify file name. How can I search for strings within text? > > It is probably in the man but I somehow overlook it. :( > > Thank you very much in advance! I guess you could use the '-exec' expression in find(1) to execute grep(1) to search for a string in the files examined. Or you could use the output of find(1) as a list of files that are given as arguments to grep(1). -- Erik Trulsson ertr1...@student.uu.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: What is the highest hard drive read/write speed you were able to achieve by entire disk mirroring or striping?
On Mon, May 18, 2009 at 08:07:10PM -0700, Yuri wrote: > Glen Barber wrote: > > No, that is not reasonable (but in a perfect world, would be correct). > > > > You are limited by the bus speed and controller buffer speed > > (whichever is slower). > > > > > My motherboard has PCI Express v2.0, that is 500MB/s limitation. That's 500MB/s for each PCI-E 2.0 lane. The PCI-E lanes originating at your southbridge (Intel ICH10R) are only PCI-E 1.0 however for a max of 250MB/s per lane (in each direction.) This is irrelevant however since the built-in SATA controller is not attached to any PCI-E lanes. What is relevant is the connection between the northbridge and southbridge. In your case that connection is equivalent to a PCI-E x4 bus, for a max speed of 1GB/s (in each direction.) > Also it has HD/RAID controller Intel ICH10R Southbidge that has peak > SATA Data Rate 300MB/s. That's 300MB/s for each SATA channel. Unless you use a port-multiplier (which is poorly supported in FreeBSD) you will only have a single disk per SATA channel. > So this brings me to 300MB/s limit. > So 3X harddrives at 85MB/s will still scale. And 4X will already show > the limitation. Actually the buses involved sets the limit at 1GB/s (the Nortbridge-Southbridge connection.) There are likely to be other limits in play however such as the maximum throughput of the SATA controller, or the max load the CPU can sustain, or the transfer speed to RAM. Of these I suspect the controller itself will be the major bottleneck in your case closely followed by the CPU. Exactly how much they can support is not so easily predicted however - it will have to be measured. -- Erik Trulsson ertr1...@student.uu.se ___ 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: qmail.sh is broken symlink
On Fri, May 15, 2009 at 06:29:27PM -0700, Kelly Jones wrote: > I just installed qmail on my FreeBSD box out of /usr/ports/mail/qmail, > and noticed this: > > # ls -l /usr/local/etc/rc.d/qmail.sh > lrwxr-xr-x 1 root wheel 13 May 15 18:43 /usr/local/etc/rc.d/qmail.sh@ -> > /va\ > r/qmail/rc > > # ls -l /var/mail/rc > ls: /var/mail/rc: No such file or directory > > I read somewhere that this is actually *supposed* to happen + that I > should copy something in /var/qmail/boot to /var/qmail/rc > > My question is: what? There are lots of files in there: > > # ls -l /var/qmail/boot/ > total 24 > -r-xr-xr-x 1 root wheel 483 May 15 18:43 binm1* > -r-xr-xr-x 1 root wheel 567 May 15 18:43 binm1+df* > -r-xr-xr-x 1 root wheel 452 May 15 18:43 binm2* > -r-xr-xr-x 1 root wheel 536 May 15 18:43 binm2+df* > -r-xr-xr-x 1 root wheel 450 May 15 18:43 binm3* > -r-xr-xr-x 1 root wheel 534 May 15 18:43 binm3+df* > -r-xr-xr-x 1 root wheel 340 May 15 18:43 home* > -r-xr-xr-x 1 root wheel 428 May 15 18:43 home+df* > -r-xr-xr-x 1 root wheel 347 May 15 18:43 maildir* > -r-xr-xr-x 1 root wheel 359 May 15 18:43 proc* > -r-xr-xr-x 1 root wheel 445 May 15 18:43 proc+df* > -r-xr-xr-x 1 root wheel 1511 May 15 18:43 qmail-smtpd.rcNG* > Any of those files could actually work. They are all shell-scripts that start qmail, but with slightly different options, or using different support-programs. I can't find a description of exactly what the difference between them is, so you will probably have to look through them to see which one suits your setup best. (There are comments in each of them giving a brief description of what it does.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: single SATA disk and yet identified as 'ad4'
On Mon, May 11, 2009 at 04:30:23PM +0200, Jonathan McKeown wrote: > On Monday 11 May 2009 21:38:50 Saifi Khan wrote: > > Hi all: > > > > The system has just one SATA disk and yet bootloader process > > identified it as 'ad4'. Ideally, it should be ad1. > [snip] > > How does the labelling logic work ? > > FreeBSD reserves numbers for devices that aren't currently connected, so that > if you connect them later your existing devices don't need to be renumbered. It does this if you have 'options ATA_STATIC_ID' in your kernel config (which is the default.) Otherwise all PATA/SATA disks installed will numbered from ad0 upwards without any gaps. The drawback of that is that without the static numbering the disk devices can (and often will) be renumbered if you add or remove a disk, which often is not desirable. > > Your BIOS is reporting two IDE interfaces, each of which could have a master > and slave disk drive, so ad0-3 are reserved for those four drives, meaning > SATA starts at ad4. > > Some BIOSes let you change this. > > Jonathan -- Erik Trulsson ertr1...@student.uu.se ___ 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 7.2 released?
On Sun, May 03, 2009 at 02:47:34PM +0200, Roland Smith wrote: > On Sun, May 03, 2009 at 06:20:40PM +0700, Old Crankbuster wrote: > > * Frederique Rijsdijk [2009-05-03 13:13:23 > > +0200]: > > > > > typicaly the images are uploaded first before the announcements are made. > > > > Hmm. I just installed 7.1 today. Should I download the new iso and > > install fresh, or upgrade? No real mods or extensive configuration has > > been done yet... > > If you haven't invested much time in it yet, install 7.2. Because if you > run into problems with 7.1, that's the first advice you'll get anyway. > > > Wait for the announcement? > > No reason not to use them if the ISO images are available. There is no guarantee that those are the final images (although they likely are.) It has happened before that last-minute problems have been found resulting in a need for images being replaced by fixed ones before the announcement went out. I suggest you wait for the announcement. I believe the official release (and accompanying announcement) is planned for tomorrow, so unless some last-minute problem do pop you should not have to wait all that long. (And if there is some last-minute problem it is probably a good idea to wait until it is fixed.) -- Erik Trulsson ertr1...@student.uu.se ___ 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: Modern FreeBSD Installer?
On Sat, Apr 25, 2009 at 05:45:49PM -0600, Tim Judd wrote:
> Reading the second half of these mailings got me thinking. Thinking of ways
> to detect what CAN be done, and what CAN'T -- based entirely on the hardware
> at boot. I think that we might come to a middle ground to get something
> working. Here's my thought process right now, with hopefully ample samples
> to example my angle (that was fun to say).
>
>
> It's based on two principles. First is the CPU class. If it's a 486 or
> 586, run a pure dialog(3) interface. If it's a slow 686 (and the fudge
> factor to define slow is based on Xorg's *recommended* CPU specs + the
> software installation CPU/RAM needs), run the dialog(3) interface. If it's
> a fast 686, default to a X environment.
As long as you have sufficient RAM (and you don't actually need all that
much of it) running X on an older CPU should not be much of a problem.
(Unless X.org has bloated really badly over the last couple of years.)
>
> Second (which ties into the first) is the hardware that was probed during
> boot-time. If a /dev entry (or even some sysctl) exists for a pci/agp/pci-e
> device, it can run a graphical installer. If it finds none of the graphical
> adapters, and sees serial ports, enable the dialog(3) as well. I feel like
> some pseudo-code might help paint the picture more.
>
>
> text-mode_install = graphic-mode_install = false
> if (CPUCLASS<=586 || CPUSPEED<=(Xorg-suggested-minimums+install
> requirements)) {
> set text-mode_install true
> } else {
> set graphic-mode_install true
> }
> if (found(VGA-graphics) && graphic-mode_install) {
> exec xinstall
> } else {
> # enable console installer
> exec sysinstall
> }
>
>
>
> I seem to find this very logical and can't (yet) see any flaws with doing
> this. sysinstall is built, we'd just need to maintain it and create the
> x-based installer. Run it with a minimalist (twm?) startup so we don't
> waste time booting.
That logic will often do the wrong thing for servers. They are the most
common case where people want to install using a serial console, but
typically do have a (fairly simple) graphical adapter and could run a
graphical installer perfectly well. That does not necessarily mean
that the person doing the install wants to do it.
Better would be to check (somehow) for the presence of a keyboard and a
screen. If those are not present forget about X. If they are present
then the user at least has a possibility of using X.
Also keep in mind that there are graphical adapters/screen combinations
where X will not work correctly without first tweaking configuration files.
Things have improved greatly here in recent years, but it is still
not perfect.
Text mode is still a good deal more compatible with all kinds of weird
hardware.
>
> I've also thought about the concept of a web-ui installer, even if it's run
> from the local machine. The benefit of a webui installer is that you can
> give the disk to someone, tell them to put it up on a publically available
> IP address and just sit back and let it run. but I ramble on
>
>
>
> And also brainstorming now has brought me another idea about installing base
> with the concerns Jordan Hubbard wrote in 2000 mentioned in this thread.
> Again based on the hardware probed (this one being the amount of RAM in the
> box, in contrast to the amount of disk space needed to install on disk),
> create a in-ram disk as the staging area when you write to disk. The other
> idea is to use dump/restore instead of tar files.
>
> It is possible to have a 3GHz machine with 256MB ram as a valid combination,
> but when bin distribution is about 128MB in size, and kernel distribution is
> 128MB in size, and blindly running an X install -- not wise.
>
>
>
> Last idea is to do similar to what Ubuntu (used to) do. Provide a X-based
> installer CD and a console-based installer CD.
>
>
> I'd be happy to provide feedback; these were brainstorming ideas and would
> really like to see progress move toward a more eye-candy installer.
I fail to see what the point of an X-based install would be - other than
pure eye-candy, which does not seem very important for something like an
installer which is used so rarely.
--
Erik Trulsson
ertr1...@student.uu.se
___
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 USB harddrive is so slow under FreeBSD?
On Mon, Apr 13, 2009 at 12:27:27AM -0600, Tim Judd wrote: > On Sun, Apr 12, 2009 at 1:54 PM, Yuri wrote: > > > I have FreeBSD-71 running with USB controller: > > uhci0: port 0xa800-0xa81f irq 21 at device 16.0 > > on pci0 > > > > I connected to it Toshiba USB hard drive HDDR500E03X: > > umass0: on > > uhub4 > > da0: Fixed Direct Access SCSI-4 device > > > > When I try to copy data with 'dd if=/dev/da0s1 of=/dev/null count=1' it > > only achieves has 0.65MB/s transfer speed. > > > > What's wrong, why is it so slow? > > > > Yuri > > > > > uhci is 1.0 devices specs of 12Mbit/sec > ohci is 1.1 devices Not quite. uhci and ohci are both just different ways of accessing USB 1.0 and 1.1 controllers. uhci is used for controllers from Intel and Via, while ohci is used for just about all other controllers. USB 1.0 and USB 1.1 both support 1.5Mbit/sec (Low Speed) and 12Mbit/sec (Full Speed) > ehci is 2.0 devices specs of 480Mbit/sec > > > Seeing various PCs boot and during the probe, typically I see 1 ehci, and > multiple uhci and ohci devices. A normal USB controller chip will provide one or more UHCI or OHCI (but never both) interfaces for handling Low and Full Speed devices and one EHCI interface for handling Hi-Speed (480Mbit/sec) devices. If you have several USB controllers in your computer you can indeed see both uhci and ohci devices as well as several ehci devices. > > > Your Toshiba External USB HDD must have 2.0 speeds to be able to transfer at > that speed... hooking a 2.0 device into a 1.x port will either cause port > shutdown, or a backwards compatible downstep for the device in terms of > speed. > > > Hope this explanation helps. > > --TJ > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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 USB harddrive is so slow under FreeBSD?
On Sun, Apr 12, 2009 at 02:53:42PM -0700, Yuri wrote: > Dan Nelson wrote: > > > > Increase your blocksize. dd's default is 512 bytes. Try bs=64k > > > > This works, I am getting 25-27 MB/s. Still lower than this device > supports (~50MB/s). > I guess because this VIA controller is very old. Although the theoretical max speed of USB 2.0 is 60MB/s it is not actually possible to reach that speed. In practice the best transfer speed one can get over USB is 35-40 MB/s and most of the time not even that. Anything over 30MB/s with USB should be considered quite good, so the 25-27MB/s you are seeing are actually not all that bad. Some other controller *might* give you a few more MB/s but probably not more than that. -- Erik Trulsson ertr1...@student.uu.se ___ 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: powerd
On Wed, Apr 08, 2009 at 04:37:35PM +0100, David Collins wrote: > > Frequency control is not supported in your case. You must > > have dev.cpu.0.freq and so on. What kind of processor do > > you have? Does it support "powernow", "cool'n'quiet" or > > similar features? > > CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x673 Stepping = 3 > > Features=0x383fbff AFAIK that processor does not support changing frequency or voltage on the fly. You will not be able to get powerd to do anything useful with that CPU. > > > > Also, make sure that you have "device cpufreq" > > kernel configuration. If you don't have it, try to load > > the module: kldload cpufreq > > I have device cpufreq in the kernel conf and I loaded/unloaded it separately. > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: going from cvs to svnq
On Wed, Apr 01, 2009 at 07:05:53AM -0300, Andrew Hamilton-Wright wrote: > > [ snippage of question re: svn and cvs ] > > On Tue, 31 Mar 2009, Chuck Robey wrote: > > > Andrew Wright wrote: > >> > >> The primary advantage of using svn is that the _server_ uses a > >> different protocol to track objects. > > > > I think that's unclear, you can't mean that just having the protocol be > > different, that's not that much of a win. Having svn track extra things, > > like > > directories, that I'd think was a win. > > I chose the word protocol poorly. For "protocol" read "way of > doing things", or perhaps "algorithm". > > What I was trying to make clear is that the choice of tool between > cvs and svn is made based on server related criteria. > > > > > What I don't know is, I use cvsup all the time, but when I switch to svn, > > what > > does the "cvsup" job of tracking an archive (not tracking the sources, I > > mean > > the archive)? Does svn do it all itself? If so, I can find out how, I just > > want to know if that's how its done. If not, what's the general tool used > > to > > track the freebsd archive, so I can investigate it? > > If you are asking "what is the name of the subversion client, and how > can I use it?", then the answer is "svn" (which is also the executable > used for the server, a la cvs with the "pserver" option). Usage No, 'svnserve' is normally the executable running on the server. > instructions are available via: > http://subversion.tigris.org > > > If you are asking "what can I type to get a readonly copy of the > repo?", then according to the ROADMAP.txt at: > http://svn.freebsd.org/viewvc/base/ROADMAP.txt?view=markup > the answer appears to be: > svn co http://svn.freebsd.org/base/head No, that is not going to get you a copy of the subversion repository, but just a checked out copy of HEAD. There is no 'svn' command that will give you a copy of the whole repository. Personally I have found 'rsync' to be quite useful in replicating a subversion repository, but that of course requires the server to support it, which is probably not the case for the FreeBSD repo. I don't know if there currently is any supported method for ordinary users to get a copy of the whole FreeBSD subversion repository. I suspect there isn't. > > Strong Caveats: > o One of the peculiarities of subversion is that if you > leave off the "head" portion of the URL, you will get _all_ of > the nodes in the repository -- that is, the history at every point. > > o As I mentioned earlier, this will produce a newly checked out working > space that is incompatible with cvsup (or cvs in general). > > o ***Early Adopter Warning***: There has not been (as far as I know) a > general call for people to move to this type of repository access except > for committers -- therefore expect rough edges until a general > announcement > is made. > > A. > -- Erik Trulsson ertr1...@student.uu.se ___ 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: Question about forcing fsck at boottime
On Tue, Mar 31, 2009 at 04:04:53PM +0100, Chris Rees wrote: > On Tue, 31 Mar 2009 16:00:18 +0530 > manish jain wrote: > > Having bgfsck enabled is like > > inviting a dragon to dinner when this happens. > > 2009/3/31 RW : > > If you've done a normal install, soft-updates aren't enabled on /, > > so it will get foreground checked by default. > > > > If I were you I'd reboot into single user mode and do a full fsck on it. > > > Seriously, why is everyone against background fsck? Can anyone give a > good reason? Please? For background fsck to work as it is supposed to, it is necessary that only certain errors can occur on the filesystem. Other types of errors cannot be corrected by a background fsck. To make sure that only the allowable errors can occur it is necessary for soft updates to be used and working as it is supposed to. For soft updates to work as it is supposed to the disk subsystem must provide certain guarantees on when and in which order blocks are written. Normal PATA/SATA disks with write caching enabled (which is the default) do not provide these guarantees. Disabling write caching on will make them adhere to the assumptions that soft updates make, but at the cost of a severe performance penalty when writing to the disks. In short therefore on a 'typical' PC you can fairly easily get errors on a filesystem which background fsck cannot handle. It is also the case that background fsck relies on snapshots to work, At least in the past snapshots had stability problems. Things are supposed to be better these days, but many people have long memories for these kind of problems. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Text mode dialog library like TSO
On Fri, Mar 20, 2009 at 12:36:31AM +0100, Polytropon wrote: > On Thu, 19 Mar 2009 16:22:01 -0700, Chuck Swiger wrote: > > Consider looking at dialog(3), which rides on top of ncurses. > > There's also a CLI utility by the same name handy for shell-scripting > > purposes. > > Allthough dialog does come with the basic means I did describe, > it looks a bit... bulky? I don't want to sound impolite, but > consider the width of > > ++ > Name: || > ++ > > to > > Name: > > which would be more... elegant. But "man dialog" is very interesting. > It even offers functionalities (lists, yes/no buttons etc.) that > I haven't thought of. > > Thank you, I'll take this into mind. Another alternative might be the form(3) library which also is built on top of ncurses. It seems to be a bit more cumbersome to use than dialog(3) but is probably somewhat closer to what you were looking for. If you look around a bit on the web you can probably find several tutorials and references for both curses as well as the form, menu. and panel libraries that are usually included with most curses implementations (including ncurses.) See for example http://tldp.org/HOWTO/NCURSES-Programming-HOWTO/ -- Erik Trulsson ertr1...@student.uu.se ___ 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: links vs real directories
On Mon, Mar 16, 2009 at 11:47:23AM -0400, John Almberg wrote: > > On Mar 16, 2009, at 11:39 AM, Erik Trulsson wrote: > > > On Mon, Mar 16, 2009 at 11:22:13AM -0400, John Almberg wrote: > >> I always thought that links to real directories were pretty much the > >> same as real directories, but I've just discovered a situation where > >> they are not and I'm wondering if I'm doing something wrong... > > > > A *soft* link to a directory entry (be it a directory or a file or > > something > > else) is not quite equivalent to the original entry since they are > > easily > > distinguished and some programs do treat softlinks differently from > > other > > targets. > > I can see that, now... If I create a soft link to ~/shared/config, > and then cd into the directory, when I type 'ls ..', I get the > listing for ~/shared, not ~/app. Yes, because '..' is a hardlink to the parent directory, and 'cd' does not know how you got to ~/shared/config so it does not know anything about the softlink used to get theere. > > Bummer... > > I've just dug through man ln, and don't see any obvious solution. > Since this must be a problem for anyone who wants to do something > like this, I guess I am taking the wrong approach, altogether. > > Will have to re-think this > > > > -- John > -- Erik Trulsson ertr1...@student.uu.se ___ 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: links vs real directories
On Mon, Mar 16, 2009 at 11:22:13AM -0400, John Almberg wrote: > I always thought that links to real directories were pretty much the > same as real directories, but I've just discovered a situation where > they are not and I'm wondering if I'm doing something wrong... A *soft* link to a directory entry (be it a directory or a file or something else) is not quite equivalent to the original entry since they are easily distinguished and some programs do treat softlinks differently from other targets. A hardlink to a file is exactly equivalent to the original (since the original directory entry is itself a hardlink). The system does not however allow you to create hardlinks to directories since it is far too easy to make Very Bad Things happen that way. > > I have a Ruby on Rails application running on a FreeBSD server. All > Rails apps use the same directory structure, that consists of an > application directory, plus a number of subdirectories. One of these > sub directories is called 'config'. > > I would like to move this config directory out of the main Rails app > directory, and then add a link from the app directory to the moved > config directory. > > so: > > app --> config > > will become > > app --> config(link) --> config > > Basically, what I'm doing is: > > cd ~/app # now in directory with real 'config' dir > mv config ~/shared/config > ln -s ~/shared/config config > > That moves the directory and creates a functional link to it (I > tested it), but Rails doesn't like it and refuses to run the app. The > permissions are correct, I believe: > > [mas...@on:current]> ls -l > total 34 > ... snip ... > drwxrwxr-x 3 master master 512 Mar 16 11:06 bin > drwxrwxr-x 3 master master 512 Mar 16 11:06 components > lrwxr-xr-x 1 master master26 Mar 16 11:07 config -> /home/ > master/shared/config > drwxr-xr-x 4 master master 512 Mar 16 11:06 db > etc... > > > So, I guess a link is NOT exactly equivalent to a directory. At least > not the way I am doing it. > > I'm guessing I'm making a real newbie mistake, so if anyone can set > me straight, I'd appreciate it. > > Thank: John > -- Erik Trulsson ertr1...@student.uu.se ___ 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: Advise on PCIX dual network card
On Mon, Mar 16, 2009 at 03:28:03PM +0700, Olivier Nicole wrote: > Hi, > > I need to buy a PCI eXtended dual network card, any advise on what > brand is supported and work reliabily? The Intel PRO/1000 series should all work fine. -- Erik Trulsson ertr1...@student.uu.se ___ 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: issues in XFCE 4.6
On Sat, Mar 14, 2009 at 03:43:53PM -0600, Keith Seyffarth wrote: > > > As i said the packages worked for me. Blow away the xfce and xorg ports > > and do the xorg mega package and the xfce mega package. if that fails > > then bkup your user data and install a clean virgin version of 7.1 and > > the xorg and xfce packages. > > It looks like this was a step in the WRONG direction. Having removed > XORG, it won't install. It appears that xorg requires xorg-drivers > (understandable), and xorg-drivers requires xf86-video-via (OK), and > xf86-video-via requires a PCI Video Card to be installed. xorg-drivers requires the drivers it has been configured to depend on, which does not necessarily include xf86-video-via. Go to the xorg-drivers port and do a 'make config' to change which drivers it will depend on. > > make clean install -k in x11-drivers/xorg-drivers will make > xorg-drivers install, but make clean install -k in x11/xorg won't > install because xf86-video-via is ignored. > > Anyone have another suggestion? At this point, I need to get X > installed so I can even consider a window manager. > > Keith S. > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: Binary upgrade 7.1 i386 -> amd64 ?
On Fri, Mar 13, 2009 at 09:05:12AM +0100, Frederique Rijsdijk wrote: > I'm planning to binary upgrade a machine that's now running i386 > 7.1-RELEASE-p3 to AMD64. Mainly because the machine has 8GB of memory > and I don't like the PAE limitations. > > I've done this a couple of times before with 4.x -> 6.x but all remained > i386. > > Are there any pitfalls when doing an upgrade of i386 to amd64 or should > it be the same as any binary upgrade? I don't know if a binary upgrade from i386 to amd64 is even possible, but I am fairly certain it is not supported. Source upgrades from i386 to amd64 are possible, but not trivial and not recommended. The recommended procedure for changing from i386 to amd64 is to make a backup of all important data on the machine, and then do a fresh install of amd64 after which any needed data is restored from the backup. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Which install ?
On Mon, Mar 09, 2009 at 02:15:25PM -0400, Michael Powell wrote: > Erik Trulsson wrote: > > > On Mon, Mar 09, 2009 at 11:25:06AM -0500, Darryl Hoar wrote: > >> Greetings, > >> I just purchased an older rack mounted supermicro server. It is running > >> CentOS, but I want to install Freebsd on it. > >> The server has (2) Xeon processors. Which download should I use ? i386 > >> ??? > >> > > > > If it is an older server then i386 is probably the right version to use. > > The recent processors from Intel that use the 'Xeon' name also support > > amd64, but older ones did not. > > > > > > > > > > If memory serves, the first Xeon to be 64 bit was the Nocona. Xeons prior to > that were 32 bit and came in OLGA 603 sockets. In early 2001 they were 1.4 > to 1.7GHz units, and later that year the speeds ramped up. There have been many 'Xeon' processors before that. The first ones were the Pentium II Xeon for Slot 2 and ran at a most impressive 400 MHz. There have been many variants after that using Slot 2, Socket 603, Socket 604, Socket 775, Socket 771, and probably some more socket type which I have missed. The Slot 2 and Socket 603 models do not have 64-bit support. Some of the Socket 604 models have 64-bit support, while I believe all the Socket 775 and Socket 771 models have 64-bit support. See http://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors for what looks like a fairly complete list of them all, which should illustrate fairly well why it is pretty much meaningless to just say that you have a 'Xeon' processor. -- Erik Trulsson ertr1...@student.uu.se ___ 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: Which install ?
On Mon, Mar 09, 2009 at 11:25:06AM -0500, Darryl Hoar wrote: > Greetings, > I just purchased an older rack mounted supermicro server. It is running > CentOS, but I want to install Freebsd on it. > The server has (2) Xeon processors. Which download should I use ? i386 ??? > If it is an older server then i386 is probably the right version to use. The recent processors from Intel that use the 'Xeon' name also support amd64, but older ones did not. -- Erik Trulsson ertr1...@student.uu.se ___ 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: USENET?
On Sun, Mar 08, 2009 at 04:16:46PM -0700, Gary Kline wrote: > > are there any ports that offer an interface to USENET? I think mozilla > did, but that was a long time ago ... . Look in ports/news for a whole bunch of reader and server software that can be used to read and/or distribute the various newsgroups available on Usenet. (And several of the more popular web-browsers can also be used as newsreaders.) -- Erik Trulsson ertr1...@student.uu.se ___ 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 do I determine the FreeBSD "world" revision/version?
On Fri, Mar 06, 2009 at 03:12:26PM -0500, Ian Bonnycastle wrote: > Good afternoon everyone, > > I'm asking this question here because I honestly don't know where to turn to > otherwise. I've looked through forums, Google search results and the FreeBSD > handbook without a specific answer. I understand the concept that FreeBSD is > actually an OS, which is a combination of the kernel and the "world". Ports > are the extraneous userland which is not mandatory for a working system. > Now, in order to explain my question, I have to use an analogy: In Linux, > you can have a kernel version, a distribution version and software versions. > If you're running kernel 2.6.20, CentOS (as an example) 5.1, and bash > (another example) 3.2, you know that upgrading can occur at any of those > levels. > > My actual question is this: Is there a way to tell what version of the > FreeBSD world you're running outside of "uname -a", which tells you what > *kernel* version you're running? I do know that any of these can be patched > to different levels outside of what you've installed from scratch (or > upgraded to at any particular level), but with Linux, when you run the > respective commands, you get the *base* revision you started from. In > FreeBSD, "uname -a" gives you the kernel "base", and "pkg_info" will give > you the software revision base for a particular port/package. If I have a > particular FreeBSD system, and know its a modified kernel, how can I tell > what base was originally on it? I've often updated the kernel on a > 7.1-RELEASE to 7-STABLE to get more recent updates to the kernel, but the > base as been left at 7.1-RELEASE. Now, it could have been 7.0-RELEASE or > 7.x-RELEASE and after upgrading the kernel, is this informaiton stored > anywhere? No, there is no such information. The version stored in the kernel applies to both kernel and userland. If you do 'mix-and-match' where different parts of your system come from different versions of FreeBSD you will have to keep track of this yourself. Having kernel and userland from different FreeBSD versions is not supported and can somtimes cause problems. -- Erik Trulsson ertr1...@student.uu.se ___ 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: zfs raid and/or hardware raid..
On Wed, Feb 11, 2009 at 10:18:42PM +0100, Wojciech Puchar wrote: > > RAID implementations (and most of the cheaper add-on RAID cards.) RAID that > > is supported in the BIOS have one advantage over other software > > implementations, and that is that you can boot from all supported RAID > > configurations, which is not always the case otherwise. > > always - if you use software RAID (gmirror) properly. gmirror handles only RAID-1 if I am not mistaken. That is the exception where you can boot from a RAID array even the BIOS does not know about it. (But I would worry about what would happen if you were trying to boot from a degraded RAID-1 array. What happens if the BIOS tries to boot the wrong disk?) For a RAID-0, RAID-5, or RAID-10 array on the other hand, I think it is not possible to boot from them unless you have a BIOS which understands the array format. -- Erik Trulsson ertr1...@student.uu.se ___ 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: zfs raid and/or hardware raid..
On Wed, Feb 11, 2009 at 12:58:04PM -0500, B. Cook wrote: > I have a dimension 9150 that I am going to put amd64 freebsd on to play > with. > > It has Intel ICH7 SATA300 on it, in the bios it says it can do raid. > > I'm assuming that would be a hardware raid.. You are assuming wrong. It is software RAID, just like almost all on-board RAID implementations (and most of the cheaper add-on RAID cards.) RAID that is supported in the BIOS have one advantage over other software implementations, and that is that you can boot from all supported RAID configurations, which is not always the case otherwise. > > Would I be better off just using two disks and mirror them in software > raid (zpool) or using the Intel hardware-ish raid and then zfs the raid? > > box has 2G of ram, and a pair of 250G sata 300 drives. > > clues appreciated. ZFS still feels a little bit too experimental for my own tastes (although opinions differ on that matter), but apart from that ZFS is probably the best solution. -- Erik Trulsson ertr1...@student.uu.se ___ 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: OT: how many rankmount units is a tower-case
On Sun, Jan 04, 2009 at 12:42:02PM -0800, per...@pluto.rain.com wrote: > > If a hard disk formatted and used in a position , in that position > > it may be used if manufacturer is NOT advised a specific position. > > After loading of files into hard disk , change of position may > > cause difficulty in reading of already recorded data . This point > > should be considered . > > Sun, at least, used to warn about this back in the MFM/ESDI days, > recommending that a disk should be reformatted if its orientation > were changed, but those drives used all their heads for data and > depended on reproduceable mechanical positioning to align the heads > at the selected cylinder. I'm not sure it still applies to drives > that dedicate one head to fine-tuning track position by reading > factory-recorded servo patterns. (Quick check, if "actual" geometry > is known: a drive with an odd number of heads most likely has a > dedicated servo surface.) BTW most drives of that era, while OK on > either side as well as "right side up", were *not* supposed to be > run "upside down" -- the bearings were not designed for that. That may well have been true back in those days, but reasonably modern drives[*] do not have those limitations. Todays drives can be mounted in any orientation, and should have no problems being remounted in a new orientation. >From Western Digital's FAQ: Physical mounting of the drive: WD drives will function normally whether they are mounted sideways or upside down (any X, Y, Z orientation). Of course, the physical design of your system may limit the positions in which the drive can be mounted. However, in all cases, you should mount the drive with all four screws for good grounding. Also ensure that there is enough air space around the drive for adequate air flow, and avoid mounting the drive near sources of excessive heat (such as some CPUs). >From Seagate's FAQ: All Seagate & Maxtor's internal hard drives can be fitted sideways or upside down. As long as they can not be moved during use and get enough cooling it is irrelevant in which direction they are mounted. >From Hitachi's installation guide: There are many variations of system cases. Hitachi Deskstar drive can be mounted with any side or end vertical or hori- zontal. Do not mount the drive in a tilted position. [*] "resonably modern drives" includes just about all drives any sane person would even consider using for a new computer build. -- Erik Trulsson ertr1...@student.uu.se ___ 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: OT: how many rankmount units is a tower-case
On Sun, Jan 04, 2009 at 08:30:50AM -0500, Glen Barber wrote: > On Sun, Jan 4, 2009 at 8:21 AM, Aryeh M. Friedman > wrote: > > I have a server that is a full tower case and want to co-locate it and > > all the providers list pricing in rackmount units so what value of x > > in xU should I get? > > When it comes to rackmounts, 1U = 1.75 inches. 2U would be 3.5 > inches, etc. I'll let you do the measuring and math. ;) It might be worth noting that 1U corresponds exactly to the height of a typical bay for 5.25" units. A normal tower case when lain on the side normally has a height of approximately 4U. Note though that most tower cases are not designed to be rackmounted and will not fit in typical rack. There are some cases available though that can be used both as floor-standing towers, or as rack-mounted cases. I suspect that many co-location services either only accepts rack-mountable servers, or charge extra for non-rackmounted cases, so it might be worth checking that. -- Erik Trulsson ertr1...@student.uu.se ___ 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: OT: how many rankmount units is a tower-case
On Sun, Jan 04, 2009 at 02:48:30PM +0100, Peter Boosten wrote: > > > On 4 jan 2009, at 14:35, "Glen Barber" wrote: > > > On Sun, Jan 4, 2009 at 8:33 AM, Aryeh M. Friedman > > > >> Small related question is there any long term harm to laying a disk > >> on > >> it's side (i.e. it lays flat when the tower is up right but on it's > >> side > >> squeezed into a rack) > >> > > > > The ideal answer is 'no'. The 'safe' answer is 'possibly'. In other > > words, I wouldn't do it personally, but I don't expect it to cause > > harm. I'd suspect it'd be more succeptible to a head crash in a > > vertical position. > > > > > > Most drives in an drive array are on their side, seems not to be any > problem. And if you ask the various harddisk manufacturers they will say "It will work fine. No problem." when asked if it matters if a disk is mounted horisontally or vertically or upside down. -- Erik Trulsson ertr1...@student.uu.se ___ 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 FreeBSD not popular on hardware vendors
On Mon, Dec 15, 2008 at 01:49:57PM +0100, Wojciech Puchar wrote: > > > > I think the list you're looking for when you talk about only discussing > > the base-system already exists (probably stable or arch). This is > > freebsd questions- and the nature of the list according to the > > all-knowing handbook IS for newbies, people who probably won't > > understand the difference between third party and base. > > there is freebsd-newbies for this. > > this group is "freebsd-question" = questions about FreeBSD. Not quite. It is also the list one should use to ask FreeBSD-related questions when one is not sure which list is most appropriate for that particular question. I.e. "freebsd-quesitions" is for all FreeBSD-related questions, not only questions about the FreeBSD base system. -- Erik Trulsson ertr1...@student.uu.se ___ 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: 7.1 - with x.org 7.4?
On Tue, Dec 09, 2008 at 02:17:27PM +0100, Ewald Jenisch wrote: > Hi, > > Does anybody out there know if FreeBSD 7.1 will come out with X.org > 7.4 (or still 7.3)? > > Thanks much in advance for any clue, > -ewald X.org 7.4 has not been imported into the ports system yet, and this far into the release process it is too late to update such an important port - too much risk of something going wrong. The X.org port(s) will probably be updated to 7.4 not too long after FreeBSD 7.1 has been released and the dust has settled. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange behaviour of the filesystem on FreeBSD-5.5
On Tue, Dec 09, 2008 at 12:51:18PM +0300, wrote: > Hello. > -- > I have a trouble with /var filesystem on FreeBSD 5.5-RELEASE-p20 (upgraded > from 5.2 to 5.3, and then to 5.5 some days ago): > 'df -h' shows: > Filesystem SizeUsed Avail Capacity Mounted on > /dev/ad0s1d248M138M 90M61%/var > 'du -s /var' shows: > 28M/var > I'm sure, that there can not be 62Mb of technical info on such small > partition. So, probably there is a bug in soft-updates, or some another > thing, that i can't understand. Free space on /var reduces with time, and > after three days there are no free inodes. But after i reboot my machine > (and background fsck makes it's job), things are good again, du and df are > in agreement about sizes of filesystems. > > Also i tried to verify, that there are no files, which are deleted, but > still occupy place in filesystem (i.e., when some process still use it's > filehandle). The output of 'lsof +D /var' shows *only* existent files on > /var filesystem. Are you sure that lsof can determine the correct directory for deleted files that still exist? They do not reside in any directory any longer after all. I strongly suspect that your problem is indeed files that have been deleted but are still in use by some process (all the symptoms fit), but that your method of finding such files is insufficient. Reading the lsof(8) manpage makes me think that 'lsof +aL1 /var' will list the deleted-but-still-existing files you are interested in. (Given as an example in the description of the +L option.) > Can anybody, please, give me some advice about how to fix this VERY > annoying problem, since this FreeBSD box is our enterprise's router, and i > sometimes must go to office and reboot it even on holidays. Maybe, > reinstalling everything from scratch would be the simplest thing to do, > but i still hope, that somebody can tell me how to fix everything 'in > place'. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: some ipfw filter does not function under Release 6.3
On Sat, Nov 15, 2008 at 01:38:02PM -0800, Jin Guojun[VFF] wrote: > Below is set of ipfw rules, but it seems that not all rules are > functioning properly. > From rule 361 to first two of rule 567 are not blocking any traffic and > not measuring any traffic. > Is this bacuse tcp rule )330) can overwrite the ip rule? or this is a > known issue in R-6.3? In general the first matching rule is the one that is applied. In your case this means that if a packet matches your rule 330 then it will be allowed through, and the rules further down the list will not be considered. > > The second and third rules in rule set 567 seem working well. > > -Jin > > ipfw rule sets - > 00330 3108378 2700826874 allow tcp from any to any established > 00361 0 0 deny ip from 203.83.248.93 to any > 00361 0 0 deny ip from 72.30.142.215 to any > 00567 0 0 deny ip from 193.200.241.171 to any > 00567 0 0 deny ip from 221.192.199.36 to any > 00567 3180 deny ip from 118.153.18.186 to any > 00567 3180 deny ip from 203.78.214.180 to any > 00567 0 0 deny ip from 118.219.232.123 to any > 65500 220 20043 allow udp from any to any > 65535 2120 deny ip from any to any > > -- traffic captured by tcpdump behind ipfw machine - > > 04:12:20.940095 IP 221.192.199.36.12200 > 192.168.2.14.80: S > 200229998:200229998(0) win 8192 > 04:12:21.204430 IP 221.192.199.36.12200 > 192.168.2.14.80: R > 20022:20022(0) win 0 > 04:31:16.262402 IP 221.192.199.36.12200 > 192.168.2.14.80: S > 200233658:200233658(0) win 8192 > 04:31:16.541868 IP 221.192.199.36.12200 > 192.168.2.14.80: R > 200233659:200233659(0) win 0 > 05:27:04.031434 IP 221.192.199.36.12200 > 192.168.2.14.80: S > 200244634:200244634(0) win 8192 > 05:27:04.303262 IP 221.192.199.36.12200 > 192.168.2.14.80: R > 200244635:200244635(0) win 0 > 05:28:18.099443 IP 221.192.199.36.3362 > 192.168.2.14.80: S > 2422872529:2422872529(0) win 65535 > 05:28:18.352083 IP 221.192.199.36.3362 > 192.168.2.14.80: . ack > 3968474717 win 65535 > 05:28:18.367745 IP 221.192.199.36.3362 > 192.168.2.14.80: P 0:205(205) > ack 1 win 65535 > 05:28:18.621538 IP 221.192.199.36.3362 > 192.168.2.14.80: R 205:205(0) > ack 473 win 0 > -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Server Freezing Solid
On Wed, Nov 12, 2008 at 11:26:15AM -0500, Michael Powell wrote: > Chris Maness wrote: > [snip] > >> For this reason, I'd advise that either you leave the PC unplugged for > >> 10 minutes or so after you've cleaned it to let any residual moisture > >> dry, or purchase an inline water filter. > > Should always put a drier on a compressor. You'll learn the hard way if you > invest in pneumatic tools; you will kill them if you don't. > > [snip] > > I ran > > into a couple of post stating that the Abit VP6 had issues with > > components that fail. This seems to have happened. The old 1U box I > > switched the hardrive to yesterday is working flawlessly. However, > > this machine is a little on the underpowered side. > > > > Without actually checking, if memory serves there were a number of products > from that time frame that used inferior electrolytic filter caps. You can > easily spot these by examining the top where there is metal showing through > in the center surrounded by the plastic wrapper. In the caps that fail the > plastic wrapper part will be swelled up and puffy looking, possibly even so > far as to have cracks with goo oozing out of them. > > I have an Abit KD7A powering a small home development server that I've been > really lucky with, it just sits there and keeps on doing it's thing. But I > have a feeling you may have hit the bad cap problem with the VP6. See http://www.badcaps.net for much more information about problems with bad capacitors, and yes the Abit VP6 is one of the boards that commonly exhibits that particular problem. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS2 limits
On Sun, Nov 09, 2008 at 12:33:06PM -0600, Modulok wrote: > >>Personally I cannot think of any situation where one would actually want > (let alone need) as many as 3 or more subdirectories in a single > directory. > > "No one will ever need more than 640K of memory!" Not quite the same thing. One major problem with having lots of entries in a directory is for humans using it (who have not become significantly faster or more capable over the recent decades.) Having lots of entries in a single directory is simply very unwieldy. There are is a reason why people invented hierarchichal files systems with directories and sub-directories, you know. For those situations where the directory is not intended to be looked at by a human, but only by programs, then there are more efficient ways of storing the data if you need that many entries. (A real database system, for example.) Besides, most (all?) of the situations where one might concievably want many entries in a single directory, what one would usually want is lots of files, not lots of sub-directories - once you start using sub-directories, you might as well use more than a single level of them. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS2 limits
On Sun, Nov 09, 2008 at 01:58:11PM -0500, Robert Huff wrote: > > Erik Trulsson writes: > > > > Question (for anyone who has an informed opinion): > > > If there any technical reason that couldn't be expanded to 32 > > > bits? Or is it possible but not done for historical or > > > policy reasons, and if so what are they? > > > > It probably could be expanded to 32 bits if that was deemed > > useful. Doing that would of course require re-creating any > > existing filesystems since the on-disk format would change, which > > would be a PITA for users, but certainly possible. > > I seem to remember at least one case (3.x -> 4.0 ) where a > major version change had no upgrade path - to get the new stuff you > had to reinstall. You are probably thinking of the 4.x -> 5.x upgrade where you pretty much had to reinstall if you wanted to switch from UFS1 to UFS2. (But you could of course keep using UFS1 if you wanted.) > But I agree there's no reason based on current evidence to do > this. > Thanks. > > > Robert Huff -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS2 limits
On Sun, Nov 09, 2008 at 12:48:51PM -0500, Dan wrote: > Erik Trulsson([EMAIL PROTECTED])@2008.11.09 17:53:14 +0100: > > Personally I cannot think of any situation where one would actually want > > (let alone need) as many as 3 or more subdirectories in a single > > directory. > > I've seen some Java apps that use the FS as the DB. Nothing wrong with > that. I think an FS can be quite a good DB, if implemented well. This gives > many data manipulation options with traditional FS tools, shell > scripts, etc. Lets just say that there are reasons why the major database systems generally use their own methods to store and organize the data rather than rely on the file system for that. Besides, for most database applications I can think of, what you would need are lots of *files*, which do not have any special limitations other than the the total space and number of i-nodes on the filesystem. Even if you were using the FS as a DB I can't think of any good reason to need 3+ subdirectories in a single directory. > > Large Maildirs for postfix and qmail/Courier. Some people don't delete > email at all. Again, that requires lots of files, not lots of subdirectories. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS2 limits
On Sun, Nov 09, 2008 at 11:02:07AM -0500, Robert Huff wrote: > > Wojciech Puchar writes: > > > the limit is 32765, just because link count is 2 bytes wide and > > each subdir adds two to base directory. you have to change to 2 > > level hierarchy. > > Question (for anyone who has an informed opinion): > If there any technical reason that couldn't be expanded to 32 > bits? Or is it possible but not done for historical or > policy reasons, and if so what are they? It probably could be expanded to 32 bits if that was deemed useful. Doing that would of course require re-creating any existing filesystems since the on-disk format would change, which would be a PITA for users, but certainly possible. It is rare that anybody actually encounter this limit however. I would even say that if you have more than a couple of thousand entries in a single directory, then you are probably doing something wrong. Personally I cannot think of any situation where one would actually want (let alone need) as many as 3 or more subdirectories in a single directory. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: UFS2 limits
On Sun, Nov 09, 2008 at 10:47:11AM +0100, Polytropon wrote: > On Sun, 9 Nov 2008 10:35:21 +0100, Erik Trulsson <[EMAIL PROTECTED]> wrote: > > Note that this does not limit the number of files you can have in a single > > directory, since normal files do not contain hardlinks to the parent > > directory, but there are of course limits to the total number of files and > > directories you can have on a single filesystem based on how many inodes > > were created when the filesystem was first created. > > Maybe this sounds stupid, but... given that a file system > can hold n entries. What happens when a program tries to > create file number n + 1? > > I do ask this in order to explore if this could have been > the reason for my massive data loss and UFS file system > corruption. I haven't tested what actually happens, but what should happen is that the attempt to create file n+1 will simply fail with some appropriate error code (see open(2) or mkdir(2) for details.) It is certainly not supposed to cause any kind of files system corruption. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
