Linux Blimp

Linux kernel has a new code of conduct (CoC). Linus Torvalds took a break from Linux kernel development just 30 minutes after signing this code of conduct. And since the writer of this code of conduct has had a controversial past, it has now become a point of heated discussion. With all the politics involved, not many people are happy with this new CoC.

If you do not know already, Linux creator Linus Torvalds has apologized for his past behavior and has taken a temporary break from Linux kernel development to improve his behavior.

The new code of conduct for Linux kernel development

Linux kernel developers have a code of conduct. It’s not like they didn’t have a code before, but the previous code of conflict is now replaced by this new code of conduct to “help make the kernel community a welcoming environment to participate in.”

“In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.”

You can read the entire code of conduct on this commit page.

Was Linus Torvalds forced to apologize and take a break?

The code of conduct was signed off by Linus Torvalds and Greg Kroah-Hartman (kind of second-in-command after Torvalds). Dan Williams of Intel and Chris Mason from Facebook were some of the other signees.

If I have read through the timeline correctly, half an hour after signing this code of conduct, Torvalds sent a mail apologizing for his past behavior. He also announced taking a temporary break to improve upon his behavior.

But at this point some people started reading between the lines, with a special attention to this line from his mail:

This week people in our community confronted me about my lifetime of not understanding emotions. My flippant attacks in emails have been both unprofessional and uncalled for. Especially at times when I made it personal. In my quest for a better patch, this made sense to me. I know now this was not OK and I am truly sorry.

This particular line could be read as if he was coerced into apologizing and taking a break because of the new code of conduct. Though it could also be a precautionary measure to prevent Torvalds from violating the newly created code of conduct.

The controversy around Contributor Covenant creator Coraline Ada Ehmke

The Linux code of conduct is based on the Contributor Covenant, version 1.4. Contributor Covenant has been adopted by hundreds of open source projects. Eclipse, Angular, Ruby, Kubernetes are some of the many adopters of Contributor Covenant.

Contributor Covenant has been created by Coraline Ada Ehmke, a software developer, an open-source advocate, and an LGBT activist. She has been instrumental in promoting diversity in the open source world.

Coraline has also been vocal about her stance against meritocracy. The Latin word meritocracy originally refers to a “system under which advancement within the system turns on “merits”, like intelligence, credentials, and education.” But activists like Coraline believe that meritocracy is a negative system where the worth of an individual is measured not by their humanity, but solely by their intellectual output.

Image credit: Twitter user @nickmon1112

Remember that Linus Torvalds has repeatedly said that he cares about the code, not the person who writes it. Clearly, this goes against Coraline’s view on meritocracy.

Coraline has had a troubled incident in the past with a contributor of Opal project. There was a discussion taking place on Twitter where Elia, a core contributor to Opal project from Italy, said “(trans people) not accepting reality is the problem here”.

Coraline was neither in the discussion nor was she a contributor to the Opal project. But as an LGBT activist, she took it to herself and demanded that Elia be removed from the Opal Project for his ‘views against trans people’. A lengthy and heated discussion took place on Opal’s GitHub repository. Coraline and her supporters, who never contributed to Opal, tried to coerce the moderators into removing Elia, a core contributor of the project.

While Elia wasn’t removed from the project, Opal project maintainers agreed to put up a code of conduct in place. And this code of conduct was nothing else but Coraline’s famed Contributor Covenant that she had pitched to the maintainers herself.

But the story didn’t end here. The Contributor Covenant was then modified and a new clause added in order to get to Elia. The new clause widened the scope of conduct in public spaces. This malicious change was spotted by the maintainers and they edited the clause. Opal eventually got rid of the Contributor Covenant and put in place its own guideline.

This is a classic example of how a few offended people, who never contributed a single line of code to the project, tried to oust its core contributor.

People’s reaction on Linux Code of Conduct and Torvalds’ apology

As soon as Linux code of conduct and Torvalds’ apology went public, Social Media and forums were rife with rumors and speculations. While many people appreciated this new development, there were some who saw a conspiracy by SJW infiltrating Linux.

A sarcastic tweet by Caroline only fueled the fire.

I can’t wait for the mass exodus from Linux now that it’s been infiltrated by SJWs. Hahahah pic.twitter.com/eFeY6r4ENv

— Coraline Ada Ehmke (@CoralineAda) September 16, 2018

In the wake of the Linux CoC controversy, Coraline openly said that the Contributor Covenant code of conduct is a political document. This did not go down well with the people who want the political stuff out of the open source projects.

Some people are saying that the Contributor Covenant is a political document, and they’re right.

— Coraline Ada Ehmke (@CoralineAda) September 16, 2018

Nick Monroe, a freelance journalist, dig up the past of Coraline in order to validate his claim that there is more to Linux CoC than meets the eye. You can go by the entire thread if you want.

Alright. You’ve seen this a million times before. It’s a code of conduct blah blah blah

that has social justice baked right into it. blah blah blah.https://t.co/KuQqeriYeJ

But something is different about this. pic.twitter.com/8NUL2K1gu2

— Nick Monroe (@nickmon1112) September 17, 2018

Nick wasn’t the only one to disapprove of the new Linux CoC. The SJW involvement led to more skepticism.

I guess the big news in Linux today is that the Linux kernel is now governed by a Code of Conduct and a “post meritocracy” world view.

In principle these CoCs look great. In practice they are abused tools to hunt people SJWs don’t like. And they don’t like a lot of people.

— Mark Kern (@Grummz) September 17, 2018

While there were many who appreciated Torvalds’ apology, there were a few who blamed Torvalds’ attitude:

Am I the only one who thinks Linus Torvalds attitude for decades was a prime contributors to how many of the condescending, rudes, jerks in Linux and open source “communities” behaved? I’ve never once felt welcomed into the Linux community as a new user.

— Jonathan Frappier (@jfrappier) September 17, 2018

And some were simply not amused with his apology:

Oh look, an abusive OSS maintainer finally admitted, after *decades* of abusive and toxic behavior, that his behavior *might* be an issue.

And a bunch of people I follow are tripping all over themselves to give him cookies for that. 🙄🙄🙄

— Kelly Ellis (@justkelly_ok) September 17, 2018

The entire Torvalds apology episode has raised a genuine concern 😉

Do we have to put “I don’t/do forgive Linus Torvalds” in our bio now?

— Verónica. (@maria_fibonacci) September 17, 2018

Jokes apart, the genuine concern was raised by Sharp, who had quit Linux Kernel development in 2015 due to the ‘toxic community’.

The real test here is whether the community that built Linus up and protected his right to be verbally abusive will change. Linus not only needs to change himself, but the Linux kernel community needs to change as well. https://t.co/EG5KO43416

— Sage Sharp (@_sagesharp_) September 17, 2018

What do you think of Linux Code of Conduct?

If you ask my opinion, I do think that a Code of Conduct is the need of the time. It guides people in behaving in a respectable way and helps create a positive environment for all kind of people irrespective of their race, ethnicity, religion, nationality and political views (both left and right).

What are your views on the entire episode? Do you think the CoC will help Linux kernel development? Or will it deteriorate with the involvement of anti-meritocracy SJWs?

About Abhishek Prakash

I am a professional software developer, and founder of It’s FOSS. I am an avid Linux lover and Open Source enthusiast. I use Ubuntu and believe in sharing knowledge. Apart from Linux, I love classic detective mysteries. I’m a huge fan of Agatha Christie’s work.

Source

KiCad EDA is an open source, freely distributed and cross-platform graphical software that helps users to effortlessly create printed circuit board and electronic schematic diagrams artwork. It includes 3D visualization functionality and numerous attractive features, including a modern and easy-to-use graphical user interface.

Comprises of several components

The application is comprised of a project manager and four main programs, such as a schematic editor called Eeschema, the PCB layout program called Pcbnew, the footprint selector tool for the components used in the circuit design, called Cvpcb, and Gerbview, the Gerber viewer, also known as the document photoplotter.

Getting started with KiCad EDA

On GNU/Linux, you can install the latest version of the KiCad EDA software suite from the main software repositories of several distributions. It the application is not available as pre-built packages in your Linux kernel-based operating system, you can install it by compiling the source tarball distributed on Softpedia.

Supported operating systems and platforms

This is a cross-platform software that has been successfully tested with numerous distributions of Linux, as well as with the commercial Microsoft Windows operating system. It is fully compatible with both 64-bit and 32-bit instruction set architectures.

Source

Share with friends and colleagues on social media

We are seeing more and more companies moving their workloads to the cloud. According to IDC, the worldwide public cloud services spend will double to over $141 billion in 2019. So what is driving this shift to cloud infrastructures? The term we often hear quoted is ‘Business Agility’, and the need for cost savings and/or efficiencies. In today’s fast-paced digital economy, the ability to innovate and stay competitive is essential. Cloud computing has enabled companies of all sizes to channel their efforts into what is important, their business.

When defining a cloud strategy what is the right option for your business? Is it public cloud, private cloud or a hybrid cloud? There isn’t typically a ‘one size fits all’ answer. It often depends on the type of application, cost, in-house expertise, and other unique and specific business requirements.

Let’s first look at the public cloud. It’s this model that people often first think of when discussing cloud computing. The model is based around the Cloud Service Providers (CSPs) leveraging the Internet to make infrastructure resources available, e.g. servers, storage etc., with a selection of payment plans, to make it easier for a business to consume resources on an as-needed basis.

These resources still require physical hardware, but instead of this being housed in an organisations own premises, it is owned and located at the CSP’s data centre. Often referred to as ‘Hyper-scalers’, Some of the largest CSPs in the market today, are Amazon Web Services, Microsoft Azure, Google Cloud, IBM’s Blue Cloud and Alibaba. With these large brands dominating commoditising the market-place, it makes it easy for businesses to move to the public cloud.

The public cloud model works by virtualising the physical hardware housed at the cloud service provider’s data centre. This provides efficiencies by allowing multiple customers to share the resources, enabling a ‘multi-tenant’ arrangement spreads the costs of running the infrastructure across several users. A number of small and medium sized businesses have realised a significant cost advantage by leveraging a pay-as-you-grow model using public cloud. A very common application (workload) in this category are public-facing web applications which can scale up or down depending on demand.

Enabling Business Agility

It seems everything is happening at a faster pace, and businesses need to be quicker and more dynamic to evolve and improve processes, tools and technologies. Business agility is about enabling the business to make faster decisions, prioritise and deliver customer satisfaction. The public cloud can, in several scenarios, provide simplified internal operations, faster rollouts of new applications and initiatives, to achieve a competitive advantage.

What about Private clouds? As with other cloud models, private cloud provides compute and often storage resource as a service within a virtualised environment. However, this time, the physical servers and storage etc. are used only by a single company and are typically housed within the organisations own data centre(s) or hosted by a third party. Private clouds provide many of the flexibilities of the public cloud, however the organisation has to bear the cost of hardware and resource to set-up and maintain these cloud services. As a private cloud is typically only accessible by a single organisation, this increases control and helps improve governance, privacy and compliance.

How can you get the best of both worlds?

We have established that cloud services provide efficiencies at varying degrees. Public cloud services are typically more cost efficient and scalable than a private cloud. Private clouds on the other hand provide more control and often make governance, privacy and compliance a little easier.

There is another option where you can have the best of both worlds, the hybrid cloud. Where you have the need is to maximise efficiencies for a given workload, a public cloud solution can be used. Typically, these consist of non-sensitive applications. However, for those workloads that require additional control for compliance and/or sensitivity reasons you can benefit from a private cloud. The trick with a hybrid approach is to ensure that both the public and private cloud workloads are seamlessly integrated.

Hybrid clouds are not just simply a mix of private and public clouds. It’s a solution that allows the flexibility to choose private and public clouds to achieve the optimal performance, efficiency, and economy for any given workload.

It’s desirable that hybrid clouds are managed through a common management solution. If done well, this approach will enable workloads to leverage different cloud solutions on an as needed basis. This solution can also offer the flexibility to shift one workload from one cloud to another or even to span multiple clouds.

Many organisations are adopting a hybrid cloud approach as the flexibility and business benefits are compelling. With the potential to immediately ‘burst’ and increase a workloads capacity during peak demand, then shrink when demand is light. This is just one of the many advantages why modern businesses are turning to the cloud. Future requirements may also include moving workloads dynamically between private and public clouds and with suitable management solutions in place, all of these options become a possibility.

You can find out more https://www.suse.com/solutions/cloud/

 

Share with friends and colleagues on social media

Source

Back in 2001, a new operating system arrived that promised to change the way users worked with their computers. That platform was BeOS and I remember it well. What I remember most about it was the desktop, and how much it looked and felt like my favorite window manager (at the time) AfterStep. I also remember how awkward and overly complicated BeOS was to install and use. In fact, upon installation, it was never all too clear how to make the platform function well enough to use on a daily basis. That was fine, however, because BeOS seemed to live in a perpetual state of “alpha release.”

That was then. This is very much now.

Now we have haiku

Bringing BeOS to life

An AfterStep joy.

No, Haiku has nothing to do with AfterStep, but it fit perfectly with the haiku meter, so work with me.

The Haiku project released it’s R1 Alpha 4 six years ago. Back in September of 2018, it finally released it’s R1 Beta 1 and although it took them eons (in computer time), seeing Haiku installed (on a virtual machine) was worth the wait … even if only for the nostalgia aspect. The big difference between R1 Beta 1 and R1 Alpha 4 (and BeOS, for that matter), is that Haiku now works like a real operating system. It’s lighting fast (and I do mean fast), it finally enjoys a modicum of stability, and has a handful of useful apps. Before you get too excited, you’re not going to install Haiku and immediately become productive. In fact, the list of available apps is quite limiting (more on this later). Even so, Haiku is definitely worth installing, even if only to see how far the project has come.

Speaking of which, let’s do just that.

Installing Haiku

The installation isn’t quite as point and click as the standard Linux distribution. That doesn’t mean it’s a challenge. It’s not; in fact, the installation is handled completely through a GUI, so you won’t have to even touch the command line.

To install Haiku, you must first download an image. Download this file into your ~/Downloads directory. This image will be in a compressed format, so once it’s downloaded you’ll need to decompress it. Open a terminal window and issue the command unzip ~/Downloads/haiku*.zip. A new directory will be created, called haiku-r1beta1XXX-anyboot (Where XXX is the architecture for your hardware). Inside that directory you’ll find the ISO image to be used for installation.

For my purposes, I installed Haiku as a VirtualBox virtual machine. I highly recommend going the same route, as you don’t want to have to worry about hardware detection. Creating Haiku as a virtual machine doesn’t require any special setup (beyond the standard). Once the live image has booted, you’ll be asked if you want to run the installer or boot directly to the desktop (Figure 1). Click Run Installer to begin the process.

The next window is nothing more than a warning that Haiku is beta software and informing you that the installer will make the Haiku partition bootable, but doesn’t integrate with your existing boot menu (in other words, it will not set up dual booting). In this window, click the Continue button.

You will then be warned that no partitions have been found. Click the OK button, so you can create a partition table. In the remaining window (Figure 2), click the Set up partitions button.

In the resulting window (Figure 3), select the partition to be used and then click Disk > Initialize > GUID Partition Map. You will be prompted to click Continue and then Write Changes.

Select the newly initialized partition and then click Partition > Format > Be File System. When prompted, click Continue. In the resulting window, leave everything default and click Initialize and then click Write changes.

Close the DriveSetup window (click the square in the titlebar) to return to the Haiku Installer. You should now be able to select the newly formatted partition in the Onto drop-down (Figure 4).

After selecting the partition, click Begin and the installation will start. Don’t blink, as the entire installation takes less than 30 seconds. You read that correctly—the installation of Haiku takes less than 30 seconds. When it finishes, click Restart to boot your newly installed Haiku OS.

Usage

When Haiku boots, it’ll go directly to the desktop. There is no login screen (or even the means to log in). You’ll be greeted with a very simple desktop that includes a few clickable icons and what is called the Tracker(Figure 5).

The Tracker includes any minimized application and a desktop menu that gives you access to all of the installed applications. Left click on the leaf icon in the Tracker to reveal the desktop menu (Figure 6).

From within the menu, click Applications and you’ll see all the available tools. In that menu you’ll find the likes of:

• ActivityMonitor (Track system resources)
• BePDF (PDF reader)
• CodyCam (allows you to take pictures from a webcam)
• DeskCalc (calculator)
• Expander (unpack common archives)
• HaikuDepot (app store)
• Mail (email client)
• MediaPlay (play audio files)
• People (contact database)
• PoorMan (simple web server)
• SoftwareUpdater (update Haiku software)
• StyledEdit (text editor)
• Terminal (terminal emulator)
• WebPositive (web browser)

You will find, in the HaikuDepot, a limited number of available applications. What you won’t find are many productivity tools. Missing are office suites, image editors, and more. What we have with this beta version of Haiku is not a replacement for your desktop, but a view into the work the developers have put into giving the now-defunct BoOS new life. Chances are you won’t spend too much time with Haiku, beyond kicking the tires. However, this blast from the past is certainly worth checking out.

A positive step forward

Based on my experience with BeOS and the alpha of Haiku (all those years ago), the developers have taken a big, positive step forward. Hopefully, the next beta release won’t take as long and we might even see a final release in the coming years. Although Haiku won’t challenge the likes of Ubuntu, Mint, Arch, or Elementary OS, it could develop its own niche following. No matter its future, it’s good to see something new from the developers. Bravo to Haiku.

Your OS is prime

For a beta 2 release

Make it so, my friends.

Source

Published October 19, 2018
Source

Linux isn’t a story anymore.

That’s a good thing, but not an interesting one. Let me explain.

Journalism’s main product is the story. In newsrooms, the three words uttered most often by editors to reporters are “What’s the story?”

As I was taught by an editor long ago—and as I have found to be true constantly ever since—all stories are about three things:

1. A character. Usually human, but not always. Could be a cause. A sports team. A political party. Could be good, or bad, or neither. All that matters is that the character is interesting. You can also have more than one, but a single one is better.
2. A problem or conflict. A situation that challenges the character, or characters, further defining them and making them more interesting. Problems and conflict keep people interested, so they keep reading, watching, listening, turning pages, talking to others about it, and “move the narrative along” (as the news watchers like to say).
3. Movement toward resolution. Doesn’t matter if the end never arrives. Hell, look at soap operas. You just have to keep the story moving in the direction of conclusion. Newsroom aphorism: “No story ever starts with ‘Happily ever after’.” Another: “If your team is up forty points with five minutes left, your new story is about how you get out of the parking lot ahead of traffic.”

All three of those are why Linux isn’t much of a story any more, even though it’s bigger in the world than it has ever been.

Linux had character when it was easy to cast as an underdog operating system, and the problem was beating Windows. Linus Torvalds, the father of Linux, did his best not to be interesting, but his fans made him interesting anyway:

Us included. The above is from a slide show that was featured in a story I wrote back in 2002 that’s off-web at the moment, but also beside the point, which is that Linus and his penguins were characters in stories that were interesting at the time and aren’t anymore.

That’s because Linux has achieved the world domination it longed for in the early years.

Yes, Linus as a character got interesting for a few minutes last month (top results in a Google News search for “Linus Torvalds” range from 22 to 29 days old), but that story is too stale to be interesting now, even though the issues around it still matter.

And that’s my point here. Lots of subjects matter that stories do a lousy job of telling.

But to journalism, and to the human beings journalism addresses, stories matter more than anything. Stories are clearly the base format of human interest.

And now, here in the digital world we now co-occupy with the physical one, it’s easier to tell stories than ever. Those who tell stories well, or who are fully interesting as characters, or who know how to “move the narrative along,” are winning at the new game that journalism has become.

Exhibit A through X for that case is the character who now runs the United States. He’s hard to beat as a character, causes and amplifies conflict (or what appears to be conflict, and in journalism there is often not much difference), and keeps new conflicts moving forward pretty much constantly. Never mind the politics or the particulars. Just look at the three elements that comprise a story and you’ll see why this one character and what he does utterly dominates the journalistic world right now.

Meanwhile fully important and consequential stuff just lies there, being uninteresting—except to specialists like our readers here, who still care about this operating system that has become as elemental to the technical world as oxygen is to the living one.

This is a topic that needs a lot of visiting by people who care about journalism, and not necessarily by Linux geeks.

But I’m not sure we’ll ever get past the basic flaws inherent in journalism’s stock-in-trade, meaning also in human nature itself. Stories are just too damned interesting.

Speaking of which, this whole topic was the subject of my first TED talk, given at TEDx Santa Barbara last month, and titled The story isn’t the whole story.

And I’m hardly close to my own conclusions on the topic. I just want to share my own thoughts and observations, so far, using Linux as an example.

By the way, that top photo is from Linux World Expo in 2005, and kind of explains itself.

Source

Having a physical access to the keyboard can simply use the Ctrl+Alt+Delete key combination to reboot the server without having to logged on, But we can prevent the use of this key combination on a production server for an accidental reboots.

To disable the reboot action taken by pressing the Ctrl+Alt+Delete key combination,

Comment out the following line in the file /etc/init/control-alt-delete.conf

$ sudo vi /etc/init/control-alt-delete.conf

Or

$sudo gedit /etc/init/control-alt-delete.conf

Find line that read as follows:

exec shutdown -r now “Control-Alt-Delete pressed”

delete configuration line or comment out line by prefixing # symbol

#exec shutdown -r now “Control-Alt-Delete pressed”

Save and close the file.

But In 16.04

In the systemd world, Ctrl+Alt+Delete is handled by ctrl-alt-del.target

ctrl-alt-del.target systemd starts this target whenever Control+Alt+Del is pressed on the console. Usually, this should be aliased (symlinked) to reboot.target.

Disable Ctrl+Alt+Delete using following command

$systemctl mask ctrl-alt-del.target

$systemctl daemon-reload

Source

Both Linux and Unix-like systems comes with various command to find out server uptime command. Under Linux file /proc/uptime has uptime information and file /var/run/utmp has information about who is currently logged on. However, information from /proc or utmp file is not directly readable by humans so you need to use the uptime command.

uptime – Tell how long the system has been running.

UNIX / Linux uptime command

Open a command-line terminal and then type the following commands:

#uptime

Sample outputs:

uptime

12:04:44 up 8 days, 19:42, 3 users, load average: 1.56, 2.56, 1.96

Note: The uptime command gives a one line display of the following information.

1). The current time

2). How long the system has been running

3). How many users are currently logged on

4). The system load averages for the past 1, 5, and 15 minutes

See uptime in pretty format pass the -p option to the uptime command

#uptime -p

Sample outputs:

uptime -p

up 1 week, 1 day, 19 hours, 47 minutes

See uptime in system up since, in yyyy-mm-dd MM:HH:SS format pass the -s option to the uptime command

#uptime -s

uptime -s
2017-12-27 16:22:09

Source

Go also known as golang, is a compiled computer programming language developed by google. It is loosely based on the C language but designed to overcome some of its short comings. It is a general purpose language and can be used from server-side development to games and streaming media. It can easily be installed on a CentOS system. This guide assumes you have at least a basic working installation of a Linux system.

Install Go on CentOS

Clean up repositories

yum clean all

Ensure everything is up to date

yum update

Change directories

cd /usr/src

Download the compiled package, you can find the most recent release on the downloads page.

wget https://storage.googleapis.com/golang/go1.8.3.linux-amd64.tar.gz

Uncompress the archive

tar xfvz go1.8.3.linux-amd64.tar.gz

Move the binary and its applicable files to /usr/local

mv go /usr/local/

Export the following

export GOROOT=/usr/local/go

GOROOT defines the path you placed the Go package in

export GOPATH=$HOME/go-project

GOPATH tells go where your project is located, this can be anywhere

export PATH=$GOPATH/bin:$GOROOT/bin:$PATH

This appends both the GOPATH and GOROOT to your $PATH. You can also add this to your .bash_profile to automatically export these variables upon logging in.

Verify Go Installation

By typing ‘go version’ it will give you a print out of the version you currently have running

# go version
go version go1.8.3 linux/amd64

By typing ‘go env’ it will show the environment variables that are currently in use.

# go env
GOARCH=”amd64″
GOBIN=””
GOEXE=””
GOHOSTARCH=”amd64″
GOHOSTOS=”linux”
GOOS=”linux”
GOPATH=”/root/go-project”
GORACE=””
GOROOT=”/usr/local/go”
GOTOOLDIR=”/usr/local/go/pkg/tool/linux_amd64″
GCCGO=”gccgo”
CC=”gcc”
GOGCCFLAGS=”-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build167939199=/tmp/go-build -gno-record-gcc-switches”
CXX=”g++”
CGO_ENABLED=”1″
PKG_CONFIG=”pkg-config”
CGO_CFLAGS=”-g -O2″
CGO_CPPFLAGS=””
CGO_CXXFLAGS=”-g -O2″
CGO_FFLAGS=”-g -O2″
CGO_LDFLAGS=”-g -O2″

Test a Go project

Create the project directory you exported earlier:

mkdir $HOME/go-project

Change to that directory:

cd $HOME/go-project

Create a new file:

nano hello.go

Insert the following lines:

package main
import “fmt”
func main() {
fmt.Println(“hello world”)
}

Execute the file:

go run hello.go

The file should print the following

# go run hello.go
hello world

That’s it, you should now have a working Go installation.

Aug 7, 2017LinuxAdmin.io

Source

Source: InfoSecurity – Posted by Brittany Day

According to a media release from Onslow Water and Sewer Authority (ONWASA) issued on October 15, 2018, a critical water utility in North Carolina was targeted in a cyber-attack. Federal and state officials are now working with the water utility as part of the investigation into the attack on some of its computer systems. “In the wake of the Hurricane Florence disaster…ONWASA’s internal computer system, including servers and personal computers, were subjected to what was characterized as ‘a sophisticated ransomware attack,’ wrote Jeffrey Hudson, CEO, ONWASA.

Read this full article at InfoSecurity

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

Source