WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Need guidance on atypical but simple setup  (Read 5447 times)

Offline patrikg

  • Wiki Author
  • Hero Member
  • *****
  • Posts: 662
Re: Need guidance on atypical but simple setup
« Reply #15 on: November 26, 2015, 06:50:53 AM »
You could also add nodhcp to the commandline for the kernel (bootcodes), to tell that udhcpc don't run with boot so you don't need to kill the udhcpc in your eth0.sh file.

Hi otheus
Basically all the networking applet does is create a script in  /opt/, mine looks like this:
Code: [Select]
tc@box:~/guilib/grabber/grabber-1.1$ cat /opt/eth0.sh
#!/bin/sh
pkill udhcpc
ifconfig eth0 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1
echo nameserver 68.237.161.12 > /etc/resolv.conf
echo nameserver 71.243.0.12 >> /etc/resolv.conf
tc@box:~/guilib/grabber/grabber-1.1$
That script is then called from  /opt/bootlocal.sh.

Offline otheus

  • Newbie
  • *
  • Posts: 11
Re: Need guidance on atypical but simple setup
« Reply #16 on: November 27, 2015, 02:31:13 AM »
"Show us your bootcodes"  -- you were looking at them in the previous posts. That's it. All of them. opt=XXX or tce=XXX or some combination of the two.


The documentation indicates (but it's not 100% clear) on the wiki and book that tce=DRIVE/dir should do the following:
  • Attempt to open the drive /dev/DRIVE and mount it (somewhere)
  • Find a directory named dir within the mounted filesystem.
  • If the directory does not exist, create it, with various subdirectories.
  • Make that directory available (somehow... bind mount??) as /tce

Am I correct that this is the expected behavior? If not, can someone point me to the documentation or source that does define the actual behavior? I can read source code; it just helps to know which code I need to look for.

Offline Misalf

  • Hero Member
  • *****
  • Posts: 1702
Re: Need guidance on atypical but simple setup
« Reply #17 on: November 27, 2015, 02:56:54 AM »
That's not
"Show us your bootcodes"
but
Show us the output of 'showbootcodes'.

For example, This is what I get
Code: [Select]
logo.nologo  cron  quiet loglevel=3  vga=788 video=inteldrmfb:ywrap,mtrr:3  blacklist=pcmcia,ssb,b43,bcma,rt2860sta,bluetooth,btusb  noutc  tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce-6.x swapfile=sda1  nozswap mydata=myxorg  laptop  nodhcp  desktop=openbox 
Download a copy and keep it handy: Core book ;)

Offline otheus

  • Newbie
  • *
  • Posts: 11
Re: Need guidance on atypical but simple setup
« Reply #18 on: November 27, 2015, 07:00:37 AM »
That's not
"Show us your bootcodes"
but
Show us the output of 'showbootcodes'.

For example, This is what I get
Code: [Select]
logo.nologo  cron  quiet loglevel=3  vga=788 video=inteldrmfb:ywrap,mtrr:3  blacklist=pcmcia,ssb,b43,bcma,rt2860sta,bluetooth,btusb  noutc  tce=UUID="cb6f8b98-91fd-4c96-b115-3d2bb9cb3e57"/tce-6.x swapfile=sda1  nozswap mydata=myxorg  laptop  nodhcp  desktop=openbox 

Heh. OK:

Code: [Select]
tc@box:~$ showbootcodes
opt=vdb1/opt tce=vd1/tce


Offline Misalf

  • Hero Member
  • *****
  • Posts: 1702
Re: Need guidance on atypical but simple setup
« Reply #19 on: November 27, 2015, 08:03:11 AM »
If I specify both opt= and tce= to the same device, the system never boots. Example: boot code is:
   opt=vdb1/opt
Code: [Select]
tc@box:~$ showbootcodes
opt=vdb1/opt tce=vd1/tce

"vdb1" != "vd1"
Download a copy and keep it handy: Core book ;)

Offline otheus

  • Newbie
  • *
  • Posts: 11
Re: Need guidance on atypical but simple setup
« Reply #20 on: November 27, 2015, 10:13:32 AM »
That was a typo in the manual copy/paste operation. (I'm using VNC which doesn't support text copy/paste, so I manually typed in what I saw on the screen).

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Need guidance on atypical but simple setup
« Reply #21 on: November 28, 2015, 05:10:31 PM »
opt=vdb1/opt should be opt=vdb1
You cannot specify a directory with opt or home.