similar to: [klibc 14/43] Remove in-kernel nfsroot code

This patch removes support for use of NFS as a root filesystem from the kernel. It also updates the documentation to reflect this. b/Documentation/nfsroot.txt | 97 +++--- b/arch/arm/def-configs/a5k | 1 b/arch/arm/def-configs/adi_evb | 1 b/arch/arm/def-configs/adsbitsy | 1 b/arch/arm/def-configs/anakin | 1

The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=X" and "vers=X", with X being equal to either 2 or 3 (nfsmount does not support NFSv4 at present). If both

Commit-ID: c4b811a1e4647224ddc717fac59900d16d0e9d4d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c4b811a1e4647224ddc717fac59900d16d0e9d4d Author: Baptiste Jonglez <baptiste.jonglez at imag.fr> AuthorDate: Thu, 14 Sep 2017 09:22:21 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] nfsmount: support

linux-2.6 2ad780978b7c0c3e7877949f098cbd06e7c73839 cleaned up linux/nfsmount.h and thus a klibc build would produce this: > usr/kinit/nfsmount/mount.c:179: error: 'MNTPROC_MNT' undeclared (first use in this function) > usr/kinit/nfsmount/mount.c:179: error: (Each undeclared identifier is reported only once > usr/kinit/nfsmount/mount.c:179: error: for each function it appears

There is a conflict in glibc between <linux/in.h> and <netinet/in.h>: one defines protocols with an enum, the other does the same, but adds a self-define for every enumerated value. #define IPPROTO_IP IPPROTO_IP This means the two cannot be mixed, and since loads of include files refer to <netinet/in.h>, effectively <linux/in.h> cannot be used with glibc. Since

Hi all, I have a problem in that when I plot points that have a high degree of precision, some significant rounding seems to occur, resulting in uneccessary overlap of my points. Is there a way to specify the resolution or precision in plotting functions? Is there an underlying grid I have to modify somehow? Many Thanks, Jon -- Mares eat oats and does eat oats and little lambs eat ivy. A

On Do, 2015-01-22 at 10:10 +0100, Martin Mares wrote: > lspci -vxxx Attached is a dump of a virtio-net device (both verbose=2 and hex). cheers, Gerd -------------- next part -------------- 00:09.0 Ethernet controller: Red Hat, Inc Virtio network device Subsystem: Red Hat, Inc Virtio network device Physical Slot: 9 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

On Do, 2015-01-22 at 10:10 +0100, Martin Mares wrote: > lspci -vxxx Attached is a dump of a virtio-net device (both verbose=2 and hex). cheers, Gerd -------------- next part -------------- 00:09.0 Ethernet controller: Red Hat, Inc Virtio network device Subsystem: Red Hat, Inc Virtio network device Physical Slot: 9 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-

On Mi, 2015-01-21 at 15:57 +0100, Martin Mares wrote: > Hello! > > > virtio uses vendor-specific capabilities to specify the location of > > the virtio register ranges. The specification can be found here: > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > This patch adds support for decoding these

On Do, 2015-01-22 at 22:46 +0100, Martin Mares wrote: > > Attached is a dump of a virtio-net device (both verbose=2 and hex). > > Thanks! > > I have cleaned up the code a little, could you please check that > it still works for you? Works fine. cheers, Gerd

On Mi, 2015-01-21 at 15:57 +0100, Martin Mares wrote: > Hello! > > > virtio uses vendor-specific capabilities to specify the location of > > the virtio register ranges. The specification can be found here: > > > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > > > This patch adds support for decoding these

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

Hello! > virtio uses vendor-specific capabilities to specify the location of > the virtio register ranges. The specification can be found here: > > http://docs.oasis-open.org/virtio/virtio/v1.0/cs01/virtio-v1.0-cs01.html#x1-690004 > > This patch adds support for decoding these capabilities to lspci. I like the patch, except for a couple of details: (1) Please follow the

Dear all, I am having some problems trying to run a GLMM model with zero-inflation using the alpha version of glmmADMB (0.6.4) using R (2.13.1) in Windows and I would greatly appreciate some help. My count response variable (number of birds: count) fits a negative binomial distribution and the explanatory variables are both continuous and categorical (species= 17). The three random effects are

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

I started with Vivek's ELF bzImage patch from Oct last year, mashed it to apply to hpa's new setup/boot code. This patch does a couple of things, which would probably be better split into multiple patches: 1. Glue an ELF header onto the front of bzImage. This is a real ELF header at the front of the file. Breaks akpm's laptop, apparently, but it works for me. 2.

Hi,, I wud just like to inform that the previous issue of memdisk not booting compressed images still persists !! The release 2.05 that was supposed to fix this issue dint yet solve the problem !! Please, let me know if more info on the problem is required !! Bye, Jassi >From: syslinux-request at zytor.com >Reply-To: syslinux at zytor.com >To: syslinux at zytor.com >Subject:

Hello! I'm puzzled by the following problem. It occurs while trying to predict responses in a test-dataset using a linear model fitted with regFit from the rMetrics "fRegression"-package. All goes well when I call "predict" using the training dataset. However, a call using the test-dataset retuns an error message - telling me that the latter dataset provides variables