| View previous topic :: View next topic |
| Author |
Message |
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
 Posted: Sun Feb 04, 2007 7:25 pm Post subject: |
 |
|
iproute2 is the way EVERYTHING should be, route is a piece of shit.... ip all the way!!!
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
 |
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun Feb 04, 2007 7:29 pm Post subject: |
|
|
yipiyeah  but... few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual 
_________________
The End of the Internet! |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 7:30 pm Post subject: |
|
|
| truc wrote: | | yipiyeah but... few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
yeah thats why einit will be the true init ng 
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 7:31 pm Post subject: |
|
|
| truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff...
lucky they're just different interfaces to the same kernel controls
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 7:32 pm Post subject: |
|
|
| rmh3093 wrote: | | truc wrote: | | yipiyeah but... few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
yeah thats why einit will be the true init ng |
lol, ++
go community! 
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 7:34 pm Post subject: |
|
|
| mdeininger wrote: | | truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff...
lucky they're just different interfaces to the same kernel controls |
should I add 'RDEPEND="sys-apps/iproute2"' to the einit-9999 ebuild?????????
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 7:41 pm Post subject: |
|
|
| rmh3093 wrote: | | mdeininger wrote: | | truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff...
lucky they're just different interfaces to the same kernel controls |
should I add 'RDEPEND="sys-apps/iproute2"' to the einit-9999 ebuild????????? |
but then what are the poor bsd users to do?
bu~t
i guess we could just add an <if file-exists="/sbin/ip"> around the templates so that the right one is used?
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun Feb 04, 2007 7:51 pm Post subject: |
|
|
| mdeininger wrote: | | truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff... |
FWIW, iproute2 is the default for LFS (I mean, it is in the manual, of course you're free to choose )
_________________
The End of the Internet! |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 7:54 pm Post subject: |
|
|
| mdeininger wrote: | | rmh3093 wrote: | | mdeininger wrote: | | truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff...
lucky they're just different interfaces to the same kernel controls |
should I add 'RDEPEND="sys-apps/iproute2"' to the einit-9999 ebuild????????? |
but then what are the poor bsd users to do?
bu~t
i guess we could just add an <if file-exists="/sbin/ip"> around the templates so that the right one is used? |
no they should have a seperate einit.xml file.... we could always store the network sections in broken out files then on build do a network-linux >> einit.xml or network-bsd >> einit.xml
or we could start breaking things out and using includes and have just have different systems include different config files
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 7:55 pm Post subject: |
|
|
| truc wrote: | | mdeininger wrote: | | truc wrote: | | yes, few people are aware of that, IIRC, ifconfig&route are even used in the gentoo manual |
well, i'd prefer iproute2 myself, but afaik ifconfig&route are the default on most systems... + i haven't seen iproute2 for other systems, like *bsds and stuff... |
FWIW, iproute2 is the default for LFS (I mean, it is in the manual, of course you're free to choose ) |
yeah, lfs is still linux tho
i don't see darwin have iproute2... nor do i think freebsd and the others :/
i think the <if /> would be the best choice
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 7:56 pm Post subject: |
|
|
| rmh3093 wrote: | no they should have a seperate einit.xml file.... we could always store the network sections in broken out files then on build do a network-linux >> einit.xml or network-bsd >> einit.xml
or we could start breaking things out and using includes and have just have different systems include different config files |
hmm, true again, was gonna add an <if kernel="" /> and <if arch="" /> or something like that anyway
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 8:02 pm Post subject: |
|
|
| mdeininger wrote: | | rmh3093 wrote: | no they should have a seperate einit.xml file.... we could always store the network sections in broken out files then on build do a network-linux >> einit.xml or network-bsd >> einit.xml
or we could start breaking things out and using includes and have just have different systems include different config files |
hmm, true again, was gonna add an <if kernel="" /> and <if arch="" /> or something like that anyway |
well system specific config files should not contain code to OS/system detection code... that should be handled by the config/build/install process
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 8:14 pm Post subject: |
|
|
| rmh3093 wrote: | | well system specific config files should not contain code to OS/system detection code... that should be handled by the config/build/install process |
true true, but i was gonna add code to allow einit to modify/rewrite its configuration on the fly, so, in the long run the file would only be parsed like that on the first run anyway... mismatched <if />s are simply ignored by einit, and whenever it would rewrite its files there wouldn't be any traces of the system detection "code" left?
(the rewrite code should also allow on-line mode modification and updates using einit-control...)
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 8:19 pm Post subject: |
|
|
| mdeininger wrote: | | rmh3093 wrote: | | well system specific config files should not contain code to OS/system detection code... that should be handled by the config/build/install process |
true true, but i was gonna add code to allow einit to modify/rewrite its configuration on the fly, so, in the long run the file would only be parsed like that on the first run anyway... mismatched <if />s are simply ignored by einit, and whenever it would rewrite its files there wouldn't be any traces of the system detection "code" left?
(the rewrite code should also allow on-line mode modification and updates using einit-control...) |
but its what the user has to see and sift through
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 8:59 pm Post subject: |
|
|
| rmh3093 wrote: | | mdeininger wrote: | | rmh3093 wrote: | | well system specific config files should not contain code to OS/system detection code... that should be handled by the config/build/install process |
true true, but i was gonna add code to allow einit to modify/rewrite its configuration on the fly, so, in the long run the file would only be parsed like that on the first run anyway... mismatched <if />s are simply ignored by einit, and whenever it would rewrite its files there wouldn't be any traces of the system detection "code" left?
(the rewrite code should also allow on-line mode modification and updates using einit-control...) |
but its what the user has to see and sift through |
hmm, even if einit.xml is generated by einit on the first run (maybe an einit --wtf called by the ebuild) and the "original" einit.xml is stored outside of /etc/einit.xml?
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 9:00 pm Post subject: |
|
|
| mdeininger wrote: | | rmh3093 wrote: | | mdeininger wrote: | | rmh3093 wrote: | | well system specific config files should not contain code to OS/system detection code... that should be handled by the config/build/install process |
true true, but i was gonna add code to allow einit to modify/rewrite its configuration on the fly, so, in the long run the file would only be parsed like that on the first run anyway... mismatched <if />s are simply ignored by einit, and whenever it would rewrite its files there wouldn't be any traces of the system detection "code" left?
(the rewrite code should also allow on-line mode modification and updates using einit-control...) |
but its what the user has to see and sift through |
hmm, even if einit.xml is generated by einit on the first run (maybe an einit --wtf called by the ebuild) and the "original" einit.xml is stored outside of /etc/einit.xml? |
i think you are making that more complicated than it has to be
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 9:08 pm Post subject: |
|
|
| rmh3093 wrote: | | i think you are making that more complicated than it has to be |
hmm, i dunno, i'd just've checked for the system type once when generating the default configuration and then used that to include the right file, then have the a clean default file written by einit...
i mean, who's better to know what its going to do than the program itself? =)
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Sun Feb 04, 2007 9:13 pm Post subject: |
|
|
| mdeininger wrote: | | rmh3093 wrote: | | i think you are making that more complicated than it has to be |
hmm, i dunno, i'd just've checked for the system type once when generating the default configuration and then used that to include the right file, then have the a clean default file written by einit...
i mean, who's better to know what its going to do than the program itself? =) |
yes einit knows the system type, but so does the system during the build process; why would I was bsd crap on my linux box?
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
mdeininger
Veteran
Joined: 15 Jun 2005
Posts: 1740
Location: Emerald Isles, observing Dublin's docklands
|
| Posted: Sun Feb 04, 2007 9:18 pm Post subject: |
|
|
| rmh3093 wrote: | | mdeininger wrote: | | rmh3093 wrote: | | i think you are making that more complicated than it has to be |
hmm, i dunno, i'd just've checked for the system type once when generating the default configuration and then used that to include the right file, then have the a clean default file written by einit...
i mean, who's better to know what its going to do than the program itself? =) |
yes einit knows the system type, but so does the system during the build process; why would I was bsd crap on my linux box? |
hmm, k yeah, we're telling it the system type during configure... same with the arch... and /etc is by definition host-specific...
got me there
i still think allowing einit to rewrite its configuration file could be a good idea in principle, though (although not for that, granted )... we could make a simple rc-update equivalent that way?
_________________
"Confident, lazy, cocky, dead." -- Felix Jongleur, Otherland
( Twitter | Blog | GitHub ) |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Mon Feb 05, 2007 6:28 am Post subject: |
|
|
here is a more adaptable way to template-ize the network scripts, this is a rough draft, maybe someone can make this even simpler... i wanted a common way for modules to call pump or dhclient or dhcpcd, or even static config
| Code: | <interfaces>
<eth1 ip="dhclient" />
<eth1-wpa_supplicant driver="wext" config="/etc/wpa_supplicant/wpa_supplicant.conf" />
</interfaces>
<shell-template id="template-shell-net-wpa_supplicant"
name="Network (${interface}, wpa_supplicant)"
provides="net-${interface}"
requires="modules"
prepare="sleep 3"
enable="pexec-options no-pipe; wpa_supplicant -D ${configuration_network_interfaces_${interface}_wpa_supplicant_driver} -i ${interface} -c ${configuration_network_interfaces_${interface}_wpa_supplicant_config} -w -B;
wpa_cli -i ${interface} -B; einit-control rc ${configuration_network_interfaces_${interface}_ip}-${interface} enable&"
disable="/bin/true"
variables="configuration-network-interfaces-${interface}/.*:configuration-network-interfaces-${interface}-wpa_supplicant/.*" />
<shell-template id="template-shell-net-pump"
name="Network (${interface}, pump)"
provides="pump-${interface}"
requires="net-${interface}"
enable="pump -i ${interface}"
disable="pump -r ${interface}" />
<shell id="shell-net-pump-eth1"
based-on-template="template-shell-net-pump"
interface="eth1" />
<shell-template id="template-shell-net-dhcpcd"
name="Using 'dhcpcd' to manage ip addresses for interface ${interface}"
provides="dhcpcd-${interface}"
requires="net-${interface}"
enable="dhcpcd ${interface}"
disable="dhcpcd -k ${interface}" />
<shell id="shell-net-dhcpcd-eth1"
based-on-template="template-shell-net-dhcpcd"
interface="eth1" />
<shell-template id="template-shell-net-dhclient"
name="Using 'dhclient' to manage ip addresses for interface ${interface}"
provides="dhclient-${interface}"
requires="net-${interface}"
enable="dhclient ${interface}"
disable="/bin/true" />
<shell id="shell-net-dhclient-eth1"
based-on-template="template-shell-net-dhclient"
interface="eth1" /> |
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
UberPinguin
Guru
Joined: 20 Nov 2005
Posts: 510
Location: 2416.94 Miles From Home
|
| Posted: Tue Feb 06, 2007 5:30 pm Post subject: |
|
|
| Is there a way to set the font used on the tty consoles? All of my ncurses apps (like alsamixer or make menuconfig) are completely fugly. |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Tue Feb 06, 2007 5:36 pm Post subject: |
|
|
| UberPinguin wrote: | | Is there a way to set the font used on the tty consoles? All of my ncurses apps (like alsamixer or make menuconfig) are completely fugly. |
i thought i made a module for that a long time ago
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
rmh3093
Advocate
Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY
|
| Posted: Tue Feb 06, 2007 5:57 pm Post subject: |
|
|
| UberPinguin wrote: | | Is there a way to set the font used on the tty consoles? All of my ncurses apps (like alsamixer or make menuconfig) are completely fugly. |
i found the module and committed it to the svn repo... reemermge einit, look in einit.xml for the main module and in local.xml for a place to set the font
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger. |
|
| Back to top |
|
|
UberPinguin
Guru
Joined: 20 Nov 2005
Posts: 510
Location: 2416.94 Miles From Home
|
| Posted: Tue Feb 06, 2007 7:35 pm Post subject: |
|
|
| rmh3093 wrote: | | UberPinguin wrote: | | Is there a way to set the font used on the tty consoles? All of my ncurses apps (like alsamixer or make menuconfig) are completely fugly. |
i found the module and committed it to the svn repo... reemermge einit, look in einit.xml for the main module and in local.xml for a place to set the font |
sweeeeet. Thanks! (still compiling...will let you know the results in a bit, if you care ) |
|
| Back to top |
|
|
UberPinguin
Guru
Joined: 20 Nov 2005
Posts: 510
Location: 2416.94 Miles From Home
|
| Posted: Tue Feb 06, 2007 8:39 pm Post subject: |
|
|
| Ok, the font wasn´t the problem. Apperently, ncurses was trying to outfox my UTF8-enabled console with some shmancy auto-detection/control-sequence-modifying behavior (see the ncurses(3X) manpage for details, or go to http://dickey.his.com/ncurses/ncurses.faq.html). The short version is that exporting NCURSES_NO_UTF8_ACS=0 makes everything happy again. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
