Tag-Archive for » ubuntu «

Sunday, August 04th, 2013 | Author:

Stair

Bhí athrú i bhfad ó luaigh mé mo deireanach freastalaí pearsanta – tá sé tar éis fás ag Raidió Rí Rá (Tá sé anois ina 7TB md RAID6) agus bhí sé atógadh le déanaí le Ubuntu Freastalaí.

Arch Ní raibh botún. Arch Linux bhí múinte cheana féin dom an oiread sin faoi Linux (agus leanfaidh sé sin a dhéanamh ar mo dheasc eile). Ach Éilíonn Arch cinnte níos mó ama agus aird ná mar ba mhaith liom a chaitheamh ar fhreastalaí. Go hidéalach, ba mhaith liom is fearr a bheith in ann a dearmad a dhéanamh ar an bhfreastalaí ar feadh tamaill go dtí go deir r-phost meabhrúcháin “tamall de bhlianta anuas … níl nuashonruithe cúpla ba chóir duit féachaint ar, buddy.”

Níl spás saor in aisce – agus nách spás

Bhí an deis dul ar imirce chun Ubuntu an bhfíric go raibh rith mé amach as SATA calafoirt, na calafoirt is gá chun thiomáineann crua a nascadh leis an gcuid eile den ríomhaire – Úsáideann an sraith Raid 7TB a lán de na calafoirt! Bhí mé fiú a tugadh ar shiúl mo an- sean dhiosca crua 200GB mar a thóg sé suas ar cheann de na calafoirt. Rabhadh mé freisin an faighteoir go bhfuil an diosca ar SMART monatóireachta le fios go raibh sé neamhiontaofa. Mar workaround sealadach chun an easpa calafoirt SATA, Bhí mé aistríodh fiú OS an fhreastalaí le sraith de cheithre bataí USB i md RAID1. Crazy. Tá a fhios agam. Ní raibh mé ró-sásta mar gheall ar an luas. Bheartaigh mé dul amach agus a cheannach tiomáint crua iontaofa nua agus cárta leathnú SATA chun dul leis é.

Cuireadh laindéal bunscoile Arch an fhreastalaí a úsáideann thart ar 7GB de diosca. A smután mór de go raibh babhtála comhad, sonraí i dtaisce agus comhaid ilghnéitheacha eile nó nach bhfuil gá. Tríd is tríd an méid iarbhír an OS, lena n-áirítear an /baile fillteán, raibh ach thart ar 2GB. Spreag sé seo dom chun breathnú isteach i Super-tapa SSD tiomáint, ag smaoineamh b'fhéidir nach mbeadh ceann níos lú a bheith chomh costasach. Iompaigh sé amach go bhfuil an feachtas saoire neamh-SSD raibh mé in ann teacht ar iarbhír costas níos mó mó ná ceann amháin de na SSDs réasúnta beag. Yay for me. 🙂

Rogha? Woah?!

I roghnú an OS, Ba mhaith chinn mé cheana féin nach mbeadh sé Arch. Lasmuigh de na dáiltí eile tóir, Tá mé an chuid is mó eolas maidir leis Ubuntu agus CentOS. Fedora Bhí freisin an deis ann – ach ní raibh a mheas mé dáiríre fós é ar feadh freastalaí. Bhuaigh an babhta ubuntu.

An cinneadh eile a bhí mé a dhéanamh nach raibh a tharlaíonn go dom go dtí go Ubiquity (Draoi suiteála Ubuntu ar) D'iarr sé orm: Conas a chur ar bun ar an Deighiltí.

Bhí mé nua chun úsáid a bhaint as SSDs i Linux – Tá mé go maith an eolas faoi na pitfalls de nach n-úsáideann iad i gceart, den chuid is mó mar gheall ar a riosca fadsaoil bochta má mí-úsáid.

Ní raibh mé ag iarraidh úsáid a bhaint as dheighilt babhtála tiomnaithe. Plean mé ar uasghrádú an fhreastalaí motherboard / LAP / cuimhne nach bhfuil i bhfad ró-sa todhchaí. Bunaithe ar sin chinn mé go mbeidh mé babhtála i gcomhad babhtála ar an Raid md atá ann cheana féin. Ní bheidh an babhtála a bheith go háirithe go tapa ach beidh a chuspóir amháin a bheith le haghaidh an ócáid ​​annamh nuair atá rud éigin mícheart agus nach bhfuil an chuimhne atá ar fáil.

D'fhág mé ansin a thabhairt ar an cosán fhréamh an 60GB iomlán amach ar Intel 330 SSD. Mheas mé a scaradh / bhaile ach an chuma air ach beagán pointless, thabhairt ar conas is beag a úsáideadh san am atá thart. Leag mé an chéad suas an laindéal le LVM – rud éigin a bhí mé le déanaí ag déanamh aon uair a leag mé suas le bosca Linux (i ndáiríre, níl aon leithscéal gan úsáid a bhaint LVM). Nuair a fuair sé an chuid i gcás ina mbeadh liom a chumrú córas comhad, Chliceáil mé ar an anuas agus instinctively roghnaithe ext4. Ansin thug mé faoi deara btrfs ar an liosta céanna. Hang on!!

Ach cad?

Btrfs (“im-eff-CSE”, “níos fearr eff-CSE”, “bee-crann-eff-CSE”, nó is cuma cad mhaisiúil tú ar an lá) tá córas comhaid sách nua a fhorbairt chun go mbeidh Linux’ cumais córas comhad ar ais ar an rian le córas comhad reatha ardteicneolaíochta. An Rí-ar-an-Hill atá ann cheana féin córas comhad, “ext” (an leagan reatha a dtugtar ext4) Is maith go leor – ach tá teorainn léi, bhfostú i paraidím d'aois (smaoineamh ar branda nua F22 Raptor vs. le F4 Phantom le iarracht leath-jested ag uasghrádú a ghlacadh) agus is dócha a bheith in ann dul san iomaíocht le haghaidh an-fhada le córais comhaid le Fiontraíocht níos nuaí mar ZFS Oracle. Btrfs Tá fós bealach fada chun dul agus meastar é fós turgnamhach (ag brath ar cé tú ceisteanna a chur agus cad iad na gnéithe is gá duit). Go leor a mheas sé a bheith cobhsaí lena n-úsáid bhunúsach – ach tá aon duine ag dul a dhéanamh ar aon ráthaíochtaí. Agus, ar ndóigh, gach duine ag rá a dhéanamh agus a thástáil cúltacaí!

Mooooooo

Is é an difríocht is bunúsaí idir fo-líne agus btrfs go bhfuil btrfs a “Bó” nó “Cóip ar Scríobh” córas comhad. Ciallaíonn sé seo go riamh go bhfuil na sonraí iarbhír overwritten d'aon ghnó ag an córas comhad ar internals. Má scríobhann tú athrú ar comhad, Beidh btrfs scríobh do chuid athruithe go dtí suíomh nua ar mheáin fhisiciúla agus beidh cothrom le dáta an leideanna inmheánacha a tharchur chuig an suíomh nua. Btrfs a théann céim eile sa mhéid is go na leideanna inmheánacha (dá dtagraítear mar meiteashonraí) Tá freisin Bó. Bheadh ​​leaganacha níos sine de fo-líne a bheith ach overwritten na sonraí. Bheadh ​​Ext4 úsáid Iris chun a chinntiú nach mbeidh éilliú tarlú ba chóir an breiseán AC a yanked amach i láthair na huaire is inopportune. Na torthaí iris i líon céanna de céimeanna a theastaíonn chun sonraí a thabhairt cothrom le dáta. Le SSD, Feidhmíonn an crua-earraí bunúsacha próiseas bó den chineál céanna is cuma cén córas comhaid tá tú ag baint úsáide as. Tá sé seo toisc nach féidir thiomáineann SSD forscríobh iarbhír sonraí – tá siad a chóipeáil na sonraí (le do chuid athruithe) go dtí suíomh nua agus ansin scriosadh an bloc sean go hiomlán. Tá leas iomlán a bhaint sa réimse seo ná nach bhféadfadh SSD scriosadh fiú an bloc d'aois ach go simplí a dhéanamh nóta a scriosadh an bloc ag tráth níos déanaí nuair nach bhfuil rudaí chomh gnóthach. Is é an toradh deiridh go cuí thiomáineann SSD go han-mhaith le córas comhaid bó agus nach bhfuil a dhéanamh chomh maith le córais comhaid le neamh-bó.

Chun a dhéanamh cúrsaí suimiúla, Bó sa chóras comhad a théann go héasca lámh ar láimh le gné ar a dtugtar deduplication. Ligeann sé seo dhá (nó níos mó) bloic comhionann le sonraí a stóráil ag baint úsáide as ach cóip amháin, spás a shábháil. Le bó, má tá an comhad mionathraithe deduplicated, Ní bheidh na focail ar leith tionchar a bheith mar beidh an comhad a mhodhnú ar shonraí a bheith scríofa bloc éagsúla fisiciúil.

Déanann bó i ndiaidh a snapshotting réasúnta éasca a chur i bhfeidhm. Nuair a pictiúr a dhéanamh taifead ar an gcóras ach an pictiúr nua a bheith ina dúbailt na sonraí agus na meiteashonraí laistigh den toirt. Le bó, nuair a dhéantar athruithe, tréimhsí an pictiúr shonraí slán, agus is féidir d'fhonn teacht ar an córas comhaid stádas ag an am a rinneadh an pictiúr a choinneáil.

A chara nua

Leis an méid sin thuas i gcuimhne, go háirithe mar tá Ubuntu ar btrfs ar fáil mar rogha shuiteáil-am, Figured mé go mbeadh sé ina am trátha chun tumadóireacht a dheanamh i btrfs agus beagán iniúchadh. 🙂

Cuid 2 ag teacht go luath …

Comhroinn
Thursday, January 01st, 2009 | Author:

Apparently, what operating system you use can say a lot about you. If you’re using some form of *nix, which distro you’re using can say a lot as well. Redundancy aside, I believe that a Linux distribution depends absolutely on its package management and distribution system.

I liked apt-get (1, 2) but there was some technical problem at some point and it caused me to use aptitude instead. Using aptitude is slightly easierit has more features automated into single, logical, commands where apt-get requires separate commands. Aptitude also has a curses-based GUI. If you’re not using the GUI then, other than brevity in terms of number of commands to learn, there is apparently no technical reason to prefer one over the other. Aptitude and apt-get serve K/X/Ubuntu agus Debian go maith. From this point, I use the names Kubuntu and Ubuntu in a loosely interchangeable fashion.

In my use of CentOS (based on Red Hat), I’ve found I like yum. It seems to work in much the same as aptitudeone command to rule them all. It has some rather annoying default behaviour I’m not going to get into here as its most likely because I’m just not used to it. At least from a technical perspective, it is very good. I believe that Fedora also makes use of yum though my experience with Fedora is very limited.

the theory

Fedora and Ubuntu are in a class of distributions that have a fairly rigorous release cycle. Ubuntu 8.10 (the version is named so for the year and month of its release) will not, except for major bugs and minor changes, have another major update until the next version, Jaunty Jackalope. Ubuntu users have the latest versions of most software on their desktops right now. In the months preceding the next release, however, they’re not going to be so lucky unless they like using “béite” releases. As I’m not very familiar with Fedora, I’m not going to bother going into its release cycle.

These 2 distributions are also within a class of distributions known asbinary” nó “binary-baseddistributions. This means that when you download an update, the files that are downloaded are precompiled and should run on anysupportedhardware. This isn’t specifically optimised for your desktop’s hardware, for example, your processor. Perhaps you have an AMD processor which has extra instruction support which Intel CPUs do not have. The reverse could also be true. For this reason, a binary-release distribution cannot optimise for one particular brand of hardware. Regardless of thisnon-optimisation”, it should run at a decent pace.

the practice!

Maidir 2 years ago I started using Kubuntu. After a few months of working with it, I started to learn more about its specifics. I’m not much of a fan of using GUI tools to update the system when, ultimately, its all happening on the command-line anyway. The GUI tools just hide the complexity I don’t mind seeing.

I ended up making a Eabhrac script, update, which would run all the steps required to get aptitude to just go ahead and upgrade already, kthx?©, perhaps stopping along the way to back up my configuration, remount the NFS network share where we keep an on-site repository, back up the local cache of aptitude’s installed packages, do some folder-link shuffling to use a local copy if the network share couldn’t remount, sync between the local copy and the network share if the previous update had a network share issue, and update lists of packages in the repository. In general, it wouldn’t go ahead if there were any errors though, as you can tell, this script became a messy beast that went above and beyond the original requirements. It worked well for me.

Until the day came to update between Kubuntu 6.10 go 7.04. I did this manually though, not with the script.

I ended up reinstalling from scratch as a result of the mess that ensued. At least, as a backup administrator should do well to demonstrate, it was easy to recover everything I really needed. 🙂

What else is out there?

Even before I had to reinstall Kubuntu, I was introduced to another distribution called Gentoo. There are 2 very distinct differences between Gentoo and Ubuntu’s update system. The first is that Gentoo is a source-based distribution. This means that when you update a package, the package manager downloads the source and compiles everything, hopefully optimising it for your system. This, I think, is very cool. The downside to this is that compiling everything takes a very long time.

Here are my (very unscientific) estimates for the length of time it takes to install a basic GUI OS to a desktop from installation media, excluding extraneous drivers (for example, the latest 3D graphics drivers):

OS: minmax (median)

Windows Vista: 15 – 30 (20) minutes

Ubuntu: 15 – 40 (20) minutes

Gentoo: 3 – 40 (6) hours

Gentoo also requires much tinkering with the config files in order to get things workingthis is another reason for the extremely long delay between inserting the CD and booting your awesome* new desktop. Popular applications have binary packages available for downloadthough this isn’t a default option.

They see me rollin

There is one more very important distinction Gentoo has from most other distributions. It is arolling-releasedistribution. This means that there isn’t any rigorous version orreleasethat the distribution adheres to. If you install Gentoo todayif you finish installing Gentoo today, you’re probably going to have the latest version of all the applications you installed. If some obscure application gets a major update tomorrow, within a few days, if you update your system, you’re going to have that latest version on your desktop.

The difference between this rolling release and theotherdistributions is rather staggering. Mar shampla: If KDE 4.2 were to be released tomorrow, you’d probably have to wait less than 2 weeks for it to be available on Gentoo. Ubuntu users might have to wait till 9.04 – that’s a 4-month wait.

Something more suitable?

Personally, I’m not willing to put in the 40 hours of effort to get my system working the way I want it to. My colleague had to reinstall recently for some obscure reason and it turns out he wasn’t willing to put in the 6 hours (he’s more experienced with Gentoo) of effort to get his system back to how it was running either. Instead, Arch Linux caught his eye. Arch Linux is a rolling-release (like Gentoo), binary-based (like Ubuntu) distribution. Its packages (go maith, the vast majority of them) don’t need much tinkering with their config files to get things working nicely either. Its the best of both worlds!

You still need to know what you’re doing* but if you’ve come to this juncture, it shouldn’t be such a giant leap of faith. Arch Linux’s package manager, called pacfear, has built-in dependency and conflict handling. I use another package manager, yaourt (French for yoghurt), which has very quickly become popular with Arch users. Yaourt enhances the functionality of pacman by allowing you to download and install applications directly from the AUR, nó Arch User Repository. This repository contains scripts that allow you to automatically download and install many applications that would otherwise be completely unsupported by Arch’s own core developers. It downloads and compiles the package into a chroot’d environment. It then packages the chroot’d environment into a pacman-compatible package tarball and uses pacman to deploy it into your system.

chomh maith leis sin, the AUR supports a voting system whereby popular packages get placed into the more official [community] repository. Yaourt also supports an automated voting mechanism whereby, after installing a package via AUR, it asks if you want to vote for its inclusion in [community].

I estimate that the time taken for my Arch installation was about 90 minutes. I don’t recommend Archlinux for newbies though I do recommend it for any Linux user who’s gotten bored with other distrosand wants to get into the nitty gritty without having to install Linux From Scratch. Arch Linux has been getting pretty popular these days. Its currently at number 14 on Distrowatch.

* IF you know what you’re doing. AND YOU BETTER BLOODY KNOW WHAT YOU’RE DOING!
Comhroinn