search for: f29

...takes about two seconds(!) to get the record and the 20 associated records from the "flowers" table. With a direct or ODBC connection, I guess you get that data in about 50 ms. Here is the tcpdump that shows all the round-trips when fetching and displaying the data. 20:55:09.128686 IP f29.attiksystem.ch.8924 > j20.attiksystem.ch.9000: S 2403473258:2403473258(0) win 65535 <mss 1444,nop,nop,sackOK> 20:55:09.128734 IP j20.attiksystem.ch.9000 > f29.attiksystem.ch.8924: S 1607928261:1607928261(0) ack 2403473259 win 65535 <mss 1460,sackOK,eol> 20:55:09.148167 IP f29.atti...

...I have a dataframe (~8000 observations, registerdata) with four columns: id, dg1, dg2 and date(YYYY-MM-DD) of interest: id;dg1;dg2;date; 1;F28;;1997-11-04; 1;F20;F702;1998-11-09; 1;F20;;1997-12-03; 1;F208;;2001-03-18; 2;F32;;1999-03-07; 2;F29;F32;2000-01-06; 2;F32;;2003-07-05; 2;F323;F2800;2000-02-05; ... I would like o have two additional columns: 1. “countF20”: a “countvariable” that shows which in order (by date) the id has if it fulfils the following logical expression: dg1 = F20* OR dg2 = F2...

...%vreg247, %vreg248; AFGR64:%vreg261,%vreg247,%vreg248 4512B ADJCALLSTACKDOWN 16, %SP<imp-def>, %SP<imp-use> 4528B %D6<def> = COPY %vreg243; AFGR64:%vreg243 4544B JAL <ga:@sin>, <regmask %FP %RA %D10 %D11 %D12 %D13 %D14 %D15 %F20 %F21 %F22 %F23 %F24 %F25 %F26 %F27 %F28 %F29 %F30 %F31 %S0 %S1 %S2 %S3 %S4 %S5 %S6 %S7 >, %RA<imp-def,dead>, %D6<imp-use,kill>, %SP<imp-def>, %D0<imp-def> 4560B ADJCALLSTACKUP 16, 0, %SP<imp-def>, %SP<imp-use> 4576B %vreg262<def> = COPY %D0<kill>; AFGR64:%vreg262 4592B %vreg263<def>...

...Hi all, >> >> >> I still use the following kickstart partition scheme for C7 installations >> (via virt-install): >> Briefly, fixed size for /root and /boot, and the rest is filled up for >> /srv. >> >> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work >> with Fedora29 (EL8). I get a "device is too small for new format" error. >> Any hints? >> >> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >> /boot --fstype="ext4" --ondisk=sda --s...

Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype=...

To reduce memory consumption clobbered registers are handled with RegisterMask machine operands which contain a bitset of all registers clobbered. - Matthias > On Jul 29, 2015, at 3:00 PM, Daniel Sanders <daniel.sanders at imgtec.com> wrote: > > I believe I've identified the problem with almabench but I haven't found the root cause in the compiler yet. > > The

...> > > Me neither. Looks like that message is either coming from spice or usbredir. > CCing spice list (and changed the subject to make it more clear) USB Redirection permissions are set by the /usr/libexec/spice-gtk-x86_64/spice-client-glib-usb-acl-helper SUID binary. I'm running f29 these days, but after downgrading the spice-gtk package to spice-gtk-0.35-1.fc28, I haven't been able to reproduce this issue. What version of the package is being used? And are you sure you don't have any non-fedora versions of spice-gtk anywhere on your system? Christophe

Hi there I am using libvirt+lxc on fedora I just upgraded a couple boxes from f29 to f31 i am running into rather puzzling glitches on one of the boxes, and am having a hard time trying to figure what exactly is going wrong symptom being that on the faulty box, my 3 containers startup correctly, but all of them stop after some random time shortly after (approx. in the 5-10 min...

On upgrading my F28 to F29, I've found that R-core and a number of R packages: R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi R-stringr R-yaml are installed, although I only ever install R from source and always keep my Rs locally. So I don't use Fedora R rpms, but these were installed...

...d sit on old crap which has nothing in common with my workstations for years ----------------- that means two major upgrades per year but that scales far better than every few years have all the changes of 7-10 releases at once given that all servers where installed in 2008 with F9 and are now at F29 without re-install and all dist-upgrades where "yum/dnf distro-sync" with no downtimes longer than a ordinary kernel update it's compareable with a rolling release but without breaking changes for 6 months and so you can override specific packages with own builds, for example PHP/MyS...

...9.910160e-07 -1.808292e-05 week3 2.735904e-05 -1.151881e-05 7.413345e-07 -1.532306e-05 week4 4.880167e-04 -7.139705e-05 1.360150e-05 -2.548684e-04 Residual Deviance: 143.6754 AIC: 257.6754 -------------- next part -------------- > nose126s2.mu <- multinom(Spoilage ~ F25 + F26 + F27 + F28 + F29 + F30 + F31+ F32 + F33 + F34 + F35+ F36 + F37 + F38 + F39+ F40 + F41 + F42 +F43 + F44 + F45 + F46 + F47 + F48 + F49 + F50 + F51 + F52 + F53 + F54 + F55 + F56 + F57 + F58 + F59 + F60 + F61 + F62 + F63 + F64 + F65 + F66 + F67 + F68 + F69 + F70 + F71 + F72 + F73 + F74 + F75 + F76 + F77 + F78 + F79 + F...

...l, > > > > > > I still use the following kickstart partition scheme for C7 installations > > (via virt-install): > > Briefly, fixed size for /root and /boot, and the rest is filled up for > > /srv. > > > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > > with Fedora29 (EL8). I get a "device is too small for new format" error. > > Any hints? > > > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > > /boot --fstype="ext4" --ondisk=sda...

...t release with precisely those settings. > > I'm happy to pass along your comments in a bugzilla for Fedora and > discourage their use of this unsupported feature. The maintainers are Samba Team members, they know the situation very well. https://docs.fedoraproject.org/en-US/fedora/f29/release-notes/sysadmin/File_Servers/ The problem is the gap between Fedora, and even un-official packages for RHEL/CentOS, as while few servers run on Fedora, people will use these packages as an AD DC, hit the bugs in the MIT KDC, then come here about it. If you only want to do a pure backport...

...problem with the USB connection failing. My old UPS (EATON Ellipse MAX 1500) works just fine with the latest f30. Both devices identify as ID 0463:ffff MGE UPS Systems UPS To narrow the focus I booted recent live CDs on a PC that has no other USB devices attached beyond the keyboard and mouse. f29 Fedora-Workstation-Live-x86_64-29-1.2.iso === $ uname -a Linux localhost-live 4.18.16-300.fc29.x86_64 #1 SMP Sat Oct 20 23:24:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [Fri Jul 19 09:44:58 2019] usb 6-2: new full-speed USB device number 2 using uhci_hcd [Fri Jul 19 09:44:59 2019] usb 6-2: New USB...

On Sat, 10 Nov 2018, I?aki Ucar wrote: > On Sat, 10 Nov 2018 at 15:17, Roger Bivand <Roger.Bivand at nhh.no> wrote: >> >> On upgrading my F28 to F29, I've found that R-core and a number of R >> packages: >> >> R-evaluate R-glue R-highr R-knitr R-magrittr R-markdown R-mime R-stringi >> R-stringr R-yaml >> >> are installed, although I only ever install R from source and always keep >> my Rs locally. S...

On Sat, October 20, 2018 8:23 am, Matthew Miller wrote: > On Thu, Oct 18, 2018 at 05:52:12PM -0700, Japheth Cleaver wrote: >> The wider EL community is trapped between a rock and a hard place >> somewhat. If you try to direct Fedora into the needs of EL users, >> you stand a good chance of getting told to pound stand, and that EL >> is getting in the way of bleeding-edge

On Fri, May 24, 2019 at 03:45:31PM +0200, L.P.H. van Belle via samba (samba at lists.samba.org) wrote: > You should have looked before upgrading. ... > If its an AD-DC. > instructions: https://lists.samba.org/mailman/options/samba Yes, very true! I really have "upgrading fatigue", this is my tenths bloody odd machine I am moving from 6.x to 7.x (all of those quite

On 30/10/18 20:06, Eddie G. O'Connor Jr. wrote: > > On 10/30/18 2:46 AM, Simon Matter wrote: >>> On 10/29/18 1:55 AM, Simon Matter wrote: >>>> To me it seems like, if they are smart, they will try to push IBM >>>> POWER >>>> and RedHat Linux together to establish real competition in the >>>> hardware >>>> market again

...eon Fauster via CentOS wrote: > Hi all, > > > I still use the following kickstart partition scheme for C7 installations > (via virt-install): > Briefly, fixed size for /root and /boot, and the rest is filled up for > /srv. > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > with Fedora29 (EL8). I get a "device is too small for new format" error. > Any hints? > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT...

...> >>> I still use the following kickstart partition scheme for C7 installations >>> (via virt-install): >>> Briefly, fixed size for /root and /boot, and the rest is filled up for >>> /srv. >>> >>> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work >>> with Fedora29 (EL8). I get a "device is too small for new format" error. >>> Any hints? >>> >>> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >>> /boot --fstype="ext4&quo...