kad 0% informativo

Las andanzas virtuales de mi cuerpo físico

Wanted: DBA Ninja, Systems Engineer Soldier

So, long time no see... I'll post a proper update later, but for now I am here to tell you that we (our team at digg.com) are looking for someone with Kick-Ass DBA Skills™ as well as someone that makes the cut for a Systems Engineer. If you:
  • Enjoy databases
  • Like kicking hard problems in the butt
  • Get excited at the prospect of wading through enormous quantities of data
  • Know your way around MySQL
  • Can estimate network/db/page latency at a glance
  • Are open minded about what the future of databases will bring
  • Get warm and fuzzy feelings when working with open source tools day and night
OR:
  • Speak in terms of datacenters
  • Like running complicated scripts making potentially dangerous operations across tons of servers (and know how to fix everything if it breaks)
  • Enjoy the thrill of production live changes
  • Hack python code and bash scripts to automate stuff you don't want to do
  • Know enough perl and/or ruby to find your way around (CPAN, gems, essential linguistics)
  • Know or -even better!- have worked with puppet
  • Debian (or any other distro) packaging experience
You are likely to fit in nicely with our eclectic group. This is what you will get:
  • An awesome working environment
  • To be part of a bad-ass team
  • To play with the most recent toys in terms of databases
  • A large environment to mold as you see fit
  • Standard bay-area startup stuff
  • Interesting stuff to do every day
We work mostly with debian but, really, you won't notice the difference even if you come from another linux-flavored background. You MUST know linux/unix, a lot of it, that's for sure.
If you think you have what it takes (or know someone who does) shoot me an email with your resume to kad at the company I work for. The job is located in San Francisco, CA, USA. So you must have the means (legal, language, etc) to move here and work here.
Besides the above, digg is hiring!, so if you see something that catches your eye, shoot me an email.

Fedora XII is out

Creo que el titulo se explica a si mismo:
http://get.fedoraproject.org
En otros asuntos, proximamente migrare el software bajo el que corre este sitio (OMFGGG!!!G!G!!!), aun no decido a que, pero... meh. Los mantendre informados

Cambio de... pues de todo

Pues he cambiado de empleo (afortunadamente), no voy a decir mucho de la anterior compañía donde estaba trabajando, solamente que mi salida fue por motivos personales (de salud mas que nada), y la verdad es que muchas ganas de regresar no me quedaron. Durante todo el tiempo que estuve ahi no tuve problemas con los pagos, excepto en la parte de viáticos, ahi siempre hubos fallos. Ah, y ahora también, se suponía que me iban a pagar el correspondiente de lo trabajado del mes de Septiembre el dia último, pero al parecer una vez que sales de ahi ya no eres tan importante. Si, me molesta porque se supone que hice varios trámites y entregué muchos documentos para que a mi salida no hubiera problemas, pero.... bueno.
Conseguí otro trabajo, de nuevo en USA en el área de la bahía de San Francisco, de hecho el trabajo es en San Francisco, estaré trabajando para digg.com, lo cual es bueno porque:
  1. Los problemas y la tecnología son interesantes
  2. La paga es buena
  3. Ya no soy un contractor, sino empleado directo de tiempo completo
  4. Es una compañía pequeña, asi que puedo moverme con mayor facilidad sin tanta burocracia
Hasta ahora llevo 2 semanas ahi, adaptándome al ambiente y conociendo a mis compañeros de trabajo. También estoy poniéndome al corriente con la infraestructura, toda basada en Debian, lo cual es bueno, no me desagrada debian como servidor, al contrario. Aunque mi estación de trabajo estoy tratando de dejarla con Fedora como es mi costumbre.
Y digo "tratando de dejarla" porque la máquina que me dieron es una macbook pro, de las cuales no soy tan fan (de su sistema operativo mas que nada, el hardware es muy decente), y pues tiene sus detalles, me he ayudado mucho de varios sitios en la red, pero principalmente estos tres, la máquina es una macbook pro 5,4 y las instrucciones en su mayoría son correctas.
Primero le puse ubuntu, y siguiendo la liga de ubuntu que puse arriba todo funciona como debiera, excepto que ubuntu se me congeló (como ya antes lo ha hecho en otras de mis máquinas) decidí quitarlo. Quería dejar una distribución .deb para tener un ambiente aproximado a lo que voy a trabajar, pero ubuntu me desanimó en este caso.
Luego le puse fedora 11 (Leónidas) y solo tuve algunos problemas:
  • El driver de nvidia, este fue error de mi parte, en estas máquinas se instala por default el kernel PAE, asi que también hay que instalar el driver de kmod-nvidia-PAE. Luego de eso blacklistear el módulo nouveau (el cual cabe aclarar que funciona out of the box pero sin aceleración 3d) para que no choque con el de nvidia
  • El sonido, pero siguiendo el consejo de la página de ubuntu en la sección Sound lo pude arreglar
  • La backlight, esa lo arreglé con pommed pero dejenme decirles que la instalación es una patada en el cuello
Aparte de esas molestias, y del hecho de que no puedes reiniciar, no importa la distribución (tienes que apagar la máquina y luego encenderla, de otra forma se "cuelga") fedora trabajó sin problemas por horas en esa máquina. Me faltaría probar con debian, presiento que va a ser más estable que ubuntu, pero aun no me decido si le sigo o ya la dejo con fedora por la paz.
En fin. Pasando al plano personal, corrí con mala suerte a mi llegada a San Francisco, ya que perdí mi cartera cuando llegué del aeropuerto. Debió caerse cuando me bajé del taxi porque me saqué la cartera para pagarle al chofer, pero ya después no la encontré. Eso me metió en muchos problemas porque no podia disponer de dinero por ATM, y no podia hacerlo en ventanilla porque no tenia una identificación... afortunadamente ahorita ya casi esta todo solucionado, aun faltan algunos detalles pero en su mayoría todo esta ya casi en orden.
También me puse a buscar un departamento, tenía de 2 sopas: buscar en San Francisco y pagar un poquito más de renta, o buscar fuera de San Francisco y pagar un poquito menos, pero aumentar mi tiempo de viaje cada dia. Luego de un par de semanas viviendo en San Francisco me convencí que lo mio no era vivir en una ciudad, así que próximamente (hoy y mañana) me estaré mudando a Burlingame, que está convenientemente localizada a escasos 30 minutos de donde está mi trabajo, casi lo mismo que hago en el camión face-smile.png
Burlingame es un pueblo muy chido, con todo lo que necesitas y muy tranquilo, asi como para mi que no me gusta el desmadre ni nada de eso, jeje.
En fin, ya me cansé de escribir, espero ya actualizar este chunche un poco más seguido.

Fedora, NetworkManager, hostname, DHCP

So after my last post I went on and started testing different configs to pinpoint where exactly the problem was. I didn't want to do that because I'm a lazy guy, but incredibly enough, google gave only vague results concerning my predicament.

The Problem

... or more like "annoyance" in this case. The facts:
  • My main router is a wireless
  • All the machines in my house connect wirelessly, all of them are linux machines
  • I used to have an ubuntu machine, now all of them are fedora
  • All of them can connect and use the internet just fine
  • Ubuntu machines (I only tried with ubuntu, I cannot assert this happens with other distros) identify themselves with their hostnames in the router list
  • Fedora machines (and I suspect any RH-based distro, again, this is just a guess) do not identify with their hostnames, the IP Address is the only record that appears in the router's client list
  • All of them are stock, just-installed machines using NetworkManager
  • My wireless network does not use any kind of key. This shouldn't have any impact whatsoever, but I wanted to clarify
  • If I connect to the router using an ethernet cable, both ubuntu and fedora work properly

The Testing Process

As I said, both distros have the stock install. I accomplished this by using ubuntu (Jaunty) and fedora (Leonidas) live CDs. No additional packages were installed, just the stock NetworkManager stack. After each test I disabled the networking (right-click on NM's applet, uncheck "Enable Networking"), deleted the lease file from /var/lib/dhclient and powered down the router. After making the changes (and waiting something like 5 minutes) I'd power up the router and re-enable NM.

The Root Cause

There were several comments in my last post explaining several theories, and I myself had a hunch where the issue could be present. Most of them pointed me to the dhclient.conf file, but that was half the issue:
  • Yes, it has to do with the DHCP request being sent to the DHCP server
  • The magic parameter here is "send host-name"
  • The tool system-config-network-gui does half the job
I had already tried adding the hostname in the DHCP part in the system-config-network-gui tool (Devices tab -> Your wireless card -> DHCP Settings -> Hostname (optional)) to no avail. I tried this with the eth0 and wlan0 cards, it worked OK for eth0, but not for wlan0.
The problem here is that fedora works with sysconfig parameters, that is, every tool fedora uses for its own management ends up creating/updating config files inside /etc/sysconfig. The conf files for the network cards are in /etc/sysconfig/network-scripts/ifcfg-YOURNIC, so, if you have eth0 and eth1 you should have ifcfg-eth0 and ifcfg-eth1, ifcfg-wlan0 for your first wireless card. If you check ifcfg-wlan0 after making the changes through system-config-network-gui you'll see a line like
DHCP_HOSTNAME=prettyhostname
Again, check both the eth and wlan ifcfg files and you'll see your changes there, so what's causing only the wireless card to bork? Right now all evidence point to NetworkManager. NetworkManager does a damn fine job at managing your network connections, but it does it differently given the distro where it is running. So it reads the sysconfig files in fedora, and reads the /etc/default/interfaces stuff in debian-based distros. Besides that, it reads the common dhclient config. In ubuntu, we do have a file /etc/dhcp3/dhclient.conf which has a line
send host-name "";
I think gets replaced somewhere along the way with the hostname taken from hostname or /etc/hosts. Fedora does not have a default /etc/dhclient.conf and, actually, it doesn't work as straightforward as you'd like.
I believe (and please, someone correct me if I'm wrong, I'm almost asleep now) NetworkManager creates a dhclient.conf file on the fly by reading the sysconfig values in fedora. After that it reads the common dhclient stuff. However, it is somehow ignoring the DHCP_HOSTNAME value, so it doesn't get translated to the "send host-name" directive in dhclient.conf lingo.

The Workaround

The simplest way would be to add a file /etc/dhclient.conf with the directive and be done with it, however, fedora somehow ignores a "common" dhclient.conf file and instead uses a "per nic" conf file. So you'll have to create a file /etc/dhclient-wlan0.conf (or ra0 or ath0 or whatever your nic is called) with the line
send host-name "prettyhostname";
Don't forget the semi-colon at the end, and of course replace prettyhostname with your actual hostname. Fedora does not work using a placeholder like ubuntu does (yes, I tried, doing so will make it appear as blank in the router's client list). Additionally, you can add any parameter you think should be superseded in this file (dns servers and whatnot)

The Closing Argument

So I spent some time understanding (or more like, trying to understand) NetworkManager's innards, I hope I got it OK. I also went ahead and posted a bug to NM's bugzilla, so hopefully this will get fixed later, the bug is here http://bugzilla.gnome.org/show_bug.cgi?id=594591
So that's it, I got to face my little pet peeve with NM, and with that, I'm off to sleep.

Whatever happened to the hostname?

Dear lazy web:
I have two machines working right now, one with fedora, the other with ubuntu live cd. Both machines connect wirelessly to my main router, but only the ubuntu machine displays its hostname in the router client table (in this case "ubuntu"), while the fedora machine is identified by the IP address. This is annoying because I can "ping ubuntu" and it would answer back, but I cannot "ping fedora".
If I connect the machines via ethernet, they both behave the same and I can see the hostname properly set in the router. Both machines answer OK to host lookups as well.
What's the deal? I'm guessing it has something to do with the way fedora handles the ifcfg scripts, but so far I've encountered no way for fedora to set the hostname in the router as ubuntu does.
Ideas?
UPDATE:
It must be my medication still wearing off (or so I hope that's the reason why I missed the whole point here). My main concern, or rather, my question is: What's the difference between ubuntu and fedora's implementation of NetworkManager? I am using it for both machines, what params ubuntu is reading (and from where) that fedora is not?
Anterior página 1 2 3 4 ... 43 Siguiente página
214 entradas