search for: dkuug

...l object returned by boost::bind. The operator() of that object has the following signature: template<class Arg1> .... operator()(Arg& a1) and since result of *it is considered to be rvalue it can't be accepted by this operator. The complete discussion is in http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2002/n1385.htm I'd suggest to apply the following patch which makes operator* return reference to pointer. It makes my code compile and the rest of LLVM compiles too. Comments? - Volodya -------------- next part -------------- A non-text attachment was s...

...e blocks may have been reused unfortunately means that there may be errors in the salvaged files. So check them afterwards. The code is alpha and has only been tested on a Linux i386 system Salvage is an addition to the debugfs program in the e2progs package by Ted Ts'o. Download: http://www.dkuug.dk/keld/e2fsprogs-1.38-ks1.tar.gz. Then follow INSTALL instructions. Author: Keld Simonsen, keld at dkuug.dk

On Fri, 23 Apr 2004, Vladimir Prus wrote: > and since result of *it is considered to be rvalue it can't be accepted by > this operator. The complete discussion is in > > http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2002/n1385.htm > > I'd suggest to apply the following patch which makes operator* return > reference to pointer. It makes my code compile and the rest of LLVM compiles > too. Comments? Hrm, I'm not sure about this at all. In particular ilists have...

Having just spent a day trying to recover a deleted ext3 file for a friend, I'm wondering about this way of maintining undelete information in ext3, like is done for ext2: The last step in the deletion process would be to put back the (previously zeroed) block pointers. Since it gets logged to the journal, I _think_ that this should be safe. The worst that would happen is that, if the plug

Hello, We have run and stopped by chance command "fsck -y" on one of our raid disks (with ext3 file system). After that we have found that SOME files disappeared (they are not seen in the directories where they have been before). The data are extremely important and contain a lot of programs, scripts for some data analysis and very hard to recover by hands. I have run ''fsck

Hi I have a problem with lm and predict I have us [1] 2789.53 3128.43 3255.03 3536.68 3933.18 4220.25 4462.83 4739.48 [9] 5103.75 5484.35 5803.08 5995.93 6337.75 6657.40 7072.23 7397.65 [17] 7816.83 8304.33 8746.98 9268.43 9816.98 10127.95 10469.60 10960.75 [25] 11685.93 12433.93 13194.70 13843.83 us.p [1] 227.62 229.92 232.13 234.25 236.31 238.42 240.59 242.75 244.97

I have a damaged Ext3 filesystem which fsck has not been able to recover. If I try to mount it, I get a message like this in dmesg: EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already cleared for block 2370866 If I try fsck on it, I get a series of messages like this: Inode bitmap for group 0 is not in group. (block 0) Relocate<y>? Up to group 95. Some say

...2, 2002 Helsinki, Finland Information regarding The fourth Nordic EurOpen/USENIX Conference, to be held in Helsinki, Finland, February 18-22, 2002. A Conference organised by EurOpen.SE ? The Swedish Association of Unix Users, and affiliate of USENIX, The Advanced Computing Systems Association and DKUUG the Danish UNIX-Systems User Group, NUUG Norwegian UNIX User Group and FUUG The Finnish UNIX User Group. Important Dates --------------- Extended abstracts due September 7, 2001 Notification of acceptance October 12, 2001 Final papers due December 7, 2001 Authors are invited to submit a one page...

On May 27, 2008, at 2:01 PM, Dale Johannesen wrote: > On May 27, 2008, at 1:40 PM, Mike Stump wrote: >> >> From n2461: >> >>> 8 The insert members shall not affect the validity of iterators and >>> references to the container, and the erase members shall invalidate >>> only iterators and references to the erased elements. >> >> Pretty

https://bugzilla.mindrot.org/show_bug.cgi?id=1501 Summary: p_read, p_send not intialized Classification: Unclassified Product: Portable OpenSSH Version: 5.0p1 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org

We are running a benchmark that does single threaded 512 KB writes to a LUN on a CLARiiON storage array. The dual Xeon host (Dell 2650) with 4 GB of memory runs RHEL 4U3 We measured the write bandwidth for writes to the block device corresponding to the lun (e.g. /dev/sdb), a file in an ext2 filesystem and to a file in an ext3 file system. Write b/w for 512 KB writes Block device 312 MBps Ext2

...to me right now, but here is what I found: Indeed, all the examples I could find where using restrict for all pointers and where not covering the case when only one had the restrict keyword. However, I found this: "Rationale for International Standard—Programming Languages—C" http://std.dkuug.dk/JTC1/SC22/WG14/www/C99RationaleV5.10.pdf (page 82) "Objects referenced through a restrict-qualified pointer have a special association with that pointer. All references to that object must directly or indirectly use the value of this pointer. In the absence of this qualifier, other pointer...

Chris Lattner wrote: > On Fri, 23 Apr 2004, Vladimir Prus wrote: > > and since result of *it is considered to be rvalue it can't be accepted > > by this operator. The complete discussion is in > > > > http://std.dkuug.dk/jtc1/sc22/wg21/docs/papers/2002/n1385.htm > > > > I'd suggest to apply the following patch which makes operator* return > > reference to pointer. It makes my code compile and the rest of LLVM > > compiles too. Comments? > > Hrm, I'm not sure about this at al...

Hi I have written a small introduction to newbies in Danish on ssh and friends. Now some people are questioning my advice and I think they have a point. I am advocating people to use DSA-keys and a config file with this: Protocol 2 ForwardAgent yes ForwardX11 yes Compression yes CompressionLevel 9 and running ssh-agent and ssh-add, and then loggin in without giving keys. One

Hi I am looking for a compressed ext3 file system, for a read-only purpose. The idea is that I would like to make a live-cd that is fast to install. The install should be almost just a raw copy of what is on the cd, uncompressed. In that way I should be able to make an install of a full Linux system of say 3 GB in under 2 minutes. The fs type I would like to unpack is ext3 - but other fs types

Hi! I had problem yesterday with e2fsck. It reported a bad superblock. I then tried to use one of the other superblocks. To no avail. Then later I remembered that I had switched the fs type to xfs. Maybe e2fsck could recognize other common fs types, and report this instead? best regards keld

For my rsync daemon, I would like it to log in a format that I could run some stats on, eg by webalizer that I use for http and ftp transfers. Is that doable? best regards keld

Hi I run a mirror service where for gentoo I run rsync as a daemon. Currently the daemon runs root to get the 873 port opened. And when transfers then run, they run as nobody. I would like the rsync daemon to connect to 873 (as root) then possibly do a chroot and then run always as something else than root (maybe nobody). It this advisable? Is it possible? best regards keld

I often get the message: EXT2-fs warning (device hda6): ext2_fill_super: mounting ext3 filesystem as ext2 I have googled for a reason and a way to solve this - but not found something I could use. Maybe somebody here konws what to do? best regards keld

Hi! I am using rsync succesfully to maintain my mirrors. I have one problem, tho. To improve speeds of my filesystems, I have created a raid 0 of 4 disks, and I place the most heavily copied disks there. The fs has subdirectories, one for each set of typically .iso files, such as Mandrakelinux or fedora. I would like to be able to just do a symlink from the original tree to the directory on the