On Monday 26 June 2006 10:16, Christopher wrote:
> I am posting this again, as I have not received a reply, and the archive
> on source forge does not appear to have been updated in about 5 days. I
> really need to get this issue resolved.
I did send you a reply. If that is not the problem, then I don't know what is
going on.
Unfortunately, debugging it is a bit difficult, but can be done under qemu
providing you force it to use a NON-smp kernel. qemu at least the last
version I had could not handle smp kernels. The Makefile has a target that
runs the iso under qemu.
I don't have the time to properly maintain the package, which is *extremely*
useful and has saved me at least 3 or 4 times from doing major restores. I
am considering switching to using mkcdrec, which looks like a very well
written and maintained package. It also looks relatively simple for someone
to add the Bacula specific code. I am looking for someone who would like to
do this project.
>
> I am using bash as the root login shell.
>
> /bin/sh is shown as below from the shell:
>
> [EMAIL PROTECTED] etc]# which sh
> /bin/sh
> [EMAIL PROTECTED] etc]# cd /bin
> [EMAIL PROTECTED] bin]# ls -l sh
> lrwxrwxrwx 1 root root 4 May 28 23:27 sh -> bash
>
> The contents of the rootetc.list file in the cdrom build directory is:
>
> /etc/bashrc
> /etc/exports
> /etc/gshadow
> /etc/shadow
> /etc/passwd
> /etc/group
> /etc/hosts
> /etc/filesystems
> /etc/fstab
> /etc/protocols
> /etc/localtime
> /etc/ld.so.cache
> /etc/syslog.conf
>
> The contents of the rootsbin.list file is:
>
> roottree/sbin/arp
> roottree/sbin/ash
> roottree/sbin/awk
> roottree/sbin/badblocks
> roottree/sbin/basename
> roottree/sbin/bash
> roottree/sbin/bunzip2
> roottree/sbin/bzip2
> roottree/sbin/cat
> roottree/sbin/cdrecord
> roottree/sbin/chattr
> roottree/sbin/chgrp
> roottree/sbin/chkconfig
> roottree/sbin/chmod
> roottree/sbin/chown
> roottree/sbin/chroot
> roottree/sbin/clear
> roottree/sbin/consoletype
> roottree/sbin/cp
> roottree/sbin/cut
> roottree/sbin/date
> roottree/sbin/dd
> roottree/sbin/debugfs
> roottree/sbin/df
> roottree/sbin/dhclient
> roottree/sbin/dhcpd
> roottree/sbin/diff
> roottree/sbin/dig
> roottree/sbin/dmesg
> roottree/sbin/dosfsck
> roottree/sbin/du
> roottree/sbin/dump
> roottree/sbin/e2fsck
> roottree/sbin/e2label
> roottree/sbin/egrep
> roottree/sbin/eject
> roottree/sbin/false
> roottree/sbin/fdisk
> roottree/sbin/fgrep
> roottree/sbin/file
> roottree/sbin/find
> roottree/sbin/findfs
> roottree/sbin/free
> roottree/sbin/fsck
> roottree/sbin/fsck.cramfs
> roottree/sbin/fsck.ext2
> roottree/sbin/fsck.ext3
> roottree/sbin/fsck.jfs
> roottree/sbin/fsck.msdos
> roottree/sbin/fsck.vfat
> roottree/sbin/ftp
> roottree/sbin/gdb
> roottree/sbin/getkey
> roottree/sbin/grep
> roottree/sbin/grub
> roottree/sbin/grubby
> roottree/sbin/grub-install
> roottree/sbin/grub-md5-crypt
> roottree/sbin/grub-terminfo
> roottree/sbin/gunzip
> roottree/sbin/gzip
> roottree/sbin/halt
> roottree/sbin/hdparm
> roottree/sbin/head
> roottree/sbin/hostname
> roottree/sbin/hotplug
> roottree/sbin/id
> roottree/sbin/ifconfig
> roottree/sbin/init
> roottree/sbin/insmod
> roottree/sbin/insmod.static
> roottree/sbin/ipcalc
> roottree/sbin/kill
> roottree/sbin/killall
> roottree/sbin/killall5
> roottree/sbin/klogd
> roottree/sbin/last
> roottree/sbin/ldd
> roottree/sbin/less
> roottree/sbin/lilo
> roottree/sbin/ln
> roottree/sbin/loadkeys
> roottree/sbin/login
> roottree/sbin/losetup
> roottree/sbin/ls
> roottree/sbin/lsmod
> roottree/sbin/lsof
> roottree/sbin/lspci
> roottree/sbin/lsusb
> roottree/sbin/ltrace
> roottree/sbin/mail
> roottree/sbin/md5sum
> roottree/sbin/mgetty
> roottree/sbin/mingetty
> roottree/sbin/mkbootdisk
> roottree/sbin/mkdir
> roottree/sbin/mkdosfs
> roottree/sbin/mke2fs
> roottree/sbin/mkfs
> roottree/sbin/mkfs.cramfs
> roottree/sbin/mkfs.ext2
> roottree/sbin/mkfs.ext3
> roottree/sbin/mkfs.jfs
> roottree/sbin/mkfs.msdos
> roottree/sbin/mkfs.vfat
> roottree/sbin/mkinitrd
> roottree/sbin/mkisofs
> roottree/sbin/mknod
> roottree/sbin/mkreiserfs
> roottree/sbin/mkswap
> roottree/sbin/modinfo
> roottree/sbin/mktemp
> roottree/sbin/modprobe
> roottree/sbin/more
> roottree/sbin/mount
> roottree/sbin/mt
> roottree/sbin/mv
> roottree/sbin/nash
> roottree/sbin/netstat
> roottree/sbin/nice
> roottree/sbin/nm
> roottree/sbin/nmap
> roottree/sbin/nologin
> roottree/sbin/od
> roottree/sbin/parted
> roottree/sbin/passwd
> roottree/sbin/ping
> roottree/sbin/portmap
> roottree/sbin/printenv
> roottree/sbin/ps
> roottree/sbin/pwd
> roottree/sbin/raidstart
> roottree/sbin/reboot
> roottree/sbin/reiserfsck
> roottree/sbin/rm
> roottree/sbin/rmt
> roottree/sbin/rmdir
> roottree/sbin/rmmod
> roottree/sbin/route
> roottree/sbin/rpc.lockd
> roottree/sbin/rpc.statd
> roottree/sbin/runlevel
> roottree/sbin/scp
> roottree/sbin/script
> roottree/sbin/scsi_info
> roottree/sbin/sfdisk
> roottree/sbin/sh
> roottree/sbin/shutdown
> roottree/sbin/sleep
> roottree/sbin/sort
> roottree/sbin/ssh
> roottree/sbin/ssh-keygen
> roottree/sbin/strace
> roottree/sbin/strings
> roottree/sbin/stty
> roottree/sbin/su
> roottree/sbin/swapoff
> roottree/sbin/swapon
> roottree/sbin/sync
> roottree/sbin/sysctl
> roottree/sbin/syslogd
> roottree/sbin/tail
> roottree/sbin/tar
> roottree/sbin/telinit
> roottree/sbin/test
> roottree/sbin/top
> roottree/sbin/touch
> roottree/sbin/tput
> roottree/sbin/true
> roottree/sbin/tune2fs
> roottree/sbin/udev
> roottree/sbin/udevstart
> roottree/sbin/umount
> roottree/sbin/uname
> roottree/sbin/usleep
> roottree/sbin/vi
> roottree/sbin/w
> roottree/sbin/which
> roottree/sbin/who
> roottree/sbin/whoami
> roottree/sbin/zcat
>
> In the roottree directory sh is symlinked to bash and bash is included
> there.
>
> >From what I can see, the rescue cd should allow me to log in, but as
> >From what I can see, the rescue cd should allow me to log in, but as
>
> stated above it always returns the login incorrect after entering root.
> Are there any other configuration files that I need to proivde copies of,
> in order for further assistance into this annoying error? I really would
> like to get this working, as it is, or at least seems to be the last
> hurdel to cross.
>
> Regards,
>
> Christopher Gregory
>
> > On Tuesday 20 June 2006 06:47, Christopher wrote:
> >> Hello all,
> >>
> >> I am running fedora core 5 and after creating the recovery cd, when I go
> >> to test it on another computer ( I do not want to test it on the actual
> >> server that I have backed up till I know it works) I am unable to
> >> actually
> >> logon.
> >>
> >> After selecting the first option, which is meant to allow you to login,
> >> start network, make any changes etc, it will not go past the login.
> >> Entering root as the username and then pressing enter returns login
> >> incorrect. It never gets to the actual password prompt. I have
> >> compared
> >> passwd and shadow with the files on the server and they are, or at least
> >> appear to be identical.
> >>
> >> This has been compiled from source, and not via a rpm, as is the case
> >> with
> >> bacula itself.
> >>
> >> What do I need to change to allow me to actually log in?
> >
> > Well I suspect that you might be using something other than /bin/sh for
> > your
> > root shell. If that is the case, (as the manual states) you must ensure
> > that
> > your shell is in the listed binaries.
> >
> >> Regards,
> >>
> >> Christopher Gregory
> >
> > --
> > Best regards,
> >
> > Kern
> >
> > (">
> > /\
> > V_V
--
Best regards,
Kern
(">
/\
V_V
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
