similar to: [PATCH 1/7] ln: Check snprintf() return values

Displaying 20 results from an estimated 500 matches similar to: "[PATCH 1/7] ln: Check snprintf() return values"

2008 Oct 11
1
[PATCH] fstype: Fix ext4/ext4dev probing
Enhance fstype so it properly takes into account whether or not the ext4 and/or ext4dev filesystems are present, and properly handles the test_fs flag. The old code also has some really buggy checks --- for example, where it compared the set of supported ro_compat features against the incompat feature bitmask: (sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP) I
2011 Jul 08
4
[PATCH 0/4] usr/kinit checkpatch
Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce
2011 Aug 07
2
[PATCH] kinit minor checkpatch cleanup
coding style fixes. FIXME: check that compiled bin the same1!! --- usr/kinit/initrd.c | 3 ++- usr/kinit/kinit.c | 12 ++++-------- usr/kinit/kinit.h | 20 ++++++++++---------- usr/kinit/name_to_dev.c | 6 +++--- usr/kinit/nfsroot.c | 5 ++--- 5 files changed, 21 insertions(+), 25 deletions(-) diff --git a/usr/kinit/initrd.c b/usr/kinit/initrd.c index
2010 Nov 20
3
[PATCH 1/4] utils: cleanup unused includes
several errno.h for no good reasons. cleanup losesetup which is not using getopt_long, thus doesn't need getopt.h included. Move stdarg.h include up in losesetup to more proper place. Signed-off-by: maximilian attems <max at stro.at> --- usr/utils/dmesg.c | 1 - usr/utils/losetup.c | 4 +--- usr/utils/mkfifo.c | 1 - usr/utils/nuke.c | 1 - usr/utils/umount.c | 1
2019 Oct 07
0
[klibc:master] fstype: Drop obsolete support for "ext4dev"
Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 8 Oct 2019 00:13:20 +0100 [klibc] fstype: Drop obsolete
2006 Aug 18
3
connect to postgres db
I''ve followed the tutorial and just don''t get it. How do I connect my ruby/rails sample app to my postgres database. I did follow step 1-4 of the tutorial, I go to step 5: (http://wiki.rubyonrails.org/rails/pages/TutorialStepFive) and try the "rake" commmand and get this: rake aborted! no such file to load -- postgres so I ran with -trace and get this:
2011 Aug 04
0
[PATCH] fstype: fix possible null deref in check_for_modules()
Make check_for_modules() more readable, just allways call continue on NULL return. That way the possible null dereference in strlen is no longer possible. This doesn't yet make it unsuck, but is a small step. Seen fixed too in blkid there with patch adding ko.gz support. Cc: Karel Zak <kzak at redhat.com> Signed-off-by: maximilian attems <max at stro.at> ---
2014 May 05
2
[PATCH] test-charset-fidelity: allow to skip testing specific FSes
Allow to skip testing the filesystem "foo" if the environment variable SKIP_TEST_CHARSET_FIDELITY_foo=1 is set. This way it possible to not test one or more filesystems without disabling the test altogether. --- tests/charsets/test-charset-fidelity.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/tests/charsets/test-charset-fidelity.c
2007 Nov 28
7
puppetrun failing: "connect'': tlsv1 alert unknown ca"
I''m trying to get puppetrun to work, without luck so far. I have my puppetmaster and clients working fine with the clients polling the master. Now I want to be able to force an update. Using version 0.23.2 On the client I set listen=true and created the namespaceauth.conf file. Restarted puppetd and it appears fine. On the master I run puppetrun as root and get root@plane:/etc/puppet#
2010 Mar 02
17
[PATCH 00/16] External building, update for 2.6.33 and multiple root devices.
The following patchset implements 3 seperate series of changes. External Building ================= Patches 1 through 8 enable to use of klibc's build system while leaving the src tree pristine (and potentially read only). Specifically: - srctree=<Sources for klibc> - objtree=<Ouput directory for klibc> - KLIBCKERNELSRC=<Kernel sources> - KLIBCKERNELOBJ=<Kernel
2012 May 04
2
[PATCH] run-init: add drop_capabilities support
Building on the work in ff0a614bd724f6c4c6a5014a9955dc1bc028f336, this moves the capability code down into the run-init library, so that run-init can use it as well, via the new "-d" flag. Signed-off-by: Kees Cook <kees at outflux.net> --- usr/kinit/Kbuild | 3 +-- usr/kinit/capabilities.h | 10 ++++++++++ usr/kinit/kinit.c | 6 +++---
2014 Dec 17
3
[PATCH 0/3] Allow environment variables to have boolean values.
https://bugzilla.redhat.com/show_bug.cgi?id=1175196 Currently if you write something like LIBGUESTFS_DEBUG=0 or LIBGUESTFS_DEBUG=true then it doesn't do what you probably expect. This patch series fixes that. Rich.
2011 Jul 07
5
[PATCH 0/5] checkpatch cleanups
It seems checkpatch errors krept in, this is a first go. Next run will go into usr/kinit directory. No code changes, just codingstyle fixes (verified with size(3)). maximilian attems (5): [klibc] sleep: have argument on next line [klibc] readklink: remove unneeded braces [klibc] mount: whitespace policy [klibc] ls: fix various checkpatch complaints [klibc] tests: checkpatch fixlets
2007 Jun 14
19
Please test export/collect from svn
For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction
2006 Jan 31
1
approximation to ln \Phi(x)
I am using pnorm() with the log.p=T argument to get approximations to ln \Phi(x) and qnorm with the log.p=T argument to get estimates of \Phi^{-1}(exp(x)). What approximations are used in these two functions (I noticed in the source pnorm.c it doesn't look like Abramowitz and Stegen) and where can I find the citation? Thanks, Richard Morey
2004 Feb 21
1
[PATCH] ln for klibc utils
this implements a ln(1) with -f and -s support. diff -p -purN klibc-0.112/utils/Makefile klibc-0.112.utils/utils/Makefile --- klibc-0.112/utils/Makefile 2004-02-21 23:49:26.000000000 +0100 +++ klibc-0.112.utils/utils/Makefile 2004-02-22 01:23:17.000000000 +0100 @@ -6,7 +6,7 @@ MAKEDEPS = -Wp,-MD,.$(subst /,-,$*). CFLAGS = $(MAKEDEPS) $(OPTFLAGS) $(REQFLAGS) -W -Wall LIBS =
2006 Aug 14
1
Possible to alias ("ln") a folder?
Greetings - I've got an interesting issue that has cropped up due to some brain-dead "functionality" in mobile Windows Mobile clients... Our mail infrastructure traditionally uses "Sent" as our sent items folder. This is the default. However, WM puts it's sent messages in a folder called "Sent Items", and does not let you change it. Is there any proper
2009 Oct 19
1
ln: creating symbolic link `file.txt': Operation not supported, Mounted to Windows 2003 shared
I did a couple of research and found no real solutions, so I thought I posted this on the samba mailing list. The date today is October 19, 2009 and I am sure a lot of people is also finding a fix. My server is running Debian Linux (lenny) -- where I am mounting the windows share and trying to link My shared folder is running Windows 2003 Server I mounted the windows shared folder on my debian
2005 Jul 10
2
Off topic -2 Ln Lambda and Chi square
Dear R : Sorry for the off topic question, but does anyone know the reference for the -2 Ln Lambda following a Chi Square distribution, please? Possibly one of Bartlett's? Thanks in advance! Sincerely, Laura Holt mailto: lauraholt_983 at hotmail.com
2011 Jul 13
9
[PATCH 0/8] switch_root() enhancements
On a train ride to Bruxelles, brought out my axe and directly attacked run_init(8). run_init(8) is dead, long live switch_root(8). The next run on switch_root(8) involves fdopendir, so another push for the upcoming stdio 1.6 branch. The following is boot tested with initramfs-tools, kinit(8) tests would very much be appreciated!? Michal Suchanek (1): [klibc] switch_root: Fix single file