On Sun 02 Oct 2016 at 08:56:07 -0400, Gene Heskett wrote:
> The hostname command is both a query tool, and a name setter. "man
> hostname" is your friend. You'll probably be asked for your passwd, or
> need to become root somehow. On the *buntu's try sudo hostname.
Jessie users might want to
On Sunday 02 October 2016 02:06:44 Byung-Hee HWANG (황병희, 黃炳熙) wrote:
> Hello, Debian people!
>
> I love my Chromebook. Via Crouton, i did install Ubuntu ( the internal
> is Debian Wheezy, i guess).
>
> (precise)soyeomul@localhost:/etc$ cat os-release
> NAME="Ubuntu"
> VERSION="12.04.5 LTS, Precise
Felix is right, indeed here ".chromebook" would indicates the DOMAIN and
not the name of the HOST.
But if you don't expect to use the chromebook in a network with a managed
domain, maybe you will not have particular problem. Indeed I never thought
to use a "." with the hostname command...
Byung-He
Byung-Hee HWANG (황병희, 黃炳熙) composed on 2016-10-02 15:06 (UTC+0900):
Hello, Debian people!
I love my Chromebook. Via Crouton, i did install Ubuntu ( the internal
is Debian Wheezy, i guess).
(precise)soyeomul@localhost:/etc$ cat os-release
NAME="Ubuntu"
VERSION="12.04.5 LTS, Precise Pangolin
The is no "hostname" service to start
Please, try:
sudo hostname "alex.chromebook"
and verify with
hostname
Else, reports here the content of /etc/resolv.conf/ and /etc/hosts
Ciao
F.
2016-10-02 8:22 GMT+02:00 Byung-Hee HWANG (황병희, 黃炳熙) :
> "Byung-Hee HWANG "(황병희, 黃炳熙)"" 께서 쓰시길,
> 《記事 全文
If you're wondering, the way I did it was to change
/etc/init.d/hostname.sh to include:
PATH=/sbin:/bin:/usr/bin:/usr/local/bin
...
do_start () {
if [ -z "${HOSTNAME}" ]; then
MAC_MAGIC="$(macstr | sed 's/://g' | cksum | cut -d ' ' -f 1 |
xargs
printf '%08X')"
Christofer C. Bell wrote:
> /bin/echo dt$(/sbin/ifconfig eth0 | head -1 | awk -F: '{print $4$5$6}') >
> /etc/hostname
Why the full paths? Those have only ever hurt me. It is therefore a
pet peeve of mine to challenge the use of them. They always hurt me.
And I always remove them whenever I see
On Tue, Feb 28, 2012 at 12:08 AM, Jason Heeris wrote:
> On 28 February 2012 13:40, Tom H wrote:
>> Everywhere that I've worked the hostnames have had something to
>> indicate its purpose and its location.
>
> I don't think this reasoning can be applied here though. There will be
> dozens of ident
On Tue, Feb 28, 2012 at 1:08 AM, Jason Heeris wrote:
> On 28 February 2012 13:40, Tom H wrote:
>>
>> Everywhere that I've worked the hostnames have had something to
>> indicate its purpose and its location.
>
> I don't think this reasoning can be applied here though. There will be
> dozens of ide
On 28 February 2012 13:40, Tom H wrote:
> Everywhere that I've worked the hostnames have had something to
> indicate its purpose and its location.
I don't think this reasoning can be applied here though. There will be
dozens of identical devices plugged into the network, and hundreds in
total (bu
On Mon, Feb 27, 2012 at 7:07 PM, Jason Heeris wrote:
> On 28 February 2012 00:27, Tom H wrote:
>> Thanks for the explanation. It's a good plan but I think that you
>> name'll be invoked in some non-flattering contexts once this is
>> implemented... :)
>
> How would you approach it?
Everywhere
On 28 February 2012 09:21, Paul E Condon wrote:
> I didn't intend that the two steps be separated by some manual
> process. I worry that when you start implementing the system you might
> find that the total fix cannot actually be done at one point during
> the boot process.
Nope it works! ifconf
On 20120228_081002, Jason Heeris wrote:
> On 28 February 2012 03:28, Paul E Condon wrote:
> > I've been lurking, hoping to learn. Maybe I don't fully understand, but ---
> > Wouldn't you be better off using the MAC address of the interface chip in
> > each computer
> > rather than a random number
On 28 February 2012 03:28, Paul E Condon wrote:
> I've been lurking, hoping to learn. Maybe I don't fully understand, but ---
> Wouldn't you be better off using the MAC address of the interface chip in
> each computer
> rather than a random number. The MAC address is supposed to be unique. I know
On 28 February 2012 00:27, Tom H wrote:
> Thanks for the explanation. It's a good plan but I think that you
> name'll be invoked in some non-flattering contexts once this is
> implemented... :)
How would you approach it?
> "cp /etc/rc.local /etc/rc.local.final" and "vi /etc/rc.local" to add
> yo
On 20120227_131327, Jason Heeris wrote:
> I have an image of a Debian Squeeze system that I want to put onto
> multiple systems (flash-based disks for a single-board computer). I'd
> like each system to have a different hostname, but have that hostname
> persist across subsequent reboots.
>
> My f
On 20120227_131327, Jason Heeris wrote:
> I have an image of a Debian Squeeze system that I want to put onto
> multiple systems (flash-based disks for a single-board computer). I'd
> like each system to have a different hostname, but have that hostname
> persist across subsequent reboots.
>
> My f
ioning procedure ;)
Thanks for the explanation. It's a good plan but I think that you
name'll be invoked in some non-flattering contexts once this is
implemented... :)
I forgot about your earlier question about a one-time hostname change.
I think that this'll work:
"cp /e
On 27 February 2012 20:50, Tom H wrote:
> Aren't your users going to hate the random names?
They won't be end users, but production staff. (I can certainly see
how you'd be sceptical of doing this for some poor end user...) There
will be multiple devices being built in a workshop, and they'll nee
On Mon, Feb 27, 2012 at 3:49 AM, Jason Heeris wrote:
> On 27 February 2012 16:19, Bob Proulx wrote:
>>
>> If you are generating random hostnames then does it actually matter
>> what name the current host uses? Would "localhost" be as good as any
>> randomly generated one?
>
> The randomness is n
On 27 February 2012 17:05, Bob Proulx wrote:
> I would do it later in runlevel 2 (same as 2-5). Even at the very end
> would be fine. You could use "Required-Start: $all" if you like.
I'll try it.
> Alternatively instead of a random name have you considered using the
> name it gets from revers
Jason Heeris wrote:
> Bob Proulx wrote:
> > You could still set the hostname randomly. Then later come back and
> > write the current hostname to the /etc/hostname file when it is
> > writable.
>
> Later in the rcS sequence, or in rc[2-5]?
I would do it later in runlevel 2 (same as 2-5). Even a
On 27 February 2012 16:19, Bob Proulx wrote:
> If you are generating random hostnames then does it actually matter
> what name the current host uses? Would "localhost" be as good as any
> randomly generated one?
The randomness is needed to avoid name collisions when multiple
devices are running.
Jason Heeris wrote:
> I have an image of a Debian Squeeze system that I want to put onto
> multiple systems (flash-based disks for a single-board computer). I'd
> like each system to have a different hostname, but have that hostname
> persist across subsequent reboots.
If you are generating random
I have an image of a Debian Squeeze system that I want to put onto
multiple systems (flash-based disks for a single-board computer). I'd
like each system to have a different hostname, but have that hostname
persist across subsequent reboots.
My first thought was that I could remove "/etc/hostname"
Interesting. I have just tried it with base-config, and it appears to have
worked. But, just in case, is there anywhere else I need to change it? Thanks.
--xyrael.net--
Quoting Bill Marcum <[EMAIL PROTECTED]>:
On Fri, Sep 23, 2005 at 04:50:26PM +0100, Sean Whitton wrote:
Hi,
My friend insta
On 9/23/05, Bill Marcum <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 23, 2005 at 04:50:26PM +0100, Sean Whitton wrote:
> > Hi,
> >
> > My friend installed Debian on his computer and I'm supposed to be
> > admining it as a server. THings are going well (except I keep
> > mistyping shutdown and killing t
On Fri, Sep 23, 2005 at 04:50:26PM +0100, Sean Whitton wrote:
> Hi,
>
> My friend installed Debian on his computer and I'm supposed to be
> admining it as a server. THings are going well (except I keep
> mistyping shutdown and killing the server), but there is one problem:
> the hostname.
>
> He
On Friday 23 September 2005 09:50 am, Sean Whitton wrote:
> Hi,
>
> My friend installed Debian on his computer and I'm supposed to be admining
> it as a server. THings are going well (except I keep mistyping shutdown and
> killing the server), but there is one problem: the hostname.
>
> He typed As
Hi,
My friend installed Debian on his computer and I'm supposed to be admining it as
a server. THings are going well (except I keep mistyping shutdown and killing
the server), but there is one problem: the hostname.
He typed Ask4 instead of ask4, which is a problem.
I assume I can change this wi
Haines Brown writes:
> I need to tell gnus to use just my domain name in the From line in the
> header. Anyone know how to do that?
Put a line like this in ~/.gnus:
(setq gnus-system-name "dhh.gt.org")
--
John Hasler
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe
I've been googling and reading, and find that there's no consistency
in setting the value of hostname.
My FQDN is teufel.hartford-hwp.com. A few places said to use the
localhost name ("teufel"), in some others, it suggested just the
domain ("hartford-hwp.com"), and most often it is the FQDN.
Chan
When I installed sarge last time, I managed to insert my FQDN in as
hostname:
# hostname teufel.hartford-hwp.com
and now regret it. I must change my domain name to "hartford-hwp.com"
and leave my host name (name of my machine) as "teufel," so that the
FQDN ends up being teufel.hartford-hwp.co
33 matches
Mail list logo
