Custom Query (1145 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (232 - 234 of 1145)

Ticket Resolution Summary Owner Reporter
#154 fixed We should implement a zenity dialog for people who are running tracker jdreed

Reported by jdreed, 15 years ago.

Description

As per ATN-30, we should implement a zenity dialog (like we do for people with mode 777 homedirs) that checks for EnableIndexing?=true in ~/.config/tracker/tracker.cfg. It should say something like "You currently have the Tracker indexer enabled. This is known to break AFS. You can disable it by doing $foo".

$foo can either be something like "athrun consult fix-tracker", or we could decide that the number is small enough we should point them at a stock answer on how to edit the file instead.

I note we currently have /etc/X11/Xsession.d/97debathena-homedir-mode. Rather than having a separate script, would it be better to lump these all together in something like debathena-warn-users or something?

#160 worksforme Live CD needs improvement for general consumption xavid jdreed

Reported by jdreed, 15 years ago.

Description

I finally got around to playing with the Live CD. It's a great start, but it needs some improvement before it's ready for general consumption:

  • Networking: Logins fail miserably if the machine isn't registered. I realize this is a function of our environment, but since we're aiming this CD at new Debathena users, we should probably figure out a way to do something clever if the machine isn't registered for DHCP (a zenity dialog would be fine, prompting the user for a static IP would be awesome). What would be clever would be if the livecd did some sort of check before starting the greeter. In a dhreg situation, all DNS requests return an A record for 10.72.0.47, which is nic.mit.edu's other interface. So perhaps the livecd could try to fetch, say, http://debathena.mit.edu/livecd.txt, and parse the output. If it it matches what is expected, then they have network. If it's a 404 error, or some other page, it means they're actually talking to nic.mit.edu. And if it can't connect, then there's no networking at all.
  • Partitioner in GUI installer: The partitioner does not understand LVM. As most Linux distributions have been defaulting to LVM for a while, this means a user cannot, for example, replace an RHEL installation without nuking their entire volgroup. I realize this is an upstream problem, but this is kind of a dealbreaker, since the tty mode partitioner (available via a PXE install) understands LVM just fine. The user should at least be informed of this before trying to install. Perhaps the "install" utility on the desktop can be wrapped with something which warns the user what will and won't work.
  • Installation choices: Ideally, we'd give users the option of installing everything they can install from the installer script (except -cluster). However, in the short term, -standard and -workstation are fine. When we rename stuff, we should figure out if the latter will still mean -workstation or if we should change it to -graphical-login.
#168 fixed busyd doesn't work rbasch jdreed

Reported by jdreed, 15 years ago.

Description

Debathena machines don't respond to udp/49154 packets correctly.

Querying an Athena 9 machine: $ nc -u w20-575-37 49154 <CR> 1w20-575-37.mit.edui686 C $

Querying an Athena 10 machine: $ nc -u w20-575-37 49154 <CR> (no output) C $

Note: See TracQuery for help on using queries.