Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
On Jan 30, 2013 1:12 PM, "Pierre Schmitz" pierre@archlinux.de wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
-- Pierre Schmitz, https://pierre-schmitz.com
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
On Jan 30, 2013 7:14 PM, "Dave Reisner" d@falconindy.com wrote:
On Jan 30, 2013 1:12 PM, "Pierre Schmitz" pierre@archlinux.de wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
Yeah, the template makes no sense unless you know the name of the interface. The regular service should just work.
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
Cheers,
Tom
On 01/30/2013 03:35 PM, Tom Gundersen wrote:
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
I was thinking about this when systemd replaced initscripts.
+1 for me.
Cheers,
Tom
On Wed, Jan 30, 2013 at 03:57:08PM -0300, Gerardo Exequiel Pozzi wrote:
On 01/30/2013 03:35 PM, Tom Gundersen wrote:
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
I was thinking about this when systemd replaced initscripts.
+1 for me.
Cheers,
Tom
Can we talk about pruning out some of the weight from the ISO before we add another 20MB via NM and dependencies? We'd need to add, roughly:
dbus-glib glib-networking gsettings-desktop-schemas libsoup nspr nss polkit sqlite networkmanager
Not really a fan of network manager, but I don't really deal with the headaches that come with wifi so often. Is nmcli more than just a config file parser these days?
d
Am 30.01.2013 20:11, schrieb Dave Reisner:
On Wed, Jan 30, 2013 at 03:57:08PM -0300, Gerardo Exequiel Pozzi wrote:
On 01/30/2013 03:35 PM, Tom Gundersen wrote:
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
I was thinking about this when systemd replaced initscripts.
+1 for me.
Can we talk about pruning out some of the weight from the ISO before we add another 20MB via NM and dependencies? We'd need to add, roughly:
dbus-glib glib-networking gsettings-desktop-schemas libsoup nspr nss polkit sqlite networkmanager
Not really a fan of network manager, but I don't really deal with the headaches that come with wifi so often. Is nmcli more than just a config file parser these days?
NetworkManager would work quite well for us. The deps look a little insane though. I don't know why it would need libsoup and Gnome stuff.
I would say we keep things as-is for at least the February ISO image.
On Wed, Jan 30, 2013 at 08:41:31PM +0100, Pierre Schmitz wrote:
Am 30.01.2013 20:11, schrieb Dave Reisner:
On Wed, Jan 30, 2013 at 03:57:08PM -0300, Gerardo Exequiel Pozzi wrote:
On 01/30/2013 03:35 PM, Tom Gundersen wrote:
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
I was thinking about this when systemd replaced initscripts.
+1 for me.
Can we talk about pruning out some of the weight from the ISO before we add another 20MB via NM and dependencies? We'd need to add, roughly:
dbus-glib glib-networking gsettings-desktop-schemas libsoup nspr nss polkit sqlite networkmanager
Not really a fan of network manager, but I don't really deal with the headaches that come with wifi so often. Is nmcli more than just a config file parser these days?
NetworkManager would work quite well for us. The deps look a little insane though. I don't know why it would need libsoup and Gnome stuff.
If adding NM is the deemed The Right Thing To Do™ then fine, but I'd like to make sure that it's actually valuable. Last I looked, using nmcli meant handwriting config files which had no documented syntax.
I would say we keep things as-is for at least the February ISO image.
Very much agreed.
d
On Wed, Jan 30, 2013 at 1:51 PM, Dave Reisner d@falconindy.com wrote:
On Wed, Jan 30, 2013 at 08:41:31PM +0100, Pierre Schmitz wrote:
Am 30.01.2013 20:11, schrieb Dave Reisner:
On Wed, Jan 30, 2013 at 03:57:08PM -0300, Gerardo Exequiel Pozzi wrote:
On 01/30/2013 03:35 PM, Tom Gundersen wrote:
For the next release I suggest we seriously consider using Network Manager on the instal medium. nmcli seems to cover most relevant use cases now.
I was thinking about this when systemd replaced initscripts.
+1 for me.
Can we talk about pruning out some of the weight from the ISO before we add another 20MB via NM and dependencies? We'd need to add, roughly:
dbus-glib glib-networking gsettings-desktop-schemas libsoup nspr nss polkit sqlite networkmanager
Not really a fan of network manager, but I don't really deal with the headaches that come with wifi so often. Is nmcli more than just a config file parser these days?
NetworkManager would work quite well for us. The deps look a little insane though. I don't know why it would need libsoup and Gnome stuff.
If adding NM is the deemed The Right Thing To Do™ then fine, but I'd like to make sure that it's actually valuable. Last I looked, using nmcli meant handwriting config files which had no documented syntax.
I would say we keep things as-is for at least the February ISO image.
Very much agreed.
If/when we do a cleanup of the ISO, we should really prune things like nmap. We're not a pen-testing LiveCD, and people can always install stuff in the live environment anyways.
-Dan
On Wed, Jan 30, 2013 at 8:51 PM, Dave Reisner d@falconindy.com wrote:
dbus-glib glib-networking gsettings-desktop-schemas libsoup nspr nss polkit sqlite networkmanager
Not really a fan of network manager, but I don't really deal with the headaches that come with wifi so often. Is nmcli more than just a config file parser these days?
NetworkManager would work quite well for us. The deps look a little insane though. I don't know why it would need libsoup and Gnome stuff.
Hm, that's something to look into. Would be nice if it could at least work without polkit if it is not installed (like systemd does).
If adding NM is the deemed The Right Thing To Do™ then fine, but I'd like to make sure that it's actually valuable. Last I looked, using nmcli meant handwriting config files which had no documented syntax.
Nope, they sorted this out now. You can use it to do stuff like list available network, and set up connections (just as in the gui clients).
I would say we keep things as-is for at least the February ISO image.
Very much agreed.
Absolutely. Just planting seeds ;-)
-t
Dave Reisner d@falconindy.com on Wed, 2013/01/30 13:14:
On Jan 30, 2013 1:12 PM, "Pierre Schmitz" pierre@archlinux.de wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
I do use wicd on my live media. Works well for the new network interface names, even wireless devices are detected correctly.
On 01/30/2013 03:14 PM, Dave Reisner wrote:
On Jan 30, 2013 1:12 PM, "Pierre Schmitz" pierre@archlinux.de wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
-- Pierre Schmitz, https://pierre-schmitz.com
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
Yes, dhcpcd on all interfaces.
On 01/30/2013 03:45 PM, Gerardo Exequiel Pozzi wrote:
On 01/30/2013 03:14 PM, Dave Reisner wrote:
On Jan 30, 2013 1:12 PM, "Pierre Schmitz" pierre@archlinux.de wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
-- Pierre Schmitz, https://pierre-schmitz.com
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
Yes, dhcpcd on all interfaces.
epa epa!, looks like something, order/race condition in rename network interface, while testing the ISO, booting multiple times inside KVM, sometimes network device appears as eth0, and other correctly renamed to enp0s3.
I think this should be reported to upstream...
Am 30.01.2013 19:14, schrieb Dave Reisner:
How are we handling network? This is the first release with the renamed network interfaces. I guess we use dhcpcd.service instead of the template?
You are correct.
On 01/30/2013 03:12 PM, Pierre Schmitz wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
* There is only one chenge in archiso but irrelevant to install medium, so there is no need another release.
* EFI boot (gummiboot) finally works (at least on Asus motherboards, this is what I tested one week ago, I guess other broken EFI hardware will also work now)
Am 30.01.2013 19:53, schrieb Gerardo Exequiel Pozzi:
On 01/30/2013 03:12 PM, Pierre Schmitz wrote:
Hi,
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
Greetings,
Pierre
- There is only one chenge in archiso but irrelevant to install medium,
so there is no need another release.
- EFI boot (gummiboot) finally works (at least on Asus motherboards,
this is what I tested one week ago, I guess other broken EFI hardware will also work now)
I can test this on my Asus tomorrow; the last ISO did not work.
Pierre Schmitz pierre@archlinux.de on Wed, 2013/01/30 19:12:
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
This is not about the ISO itself but its download...
Torrent download files can contain more than just one file. How about including gpg signature for the ISO file? Possibly this increases the number of people actually checking the authenticity of downloaded files.
On 31.01.2013 13:02, Christian Hesse wrote:
Pierre Schmitz pierre@archlinux.de on Wed, 2013/01/30 19:12:
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
This is not about the ISO itself but its download...
Torrent download files can contain more than just one file. How about including gpg signature for the ISO file? Possibly this increases the number of people actually checking the authenticity of downloaded files.
Frankly, why? The torrent already guarantees you didn't get bad data.
Sven-Hendrik Haase sh@lutzhaase.com on Thu, 2013/01/31 13:19:
On 31.01.2013 13:02, Christian Hesse wrote:
Pierre Schmitz pierre@archlinux.de on Wed, 2013/01/30 19:12:
I am going to build a new ISO image on Friday. I did a test build today and everything looks fine. It's just updated packages; no changes to ais nor archiso. Let me know if there are any known issues or blockers.
This is not about the ISO itself but its download...
Torrent download files can contain more than just one file. How about including gpg signature for the ISO file? Possibly this increases the number of people actually checking the authenticity of downloaded files.
Frankly, why? The torrent already guarantees you didn't get bad data.
Sure. But the gpg signature is not (only) about integrity but authenticity.
If you get a bad (not broken) torrent file you could download a bad ISO image without noticing anybody is fooling you.
arch-releng@lists.archlinux.org