Custom Query (1145 matches)


Show under each result:

Results (193 - 195 of 1145)

Ticket Resolution Summary Owner Reporter
#211 fixed No documentation on the PXE installer jdreed broder

Reported by broder, 15 years ago.


The "Installing Debathena" page should talk about the PXE installer for people on campus. This should include things like "no really, you don't want debathena-cluster". Maybe some other stuff.

#212 fixed wireless LAN doesn't start at graphical login screen geofft geofft

Reported by geofft, 15 years ago.


Ubuntu doesn't start the wireless network until a user has logged in, ostensibly so that it can pick up the list of preferred networks, and if they need encryption, grab the password out of the login keyring.

This interacts poorly with debathena-login-graphical. In particular, you need the wireless LAN to be working before a user logs in, so you can authenticate their network login. If you have no local users, the machine is basically useless. This mostly affects laptops, although desktops with wireless-only connections are common in places like dorm rooms that don't have many Ethernet drops.

When I heard about this problem last fall, I wrote , a simple Python script to ask NetworkManager over D-Bus to enumerate all wireless networks on all interfaces and connect to the first one named "MIT". I haven't tested it with Ubuntu 8.10 or 9.04 -- the interfaces may well have changed. It also needs to be packaged better; two options are to run this out of an initscript at boot time, and to make this a "custom command" in the GDM greeter that you can choose from the login screen.

It would be nice if you could also specify what network to connect to. To be useful, though, this functionality probably depends on running GUI applications at the login screen, which we haven't yet figured out how to do. Maybe we can use the same setup as the Firefox kiosk mode will, and create a special local user that can only choose a wireless network to log in to (via the built-in GUI applet to do this).

Ticket #208 is also relevant for this configuration, since the wireless connection is prone to disconnecting.

#213 fixed Craft a policy on the implications of each metapackage and what software goes where jdreed jdreed

Reported by jdreed, 15 years ago.


We started to do this over e-mail (Subject: the impact of each metapackage), but we should, by the summer, come up with a policy regarding how software gets added to -extra-software, -third-party, or one of the major metapackages (clients, standard, login, etc).

Note: See TracQuery for help on using queries.