GBC Tech Video News

Quick Overview of Bsd Systems With Main Focus on Openbsd

admin — Fri, 12 Mar 2010 04:05:43 +0000

Most users who use Linux use it because they hate Microsoft; people who use BSD use it because they love Unix

Juraj Sipos

I have been a BSD user since the late 1990’s. I started with FreeBSD 3.0 and I also made my own FreeBSD distro – a tiny floppy disk entitled 1fcdbsd, which boots in any x86 computer and plays MP3 files from a hard disk or CD’s (One Floppy CD Audio and MP3 Player – http://www.freebsd.nfo.sk/). I gained some experience with the BSD world, which rather thrives on the side without people’s knowledge that it is almost the best.

History

To say it metaphorically, the Internet sprung out of BSD. It is not because these systems can handle the biggest traffic as servers, but because the concept of IP addresses and the TCP/IP stack is a BSD invention. If you right click on the file “winsock.dll” in Windows 98 (C:Windowswinsock.dll), you will see “BSD Socket API for Windows” in the Properties > Version window; however, the “BSD” is not seen in newer Windows systems in the “version information” window of winsock.dll. But there is a lot of writing on the Internet about this if you Google both terms: “winsock.dll” AND “bsd”. BSD systems have a different licensing policy and anybody can take their code. BSD license gives more freedom to programmers.

From the above it is clear that Microsoft, too, used or “stole” this code, not only Linux.

BSD grew up in the 1970’s with a Defense Advanced Research Projects Agency (DARPA) support. Version 4.3 BSD (1986), 4.3 BSD Tahoe (1988), BSD Net 1 (1989), and so on followed. The history is well described also on BSD sites, such as www.freebsd.org. FreeBSD, for example, started as a project in 1993 shortly after NetBSD; and OpenBSD is a fork of NetBSD, but these all are derived from 386/BSD.

Linux versus BSD

BSD: BSD systems are based upon an actual Unix variant called Berkeley Software Distribution, which has a long history.

Linux: Linux is based upon a clone of Unix (Minix), which was far away in functionality in comparison to the above Unix at its time. Terminologically speaking, Linux is only the kernel.

The “Linux-versus-BSD” discussion is very sensitive for some people – they may get very angry about any direction, either in favor of BSD or Linux. It is not a good idea to compare these systems as the whole, but it’s not a bad idea to compare their “usability” in various aspects, for example, as an “office solution”, “desktop solution”, “multimedia solution”, “server solution”, “firewall solution”, etc.

The widespread use of Linux helped some users switch to BSD for good, as various opinions made the issue of “Linux-versus-BSD” visible to public eyes, which made the BSD world appear more attractive.

If we talk in general, we can say that “BSD is much more stable, as it is a REAL Unix” and that “Linux is a very good desktop toy more adapted to users’ needs, as it has more drivers and apps”.

Other global aspect that makes Linux and BSD systems look different is that BSD OS’s have everything under one hood and control. Linux is murky waters because it is not united. For example, you have a DEB (Debian Linux) package – you will not always install it if you use Mandrake or SuSE. A long list of problems ensuing from discrepancies among Linux distros may be written. Linux users surely remember the effort of UnitedLinux, but now it is devoid of life. In the chaos where one Linux system installs with various services and the other one does not, we see that the Linux community is broken as the whole.

Linux is more developed in terms of its accessibility to various types of hardware like, for example, inkjet printers or WiFi USB solutions. But this is because, as I already said, various companies support it. Linux is good for desktop users who want to forget about Microsoft and BSD systems are best as server/router/firewall solutions. Many good administrators say that Linux behaves much worse as server than BSD systems. Something like Red Hat or SuSE Enterprise Server is rather a joke – these systems cost a lot of money. Every good administrator would only bet on BSD or other Internet solutions today. Slackware Linux is exception – it is one of the best.

There are many reasons why BSD systems are less noticeable. The availability of Live CD’s and their easy-to-use presentation is something in which BSD systems lagged behind. You may download Linux ISO images at the drop of a hat. With BSD systems, this is a bit different. You could hardly find a desired BSD Live CD in the 1990’s. Only a few of them do appear now.

OpenBSD

I tackled the problem of building such a CD myself. I toiled with FreeBSD. I succeeded. Later I focused on OpenBSD, as it has a good reputation concerning its solid security structure. I succeeded too. But this would require additional writing and this article is not about making an OpenBSD Live CD; I only want to introduce this system a little and give advice how to make a simple OpenBSD bootable installation CD/DVD, which is also hard to get.

Usability

BSD systems work well with all kinds of standard hardware; however, some users say they are “less user-friendly”. On the other hand, others consider the so-called “user-friendliness” to be a hindrance in making needed configurations. In other systems, where many services run automatically, it is a bit irritating when administrators, with their own security policies in mind, must turn them off on a regular basis after every installation.

OpenBSD could be, from a Linux user’s point of view, a can of worms. Some may disagree with me, but in the world where all mainstream operating systems bet on easiness-to-use and the graphical interactivity, this is surely the case. This means you must forget about graphical installers – your first touch with the system is the text mode. But the text is the best format some people like.

OpenBSD can run Linux binaries on an emulation layer; DOS (and other systems) programs within the Qemu emulator, as well as FreeBSD and other BSD and Unix binaries. Albeit OpenOffice.org has not been ported yet (do you really need such a big bulk of software when there are more handy solutions?), you can easily write or open your MS Word documents in TextMaker for Linux, or in native OpenBSD AbiWord port.

The system and packages

The BSD family of operating systems consists of the base system and packages. The OpenBSD core – its kernel and the base system (system/network utilities, man pages, etc.) get cautiously, if not paranoically audited for security holes.

The OS has a different packaging philosophy in comparison to Linux. It uses ports and prebuilt packages. Ports are fingerprints of applications on your disk. They contain the basic information where they can be downloaded from. You just “cd” somewhere to the hierarchy of the /usr/share/ports directory, where applications are divided by categories; then type “make install” and wait for sources to be downloaded, compiled, and installed.

Prebuilt packages, too, can be installed with a breeze. Unlike RPM archives, which you must install in the consecutive dependency order, here you have everything on tap. And with the “pkg_add –v ftp://ftp.openbsd.org/pub/OpenBSD/4.0/packages/i386/package.tgz” command you download everything from the Internet even without specifying a package’s version. This is something most Linux packagers cannot do, only APT (Debian) and its clones.

Installation

The policy of the OpenBSD team is to sell CD’s. Unless you are prepared for a difficult network install, you have two options: either you buy their CD’s, or build them yourself. If you choose the latter option, download the core system from these FTP mirrors: www.openbsd.org/ftp.html. Pick out your architecture like AMD
64 or i386 and the version (like 4.0, 3.9, etc.). Place all downloaded files in any directory (for example, in /usr/opbsd) and issue the following command to make the ISO image of it:

mkisofs -b cdrom40.fs -c boot.cat -R -v -o /usr/my_openbsd.iso /usr/opbsd

The above command may be used both in Linux and in BSD systems and possibly in any system to which mkisofs is ported.

When ever in the future you are ready to download a newer version of OpenBSD with purpose to make a bootable CD/DVD of it, just change the “cdrom40.fs” in the above mkisofs command (4.0 is the current version of OpenBSD) to the version it agrees with, for example, “cdrom45.fs” (a future OpenBSD), which is a bootable image as the emulated big floppy. A CD or DVD burned with this ISO file will boot on any PC (not DVD in UDF format, but DVD in ISO format).

The following files contain the basic OpenBSD installation – networking, Unix commands, X Window, man pages; not packages like KDE, Aspell, etc.

OpenBSD 4.0 core system

Packages # you can create this directory and put packages in it

CKSUM, INSTALL.i386 , INSTALL.Linux, MD5, base40.tgz , bsd, bsd.mp, bsd.rd, cd40.iso, cdboot ,cdbr, cdemu40.iso, cdrom40.fs, comp40.tgz, etc40.tgz, floppy40.fs, floppyB40.fs, floppyC40.fs, game40.tgz, index.txt, man40.tgz, misc40.tgz, pxeboot, xbase40.tgz, xetc40.tgz, xfont40.tgz, xserv40.tgz, xshare40.tgz

It is important to say that the ISO file cannot be burned to a CD as an ordinary file like an MP3 file – it can be done this way, however, but you will not be able to boot from such a CD/DVD. If you use Windows, the proper way for burning ISO files is to use the “burn image” command in programs like Nero Burning ROM (or “burn ISO” in other programs). Under FreeBSD, you can burn the ISO image with the burncd command (if your CDROM is the master on the second IDE channel; “-s” is for speed):

burncd -f /dev/acd0 -s 4 data my_openbsd.iso fixate

It would be a good idea to make the bootable OpenBSD DVD with packages included in it – just download them and put them to a directory (for example, to a directory “Packages”) where you have your core OpenBSD installation files; then apply the above mkisofs command.

Installation is quite easy. For newbies it is recommended to use a mobile rack and use some older disk (about 3 GB). This is because installing OpenBSD to an already partitioned disk requires a lot of knowledge and if users do not want to bother about numbers of sectors/cylinders and other things they must type in the text wizard, this solution is very handy.

OpenBSD in action

The system boots fast (much faster than Linux). If you selected the X Window environment during the installation text wizard, you only need to run the “xorgcfg” command from the console to configure your X Window environment.

Did you lose yourself somewhere in the text-mode consoles? Use the F5 key (Ctrl+Alt+F5) to get back to the X Window. Are you a complete newbie? Type “man afterboot”. Are you accustomed to Linux and do you prefer a Linux terminal type? After every logon, OpenBSD asks you to type the terminal type you want to use, but the default one – vt220 – does not map keys like you got accustomed to in Linux if you use programs like Midnight Commander (for example, F7 behaves like F6, etc., but not in X). After typing “nxterm” everything should work OK.

A manual text-mode configuration is the absolute preference here. Almost all services are turned off – a first choice for every good administrator, as he will have ultimate control over the whole system. Users, too, may familiarize themselves with Unix and see what is going on under its hood. To run the X Window, just execute the “startx” command. If you want to edit or re-edit the configuration files, peep into the /etc directory with vi as your editor. Do you want to add more packages? Just download them and issue “pkg_add -i package.tgz” command and that’s it!

OpenBSD 4.0 is geared up for most of the network or desktop tasks. After I downloaded some fine MP3 players, I could instantly listen to music. The X Window’s look does not differ from any Unix-like box. VLC or MPlayer multimedia players will help you enjoy all your favorite music or film recordings.

If you have euphoria from seeing the KDE or Gnome Desktop and other apps running smoothly, you may soon become disappointed – OpenBSD has fewer packages than FreeBSD or Linux. For example, running VMware on FreeBSD has been possible for quite a long time; OpenBSD (but not OpenBSD in the VMware environment) requires some smart tweaks to achieve this.

New technologies and automation can also impose a risk

Numerous companies want to earn the highest profit and they introduce various technologies that serve as a marketing competition strategy for most of the time and are often useless. A bluetooth or WiFi technology in your mobile phone brings a security risk when any good hacker can get to your most sensitive data within seconds right from your neighborhood. Most users do not have time to study various security datasheets and they often live happy without knowing they are unprotected. I do not want to say that newer technologies are always nonsensical; however, they deserve pertinent praise only if used on the right place.

If a reader understands this, the mainstream world’s policy is to create the Matrix or a big web of dependencies – if hardware can run in Linux, users use Linux (and possibly buy Red Hat or Xandros).

Numerous “terrific” companies that sell their “amazing security products” forget that using carrier pigeons for communication is by far a more secure solution than any computer communication – an encrypted e-mail, if you are already under suspicion, will always get intercepted, and governments have always enough resources and money to do their job well.

Why BSD or OpenBSD?

Today, when too many companies bring out various distros, it is hard to tell which of them best suits our needs and you may become mixed-up in such a huge list. If companies invest money to a software solution, they may become disappointed if its licensing policy changes. OpenBSD has one sturdy feature above everything – the system and packages are perfectly audited for security holes.

The power of a good policy will make you feel somewhat sheltered from the bad behavior of the world, because you do not have to worry that network services, for example, contain security holes. Something like this often happens with Linux – its websites urge users to download important patches soon after distros are released. With this particular security point OpenBSD as a BSD system stands aside from the usual crowd.

Source: http://www.freebsd.nfo.sk/

Make Money On Casino

admin — Thu, 11 Mar 2010 16:56:30 +0000

Which full of confident, I believe that everyone loves playing games. games is a simple entertainment, yet very enjoyable to try. It is simply click from your computer and you dont even have to change your clothes to gamble at casino club.

Yes, this is true. Casino online is one of the most famous games worldwide. They are played by everyone. Technology enables casino online to be more challenging and fun. They have great digital sounds and perfect detail of graphics and figures that bring the atmosphere of gambling in real casino bar. Even people prefer to play online, for economical and practical reason. If you want to play at prestigious web as the games, Lonelyheartcasino.com is the correct destination. They have the best online casino slots for instant playing completed with latest reviews, to make sure that you play casino online only at the best recommended place. Which is an online slots real money, instead of usual slots machine. However, they have not only slots, video pokers and blackjack very easy to find here. One more benefit of this web, unlike any other web, this web casino excepting usa players, so you will be assure of its convenience.

If you find it interesting, please dont hesitate to visit this web by now!

7 Technology Transfer Officer Tips For Tough Economic Times

admin — Thu, 11 Mar 2010 20:33:01 +0000

There is no doubt that these are tough economic times. Unemployment is high and credit is tight. Key indicates show that is the worse economy in a generation. Many technology transfer offices have seen potential business partners reduce their innovation portfolios and expenditures. This coupled with a reduction in funding sources, from grants and investors to university sources are blowing the technology transfer research commercialization efforts into the perfect storm.

There are difficulties and challenges, but these times also create opportunities. Here are seven tips to help your technology transfer office succeed in these tough economic times.

1. Maintain a list of problems that are relevant to the research and technologies in the pipeline.

Technology transfer offices typically get involved in research commercialization efforts late in the research and testing process. Get involved earlier in the process and start developing a list of problems of which the research can be applied.

This is really an early brainstorming exercise. Don’t just talk to the researchers. Get business input from those who are not involved with the research or the research teams. Independent ideas can be worth their weight in gold.

2. Develop long-term business relationships.

“Dig the well before you are thirsty.”

-Chinese Proverb

Start developing business relationships with business leaders from a wide range of industries. Do this even before you have any applicable research or solutions for them. These relationships will pay off in two ways.

? You will have a better understanding of the types of challenges that these businesses face.

? When you do have promising research technologies and solutions you already have a relationship with the business or their contacts.

3. Pair researchers with business mentors.

Researchers think like researchers. Business people think like business people. Getting the two to communicate with each other versus talking to each other is a common technology transfer office challenge.

Providing a business mentor to promising research leaders will help alleviate this common problem. This continuous conduit will go a lot further than a long forgotten entrepreneurial seminar.

4. Develop alternative commercialization strategies early.

Good business people know that there is always a chance that their efforts may fail. Technology transfer officers know this too. Unfortunately, many researchers and inventors do not think about this, much less plan for it.

Most inventors think that their invention is world changing and worth millions. They have visions of establishing a company based on their research or technology, selling it for millions, and retiring in the lap of luxury.

The truth of the matter is that nine out of ten spin offs and startups will fail. You, can as the technology transfer officer can improve these odds.

I sit on the advisory board for some start up focused investment funds. One of the strategies that we have developed recently is to go for the big distribution partnering deal with large companies. When that doesn’t work – we find out why and have alternative proposals available.

This alternative could be limited distribution agreements on licensing deals. It really doesn’t matter what the alternative is. What does matter is that you get to stay in the game and get a return on the sunk costs.

5. Reduce risks for all involved.

It wasn’t that long ago that many universities shunned the entire technology transfer process. They wanted their faculty teaching and doing research, not commercializing their intellectual property. My, how times have changed.

Now universities love the revenue that comes from royalties and equity distributions and sales that are associated with intellectual property commercialization. Businesses are always looking for a competitive advantage and right now innovation is the soup de jour, except for one thing …RISK!

In order to get more businesses interested in potential technology look for new ways to reduce their potential risks. Right now cash is king. Instead of negotiating a lower royalty percentage, offer your potential licensor a deferred royalty agreement at a higher percentage. This is the business innovator’s version of “no interest payments for 3 years”.

This approach allows the business to conserve cash today and the university to reap more money in the long run. It’s better than the technology sitting on the shelf waiting to become obsolete.

6. Teach bootstrapping to your startups.

All technology startups need money. That is a known fact. The truth is that many could get by with less money than they think that they need. There in lies the art of bootstrapping. Bootstrapping basically means to start and operate a business without lots of investment funds. It requires the entrepreneur to focus on sales and to hold fixed costs to an absolute minimum.

Bootstrapping requires a unique mindset that few lead researchers turned entrepreneurs can relate to. It takes a special entrepreneur to be able to successfully bootstrap a business.

Help your lead researchers and startup teams. Get some experienced bootstrappers on your advisory and consulting teams and pass the knowledge on to your startups.

7. Partner with other technology transfer offices.

Technology transfer offices provide a valuable service to both the university and their research communities. They play a vital role in the economic development of their respective communities and states. Unlike many organizations involved in the invention commercialization process they do not compete.

Some technology transfer offices such as Stanford and MIT are the envy of their peers, however most technology transfer offices do not reside in a geographic area that harbors entrepreneurship in its DNA.

Partnering with other technology transfer offices offers many unique benefits that cannot be found though other means. It opens up dialogue and support for represented research and technologies to new areas and new commercialization ideas. It develops relationships with other potential business partners and fosters potential research synergies.

Targeted TTO partnerships can lead to specific research pairing with higher degrees of commercialization potential. This focused effort will, in the long run, yield a high degree of return on investment.

These 7 technology transfer officer tips can help you reduce your operating costs and increase your revenue generation success rate. It’s a win for society, the researcher, the business community, the university, and YOU!