search for: device_nam

...1e1 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -406,7 +406,7 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, u64 *subvol_rootid, struct btrfs_fs_devices **fs_devices) { substring_t args[MAX_OPT_ARGS]; - char *opts, *orig, *p; + char *device_name, *opts, *orig, *p; int error = 0; int intarg; @@ -457,8 +457,14 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, } break; case Opt_device: - error = btrfs_scan_one_device(match_strdup(&args[0]), +...

Hi Mikhail, I was trying to figure out how to do the following in compiler driver. 1. mcc16 driver has a -p <device_name> option. Now from this device_name I want to be able to construct a file name like "device_name.o" and pass that to the linker. Unpack_values "p" gives me the device_name, but I do not know how to add ".o" suffix to it. something like: (not_empty "p")...

Hi Sanjiv, On Thu, Nov 19, 2009 at 5:07 AM, Sanjiv Gupta <sanjiv.gupta at microchip.com> wrote: > Hi Mikhail, > > I was trying to figure out how to do the following in compiler driver. > > 1.  mcc16 driver has a -p <device_name> option. Now from this device_name I > want to be able to construct a file name like "device_name.o" and pass that > to the linker. Unpack_values "p" gives me the device_name, but I do not know > how to add ".o" suffix to it. > > something like: >...

...t statvfs statvfsbuf; + size_t blocks; if (data->debug >= 3) printf ("supermin: ext2: copy_file %s -> %s\n", src, dest); @@ -649,6 +653,20 @@ ext2_copy_file (struct ext2_data *data, const char *src, const char *dest) caml_copy_string (data->fs->device_name)); } + /* Check that we have enough free blocks to store the resulting blocks + * for this file. The file might need more than that in the filesystem, + * but at least this provides a quick check to avoid failing later on. + */ + blocks = ROUND_UP (statbuf.st_size, data->fs->bl...

...t2_filsys fs, const char *src, const char *dest) +ext2_copy_file (struct ext2_data *data, const char *src, const char *dest) { errcode_t err; struct stat statbuf; @@ -551,13 +556,13 @@ ext2_copy_file (ext2_filsys fs, const char *src, const char *dest) * Note we cheat by looking at fs->device_name (which is the output * file). We could store this filename separately. */ - if (fs->device_name && statvfs (fs->device_name, &statvfsbuf) == 0) { + if (data->fs->device_name && statvfs (data->fs->device_name, &statvfsbuf) == 0) { uint64_t s...

...uot;%" PRIu64 " bytes, available only %llu\n", + src, blocks, data->fs->blocksize, (uint64_t) statbuf.st_size, ext2fs_free_blocks_count (data->fs->super)); unix_error (ENOSPC, (char *) "block size", data->fs->device_name ? caml_copy_string (data->fs->device_name) : Val_none); -- 2.5.5

...driver What I *can* do --- Print just fine on RH9/Samba server to the directly connected HP Office jet via USB connection. From Windoze client, access all appropriate shares on Server -- read/write, etc. From client, I can print from Windoze CL, e.g. C:\echo Blah, blah > \\Samba_server\device_name. What I can*not* do --- From the client Win2K config printer window do a test print. When I pull up "properties" on the shared printer, I get the "Access denied..." error. All suggestions, recommendations and jeers cheerfully accepted... TIA, te

...u (guestfs_h *g); extern struct version guestfs_int_qemu_version (guestfs_h *g, struct qemu_data *); extern int guestfs_int_qemu_supports (guestfs_h *g, const struct qemu_data *, const char *option); extern int guestfs_int_qemu_supports_device (guestfs_h *g, const struct qemu_data *, const char *device_name); +extern int guestfs_int_qemu_mandatory_locking (guestfs_h *g, const struct qemu_data *data); extern char *guestfs_int_drive_source_qemu_param (guestfs_h *g, const struct drive_source *src); extern bool guestfs_int_discard_possible (guestfs_h *g, struct drive *drv, const struct version *qemu_ve...

...03 00 00 08 SCSI device sda: drive cache: write through sda: sda1 sda2 sda3 sd 0:1:0:0: Attached scsi disk sda Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05 scsi 0:0:0:0: SSP: handle(0x000a), sas_addr(0x500000e1150ca882), device_name(0x0000000000000000) scsi 0:0:0:0: SSP: enclosure_logical_id(0x5842b2b0194dce00), slot(1) scsi 0:0:0:0: qdepth(254), tagged(1), simple(1), ordered(0), scsi_level(6), cmd_que(1) Vendor: FUJITSU Model: MBA3147RC Rev: D306 Type: Direct-Access ANSI SCSI revision: 05...

Patches 1 & 2 were posted previously here: https://www.redhat.com/archives/libguestfs/2016-May/msg00134.html Patch 3 is a hack so I can test this using my own version of qemu (the `-L ?' stuff is not upstream). Patch 4 is where the real action takes place: Replace the caching of qemu features in blob-like files with a sqlite database. Probably the best way to approach this patch is to

NOTE: Not for upstream, yet. This depends on 3 non-upstream patches. - The qemu rework in libguestfs, which in turn depends on what Pino is up to. - Support for '-L ?' in qemu: https://lists.gnu.org/archive/html/qemu-devel/2016-05/threads.html#02596 - Support for bios-fast.bin in qemu: https://lists.gnu.org/archive/html/qemu-devel/2016-05/threads.html#02408 This commit

This commit uses -bios bios-fast.bin if available, which basically stops SeaBIOS from trying to do PCI probing during boot, which is a waste of time when using the -kernel option. v1 -> v2: - Rebase on top of Pino's work. This still has 3 dependencies: - The qemu memoization work (v2). - Support for '-L ?' in qemu:

Hi, I''m trying to automate the conversion of a PDF document received via a browser upload to a tiff image via ghostscript. I have the PDF data in a string, and I need the tiff data returned into a string. The general command I want to emulate is: type test.pdf | "c:\program files\gs\gs8.56\bin\gswin32c.exe" -q -dNOPAUSE -dBATCH -sDEVICE=tiffg4 -sOutputFile=- > test5.tiff

v1 -> v2: - Rebase on top of Pino's version work. Two patches went upstream, these are the two remaining patches. Note the generation number is still inside the qemu.stat file. We could put it in the filename, I have no particular preference. Rich.

...u_data; extern struct qemu_data *guestfs_int_test_qemu (guestfs_h *g, struct version *qemu_version); extern int guestfs_int_qemu_supports (guestfs_h *g, const struct qemu_data *, const char *option); extern int guestfs_int_qemu_supports_device (guestfs_h *g, const struct qemu_data *, const char *device_name); -extern int guestfs_int_qemu_supports_virtio_scsi (guestfs_h *g, struct qemu_data *, const struct version *qemu_version); extern char *guestfs_int_drive_source_qemu_param (guestfs_h *g, const struct drive_source *src); extern bool guestfs_int_discard_possible (guestfs_h *g, struct drive *drv,...

Hello!! I'm a sysadmin at La Laguna University in Spain. We are using NUT to manage our UPS with great success, but we miss a feature and we would like to send this patch to you. If you apply this patch running upsd -c info you'll get information about client connections in syslog. This is very simple and helpfull if you have hundreds of servers connected to the same upsd. Thank you for

...pt_subvolid, "subvolid=%s"}, {Opt_device, "device=%s"}, {Opt_nodatasum, "nodatasum"}, {Opt_nodatacow, "nodatacow"}, @@ -673,8 +673,8 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, { substring_t args[MAX_OPT_ARGS]; char *device_name, *opts, *orig, *p; + char *num = NULL; int error = 0; - int intarg; if (!options) return 0; @@ -704,16 +704,14 @@ static int btrfs_parse_early_options(const char *options, fmode_t flags, } break; case Opt_subvolid: - error = match_int(&args[0], &intarg); - if (!erro...

...ot.server.1.address="" voIpProt.server.1.port="" ... /> Change these two values to the address of your asterisk server, and the sip port (5060 by default) 4. In /etc/asterisk/sip.conf you'll need to add an entry for each phone. It should look something like this: [device_name] <--------- whatever you want, but needs to be the same as auth.userId above type=friend secret=<password> <-------- whatever you want, but the same as auth.password above callerid=<whatever> host=dynamic <------------- If you're using DHCP, or the...

Doing qemu feature detection in the direct backend takes ~100ms because we need to run `qemu -help' and `qemu -devices ?', and each of those interacts with glibc's very slow link loader. Fixing the link loader is really hard. Instead memoize the output of those two commands. This patch series first separates all the code dealing with qemu into a separate module (src/qemu.c) and

These assorted patches end up with adding virtio-scsi support to libguestfs. It passes libguestfs-test-tool, but I haven't yet tried to run the full set of tests. In theory > 26 devices can be added, but it's likely that certain parts of the daemon will break if you actually try this. This of course needs to be fixed. Thanks Paolo Bonzini for invaluable help. Rich.