search for: mac1

hello list i got the following pb: # xm create -f mac1/mac1.xen Using config file "mac1/mac1.xen". Error: Error creating domain: vbd: Segment not found: uname=file:/xen/mac1/swapfs but: # dmesg | grep loop loop: loaded (max 32 devices) # ls -l /xen/mac1/swapfs -rw-r--r-- 1 root root 268435457 2005-04-12 11:25 /xen/mac1/swapfs # xm list Na...

...10:05 To: Georgi Boshnakov; r-devel at r-project.org Subject: Re: [Rd] Rd parser throws error for user macros invoked with empty argument Thanks for the report and the examples - and they do not have to be that verbose, it is enough to just define and use a command, e.g. cat("\\newcommand{\\mac1}{MAC1:#1}\\mac1{}", file=f) rd <- tools::parse_Rd(f) Whenever you get an error message like "Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL'", there is a bug (at least the error message should be relevant/informative). I am testing a patch that will...

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but

Thanks for the report and the examples - and they do not have to be that verbose, it is enough to just define and use a command, e.g. cat("\\newcommand{\\mac1}{MAC1:#1}\\mac1{}", file=f) rd <- tools::parse_Rd(f) Whenever you get an error message like "Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL'", there is a bug (at least the error message should be relevant/informative). I am testing a patch that will...

...r-devel at r-project.org > Subject: Re: [Rd] Rd parser throws error for user macros invoked with empty argument > > Thanks for the report and the examples - and they do not have to be that > verbose, it is enough to just define and use a command, e.g. > > cat("\\newcommand{\\mac1}{MAC1:#1}\\mac1{}", file=f) > rd <- tools::parse_Rd(f) > > Whenever you get an error message like "Value of SET_STRING_ELT() must > be a 'CHARSXP' not a 'NULL'", there is a bug (at least the error message > should be relevant/informative). > >...

...er running Version 3.4.0 Most windows and OS X clients connect with no issues. Permissions are working correctly on shares and umask settings are working on Window 7, OS X, and XP. The annoying mystery here is that these little bugs are annoying users and taking up precious time... Most recently, Mac1 (OS X 10.6.5 smb Version 3.0.28a-apple) is able to change a directory's name and Mac2 isn't able to rename SAME directory: Both Mac1 and Mac2 have: SAME OS X 10.6.5 SAME version of Samba = Version 3.0.28a-apple SAME samba user account authenticated (user1) SAME method of accessing server...

>>> Gene, Your binaries didn't work for me, <<< I had problems with them too (I didn't see anything) >>> however I put some code in to print the byes of mac1 and mac2. In?efi_create_binding() it does go through all of the macs looking for the correct one and then finds a 100% match. In this case the mac is 8c-dc-d4-0d-a5-f0 so?&& memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { is correct <<< mmmhh that means there's a match consider...

...bar: a message will appear saying "the element cannot be opened because the original cannot be found" (sorry, this is a translation from Italian). Closing the Finder window and reopening it, will work (!!!). Seems like the Mac is disconnecting and needs to keep reconnecting. B) If Mac1 opens "file.doc" with LibreOffice. "._file.doc" will be created to lock it. Mac2 will see the lock file in finder and cannot obviously open "file.doc" read/write. Mac1 closes "file.doc" and Mac2 sees the lock file going away. However, if Mac2 tries to open...

...element cannot be opened because the original cannot be found" (sorry, > this is a translation from Italian). > Closing the Finder window and reopening it, will work (!!!). > > Seems like the Mac is disconnecting and needs to keep reconnecting. > > > > > > B) If Mac1 opens "file.doc" with LibreOffice. "._file.doc" will be > created to lock it. > Mac2 will see the lock file in finder and cannot obviously open > "file.doc" read/write. > Mac1 closes "file.doc" and Mac2 sees the lock file going away. > Howeve...

...4:10 AM, Gene Cumm via Syslinux <syslinux at zytor.com> wrote: > On Fri, Aug 28, 2015 at 3:13 PM, Derrick M <derrick.martinez at gmail.com> > wrote: > > Gene, > > > > Your binaries didn't work for me, however I put some code in to print the > > byes of mac1 and mac2. In efi_create_binding() it does go through all of > the > > macs looking for the correct one and then finds a 100% match. In this > case > > the mac is 8c-dc-d4-0d-a5-f0 so && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) > == > > 0) { is correct > > > h...

...> >We should not have 2 bypass configs with the same MAC. >I need to add a check in the bypass_master_register() to prevent this. Mac can change, you would have to check in change as well. Feels odd thought. > >The above check is to avoid cases where we have >bp1(a1, b1) with mac1 >and a2 is mis-configured with mac1, we want to avoid using a2 link events to update bp1. > >> Now bypass_master_get_bymac() will return always bp1 or bp2 - depending on >> the order of creation. >> Let's say it will return bp1. Then when we have event for a2, the >&g...

...> >We should not have 2 bypass configs with the same MAC. >I need to add a check in the bypass_master_register() to prevent this. Mac can change, you would have to check in change as well. Feels odd thought. > >The above check is to avoid cases where we have >bp1(a1, b1) with mac1 >and a2 is mis-configured with mac1, we want to avoid using a2 link events to update bp1. > >> Now bypass_master_get_bymac() will return always bp1 or bp2 - depending on >> the order of creation. >> Let's say it will return bp1. Then when we have event for a2, the >&g...

...ntinues On Aug 29, 2015, at 01:00, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: > Gene, > Your binaries didn't work for me, > <<< > I had problems with them too (I didn't see anything) > > however I put some code in to print the byes of mac1 and mac2. In efi_create_binding() > it does go through all of the macs looking for the correct one and then finds a 100% match. In this case the mac is > 8c-dc-d4-0d-a5-f0 so && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == 0) { is correct > <<< > > mmmhh that means there...

On Fri, Aug 28, 2015 at 3:13 PM, Derrick M <derrick.martinez at gmail.com> wrote: > Gene, > > Your binaries didn't work for me, however I put some code in to print the > byes of mac1 and mac2. In efi_create_binding() it does go through all of the > macs looking for the correct one and then finds a 100% match. In this case > the mac is 8c-dc-d4-0d-a5-f0 so && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == > 0) { is correct https://sites.google.com/site/genecsyslinux/1...

...a, where the laptops and the Win95 workstation can all access. (I haven't added the Mac's to this mix as yet, I think from memory they were working just fine.) From ALPHA using smbclient I can connect and map to all shared services on anything (ALPHA, WWW, OTHERWOMAN, LAPA, LAPB, WWW, MAC1, MAC2, FEP1) What is important is that LAPA and LAPB had NO problem communicating with ALPHA2 prior to a few weeks ago. There are no filewall problems or restrictions and the LAP's can Browse, get a SHARE listing, but not get access to the files or paths. (I haven't tried printers, I...

...e='none' type='raw'/> <source file='/vm/path/disk.raw'/> <!-- <target dev='vda' bus='virtio'/> --> <target dev='vda'/> </disk> <interface type='bridge'> <mac address='mac1'/> <source bridge='br0'/> <!-- <model type='e1000'/> --> </interface> <interface type='bridge'> <mac address='mac2'/> <source bridge='br9'/> <!-- <mode...

On Mon, Aug 31, 2015 at 06:08:19AM -0400, Gene Cumm via Syslinux wrote: > On Aug 30, 2015 8:42 PM, "Derrick" <derrick22 at gmail.com> wrote: > > > > Gene thanks, here is the output > > > > My IP is 10.2.49.10 > > Img @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 = 8cdcd40ca5f0 > > Udp @ 71d89718 =

...yslinux < syslinux at zytor.com> wrote: >> >> On Fri, Aug 28, 2015 at 3:13 PM, Derrick M <derrick.martinez at gmail.com> wrote: >> > Gene, >> > >> > Your binaries didn't work for me, however I put some code in to print the >> > byes of mac1 and mac2. In efi_create_binding() it does go through all of the >> > macs looking for the correct one and then finds a 100% match. In this case >> > the mac is 8c-dc-d4-0d-a5-f0 so && memcmp(mac_1, mac_2, PXE_MAC_LENGTH) == >> > 0) { is correct >> >> h...

...bp2 > a1 b1 a2 b2 > > > a1 and a2 have the same mac and bp1 and bp2 have the same mac. We should not have 2 bypass configs with the same MAC. I need to add a check in the bypass_master_register() to prevent this. The above check is to avoid cases where we have bp1(a1, b1) with mac1 and a2 is mis-configured with mac1, we want to avoid using a2 link events to update bp1. > Now bypass_master_get_bymac() will return always bp1 or bp2 - depending on > the order of creation. > Let's say it will return bp1. Then when we have event for a2, the > bypass_ops->slave_...

...with the same MAC. > >I need to add a check in the bypass_master_register() to prevent this. > > Mac can change, you would have to check in change as well. Feels odd > thought. > > > > > >The above check is to avoid cases where we have > >bp1(a1, b1) with mac1 > >and a2 is mis-configured with mac1, we want to avoid using a2 link events to update bp1. > > > >> Now bypass_master_get_bymac() will return always bp1 or bp2 - depending on > >> the order of creation. > >> Let's say it will return bp1. Then when we have...