similar to: Add floppy image to pv domain

Hello, I've installed samba 3 on rh9. I configured kerberos, winbind, joined the workstation to the AD domain . Now I am able to login using domain user/password. How can I automatically mount the user's home directory from the windows 2000 server. Thanks, Laszlo

Hi, I'm trying to authenticate users from AD. I did join the machine to the domain, and I'm able to see the users list with wbinfo -u. I have the following problem: "getent passwd" it givs me the list of all users. "getent passwd user" does not give any answer. what could be the problem? I'm using SUSE Linux 10. with the packages that came with the distrib.

Hello everybody, I''am trying to make an installation of a sles9 based system. In order to install this system after booting a floppy disk (or usb) should be "inserted" with a auto configuration file. My problem is what ever I try I can not attach a floppy image to the sles9. the command I tried is xm block-attach <dom nr> file://path/to/floppy.img /dev/fd0 w After

Does anyone know of a way to give DomU a floppy disk of some sort? I need to try and load some drivers at the text mode install step of installing Windows... Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello, when testing FreeBSD-7.1-BETA i discovered that the floppy disk controller doesn't work correctly. Trying to format a floppy (perhaps with bad blocks) i get: Processing fdformat: ioctl(FD_FORM): Device not configured instead of the normal E letter. I then checked the same problem is present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in 2006! Of course the floppy disk

Hello All: I've recently had to provision some RHEL and CentOS VMWare instances. There was no network connectivity so I had to use a kickstart floppy and DVD iso rather than installing from our repository. To create the floppy I used the following: As root: dd if=/dev/zero of=floppy.flp bs=1k count=360 mkfs.vfat floppy.flp mount -o loop floppy.flp /mnt/floppy cp base_kickstart.ks

Trying to be not long, on x86 I have 3 floppies images boot, root-1, root-2 Booting from boot image with no problem, I try reading root-1 and root-2 image in raw format. Reading root-1 and root-2 is made from boot init script, using klibc-1.5.9 or klibc-1.5.10 with debian insmod patch, and a vanilia linux-2.6.24.7 root-1 and 2 images are smaller than 1440 kB and are made the same way with cd

It is now possible to build a bootable floppy image which contains HDT, with my patch applied to Erwans HDT branch: http://git.zytor.com/?p=users/erwan/hdt.git;a=commit;h=16b37fe2266c920087f88cdec94243b71218d871 Unpack the Syslinux archive and build whole Syslinux first, then cd to ./com32/hdt/ and make hdt.img $ make $ cd ./com32/hdt/ $ make hdt.img Now you have a 2.88 MB floppy image which

I found that if I do not have a local floppy installed and enabled on my client, I will get the error 'Non-system disk' when I try to boot DOS floppy images. NT or Syslinux floppy images boot fine. If I enable the floppy in the BIOS, then it boots the DOS floppies just fine. Is this normal? Is there a workaround? There are MS-DOS images, so perhaps this is an MS-DOS limitation. --

Hi, I am trying to load an disk image as Floppy=1, og B: using ISOLINUX. My Config file reads: ------- Begining Of File ------- KERNEL MEMDISK APPEND raw floppy=1 initrd=CERC6.IMG ------- End Of File ------------ --- MEMDISK Output Snip ------ Ramdisk at 0x03b58000, length 0x00168000 command line: initrd=CERC6.IMG raw floppy=1 BOOT_IMAGE=MEMDISK Disk is hard disk, 1440 K, C/H/S =

I just wanted to chime in and mention that I'm running into the problem with getting a "Non-system disk..." error on a system using a USB floppy when the floppy is not attached when I try to boot the system over the network using memdisk to boot a floppy image. Its actually fairly important to be able to do this, as the architecture of the hardware that I'm working with utilizes

Hello, I am using the pxelinux.0 and memdisk files from distribution syslinux-3.36. I am no longer able to access the real floppy disk drive B: instead I just get a mirrored copy of the emulated floppy disk A: The default config file is as follows label 1 kernel memdisk append initrd=kd202.img I was previously using the sysliunx-3.20 distribution which gave me access to the real floppy

Can anybody please tell me how to access the floppy disk drive from wine-installed programs? I've installed some basic accounting software which backs-up to floppy (don't laugh!), but when I try to do this I get the message "no removable drives..." even though I've mounted the floppy drive. The CDROM (fake d:) drive is listed in dosdevices, but floppy (fake a: ?) doesn't

After formatting a floppy to MSDOS format and using syslinux /dev/fd0, I successfully installed ldlinux.sys to the root directory of the floppy. Then I created a syslinux.cfg under the root directtory of this floppy to load the linux kernel in my first hard disk, 3rd partition, boot folder. The file system of this partition is ext3. The floppy has a FAT file system. This config file is listed

Hi, I stumbled on a rather odd problem. A brand new HP Compaq dx2200 computer didn't want to boot up pxelinux+memdisk image. The computer just gave "Disk I/O error" and stopped there. Workaround was rather simple... Just attach regular floppy drive to the motherboard and everything started working fine. I tried with older 2.05 (pxelinux+memdisk) and newer 3.31. Both produced

syslinux 3.11 (from debian's 3.11-3 package) does it job. The machine boots as expected with an 1.44 floppy. Yet the floppy driver's led doesn't turn off. 1) Is this a syslinux issue? 2) Can I safely remove the boot floppy (media) without dameging it? From memory: $ cat syslinux.cfg say linux 2.6.14 (probably with debian modifications) default linux append root=/dev/nfs

Hi guys, I have been fighting with Syslinux and PXElinux for two days now. I have gotten the floppy to boot but can't get pxelinux to work. I get a message: No !PXE or PXENV+ API fournd; we're dead I am guessing this means I need something else on the floppy? The floppy has: # ls /floppy/ total 24K -r-xr-xr-x 1 9.4K Nov 2 16:31 ldlinux.sys -rwxr-xr-x 1 14K Nov 2 16:50

Hi there, http://www.seagate.com/support/disc/download/seatoold_en.exe Seagate offers a Windows executable (needs Win98 or better, 1,9MB) that should create 2 bootable floppy disks that contain a harddrive check program. Invoking "wine seatoold_en.exe" works, but when the floppy should be written, an error occurs "insert 1.44 MB...click retry". I tried to mount a DOS

On Thu, Feb 2, 2017 at 1:26 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Hi all, > > > > I have observed a problem where, under legacy BIOS booting mode on the > > DL360g9, memdisk fails to execute. The same mechanism works fine on the > > DL360g8. The system displays the below on the console and ceases to > > respond and must be

I tried to use memdisk 2.06 to boot a floppy image on my notebook which doesn't have a floppy drive. The boot failed, because the bootstrap code tried to reset the floppy drive (int13, ah=00). Memdisk passes reset calls on to the original int13 handler, which returns failure, because there is no floppy drive to reset (#1). Also i noted that some boot records (notably some created by