mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-03-21 02:10:11 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
runningwater
commit
08963a2c7b
@ -0,0 +1,44 @@
|
||||
Daily Ubuntu Tips – Restore Your Machine To A Previous State
|
||||
================================================================================
|
||||
When you compare Windows and Ubuntu, you’ll see that Windows has many advantages over Ubuntu and maybe Ubuntu has few over Windows as well. But one feature that stands out is the ability to restore your machine to a previous state. Windows has had this feature going back to Windows XP and worked great at times and can save your a lot of time when you need to fix issues.
|
||||
|
||||
Ubuntu on the other hand don’t have it. You can’t just restore your machine to a previous state in Ubuntu. You may be able to restore individual files and folders but not the entire machine like what Windows does.
|
||||
|
||||
Well, thanks to [TimeShift][1], you may just be able to restore your entire Ubuntu machine to a previous state like Windows. TimeShift may not give you all the benefits that you get in Windows, but it’s a step closer.
|
||||
|
||||
TimeShift is a open source application that provides the same function as Windows Restore in Windows or Time Machine in Mac OS X. It takes snapshots of you system at scheduled time that can be restore in the event you need to undo changes that were made after a snapshot.
|
||||
|
||||
To install TimeShift in Ubuntu, run the command below to add its PPA archive.
|
||||
|
||||
sudo apt-add-repository -y ppa:teejee2008/ppa
|
||||
|
||||
Next, run the commands below to update your system as well as install TimeShift.
|
||||
|
||||
sudo apt-get update && sudo apt-get install timeshift
|
||||
|
||||
After installing it, go to Unity Dash and search for TimeShift. Next launch it and set your preferred settings. When it first launch it may take few minutes scanning your machine for available space and files to backup.
|
||||
|
||||
|
||||
|
||||
If you like the default settings, you can keep. To perform immediate backup, click the Backup button at on the menu. You’ll use the same apps to restore your machine in the event you need to.
|
||||
|
||||
Enjoy!
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.liberiangeek.net/2013/10/daily-ubuntu-tips-restore-machine-previous-state/
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:http://teejeetech.blogspot.com/2013/10/introducing-timeshift.html
|
||||
[2]:
|
||||
[3]:
|
||||
[4]:
|
||||
[5]:
|
||||
[6]:
|
||||
[7]:
|
||||
[8]:
|
||||
[9]:
|
||||
[10]:
|
||||
@ -0,0 +1,35 @@
|
||||
Linux Top 3: RHEL 6.5, Debian 7.2 and EOL for Linux 3.0.x
|
||||
================================================================================
|
||||
**Linux 3.0.100 Released**
|
||||
|
||||
Though it might seem like Linux 3.0 was released just yesterday, the truth is that it was [released back in July of 2011][1].
|
||||
|
||||
Since then some 100 milestone update have been released fixing bugs and providing some security updates. The Linux 3.0.x kernel had been selected as a Long Term Support kernel, meaning that it is maintained for up to two years.
|
||||
|
||||
In August of this year, Linux kernel developer, Greg Kroah-Hartman [declared][2] that the 3.10 Linux kernel would be a longterm support release. That release now supersedes the longterm 3.0.x kernel
|
||||
|
||||
"Linux stable kernel 3.0.100 is now released, please move to 3.4.x or 3.10.x as this might be the last release of 3.0.x," Kroah-Hartman wrote on October 13th.
|
||||
|
||||
**Red Hat Enterprise Linux 6.5 Beta**
|
||||
|
||||
Barely a week after Red Hat released Red Hat Enterprise Linux 5.10, the Linux vendor is now out with a beta release for its next generation platform.
|
||||
|
||||
RHEL 6.5 beta provides support for the precision timing protocol, as an improvement of the traditional network timing protocol (NTP). Precision Time Protocol (PTP) is important to users who require sub-microsecond time stamping of transactions.
|
||||
|
||||
**Debian 7.2**
|
||||
|
||||
Debian is also out with an update. The Debian 7.2 update is the second since Debian 7.x aka Wheezy was released earlier this year.
|
||||
|
||||
"This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems," The Debian project [stated][3]. "Security advisories were already published separately and are referenced where available. Please note that this update does not constitute a new version of Debian 7 but only updates some of the packages included."
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxplanet.com/news/linux-top-3-rhel-6-5-debian-7-2-and-eol-for-linux-3.html
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:http://www.datamation.com/open-source/linux-3.0-debuts-with-xen-integration.html
|
||||
[2]:http://www.eweek.com/developer/linux-3.10-goes-long-term-why-it-matters-for-the-enterprise-consumers/
|
||||
[3]:http://www.debian.org/News/2013/20131012
|
||||
48
sources/New GNOME IRC App ‘Polari’.md
Normal file
48
sources/New GNOME IRC App ‘Polari’.md
Normal file
@ -0,0 +1,48 @@
|
||||
New GNOME IRC App ‘Polari’
|
||||
================================================================================
|
||||
You have to hand it to the GNOME designers and developers: their work in creating a coherent, integrated set of apps for the desktop is showing true promise.
|
||||
|
||||
|
||||
|
||||
*The latest build of Polari in action.*
|
||||
|
||||
In fact, they’ve barely sat still over the last couple of years, creating app after app.
|
||||
|
||||
There are now dedicated apps for Music, Video and Photos; a virtual machine manager in the shape of Boxes; the Maps, Weather & Notes tools are all looking fantastic. And the new GNOME Software Store? Design wise it knocks Ubuntu’s aged offering out of the park!
|
||||
|
||||
But it seems that the GNOME app gurus aren’t done yet. Work has recently begun on a new GNOME 3 IRC app called ‘Polari’.
|
||||
|
||||
*(As an aside, it’s a testament to the focus within the GNOME development community on putting users first that the one tool they likely use most often to communicate is one of the last to get the GNOME app treatment.)*
|
||||
|
||||
## Polari – Planned Features ##
|
||||
|
||||
It’s not fixed in a dusty coding tome that all IRC clients have to resemble something from an 80s sci-fi movie, or be intimidating to the general user. Even in today’s world of instant communications via social networks, IRC remains a great way for people to chat.
|
||||
|
||||
To this end, if [Polari][1] (expect a name change further down the line) had a slogan it would be “*An IRC client for dummies.*”
|
||||
|
||||
- Connect to IRC servers & rooms
|
||||
- Clearly see mentions & notifications
|
||||
- Support GNOME 3 notifications
|
||||
- Integration with Contacts, the GNOME contacts app
|
||||
- History & transcript features
|
||||
- Link previews
|
||||
- File transfers
|
||||
|
||||
Developer-orientated features have also been mooted, including integrated support for Pastebin & Bugzilla.
|
||||
|
||||
So when can you try it? Not quite yet. Development of Polari is still in its early stages, but, if you’re willing to build it from Git (requires GNOME 3.10) you’ll find that it’s already capable of handling the basics, including delivering notifications for mentions.
|
||||
|
||||
For code-compiling-phobes Polari is expected to feature (most likely as an app preview) in GNOME 3.12, due next year.
|
||||
|
||||
- [More about Polari][2]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.omgubuntu.co.uk/2013/10/gnome-irc-app-polari-in-development
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:https://git.gnome.org/browse/polari
|
||||
[2]:https://wiki.gnome.org/Apps/Polari
|
||||
291
sources/Raspberry Pi--the Perfect Home Server.md
Normal file
291
sources/Raspberry Pi--the Perfect Home Server.md
Normal file
@ -0,0 +1,291 @@
|
||||
Raspberry Pi: the Perfect Home Server
|
||||
================================================================================
|
||||
Ever since the announcement of the Raspberry Pi, sites all across the Internet have offered lots of interesting and challenging uses for this exciting device. Although all of those ideas are great, the most obvious and perhaps least glamorous use for the Raspberry Pi (**RPi**) is creating your perfect home server.
|
||||
|
||||
If you've got several different computers in need of a consistent and automated backup strategy, the RPi can do that. If you have music and video you'd like to be able to access from almost any screen in the house, the RPi can make that happen too. Maybe you have a printer or two you'd like to share with everyone easily? The Raspberry Pi can fill all those needs with a minimal investment in hardware and time.
|
||||
|
||||
**Raspberry Pi Benefits**
|
||||
|
||||
Low cost: for $35, the RPi model B is nearly a complete computer with 512MB of RAM, 100Mb Ethernet, an SD card slot, two USB ports, audio out and HDMI or RCA video out. I've seen HDMI cables that cost more than that.
|
||||
|
||||
Energy efficient: hardware costs are only one component of a server's expense, because you also need to consider the energy cost to keep the device running constantly. The services needed for home use aren't going to tax the CPU much, and most of the time it will just be idling, waiting for something to do. The RPi's ultra-low power components are a perfect fit for this workload, which helps keep your power bill down. My model B unit plus external hard drive consume only 8 watts total, while the old Athlon-based box it replaced drew 54 watts at idle. Assuming 10 cents per kilowatt hour, that puts the yearly power bill for an RPi at $7 vs. $47 for an Athlon-based machine. The RPi basically pays for itself in less than a year!
|
||||
|
||||
Low noise: because the RPi doesn't have fans or moving parts, the only component in your final configuration that generates noise or any appreciable heat will be the hard disk. If you're concerned about noise, enthusiast sites like [Silent PC Review][1] often include noise benchmarks in their storage reviews. My experience is that any modern drive is quiet enough to avoid detection anywhere there's something else already running (such as a media center, gaming console or other computer). If your home doesn't provide a lot of flexibility for wiring options, the RPi's small size, minimal thermal output and low-noise footprint may make it possible to sneak in a server where it was difficult to justify one in the past.
|
||||
|
||||
|
||||
|
||||
Figure 1. A Compact, but Highly Capable Home Server
|
||||
|
||||
New opportunities: a less tangible benefit is the simple joy of trying something new! For me, this was my first time really working on a Debian-based distribution, and it's probably the first time many Linux enthusiasts will have a chance to try an ARM-based architecture.
|
||||
|
||||
**Arranging the Hardware**
|
||||
|
||||
For a home server, you'll need a medium-size SD Flash card for local storage. It's possible to use a USB thumbdrive for booting, but that would use up one of the two precious USB slots. The Flash storage card doesn't need to be large, but the faster the better. I chose a name-brand SD card with an 8GB capacity and class 10 speed rating. For backups and multimedia files, a large hard drive with a USB dock is a must. I chose a 1.5TB hard drive and a Calvary EN-CAHDD-D 2-bay USB 2.0 hard drive dock. This dock has a feature to run two drives in RAID-0 mode, which could be useful someday. Finally, the RPi doesn't come with a power supply, but most smartphone chargers supply the required 5v-over-micro USB. To see if the RPi was fussy about the power source, I swapped through three different micro-USB cell-phone chargers for power supplies. I tried each one for about a week, with no issues on any of the units.
|
||||
|
||||
**Installing the Operating System**
|
||||
|
||||
Installing the RPi operating system is covered in extensive detail elsewhere, but here are a few home-server-specific tips, roughly in the order needed.
|
||||
|
||||
1) Get the Raspbian "Wheezy" install image directly from [http://www.raspberrypi.org/downloads][2], and copy it onto the SD card, using the steps listed on the site.
|
||||
|
||||
2) When booting the RPi for the first time, attach a keyboard, mouse and monitor. Don't forget to turn on the monitor before booting the RPi, so that it can detect the correct HDMI or composite output port.
|
||||
|
||||
3) The RPi has a nice "raspi-config" screen that you'll see on first boot. For a home server, the following selections will be useful:
|
||||
|
||||
|
||||
- expand_rootfs: resizes the default 2GB OS image to fill the rest of the Flash card.
|
||||
- change_pass: the default password is "raspberry", but something more secure than that would be better.
|
||||
- Set your locale and timezone.
|
||||
- memory_split: assign the minimum amount possible (16) to the GPU to leave as much room as possible for services.
|
||||
- SSH: don't forget to enable the SSH server.
|
||||
- boot_behaviour: turn off boot to desktop (again, to save memory for your services).
|
||||
|
||||
When finished, you'll be at the `pi@raspberrypi` prompt. The setup script can be re-run at any time via `sudo raspi-config`.
|
||||
|
||||
There are just a few more configuration items, and then the operating system is ready to go.
|
||||
|
||||
1) A static IP makes everything easier, so switch the network settings for eth0:
|
||||
|
||||
>> sudo nano -w /etc/network/interfaces
|
||||
|
||||
change the eth0 line `iface eth0 inet dhcp` to the following (modify to meet your home network setup):
|
||||
|
||||
======/etc/network/interfaces======
|
||||
...
|
||||
iface eth0 inet static
|
||||
address 192.168.1.10
|
||||
netmask 255.255.255.0
|
||||
gateway 192.168.1.1
|
||||
...
|
||||
======/etc/network/interfaces======
|
||||
|
||||
2) Create a local user, and put it in the users and sudo group:
|
||||
|
||||
>> sudo adduser YOURUSERIDHERE
|
||||
>> sudo usermod -a -G users YOURUSERIDHERE
|
||||
>> sudo usermod -a -G sudo YOURUSERIDHERE
|
||||
|
||||
3) Update the system to ensure that it has the latest and greatest copies of all the libraries:
|
||||
|
||||
>> sudo apt-get update; sudo apt-get upgrade
|
||||
|
||||
4) At this point, you're ready to go headless! Shut down the PI:
|
||||
|
||||
>> sudo /sbin/shutdown -h now
|
||||
|
||||
Once it's down (monitor the green status LEDs on the RPi circuit board to know when it has finished shutting down), unplug the monitor, keyboard, mouse and power cord. Attach the USB storage, then restart the RPi by plugging the power back in.
|
||||
|
||||
5) Once the RPi starts up (again, those green LEDs are the clue to its state), you can ssh in to the RPi from any other machine on the network and finish all the configuration remotely from here on out (modify the following for your static IP):
|
||||
|
||||
`>> ssh YOURUSERIDHERE@192.168.1.10`
|
||||
|
||||
Congratulations, you have a working Raspberry Pi!
|
||||
|
||||
**Peripherals**
|
||||
|
||||
The first order of business is to get the external storage device mounted. Use dmesg to look for where the storage device was found—it almost certainly will be /dev/sda. I like using automounter to handle mounting removable storage devices, as it is more flexible about handing devices that may not be present or ready at boot time:
|
||||
|
||||
>> sudo apt-get install autofs
|
||||
>> sudo nano -w /etc/auto.master
|
||||
======/etc/auto.master======
|
||||
...
|
||||
/misc /etc/auto.misc
|
||||
...
|
||||
======/etc/auto.master======
|
||||
|
||||
>> sudo nano -w /etc/auto.misc
|
||||
|
||||
Note, my external storage device is formatted with ext4—modify this for your needs if required:
|
||||
|
||||
======/etc/auto.misc======
|
||||
...
|
||||
storage -fstype=ext4:/dev/sda1
|
||||
...
|
||||
======/etc/auto.misc======
|
||||
>> sudo /etc/init.d/autofs restart
|
||||
>> ls -lat /misc/storage
|
||||
|
||||
Optionally, create a symlink to shorten the path a smidgen:
|
||||
|
||||
>> ln -s /misc/storage /storage
|
||||
|
||||
**Backup Repository**
|
||||
|
||||
At the top of any home server feature list is providing rock-solid backups. With the RPi, this is pretty simple, due to the wide range of network-sharing options in Linux: Samba/CIFS for Windows machines, NFS for UNIX-based devices and even SFTP for more advanced backup clients like deja-dup. Because the RPi has only 100Mb Ethernet, and the storage device is on USB, it's not going to have super-fast transfer speeds. On the other hand, good backup clients run automatically and in the background, so it's unlikely that you'll notice the slightly slower transfer speeds.
|
||||
|
||||
My home network includes one Windows 7 machine. For it, I exported a backup directory on the RPi's external USB storage device via Samba. Because the backup utility in the basic version of Windows 7 doesn't support network drives as a backup destination, I used [SyncBack Free][3] to set up automated, daily backups.
|
||||
|
||||
Configuring Samba is simple.
|
||||
|
||||
1) Install the samba and common-bin library (which has the smbpasswd utility):
|
||||
|
||||
>> sudo apt-get install samba samba-common-bin
|
||||
|
||||
2) Use `smbpasswd` to let your local ID have access:
|
||||
|
||||
>> sudo smbpasswd -a YOURUSERIDHERE
|
||||
|
||||
3) Edit the samba configuration file:
|
||||
|
||||
>> sudo nano -w /etc/samba/smb.conf
|
||||
|
||||
4) Change the `workgroup = WORKGROUP` line to match your Windows workgroup name.
|
||||
|
||||
5) Comment out or delete the [homes] and [printers] share. (Printer sharing will be done later via direct CUPS access.)
|
||||
|
||||
6) Add an entry for the Windows backup paths. Here's my example, which I placed at the bottom of the file:
|
||||
|
||||
======/etc/samba/smb.conf======
|
||||
...
|
||||
[win7pc]
|
||||
comment=Backup for windows PC
|
||||
path=/storage/win7pc
|
||||
writeable=Yes
|
||||
create mask=0777
|
||||
directory mask=0777
|
||||
browsable=Yes
|
||||
public=Yes
|
||||
valid users=YOURUSERIDHERE
|
||||
...
|
||||
======/etc/samba/smb.conf======
|
||||
|
||||
7) Restart Samba to implement your edits:
|
||||
|
||||
>> sudo /etc/init.d/samba restart
|
||||
|
||||
8) Test connectivity from the Windows machine by mapping a network drive from the file explorer.
|
||||
|
||||
For Linux devices, deja-dup is brilliantly simple to set up and use. It's been installed by default on both my Fedora 18 and Ubuntu 12.10 installs. While the package name is "deja-dup", the front end is simply called "Backup". Although the RPi easily could support NFS export, I've found that using deja-dup's SSH option is easier and more portable, and it eliminates the need for an additional service on the RPi. Specifying a deja-dup encryption password is probably a good idea, unless you like the idea of all your files walking off if someone pockets the storage drive:
|
||||
|
||||
>> sudo mkdir /storage/linuxlaptop
|
||||
>> sudo chown -R YOURUSERIDHERE:YOURUSERIDHERE /storage/linuxlaptop
|
||||
|
||||
From the client Linux machine, launch the backup utility, choose "SSH" as the backup location, and enter the RPi's IP address and the storage location you just created. The first backup will be slow, but future runs will be sending only incremental changes, which is significantly faster.
|
||||
|
||||
|
||||
|
||||
Figure 2. Deja-dup Client Setup
|
||||
|
||||
**Multimedia Server: DLNA**
|
||||
|
||||
Now that everyone's files are backed up safely, let's move on to some fun! A DLNA server will give you a central place to store your movies, music and pictures. From this central repository, DLNA clients from every screen in the house can play back this content with ease.
|
||||
|
||||
At least, that's the promise. The reality is that the DNLA specs don't quite nail down many important things like which formats or encodings are supported. Each client typically has a slightly different idea of what formats and server features it would like to support. A much higher-power server might be able to transcode local content to device-supported formats on the fly, but that's not possible on the RPi, and the on-the-fly transcoding often messes up other features like pause, fast-forward and rewind. In general, higher-powered devices like the PS3, Xbox and WD TV devices can handle most formats without any transcoding. Lower-end devices like smart TVs or Blu-ray players support a much more limited list of codecs.
|
||||
|
||||
For the RPi, your best bet is simply to encode to the standards your primary DLNA device supports and then test your other DLNA clients. If they won't play nicely, the tips in the next section may help. In my case, my PlayStation 3 acts as the DLNA client, which plays nicely with the compact .m4v files generated by Handbrake.
|
||||
|
||||
Minidlna is a great choice for the RPi DLNA server. It's already in the Raspbian distribution, is quite simple to set up and uses minimal server resources while running:
|
||||
|
||||
>> sudo apt-get install minidlna
|
||||
>> sudo nano -w /etc/minidlna.conf
|
||||
|
||||
Here are the relevant sections of my /etc/minidlna.conf:
|
||||
|
||||
...
|
||||
# I found keeping video + audio in different paths helpful
|
||||
media_dir=V,/storage/dlna/video
|
||||
media_dir=A,/storage/dlna/music
|
||||
...
|
||||
presentation_url=http://192.168.1.10:8200/
|
||||
...
|
||||
friendly_name=MyRPi
|
||||
...
|
||||
# Since I add new media infrequently, turning off
|
||||
# inotify keeps minidlna for polling for
|
||||
# content changes. It's simple enough to run
|
||||
# sudo /etc/init.d/minidlna force-reload
|
||||
# when new content is added.
|
||||
inotify=no
|
||||
|
||||
Once done editing, tell minidlna to restart and rescan for content:
|
||||
|
||||
>> sudo /etc/init.d/minidlna force-reload
|
||||
|
||||
Minidlna has the ability to provide movie-poster thumbnails for your movies for devices that support it (like the PS3). It makes finding a specific movie when scrolling through dozens of movie files much more convenient. I've found that the most compatible file layout is to have one directory per movie, containing just the movie file plus the thumbnail image named "Cover.jpg". Using a format like "MovieName.m4v" and "MovieName.jpg" works fine for the PS3, but it breaks VLC (if you can convince the VLC uPNP plugin to find the server in the first place).
|
||||
|
||||
From the PS3, you can test connectivity by going to "Video" on the XMB bar. The "friendly_name" you set previously should be visible when scrolling down in the Video section. If you cant find it, test to ensure that Minidlna is up by going to http://192.168.1.10:8200/ with a Web browser.
|
||||
|
||||
**Multimedia for Non-DLNA Devices**
|
||||
|
||||
Once you get DNLA working with some of your devices, you may find devices it doesn't want to work with, so a multimedia plan B is a good idea. The nginx Web server has an MP4 plugin that tries to improve streaming over plain-old HTTP, but browser playback performance varied widely, and fast-forwarding within a movie didn't work consistently either. It seems like the lowest common denominator for multimedia sharing across fussy or non-DLNA devices is a good-old-fashioned Samba share with guest read-only access.
|
||||
|
||||
Here's an sample section from /etc/samba/smb.conf:
|
||||
|
||||
[dlna]
|
||||
path=/storage/dlna
|
||||
read only=yes
|
||||
browsable=yes
|
||||
public=yes
|
||||
|
||||
After defining the share and restarting Samba (`sudo /etc/init.d/samba restart`), you can start to test out your clients.
|
||||
|
||||
I tested the following clients with a mix of videos encoded with Handbrake as m4v files:
|
||||
|
||||
- Android 4.0.4 phone: "ES File Explorer" with "ES Media Player" (player comes with install).
|
||||
- Android 4.1.2 tablet: "ES File Explorer" with "ES Media Player" (player comes with install).
|
||||
- Linux devices: automount ://192.168.1.10/dlna, then use VLC or MPlayer.
|
||||
- Windows: mount //192.168.1.10:/dlna, then use VLC.
|
||||
|
||||
All devices were able to start playing almost instantly and fast-forward with no delays.
|
||||
|
||||
**Print Server**
|
||||
|
||||
The RPi runs CUPS quite well, so it's easy to share an older printer that doesn't have native networking features.
|
||||
|
||||
Install CUPS and any packages needed by your printer. I needed hplip-cups since I have an HP inkjet printer:
|
||||
|
||||
>> sudo apt-get install cups hplip-cups
|
||||
|
||||
Update the "Listen" line and add the `Allow @LOCAL` block to the Location directives as shown below (so you can use other machines on your LAN to administer CUPS):
|
||||
|
||||
======/etc/cups/cupsd.conf======
|
||||
#Listen localhost:631 #Comment this out
|
||||
Listen 192.168.1.10:631 #Add this line
|
||||
...
|
||||
<Location />
|
||||
Order allow,deny
|
||||
Allow @LOCAL
|
||||
</Location>
|
||||
|
||||
# Restrict access to the admin pages...
|
||||
<Location /admin>
|
||||
Order allow,deny
|
||||
Allow @LOCAL
|
||||
</Location>
|
||||
|
||||
# Restrict access to configuration files...
|
||||
<Location /admin/conf>
|
||||
AuthType Default
|
||||
Require user @SYSTEM
|
||||
Order allow,deny
|
||||
Allow @LOCAL
|
||||
</Location>
|
||||
======/etc/cups/cupsd.conf======
|
||||
|
||||
Add your local ID to the lpadmin group so you can administer CUPS:
|
||||
|
||||
>> sudo usermod -a -G lpadmin YOURUSERIDHERE
|
||||
|
||||
Restart CUPS:
|
||||
|
||||
>> sudo /etc/init.d/cups restart
|
||||
|
||||
Then, go to http://192.168.1.10:631/ and click "Adding Printers and Classes" to set up your printer. My printer was auto-discovered on the USB, so all I had do to was click "share". Also access https://192.168.1.10:631/admin, and make sure to check "Share printers connected to this system".
|
||||
|
||||
Once you're done, you can set up your clients the usual way. My Linux clients auto-discovered the printer and picked the right printer drivers once I entered the hostname. On my Windows 7 machine, once I selected "Network Printer", I had to click "The printer that I want isn't listed", select "Select a shared printer by name" and then enter the URL from the CUPS Web interface: http://192.168.1.10:631/printers/HP_J4500.
|
||||
|
||||
**Conclusion**
|
||||
|
||||
With a minimal amount of additional hardware and configuration, the Raspberry Pi can be a highly capable, compact home server. It can bring the wide range of enterprise services offered by Linux into a home environment with minimal hardware expense.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.linuxjournal.com/content/raspberry-pi-perfect-home-server
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:http://www.silentpcreview.com/
|
||||
[2]:http://www.raspberrypi.org/downloads
|
||||
[3]:http://www.2brightsparks.com/freeware/freeware-hub.html
|
||||
65
sources/Ubuntu 13.10--It just works.md
Normal file
65
sources/Ubuntu 13.10--It just works.md
Normal file
@ -0,0 +1,65 @@
|
||||
Ubuntu 13.10: It just works
|
||||
================================================================================
|
||||
**Find out why Jack Wallen thinks that Ubuntu 13.10 is a solid, reliable platform that just works. Do you agree? **
|
||||
|
||||
|
||||
|
||||
I've been using Ubuntu for a very long time. I was one of the few in the media who adopted Unity as my primary desktop interface. In fact, I've grown so used to Unity that I have trouble finding any form of efficiency in other desktops. So, naturally, when a new Ubuntu release is about to be unleashed upon the world, I grab a beta and install it.
|
||||
|
||||
The hype surrounding the upcoming 13.10 (Saucy Salamander) was fairly significant. Leading this charge was the much-anticipated switch to Xmir. Well, thanks to a few show-stopping issues (such as dual-monitor support), Xmir has been pushed back to 14.04. Is this a big deal? Yes and no. Yes, because Xmir will be a major change to the sub-systems of Ubuntu. No, because Xmir must be faultless when released -- otherwise, the backlash will knock Canonical back so far in the past that they'll have a hard time recovering in the eyes of the Linux community.
|
||||
|
||||
Beyond Xmir, the biggest change from .04 to .10 is the much-maligned inclusion of Smart Scopes. What are Smart Scopes? Let me explain it in the simplest terms as possible.
|
||||
|
||||
When you open your browser and begin typing a string of characters, you know how that browser will make suggestions for you based on search terms, location, and history? Smart Scopes brings that same functionality to the desktop. I've run some tests on it, and it's pretty incredible. Search for nearly anything, and it will return results based on a number of criteria. Want to know the location of a restaurant in your area? I conducted a search for my favorite Mexican restaurant, Bazos, and an entry appeared in Smart Scopes (**Figure A**). Click the entry to get the address or open that entry in a web browser to get more information (and even reviews).
|
||||
|
||||
**Figure A**
|
||||
|
||||
|
||||
|
||||
**My favorite place to eat listed in Smart Scopes.**
|
||||
|
||||
I get it, there are people out there suffering from apoplectic fits of terror because Smart Scopes is an invasion of privacy. This is no different than what your web browser is doing. So, unless you constantly run your web browser in Incognito mode, all those search strings are saved and compared anyway. And the truth is, why wouldn't you want your search results based on your preferences and behavior instead of some generic algorithm? Personally, I don't mind my search results being quantified and qualified, so long as it constantly refines the search results based on my needs.
|
||||
|
||||
Smart Scopes isn't limited to seeking out search results from the network. You'll be happily searching for anything and everything on your local (or locally attached) drives as well. With this inclusion, Smart Scopes becomes one of the single most powerful search tools available.
|
||||
|
||||
Of course, if you don't like Smart Scopes, you can turn them off. Here's how:
|
||||
|
||||
1. Click the Settings launcher
|
||||
1. Select Security & Privacy
|
||||
1. In the Search tab, turn Include online search results to Off (**Figure B**)
|
||||
|
||||
**Figure B**
|
||||
|
||||
|
||||
|
||||
**It's easy to turn off the Smart Scopes feature.**
|
||||
|
||||
With all of that said, let's step away from the arguments for or against search privacy and let me explain exactly why Ubuntu 13.10 is the perfect desktop for nearly any user.
|
||||
|
||||
The install was fresh from the latest daily build. During the installation, I included third-party software, updates, and was even able to authenticated to my UbuntuOne account. The install was incredibly simple (as most modern Linux distributions are), and at first login, everything was smooth.
|
||||
|
||||
What initially struck me about Ubuntu 13.10 is how everything worked out of the box. There was no need to install codecs to listen or view various multi-media files, flash worked, and everything was ready for average, daily computer use. You could work on office documents, set up your email account... you name it. But that has become the standard operating procedure for Ubuntu.
|
||||
|
||||
So, what's different? Honestly, not much. However, what little difference there is should go a long way with the average user. Probably the single most important thing I've found is that a lot of the little quirks and oddities are gone. There are no longer any strange errors that randomly pop up to cause confusion and disdain among new users. Windows don't artifact or stall, the Dash is very responsive (as is Smart Scopes), and the compositing is smooth and effortless against your CPU. Also, the bug is resolved that plagued the Dash when trying to use the arrow keys to navigate through search results.
|
||||
|
||||
## Ubuntu 13.10 just works ##
|
||||
|
||||
I would go as far to say that Ubuntu has done to the desktop what Apple did with hardware/software -- it developed a clean, solid convergence of pieces to create a cohesive whole. Although that whole has ruffled some feathers, Ubuntu 13.10 should go a long way to smooth them out. How is that possible, considering how many users have turned their back (thanks to [the Wayland kerfuffle][1])?
|
||||
|
||||
Outside of Smart Scopes, there are no major changes. There's little excitement on the desktop -- it's still the same old look and feel. Oh sure, there are tiny tweaks here and there, but overall, 13.10 and 13.04 look the same at first blush. Under the hood? Same thing. You'll find a new kernel (3.11) and a few other tweaks, but nothing to cause the cheerleaders of the world to frustratingly toss their pompoms in the air.
|
||||
|
||||
Instead, Ubuntu 13.10 is a refinement of something that was already there and polished. There are no show stopping or curtain call worthy new features -- just countless tweaks here and there that make the whole system run smooth and fast.
|
||||
|
||||
The final release of Saucy Salamander is set for October 17, 2013. You can get a copy of the [daily build][2] or wait for the release date. Either way, you're going to get a solid, reliable platform that just works.
|
||||
What are your thoughts about Saucy Salamander? Share your opinion in the discussion thread below.
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: http://www.techrepublic.com/blog/linux-and-open-source/ubuntu-1310-it-just-works/
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创翻译，[Linux中国](http://linux.cn/) 荣誉推出
|
||||
|
||||
译者：[译者ID](https://github.com/译者ID) 校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
[1]:http://www.techrepublic.com/blog/linux-and-open-source/the-canonical-conundrum-why-the-ubuntu-hate/
|
||||
[2]:http://cdimage.ubuntu.com/daily-live/current/
|
||||
Loading…
Reference in New Issue
Block a user