On Sun, Aug 09, 2009 at 06:26:15PM +0200, Julian Andres Klode wrote:
> On Sun, Aug 09, 2009 at 05:44:32PM +0200, Aurelien Jarno wrote:
> > > Installed: keyboard layouts missing
> > > ------------------------------------
> > > There appears to be no way to use a keyboard layout different
> > > than the standard US one.
> >
> > Maybe related to the problem in the installer.
> This was on an installation using the sysinstall based disc. I don't
> know about the d-i created installation. But maybe I just don't know
> how to change the keyboard layout in kFreeBSD.
dpkg-reconfigure kbdcontrol
I fixed my problem with this command, but after reboot. and I have this problem on debian installer when start installing base system.
I have some problems with set users passwords, I can't login in the system, then of the installation the file /etc/shadow is in wrong format, I don't know if it is coding.
cat /etc/shadow
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
I fixed this issue recreating shadow file and setting same configuration of my sysinstall installation.
cat /etc/shadow
root:erase_password:14466:0:99999:7:::
daemon:*:14437:0:99999:7:::
bin:*:14437:0:99999:7:::
sys:*:14437:0:99999:7:::
sync:*:14437:0:99999:7:::
games:*:14437:0:99999:7:::
man:*:14437:0:99999:7:::
lp:*:14437:0:99999:7:::
mail:*:14437:0:99999:7:::
news:*:14437:0:99999:7:::
uucp:*:14437:0:99999:7:::
proxy:*:14437:0:99999:7:::
www-data:*:14437:0:99999:7:::
backup:*:14437:0:99999:7:::
list:*:14437:0:99999:7:::
irc:*:14437:0:99999:7:::
gnats:*:14437:0:99999:7:::
nobody:*:14437:0:99999:7:::
libuuid:!:14437:0:99999:7:::
Debian-exim:!:14437:0:99999:7:::
sshd:*:14437:0:99999:7:::
junix:erase_password:14437:0:99999:7:::
After, the file /etc/fstab is misconfigured.
http://imagebin.ca/view/c-OqOc.html (dmesg: mount options <defaults> is unknown, and cat /etc/fstab)
http://imagebin.ca/view/VEXGJX.html (Sysinstall settings /etc/fstab)
I've changed default for rw and I get booting my first installation :) =D
> > > Installed: Filesystem of /proc should be procfs
> > > -------------------------------------
> > > The filesystem of /proc should be procfs and not linprocfs in
> > > order to be compatible to FreeBSD. linprocfs only emulates parts
> > > of a Linux 2.4 procfs and is not really useful. This is needed
> > > e.g. to get kbuild working, as it calls readlink() on
> > > /proc/curproc/file which is only available on procfs.
> >
> > linprocfs is really useful, a lot of applications breaks without it.
> OK, but BSD applications may also break without procfs or not behave
> correctly. At least it is not as critical as I thought, because kbuild
> seems to work without procfs.
We have a lot more GNU application than BSD applications.
> >
> > > If this gets changed, /sys should maybe be dropped to, and both
> > > linux compatibility FS should be mounted somewhere in e.g.
> > > /var/lib/linux (i.e. /var/lib/linux/{sys,proc}).
> >
> > This will break a lot of application looking in /proc and /sys for Linux
> > style files, not something we are going to change until all those
> > applications are fixed (aka in a few years).
> The question would be how to fix them. You can't fix an application to support
> FreeBSD's procfs if it is not mounted.
Change them to use sysctl or any other source of information instead of
/proc, meaning a different code than the GNU/Linux one, and thus
difficult to get integrated patches.