similar to: Can USBstikA boot USBstkB ?!

> I don't think that syslinux be in concern here. If I understand well > Slackware is installed on a hard disk partition that you want to access > through the USB-adaptor to IDE/SATA. No. I'm not married to Slak. It's important to distinguish between verbatim/pasteable and what the old-writer merely thinks/remembers. I want to be able to boot ANY installation/partition as I

> ]You seem to be assuming that changing from a direct SATA and IDE > ] connections to some USB adapter would have no impact on how the > ] respective HDDs are recognized/detected by the BIOS. > > ] You seem to be > ] assuming that the BIOS from 2 different PCs/Laptops would recognize all > ] your devices in the same exact way and that there would be no changes > ] in

AIM: from <isolinux> on USBstikA, boot Debian7 installation on USBstikB. EXISTING STATE: USBstikA is TinyCore64bit booter, with:- /boot/isolinux/* 61312 Oct 26 2016 menu.c32 24576 Oct 26 2016 isolinux.bin 2069 Nov 22 01:24 isolinux.cfg ... USBstikB-partition3: Currently boots a 32bit installation, via GRUB using the entry:----- menuentry 'Debian GNU/Linux, with Linux

PS. Since I've now only got a laptop, I mostly use TinyCore linux; which is also sysylinx booted; and makes provision for *THE SLOW REACTION TIME OF SOME USB DEVICES*; which may be the subtle cause of my problem in trying to boot a second USBdevice [other than the <boot device>]. WDYS? On 6/14/17, eas lab <lab.eas at gmail.com> wrote: >> I don't think that syslinux be

> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions. How exactly were you editing (something)? Do you mean that you somehow changed some boot command from the Syslinux boot prompt during boot? In that case, which

On Sat, Dec 2, 2017 at 10:35 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: > AIM: from <isolinux> on USBstikA, > boot Debian7 installation on USBstikB. I thought we answered this but perhaps it's not the "Can I boot ISOLINUX/SYSLINUX from USB-A and boot to USB-B" whose short answer is "No" but long answer is "It depends on the BIOS/CSM

> I don't think that syslinux be in concern here. That's why I pasted the `ls -l` of the directory: to show that the previous working USBstik was *SYSLINUX* based.

[quoted lines from Ady Ady]: > At this time, Syslinux by itself cannot boot files located on a > different filesystem volume. > Using chain.c32, you can load a boot sector (MBR or VBR) located on > another device. Since the list of files located in your boot stick did > not include chain.c32, my assumption (and not only mine, if you > carefully read some of the prior

]You seem to be assuming that changing from a direct SATA and IDE ] connections to some USB adapter would have no impact on how the ] respective HDDs are recognized/detected by the BIOS. ] You seem to be ] assuming that the BIOS from 2 different PCs/Laptops would recognize all ] your devices in the same exact way and that there would be no changes ] in behavior or in supported features by the

Amazing how zillions of us victims tolerate web-based gmail ? On 12/10/17, eas lab <lab.eas at gmail.com> wrote: > Gene Cumm wrote:- >>TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >>USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >>version that you can use the "guid" or "label" options to auto-detect

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ? But once the USBsyslinux takes over, has IT also got a USB driver? Since my MotherBoard & 2009 Slackware built USBstik syslinux booter were stolen I bought a <WinTel> laptop and USBextender to access my old IDE & SATA disks. With WinTel's new arrangement of not allowing the tail of the

On Mon, May 1, 2017 at 7:45 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: >>Do you mean boot SYSLINUX from stik-A but then load files like a >>kernel/initrd from stikB:partition5? It's possible but only from a >>development version of Syslinux that has the multifs patch merged. > > Yes: before my x86MotherBoard & <syslinux>USBstik were stolen,

I've been using linux:TC from a USBstik in order to not break the M$ capability, as previously always happened. Since TC runs in RAM, it has many extra problems; like reinstalling all the apps and your private settings at each boot. The sample isolinux.cfg which I've been emailed by the oficianado is very unfamiliar and worrying. Where is the official syntax ? -- Without knowing if/how

When a USBstiked-syslinux starts, it's the PC's firmare that's reading the USB ?. But once the USBsyslinux takes over, has IT also got a USB driver? So that USBsyslinux can install a different USBstik/partition? Ie. boot with stikA to install & run stikB:partition5 ? ------------ Is the following sound logic? > Do zero out the partition table first so you don't

Hello all, i have already had a discussion on the software raid mailinglist and i want to switch to this one :) I am having a really strange problem with my md0 device running centos7. after a new start of my server the md0 was gone. now after trying to find the problem i detected the following: Booting any installed kernel gives me NO md0 device. (ls /dev/md* doesnt give anything). a 'cat

Hi all, This is the third fresh install of CentOS 7 1708 the last two months that won't boot after a regular "yum update" just after the fresh install has finished. I've never had this problem before, it has just worked. The installs are on OEM's that have previously run CentOS 6.9 x64. Am I missing something here? -- BW, Sorin

Everyone, Is there a way to manually assign usb drives to a specified device label. Is there a way to force two usb drives to be labeled as /dev/sdc and /dev/sdd? I decided to build an archive server for the purpose of backing up other fedora/centos desktops at the office. I built a machine and have installed Centos 7.3 on it with all updates current. I also purchased a 3.0 usb sata drive

I've started updating systems to CentOS 7.6, and so far I have one failure. This system has two peculiarities which might have triggered the problem. The first is that one of the software RAID arrays on this system is degraded. While troubleshooting the problem, I saw similar error messages mentioned in bug reports indicating that sGNU/Linux ystems would not boot with degraded software

The following patch attempts to implement sparsification of LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS block device with its mapped name. Also, --allow-discards was added by default to luks_open(). There are several potential issues that I can think of: 1) If and entire device is encrypted (not just one of more partitions), the lsblk trick might not work. 2) The