search for: rubbishs

Dear all, I cannot seem to get the R functions step or stepAIC to perform forward or stepwise regression as I expect. I have enclosed the example data in a dataframe at the end of this mail. Note rubbish is and rnorm(17) variable which I have deliberately added to the data to test the stepwise procedure. I have used wateruse.lm<-lm(waterusage~.,data=wateruse) # Fit full model

Hi there, I've been trying to play The Elder Scrolls: Oblivion under Linux. But under WINE performance is horrible. 640 x 480 minimum settings, and I'm getting about 4 FPS. The game runes maxed out at 1680 x 1050 with 4xAA all settings to maximum smooth on Windows. Wine 1.1.6 Ubuntu 8.10 Intrepid Ibex fglrx 8.10 ATi Radeon 3870. I appreciate any responses. Btw Direct Rendering is

Hi, I just tried to register for the wine forum, and noticed several really annoying things about the process: 1. The "Register" link is kind of hard to find. Normally it is just next to the "Forgot password" link. 2. No SSL. 3. You emailed me my password! Argh! This is a terrible idea for obvious reasons, and also implies: 4. Passwords aren't stored hashed. Seriously.

David Hildenbrand <david at redhat.com> writes: > Some devices/drivers that add memory via add_memory() and friends (e.g., > dax/kmem, but also virtio-mem in the future) don't want to create entries > in /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the

David Hildenbrand <david at redhat.com> writes: > Some devices/drivers that add memory via add_memory() and friends (e.g., > dax/kmem, but also virtio-mem in the future) don't want to create entries > in /sys/firmware/memmap/ - primarily to hinder kexec from adding this > memory to the boot memmap of the kexec kernel. > > In fact, such memory is never exposed via the

hi guys I have rather a large set of Seagate's SAS ST32000444SS, over a hundred - experience I'm having from those in conjunction with their tech support is abysmal. I'm trying to update firmware of these drives and nothing works, including tech support. ... and I cannot help but wonder - is just me who is so unlucky and getting very, very poor support(taking naturally only of

Full_Name: George Russell Version: 2.10.0, 2.11.0 (2009-12-13 r50716) OS: Windows Submission from: (NULL) (217.111.3.131) R trace: -- cut here -- > v <- integer(0) > v[[1]] <- v > v [1] 20522144 > v <- numeric(0) > v[[1]] <- v > v [1] 4.254131e-314 > sessionInfo() R version 2.10.0 (2009-10-26) i386-pc-mingw32 locale: [1] LC_COLLATE=German_Germany.1252

In building a function for a package, I'd like to set the defaults in a control list, e.g., makeg<-function(parameters, eps = 1.0e-7, control=list(showwork=TRUE, rubbish=1.0e+101)){ etc. } This does not provide showwork or rubbish within the function if control() is not fully specified. Copying others, I've previously set the control defaults within the function then matched

Not all the fields of struct stat are actually filled by us. This caused rubbish to appear in the microseconds fields, which were then used as base when changing atime/ctime (with e.g. touch), triggering EINVAL by futimens/utimensat when those rubbish values were out of the range allowed for microseconds. --- src/fuse.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/fuse.c b/src/fuse.c

David Hildenbrand <david at redhat.com> writes: > On 30.04.20 17:38, Eric W. Biederman wrote: >> David Hildenbrand <david at redhat.com> writes: >> >>> Some devices/drivers that add memory via add_memory() and friends (e.g., >>> dax/kmem, but also virtio-mem in the future) don't want to create entries >>> in /sys/firmware/memmap/ -

David Hildenbrand <david at redhat.com> writes: > On 30.04.20 17:38, Eric W. Biederman wrote: >> David Hildenbrand <david at redhat.com> writes: >> >>> Some devices/drivers that add memory via add_memory() and friends (e.g., >>> dax/kmem, but also virtio-mem in the future) don't want to create entries >>> in /sys/firmware/memmap/ -

Try adding a star at the end. eg : /home/bob/.mozilla/firefox/* If this is still not excluding as you expect then please let me know. On 16/04/2009, at 8:19 AM, Robert Parker wrote: > Reading and re-reading the man page has got me nowhere with this issue > and searching your site on '--exclude-from' got me to the same place. > > Here is the script I am using: >

On 26/09/18 20:19, Mauricio Tavares wrote: > If ti makes you feel any better, I am not having stellar service from > WD's support. In fact, they act like they never received the HD I sent > for RMA whose tracking number says they did 10 days ago. > > On Wed, Sep 26, 2018 at 2:16 PM, lejeczek via CentOS <centos at centos.org> wrote: >> hi guys >> >> I have

On 30/05/2023 09:57, Marco Gaiarin via samba wrote: > Mandi! Rowland Penny via samba > In chel di` si favelave... > >>> Probably, but first, I will install Ubuntu 22.04 with that god awful GDM >>> and see if I can get that to work. > > As just stated, i really doubt it is gnome or GDM the fault... > > >> I give up with Ubuntu > > What

Hi, Is anybody in the UK using Telewest as a PRI Telco provider? Are you sending them caller ID? I've been told by Telewest that:- 1. Oftel doesn't allow them to accept caller ID (this is rubbish, and I replied pointing out where in the link to Oftel that they sent me it was stated. We need Type 2 caller ID) 2. Telewest can't do this. (this is rubbish, I'm certain

Reading and re-reading the man page has got me nowhere with this issue and searching your site on '--exclude-from' got me to the same place. Here is the script I am using: #################################### #/bin/bash suffix=`date +%Y%m%d` echo Suffix is "$suffix" fromdir=/home/bob/ echo Source dir is "$fromdir" todir="$maxtor6"BackupOfHome

Dear All, I'm trying (and failing) to implement a shared mailbox folder. My goal is to share the inbox of a user 'invoices' to a test user 'rubbish'. My ACLs appear to be correct: # doveadm acl get -u invoices inbox ID Global Rights user=rubbish create delete expunge insert lookup post read write write-deleted write-seen The shared-dict is

Hi Arushi, > %tmp63 = call %struct.TypHeader* (...)* bitcast (%struct.TypHeader* > (%struct.TypHeader*, i64, i64)* @Cyclotomic to %struct.TypHeader* > (...)*)(%struct.TypHeader* %tmp62, i64 %tmp24, i32 1) nounwind, !dbg !907 ; > <%struct.TypHeader*> [#uses=1] > > the 3rd parameter is now used in an srem statement. How do we know what value is > used? Does this use

...cl_shared_dict: file:/%Lh/%Ld/shared-mailboxes.db quota: maildir quota_rule: *:storage=10M expire: * 7 expire_dict: proxy::expire auth_socket_path: /var/run/dovecot/auth-master sieve: /opt/nsmail/data/sieve/%Ld/%Ln/.dovecot.sieve autocreate: trash autosubscribe: trash autocreate2: rubbishs autosubscribe2: rubbishs autocreate3: &XfJT0ZABkK5O9g- autosubscribe3: &XfJT0ZABkK5O9g- autocreate4: &g0l6Pw- autosubscribe4: &g0l6Pw- autocreate5: decrypt dict: expire: mysql:/etc/dovecot-expire.conf THANKS YINGYING

%tmp63 = call %struct.TypHeader* (...)* bitcast (%struct.TypHeader* (%struct.TypHeader*, i64, i64)* @Cyclotomic to %struct.TypHeader* (...)*)(%struct.TypHeader* %tmp62, i64 %tmp24, i32 1) nounwind, !dbg !907 ; <%struct.TypHeader*> [#uses=1] the 3rd parameter is now used in an srem statement. How do we know what value is used? Does this use decide whether the value is sign extended or zero