ubiquity (2.3.18) maverick; urgency=low
[ Evan Dandrea ]
* Improve the text on the prepare page, based on input from Matthew
Paul Thomas, Amanda Brock, and Andrew Sinclair
(LP: #635269, LP: #635260).
* Translate latitude and longitude from the Geonames service to its
respective
Hello,
So now I realize my 'bug' is actually a feature and we have comments all the
way to the top. very cool.
The installer should have a place to set the host name of the computer.
Put it back . Maybe tweak it so its more like a question, Do you want
to name this computer or is I_dont_care
The fix is already released in Ubiquity version 2.3.18 and said to be
included in today's daily build.
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Branch linked: lp:ubuntu/ubiquity
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Just for the record: one more reason to avoid duplicate hostnames is
that some DHCP servers (including ones run by some ISPs) (re-)assign IP
addresses based on the hostname a host supplies to it (hey I know that
host, let's re-assign its previous IP), and that could result in real
breakage when
On 09/09/10 23:57, Dave Gilbert wrote:
(I think this is a general case of over-simplification - please don't
take it too far!)
Yes, it's a mistake to go too far, but you don't know how far is too far
till you really push it. I'd rather we erred on the side of
oversimplification, because we
** Branch linked: lp:ubiquity
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Mark,
Thanks for the reply. Some things to consider I think are, having simplified
something what the alternatives are for someone;
in this case if they want to do it they end up having to edit a critical
system config file or two as root.
So yes, it is a very slight simplification of the
** Changed in: ubiquity (Ubuntu)
Status: Confirmed = Fix Committed
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
As the sole user of a multi-PC LAN, I too feel the need to set specific
hostnames for each machine.
(so that I don't have to furtle with my router firewall settings every single
time I do a re-install).
--
Maverick ubiquity lacks option to change computer name
I don't see setting the name as advanced, and the old installers filled
it in so that people didn't have to think about it.
It's a perfectly normal thing to do during installation and removing it
is a serious pain since there is no easy way to change it afterwards.
By all means remove it from the
I'd like to know the rationale behind the removal of hostname choice in
the installer - particularly when there is no easy way to change it
post-install. Are we against people choosing their own name for the
computer altogether?
+1 on Randall's suggestion.
--
Maverick ubiquity lacks option to
The specification for the installer that was used at UDS can be found
here: http://docs.google.com/View?id=dfkkjjcj_101gnkrpg5v
The spec describes the first Objective of the installer as: Make
installation process quick with an engaging hand-off to the desktop.
It goes on to describe the Problem
Now to the fact that there is no way to change the name of the machine.
If that is a use-case we need to support, let's design and make the best
way to do that.
this is only needed indeed if all computers you install in a network end
up with the same name assigned automatically.
if there is
Ivanka, to reframe Oliver's comment: we heavily promote the idea that
lots of apps allow easy sharing with machinename.local. And all of
those break if you end up with two machines called michael-desktop.local
So, we probably need to do this.
I agree with your assessment that we do not want a
It seems very much likely that we will wind up with a set of tools to set and
change the machine name so it is likely that there is little more needed from
me, but I wanted to add another comment.
Ivanka Majic helpfully listed the design goals for the installer. I think the
goal of Make
Maybe we could bifurcate the installation process at the outset -- a big
button that says I'm a new user, help me out! and a barely visible
link underneath that says I'm an advanced user, show me the goods.
This way, the default option would give new users the ooh shiny button,
let's click effect,
Maybe we could bifurcate the installation process at the outset -- a big
button that says I'm a new user, help me out! and a barely visible link
underneath that says I'm an advanced user, show me the goods.
That's my thoughs (wish) too, to divide the install process in near
future into a
@jyio @Bowmore: Mark has been pretty clear that we don't want to go down
the route of having an Advanced pathway on the Live CD and I'm
inclined to agree.
However, it would appear that we generally agree that hostname should be
exposed in the installer (for many reasons), and that it should be an
As David said, we prefer to avoid Advanced option sets and questions.
They create alternative code paths that are inevitably poorly tested,
and compounded by one another. We are very fortunate to benefit from the
amazing Debian installer on the alternative install CD that provides
very precise
On 06/09/10 22:41, David Guest wrote:
I'd never really thought about your first point Mark, but I agree, it
would be nice to have an applet to shield users from the command line
for something as simple as a hostname change.
Indeed. I think it belongs in one of the system settings, so I've
I'll let Michael or someone from the design team speak on why this
should not be exposed in the user interface. That said, with guidance
from the design team, we've taken great pains to remove dialogs,
especially the advanced dialog, from the installer. If we are to at
some point add the
I use my own specific naming convention on my home network, having to be
forced into googling what command line options I have to throw in just
to allow those names simply degrades the user experience for anyone
going a bit more advanced.
I would rather see this being editable during setup. You
*If* we are thinking about getting a sensible naming scheme for the hostname ,
bug 486050 [ Default computer name confusing ]
Can also be knocked out at the same time.
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug
I understand Mark's solution of adding the MAC address (or something) on
as a suffix to the machine name to prevent name collisions, but I think
that it would add yet more clutter to the machine name. As it stands
now, a long username with -desktop is already too much text when using
the command
Choosing a custom host name is right on the threshold of necessary,
afaics. At this stage I'm supportive of the current approach of making
it a live-CD boot parameter as long as that's well documented. We're
definitely not going to add it to the questions we expose to every user,
nor are we going
@Mark
I'm going to lobby for putting the user first. And, to do so we can
possibly lift (and improve) a page from the Fruit Sellers In Cupertino
(FSIC) on this one:
Please type a name your computer. It's a simple question and gives the
user a sense of being in control. (They are already typing
I tried putting in the string that Evan suggested but it didn't work for
me - perhaps I was adding it in the wrong place... Any suggestions on
that? Does it have to be in particular place?
Either way, this seems overly complicated just to be able to choose a
hostname at install time. This is
Am Dienstag, den 07.09.2010, 14:40 + schrieb Mark Shuttleworth:
Choosing a custom host name is right on the threshold of necessary,
afaics. At this stage I'm supportive of the current approach of making
it a live-CD boot parameter as long as that's well documented. We're
definitely not
+1 for Oliver's idea
Don't forget then THE MEME for hostname of linux-box on planet.*
A other choice is use of http://computernamer.com/ ;-)
bye
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are
Though I'd love to have the installer always ask for hostname, Oliver's
solution would be a good compromise situation for me and my shop.
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member
@ Evan Dandrea,
You said, Advanced users can still set their own hostname by putting
netcfg/get_hostname=ubuntupad on the live CD's kernel command line. To
do this, press a key when you see the keyboard = accessibility options
image, then select a language, press F6, followed by escape.
I'd like
I doubt that adding more use cases to this thread will matter much, but I must
mention that this bug coupled with the inability to easily change host names
creates problems for those of us attempting to use Ubuntu in a more corporate
environment. We set up Ubuntu to authenticate against our
I doubt that adding more use cases to this thread will matter much
Much to the contrary we need all the feedback we can get.
I'd also be much more comfortable if this were assigned to someone :^)
Evan .. Colin . ?
Help me out here, please.
I'll jump through any hoops requested ;^)
--
I think there are two separate issues:
1. we need an effective way to rename a machine post-install.
2. we need to take a view on how important it is to expose the name during
install, and how visible to make the option to change it.
If name conflicts are a problem, then [1] is just as
Thank you Mark. I couldn't agree more.
Somewhere around Intrepid or Jaunty we dropped the gui to allow for
changing that.
While it doesn't effect me personally doesn't make it any less serious,
and after googling quite a bit there is no one correct way to
accomplish this. Since it doesn't
I'd never really thought about your first point Mark, but I agree, it
would be nice to have an applet to shield users from the command line
for something as simple as a hostname change.
As for the second, I think it's important that it be exposed in the
installer, even if it gets hidden behind an
Thanks for the response Mark, this will make running things in our
corporate environment much easier.
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Having to change the hostname post-install is made more awkward by the
fact that it's not just one place it needs to be changed. At the very
least you need to change it in /etc/hosts and /etc/hostname, but also
some programs (I think postfix is one that springs to mind, but there
might be others
i disagree that this is an advanced task at all.
if i let my (completely computer illiterate) 73 year old mother do an install i
observe, she has a lot less probs to understand that she has to give her
computer a name than getting the concept of the difference between real name
and login ...
I agree with seeker5528 that duplicate network names could well be an
issue. I've got quite a lot of machines to upgrade and having to do this
manually, whilst very simple, is something I'd like to avoid. An
Advanced tab or similar that includes the ability to change the
hostname at install is
I agree on simplicity here but that does not exclude ubiquity from
providing advanced options as well in a tab or behind a button.
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of
I'd love to see an advanced configuration option that allows hostname
selection, because there's nothing like descriptive names on the
network. I could easily imagine having three or four username-desktop
machines on my network, which would be really confusing.
Another option would be to launch
** Attachment added: Casper.gz
https://bugs.launchpad.net/bugs/628087/+attachment/1534495/+files/Casper.gz
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/628087/+attachment/1534496/+files/Dependencies.txt
** Attachment added: UbiquityDebug.gz
** Tags added: iso-testing
--
Maverick ubiquity lacks option to change computer name
https://bugs.launchpad.net/bugs/628087
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I believe this was intentionally removed as part of the installer
redesign, but design work may be open to re-evaluation in light of user
feedback, so this bug might as well remain open ...
** Changed in: ubiquity (Ubuntu)
Importance: Undecided = Low
** Changed in: ubiquity (Ubuntu)
This is also a problem for amd64.
I would hope that this remains open. This is a security risk. Nothing
like just having you user name listed for folks that might need it.
If this is a feature instead of a bug it is a really stupid feature.
--
Maverick ubiquity lacks option to change
I fail to see how this presents a security risk, in fact I think that
argument could be reversed.
Regardless lets keep this civil. Words like stupid are not
particularly useful and only tend to inflame emotions rather than
resolve anything.
--
Maverick ubiquity lacks option to change computer
For the typical home use situation, having the user name as the host
name doesn't really seem like much of a security risk, in a corporate
situation I would be more inclined to think about the security
implications.
Duplicate hostnames on the network seems like a much bigger issue.
The best
I'd keep it very simple.
Since the ability to rename a computer changed after Hardy or Intrepid,
where you could just use a gui, I'd simply create an official Ubuntu
document describing how to properly do so. I'd probably link to it in
the Release Notes.
I dare anyone to google the solution now.
50 matches
Mail list logo
