similar to: extlinux and btrfs

With this we try to detect if the endianess switch works and assume LE if not. Suggested by Ben. Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") --- .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c

Dear R and S People: I have run across something very strange. Here is a function that I wrote for R: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y){n2 - pmax(x,y)})) return(a) } and here is the R output: > y1 [1] 9 8 7 3 6 > source("boot1.R") > boot1(y=y1,p=4) [,1] [,2]

From: Gene Cumm <gene.cumm at gmail.com> alias.c: A simple COM32 module that allows the creation of an alias within the config for SYSLINUX, etc. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- If, for example, you had two labels that only differed by the length of the label (a short name) or additional APPENDd parameters, this would reduce the amount of copies of the same

I seem to have partitions on two different disks with the same UUID: [tim at helen ~]$ sudo blkid /dev/sda2 /dev/sda2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" [tim at helen ~]$ sudo blkid /dev/sdb2 /dev/sdb2: LABEL="/boot1" UUID="5bbc8e95-6108-41f5-bc0e-5b5f8df5ce03" TYPE="ext3" This is

Hi,there, I am using R package "boot" to bootstrap. I have one question here: does anybody possibly know how the boot package generates the "indices" which is used in the statistic function? I thought "indices = sample(data, replace=TRUE)", but when I replaced "indices" with this command and used "boot", I got different results. Specifically,

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

Hiya, Just joined the list and started using pxelinux. Very cool product!!! I searched the, 8+ MB, archives looking for multicast entries. I know that the pxelinux page says that the support of mtftp in pxelinux isn't in the works but I'm not sure how old/relavant that comment is. I have noticied some comments from H.P.A. describing the difficulties in doing MTFTP. Are there any plans to

I was under the impression that the value of /etc/machine-id was unqiue for every OS installation on a system. This seems to be the case on real hardware. That is, if I install Fedora 19, Fedora 20, and Fedora-rawhide on a system, they will each have a different value for /etc/machine-id. This does not seem to be the case for qemy-kvm-libvirt virtual systems. SOmetimes they are different

this is strange to me but maybe not to y'all I use clamscan --exclude in other places but this certain one will not work... let me put up my fstab before I explain k: # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/ / ext3 defaults 1 1 LABEL=/boot1 /boot ext3 defaults 1 2 none

I did a clean install of centos4.2 and i noticed on boot up that my mount points had a "1" added to each. For example here is a snippet of my /etc/fstab: /1 ...... /boot1 ...... /var1 ..... of course just what is pertinent to the problem is listed?

Hi!!! I am trying to run a bootstrap but I have troubles. My code is as follows theta <- function(x){mean(x,)} boot1<-boot(x,theta,R=1000) Error in statistic(data, original, ...) : unused argument(s) (1:487) Any help is welcome Thanks [[alternative HTML version deleted]]

In my /etc/fstab here is just a snippet LABEL=/1 ....<rest of line> LABEL=/boot1 ....<rest of line> When i installed centOS-4.3 and it has appeared after starting to use any version of centOS4 was that the labels in my fstab were getting the "1" appended to each label... but if the all the labels for my partitions are appended with the "1" and i format and

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..17676c75a 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

Hi, Erin: A cleaner way is to pass "n2" to "outer" as a "..." argument, as in the following modification of your code: boot1 <- function(y,method="f",p=1) { n1 <- length(y) n2 <- n1*p n3 <- n2 - 1 a <- 0.5*(outer(1:n3,1:n3,function(x,y, n2.){n2. - pmax(x,y)}, n2.=n2)) return(a) } y1 <- c( 9, 8, 7, 3, 6) boot1(y=y1,p=4)

Fixes warnings on GPUs with smaller a smaller mmio region like vGPUs. Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 27 +++++++++++++++------------ 1 file changed, 15 insertions(+), 12 deletions(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 8ebbe1656..37589f365 100644 ---

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

v2: relax the checks a little Signed-off-by: Karol Herbst <kherbst at redhat.com> --- drm/nouveau/nvkm/engine/device/base.c | 26 +++++++++++++++++++++----- 1 file changed, 21 insertions(+), 5 deletions(-) diff --git a/drm/nouveau/nvkm/engine/device/base.c b/drm/nouveau/nvkm/engine/device/base.c index 37589f365..c732074bf 100644 --- a/drm/nouveau/nvkm/engine/device/base.c +++

On Tue, Oct 13, 2020 at 8:01 AM Karol Herbst <kherbst at redhat.com> wrote: > > With this we try to detect if the endianess switch works and assume LE if > not. Suggested by Ben. > > Fixes: 51c05340e407 ("drm/nouveau/device: detect if changing endianness failed") > --- > .../gpu/drm/nouveau/nvkm/engine/device/base.c | 39 ++++++++++++------- > 1 file

HI, i have updatete to 6.1-PRERELEASE and after the "installworld" step GRUB is unable to boot FreeBSD. After i did the installworld and rebooted the GRUB error was: 23 : Error while parsing number I have reinstalled the standard FreeBSD loader for now. Booting with a GRUB boot-floppy i am able to start either XP or Linux but trying to start FreeBSD the system just reboots, no