Wishlist for Gentoo 2005.1

Message

Post by **GurliGebis** » Thu Oct 28, 2004 6:46 pm

The ability to say that when eth0 is started, several other services is started too, and they are stopped when eth0 is stopped.
I have created a bug for this, please comment: http://bugs.gentoo.org/show_bug.cgi?id=68190

Stormy Eyes · Post by **Stormy Eyes** » Thu Oct 28, 2004 6:50 pm

GurliGebis wrote:The ability to say that when eth0 is started, several other services is started too, and they are stopped when eth0 is stopped.
I have created a bug for this, please comment:

I'm pretty sure that that's what ip-up and ip-down scripts are for. They should be somewhere in /etc, but I don't remember where.

rbr28 · Post by **rbr28** » Thu Oct 28, 2004 10:37 pm

I know this would probably be an outrageously difficult thing to accomplish, but how about a progress indicator for emerges. Seems like it would be tough because it would have to take into account use flags, hardware, other things going on, etc, but I think it's possible. Even more difficult than that, how about an estimate of build time before an emerge. Again, it would have to take a lot into account, but even a rough estimate would help greatly. Even if we had a baseline it would be a big help. For example, if we knew the build time for every package, with no use flags, based on a standard PIII 1Ghz machine, or something like that, it would give us a better idea of what to expect on a slower or faster machine, at least some kind of ballpark figure.

nyda · Post by **nyda** » Fri Oct 29, 2004 6:02 am

SoLC wrote:Default to using hardened Gentoo

would go along with massive breakage of binary only drivers and a lot of frustration for the users (who aren't responsible for the lack of OS drivers, in case you want to say "don't use CS shit"

)

thechris · Post by **thechris** » Fri Oct 29, 2004 6:06 am

rbr28 wrote:I know this would probably be an outrageously difficult thing to accomplish, but how about a progress indicator for emerges. Seems like it would be tough because it would have to take into account use flags, hardware, other things going on, etc, but I think it's possible. Even more difficult than that, how about an estimate of build time before an emerge. Again, it would have to take a lot into account, but even a rough estimate would help greatly. Even if we had a baseline it would be a big help. For example, if we knew the build time for every package, with no use flags, based on a standard PIII 1Ghz machine, or something like that, it would give us a better idea of what to expect on a slower or faster machine, at least some kind of ballpark figure.

there is one. not from gentoo, but there is one that i've heard of. i'm working on a personal portage wrapper, but this is definately not one of the features because, well, it would take too long to program this as i have no idea how to do it...

jpalko · Post by **jpalko** » Fri Oct 29, 2004 6:13 am

thechris wrote:
rbr28 wrote:I know this would probably be an outrageously difficult thing to accomplish, but how about a progress indicator for emerges. Seems like it would be tough because it would have to take into account use flags, hardware, other things going on, etc, but I think it's possible. Even more difficult than that, how about an estimate of build time before an emerge. Again, it would have to take a lot into account, but even a rough estimate would help greatly. Even if we had a baseline it would be a big help. For example, if we knew the build time for every package, with no use flags, based on a standard PIII 1Ghz machine, or something like that, it would give us a better idea of what to expect on a slower or faster machine, at least some kind of ballpark figure.
there is one. not from gentoo, but there is one that i've heard of. i'm working on a personal portage wrapper, but this is definately not one of the features because, well, it would take too long to program this as i have no idea how to do it...

Would be interesting to see how well this sort of solution works with distcc clusters.

Chiron · Post by **Chiron** » Fri Oct 29, 2004 6:15 am

wolf31o2 wrote:2005.0 is also the the first release in our new biannual release cycle. Our releases will be changed to a six-month interval to allow the developers more time to implement new features between releases.

Pet peeve time ... every 6 months is semi-annual, biannual every two years.

Imek · Post by **Imek** » Fri Oct 29, 2004 7:39 am

Chiron wrote:Pet peeve time ... every 6 months is semi-annual, biannual every two years.

Actually, biannual can mean either...

tmadhavan · Post by **tmadhavan** » Fri Oct 29, 2004 9:16 am

Indeed it does!

Was sure some newsread or footy pundit or something had made a mistake the other day, but a quick trip to dictionary.com confirms that 'biannual' does indeed have two meanings:

Code: Select all

bi·an·nu·al    ( P )  Pronunciation Key  (b-ny-l)
adj.

   1. Happening twice each year; semiannual.
   2. Occurring every two years; biennial.

Heh.
T.

colo · Post by **colo** » Fri Oct 29, 2004 9:23 am

I'd really like to see some initscript on the livecd, meant for starting a tftp/dhcp-server-combo, and therefore allowing other computers on the network to boot the livecd via PXE (similar to the "Knoppix Terminal Server", but without all the X11-Stuff). That's the only thing not already mentioned I think would be of reaonsable use to some people.

Maybe I'm lucky and it makes it in 2005.x?

Chiron · Post by **Chiron** » Sat Oct 30, 2004 7:25 am

Imek wrote:
Chiron wrote:Pet peeve time ... every 6 months is semi-annual, biannual every two years.
Actually, biannual can mean either...

I loathe words that require additional information in order to know which meaning you intend. Especially those that require you to specify the definition ... why even bother with the words itself then.

Mea culpa. I always think of bi-<period> as two periods, not twice in a period.

playfool · Post by **playfool** » Sat Oct 30, 2004 11:00 am

nyda wrote:
SoLC wrote:Default to using hardened Gentoo
would go along with massive breakage of binary only drivers and a lot of frustration for the users (who aren't responsible for the lack of OS drivers, in case you want to say "don't use CS shit" )

And that is our problem why?

I refuse to continue using a technically infinior solution because some company who's asshat engineers can't code and who's asshat lawyer won't allow anyone to see said code even under NDA so it can be fixed - traditiionally companies like nvidia have followed suit everytime we have changes the parameters and if they one day elect not to, to bad they will loose business - remember Linux is growing and one of our selling points is security, also remember than NX technology will be the standard soon with all new CPU designs supporting this - do you want us to set aside the needs of the many to care for the needs of the few?

Remember that the main reason that Linux now runs natively on the AMD64 arch and Windows doesn't is that we have open drivers.

Now can we please just do the right thing?

pep11 · Post by **pep11** » Sat Oct 30, 2004 7:02 pm

definitly:
another search option for emerge

apt-cache search, is a query on the contents of the packages not on their name. This behaviour is powerfull for you can find a package matching your purpose even if you have no idea of it's name, and often proposes different solutions to your problem.

For example if you search for vector graphics it returns a lot of packages including sodipodi, gimp-svg, inkscape, karbon ... while emerge won' t return any usefull information

chunderbunny · Post by **chunderbunny** » Sat Oct 30, 2004 7:12 pm

pep11 wrote:definitly:
another search option for emerge

apt-cache search, is a query on the contents of the packages not on their name. This behaviour is powerfull for you can find a package matching your purpose even if you have no idea of it's name, and often proposes different solutions to your problem.

For example if you search for vector graphics it returns a lot of packages including sodipodi, gimp-svg, inkscape, karbon ... while emerge won' t return any usefull information

You can search the descriptions of packages using "emerge --searchdesc foo". The only problem is it takes a rediculously long time to process the results. A solution to this is to use esearch, which caches all the relevant information in a databse for fast searching. The downside to this is that you have to rebuild the database periodically in order to get accurate results. I search packages fairly often, so I use esearch and I rebuild the database every week.

codergeek42 · Post by **codergeek42** » Sat Oct 30, 2004 7:31 pm

In fact if you emerge esearch, you can use the 'esync' script, which will `emerge sync`, then update the esearch database, then tell you what's changed since last `emerge sync`. Nifty little thing.

Suicidal · Post by **Suicidal** » Sat Oct 30, 2004 8:53 pm

In general in the next year I would like to see a stable branch that is stable, quit breaking bootstrap and emerge system. If we want the latest package x or y we can do it through /etc/portage. Also 2.4 needs to go.

shash · Post by **shash** » Sun Oct 31, 2004 6:07 am

Stormy Eyes wrote:
GurliGebis wrote:The ability to say that when eth0 is started, several other services is started too, and they are stopped when eth0 is stopped.
I have created a bug for this, please comment:
I'm pretty sure that that's what ip-up and ip-down scripts are for. They should be somewhere in /etc, but I don't remember where.

They do that for ppp (/etc/ppp/ip-up). He wants the same for eth0.

I think it should be trivial to insert what you want into the init.d script, though you'll have to change it every time there's a change in the script...

slonocode · Post by **slonocode** » Sun Oct 31, 2004 6:33 am

miqorz wrote:I'm not trying to beat a dead horse here.

But seriously, How fucking hard is it to type emerge a few times and to type some commands directly off a website?

Get over it and learn some command, You'll fucking need it after the install.

I gurantee it. If you can't install gentoo, chances are you won't have the experience to admin the system.

Wow if its that easy a gui installer should be trivial to create so I guess your argument about developer time is complete BS.

HydroSan · Post by **HydroSan** » Sun Oct 31, 2004 7:28 am

Make the hardened toolchain default.

jklmnop · Post by **jklmnop** » Sun Oct 31, 2004 7:54 am

shash wrote:
Stormy Eyes wrote:
GurliGebis wrote:The ability to say that when eth0 is started, several other services is started too, and they are stopped when eth0 is stopped.
I have created a bug for this, please comment:
I'm pretty sure that that's what ip-up and ip-down scripts are for. They should be somewhere in /etc, but I don't remember where.
They do that for ppp (/etc/ppp/ip-up). He wants the same for eth0.

I think it should be trivial to insert what you want into the init.d script, though you'll have to change it every time there's a change in the script...

i did some digging... you can put functions in the /etc/conf.d/net script.

Code: Select all

# /etc/conf.d/net:
...
preup() {
        case ${1} in
                eth0) echo eth0 going up >> /tmp/duh
                ;;
                *) echo huh >>/tmp/duh
                ;;
        esac
}
postup() {
        case ${1} in
                eth0) echo eth0 gone up >> /tmp/duh
                ;;
                *) echo huh >>/tmp/duh
                ;;
        esac
}

Code: Select all

root # /etc/init.d/net.eth0 start
 * Running preup function
 * Bringing eth0 up (192.168.254.31)...                                   [ ok ]
 *   Setting default gateway (192.168.254.254)...                         [ ok ]
 * Running postup function

root # cat /tmp/duh 
eth0 going up
eth0 gone up

there is also (pre|post)down. you can probably have what you desire with this hook.[/code]

Zeddicus · Post by **Zeddicus** » Sun Oct 31, 2004 10:16 am

For the record, an installer (x86) may actually make it into 2005.0.

http://www.gentoo.org/proj/en/releng/in ... 040912.xml

klieber suggested a public beta before releasing on a LiveCD, and the idea was generally accepted. esammer asked "can we be tested and working for 2005.0?", with samyron answering "i'm pretty confident", and codeman answering "we can do it".

miqorz · Post by **miqorz** » Sun Oct 31, 2004 3:25 pm

That better not be on the main disk or I'll hurt someone.

Deranger · Post by **Deranger** » Sun Oct 31, 2004 3:29 pm

I fucking can't understand why there should be GUI installer in mainline Gentoo! CLI-installation is logical as hell and I can't understand how someone cannot manage to install Gentoo with it (...and with step-by-step handbook).

I'm happy as long as minimal LiveCD is GUI installer-free.

miqorz · Post by **miqorz** » Sun Oct 31, 2004 4:12 pm

Guy: Gentoo has a GUI installer? All right!!

Guy: (five hours later) So... I'm IN the system? What do I do now!?!?!?!?!?!?!?

Guy: *boots into windows and opens IE to post on the Gentoo Forums*
DOODZ IM IN TEH GENTOO BUTZ I GOTS NO APPS, LYKE WHEREZ MY KDE ANDZ MOZILLER HAW HAW.

Deranger · Post by **Deranger** » Sun Oct 31, 2004 4:20 pm

miqorz wrote:Guy: Gentoo has a GUI installer? All right!!

Guy: (five hours later) So... I'm IN the system? What do I do now!?!?!?!?!?!?!?

Guy: *boots into windows and opens IE to post on the Gentoo Forums*
DOODZ IM IN TEH GENTOO BUTZ I GOTS NO APPS, LYKE WHEREZ MY KDE ANDZ MOZILLER HAW HAW.

Indeed

Wishlist for Gentoo 2005.1

progress indicator for emerge & build estimate

Re: progress indicator for emerge & build estimate

Re: progress indicator for emerge & build estimate