I just wanted to know whether it's possible to send a command to all raspi at once

09:07

<alkisg>

!epoptes

09:07

<ltsp>

epoptes: Epoptes is a computer lab administration and monitoring tool. It works on Ubuntu and Debian based labs with LTSP or non-LTSP servers, thin and fat clients, standalone workstations, NX clients etc. More info: http://www.epoptes.org

09:07

<alkisg>

epoptes can send a command to multiple ltsp clients

09:07

<ronstar>

ah right, haven't looked hard enough then

09:08

laters

09:08

ronstar has left IRC (ronstar!c3466c41@gateway/web/freenode/ip.195.70.108.65)

tbh not the important ones lol ..the bottom line is i will send back this mini pc

12:41

one big issue with is it has no ntfs support on the bios

12:42

still i have another system that is uefi

12:42

so we can continue testing just with some thing that is going to be allot easier to work with

12:45

intel cpu in that mini pc is weird to you need to pxe it a 32bit image but it must a run 64bit os from what I was told so that is ugly .. and which brings me to dnsmasq and why it wont get recognized with option client-arch 7 and also not get a IP unless its not client-arch 7 but thats what dnsmasq was report it as when it was getting a ip

12:53

all this which has me baffled

12:53

if its X86-64_EFI

12:53

then it should be client-arch 9

13:06

sbalneav has joined IRC (sbalneav!~sbalneav@wnpgmb0311w-ds01-165-236.dynamic.mtsallstream.net)

13:09

<bennabiy>

slog1235: What client are you working with?

13:11

alkisg: how do you install printers to a fat client? I did ltsp-pnp from a server which had printers installed, but cannot print from my fat client (cups server not enabled_)

13:11

<slog1235>

its a ECS Liva bat-mini v1.0 .. basically its a celleron baytrail M system on chip deal with integrate eMMC and 2 GB of DDR3-UL ram

13:11

<bennabiy>

hmm, sounds similar to the nexbox I am working with

13:12

mostly set up for android

13:12

or windows

13:12

<slog1235>

yeah this one they give you instruction on how to isntall ubuntu via fat32

13:12

<bennabiy>

It is not properly netbooting UEFI, but I am not saying I have it set up correctly

13:12

<slog1235>

so I guess I could fat client it that way

13:13

<bennabiy>

I installed Ubuntu just fine as 64 bit etc

13:13

network booting is just not working

13:13

and I cannot put it in legacy modem because legacy mode does not exist on this hardware

13:13

modem=mode*

13:19

<slog1235>

yeah

13:19

that is the same for me

13:19

http://pastebin.com/dSyMPHyx

13:30

I wonder if its because the proxy code is not forwarding authoritative flag

13:41

gdi2k has left IRC (gdi2k!~gdi2k@119.94.27.63, Quit: Leaving)

13:45

<bennabiy>

slog1235: have you tried iPXE instead of gpxe?

13:46

I am probably not going to be able to work on this this weekend... building a deli. Will have to look at this more after the weekend

13:47

slog1235: did you try this ? av

13:47

http://doc.rogerwhittaker.org.uk/ipxe-installation-and-EFI/

13:48

<slog1235>

let me have look at that again

13:49

i was going to try with shim.efi as well

13:56

<alkisg>

bennabiy: the general idea about printers is, you enable printer sharing on the server, and leave the default CUPS_SERVER=server for the clients

13:56

mikkel has left IRC (mikkel!~mikkel@mail.dlvs.dk, Quit: Leaving)

13:56

<alkisg>

bennabiy: that way you manage/install printers in one place only

13:56

ben_roose has joined IRC (ben_roose!~roose@roose.cs.wichita.edu)

13:57

<bennabiy>

alkisg: It was very much easier to administer the server from a thin client, but now that I am on a fat client, I can see the need to either use X2GO or such to be able to directly make changes on the server (things that are better done outside ssh / cli)

13:58

<alkisg>

Here we have the teacher log in and use the server directly

13:58

<bennabiy>

I have a monitor hooked up to the server and to my fat client, so I can switch between them easily, but somewhat inconvenient

13:59

<alkisg>

We don't want to waste the extra seat that the server provides

13:59

<bennabiy>

alkisg: I have been running from the server in the past, but I put myself on a fat client to lessen my impact on the other users, as well as to debug the process and fine tune it

btw, (03:22:10 μμ) bennabiy: alkisg: CSM is only if the client has the OPROM ==> afaik, "oprom" is firmware on adapter cards, while csm is part of the motherboard firmware, i.e. those 2 are not related concepts

14:05

<bennabiy>

alkisg: I looked in the firmware, and it says next to legacy (OPROM only)

14:05

and it does not show up in the firmware

14:05

<alkisg>

legacy what? video?

14:05

or network stack?

14:05

<bennabiy>

network

14:05

<alkisg>

OK, it's not related to what we were discussing

14:05

That will be activated when you activate csm

14:06

<bennabiy>

ok, tell me again how to do it? and I will try it

14:06

secure boot is disabled, etc

14:06

<alkisg>

search the logs for "alkisg" and "bennabiy" on the same line; I pasted the link 3-4 days ago, I don't have it handy now

I think it was saying something like "set a supervisor pass to disable secure boot, then save, reenter firmware, switch to legacy"

14:12

Anyway, are you still having issues booting those machines over the network? either with uefi or with a local kernel?

14:14

<bennabiy>

I cannot network boot yet, but can load an Ubuntu install, so I know UEFI works for local boot

14:15

I set the password, but secure boot was not enabled in the first place, and no legacy mode to select

14:15

Btw, "In order to change the secure boot setting, you need to set a supervisor password. Once password is set, secure boot setting will no longer be greyed out. Disable. Switch UEFI to legacy and save. Now enter BIOS again and clear the supervisor password."

14:15

UEFI only shows IPV4 V6 and Both V4 and V6

14:15

no legacy

14:16

It mentions it on the side, with a comment OPROM only)

14:16

<alkisg>

"switch uefi to legacy" is not for the network booting

14:16

It's for the whole firmware

14:16

<bennabiy>

I could not find that

14:16

<alkisg>

Once you enable legacy firmware, i.e. bios, then you won't even see an uefi network booting option at all

14:16

OK

14:16

<bennabiy>

only thing mentioning legacy is legacy android

14:16

as os

14:16

or GMIN

14:17

whatever that is

14:17

<alkisg>

Anyways, what about the local kernel thing? Did you made that work?

14:17

<bennabiy>

It is the worst firmware I have ever worked with

14:17

I only got to a busy box

14:18

<alkisg>

With what error message?

14:18

<bennabiy>

will have to do it again to see

14:18

<alkisg>

OK, also note /proc/cmdline when you do

14:18

I've been using that method for years in a laptop of mine

14:19

<bennabiy>

ok, one moment

14:19

<alkisg>

(I have a local uefi installation there for tests, so I don't want to have to enter the firmware to switch to csm every time I netboot it)

If netrunner is based on kubuntu, then you just need to use the stable epoptes ppa

21:44

!termbin

21:44

<ltsp>

termbin: To share the output of some command, run: command | nc termbin.com 9999 . This executes command , sends its output to termbin.com, and returns a URL. Paste this URL here to share the command output with us.