Search posterous

Search all posts and users. Type a name, type a favorite song title, whatever! See what comes up.
  

More posterous blogs











More recommended blogs »

Here are posterous posts filed under os...

1uk3 says...

I’ve been running Windows 7 as my main OS for quite some time now.  Ever since I installed it, there was no going back to any previous version of Windows because of its new features.  I must admit that I had been a Windows Vista user since it’s Beta days too but the reason I used Vista over XP was more about the way it looked rather than having any killer new features.  Windows 7 on the other hand does have killer features and it runs better than Vista on machines of the same spec!

I am going to write some short articles about some of these features in Windows 7 and how they help me in my everyday computing life.  Number 1 in my “Features I Cannot Live Without” is going to be Aero Snap.

Here is a brief description of Aero Snap tacking from the Wikipedia article which can be found here: http://en.wikipedia.org/wiki/Aero_Snap

Clicking and dragging a window to the right or left side of the desktop causes the window to fill the respective half of the screen. Snapping a window to the top of the desktop maximizes it. Resizing a window to touch the top or bottom edge of the screen maximizes the window to full height, whilst retaining its width; these windows will then slide horizontally if moved by the title bar, or can be pulled off, which returns the window to its original height.

Here is the sort of thing you can easily do using Aero Snap.

There’s no fiddling around trying to align windows side by side.  It’s simples!

To do this I could have either dragged one window to the left and one to the right or to achieve the same result, I could select a window and hit [WINDOWS KEY] + [LEFT ARROW] for the left window and [WINDOWS KEY] + [RIGHT ARROW] on the for the right window to be placed as shown.

Using the Windows key and directional (cursor) arrow is the best method if using more than one screen.  If you have a setup as I do with another monitor to your left, you cannot drag a window to the left hand side to “snap”.  It will just continue onto the monitor to the left until it reaches the far left of the screen.

I have noticed that a third party developer has released (in Beta) some software that mimics the Windows 7 Aero Snap feature.  I have not tested this as I do not have a test machine running Windows XP or Vista at this time but if you’d like to give it a go, you can download it for free from here: http://www.aerosnap.de/eng/download.htm I’d love to hear your comments about this download in XP or Vista, especially if you have used Aero Snap on Windows 7.

If you have any comments or questions, please go ahead – I’ll be listening.

Next up on my “Features I Cannot Live Without” will be Jump Lists – they’re very cool indeed!

http://www.lukeaddison.com/windows-7-features-i-cannot-live-without-part-1/

Filed under: OS

1uk3 says...

Over the past week my Windows Home Server box has been crashing, restarting and causing me and my family many problems.  It’s not been the first time this has happened.  A couple of times now I have managed to rescue data from it before re-installing Windows Home Server on the same machine and starting again.

I decided to ask people on Twitter if they knew of an alternative to Windows Home Server.  I chat to quite a few Linux geeks on Twitter and they’re always trying to get me off my Windows machines.  I’m not a fan boy but I do use Microsoft operating systems normally because I can run all kinds of software and games that I wouldn’t be able to with Linux.  This wasn’t really a concern for a server.  All I wanted were back-ups and some shared folders that could be accessed across my home network.

A great guy on Twitter named Simon Doyle (@sidolye) suggested that I should take a look at Amahi so I did.  I was very impressed with what I saw looking around the website and was sold on installing it after reading some of the testimonials.

First of all I needed to download myself a Fedora 10 Installation DVD (Fedora 11 isn’t supported with Amahi yet) which I got from here.  Don’t do what I did in my haste and excitement though – I stupidly downloaded the PPC version which is of course for Power PC Mac’s – that’s not going to work on a home built PC with an AMD64 processor.  You need the i386 version. EDIT: The x64 version is also supported so you could also use that if you have a 64bit CPU.

Installation of Fedora 10 was a breeze.  I have installed various Linux distributions in the past but I’m no expert.  I don’t think anyone would have a problem with it as long as they read the on-screen instructions.

Unfortunately I didn’t read the instructions for the installation of Fedora on the Amahi installation page!  I should have added a software repository for Amahi during the installation.  I mistaken thought that it wouldn’t matter and that I’d be able to add the software repository address after Fedora was up and running – you can’t!  You can read these instructions which I didn’t and caused me to have to reinstall Fedora from here.  You’ll kick yourself if you don’t read them!

If you install Fedora with the Amahi repository correctly by following the instructions, installation is so easy!  It’s just as easy as installing Windows Home Server (which is just like installing Windows XP).  I guess that it took around 30 minutes.

I won’t go into every step of the installation process, just make sure you read the instructions over at the Amahi site and you’ll have no problem whatsoever.

If you’re interested in the spec of the machine I’m now running Fedora 10 and Amahi on here you go.

AMD64 3700+ (2.4Ghz)

Socket 754 Motherboard

2GB DDR400

500GB HDD

Once everything was installed and up and running per the instructions I turned off DHCP on my router (read the instructions before doing this), set-up a few static IP addresses for the 3 PC’s at home and everything worked well.  Amahi uses OpenDNS which is a good choice for DNS IMHO but I think this is something that can be changed if you’d like.

One of the main reasons for me having a server at home is for back-ups.  These are easily set-up through Windows 7 which is the OS I’m using on all 3 PC’s at home at the moment.  It’s just a case of visiting the Control Panel, going to the Back-up and Restore page, selecting the network location and running through a wizard.  This isn’t as nice as the back-up system in Windows Home Server but it’s simple and does the job just as well.  I have created a back-ups folder of the server for each machine.  For example: \\hda\luke\backup and \\hda\mandy\backup etc.

The other reason I have a server at home is so that media files can be accessed from any PC that happens to be on and files aren’t duplicated across machines.  I have all of my music in a shared folder on the server so someone in the living room can be listening to something, I can jump on my PC and also have access to the same music folders.  The same could be done with photos, videos or any other files that need to be accessed from multiple machines.  The only issue I have found with Amahi is that because it is running on Fedora and not a Windows machine, the files and folders aren’t indexed in a way that Windows 7 understands.  This means that folders on the server can’t be included in “Libraries”.

Okay, so I think I’ll mention what I miss from Windows Home Server now.  There are a few things but nothing that I miss so much that I’d change back.

  • I miss the nice Windows Home Server connector software.  It sits in your system tray and allows the user to do all kinds of cool things with the server vary easily through a nice interface.
  • I’m going to miss shared folders being included in Windows 7 libraries.  I think this is something I’ll just have to live without because I can’t see how the functionality could be implemented under Linux.
  • … I think that’s it!

What I won’t miss from Windows Home Server.

  • I really won’t miss the OS screwing up after a month or two to the extent that I have to painstakingly recover data, format and reinstall.
  • I also won’t miss having to worry about viruses on what was and still is a headless server that I like to set and forget about.

What I really like so far about Amahi.

  • It seems to run so much better than Windows Home Server.  It must be much lighter on resources.
  • I love that I can install web applications with one click though a web browser.  There are some great web apps in the repository and lots more on the way.  You can even make suggestions to the Amahi team for what you’d like to see there.
  • The community (although I haven’t joined in on the forums yet) seems to be really good even for Linux n00bs like me.
  • It makes you feel like a proper geek because you’re running a Linux server – how cool is that!?

What would I like to see in the future from Amahi?

  • I’d love to see more web apps.  I do think that as the list grows, the repository that is accessed through a browser should be categorised and searchable.
  • I’d like a Windows Home Server tray application program that could open, perhaps a browser window with no navigation options.  I could create one of these or something like using Prism for Firefox (https://wiki.mozilla.org/Prism) but unfortunately the web config page for Amahi doesn’t function correctly in Firefox. (EDIT: It does work fine in Firefox but I had one or two Greasemonkey scripts interfering with the “site”)

Want some screenshots?  I won’t disappoint.  Here are a selection of screens using two different themes.  Enjoy and please leave me comments and questions and also visit the Amahi site: www.amahi.org

amahi1

amahi2

amahi3

amahi4

amahi5

amahi6

http://www.lukeaddison.com/amahi-home-server-the-free-alternative-to-windows-home-server/

Filed under: OS

raumwiese says...

Ich lese die c’t ja schon länger nicht mehr, vor allem weil es mich genervt hat, daß die Computer-Welt sich massiv schnell bewegt, aber in Hannover das Web immer noch keine Rolle spielt, sondern nachwievor Hardware-Specs, Testlabore und irgendwelche abstrusen Anwendungsszenarien, die irgendjemand unbedingt niederschreiben mußte, noch dazu sind nahezu alle Artikel längst “durch”, man hat das meiste schon vorher im Web lesen können.

Nun bin ich eben gerade bei heise.de über folgenden Artikel gestolpert: Chrome OS: Der “Windows-Killer” fällt aus – dort schreibt Oliver Diedrich:

Seit dem Sommer geistert Chrome OS durch die Schlagzeilen, jetzt hat Google eine erste Entwicklerversion als Chromium OS veröffentlicht. heise open hat sich das Google-Betriebssystem angesehen und kommt zu dem Schluss: Ein Windows-Killer ist es nicht – und will es auch gar nicht sein. Chrome OS, an dem auch Ubuntu-Entwickler mitarbeiten, zielt auf Web-Appliances, die immer online sind und im Wesentlichen für Internet-Aktivitäten genutzt werden. Das System spielt in einer ganz anderen Klasse als Windows und Mac OS X, aber ist auch kaum mit den etablierten Linux-Distributionen vergleichbar.

Natürlich wird Google Chrome OS der Windows-Killer sein, und zwar präzise, weil es nicht mit Windows vergleichbar ist, sondern sich auf das konzentriert, was die Masse der Anwender interessiert: Anschalten, Nutzen.

Diedrich schreibt dann weiter, um seinen Punkt zu untermauern:

So verzichtet das Google-Betriebssystem komplett auf einen Desktop, die einzige Anwendung in Chrome OS ist der Google-Browser. An die Stelle lokal installierter Programme treten Web-Applikationen; in seiner Standard-Konfiguration ist es ohne Google-Account gar nicht benutzbar. Für den Einsatz auf Web-Appliances bietet es allerdings interessante Ansätze.

Ja, eben. Das ist ja gerade das Spannende an Google Chrome OS. Ok, aus Sicht der c’t wäre das natürlich total fatal, wenn künftig nicht mehr irgendwelche Viren-Programme getestet, keine 1500 Superduper Office-Tipps niedergeschrieben werden müssen und so weiter und so fort, sondern wenn die Nutzer einfach einen kleinen Rechner hätten, den sie einschalten und dann gleich loslegen können, mit lauter Nutzungsszenarien, die alle sofort realisierbar sind, da die Applikationen oder Inhalte irgendwo in der Cloud zu finden sind. Diedrich versteht nicht, oder will es nicht verstehen, dass die Welt sich schneller ändert als man es in Hannover wahrhaben will.

Google Chrome OS ist der Windows Killer – und zwar eben genau aus einem Grund: es ist nicht mit Windows vergleichbar und macht damit den dramatischen Unterschied. Es “spielt in einer ganz anderen Klasse” – sagt Diedrich selber, aber die richtigen Schlüsse kann er nicht ziehen. Schade, er war dicht dran. Das Web wird den Desktop ersetzen und Google Chrome OS ist ein massiver Schritt in diese Richtung.

Share:
  • email

  • Print

  • Twitter

  • Facebook

  • Tumblr

  • Yigg

  • StumbleUpon

Filed under: os

omarkamal says...

 

Until today, Google's Chrome OS has been little more than a wordy concept. Now, finally, we truly know what it is, what it looks like, and how it works. Here's the breakdown:

Google went to great pains to emphasize that today's event wasn't a launch—that'll come a year from now, apparently, with a public beta still well over the horizon. This is all about a seeing the OS for the first time; understanding in real terms how it's different from what's out there; figuring out why you might actually want to use it; etc. So! Here's what we knew going in:

Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks" and "most of the user experience takes place on the web." That is, it's "Google Chrome running within a new windowing system on top of a Linux kernel" with the web as the platform. It runs on x86 processors (like your standard Core 2 Duo) and ARM processors (like inside every mobile smartphone). Underneath lies security architecture that's completely redesigned to be virus-resistant and easy to update.

 

Like I said, there were plenty of questions. Onwards:
What It Is

• It's basically just a browser: meaning that it'll be based around preexisting web services like Gmail, Google Docs, and so on. There are going to be no conventional applications, just web applications—nothing gets installed, updated, or whatever. Seriously.

• It only runs web apps: It's going to integrate web apps into the operating system deeper than we've ever seen before, meaning that a) they'll seem more like native apps than web apps and b) they'll be able to tap into local resources more than a typical web app in Firefox, for example. They're web apps in name, but they'll have native powers.

• How, exactly?: With HTML 5. This is the next version of HTML, which gives the browser more access to local resources like location info, offline storage—the kinds of things you'd normally associate with native apps. More on that here.

• Chrome is Chrome: The user's experience with Chrome OS will basically be synonymous with their experience on Chrome Browser. Technically speaking, Chrome OS is a Linux-based OS, but you won't be installing Linux binaries like you might on Ubuntu or some other Linux distribution. Any "apps" you have will be used within the browser. Chrome OS is effectively a new version of Chrome, that you can't leave. There are a few reasons Google's pushing this, which we'll get to in a bit.

• And as you've probably guessed, it's super-light. It starts up in a matter of seconds, and boot straight into the browser. Likewise, the Chrome browser is apparently very, very optimized for Chrome OS, so it should be faster than we've ever seen it.

• It won't support hard drives, just solid state storage. I mean, hard drives are dying, sure, but this is pretty bold. Hardware support sounds like it'll be pretty slim, because:

• You'll have to buy a Chrome OS device: You might be able to hack this thing onto your current machine, but you won't just be able to install it to replace Windows, or opt for it on your next laptop, for example. You'll have to buy hardware that Google approved, either component by component, or in a whole package. They're already working on reference designs.

• For now, it's for netbooks. It's not intended for desktops, to the point that Google is saying that the first generation of Chrome hardware will be secondary machines.
How It Looks

• It looks like Chrome browser—specifically, like the leaked shots we saw before. As in a browser, you have tabs—these have to serve as a taskbar as well. To the left of the tabs, you have a sort of start menu, which opens up a panel full of shortcuts. These are your favorites. These are your apps. (Get used to this weird feeling, btw. That Google whole point here.

• You can peg smaller windows, like chat windows or music players, to sit above your tabs at all times. This feature looks a lot like the Gchat feature in Gmail, which is to say, it's a box in the corner.

• Along with tabs, it's got its own version of virtual desktops. This means you can have multiple "windows" of Chrome OS to switch between, each of which is a different set of tabs. Think one desktop for work, one for play, on for porn, etc etc etc. It's a bit like using Spaces on Mac, except only with the browser.
When, and How, It's Coming

Google's staying specifics on the exact release date—it'll be sometime next year—but the source code for the project is published now. That doesn't mean it's ready, really, but rather that they're just planning on developing it in the open from here on out. Expect builds to start showing up online, which'll probably work wonderfully in a virtual machine app like VirtualBox.

The code is available as part of the Chromium OS (the Chromium/Chrome distinction should be familiar to anyone who's wrestled with the open source Mac version of Chrome) project, posted here.
Why It Matters

With Chrome OS, Google is taking (or in a way, forcing) the operating system to go totally online. As Google's freshly designated evangelists are eager to tell you, the browser is already the center of most people's computing experience. The idea here is to make the browser powerful enough to render the rest of the operating system, and its native apps, moot.

It's more pure than a lot of people expected: When Google said that Chrome OS would be centered around the web, I think most people just assumed it would be a lightweight Linux distribution with deep integration for Google web services. It's not that. It's a browser.

But it's a browser that runs different processes for each tab, that will have access to local OS resources, will to some extent work offline. In other words, it's not really a browser in the sense that we use the word, and the web apps that we'll be using won't be like the ones we're used to now, either. The idea, here, it seems, is to replicate most, if not all, of the functionality in a native OS, while keeping the lightweight, ultra-secure framework of a thin client. In other words, Google's not asking much of its users in terms of changing how they do stuff; they're trying to change the way the operating system lets you do those things, transparently.

Think of it this way: now, the buttons in your taskbar or dock are now tabs; your email client now runs within your browser, but stores stuff offline just like Mail or Outlook; your documents will still open with a few clicks, but they'll be stored remotely (and locally only if you choose). It's all the same stuff, given to you in a different way.
Update: you can download it here : http://gizmodo.com/t/chromeos/

 

via gizmodo.com

Filed under: OS

jazzy says...

It´s simple, just a thought. I´m agree that, most of the part, we are on internet. Very good to become an "conditional" Open Source project, lovely thing than Canonical works together with the big G, around the project, but: Do you want an "ubuntized" world?....

Dont create an iso file for simple download is a mess...

In some point, the GNU and the Linux itself project, are outside the show. Reason?: People will think that they are use Google OS, but no Open Source Software.
I don´t like this kind of world....really.... Could be more honest, make a move like Moblin, lettin all the distros work together in a common UI interface...

Intel, in spite of this, I don´t like their politics, was too much fair like OLPC project and Chrome OS.

We cannot speculate the use of a netbook. Limitations creates rejection.
Could be more useful work with a project like Cairo Shell, to transform Windows Shell, and Linux shell?....

mmmm.....some weird posibilities are coming...

P.

Filed under: os

danlazar says...

"Engadget turns the design stakes up to 11, Google finally dishes the dirt on Chrome OS, and now you can even download the forthcoming software to have a fiddle with yourself. It's completely free, though you'll need VMWare running atop a Windows, Linux or OS X installation to make the magic happen."

Filed under: OS

sarikas.at says...





Filed under: OS

Filed under: os

kf says...

Filed under: OS

Google has unveiled the thinking behind Chrome OS, an operating system that rethinks the computer, the desktop and the operating system.

With the Web being the "killer app" for an increasing number of computer users, the proliferation of web-enabled gadgets and the rise of low-cost netbooks with limited built-in memory, Chrome OS may be right on the money.

Filed under: OS