The artist did a good job with this logo and font, I just don't think it's appropriate for the product it's representing. How does this represent what FreeBSD *is*? As other people have already noted, this makes "FreeBSD" look like some new fad, a trendy plastic thing that may never mature. A solid, reliable product shouldn't be represented this way, this logo does it no justice. Though I like the font, again, I don't think it screams FreeBSD. Wouldn't a boxy, bold font be better? Why does there even need to be an icon? Couldn't something artistic (simple but arresting) have been done just with the text?
I haven't really used KDE, but you can do what you want with either KDE or Gnome. It's really a matter of your own preference, and what you think users will be more familiar with. Some Windows users like KDE better. But Gnome can be configured to resemble windows as well, so it's really up to you.
It sounds like you want a single guest account per machine, which is why you don't want settings changed. Because if you didn't care about managing multiple accounts, then you wouldn't care about changed settings. In which case, you probably wouldn't want users worrying about logging in as "guest", since that's just another "instruction" page that you have to print out and post to every machine.
I know that GDM, the "Gnome display manager" which makes graphical login to gnome easy, has an option to allow for automatic login. You could set up GDM to automatically log in the guest account. If you were an administrator, you could just switch the tty, kill gdm and startx as yourself if you ever needed to get into X under the administrator account.
Next, you said that you didn't want settings modified by this guest account. Two ideas:
Idea #1: Create this new account and configure settings the way you want them. Then log out and chown all the gnome desktop config files (in ~/.gnome*, I assume) to another user on the system. You could have the group 'guest' and have two accounts that are in that group, for example. You could have the 'guest' account, which is the one used by the people, and a 'phonyguest' account, which would own the desktop config files in 'guest''s home directory. Make it so that the 'guest' account can read the files owned by 'phonyguest', but not write to them.
You don't want to block the entire/home/guest directory from being written to by 'guest', however. If a user needs to browse the web or write a document or something, it wouldn't be pretty. This is where a logout script comes in to place - have it clean out anything that's not a designated config file. In fact, since it'll be executed by the 'guest' guest, it won't be able to wipe out stuff that's owned by 'phonyguest'.
So if this works out right, you should get the desired affect: User sits down at computer, and it's clean. User can use programs, but not modify desktop settings. User is done using computer, and logs out. Data created by user is erased. Computer automatically logs back in. New user can use it, without any old stuff cluttering his space.
Idea #2: Another option (with much less work involved) would just be to allow the 'guest' user to do anything that s/he likes. The logout script would wipe out the entire/home/guest directory and then copy over files in the skel directory and any extra desktop configuration files that you added to make things look right. This is more user-friendly also, since it allows users to do whatever they feel like. And it's worry-free for any new person that logs on. And you don't have to worry about having an extra user on your system that does almost absolutely nothing ('phonyguest').
Oh yea..forgot about the newton. They were nice...apple should resurrect their PDA line. Maybe they could make an embedded OS X to compete with the PocketPC line.
Because graffiti, afaik, was the first usable, universal "handwriting" recognizer. Qwerty came before Dvorak, so people got used to it. Palm graffiti came before other similar tools, so graffiti became popular.
People won't want to learn something new unless it has benefits that they can SEE before they DO it.
People won't know if Dvorak will actually help their WPM by that much until after they spend time doing it.
However, with the case of Palm and its decline in popularity, people are willing to learn other handwriting recognition characters since PocketPCs, for example, *seem* to do so much more!
Thus, the benefit here is other functionality. The benefit with a Dvorak keyboard would only be less stress and faster WPM. But like I said, you can't SEE that until after you've spent time learning it...which most people (including myself) don't want to do.
Slashdot Mirror
The artist did a good job with this logo and font, I just don't think it's appropriate for the product it's representing. How does this represent what FreeBSD *is*? As other people have already noted, this makes "FreeBSD" look like some new fad, a trendy plastic thing that may never mature. A solid, reliable product shouldn't be represented this way, this logo does it no justice. Though I like the font, again, I don't think it screams FreeBSD. Wouldn't a boxy, bold font be better? Why does there even need to be an icon? Couldn't something artistic (simple but arresting) have been done just with the text?
so it's deadjournal now ?
so how exactly did they make the music? an external instrument midi thing, or some incredible piece of software?
I haven't really used KDE, but you can do what you want with either KDE or Gnome. It's really a matter of your own preference, and what you think users will be more familiar with. Some Windows users like KDE better. But Gnome can be configured to resemble windows as well, so it's really up to you.
/home/guest directory from being written to by 'guest', however. If a user needs to browse the web or write a document or something, it wouldn't be pretty. This is where a logout script comes in to place - have it clean out anything that's not a designated config file. In fact, since it'll be executed by the 'guest' guest, it won't be able to wipe out stuff that's owned by 'phonyguest'.
/home/guest directory and then copy over files in the skel directory and any extra desktop configuration files that you added to make things look right. This is more user-friendly also, since it allows users to do whatever they feel like. And it's worry-free for any new person that logs on. And you don't have to worry about having an extra user on your system that does almost absolutely nothing ('phonyguest').
It sounds like you want a single guest account per machine, which is why you don't want settings changed. Because if you didn't care about managing multiple accounts, then you wouldn't care about changed settings. In which case, you probably wouldn't want users worrying about logging in as "guest", since that's just another "instruction" page that you have to print out and post to every machine.
I know that GDM, the "Gnome display manager" which makes graphical login to gnome easy, has an option to allow for automatic login. You could set up GDM to automatically log in the guest account. If you were an administrator, you could just switch the tty, kill gdm and startx as yourself if you ever needed to get into X under the administrator account.
Next, you said that you didn't want settings modified by this guest account. Two ideas:
Idea #1:
Create this new account and configure settings the way you want them. Then log out and chown all the gnome desktop config files (in ~/.gnome*, I assume) to another user on the system. You could have the group 'guest' and have two accounts that are in that group, for example. You could have the 'guest' account, which is the one used by the people, and a 'phonyguest' account, which would own the desktop config files in 'guest''s home directory. Make it so that the 'guest' account can read the files owned by 'phonyguest', but not write to them.
You don't want to block the entire
So if this works out right, you should get the desired affect: User sits down at computer, and it's clean. User can use programs, but not modify desktop settings. User is done using computer, and logs out. Data created by user is erased. Computer automatically logs back in. New user can use it, without any old stuff cluttering his space.
Idea #2:
Another option (with much less work involved) would just be to allow the 'guest' user to do anything that s/he likes. The logout script would wipe out the entire
Hope this helps
Oh yea..forgot about the newton. They were nice...apple should resurrect their PDA line. Maybe they could make an embedded OS X to compete with the PocketPC line.
Because graffiti, afaik, was the first usable, universal "handwriting" recognizer. Qwerty came before Dvorak, so people got used to it. Palm graffiti came before other similar tools, so graffiti became popular.
People won't want to learn something new unless it has benefits that they can SEE before they DO it.
People won't know if Dvorak will actually help their WPM by that much until after they spend time doing it.
However, with the case of Palm and its decline in popularity, people are willing to learn other handwriting recognition characters since PocketPCs, for example, *seem* to do so much more!
Thus, the benefit here is other functionality. The benefit with a Dvorak keyboard would only be less stress and faster WPM. But like I said, you can't SEE that until after you've spent time learning it...which most people (including myself) don't want to do.