Re: pxelinux boot isn't loading woody kernel
Hi Norman, Thanks for your quick reply. Following your suggestion, I verified that the IP address being used by the Shuttle XPC was not already in use, so that wasn't the problem. Further investigation shows that the woody kernel doesn't work with the Shuttle. I don't know whether the problem is the CPU or the chipset, but kernel-image-2.4.20-1-k7 seems to make a lot more progress in the boot. I haven't gotten it to boot completely yet, but at least now I know that the problem is the kernel (and not the DHCP setup or the TFTP setup or the PXE setup, or something else). Thanks again, Susan On Sat, 29 Mar 2003 17:45:18 CST, Nathan E Norman <[EMAIL PROTECTED]> said: > This is a shot in the dark since I don't have any PXE cards installed > right now. However, I have done netboot installs for several of my > sparcs and ran into a similar problem. The symptom was that after > downloading some amount (a power of 2 no less) the download would > freeze, and tftpd began logging timeouts. I discovered that this was > because the machine attempting to netboot had grabbed an IP address > already in use elsewhere on the network! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pxelinux boot isn't loading woody kernel
I am trying to install Debian onto a floppy-less CD-ROM-less Shuttle XPC SS40G with an AMD Athlon installed. Following the instructions at: http://www.debianplanet.org/node.php?id=818 I obtained the linux.bin and root.bin files from the woody distribution, (woody/main/disks-i386/current/bf2.4), installed them as suggested, got the Shuttle to connect to a DHCP server and fetch itself an IP address, return a boot prompt, and then begin booting. Soon thereafter, the boot loader gets stuck, with the following message: Loading. 8000 AX:0208 BX:0200 CX:0002 DX:. 8000 AX:0208 ... (repeats) At this point, the tftp process begins to record this in syslog: sent DATA timeout: retrying... I checked the md5sums of the linux.bin and root.bin files were correct. Can anyone offer suggestions as to what I might look at to diagnose this problem? Thanks in advance, Susan P.S. In case it matters: this system comes with a network chip built into the motherboard, but I also installed a second network card, and that's what I'm booting with. pgp0.pgp Description: PGP signature
question about amanda's backup user
Hello, Is the following a reasonable invocation of adduser for adding a user named 'backup' on: the amanda-client host? the amanda-server host? adduser --system --ingroup nogroup --home /var/run/backup \ --shell /bin/sh --disabled-password backup >/dev/null 2>&1 || true Are there any security problems or filesystem problems (or amanda problems) with using the above on either type of host? TIA, Susan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: what to do without gnome-session
Pollywog <[EMAIL PROTECTED]> wrote: > It is still gnome-session, but now part of the gnome-session2 package: > > gnome-session2: /usr/bin/gnome-session grep-available -P -sPackage gnome-session2 yields nothing grep-available -P -sPackage gnome | grep session yields only: Package: gnome-session grep-available -PX -sPackage,Version gnome-session yields: Package: gnome-session Version: 1.4.1-1 I looked for another x-session-manager, and found only two: grep-available -FProvides -sPackage x-session-manager Package: kdebase Package: gnome-session Where does one find gnome-session2? Confused, Susan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
what to do without gnome-session
I used to use gnome and start X with the following .xinitrc: exec gnome-session But after upgrading to gnome2, gnome-session has disappeared. What am I supposed to exec to launch gnome2 session? I tried using exec /etc/X11/Xsession but that never produced an Xwindow screen (just some noise). This may or may not be related to the fact that I'm using nvidia drivers. TIA, Susan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
