Been down with a nasty flu for about a month. It lines your lungs with a thick phlegm and saps your energy. Rough stuff. Getting enough sleep to get better was the thing to do.
Congratulations to Flameeyes on his elevation to Gentoo QA lead. An excellent 'technical' choice by Gentoo and due recognition for what he has accomplished in the community. I am very pleased in having contributed in some small way to his fine book Autotools Mythbuster which he has recently expanded and edited considering some more minor changes I proposed. What is discussed is quite concise and a valuable resource worthy of a hard copy but available online. Please consider Flattr'ing it if you find it useful. I hope for him patience enough to work with us all ;-) (users and devs alike)
I decided to just build in support for the 'random' box's new hardware and just move the drive. Mostly done but the drive swap isn't. Several questions arise from this. I may need to run an 'emerge -e world' before/after the swap which will rebuild all packages. The compiler flag was set 'native' and the old AMD 64 3200+ vs a dual core Pentium 4 It is speculated that the chipset of the ATI 650 tv tuner card may be supported by the Xcieve driver in kernel. If it is I will know soon but cannot say until I move to the new platform.
The first computer I ever bought off the shelf arrived. I'll perhaps review it soon.
Connman is a blur of work and I'm sure it is wonderful for those it works for ...but not for any setup I've built yet. I'm still using wpa_cli at startup (tuxmobl and random) with my configured wlan fine. I've a lot to do if I had the time. ;-( and 'iw list scan' works fine with both SMC 2802 (p54pci) and WNA1100(ath9k_ht) For now it's cli tools only for me. The p54pci support requires a custom kernel build something non-trivial on some linux distributions (Ubuntu I know of Debian no idea Red Hat don't remember it being an issue ) But all my linux is wireless.
Really ruminating of late about Gentoo but I don't make a living from it. My change process seems to be more along the lines of dripping water, than a flood; since for me it's just utilizing older hardware and I've only so many projects for the boxes. It's cheaper to just turn them off though they do run pretty much 24/7 they need work jobs.
Showing posts with label flameeyes. Show all posts
Showing posts with label flameeyes. Show all posts
Thursday, March 3, 2011
Friday, December 3, 2010
Making a better distribution of Gentoo
G'day mate! Today we advocate not only mental but physical stimulation and your homework assignment is to master the boomerang.
My Gentoo installation on the Dell Inspiron 8000 (nee tuxmobl) shows some progress now since I have managed to successfully start X and obtain an LXDE desktop. Network access is currently through the PCMCIA card and I have yet to try the laptops built in NIC jack that would not work under M$. I can ssh in and set it building while working from 'random' host; which I did yesterday. Once set to a task I checked on some of my open bugs and posted a new blog. Flameeyes has hardware issues and reported he is not able to do tinderbox runs at least where it concerns the packages I use I can try to pick up some small portion of the work.Since updating to gcc-4.5.1 I am currently running 'emerge -e world' on the the 'random' host At 12:00 pm EST there are 290 of 856 packages done.
As the laptop installation proceeds I am forced to make choices concerning hal and udev. Since hal is going away but the documentation still outlines hal and until Gentoo migrates to openrc and baselayout2 hal is still used on Gentoo stable AFAIK With laptops there is the whole battery runlevel and issues of power management as I progress through the problems I intend to post updates here. Further there was discussion I recall on using i2c versus lm_sensors.
The 'random' host has already been migrated to openrc and baselayout2 and seem to be fine running udev without hal. The only thing that at last check actually still required hal on that system was the gnome-gvfs IIRC I chose gnome for a desktop on it since it seemed the easiest way to manage a working install without hal.
I must also keep in mind some kind of solution where integrating the other boxes into the network better yields access to what the linux and windows boxes here can do. Like shared printing and a shared rsync solution between hosts random and tuxmobl Then there is a little router project I have in mind as well.
Good luck with your own tasks. And enjoy a sunset near you with a friend. I'm off the weekend and hope to make some progress then so keep checking back.
My Gentoo installation on the Dell Inspiron 8000 (nee tuxmobl) shows some progress now since I have managed to successfully start X and obtain an LXDE desktop. Network access is currently through the PCMCIA card and I have yet to try the laptops built in NIC jack that would not work under M$. I can ssh in and set it building while working from 'random' host; which I did yesterday. Once set to a task I checked on some of my open bugs and posted a new blog. Flameeyes has hardware issues and reported he is not able to do tinderbox runs at least where it concerns the packages I use I can try to pick up some small portion of the work.Since updating to gcc-4.5.1 I am currently running 'emerge -e world' on the the 'random' host At 12:00 pm EST there are 290 of 856 packages done.
As the laptop installation proceeds I am forced to make choices concerning hal and udev. Since hal is going away but the documentation still outlines hal and until Gentoo migrates to openrc and baselayout2 hal is still used on Gentoo stable AFAIK With laptops there is the whole battery runlevel and issues of power management as I progress through the problems I intend to post updates here. Further there was discussion I recall on using i2c versus lm_sensors.
The 'random' host has already been migrated to openrc and baselayout2 and seem to be fine running udev without hal. The only thing that at last check actually still required hal on that system was the gnome-gvfs IIRC I chose gnome for a desktop on it since it seemed the easiest way to manage a working install without hal.
I must also keep in mind some kind of solution where integrating the other boxes into the network better yields access to what the linux and windows boxes here can do. Like shared printing and a shared rsync solution between hosts random and tuxmobl Then there is a little router project I have in mind as well.
Good luck with your own tasks. And enjoy a sunset near you with a friend. I'm off the weekend and hope to make some progress then so keep checking back.
Subscribe to:
Posts (Atom)