Discussion in 'Off-Topic' started by sossego, Mar 18, 2012.
And what are you learning now?
Setting up a system.
Avoid flash-based websites
Setting up the base system and installing software using pkg_add.
How to add users.
How to use vi.
t'Is a lot more simple than Linux.
How to mount partitions.
Off Topic. Why is flash considered bad? Do you mean sites that are entire flash based? What are your alternatives for YouTube? I've tried HTML5 its not as fast.
That linux is not as UNIX like as it could be.
That FreeBSD's organisation (in terms of /usr/local ) is awesome and very convenient.
That building everything from source takes longer than I thought it would... :e
That I can't stand the c-shell.
Heavyweight plugin needed to run it. Doesn't work everywhere. Won't run on mobile well, if at all. Proprietary to Adobe so you rely on Adobe to keep it up to date (which they don't).
Google will eventually switch everything to HTML5 audio/video. Browsers are just now coming up to speed with those elements. If you have hardware acceleration turned on, it's just as fast as Flash. Not all browsers have that.
Years ago it was something that was difficult to set up or didn't work at all. When it worked it was limited to youtube videos. Games and rich media no doubt would never work due to adobe not supporting FreeBSD.( I'm assuming that this may have changed).
Binary blobs tends to break the core conventions of open source ideals and the hacker ethic. Flash cookies used for tracking and data mining are outside the browser and therefor cannot be controlled from within browser without installing a addon.
Adobe products have been known to to have some very bad security flaws which they are slow to fix. Even adobe reader can execute code (js if I am correct) which opens up the door for trojans and other "bad things" where executable code should stay far away from or user interactive in allowing the executable from their "trusted" source. Maybe they didn't learn from M$ issues over the years where an application level exploit can propagate from a user opening what would seem like a friendly and useful document.
(Disclosure: I purchased Macromedia stock years ago during the bubble. It was later converted to Adobe. I advised my parents to buy apple. Looking back I should have taken my own advice)
For the OP:
I believe the most important thing I have ever learned from our community (as well as how this OS is designed) is to take the time to learn the standards because knowledge is ALWAYS portable. Reading man pages is essential for every one on unix system. If and when you fail... try and try again. It is essential to ones own self-actualization to fail at least once. Consider the first time you may have set up x11 or a web server. The process motivated by determination is amazing when you think of the things you may have learned comes back ten fold and you will carry that knowledge with you for the rest of your life.
I learned that documentation is a must, and since there are people spending time to write it, I must spend time to read it too.
I learned that the system must have a sense, and should not be an assembly of scripts, programs and configuration files placed somewhere. Each thing has a place and an aim.
I learned how much important is to separate the base from the rest of the system.
I appreciated the community, that is going to take decisions for the best of the OS and not to stop claiming someone.
What have I learned? Well just this last week actually:
iscsi-target is pretty non-production ready (performance not so good)
istgt has basically zero documentation on configuration format (in english anyway).
There are plenty of "tutorials" for istgt which basically say "replace contents of file with this" without explaining any of the configuration file options.
I didn't mean that flash is bad, just that there is no native driver on FreeBSD and I don't feel like installing a whole linuxdist on my system just to get it running.
I am very glad that HTLM5 is taking over more and more - it works very good on Youtube for me so now I really don't need flash, facebook works fine as it is too. Same goes for Java, I never install that on FreeBSD anymore...
I've learned that ZFS is awesome on FreeBSD, too.
Back up your data.
Csh is great.
Desktop metaphora sucks.
Edit it with vim!
Fsck. Or not, with ZFS.
Gmake is worse than BSD-make.
Hack up and shut.^W^W^W^W
HEADS UP. Some important news in mail.
I'm the master of my system. The only master.
Java is bad.
Ksh does the job. (From obsd actually..)
Lua is great.
Makefiles could be easy to edit.
Nethack is a great game.
Options in kernel could actually be changed without pain.
Ports and packages. Port it and package it.
Run security audit from time to time.
Tmux. Awesome, better than Screen.
Update when necessary.
Vi. Powerful. Simple. Not emacs.
Zfs rocks. When your machine could run it nicely.
One thing that I have learned on FreeBSD that will make me stay here and never look back at my years of Windows/Linux: ZFS :e
What I have learned:
Watching QT4 compile is like watching paint dry, even on a fast machine. Graphics card manufacturers suck. How much easier sysctl is to use, as opposed to wading through ACPI scripts on Linux. ZFS owns. Things get loaded into memory a little differently. FreeBSD is definitely good for desktop use, despite what others are saying. Having an entire base system included with the kernel is a REALLY good thing. Choose config options for ports wisely, you may wind up building everything but the kitchen sink. How awesome this community is i.e, readiness to help, professionalism (most of the time :e), and just the sheer amount of collective knowledge here.
What I am learning now:
How to cope with the loss of KMS. How to get the most out of AIGLX. The FreeBSD kernel, and how to interact with it programmatically. Makefiles, advanced shell scripting, the subtle differences between C on FreeBSD vs. Windows or even Linux.
I had painted for a few years. There are roof paints that must be thinned with a special additive or they will dry within minutes upon contact with air. The base of the paint matters. Is it latex, oil, epoxy, etc? Is it tempura or acrylic? What type of oil are you using? Are you using an egg tempura? The last two questions are specific to painting as applied to creative arts.
Temperature and humidity affect the drying time of any paint.
What material was painted? Was it treated? Did the person properly prepare the surface area?
What is the viscosity of the paint? What methods were used to apply the paint to the surface and with what equipment?
To which level of curing are you referring? Surface tack at zero or the entire layer to have become the plastic coating that paint is- for the most part?
Nice. That made me smile.
It's a figure of speech, but I have seen acrylic exterior paint take quite a while, I do not paint myself per se, but a relative uses walnut oil based oil paints as an artistic outlet. As to the degree of dryness, I would think that surface tack at zero would be sufficient.
And before anyone ends up painting a bikeshed , I will retract the off the cuff "like watching paint dry..." statement, and say that watching qt4 compile is like watching grass grow.
But it keeps on spinning and spinning and ...
Technologically wise, I have learned more about the innermost workings of Unix than I would have had I used Linux or some other *nix system.
Examples: compilation from source, customizing software for a particular architecture to obtain peak binary performance, building and using custom kernels, building kernel modules, etc.
And, what is more, and perhaps most important, is that it can be a straightforward process (thanks to the well written FreeBSD Handbook). Case in point - try compiling and using a custom kernel in any version of Linux.
In fact, I am probably a better Linux user because of FreeBSD, (but, thankfully I don't use Linux).
How to use pkg_add which is in many respects similar to Debian GNU/Linux's apt-get install.
How to use vi as I am a GNU Emacs person. To be honest, I enjoy elements from both but prefer Emacs.
So far, I have had a very rocky start using FreeBSD. I can see some potential benefits to running FreeBSD on my machines, but for now I'm running Debian GNU/Linux for personal and professional use.
Also huge levelup on English knowledge goes for me.
Build servers for home (NAS, www, sendmail), routers for lab (customized nanoBSD/BSDRP).
Avoid FreeBSD for music as there is no MIDI driver for onboard sound chips.
There is always something new to learn.
Do you mind if I use that as a motto /signature?
More than I thought there was to know. I just hope I can retain some of these things learned.
(Once I had understood how to set up a working FreeBSD) I have learned how to make new ports, update existing ones and how the ports tree works. Enough for now.
Using linux is bloody easy! Haha.
Separate names with a comma.