similar to: Does anyone think a mini-Samba server would be useful?

I've got an embedded x86 system built with Yocto, which boots from a USB flash drive. It uses a loop mount to give access to an ext3 root file system contained within a FAT16 file, which means it has persistent storage. What I want is something that boots from the flash drive, but copies everything into a large RAM disk, and runs from there, so that it doesn't touch the flash drive once

For a long time, I've had a share set up on my Samba server (Ubuntu 14.04) that gives me read/write access to /. (It's a machine that does Yocto Linux builds, nothing proprietary on it.) I routinely accessed it from a couple of Win7 boxes and one Mac. A few days ago, I installed some Ubuntu updates, and suddenly the share stopped working. I could open the machine, and I could open the

I have an embedded box (Yocto Project based linux distro) to which I'm adding Samba 3.6 (from OpenEmbedded). All I need it for is to provide one browsable file share that allows read/write access to anyone on the network. But I want it to be password protected. My best guess as to what goes into smb.conf is: [global] workgroup=WORKGROUP netbios name=MACHINE security=share

I'm having trouble changing the machine name programmatically on Samba 4 (running under systemd). There's no "netbios name" option in smb.conf, so I'm relying on it using the hostname. Here's what I'm doing: 1) Call sethostname() with the new name. 2) Write the same name into /etc/hostname, to make it nonvolatile. 3) Read a decimal number from /var/run/smbd.pid.

I'm using the Yocto Project to build an embedded distro, to which I'm adding Samba 3.6 from OpenEmbedded. Doing so increases my root file system from about 63MB to 175MB. I seem to be building a large Samba server with a small ancillary operating system tacked onto it. I listed the files in my file system image, and see that lots of the commands are quite large. I understand that Samba 4

I have a Windows home network with a bunch of Windows boxes and two Ubuntu boxes. Everything can access shares on everything else, with one exception: no one can get to the one share on the second Ubuntu box which I just added to the system. All my machines have one user account (admin privileges in Windows) with the name "pauld" and the same password. In an effort to solve this problem

> From: Reindl Harald > > just restart the samba server instead only reload? But how do you do that in C? Frankly, I don't even know how to do that from the command line. This is an embedded system without a lot of high-level utilities like you get on Ubuntu. -- Ciao, Paul D. DeRocco Paul mailto:pderocco at ix.netcom.com

> From: Reindl Harald > > besides that you did not provide the info "embedded system" - > when you > have systemd you also have "systemctl restart > whatever.service" and in > PHP it would be passthru('command') > > you don't know how you restart a service via CLI - seriously? I know how to do it through systemctl, but I was

I've added Samba 3.6.8 to my Gumstix build, and I'd like to include a single Samba user and password as part of the initial image. Can I do that by manually adding the user to the TDB database, and then copying the resulting file into my build machine and including it in the build? If so, where is that file normally? (The few locations I've found mentions of via Google didn't have

>> Thanks. I've looked through all the links, and it seems everything is >> fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, >> but it didn't help). I'd be glad to provide more details, but the error >> message is the only info I've got by now. It seems nothing else can be >> got from syslinux shell without modifiying the

Systemd service files are generally coming with packages. This means these files can be overwritten by some system update if this updates also your Samba packages (note: I never had nor tested that behaviour with Samba packages, but it happens for other packages). 2016-02-23 8:39 GMT+01:00 L.P.H. van Belle <belle at bazuin.nl>: > Uh... just add : > > netbios name = PC_NAME >

I'm interested in using smbclient in an embedded Linux system, to copy files to a Windows file share. I don't need the entire samba suite. I'd like to get a smbclient compile that is reasonably small (less than 3 MB ideally). I'm building the embedded Linux system cross-compiled for an ARM based platform using Yocto. Yocto has support for building samba. But it is aimed at the

I've read what I can find about SMB passwords, but I don't get what they are. Are they Unix passwords or an alternative to them? If I have a file share, and the underlying file system requires some sort of credentials to access it, what is the relationship between that and an SMB password? If a client tries to access the share, using a user account that is listed in the smbpasswd file,

Dear all, I am currently trying to cross compile R3.5.2 using X86 host and trying to cross compile for ARM target (raspberry pi 3 running on linux system generated by buildroot). The problem I am encountering is that the compilation fails because the current R buildsystem I trying to execute the R binary generated for Arm arch on the host X86 computer. My question is: Is there an R

Hi Johannes, Thank you for your quick feddback. As I am using linux os build with buildroot on my raspberry pi I can't use package manager such as apt-get to install R. What I need to do is to get the precompiled R for arm arch and then when I build my linux image using buildroot I include the R precompiled package to my rootfs. Could you please send me a link where I can download

On 11/22/19 2:46 PM, David Blaikie wrote: > Sorry, I'm not sure I follow/understand your email, or what sort of > replies/responses/discussion you're hoping to get from it - perhaps > you could rephrase and/or provide more detail? David, Sorry its more to give you guys a heads up in case they ask about it being of interest and know that its something of interest outside that

Thanks. I've looked through all the links, and it seems everything is fine wrt. to what was mentioned there (I've disabled 64 bits in mke2fs, but it didn't help). I'd be glad to provide more details, but the error message is the only info I've got by now. It seems nothing else can be got from syslinux shell without modifiying the code. I've tried to make it load the kernel

Is it possible to find a repository that hold a newer version of tar. The current version is 1.26 I have some students trying to build Yocto project on my Centos 7 host, but OpenEmbedded reports incompatibility problems with the current version of tar. I thank you on beforehand for any help. |< -- Med venlig hilsen Klaus Kolle Teknikumingeni?r, B.Sc.EE., e-mail : klaus at kolle.dk

Hi! I'm using a Toradex apalis imx6 board to make a project for my bussiness and I need Icecast running on it, but I can't compile it in the board. It shows an error in "xslt" while compiling- I'm using Yocto. Do yow have any idea how can I compile Icecast source code in my Toradex apalis board without using this xslt? Thanks in advance!

Greetings All, I've already mentioned this on the GCC side but it seems that the Yocto Project has a class for testing upstream projects. The project is used for building embedded distributions but due to the ability with bitbake and the amount of supported upstream projects I've asked them to mention that other projects are interested in seeing this happen at the usual Embedded