Search results

You might be able to make the linux version (edit: I mean the linux version of skype, since that's what you seem to want to run) work, if you fiddled with it enough.

As mk hints at, download the floppies for 7.3 and when syinstall starts, go into the options and change the release to 8.1-RELEASE. As long as you keep in mind that you cannot use dangerously dedicated disks with 8.x (I think 7.x still allows their creation) you should be fine.

Well, from this it looks like the latest version is based on Linux 2.6. Bummer.

FreeBSD's ARM port looks a bit rough, to say the least: http://www.freebsd.org/platforms/arm.html Installation also isn't just a matter of running an installer and rebooting: http://people.freebsd.org/~cognet/arm.html Though given the Chinese and their Kylin, there might be some development...

As I think about it, why not just install FreeBSD and take advantage of jail to custom tailor a redistribution? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Also, if you have the inclination, check out what GhostBSD, PC-BSD, & DesktopBSD have done. I'm not suggesting...

Submitting a pr does seem like the logical next step (& prs aren't just for massive, Earth-shattering problems in any case), though I don't see #1 & #3 as mutually exclusive. As for #2, I have an irrational fear of non-optional options.

Indeed. AFIK _all_ externally plugged in storage on FreeBSD is through scbus and da. In any case, unless you really know for certain that you'll never use it (embedded devices, for instance) or you really desperately need to save a couple 100K in your root directory do not remove basic SCSI...

Or grab all of the ssys.?? in ftp://ftp2.freebsd.org/pub/FreeBSD/releases/i386/8.1-RELEASE/src/ (wget is great for this), cat them together and tar out the resulting stream (or file)*. *(see ftp://ftp2.freebsd.org/pub/FreeBSD/releases/i386/8.1-RELEASE/src/install.sh for how this is done...

I think you're talking about the difference between static- and dynamic-linking. http://en.wikipedia.org/wiki/Static_build A dynamically-linked build for firefox isn't going to be hugely different, size-wise on either FreeBSD or Linux. (Well, maybe. The .deb for firefox 3.6 on i386 ubuntu...

I thought source was a csh builtin Oughtn't that be . ~/.bashrc or is my memory of Bourne syntax obsolete?

And SCO, Xenix, IRIX, AIX, OSX (why didn't Apple stay with the theme of the old Apple ][ and spell it "OS><"? I don't know either), True-64 (or whatever they last called it), etc.

I'm glad somebody got the joke. ;) Edit: I should footnote that the reason I threw ARM into the mix is that it's one of the fastest growing markets right now. Obviously prediction is quite difficult (especially about the future), but having ARM as a tier-1 architecture might be a good bet.

Reset the owner/group/permissions on your ~/.profile and don't use sudo when editing your user files? You could also put the TMPDIR statement in your global /etc/profile, if you're so inclined.

Without swap, 6G is probably enough, but you have to keep a close eye on stuff.

Linux has nothing to do with Unix other than copying the look & feel (& a bunch of the command syntax) from its use of the GNU toolset. FreeBSD relies on some of the legacy BSD tools (which have obviously been rewritten over the years) which were once distributed along with Unix as BSD. Note...

for zsh, cat /dev/urandom >> .zshrc If you want things to use /tmp/tmpfs/ for temporary storage, set TMPDIR in your shell startup. For [t]csh echo "setenv TMPDIR /tmp/tmpfs" >> .cshrc; for bash echo "export TMPDIR=/tmp/tmpfs" >> .profile.

Here we go, a small test: > df -h /home/tmp/tmpfs* Filesystem Size Used Avail Capacity Mounted on tmpfs 17G 4.0K 17G 0% /home/tmp/tmpfs0 tmpfs 17G 4.0K 17G 0% /home/tmp/tmpfs1 tmpfs 17G 4.0K 17G 0%...

Sort of. I'd assume it's also somewhat like the virtual mountpoints in zfs that draw from a common pool of storage. So the sum of the used space in all of your tmpfs mounts can't exceed your available swap+RAM. If that makes any sense.

Yes, but do let me know how large of a filesystem it allocates without a size argument. Ah, from /usr/src/sys/fs/tmpfs/tmpfs.h Therefore, the amount of memory to be * used is either the limit imposed by the user during mount time or the * amount of available memory, whichever is lower. To...

Ah, I see, yes, thank you for that hint. The size= argument must be in bytes or it is ignored. With ~15G of swap and 4G RAM my machine uses a 17G tmpfs by default. I'll have to fiddle with the inodes= argument to see what that does.