Ok, I figured out what was not working.
I thought it was quite stupid to use /home/net (which is a symbolic link to
/net) in auto.master map, and tried to use the real mount point /net. And it
worked as expected. Now I can deploy. I'm so happy !!!
Sorry for this useless bug report...
--
(luci
Hello,
Just tried today from a fresh install of Maverick (10.10 32bits).
Doesn't work as expected, and you know I'd love to deploy Maverick... If
anyone has a hack/turnaround for this, tell me please.
--
(lucid) autofs had a strange behaviour with paths
https://bugs.launchpad.net/bugs/605062
You
Re-do today the configuration from a fresh install, exactly the same
behaviour...
--
(lucid) autofs had a strange behaviour with paths
https://bugs.launchpad.net/bugs/605062
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in ubuntu
Public bug reported:
Binary package hint: autofs5
Hello, (sorry for my english, I will try to make it clear, french here)
I'm upgrading my workstations from karmic to lucid 32bits and I've got a
strange behaviour with autofs.
The home directories (on my.debian.lenny.server:/home/net) are automo
Hi all,
well, after reinstallation an reconfiguration of the full system, it now
works... The only thing i did is to remove the file /etc/hostname
(without believing in this action) and it's ok now... So now I can
deploy Sorry for that...
--
hostname supplied by dhcp server is not used
https
Hello...
I was so happy finding this script but it didn't work for me... I tried to use
it on karmic today. First I did like on hardy, using a hostname file empty (it
was well working), but it seems it prevents the eth0 interface to be brought up
networkmanager and even if declared in /etc/netw
