similar to: Unable to find linux kernel on ext4, filesystem-related root cause assumed

Displaying 20 results from an estimated 2000 matches similar to: "Unable to find linux kernel on ext4, filesystem-related root cause assumed"

2017 Oct 10
2
Unable to find linux kernel on ext4, filesystem-related root cause assumed
> On 10/10/17 12:28, Manuel Wagesreither via Syslinux wrote: > > Dear all, > > > > I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. > > Used versions: > > extlinux 6.03 > > QEMU emulator version
2017 Oct 10
0
Unable to find linux kernel on ext4, filesystem-related root cause assumed
On 10/10/17 12:28, Manuel Wagesreither via Syslinux wrote: > Dear all, > > I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. > > Unfortunately, I'm experiencing problems with the bootability of the produced image. When selecting
2017 Oct 11
0
Unable to find linux kernel on ext4, filesystem-related root cause assumed
Am Mi, 11. Okt 2017, um 01:34, schrieb Ady Ady via Syslinux: > > > On 10/10/17 12:28, Manuel Wagesreither via Syslinux wrote: > > > Dear all, > > > > > > I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. >
2013 Nov 21
0
[PATCH] FSUUID for ext2 filesystem
The ext2 filesystem supports volume UUID now. The FSUUID variable can be set to kernel command line. Patch is based on FSUUID for FAT patch. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- core/fs/ext2/ext2.c | 40 +++++++++++++++++++++++++++++++++++++++- core/fs/ext2/ext2_fs.h | 1 + 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/core/fs/ext2/ext2.c
2013 Nov 19
2
[PATCH] Add filesystem UUID to SYSAPPEND for FAT
Filesystem UUID shows the partition we boot kernel from. The kernel parameter has format like FSUUID=DA1A-0B2E. The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. The patch is based on 67aaaeeb228. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- com32/include/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c
2013 Nov 20
0
[PATCH] Add filesystem UUID to SYSAPPEND for FAT
On 11/19/2013 04:30 AM, Serj Kalichev wrote: > Filesystem UUID shows the partition we boot kernel from. > The kernel parameter has format like FSUUID=DA1A-0B2E. > The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. > The patch is based on 67aaaeeb228. > > Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> Nice. It would be good to get a patch for ext2
2012 Aug 31
1
[PATCH V1] NEW API:ext:mke2fs
New api mke2fs for full configuration of filesystem. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/ext2.c | 452 +++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 18 ++ gobject/Makefile.inc | 6 +- src/MAX_PROC_NR | 2 +- 4 files changed, 475 insertions(+), 3 deletions(-) diff --git
2017 Oct 12
0
Unable to find linux kernel on ext4, filesystem-related root cause assumed
Hi, On Wed, 11 Oct 2017 18:29:42 +0000 Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Relevant developer(s) in Debian have already known about this ext4 > matter for quite some time, but they consciously choose not to add > information in the relevant bug report in Debian's bug tracker. They > also actively choose not to implement any workaround nor provide any
2014 Jan 05
2
Syslinux: Pending patches
Searching threads back to 2013-07-01 (date of last message on thread), I've come up with the folloowing: -Needs review for inclusion: 12/26 Init cache once 11/27 efi PE header set 11/21 FSUUID for ext2 filesystem 10/15 Upgrade to Lua 5.2.2, add filesystem module and get_key binding (21) 09/23 com32: hdt: fix memory leak 10/3/12-12/16 4k sector support 10/18 MultiFS from MultiDisk 10/07 Lua
2017 Oct 11
2
Unable to find linux kernel on ext4, filesystem-related root cause assumed
> I found the wiki page you were referring to [1] and followed the > mentioned advise, that is, I created the ext4 filesystem without the > '64bit' feature. It worked! Booting is possible now. > > Unfortunately I did not find that wiki page when I was conducting my > own research. There were some locations were I suspected this kind > of information (namely the
2014 Feb 03
0
xorriso or genisoimage syntax assistance
Hi, > If any of you have time, let me know if it > looks wrong or if I missed anything anyone suggested. Nitpicking: Consider whether to use -r instead of -R, i.e. whether to make up ownership and permissions for publishing, or whether to preserve the ownership and permission as in ISO_root. The latter (-R) is more suitable for backup purposes, or if you have reason to have multiple
2015 Jan 25
0
release cycle 6.04
X-Original-In-Reply-To: <CAD0Rxe=5uLCWQ+jfj1J6zepDzqx0vAiBREiwiKOih59MKgBDHg at mail.gmail.com> X-Previous: http://www.syslinux.org/archives/2015-January/023070.html On Mon, Jan 05, 2015 at 08:59:57PM -0500, Gene Cumm wrote: > On Sat, Jan 3, 2015 at 1:21 PM, Geert Stappers wrote: > > On Thu, Jan 01, 2015 at 09:48:16AM -0500, Gene Cumm wrote: > > >> I'm planning on
2015 Jul 02
1
boot... round 2
On 01.07.2015 17:46, Ady via Syslinux wrote: > >> On 01.07.2015 12:10, Gene Cumm wrote: >>> On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> >>>> To remind you once again. >>>> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >>>> This relates specifically to the use of the
2017 Nov 17
2
HTML documentation is not in the expected location
Since I have updated my Linux system, and consequently re-installed R, I am unable to see HTML documentation which I used to access via a web browser. To be more specific, my R installation is declared to be here: > R RHOME /usr/local/lib/R However, if I look at a location such as /usr/local/lib/R/library/base/html this contains only two entries File: 00Index.html File: R.css
2017 Nov 17
0
HTML documentation is not in the expected location
On 17/11/2017 10:47 AM, Adelchi Azzalini wrote: > Since I have updated my Linux system, and consequently re-installed R, I > am unable to see HTML documentation which I used to access via a web > browser. To be more specific, my R installation is declared to be here: > > > R RHOME > /usr/local/lib/R > > However, if I look at a location such as >
2002 Mar 06
1
Possible bug in 2.2.3a source/script/installbin.sh (with patch)
Hi all, the file samba-2.2.3a/source/script/installbin.sh has a rather odd blindspot. It doesn't honor the --with-privatedir= option to ./configure it just blindly uses $BASEDIR/private instead. I think the fix would be:- a) move directory creation out of installbin.sh altogehter (after all what's the installdirs: target for in the Makefile?) OR b) add an extra parameter
2003 Mar 19
1
Patch for relocatable installs
I remember seeing a patch here a long while back that I thought was going to be committed for making the install relocatable (i.e. allowing for a DESTDIR to be specified during a "make install"). I can't find it, and I'm not sure I am remembering correctly, anyway, so here is a shot at it. Tested both the install and uninstall, run as "make install
2002 Jun 21
1
samba-2.2.5 -- a minor "make install" problem and 2 suggestions
Hi, I would like to ask you to consider the attached patch for inclusion into the next samba release. The patch addresses the following three points: 1. 'make install' with VPATH fails at one point ( $(srcdir)/script/findsmb vs. script/findsmb ) 2. support for 'make DESTDIR=<somewhere> install' (e.g. to build a binary package) 3. support for 'configure
2001 Apr 07
1
samba on NetBSD - some patches
Hi, We (NetBSD) just received a bug report that smbclient's mput command usees find(1) with a non-standard option "-maxdepth". This was replaced with a simple call to ls(1). As I don't know how many of the patches from out Packages Collection were sent to you in the past, I'm simply sending you all our patches - please include any you like in future samba releases! BTW,
2020 Apr 07
4
Join new DC to domain - advice to upgrade Samba 4.
Hi Rowland, thanks for your email. The working DC was installed around 2 years ago. It is the reason to stick in Stretch. But if I can upgrade the working DC to Buster and Samba 4.9.5 without any problem, it is OK to me. I'm not a Samba expert. How can I verify my database? Can you point me to some link, tutorial, etc? I have used the samba-tool dbcheck (with and without --cross-ncs), is